Privacy policy
How Tdriss handles the data needed to operate its web and mobile clients.
Authentication, database, and file storage use Supabase.
Required transaction data is sent when you choose to buy.
Support messages are tied to your account to prevent impersonation.
Didit processes the document and, when required, biometric data after your consent.
- Account and profile data.
- Purchase, entitlement, and progress records.
- Chat, support messages, and files you submit.
- Security and operational logs needed to prevent abuse and diagnose failures.
- Authentication and delivery of purchased content.
- Payment, settlement, and refund processing.
- Content moderation and fraud prevention.
- Support and service reliability.
We do not sell personal data. We share only what is necessary with Supabase, Chargily, and infrastructure providers to deliver the service or meet a legal obligation.
After your consent, Didit acts as the verification processor for your identity card and may process biometric data required by the selected workflow. Tdriss uses the approved result to assign a male or female learning environment and guide each user to the environment appropriate for them.
- Tdriss does not store the document image, document number, face image, or raw Didit payload.
- We retain the verification status, document-workflow kind, verified gender, consent time, and decision time.
- Separated learning environments rely only on the identity-card workflow; birth certificates are not accepted for this decision.
Financial and security records are retained as required for operational and legal obligations.
- Request access to or correction of your data.
- Report unauthorized access promptly.
- Never share your password or session token.