This document has not yet been reviewed by a lawyer.
1. In short
- Clavem is run by an independent operator in Switzerland.
- We process sellers’ account data, and, on sellers’ behalf, their customers’ email, name, license keys, device names and IP addresses at activation.
- We do not process card data. Stripe does.
- We use three sub-processors: Cloudflare, Neon and Stripe.
- We use no advertising or analytics trackers. Fonts are served from our own site.
- You can export your data as CSV and delete your account.
2. Who is responsible
For sellers, the people who create a Clavem account, we decide why and how the data is used, so we are responsible for it. For buyers, the customers of a seller, the seller decides why the data is used and we process it on the seller’s behalf. If you bought software from a seller who uses Clavem and want to see or remove your data, ask that seller first. We help them do it.
3. What we process
| Whose | What | Why |
|---|---|---|
| Sellers | Email address and a hash of the password, store name, support email, Stripe connection (restricted key and webhook secret, stored encrypted), plan, subscription status, products, releases, uploaded files, API key hashes, sign-in sessions with their IP address and browser, activity logs. | To provide the account, the dashboard and the API, and to bill you. |
| Buyers | Email address and name, license keys, order details from Stripe (identifiers, amount and currency, not card data), device names, an optional device fingerprint chosen by the seller’s app, and the IP address and browser string at the time of activation. Counts of downloads, without who downloaded. | To issue and validate licenses, deliver downloads and let buyers manage their devices. |
| Anyone who writes to us | The email address, the message and the IP address. | To answer, and to block abuse. |
| Everyone | Technical request data such as IP address and user agent, processed by the hosting provider to deliver the pages and to apply rate limits. | To run and protect the service. |
Emails we send, such as a buyer’s license delivery or a password reset, are logged with the recipient, subject and delivery status, not the body.
4. Who else handles it
| Sub-processor | For what | Where |
|---|---|---|
| Cloudflare | Hosting of the site and API, file storage for release downloads, rate limiting, and email delivery. | A global network. Requests are handled in many countries. |
| Neon | The database that holds accounts, licenses, customers, orders and logs. | Frankfurt, Germany |
| Stripe | Payment of Clavem plans, and, through the restricted key you give us, reading purchases in your own Stripe account. | Stripe’s own infrastructure |
We do not sell personal data and we do not share it for advertising.
5. Card data
Clavem does not process card data. Card numbers are entered into Stripe’s pages and never reach us. Through your restricted key, Clavem can read the products, checkout sessions, subscriptions, customers, invoices and charges it needs to issue licenses. It cannot move money.
6. Retention, export and deletion
- We keep your data while your account exists. Sessions expire after 30 days.
- Removing a device from a license ends the activation, and we keep the activation record, including its IP address, as history until the account is deleted.
- Export. Every license, buyer and status can be exported as CSV in the dashboard at any time.
- Deletion. You can delete your account in the dashboard settings, after cancelling any paid subscription. This deletes your licenses, customers, orders, devices, products, releases and uploaded files.
- Copies in the database provider’s backups disappear when those backups expire on the provider’s own schedule.
- Messages sent through the contact form are kept as long as we need to answer them, and deleted on request.
7. Security
Passwords are stored as salted scrypt hashes. Stripe keys and each product’s signing key are encrypted at rest, with an encryption key kept outside the database. Session tokens and API keys are stored as hashes. Traffic uses HTTPS. No system is perfectly secure, and we do not claim any security certification.
8. Cookies
When you sign in, we set one cookie, signet_session, that keeps you signed in for up to 30 days. It is needed for the dashboard and is not used for tracking. Visitors and buyers who do not sign in receive no cookies.
9. Your rights
Swiss data protection law and, where it applies, the GDPR give you rights over your personal data: to access it, to have it corrected or deleted, to receive a copy, and to object to some uses. Sellers can do most of this themselves in the dashboard. Buyers should ask the seller, or write to us and we will pass the request on. You can also complain to your data protection authority.
10. Changes and contact
We will update this page when the service or its sub-processors change, and tell sellers about material changes before they apply. Questions or requests: contact form. See also the terms.