Scope and roles
This policy describes how AnzarSeha processes personal data. It distinguishes two levels that must not be confused, because AnzarSeha's role differs between them.
| Level | Data | AnzarSeha's role |
|---|---|---|
| The public site | Visitors, contact form | Data controller |
| The Service | Clinician accounts, a study's patient data | Processor, on behalf of the client institution |
Data collected on the site
On the public pages, AnzarSeha collects:
- Contact form — name, email address, organisation (optional) and message. Purpose: to respond to your request. Legal basis: your consent and the legitimate interest in handling an enquiry. These messages are delivered by email via Brevo to the service's inbox; they are not stored in an application database.
- Technical logs — the hosting servers keep access logs (IP address, timestamp, page requested) for security and proper operation, for a limited period.
The site contains no advertising network and no behavioural tracker.
Account data
Opening a clinician account requires a professional email address, a password and a display name. Authentication is handled by Supabase's identity service; passwords are never stored in clear text by AnzarSeha.
An account only accesses records after approval by an administrator of the institution. This data serves to identify the user, secure access and maintain the action log.
Health data and patient data
Data entered or imported into a study may constitute health data, a special category of sensitive data. For this data, AnzarSeha acts as a processor; the data controller is the client institution.
- AnzarSeha processes this data only on the controller's instructions and for the purposes of the study.
- Data is partitioned by study using row-level security closed by default; the browser holds no access key.
- Using health data in Morocco requires the prior authorisation of the CNDP, which falls to the data controller. AnzarSeha provides the technical means (traceability, security, export) needed for their compliance, without substituting for them.
AI-assisted processing
Some extraction features may call on an artificial-intelligence model. This processing is bound by strict safeguards:
- Prior pseudonymisation — direct identifiers (name, record number, contact details) are removed from the text before any transmission to an external model.
- Consent gate — no call to an external model occurs without an explicit decision recorded in the log; otherwise, only the internal rules engine runs.
- No automatic final value — a value proposed by a model is discarded if it does not cite its source in the document; it is retained only after human validation.
- No training — the data transmitted is not used to train the providers' models, subject to those providers' contractual commitments.
Sub-processors and recipients
AnzarSeha uses sub-processors, chosen for their security guarantees. Data is neither sold, rented, nor disclosed to third parties for commercial purposes.
| Sub-processor | Role | Location |
|---|---|---|
| Supabase | Database, file storage, authentication | European Union |
| Vercel | Hosting of the site and application | United States / global network |
| Brevo (Sendinblue) | Transactional and contact emails | European Union (France) |
| Cloudflare | DNS, edge security | Global network |
| Google (Gemini) / Anthropic | Assisted extraction — on pseudonymised text only | Outside the European Union (depending on provider) |
Transfers outside Morocco
Some sub-processors are located outside Morocco. These transfers are covered by appropriate safeguards (standard contractual clauses, security commitments). Patient data resides on European Union infrastructure; only pseudonymised extracts may, with consent, be sent to an AI model outside the EU.
Retention periods
- Contact messages — kept for as long as needed to handle the request, then archived or deleted.
- Accounts — kept for the duration of the relationship, then deleted or anonymised.
- Study data — kept according to the controller's instructions; returned or deleted at the end of the contract (see the Data Processing Agreement).
- Audit logs — kept to guarantee integrity and traceability, for as long as necessary for that purpose.
Security
AnzarSeha implements technical and organisational measures suited to the sensitivity of the data:
- encryption of communications (HTTPS) and encryption at rest provided by the infrastructure;
- row-level security closed by default: public keys grant access to no data, the application API is the only door in;
- hash-chained audit log: any change to a past entry breaks the chain detectably;
- email authentication, account approval by an administrator, no key on the browser side;
- pseudonymisation before any call to an external model.
Your rights
In accordance with Law No. 09-08 and, where applicable, the General Data Protection Regulation, you have the rights of access, rectification, objection, erasure and restriction, as well as the right to portability.
- For site and account data: write to [email protected].
- For a study's patient data: these rights are exercised with the institution acting as data controller; AnzarSeha assists it technically in responding.
Cookies
The public site uses no advertising-tracking cookie. The application uses cookies strictly necessary to open and maintain a secure session (functional session cookies), without which sign-in cannot work.
Contact and complaints
Point of contact for any question or request relating to personal-data protection — including the exercise of your rights: [email protected]. As the publisher is a natural person, no data protection officer (DPO) is appointed; this address is the single point of contact.
You may lodge a complaint with the CNDP (National Commission for the Control of Personal Data Protection, Morocco) and, where applicable, with the competent supervisory authority within the European Union.