Data processing agreement
About this agreement
This data processing agreement sets out how Qwrki handles your organisation's records when you use Qwrki. Read it beside the terms (/terms) and the privacy policy (/privacy).
Your organisation and Qwrki
Your organisation decides what records to keep in Qwrki and what to do with them. Qwrki handles those records only to run the service for your organisation, as the product is built to handle them.
How records are protected
Each customer's tables are separated by the database itself: every tenant-owned table enforces row-level security keyed on a per-transaction setting, and the runtime database role cannot bypass it. Files sit in a private bucket whose tenant segment comes from the session, never from caller input.
Every app response carries Strict-Transport-Security and traffic is encrypted in transit. Integration credentials, connection secrets, TOTP secrets, export documents, archived message bodies, provider mirror fields and AI Employee boundary material are encrypted with AES-256-GCM bound to their row and tenant; ordinary business data is protected by row-level security and the hosting provider's disk encryption. Passwords are hashed with scrypt. The audit trail is append-only: tenant admins can view 200 rows on screen and export up to 5,000 rows as CSV. No external audit, penetration test or certification exists.
Sub-processors
Some work is done by other providers, for example hosting, mail delivery and billing. The register behind the public list is the source of truth: if it and this paragraph differ, the register wins.
The current list of sub-processors is at /subprocessors.
Rights over personal data
Tenant admins can run a privacy request for one person in one company. It produces an export document sealed under the tenant key and downloadable once approved, and it can remove that person's records: ERP leads, Website Chat conversations and messages, case message archives, the provider mirror, AI tool outputs naming them, the customer record, onboarding links and their calls. A record removed this way keeps only its id, its dates and a label saying it was removed. Files the person appears in are not deleted, and meeting notes and transcripts are not reached.
An owner can download one ZIP file with a CSV for each kind of record the organisation holds, once a day; single lists and single people can also be exported.
How long records are kept
Provider report figures are deleted automatically 400 days after the period they cover. A paused tenant's voicemails are kept 60 days with notices before deletion, and AI tool outputs are kept 90 days. Automatic deletion of the rest of a suspended tenant's data is not built. Qwrki takes an encrypted backup of the database every night and keeps the copies with its file storage provider.
If records are exposed
If Qwrki becomes aware that your organisation's records were exposed, Qwrki contains an active breach (someone still has access) within 4 hours of becoming aware of it, and tells your organisation without undue delay what is known, which records and people are affected and what Qwrki has done. Any other security report receives a response within one week. Qwrki does not notify regulators or the people affected on your organisation's behalf unless you ask it to.
Contact
Questions about this agreement go to liam@qwrki.com.