Aveexia · legal information
Data Processing Agreement
Last updated: October 17, 2026 · v2026-10-17
1. Parties, roles and scope
This Data Processing Agreement under Article 28 GDPR applies between the customer (controller) and Aveexia, Abdirahman Hersi, a sole trader in Malmö, Sweden (processor). It forms part of the agreement and takes effect when the customer accepts the terms on creating the workspace. It applies for as long as Aveexia processes personal data for the customer.
If the DPA and the terms of service conflict, the DPA prevails on matters of personal data.
2. Aveexia’s commitments
- Process personal data only on the customer’s documented instructions, meaning this agreement, the customer’s configuration of the service and written instructions. If an instruction infringes data protection rules, we tell the customer.
- Make sure people who process the data are bound by confidentiality.
- Take the technical and organisational measures described in Annex B.
- Assist the customer in responding to data subject requests. Requests that reach us directly are forwarded to the customer within five working days.
- Assist the customer with impact assessments and prior consultation with a supervisory authority, to a reasonable extent.
- Notify the customer of a personal data breach affecting the customer’s data without undue delay and no later than 48 hours after we become aware of it, with the information we have about what happened, which data is affected and what measures were taken. The customer is responsible for notifying the competent supervisory authority (in Sweden IMY) within 72 hours under Article 33.
- Delete the data after the agreement ends as set out in section 5.
3. Subprocessors
The customer gives Aveexia general authorisation to use the subprocessors listed in the subprocessor register. For planned additions or replacements we notify the customer by email at least 30 days in advance. The customer may object within 14 days on data protection grounds. If we cannot resolve the objection, the customer may terminate the affected part of the service. Aveexia has a written agreement with each subprocessor with equivalent data protection commitments and is responsible for the subprocessors’ performance.
4. Transfers outside the EU/EEA
Transfers take place only where there is a valid basis under Chapter V GDPR, such as an adequacy decision or the European Commission’s standard contractual clauses, and only to the subprocessors in the register. Liability under the terms of service applies.
5. Deletion and return
When the agreement ends, the customer can request an export of its data for 30 days. After that we delete the data within 30 days. Backups are overwritten on the provider’s cycle, and deleted data is not restored to production. Data we are legally required to keep (such as accounting records) is excepted.
6. Audit
Aveexia provides the information needed to show compliance with Article 28, such as answers to security questionnaires. If that is not enough, the customer may, with 30 days’ notice and no more than once a year, carry out an audit during normal working hours without disrupting operations. The customer bears the cost. The auditor must be bound by confidentiality.
Annex A: The processing
- Purpose: run the customer’s AI agent in the selected channels, answer and handle end users’ questions, book and forward cases, and provide support and security for the service.
- Type of processing: storage, search, AI response generation, transmission, deletion.
- Categories of personal data: name, email, phone number and other contact information that end users provide, message content, booking details, technical data such as IP address. Voice channel: phone number, call metadata and transcripts. No special categories intended.
- Categories of data subjects: the customer’s customers, website visitors, callers and others who contact the customer, and the customer’s users of the service.
- Duration: the term of the agreement, with retention periods per the retention matrix (default 90 days for conversations).
Annex B: Security measures
See the security page. In short: encryption in transit (TLS), encryption at rest at the infrastructure providers, separation between customers using server-enforced authorisation and row-level security in the database, role-based access, limited internal access, security headers and rate limiting, and a documented incident procedure.
Annex C: Subprocessors and contact
Subprocessors, purposes and locations are set out in the subprocessor register, which serves as Annex C. Data protection contact: privacy@aveexia.com. Contract questions: legal@aveexia.com. Version 2026-10-17.