Privacy policy
Last updated 2026-10-23.
Angelo Lamonaca (sole proprietorship), trading as Neuramare, in Switzerland (UID CHE-491.417.985), runs Kennmarq.com and is responsible for the personal data this policy describes. It follows the Swiss Federal Act on Data Protection (FADP) and, where it applies, the EU General Data Protection Regulation (GDPR). Write to privacy@kennmarq.com about anything in it.
Where you use Kennmarq.com to process files for your own users, you decide what those files hold and we process them on your behalf, under the data processing agreement. This policy covers the rest: your account, your use of the service, and visits to this site.
Your files
- A file sent to the API is read in memory for that one call and kept nowhere: not on disk, not in logs. A file uploaded first (for files over 4 MB) waits in our storage in Zurich until the call uses it, and is deleted then, or an hour after the upload at the latest.
- In local mode the file never reaches us: only its manifest does, to be signed. The free checker page reads files in your browser, without sending them.
- The safety check estimates whether a picture shows nudity, an apparent minor or a realistic face, to block or flag it. It never identifies anyone, never stores or returns an age, and keeps nothing of the picture, not even its hash. Its answer goes into the API response, never into the file.
- Marks carry what you declare (how the file was made, the model, your app's name, a title), never who made the file. Don't put personal data in those fields: marks travel with the file, and anyone can read them.
What we keep
| What | Data | How long |
|---|---|---|
| Your account | Name, email address, a hash of your password, the organisations you belong to and your role in each | Until you delete the account; backups for 7 more days |
| Sign-in and audit | Sessions; for each change in an organisation (keys, members, plans), who made it, when and from which IP address | Sessions until they expire; the audit log while the organisation exists |
| API keys | A hash of each key, its prefix and last four characters, scopes, allowlist | Until the key is deleted with its organisation |
| Marks | Each mark's ID, the marked file's SHA-256, sizes and format, the watermark ID, the key and project, the time. Never the file, its name, its pixels or a prompt | While the organisation exists |
| Durable credentials | For each watermarked file, its C2PA manifest store: what you declared in it (source, model, app name, title), the signature and the time-stamp | As long as the service runs: they let a stripped copy be traced back |
| Transparency log | Hashes of each signature and time-stamp, and pseudonymous heads of audit logs. No personal data | Permanently: an append-only public log |
| Billing | Your organisation's Stripe customer ID, plan and subscription state. Card details go to Stripe, never to us | While the organisation exists; invoices as the law requires (10 years in Switzerland) |
| Email we send | The address and the kind of email (sign-in link, invitation) | In the email provider's logs for up to 30 days |
This site sets one cookie, to keep you signed in. It uses no analytics, no advertising and no tracking. Our servers' logs keep request IDs, key IDs and timings for 30 days, not file contents.
Why
- To provide the service you signed up for, and bill it (performing our contract).
- To keep it secure and working: abuse and fraud prevention, the audit log, logs (our legitimate interest).
- To keep accounting records and answer lawful requests (legal obligations).
- To send emails the service needs, and notices of changes to it. No marketing email without your consent.
Where, and who else
Customer data is kept in AWS's Zurich region; database backups are copied to Frankfurt. Requests reach our API in Frankfurt, where they pass through memory on their way to Zurich. Only three companies process personal data for us, each listed with what and where on the sub-processors page: Amazon Web Services, which hosts everything; Stripe, which takes payments; and Proton, in Switzerland, which holds the email you send to our addresses. Stripe may process payment data in the United States, under the Standard Contractual Clauses and the EU–US and Swiss–US Data Privacy Frameworks. We share personal data with authorities only when the law requires it.
Your rights
You may ask to see the personal data we hold about you, to have it corrected or deleted, to receive it in a portable form, and to object to processing based on our legitimate interest. Most of it you can see and change in the dashboard; for the rest, write to privacy@kennmarq.com from your account's address. We answer within 30 days. You may also complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) or, in the EU, to your data protection authority.
Security
Data is encrypted in transit (TLS 1.2 or later) and at rest; signing keys never leave AWS KMS; secrets are kept in AWS Systems Manager, encrypted. The trust center describes these measures in detail.
Changes
We announce material changes to this policy on this page and by email to organisation owners, 30 days ahead.