Data Processing Agreement
Last updated:
How Conviqa processes personal data on behalf of businesses that use Conviqa, in line with Article 28 of the GDPR and the Law of the Republic of Azerbaijan “On Personal Data”.
1. Scope and roles
This Data Processing Agreement (“DPA”) forms part of the Terms of Service between Conviqa (“Processor”) and the Customer (“Controller”). It applies to personal data the Processor processes on the Controller's behalf when providing the Service (“Customer Personal Data”).
The Controller determines the purposes and means of processing. The Processor processes Customer Personal Data only to provide the Service.
2. Details of processing
| Item | Description |
|---|---|
| Subject matter | Providing the Conviqa platform: shared inbox, customer records, orders, pipeline, automations, analytics and optional AI assistance |
| Duration | The term of the subscription plus the deletion period in section 9 |
| Nature and purpose | Hosting, storing, organising, displaying, transmitting to connected channels, analysing and deleting data as instructed through the Service |
| Data subjects | The Controller's customers and prospects, and the Controller's team members |
| Categories of data | Names, phone numbers, email addresses, social media handles and channel identifiers, delivery addresses, message content and attachments, order and payment status, notes and tags |
| Special categories | None intended. The Controller should not use the Service to process special category data unless it has a legal basis and has assessed the risk |
3. Instructions
The Processor processes Customer Personal Data only on documented instructions from the Controller: these Terms, this DPA and the Controller's use and configuration of the Service. The Processor will inform the Controller if it believes an instruction breaks the law.
4. Confidentiality
Personnel authorised to process Customer Personal Data are bound by confidentiality obligations and receive access only as needed for their role.
5. Security measures
- Encryption in transit (TLS) for all connections to the Service.
- Encryption at rest of channel access tokens and credentials.
- Tenant isolation enforced in the database by row-level security on every workspace table.
- Role-based access control inside each workspace, with an audit log of sensitive actions.
- Passwords stored as salted hashes (argon2id); session and CSRF protections; rate limiting.
- Short-lived signed links for file downloads; uploaded files checked before they are served.
- Minimised data sent to AI providers (no phone numbers, emails or internal notes) and no AI training on Customer Personal Data where the provider allows us to opt out.
- Retention limits for logs, webhook payloads, AI outputs and automation history.
6. Sub-processors
The Controller gives general authorisation for the Processor to use sub-processors. The Processor imposes data protection terms on each sub-processor that are at least as protective as this DPA and remains responsible for their performance. The Processor will give at least 30 days' notice of new sub-processors; the Controller may object on reasonable data protection grounds and, if no solution is found, terminate the affected Service.
| Sub-processor category | Purpose | Notes |
|---|---|---|
| Cloud hosting and storage provider | Hosting the application, databases and files | Region to be confirmed at launch |
| Transactional email provider | Account and notification emails | To be confirmed at launch |
| OpenAI, L.L.C. | AI reply suggestions, summaries and extraction | Only when AI features are used; storage disabled |
| Anthropic, PBC | AI reply suggestions, summaries and extraction | Only when configured; used as an alternative model provider |
Messaging platforms the Controller connects (for example Meta for WhatsApp and Instagram) are not sub-processors: the Controller chooses to use them and they process data under their own terms.
7. Data subject requests
The Service lets the Controller find, export and erase a customer's data. Taking into account the nature of the processing, the Processor will assist the Controller in responding to data subject requests and forward any request it receives directly.
8. Personal data breaches
The Processor will notify the Controller without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data, with the information the Controller needs to meet its own obligations.
9. Deletion and return
During the subscription the Controller can export and erase data at any time. Within 30 days after the subscription ends the Processor will delete Customer Personal Data, unless the law requires it to be kept. Backups are overwritten on their normal schedule, and erasures are re-applied if a backup is restored.
10. Assistance and audits
The Processor will provide the information reasonably needed to demonstrate compliance with this DPA and assist with data protection impact assessments. Audits may be requested once per year with 30 days' notice, at the Controller's cost, and subject to confidentiality.
11. International transfers
Where Customer Personal Data is transferred to a country that does not provide an adequate level of protection, the parties rely on the European Commission's Standard Contractual Clauses (module two, controller to processor, and module three, processor to processor, as applicable) or another lawful transfer mechanism.
12. Order of precedence
If this DPA conflicts with the Terms of Service on the processing of personal data, this DPA prevails.