Version 2026-11-15. AlKhwarizmi Metrics Analytics (FZC), licence 20094. This link identifies this specific published version.
1. Scope, roles and precedence
This Data Processing Agreement applies when AlKhwarizmi Metrics Analytics (FZC) processes personal data on behalf of a business customer using AKM. The customer determines the purposes and lawful instructions as controller; AKM acts as processor for those activities. Each party remains a controller for its own independent administration, billing, security and legal purposes.
This DPA forms part of an applicable customer contract incorporating it. A separately signed data-processing agreement or order may specify additional requirements. Its specific data-protection provisions prevail over conflicting general service terms. A member acknowledging this notice does not by itself amend an organisation’s separately signed agreement.
2. Processing description
- Subject matter and purpose: authorised marketing reporting, analytics, workspace collaboration, connected-data processing, pipelines, exports, Website Intelligence and optional AI or media operations selected by the customer.
- Duration: the service term and the period reasonably necessary for instructed return/deletion and lawful retention, as specified in the order, product settings and this DPA.
- Data subjects: customer staff and authorised users, website visitors, marketing audiences, leads, customers and other people whose data the customer is authorised to process.
- Data categories: business contact and account identifiers, permitted source-platform records, campaign and analytics information, website/session/event context, selected diagnostics, customer-provided content and the related technical and access metadata.
- Special-category and restricted data are not part of the standard permitted scope. Health records, patient information, government-restricted datasets, payment-card data and other sensitive material require separate written review and safeguards before submission.
3. Documented instructions and customer responsibilities
The contract, authorised feature configuration, account connections, permissions and customer requests constitute documented instructions. AKM processes customer personal data only to provide and secure those services under those instructions, unless law requires otherwise; where permitted, we inform the customer of the legal requirement.
The customer is responsible for a lawful basis, notices, necessary consents, authorised source access, appropriate retention settings and lawful destinations. It must not instruct an unlawful transfer or disclosure. We will inform the customer if we reasonably consider an instruction unlawful and may pause the affected activity while it is resolved. Customer responsibility does not remove AKM’s own processor duties.
4. Confidentiality and access
Persons authorised to access customer personal data must be subject to confidentiality obligations and access appropriate to their role. Customer administrators control their own members and sharing. Support access must be justified by the task and handled with appropriate safeguards. Customer passwords, tokens or sensitive datasets should not be sent in ordinary support email.
5. Technical and organisational measures
Measures include account, tenant and workspace permission boundaries; authentication and scoped integration access; HTTPS for public service endpoints; protection of integration credentials; sanitised operational logs; controlled deployment and change handling; and investigation of security events. The measures applicable to a feature and environment must be assessed with its actual configuration.
The customer must configure its own source permissions, destination access, public sharing, analytics consent mode, event exclusions and replay masking. We do not represent that all stored records have identical encryption, every legacy component is identical or every customer environment has completed an independent security certification. A required security schedule, backup location, recovery objective or strict residency scope must be agreed and verified before use.
6. Service providers and subprocessors
The customer authorises providers necessary for the selected services, as identified in the subprocessor notice and any agreed order. We require relevant providers acting as our subprocessors to have appropriate written data-protection obligations and remain responsible for their processing to the extent required by applicable law and this agreement.
For a material addition or replacement affecting customer personal data, we will provide advance notice where reasonably practicable, normally at least 30 days, and a reasonable opportunity to object on documented data-protection grounds. We will discuss an appropriate alternative or ending the affected service if the objection cannot reasonably be resolved. Urgent security or legal changes may require shorter notice with an explanation.
A source account, AI client or export destination independently selected and contracted by the customer is not automatically an AKM subprocessor for every purpose; its role and the applicable agreement must be assessed.
7. Location and international processing
The selected regional environment identifies core hosting. UAE core infrastructure uses Microsoft Azure in the UAE; Egypt core infrastructure uses LinkDataCenter in Egypt. Optional providers, recovery or support arrangements, source platforms, destinations and some callback routing can involve other countries. Acceptance does not migrate an account or authorise every possible onward transfer.
Each party must comply with applicable international-transfer restrictions, including contractual safeguards and any required approvals or permits. Where consent is the relevant legal mechanism, it must meet the applicable standard and cannot override a legal prohibition. The customer must not select a destination or feature inconsistent with its legal or contractual restrictions.
Strict in-country processing, including backups, support access and integrations, requires a written scope and reviewed configuration. General UAE availability is not evidence of DESC certification or permission to process regulated health or government data.
8. Rights requests, assessments and regulator cooperation
We provide reasonable assistance, taking account of the nature of processing and information available, with valid data-subject requests, security assessments, impact assessments and consultations required by applicable law. The customer normally leads responses concerning data for which it is controller. We may redirect a request to it unless prohibited by law.
We will make relevant information reasonably available to demonstrate compliance with this DPA. A proportionate review or audit must protect other customers, confidential information and security. It must be agreed in scope, timing and access method unless an authority or law requires otherwise. Neither a confidentiality clause nor audit procedure may prevent lawful regulator cooperation.
9. Personal-data incidents
We notify the customer without undue delay after becoming aware of a personal-data breach affecting its customer personal data, and comply with applicable legal notification obligations. We provide available information about the nature, affected categories, likely consequences, response and a contact point, and supplement it as the investigation develops.
The parties cooperate in containment, remediation and required notifications. The customer remains responsible for its controller obligations, and AKM remains responsible for obligations imposed directly on it. A notice is not by itself an admission of liability. These provisions do not exclude a mandatory deadline or duty.
10. Return, deletion and recovery copies
On ending the affected service or a valid instruction, we will return or delete relevant customer personal data as agreed, subject to lawful retention and technically necessary recovery-copy handling. A customer must request and retrieve needed exports before expiry of an agreed retrieval period. Third-party copies and customer destinations may require action with the relevant provider.
Retained data must be limited to its permitted purpose, protected against routine use and removed when the retention ground ends. A restoration must preserve applicable deletion obligations. The parties should agree a specific retention and recovery schedule where required; no universal 90-day backup deletion promise is made by this document.
11. Other terms and contact
Service responsibility, liability and dispute provisions apply only to the extent lawful and not inconsistent with this DPA or a signed agreement. Nothing prevents a regulator from exercising powers or an individual from exercising non-waivable rights. Questions or requests may be sent to info@alkhwarizmimetrics.com. This is DPA version 2026-11-15.