LicenseKit

Privacy Policy

Last updated 2026-11-16

Who we are

[LEGAL ENTITY NAME], [ADDRESS]. Data protection questions go to [PRIVACY EMAIL].

What we store about you

Your email address, workspace name, and Stripe customer id. That is the whole list. We do not run third-party analytics or advertising trackers on the dashboard.

What we store about your customers

Whatever you send us: usually an email address, sometimes a name, and the metadata you attach to a license. You are the controller of that data and we are the processor. Do not send us anything you would not want in a database — there is no reason for a licensing system to hold an address or a payment detail.

Machine fingerprints and IP addresses

Fingerprints are stored exactly as your application sends them, so hash whatever you derive them from. IP addresses are never stored in raw form: we keep a salted HMAC truncated to 32 characters, which is enough to spot abuse from one source and not enough to reverse. Rotating the salt anonymises the entire history.

Retention

Activity events are pruned on your plan's retention schedule — 7 days on Free up to 365 on Business. Licenses and activations are kept until you delete them, because they are the record of a real purchase. Deleting your account removes everything within 30 days.

Sub-processors

The database runs on our own infrastructure rather than a managed provider, so your data is not handed to a third party to store. Authentication is ours too. The services that can touch your data are: our hosting provider (the server the application runs on), Stripe (payments — card details go to Stripe and never reach us), Resend (transactional email, which sees the recipient address and the message), and GitHub (only if you choose to sign in with it, and only to confirm your identity and verified email address).

Encryption

Everything is served over TLS. Product signing keys and webhook secrets are encrypted at rest with AES-256-GCM under a key that is not stored in the database. API keys are stored only as SHA-256 hashes, which is why we cannot show you a key a second time.

Your rights

Access, correction, export and deletion, on request or self-serve from the dashboard. We do not sell data and there is no legitimate interest we are stretching to justify — the only processing we do is what running the service requires.

Cookies

One session cookie, holding an opaque random token that identifies your session on our own servers, so that being signed in works. No advertising or analytics cookies, which is why there is no consent banner on this site.