Legal
Data Processing Agreement
Effective 15/11/2026 · Version 1.2
1. Parties and roles
This Data Processing Agreement ("DPA") is between the customer organisation ("Customer", the controller) and Ashnet AI ("we", the processor), and forms part of the Terms of Service.
The Customer is the controller of the personal data it keeps in ASHNETAI (tenants, landlords, leads, vendors, staff). We process it only on the Customer's documented instructions — the Terms, this DPA and the Customer's use and configuration of the Service — and tell the Customer if we believe an instruction breaks the law.
2. Processing details
Subject matter and duration: providing the service for the term of the subscription.
Types of data: contact details, identity document numbers, lease, payment and maintenance records, communications. Data subjects: tenants, owners, leads, contractors and staff.
Nature and purpose: hosting, storing, organising, retrieving, displaying, transmitting (email, WhatsApp, SMS and portals the Customer uses), backing up, exporting and deleting personal data so that the Service works as described in the Terms.
The Customer's obligations: to have a lawful basis for the personal data it puts into the Service, to give data subjects the notices the law requires, and to configure who may see what (roles, building restrictions, two-step verification).
3. Confidentiality and security
Staff with access are bound by confidentiality. Measures: separation of each organisation's data (application checks and database row-level security), encryption of identity numbers and integration secrets, role-based access, two-step verification, audit logging and nightly backups.
Our support staff enter the Customer's workspace only at the Customer's request or to fix a fault. Each support session is time-limited, recorded in the Customer's audit log, and the Account Owner is notified when it starts.
4. Sub-processors
Current sub-processors: Vercel (application hosting and file storage), Neon (database) and Resend (email delivery). When switched on: Stripe (card payments), Cloudflare Turnstile (sign-up security check) and Anthropic (the in-product help assistant, which is never given organisation records). Integrations an organisation connects itself (its own mailbox, WhatsApp or SMS provider) process data on the organisation's instructions.
AI connectors are off until the organisation switches them on. An AI app a member then connects (for example Claude or ChatGPT) receives the records that member asks for, within the member's role and buildings. The organisation chooses that AI provider and instructs it under its own agreement; the provider is not our sub-processor. We record each connection and what it reads or creates in the audit trail, and the organisation can revoke any connection at any time.
We bind every sub-processor by a written agreement with data-protection obligations at least as protective as this DPA, and remain responsible for their performance. We tell the Account Owner by email at least 30 days before adding or replacing a sub-processor; if the Customer objects on reasonable data-protection grounds and we cannot resolve it, the Customer may end the affected Service and receive a refund of the unused part of the period paid.
5. Where data is processed
The application runs in Frankfurt, Germany (Vercel, region fra1). The database is in London, United Kingdom (Neon). Uploaded files are kept in a private store in Frankfurt (Vercel Blob). Email is sent through Resend. We are operated from the United Arab Emirates, and our staff there can reach the data to run and support the Service.
We do not move the Customer's data to another country without telling the Account Owner 30 days before, as for a new sub-processor.
6. Customers outside the UAE
We hold the Customer's records only on the Customer's behalf and use them for nothing of our own. The Customer is responsible for having a lawful basis under its own country's law for keeping its records with a provider abroad. We give the Customer, on request, the information it needs to assess the protection of the data: where it is kept, who processes it and the security measures in place.
Oman: the Customer is the controller of the personal data of its tenants, landlords, leads, suppliers and staff, which is kept and processed outside Oman, in Germany and the United Kingdom. The Customer confirms that it has told those people so and has their explicit consent to the transfer where the law requires it. We tell the Customer without delay of a personal-data breach so that the Customer can meet its 72-hour duty to notify.
Saudi Arabia: the Customer is the controller and decides whether to transfer personal data outside the Kingdom, after its own risk assessment. On request, we sign with the Customer the standard contractual clauses (controller to processor) published by the Saudi Data and AI Authority, unchanged; where they and this DPA differ, the clauses prevail.
United Kingdom: for personal data the UK GDPR covers, this DPA sets out the processor terms of Article 28 of the UK GDPR; the European Economic Area, where part of the processing happens, is treated as adequate by the United Kingdom.
New Zealand: we store and process the Customer's personal information only on its behalf and on its instructions, and do not use or disclose it for our own purposes. We name the hosting regions and each sub-processor, tell the Customer before either changes, protect the information to a standard comparable to the Privacy Act 2020, and tell the Customer without delay of a privacy breach so the Customer can meet its own duties.
7. Assistance
We help the Customer answer data subject requests (one person's export and erasure are available in the product) and, where reasonably needed, with impact assessments and consultations with authorities.
We notify the Customer of a personal data breach affecting its data without undue delay, and in any case within 72 hours of becoming aware of it, with the information we have about its nature, likely consequences and the measures taken; we update the Customer as more becomes known.
8. Return and deletion
The organisation can export all its data at any time. Closing the organisation erases personal data after a 30-day cooling-off period; financial records are kept for the legal retention period.
9. Audits
We make available the information reasonably needed to show compliance with this DPA, first by answering the Customer's written questions and sharing relevant documentation.
Where that is not enough, the Customer (or an independent auditor bound by confidentiality) may audit our compliance once a year on 30 days' written notice, during business hours, at the Customer's cost and without access to other customers' data. A competent authority may audit at any time the law allows.
10. Governing law
This DPA is governed by the same law and courts as the Terms of Service: the laws of the United Arab Emirates as applied in the Emirate of Dubai, and the courts of Dubai. If this DPA and the Terms conflict on personal data, this DPA prevails.
11. Contact
Data-protection questions: support@ashnetai.com. Ashnet AI — Cloud business (operating online).
Version history
| Version | Date | Changes |
|---|---|---|
| 1.2 | 15/11/2026 | Adds customers outside the UAE: where their data is held, a section for each country we serve, the country-choice cookie, and prices in AED with the customer's own taxes. |
| 1.1 | 10/11/2026 | Adds when our support staff enter a customer's workspace: only on request or to fix a fault, time-limited, recorded in the audit log, with the Account Owner notified. |
| 1.0 | 30/10/2026 | First complete version, in force. |
| 0.2-draft | 30/10/2026 | Adds AI connectors: AI apps an organisation connects act on its instructions. Still a draft. |
| 0.1-draft | 15/10/2026 | Draft structure with placeholders, pending legal review. Not yet in force. |