NurvexConnect Data Processing Agreement (DPA)
Last updated: [date of publishing]
This agreement is part of the Terms of Service between NurvexThink (Private) Limited ("we", the "processor") and the company that owns a NurvexConnect workspace (the "customer", the "controller"). It applies when the customer accepts the terms.
1. Roles
| Data | Customer's role | Our role |
|---|---|---|
| Workspace content: messages, files, voice notes, calls, statuses, calendar events, alerts, member profiles, roles and departments, activity log, AI requests and replies | Controller | Processor |
| Account data: sign-in details, sessions, devices, billing records, support messages, security and technical logs | — | Controller (see the Privacy Policy) |
2. What we process, and why
- Subject matter: hosting and running NurvexConnect for the customer's workspace.
- Duration: for as long as the workspace exists, plus the deletion periods in section 9.
- Nature and purpose: store, encrypt, send, show and search content; deliver notifications and calls; run AI features the customer turns on; support and security.
- People concerned: the customer's staff, contractors, guests and anyone they communicate with in the workspace.
- Kinds of data: names, work contact details, profile details, job details, message and file content, call records, device and usage records. The customer decides whether special-category data (such as health information) is shared; NurvexConnect is not designed for it.
3. Our promises
We will:
- Process workspace content only on the customer's documented instructions. The terms, the workspace settings and the customer's admin actions are those instructions. If we think an instruction breaks the law, we will say so.
- Make sure everyone at NurvexThink who can access the data is bound to keep it confidential.
- Keep the security measures in section 5.
- Use sub-processors only as set out in section 6.
- Help the customer answer requests from people using their rights (access, correction, deletion, export), as far as the service allows.
- Help the customer with security, breach notices and data protection impact assessments, as far as is reasonable.
- Delete or return the data when the workspace ends, as set out in section 9.
- Give the customer the information needed to show we keep this agreement, and allow reasonable audits as set out in section 8.
We do not sell workspace content. We do not use it to train AI models. We do not read it as a matter of policy; access happens only as set out in section 5.
4. The customer's promises
The customer:
- has a lawful basis for putting the data into NurvexConnect and has told its members how the workspace is used
- is responsible for who it invites, the roles it gives and the settings it chooses (including turning AI on)
- keeps its admin accounts safe
5. Security measures
- HTTPS and secure connections for all traffic.
- Workspace content encrypted on our server with AES-256-GCM. [Per-workspace key: in place from Phase 10 — confirm before publishing.] The master key is kept apart from the database.
- Secret Chats are end-to-end encrypted on the phones; we cannot read them.
- Passwords hashed with Argon2id; limits on wrong passwords; short sign-in tokens.
- Separation of each workspace's data in the database and in the code, tested automatically. [In place from Phase 10 — confirm.]
- Our platform console cannot read messages, files or keys. Support may enter a workspace only when the customer grants it, for a limited time, and every access is logged.
- Push notifications carry ids only, not message text.
- Daily backups, kept 14 days, with restore tested.
- Access to the server limited to named staff, with strong authentication. [Staff access controls: confirm.]
Honest note: for content that is not in Secret Chats, our server holds the keys so it can deliver and show the content. Staff not reading it is a policy, enforced by access controls and logs, not a technical impossibility.
6. Sub-processors
- The customer agrees that we use the sub-processors in our sub-processor list.
- We bind each one by contract to protection at least as strong as this agreement.
- We will give at least [notice period: confirm — suggested 30 days] notice of a new sub-processor by email to workspace owners and on the list page. The customer may object for a reasonable data protection reason. If we cannot solve it, the customer may end the paid plan and get a refund of the unused prepaid part.
- AI providers receive data only when the customer turns AI on.
7. Breaches
If we become aware of a breach that affects the customer's workspace content, we will tell the workspace owner without undue delay, and within [hours: confirm — suggested 72 hours], with what we know, what we are doing, and what the customer should do. We will update them as we learn more.
8. Audits
On written request, once a year, we will answer a reasonable security questionnaire and share a summary of our measures. On-site audits, if needed by law, are at the customer's cost, with [notice: confirm — suggested 30 days] notice and under confidentiality.
9. Deleting or returning data
- A workspace owner can export the workspace (JSON plus files) on plans that include export, or ask us for an export.
- When a workspace is deleted, it can be restored for 30 days. After that, its content is deleted and its encryption key is destroyed.
- Backups that still hold copies expire within [backup expiry: confirm — our copies 14 days; Hetzner server backups may add up to 7 days].
- We keep billing records as long as tax law requires.
10. Transfers between countries
Data is stored on our server in [server location: confirm — Germany or Finland]. Our staff access it from Pakistan. Some sub-processors are in the United States. Where the law that applies to the customer requires it (for example, the GDPR), we use the European Commission's Standard Contractual Clauses or another valid transfer tool. [Transfer mechanism: lawyer to confirm.]
11. Legal requests
If an authority asks for workspace content, we will check that the request is valid under Pakistani law, including PECA 2016, give only what is required, and tell the customer first unless the law forbids it.
12. Liability and order of documents
The limits of liability in the terms apply to this agreement. If this agreement and the terms disagree about personal data, this agreement wins.