Terms of Service

Version 1.1, in effect from 2026-06-01.

These terms cover the purchase and use of the LumasPDF SDK. They apply to you as the customer and, where you buy on behalf of a company, to that company.

They are versioned. When they change, the new version gets a new number and the previous one stays published at its own address. What you accepted is recorded against the version number you saw, so both sides can always read the same words.

What you are buying

A LumasPDF purchase is three things: a licence to use the engine in software you build, an entitlement to download the package your licence names, and, if you bought one, a maintenance term.

The licence is delivered as a signed key. You paste it into your application; the engine checks the signature locally. There is no account to activate, no server to reach, and nothing that stops working if our systems are unavailable.

The four things a key records

Edition

Which capabilities the engine enables -- creation, import, optimisation, rendering, and whether source code is included.

Package

Which of the seventeen download packages the key is for. The engine refuses to run on a platform that package does not ship binaries for.

Seats

How many developers the licence covers. Recorded in the key and not counted by any code -- see below.

Build window

Which engine builds the licence covers, expressed as a build date rather than a calendar date.

The build window

A maintenance term sets a window over BUILD DATES. When the engine checks a key it compares that window against the date the binary you are running was cut. It never reads your system clock.

The consequence is worth stating plainly, because most software licences do not work this way: nothing you have already built stops functioning, whatever happens to your account with us. Ending maintenance means you stop receiving newer builds and stop being entitled to download them. It does not reach into software you have shipped.

Seats

The number of seats you bought is recorded in the key. No part of the engine or of this site counts installations, and there is no mechanism that could. Your portal has a seat register so you can record who holds what for your own compliance; it is a record you keep, not a limit we impose.

If your team grows, buy the additional seats. We are relying on you to do that, and saying so is more honest than implying an enforcement that does not exist.

Redistribution

Every edition is royalty-free for redistribution of the engine inside your own application. You owe nothing per copy, per end user or per document produced.

What you may not do is redistribute the SDK itself -- the headers, the bindings, the examples, the documentation or a standalone copy of the engine binary -- as a development kit, or make its functionality available to third parties as a competing library or service.

Support

Support is provided through the portal for the duration of your maintenance term. It covers defects, integration questions and documentation gaps.

A reproducible defect becomes a tracked issue, and you are notified when a release fixes it. We do not commit to a fix date in these terms; the ticket tells you where the work stands.

Warranty and liability

The SDK is supplied as it is. We do not warrant that it is free of defects or that it will meet a requirement we have not agreed in writing.

To the extent the law allows, our total liability under these terms is limited to the amount you paid for the licence in question. Nothing here limits liability that cannot lawfully be limited.

Changing these terms

We may publish a new version. Changes apply from the effective date of the new version and are never applied retroactively to a purchase already made.

Every version stays readable at its own address, and the version you accepted is the one recorded against your account.

Operator

Lumas Softech
705, Alif Apartment
Sarkhej-Makraba Road, Sarkhej
Ahmedabad 382210, Gujarat
India
support@lumaspdf.com · Contact page

Versions

Acceptance is recorded against a version number, so every version stays readable at its own address for as long as the record does.