Afiyah · Policy notice · 29 October 2026
Data retention and deletion.
A clear purpose, a defined period and an accountable deletion process. These are Afiyah’s retention rules; a shorter necessity period or a binding legal requirement takes priority.
Finding your country preference…
| Data category | Period and trigger | Purpose and limits |
|---|---|---|
| Enquiries and support | Up to 24 months after the enquiry or support case is closed; delete earlier when no longer needed. | Respond, follow up and resolve documented service issues. |
| Account and profile data | While the account is active; after closure, retain only justified support or dispute records for up to 24 months. | Deliver the account, verify permissions and resolve issues; no automatic two-year copy of every field. |
| Non-clinical wellbeing data | While needed for the selected service; delete on a valid request or when the purpose ends. A documented closure exception may last up to 24 months only where lawful and necessary. | Provide the requested wellbeing features; optional collection can be stopped. |
| Clinical and regulated health records | The service-specific statutory schedule applies, including the UAE health-record rule where applicable. | Clinical continuity, patient safety and legal record obligations. |
| Private-service AI interaction records | 90 days by default where recording is necessary; a documented higher-risk review may justify up to 365 days. A clinical record or legal hold follows its own rule. | Investigate safety, quality and service issues using the minimum necessary information. Public website chat is excluded from this logging schedule. |
| Consent and rights evidence | During the relevant relationship and normally six years afterwards where necessary to evidence permissions or meet a legal duty; retain a minimal record, not the underlying health file. | Demonstrate the choice, version, scope, withdrawal and response. A cookie preference is not a six-year tracking identifier. |
| Security and access logs | Normally six months; up to 24 months for a documented risk or incident need, or a different mandatory period. | Protect access, investigate abuse and demonstrate control, without unnecessary message or health content. |
| Invoices and financial records | Applicable tax and accounting periods. Relevant UAE corporate-tax records are kept for at least seven years after the relevant tax period ends. | Tax, accounting, refunds and payment disputes. No full card number or card security code is stored by Afiyah. |
Purpose and minimum information
We keep identifiable data only while needed for a stated purpose and valid legal basis. The schedule sets limits rather than permission to retain everything until a deadline. Deletion, anonymization and pseudonymization are different: a coded or hashed record that can still relate to a person remains protected personal data. Fully anonymous statistics may remain only when re-identification is not reasonably possible.
Health records and statutory retention
Clinical records follow the law applicable to the service and the responsible healthcare organization. For health information within the scope of UAE Federal Law No. 2 of 2019 on ICT in health fields, Article 20 provides a minimum of 25 years from the last health procedure. This is not a blanket period for every website enquiry or ordinary wellbeing entry. HIPAA does not itself set a universal medical-record retention period; its documentation requirements are a separate category. A provider may need to retain its original record independently of an Afiyah account deletion.
Website storage has separate limits
Website cookie preferences last 180 days. Manual country and language choices remain until changed or browser storage is cleared. Public guide context stays in page memory; an optional same-tab handoff expires after five minutes and is removed on arrival or a new conversation. The public guide does not send chat to an AI provider or create stored private-service AI transcripts. Journal daily view tokens are pruned on the next recorded view after their four-calendar-day window; totals remain. A hashed Journal reaction remains until changed or removed. Clearing the browser identifier does not erase that server reaction. See Cookie Policy for exact controls.
Deletion, backups and processors
A verified deletion request is applied to relevant active systems and communicated to processors or recipients where required. Backup copies are restricted from ordinary use and removed through the documented rotation or a legally required earlier process. If restored, deletion restrictions must be reapplied before normal use. We explain any residual copy, legal exception and expected handling rather than promise instant erasure from every backup. Provider settings and contractual deletion evidence are part of the control record.
Legal holds and accountability
A dispute, tax rule, clinical obligation or lawful preservation request may require specified records for longer. The hold must identify the purpose, authority, information, access restrictions and review date; unrelated data is not retained automatically. The privacy owner reviews expired records and deletion evidence. We explain a lawful refusal or extension and available complaint routes. Closing a subscription, withdrawing optional consent and deleting an account are distinct requests.
Questions and complaints
Contact privacy@getafiyah.com for privacy, permissions, deletion or security concerns, and contact@getafiyah.com for service complaints. Include a brief description and a safe reference; do not attach health records, identity documents, passwords or card details to an initial email. We verify identity and authority before releasing or changing personal data. You may complain to the competent regulator or court without first giving up any statutory right.