Legal
Data processing terms
How Reportive processes its clients' data, under Article 28 of the GDPR and the UK GDPR. For a signed copy, write to contact@reportive.io.
1. Subject
Reportive processes personal data on the Client's behalf only to provide the service in the contract. The details (what data, about whom, for how long) are in Annex 1.
2. Instructions
Reportive processes the data only on the Client's written instructions; instructions are the service contract, these terms and anything the Client asks in writing, including by email. If an instruction in its view breaks the law, it says so at once. It does not use the data for its own purposes, does not sell it and does not train AI models with it.
3. Confidentiality
Only those who need access to provide the service, and who are bound by confidentiality, have access to the data.
4. Security
Reportive applies the measures in Annex 2 and reviews them at least once a year. It may change them only if the level of protection does not fall.
5. Sub-processors
The Client approves the sub-processors in Annex 3. For a new or changed sub-processor, Reportive informs the Client 30 days in advance; if the Client has a serious reason to object and no solution is found, it may terminate the affected service without charge. Every sub-processor is bound by contract to obligations equal to these.
6. Transfers outside the EU and the United Kingdom
Where data goes to another country (Annex 3), the transfer relies on the safeguards the law provides (standard contractual clauses or the EU-US Data Privacy Framework and its UK Extension), as set out in the sub-processors' data processing terms.
7. Assistance
Reportive helps the Client answer requests from individuals (access, correction, erasure and so on), carry out impact assessments and answer the supervisory authority. A request from an individual that reaches Reportive is passed to the Client within 5 working days, and Reportive does not answer it itself without instruction.
8. Breaches
If it becomes aware of a breach affecting the Client's data, Reportive notifies the Client without undue delay and within 48 hours at the latest, with what it knows: what happened, which data and people are affected, likely consequences, what it has done and what it proposes. It adds information as it learns it.
9. End of the service
When the service ends, Reportive, as the Client chooses, returns the data in a file or deletes it, together with any copies, within 90 days, and confirms this in writing. Only what the law requires to be kept is excepted.
10. Audit
Reportive gives the Client what it needs to show that these terms are met (for example the results of the latest security review) and accepts an audit by the Client or its auditor, on 30 days' notice, during working hours, once a year or after a breach, at the Client's cost.
11. Duration
These terms apply for as long as the service contract and for as long as Reportive holds the Client's data. Where the service contract says something different about data, these terms prevail.
Annex 1: what Reportive processes
| Purpose | Monthly management reporting: report pages, What to Watch, Cash Pilot, emailed Reports, AI analyses, Ask Reportive |
|---|---|
| Types of data | Accounts (trial balance, ledgers), sales by customer and product, cash, receivables and payables, department data. These include names of customers, suppliers and, where they appear in the books, employees. Details of the Client's users of the platform (name, email, role, sign-ins) |
| Individuals | The Client's customers, suppliers and employees who are natural persons; the Client's users of the platform |
| Special categories | None; the Client does not send health, belief or other special category data |
| Operations | Loading, storage, calculation, display to the Client's users, emails to recipients the Client sets, sending figures to an AI model for texts and answers |
| Duration | For as long as the service contract and up to 90 days after (point 9) |
| Logging | Who signs in and what they open: 12 months. Ask Reportive questions: 12 months. Failed sign-in attempts: 30 days |
Annex 2: security measures
- Separation by client: each client has its own service, which reads only that client's data, with its own key. Every page opens only with a signed access key that expires within hours. Separation tests run automatically on every new version.
- Encryption: HTTPS everywhere; data encrypted at rest.
- Access: passwords stored only in hashed form; limits on failed sign-in attempts; administrator sessions expire; secret keys only in a secure store, never in the code.
- AI: calculations are made on the server, not by the model. Ask Reportive only reads, only the Client's data, with a check before every query and usage limits per user and day.
- Logging: access logs kept for 12 months, so it can be seen who saw what.
- Changes: every change is reviewed before it reaches the main version, and an automatic check stops a new version that changes a client it should not.
- Review: regular security reviews.
Annex 3: sub-processors
| Provider | What it does | Where | Client data involved |
|---|---|---|---|
| Google Cloud | Services, database (BigQuery), files, logs, secrets | Belgium and USA (BigQuery) | All |
| Anthropic | AI model for analyses and Ask Reportive | USA | Figures for the texts, users' questions and the rows an answer needs |
| Supabase | AI analyses and email settings | Germany | Analysis texts, email recipients |
| Brevo | Sending the emailed Reports | France | Recipients, email content |
| GoDaddy | The platform server app.reportive.io | USA | User accounts, access logs, Ask Reportive questions |
See also the privacy policy.