--- title: Data processing agreement description: The GDPR Article 28 terms under which Kaviris processes your app's end-user data on your behalf. --- # Data processing agreement > **Draft for legal review (2026-10-12).** Not yet in force; not legal > advice. Items marked `[confirm]` are checked before publication. > `[build]` marks something the system does not > do yet; it is built or the text changes before publication. This agreement is part of the [Open beta terms](beta-terms.md) for every customer whose app processes personal data of other people. It applies automatically; a signed copy is available on request for business customers. ## 1. Parties and roles - **Controller**: you, the customer, for the personal data your app collects and stores (your app's users, visitors, customers). - **Processor**: **U Secure IT AB** (Kaviris), org. no. `[registration number]`, `[address]`, Sweden. For your own account data we are the controller; see the [Privacy notice](privacy.md). This agreement covers only your app's data. ## 2. What we process (Art. 28(3)) | | | |---|---| | **Subject matter** | hosting your app: building, running, backing up, restore-testing, logging and exporting it | | **Duration** | while your app exists on Kaviris, plus the retention periods in section 9 | | **Nature** | storage, execution, transmission, backup, automated restore testing, log retention, export; no analysis of content. Our edge logs every request to your app (the visitor's IP address, user agent, host, path without query string, time, status) for 14 days, and passes the visitor's IP address to your app (`X-Forwarded-For`); what your app writes to its logs is kept 14 days `[lawyer: README question 17]` | | **Purpose** | to run your app as you deployed it, and nothing else | | **Types of data** | whatever your app stores in its database, writes to its logs, or receives from and sends to its users; typically names, email addresses, identifiers, IP addresses in logs, and whatever your app's purpose entails. You decide; we do not inspect it | | **Data subjects** | your app's users and visitors | | **Special categories** | not expected. If your app processes special-category data (Art. 9) or data on a large scale, tell us at `legal@kaviris.com` before deploying; the beta is not suited to it (no uptime promise, no SLA) | ## 3. Your instructions (Art. 28(3)(a)) We process your app's data only on your documented instructions. Your instructions are: this agreement, the terms, and what you do through the portal, API, MCP and CLI (deploying, approving a contract, naming outside hosts, restoring, exporting, deleting). We will tell you if an instruction would in our view break the law. We may process otherwise only when EU or Swedish law requires it, and then we tell you first unless that law forbids it. Your responsibilities: a lawful basis for your app's processing, your app's own privacy notice, answering your users' rights requests (we help, section 7), keeping your app's secrets safe, and naming in the contract only outside services you are entitled to send data to. ## 4. Confidentiality (Art. 28(3)(b)) The people and AI agents who operate Kaviris are bound to confidentiality. Nobody at Kaviris reads your database. Support sees your app only through read-only tools, by default its state and refusal codes, and more (contract, deploys, build logs, recent runtime logs with emails, tokens and IP addresses masked) only under a **case grant** you give for at most 72 hours and can revoke; every read is logged and listed to you ([Support](../support.md)). ## 5. Security (Art. 28(3)(c), Art. 32) What is built today, in plain words; our [Security overview](../security.md) has more. | Measure | What it means | |---|---| | **A micro-VM per app** | each app runs in its own lightweight virtual machine (Kata Containers) with its own kernel, not in a shared container; its database runs in the same isolated namespace | | **Default-deny egress** | an app can reach only the outside hosts its approved contract names; everything else is blocked at the network layer. Data cannot be sent out to an undeclared destination, by your app or by an attacker inside it | | **The gate on every deploy** | build in an isolated machine, scan for secrets and vulnerabilities, a probe run in a sealed machine to see what the app connects to, comparison with the contract, then signing. The cluster runs only images we signed | | **Encryption in transit** | TLS at the edge; traffic between platform components is encrypted and authenticated inside the cluster (mutual TLS). We do not intercept your app's encrypted outbound traffic | | **Encryption at rest** | **Not in place today.** On the development cluster, disks, databases, object storage (including backups), the image registry and logs are not encrypted at rest; the Kubernetes secret store is (since 2026-10-12). For the beta cluster we plan full-disk encryption of every server (Talos system-disk encryption) and encryption of the secret store; off-site backup copies are encrypted before they leave the cluster, with a key the off-site provider never sees. The off-site provider (Elastx) also encrypts its storage at rest | | **Secrets write-only** | secret values you give your app can be set but never read back by anyone, including us | | **Backups with tested restores** | the database is archived continuously and backed up nightly to separate object storage, with an off-site copy, encrypted before it leaves the cluster and kept at most 8 days longer than the cluster's backups `[build: the off-site copy is not yet switched on]`; every night each backup is restored into a sealed place to prove it works and the copy is discarded `[build: restore tests are not yet run on every database]` | | **Least privilege and audit** | our own operators and agents act through narrow, logged interfaces; privileged actions need a person's passkey; every action on your organisation is in an audit log you can see | | **Patching** | the platform rebuilds your app from your last approved source when its base system gets a security fix, and advises you on your own dependencies without changing them | | **Isolation of untrusted input** | agents that read customer text hold no credentials; text from apps is treated as data, never as instructions | | **Security reviews** | each larger change is reviewed as an adversary would before the next builds on it; an external penetration test precedes any paid plan | We will not lower the level of protection during the beta. Security measures may be improved or replaced by equivalent ones. ## 6. Sub-processors (Art. 28(2), (4)) You authorise the sub-processors listed in the [Privacy notice, section 3](privacy.md#3-who-processes-it-for-us-sub-processors) (hosting, off-site backup, email, payments, helpdesk, EU-hosted AI models). For your app's data the relevant ones are the hosting provider, the off-site backup provider, and, only if you open a support case and grant access, the helpdesk and the EU-hosted AI models that triage it. We tell you by email and in the portal at least **30 days** before adding or replacing a sub-processor. If you object on reasonable data-protection grounds and we cannot resolve it, you may delete your app or account before the change takes effect; export is free. Each sub-processor is bound by a contract with equivalent data-protection terms, and we stay responsible for them. Models outside the EU (Anthropic) never receive your app's data. ## 7. Helping you (Art. 28(3)(e), (f)) - **Rights requests from your users**: your app's data is yours to search and change; we provide export (full database dump and source), restore to a point in time, and deletion. If you need more, write to `legal@kaviris.com`; we help at cost for unusual requests. - **Security, DPIAs and consultations**: this agreement, the Security overview and the published security reviews are the documentation; we answer reasonable questions. - **Breach notification**: if we become aware of a personal data breach affecting your app's data, we tell the owners of your organisation **without undue delay and at the latest within 48 hours** `[lawyer: period]` by email and in the portal, with what we know: what happened, which data and how many people are likely affected, what we did, and a contact. We update as we learn more. Notifying your supervisory authority and your users is your duty as controller; we help with the facts. ## 8. Audits (Art. 28(3)(h)) We make available: this agreement, the Security overview, the sub-processor list, our security review records and, before paid plans, a summary of the external penetration test and our self-assessment. You may audit our compliance once a year, or after a breach, with 30 days' written notice, during business hours, by yourself or an independent auditor bound to confidentiality, at your cost, without access to other customers' data or to secrets; we may answer by a written response or a recognised audit report where that reasonably covers the question. ## 9. Deletion and return at the end (Art. 28(3)(g)) - **Export** is free at any time while your app exists and until it is deleted: a full `pg_dump` of each database, every source archive, the contract and secret names ([Backups and restore](../concepts/backups-and-restore.md)). - When you **delete an app** it is kept, stopped, for **30 days** (export still works), then **purged**: namespace, database, volumes, backups, **the off-site backup copy**, source archives, images and the platform's rows about it. The purge lists everything owned by the app's id, deletes it, lists again and must find nothing. Logs expire within 14 days and metrics within 30 days on their own. - An app stopped under the free-plan rules is purged **90 days after the stop** after two warnings ([terms, section 3](beta-terms.md#3-the-free-plan-rules-that-stop-and-delete-apps)); a deleted organisation or account purges its apps after **30 days**. - Nothing of your app's data survives a purge except what is under a legal hold (a court or authority order) while it lasts, and the deletion record (ids, date, rule, no personal data). ## 10. Transfers (Chapter V) Your app's data is stored and processed in the EU. Off-site backups stay in the EU. Support tooling is in Germany, and routine AI triage in Sweden with a Swiss second source (EU adequacy decision). No other transfer takes place for your app's data. If one becomes necessary we tell you 30 days ahead with the safeguard used (adequacy decision or standard contractual clauses). ## 11. Liability and term Liability follows the [Open beta terms](beta-terms.md), section 12. Each party is liable to data subjects as Art. 82 GDPR provides. This agreement lasts as long as we process your app's data and ends with the purge. Conflicts: this agreement wins over the terms for data-protection matters; mandatory law wins over both. ## Annex: contact and documents - Data protection contact: `privacy@kaviris.com` `[confirm]` - Security reports: `security@kaviris.com` - Legal: `legal@kaviris.com` - Documents: [Privacy notice](privacy.md) · [Security overview](../security.md) · [Support](../support.md) · [Open beta terms](beta-terms.md)