1. Who we are and scope
The data controller is Digital Delmar, located at JEZB2550 Ismail Al Menzi, Al Zahra, Jeddah 23522, Kingdom of Saudi Arabia. In this policy, “Digital Delmar”, “Anees”, “we”, and “us” refer to that company.
This policy applies to website visitors, waitlist members, customers, older care recipients, family members, caregivers, authorized facility users, installers, and support contacts who interact with Anees.
2. Data we process
We process only data reasonably needed to provide, protect, and improve Anees. This can include personal and sensitive data when needed for care and reassurance.
- Identity, contact, account, country, and caregiver-relationship information, including name, mobile number, and email. A caregiver’s mobile number is required when the account is created; a care recipient’s phone number is optional.
- For care-facility staff and Anees installers: name, job title, and mobile number; a photo and an identity document (optional for facility staff); and for installers also company and certification number.
- Dispatch and view records: who was sent an emergency notice, when, and whether it was accepted for delivery or failed, and how often and when identity-card links were opened; and when the team was dispatched, on its way, and arrived, the outcome (taken to hospital, with the hospital name, or stayed at the care home), and who recorded each step.
- Home and installation details, including service address, covered rooms, appointments, device status, and connectivity.
- Movement, presence, rest, routine, alert, and other insights produced from home signals.
- Health or safety information supplied by users, caregivers, or generated while providing the service, which may be sensitive personal data.
- Live audio data needed to enable audio check-ins. Anees does not use in-home cameras and does not record conversations by default unless separately disclosed and appropriately authorized.
- IP address, browser, device identifiers, security logs, cookies, and language preferences.
- Support communications, inquiries, feedback, consent records, and legal requests.
3. Where data comes from
We receive data directly from you, authorized family members or caregivers, Anees devices and apps, installation and support teams, and service providers working for us. A care facility provides the details of its own staff; Anees operations staff provide installer details. Anyone providing another person’s data must have proper authority and inform that person about this policy.
4. How we use data
We use data to operate Anees and provide reassurance without turning the home into a camera-based surveillance environment.
- Create and verify accounts and manage caregiver permissions.
- Plan installation, activate devices, monitor technical health, and provide maintenance.
- Interpret authorized home signals and present summaries, patterns, and alerts.
- Enable audio check-ins, customer support, and service communications.
- Manage the waitlist, launch, orders, contracts, and payments when available.
- Protect accounts and devices, prevent fraud, and investigate failures or security incidents.
- Meet legal obligations, record consent, and respond to rights requests.
- Improve reliability using aggregated or anonymized data where practicable.
5. Legal basis and consent
Depending on the activity, we rely on performance of a contract, explicit consent, compliance with law, vital interests, or a legitimate interest that does not override the data subject’s rights, under the Saudi Personal Data Protection Law and its Regulations.
Where consent is required—especially for sensitive data or a person lacking legal capacity—we request clear, provable consent. Consent may be withdrawn without affecting processing already lawfully completed.
6. Older people and household members
Anees must be installed and used with the knowledge of the care recipient and affected household members, and with consent where required. It must never be used secretly, for spying, or without appropriate legal authority.
Where a person cannot provide consent, their legal guardian or representative must act within their authority and in the person’s interests.
7. Sharing and disclosure
We do not sell personal data. We share the minimum necessary with the service providers that act on our behalf, under contractual safeguards. Every provider outside Saudi Arabia, what it receives and why is listed in section 8.
We may disclose data to authorized family or care-facility users, competent authorities when legally required, to protect life, health, or safety, or in a lawful corporate transaction with continuing safeguards.
8. International transfers
Anees is hosted in Oracle Cloud Infrastructure in Jeddah, Saudi Arabia. Some service providers process data outside the Kingdom. When personal data is transferred outside Saudi Arabia, we follow the Saudi Personal Data Protection Law (PDPL) and its regulations on the transfer of personal data outside the Kingdom, assess the protection offered, apply the required safeguards, and limit each transfer to what is necessary.
For customers in Egypt, Egypt’s Personal Data Protection Law No. 151 of 2020 also applies. Their data is hosted in Saudi Arabia, which is a cross-border transfer under that law. Where the law requires a licence or permit from Egypt’s Personal Data Protection Centre, we obtain it.
These are the recipients, the country they are in, what each receives, and why:
- OpenAI, L.L.C. (United States): (a) the daily-report figures described in section 16, only when the primary caregiver turns on the AI summary; (b) the text of your support-chat messages, with the names on your account, phone numbers, emails and Anees IDs replaced by placeholders (other names you type may be sent as written), and, only if you agreed when asked, a summary of your account that uses placeholders instead of names. Purpose: to write the summary and the assistant’s replies. We ask OpenAI not to store the request.
- Mailtrap, operated by Railsware (United States or the European Union, as stated in its data processing agreement): the full content of the emails we send: the daily report email (the person’s name, the report date, the day’s status and the report’s figures); emergency-dispatch, incident-update and installer notices, with the details described in sections 14–15; caregiver invitations; staff and installer invitations, which carry the sign-in name and a temporary password that must be changed at first sign-in; and account emails, one-time codes and privacy-request notices. Purpose: to deliver email.
- Twilio Inc. (United States) or Cequens (Egypt): the recipient’s mobile number and the text of SMS and WhatsApp messages. These carry: for family and caregiver alerts and escalations, the care recipient’s first name and the alert type and, where relevant, the main caregiver’s first name, the team name and an identity-card link; for emergency-team dispatch, the resident’s full name, the facility, the room, the address and an exact map link; for incident outcomes, the hospital name; for installer notices, the installer’s name, the visit time and an identity-card link (section 15); and shop verification codes. Purpose: to deliver emergency, incident, installer and verification messages. We use Twilio or Cequens; shop verification codes are sent through Twilio. WhatsApp messages travel over WhatsApp, operated by Meta (below).
- Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging), United States: the notification text, which carries a first name and the notice described in sections 14–15, and the device token. Purpose: to deliver push notifications.
- Meta Platforms, Inc. (United States), which operates WhatsApp, Instagram and Facebook Messenger: the WhatsApp messages we send you (see Twilio and Cequens above), and the messages you write to Anees support on WhatsApp, Instagram or Facebook if you choose to contact us there. Purpose: to carry the message on the channel you use.
- Google Maps Platform or Mapbox (United States): the approximate location of the home, rounded to about 1 km. Purpose: to find the country’s emergency number and the nearest hospital.
- Paymob (Egypt, Saudi Arabia or the United Arab Emirates, according to the customer’s region): name, email address, mobile number and the order being paid. Purpose: to take payment. Card details are entered on Paymob’s page and never reach Anees.
9. Retention and destruction
We retain data only as long as needed for its stated purpose, service delivery, legal obligations, and dispute handling. The period depends on data type and sensitivity, account and contract duration, security requirements, and recordkeeping law.
We review unconverted waitlist records after 24 months without activity. The review date is not automatic deletion: authorized staff decide whether a lawful purpose still requires retention or the record should be irreversibly anonymized.
When no longer needed, we securely delete or destroy data or irreversibly anonymize it. Limited copies may remain in backups until the secure deletion cycle completes.
10. Security and incidents
We use proportionate technical and organizational controls, including access restrictions, encryption in transit, operational safeguards, security monitoring, and testing. No electronic system is entirely risk-free.
If unauthorized access or disclosure may cause harm, we contain, assess, and notify as required by applicable law.
11. Language and approximate country
We remember Arabic or English and the appropriate Arabic dialect for returning visitors (the cookies are listed in section 12). We may infer country approximately from an IP address to select Khaleeji, Egyptian, or neutral Arabic. This does not provide a precise home or city location.
You can change language from the menu. Deleting cookies may cause the dialect to be selected again from country on the next visit.
12. Cookies and consent
You can change your choice at any time from the “Cookie settings” link at the bottom of the page.
- Necessary (always on, no consent asked): anees_consent, which remembers this choice (365 days); anees_language, anees_locale and anees_dialect, which remember your language and dialect (365 days); anees_shop, an HTTP-only cookie that page scripts cannot read, which shows you completed shop verification for the length of that session; and, in the staff and care-facility apps, the sign-in session cookies, anees_mfa_pending (HTTP-only, a few minutes, held only while you sign in) and anees_mfa_trust (HTTP-only, 30 days, remembers that this browser completed two-step sign-in).
- Optional (only with your consent): the chat widget, run by Chatwoot on Anees servers, which sets its own cookies, and the how-to videos embedded from YouTube on the support site. We do not load the widget, and none of its cookies are set, unless you choose Accept all. If you choose Only necessary, the chat does not appear and you can reach us at Info@ddelmar.ai.
13. Your rights
Under Saudi law, you may have rights to be informed, access and receive a copy, request correction or completion, request destruction when data is no longer needed, withdraw consent where applicable, and complain to the competent authority.
Email Info@ddelmar.ai to exercise a right or ask about a decision or alert. We may verify identity before acting to protect the data.
14. Mobile numbers and SMS
We use a caregiver’s mobile number for emergency-dispatch notices about the care recipient, incident updates, and installer-visit notices. When you order from the shop, the mobile number you enter receives a verification code. Messages are sent in the language chosen for the account.
SMS text messages are sent through Twilio Inc. or Cequens (section 8), which receive the recipient’s number and the message text only to deliver it. The same notices may also be sent by email and as an in-app notification. If no mobile number or email is on file, the notice goes out through the channels that are available.
When a care facility decides to dispatch an emergency team after a fall alert, each member of the team the facility chose receives an SMS with the resident’s name, the facility, the room, the address, and a map link so they can reach the resident. We record each recipient, their name and number at the time, and whether the message was accepted for delivery or failed. Phone numbers and addresses are not written into general audit logs.
The family caregivers of the resident receive incident updates by push notification, SMS, and email: the team dispatched, the team on its way, the team arrived, and the outcome, either taken to hospital (with the hospital name) or stayed at the care home. These step messages carry no identity link.
We do not use mobile numbers for marketing as part of these notices, and we do not sell or share them for advertising.
15. Emergency responders, installers, and identity links
A care facility may upload a photo and an identity document for any of its staff (both optional); a staff member on an emergency team receives dispatches only once both are on file. The photo is shown to the resident’s family on the emergency identity card; the identity document is never shown to families. Both are stored privately and viewed only through short-lived links. Anees operations staff add installer details, including a photo and an identity document. The purpose is to let a family know who is coming to their relative and to allow the person’s identity to be verified.
When an emergency team is dispatched, the caregivers who receive the care recipient’s alerts are notified in the app, by email, and by SMS: the email lists each member’s name and job title, and the SMS gives the team name. When an installer is assigned or changed, the caregiver who requested the installation is notified through the same channels. The email and SMS each carry a personal link to an identity card; in-app notifications carry no link. An emergency-team card shows the care recipient’s first name, the facility name, the team name, the dispatch time, and each member’s name, photo, and job title. An installer card shows the installer’s name, photo, company, certification number, phone, and the visit time. Anyone the link is forwarded to can see the same card. The identity document is never shown to families. It is kept for verification only by the care facility (for responders) or by Anees operations (for installers), and only their authorized administrators can view it.
An emergency-team link expires 72 hours after the dispatch. An installer link expires 2 days after the scheduled visit, or 14 days after it was issued if no visit is scheduled, and is cancelled if a different installer is assigned, the installer is unassigned, or the visit is cancelled; it is extended if the visit is rescheduled. These pages are not indexed by search engines, and we log how many times each link was opened, when it was last opened, and whom it was issued to.
Photos are used for identity cards and identity documents for verification only, and both are retained under section 9. Their deletion can be requested at Info@ddelmar.ai once the person leaves an emergency team or stops working as an Anees installer. Responders and installers can exercise the rights in section 13.
16. Use of AI: daily report summary and support assistant
Each evening Anees prepares a daily report for the caregivers linked to a care recipient, at the time zone set for that person. The report is built from the day’s data collected by Anees devices: device connectivity, sleep, activity and presence, heart and breathing rates, and falls or vital-sign alerts and how they were handled. The report is stored in the family’s account so it can be read in the app.
We send a generic push notification saying the report is ready, with no details, and the report by email through Mailtrap (United States or the European Union, as stated in its data processing agreement; see section 8) with its full content: the person’s name, the report date, the day’s status and the report’s figures, including the AI summary if it is on. Email is not end-to-end encrypted, so anyone who can read the recipient’s mailbox can read the report. The report can also be read inside the app.
The AI summary is optional. It is off by default and can be turned on only by the care recipient’s primary caregiver. Without it, the report shows ready-made text for the day’s status and loses none of its content. If a summary cannot be created for any reason, the ready-made text is shown.
When the feature is on, we send the following, and only this, to OpenAI, L.L.C. in the United States, acting as our processor: the day’s status and its reasons; for each device its type, whether it is new, its coverage percentage, and its longest offline period in minutes; sleep measures (time in bed, night-time bed exits, turn-overs, restless minutes); activity and presence minutes; average heart and breathing rates and minutes outside limits; and events with their local time, type (fall or vital-sign alert), fall response, and whether resolved.
We never send the person’s name, any identifiers, room labels, free-text alert notes, or the time zone name. We instruct OpenAI not to store the request (store: false), and under OpenAI’s published API terms, API data is not used to train its models. The model is told to describe the day consistently with the calculated status and not to diagnose.
The primary caregiver can turn the summary off at any time in the daily report settings in the app, and nothing further is sent to OpenAI from the next report. To ask a question or exercise your rights, write to Info@ddelmar.ai.
Support assistant: the first reply in the Anees support chat (website, apps, and WhatsApp/Instagram/Facebook inboxes) may come from an automated assistant. Messages on WhatsApp, Instagram and Facebook pass through Meta, which operates those channels (section 8). To answer, we send OpenAI the text of your message and a few recent messages of that conversation (yours and the assistant’s), with the same instruction not to store them (store: false). Before anything is sent, names on your account (when you write from the app while signed in), phone numbers, email addresses and Anees IDs are replaced by placeholders such as [YOU] or [ROOM_1]; the assistant’s reply is turned back into real names on our side. Names you type that are not on your account may be sent as written. When you write from inside the app, the assistant asks once whether it may use your account details. Only if you agree do we also send a short summary: your role and language; placeholders for you, your family and caregivers with the relationship label you chose; the type of each sensor, a placeholder for its room, its status and last-contact time; the number of recent alerts by type and status; and the status of open orders. Alerts are sent as counts only. If you decline, or you are not signed in, no account details are sent. To withdraw consent, write to Info@ddelmar.ai. Room names and relationship labels are text customers type themselves, so do not put details in them that you do not want shared.
A message suggesting someone may be hurt is not sent to the model: it is answered at once with advice to call emergency services and passed to a member of the Anees team. The assistant hands the conversation to a person for anything about a specific account, order, payment, or installation appointment, for complaints, when it cannot answer, and whenever you ask for a person. It never asks for a password or card number; do not share them in chat. The assistant keeps the last eight messages of recent conversations in our server’s memory, with no fixed time limit, until newer conversations replace them or the server restarts; the conversation itself is kept in our support system.
Help messages: if a care recipient types a phrase in the support chat that suggests they need help, that message is not sent to OpenAI. We create a “help request” alert that reaches their caregivers and, if they live in one, their care home, and includes the text of their message. It appears to them in the app only, never in push notifications, text messages, or email. The message is also posted in the support chat, so our support team can read it. We may also show the person and their caregivers their country’s emergency number and the nearest hospital. For this we send the approximate location of the home, rounded to about 1 km, from the installation address (or the care-home branch), to Google Maps Platform or Mapbox to find the country and nearest hospital, when an installation is completed, when emergency information is shown on an alert, and when a help message is sent in the support chat, and we keep the result for 30 days.
AI makes no decision about alerts or emergency dispatch.
17. Contact and changes
Contact us at Info@ddelmar.ai or Digital Delmar, located at JEZB2550 Ismail Al Menzi, Al Zahra, Jeddah 23522, Kingdom of Saudi Arabia.
We may update this policy when services or law change. We will publish the new version and effective date and provide additional notice when a change is material or requires renewed consent.
