Privacy notice
Draft for legal review (2026-10-12). Not yet in force; not legal advice. Items marked
[confirm]are checked by us or a lawyer before publication.[build]marks something the system does not do yet; it is built or the text changes before publication.
1. Who is responsible
The controller for your personal data is U Secure IT AB, org. no.
[registration number], [address], Sweden, which runs Kaviris. Contact:
privacy@kaviris.com [confirm mailbox]. Data protection contact
(no DPO is appointed [lawyer: Art. 37 check]): [name or role].
This notice covers you as a Kaviris customer or visitor to our sites. For the people who use your app, you are the controller and we process their data on your behalf under the data processing agreement. Your app needs its own privacy notice.
2. What we collect and why
| What | Where it comes from | Why | Legal basis (GDPR Art. 6) | Kept |
|---|---|---|---|---|
| Account: email address (confirmed by a code), display name, country, whether you act as a private person or a business, company name and VAT id for a business, language | you | to create and run your account, invoices later | contract (6(1)(b)) | until your account is deleted, then 30 days (lock period), then erased except section 6 |
| Sign-in credentials: passkeys (we store only the public key and a name for it; the private key never leaves your device), or the identifier Google or GitHub gives us when you sign in through them | you, Google, GitHub | sign-in | contract | as above |
| Connection and sign-in metadata: for every request to our sites and to the apps we host, the IP address, the browser/client name your device sends (user agent), host, path (no query string), time and result; for failed sign-ins, sign-ups and token refreshes, the IP address and account id; for a signed-in session, the IP address and the browser and system it was started from | your device | security, abuse prevention, rate limits, proving who did what | legitimate interest (6(1)(f)): security of the service and your account | request and failed sign-in logs 14 days; session details while the session lasts (browser sessions at most 10 hours; a connected agent's session until it is unused for 30 days, and at most 90 days); short-lived rate-limit counters at most 1 day, in memory. Our own audit log holds no IP address or user agent |
| Agent keys and grants: which coding agent you connected, its permissions, when it was last used | you | to let your agent act for you | contract | until revoked, unused for 30 days or 90 days old (then you connect the agent again), or your account is deleted |
| Audit log: who did what, when, through which agent (deploys, contract approvals, secret names set, members, keys, support reads, refusals) | your actions | your own audit trail; security; accountability | contract; legitimate interest | 24 months, then deleted (billing entries, once paid plans exist: the person in them replaced by a pseudonym at 24 months, the entry kept with the invoices); after account deletion only security-relevant entries under a pseudonym (section 6) |
API and agent usage [confirm]: for every call to our API, including calls your coding agent makes through MCP, the time, the route or tool, the result, how long it took, your account and organisation id and which client made it (for example the portal or Claude Code); never the content of the call. For each deploy, the result and the refusal codes |
the platform | to run the service and see which features work and where they fail | contract (running the service) | 14 days |
Usage counts [confirm]: how many calls, deploys, refusals, sign-ups and page requests there were, per day, route, tool, result and site; no account, address or other personal data in them |
the platform | to see how Kaviris is used | legitimate interest (6(1)(f)): improving the service | 30 days; 24 months once they are kept as daily totals [build] |
| Your apps: name, source uploads, build logs, the contract, deploys, releases, the database your app uses, backups, images | you | to host the app | contract | source, images and backups until the app is deleted (backups 7 days rolling in the cluster; the off-site copy, encrypted before it leaves the cluster, keeps what the cluster deleted at most 8 days longer); build logs 14 days |
| Runtime logs and metrics of your apps | your app | so you and we can see what it does | contract | logs 14 days, metrics 30 days |
| Usage metering: awake time, data sent, storage, builds per org per day/month | the platform | free-plan allowances; later billing | contract | daily figures 24 months; the raw measurements 30 days; invoices 7 years once paid plans exist |
| Notifications and mail delivery: what we sent you, when, and whether it bounced | the platform, our mail provider | lifecycle warnings the terms promise; proving we warned you | contract; legal obligation (fair terms) | 24 months |
| Support: your messages, case grants, what support read under them | you, the helpdesk | to help you | contract | tickets 24 months after close; abuse and legal cases 7 years [lawyer] |
| Beta admission and sanctions screening: your place on the beta waitlist, when and how you were admitted (a batch, an invite code, an invitation to an organisation), and the result of checking your name and your email address (the part before the @ and the domain) against the EU's consolidated list of persons and entities under financial sanctions (the official list, which we copy from the EU each night): clear, or the listed names it resembled with their EU reference numbers. Every name you give while you wait is checked, so a name you changed is kept beside the new one until you are admitted or not. Your names are kept for this only while you wait (at most 30 days in review), and with the result only when it resembled a listed name, until a person at Kaviris has checked it. Once you are admitted, your email address is checked again each night against the latest list; a resemblance is looked at by a person and never closes your account by itself. We do not ask your country for this today. A close resemblance never refuses you by itself: a person at Kaviris looks at it; a match (the same name, also spelled or transliterated otherwise, or with a name added) holds your admission until they have | you, the EU list | admitting people to the beta in batches; not making our service available to listed persons and entities | legal obligation (6(1)(c)): the EU sanctions regulations; legitimate interest (6(1)(f)): learning abuse rates before opening further [lawyer] |
the names until admission or denial (at most 30 days in review); the result while your account exists, erased with it; the admission and screening entries in the security audit 24 months (section 6) |
Referrals [confirm]: if you signed up through a customer's referral link, which organisation's link it was and when, and whether the referral counts yet (you were admitted and put an app online). That customer sees only how many people signed up through their link and how many count, never who |
the link you followed | to count referrals and, later, to thank the customer who referred you | legitimate interest (6(1)(f)): knowing where customers come from and rewarding referrals | while your account exists, erased with it; when the referring organisation is deleted, once it can no longer come back |
| Trust and safety: sign-up screening result, abuse reports about your apps, takedown statements and appeals, legal holds | the platform, third parties, authorities | DSA duties; keeping the platform safe | legal obligation (6(1)(c)); legitimate interest | takedowns and appeals 2 years after the decision; holds while they last |
| Notices about illegal content (the notice form): from the person who sends one, their name and email (optional for child sexual abuse material), the address reported, their explanation and the time; about you as an app's owner, that a notice concerned your app (its reference and category, never the notifier's identity unless the law requires it) | the notifier | DSA Art. 16 and 17: deciding on the notice, telling the notifier and the owner | legal obligation (6(1)(c)) | 2 years after our decision; while a legal hold lasts; an undecided notice until decided. The address is used only to confirm receipt and tell the decision |
| Payment (when paid plans exist; a card is verified without a charge during the beta): a Stripe customer id, the card's brand, last four digits, expiry, country and Stripe's fraud score and card fingerprint. We never see or store the card number | you, Stripe | card validity for the free plan; billing; fraud prevention; one free organisation per card | contract; legitimate interest: fraud | until your account is deleted; invoices 7 years; a banned account's card fingerprint and a hash of its email 2 years [lawyer] |
| GitHub (only if you connect it): the installation id, repository names, pushes that start builds | GitHub, you | deploy on push | contract | until disconnected or the app is deleted |
We do not collect: the contents of your database (an automated restore
test reads it inside a sealed machine and discards the copy; no person or
AI reads it), your secret values (write-only; nothing can show them), or
browsing behaviour. The portal sets a session cookie and nothing else; we
run no advertising or tracking. Our websites use no analytics scripts and no
cookies other than the portal's session cookie; we count page requests from
our own server log, which holds your IP address for 14 days for security,
and we do not count people. [confirm] When you arrive at our website or
the portal's start or sign-in page from a link on another site, we count
the visit under that site's name only (for example news.ycombinator.com),
never the address of the page you came from. [confirm]
A refused action and a privileged action (granting access, support reads, key changes) are kept in the security audit for 24 months with your account id, so that abuse can be investigated after the fact.
3. Who processes it for us (sub-processors)
We choose providers in the EU first. The current list; we tell you 30 days before adding one (see the DPA for how to object).
| Provider | Where | What they do | What they see |
|---|---|---|---|
| Hetzner Online GmbH | Germany, servers in Finland (planned beta cluster) [confirm site] |
runs the servers the platform and your apps run on; DNS; object storage | everything stored on the platform; encrypted in transit; encryption of the servers' disks is planned, not yet configured [build, README check 2]; Hetzner has no application-level access |
| Elastx AB | Sweden | off-site copies of backups (may change before the beta) | backup files |
| Scaleway SAS | France | alternative off-site backups; candidate transactional email [confirm] |
backup files; email addresses and the notice text |
Transactional email provider [to be chosen; EU] |
EU | sends our notices and sign-in codes; reports bounces | your email address, the message |
| Stripe Payments Europe Ltd (later; not yet connected) | Ireland; Stripe Inc., USA [lawyer: Stripe's terms make it a processor for payments and an independent controller for its own fraud prevention and legal duties; confirm, and the transfer basis] |
card verification, later billing and invoices | card details (never us), name, address, email, amounts |
| Zammad GmbH | Germany | the support helpdesk | your support messages and address |
| Berget AI AB | Sweden | AI models for routine operations: ticket triage and first drafts, log and alert summaries, sign-up screening | support text, redacted logs, metadata; see section 4 |
| Infomaniak Network SA | Switzerland (EU adequacy decision) | second-source AI models, same uses, when Berget is unavailable; company mailboxes [confirm] |
as Berget |
| Anthropic PBC | USA | AI models for our engineering, planning and decisions | our own code, plans and documents; summaries of customer matters without personal data. Not customer data, logs or tickets [lawyer: whether this is processing at all; transfer basis if it is] |
| Let's Encrypt (ISRG) | USA | TLS certificates for app hostnames | the hostname; note that every hostname is published in public certificate transparency logs, as for any HTTPS site |
Not sub-processors: GitHub and Google act as independent controllers when you sign in through them or connect a repository, under their own terms. GitLab holds backups of our own source code, not customer data. Our sign-in service (Keycloak), chat, alerting and the operator console run on our own servers.
4. We use AI systems to run parts of the service
Honestly: Kaviris is operated largely by AI agents under one human owner. They triage support, summarise alerts and logs, screen sign-ups for abuse, draft replies, and prepare decisions. What that means for you:
- Every reply drafted by AI says so (EU AI Act Art. 50). Ask for a
person and one reviews your case
[build: no support channel exists yet (no support mailbox, helpdesk or portal form); required before publication, README check 5]. - Agents that may see customer data (support, abuse, operations on your apps) run only on EU-hosted models (Berget AI in Sweden, Infomaniak in Switzerland). Models outside Europe (Anthropic) work on our own code and plans and get at most a summary without personal data.
- Agents that read text you send us hold no credentials and cannot act on your account; a separate agent sees only structured fields.
- No agent can delete customer data, suspend a customer, pay, sign, or send you a non-template message without a human's approval. Suspensions and takedowns are approved by a person, and a person reviews every appeal.
- Every tool call an agent makes is logged (kept 13 months).
- No decision with legal effect on you is made by AI alone (GDPR Art. 22). Sign-up screening may put you in a queue or a review; a person decides a denial.
5. Transfers outside the EU/EEA
The platform, your apps, backups and support run in the EU (and Switzerland,
which the EU recognises as adequate). Transfers to the USA happen only for:
Stripe (payments, under the EU-US Data Privacy Framework or standard
contractual clauses [confirm]), Let's Encrypt (hostnames only), and
Anthropic (no personal data by design, section 3). If you connect GitHub or
sign in with Google, those transfers are under your agreement with them.
6. How long we keep things, and what survives deletion
Section 2 gives the period per kind of data. When you delete your account (or it is deleted after 365 days unused), after the 30-day lock everything is erased except:
| Kept | How long | Why |
|---|---|---|
| Invoices, receipts, payment records, the billing name and address on them, the terms version you accepted (paid plans only) | to the end of the 7th year after the financial year | Swedish Bookkeeping Act (bokföringslagen 7 kap. 2 §) |
| VAT records for consumer sales to other EU countries, if any | 10 years | EU VAT One-Stop-Shop rules |
| Takedown statements of reasons, appeals and decisions about your apps, and the notices they followed | 2 years after the decision | EU Digital Services Act (Art. 17, 20, 23, 24) [lawyer] |
| Security audit entries (refused and privileged actions) | 24 months from the event, under a pseudonym | legitimate interest: investigating abuse |
| That your account was deleted, when and under which rule, with no personal data | indefinitely | proving we deleted it (GDPR Art. 5(2)) |
| For a banned account: the card fingerprint (Stripe's token, not the number) and a salted hash of the email address | 2 years after the ban | legitimate interest: stopping ban evasion [lawyer] |
| The version and time of the terms a free organisation accepted | 3 years after the account is gone | defending claims (preskriptionslagen) [lawyer] |
| Anything under a legal hold | while the order or case lasts | the order |
Backups of a deleted app, including the off-site copy, are deleted with it. Logs expire on their own after 14 days, metrics after 30 days.
7. Your rights
Under the GDPR you can ask us to access, correct, erase or restrict your data, object to processing based on legitimate interest, and get your data in a portable form. Self-service:
- Download my data (portal, Account): a JSON file (
me.json) with your account, organisations, roles, keys (never their secrets) and audit trail. Each app's source, contract and database are exported from the app's page, free, at any time. - Delete my account (portal, Account, with your passkey): locked at once, erased after 30 days unless you press Reactivate (your account).
- Change your address, name and details in the portal.
For anything else write to privacy@kaviris.com. We answer within one
month. We may ask you to prove it is your account (a signed-in request from
the portal is enough).
You can complain to the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY), Box 8114, 104 20 Stockholm, imy.se, or to the supervisory authority where you live.
8. Children
Kaviris is not for people under 18 [lawyer: see terms section 2]. We do
not knowingly hold data about children; tell us if we do.
9. Changes
We will change this notice as the service grows (paid plans, the mail provider, the beta cluster). The date at the top is the version; material changes are announced by email and in the portal 30 days ahead.
Related: Open beta terms · Data processing agreement · Support, and how we use AI · Security overview