إشعار معالجة البيانات

This notice complements the Privacy Notice with more precise technical detail: what the processing activities are, what data enters each one, and which third parties are involved and what their status actually is today.

1. Processing activities

1.1 Creating and operating an account

Data: name, e-mail, password (stored in hashed form by the authentication provider), phone, self-declared country, role, interface language. Purpose: for the account to exist, to sign in, and to route you to the right interface. Without this data an account cannot be created.

1.2 Delivering the requested service

Data: booking and appointment data, consultation type, status, cancellation reasons, meeting links, in-app notifications. Purpose: to deliver the consultation you requested and manage its appointment.

1.3 Health and clinical information

Data: chronic conditions, medication, allergies, date of birth, your clinical notes, uploaded files (clinical images, lab reports, radiology, prescriptions), the consultation record and the doctor's summary. Purpose: to provide the medical opinion and keep the necessary medical record. Basis: separate explicit consent, requested at the point where health information is first submitted or a consultation is requested — not required to read educational content or join a waiting list.

Files are held in private, non-public storage, and access is restricted at the database level.

1.4 Usage measurement (optional)

Data: event name, internal page path, event time, an optional hashed session identifier, and sanitised metadata. Every payload passes through a sanitiser that removes name, e-mail, phone, notes, file paths, and user and patient identifiers before anything is stored. By construction this log cannot contain health data.

1.5 Marketing

Not implemented. There is no e-mail, WhatsApp or SMS delivery provider in the source code; in-app notifications are the only existing channel.

1.6 Security and abuse prevention

An IP address is used momentarily and in hashed form (SHA-256) to build a rate-limiting key. The raw address is never stored and never logged. Sensitive operations are recorded in an audit log.

1.7 Consent records

Data: consent category, granted or withdrawn, text version, a snapshot of the text shown, its language, the screen, and the server time. The database layer makes any edit impossible, and blocks deletion except inside an explicitly declared account erasure.

2. Third parties and their actual status

• Supabase — currently used. Database, authentication and storage.
• Hostinger — planned hosting provider, nothing deployed yet. The application is not currently deployed.
• Upstash — required/planned, not yet provisioned. Used for rate limiting.
• Google Analytics 4 — optional and off unless explicitly enabled and configured. Not configured.
• Google AdSense — optional and off unless explicitly enabled and configured. No real advertising account is configured.
• E-mail / WhatsApp / SMS providers — not implemented.

3. International transfers

Data may be processed on infrastructure located outside your country. International transfer requirements differ between countries, and no claim of automatic compliance with every legal regime is made here.

4. Retention

Final numeric retention periods have not yet been approved for each category. Until they are, data is kept for as long as needed to provide the service and to meet legal and professional duties. The retention decision is tracked as an owner action required before launch.

5. Version

Version data_processing_notice_v1, effective from 2026-08-02.