Privacy Policy
Scope and contact
Taj Alwaqar Academy Administration — Amman, Jordan. Support, privacy and account deletion requests: support@tajalwaqar.app. Updated: 15 October 2026. This policy covers the app and website. App emails are sent from no-reply@tajalwaqar.app; send requests to the support address; the automated sender does not receive support requests.
Guardians and independent students
Guardians provide a full or familiar name, email, sign-in information, required phone number, country and time zone. Independent students aged 18 or older provide name, gender, full date of birth, email, sign-in details, phone, country, time zone and an optional learning-level note. A full date of birth is required. The server rejects independent registration for anyone who has not reached their 18th birthday; younger students are added through a guardian account.
Adult declaration
When creating a guardian or teacher account, the account holder expressly declares that they are aged 18 or older. The declaration, its time and its source are recorded on the server in an internal database record that the app cannot read and that is not displayed to users. This is a self-declaration, not identity verification; we do not request identity documents for this declaration.
Minor students and teachers
Guardians create student profiles, including profiles for minor students under 13, with name, gender, birth date and an optional photo, using the guardian’s time zone. This information supports lessons, progress and educational communications. Minor students are not asked for email, phone, password or Google sign-in; devices pair with a single-use code valid for 30 minutes. We also process device identifiers, sign-in events and lesson and communication data as described in this policy. Teacher applications include identity, contact, country, time zone, subjects, languages, experience and biography, plus review decision, date and reason. Teachers upload no documents and use a fixed image based on gender.
Google sign-in
We request only basic identity scopes: openid, email and profile. We receive email and its verification status, name, image URL and Google account identifier for authentication and account creation or linking. Email becomes the account email and the suggested name can be edited. The Google image is not used or copied into the app profile. Supabase stores identity data in the linked authentication record in Frankfurt; name and email are transferred to the app profile. We request no Gmail, contacts, files or calendar access. Google data is not sold, used for advertising or shared beyond operating the service.
Linking and revoking Google access
New users choose a role, complete details and accept privacy and service terms before use. If you sign in with Google but do not complete account creation, or your email is not registered with us, an incomplete record containing your email, name, Google identifier and image URL remains; we use it only to complete account creation if you return, and you can contact support about that record through the deletion-request page; submitting a request does not mean the record has been deleted. If your verified Google email matches an existing Taj Alwaqar account, Google is linked automatically to that same account as an additional sign-in method, and we send an in-app notification and an email; if this was not you, contact support immediately. Revoking permission in Google settings stops that sign-in method without deleting the Taj Alwaqar account. A password can be created under My information for email sign-in. Minor students cannot use Google sign-in.
Learning and certificates
We process schedules, lesson status, attendance, recitation, assessments, teacher notes, assignments, monthly reports, private teacher notes for administration and supervision reports. Certificate PDFs contain student name, program, achievement, date and certificate number. They reach the guardian or independent student in a conversation and by email through a link valid for 30 days, and a copy reaches a student who signs in with a device code in their own «Certificates» conversation, without email. Link expiry does not delete the certificate.
Messages and attachments
We store text, sender, read time, images and PDFs up to 5 MB. Sent messages cannot be edited or deleted within the conversation; contact support about data or concerning content. Students cannot message one another. Administration reads conversations and supervisors read those within their scope. Message notifications for non-student accounts may include the sender’s name and a preview of up to 80 characters, which may appear on the device screen depending on notification settings; student notifications do not include a message-text preview.
Payments
Transfers take place outside the app. We store amount, currency, method, reference, review status, reviewer note and receipt image. The app does not collect or store card credentials as an in-app payment method. Receipts may include financial information; provide only what is needed to verify a transfer and do not send full card numbers or security codes.
Live lessons
Lessons use audio and optional video through Agora without recording or room chat. We store who joins and entry and exit times. Guardians and supervisors may observe with their presence visible. For Zoom or other external links, we store the link, access code and when staff open it; the external provider’s policy applies.
Devices, location and permissions
We process notification tokens, operating system, a random installation ID and app version. A student’s device name, model, operating-system version and last-seen time are shown to the guardian. Country is first inferred from the SIM; if unavailable, an optional one-time location permission is requested during adult and teacher registration only, and your device's operating-system geocoding service (such as Google on Android) converts the location to a country code; only the country code reaches our servers. Coordinates are not stored and location is not tracked. Audio, camera and image permissions support selected features and can be managed in device settings.
Purposes and audit records
Data supports accounts, authentication, scheduling, lessons, progress, reports, certificates, communication, transfer review, subscriptions, alerts, security and troubleshooting. Account, payment, subscription, lesson and consent changes are logged with the actor and before-and-after data. Terms and privacy acceptance includes version and time. We use no behavioural usage analytics, advertising or advertising IDs, and data is not sold or shared for marketing; we only measure release stability as described under Crash reports.
Access permissions
Guardians see their own and their minor students’s data, devices and attendance; teachers see student data connected to their teaching work; supervisors see assigned users and conversations without payment receipts or writing in student conversations. Administration accesses operational data including conversations and receipts. Minor students see their learning and communicate with teachers and the Taj Alwaqar team through available permissions, without payment access. Former teachers can no longer access the student’s conversations. A student may receive a certificate in a private conversation that is not shown among the guardian’s conversations; do not assume all student conversations are visible to the guardian. App screens show users’ email addresses and phone numbers only to academy staff (administration and supervisors) for operations and support. The web supervisor dashboard shows read-only operational data without message content.
Providers and international access
Supabase provides authentication, databases and files in Frankfurt, Germany; Google provides sign-in and Android notification delivery, and converts location to a country code when the location permission is used; Expo provides notifications and updates; Agora provides audio/video; Sentry provides crash reporting; Titan Email through Hostinger provides email; Hostinger hosts the website and dashboard. Notification services receive tokens, titles and text; email services receive recipient addresses and message content. Providers, teachers and administrators may work outside your country and the EU. Frankfurt database hosting does not mean all processing stays there. A teacher or administration may add a lesson link to an external meeting service (such as Zoom); when opened, the lesson takes place on that service, which may process display name, voice, video and device data under its own policy, including when minor students attend. Transfer services, WhatsApp and Telegram are chosen by users themselves and have their own policies.
Crash reports
The public release uses Sentry for crash reporting, stability and troubleshooting. Reports may include device and release information, technical context and identifiers, and the provider may process IP addresses. Filtering is applied to some JavaScript reports, but this does not establish removal of all personal information from native events or the provider’s processing. We do not describe all reports as anonymous or confirm a processing region or provider retention period before its settings are established.
Retention and expiring links
In-app notifications are automatically deleted after 180 days, notification-delivery and sent or failed email records after 30 days, and student sign-in attempts after one day. Pairing codes are single-use and valid for 30 minutes; certificate links last 30 days. These periods concern specific records or links, not general account or certificate deletion. There is currently no automatic inactive-account deletion. Account deletion requests follow the stages, retained categories and periods explained in the deletion and retention sections below.
Security records
Our authentication provider stores the IP address and device or browser type with each sign-in session and may keep short-lived technical logs. Student device-code sign-in attempts are stored with the IP address and a device identifier for one day to prevent guessing. We log security events such as password, sign-in email or sign-in method changes and notify you in the app and by email. Audit records may include a copy of your data (such as name, email and phone) before and after a change.
Account and data deletion
Account deletion is active. Request it in the app through My Account → Help and Support → Delete Account, or through the website’s deletion-request page. A 6-digit code is sent by email for confirmation, and the account is immediately frozen and sign-in is blocked. Administration reviews the request, then completes deletion within 30 days, with a maximum of 60 days. Uninstalling the app or revoking Google sign-in does not submit a Taj Alwaqar account deletion request. Deletion removes the name, email, phone number, password, sign-in methods including Google, and sessions. It also removes the guardian’s linked student accounts and their devices, profile images, message attachments and certificates. The deleted account holder’s name and text are removed from other users’ notifications, and upcoming lessons and open subscriptions are cancelled. The retained categories are explained below.
Payment records and transfer receipts
Payment records—amount, currency, date and status—and transfer-receipt images are retained for accounting and fraud prevention, separated from the account. Administration deletes receipt images manually. A receipt image may contain the payer’s name as shown by the bank; separation from the account does not make the image anonymous. Administration’s payment notifications are automatically deleted after 180 days.
Other records and backups
Past lessons remain in the records without a name, and the text of a previously reported message is retained as security evidence. The deletion-operation record is kept for two years without personal data. The final “Your account has been deleted” email is removed from the sent mailbox after 30 days. Backups are deleted after 90 days.
Consent records after account deletion
After account deletion, some consent records may remain to document the recorded consent and the document accepted. These records include the record ID, user ID, consent type and status, document version, consent time, and student ID where present. These identifiers remain linked to the record. The IP address is removed from consent records registered under the account holder and linked accounts included in the deletion; removing the IP address alone does not anonymize all data. The current documentation does not establish an implemented final retention period or automatic expiry mechanism for this category. The two-year period for the deletion-operation record does not automatically apply to consent records. The adult-declaration record, including the internal account identifier, declaration time and source, and the messaging-consent record, including the relevant internal identifiers, consent time and text version, also remain after account deletion. These records remain linked to an internal identifier for the deleted account and do not contain the name, email or phone number; this does not make them fully anonymous. They are retained to document the recorded declaration and consent. No retention period has yet been approved for these two categories, and the two-year period for the deletion-operation record does not automatically apply to them.
Guardian supervision
Guardians create profiles for students who are minors and manage their data and devices through My children. A minor student cannot pay, view payments, cancel lessons or change identity details. When adding a student, the guardian expressly consents to processing under this policy; we record the policy version and consent time. Messaging from a student account accessed through a pairing code is off by default. The student can message teachers only after the guardian expressly accepts a specific consent text in the app; the server records the consent time, the consenting guardian and the text version. Sending images and files is off until the guardian allows it. The guardian can turn messaging off at any time and view the student’s conversations with teachers. The student, teacher or anyone other than the authorized guardian cannot change these settings. Younger students receive a safety reminder before messaging, and messaging rules must be accepted before the first message. Students should not share phone numbers, addresses, passwords or sensitive information in messages. Guardians can contact support about their students’ data or request access, correction, withdrawal of consent or deletion.
Reporting and blocking in messaging
Users can report any message or user and block any person, including members of administration and supervisors, in one-to-one conversations between a teacher and a student or their family. Official communication channels with academy administration remain open for support and complaints and are not disabled by blocking. Messaging and acceptable-content rules continue to apply, and support remains available for abuse or data concerns.
Website and security
The informational website creates no accounts, accepts no payments and adds no analytics, advertising or tracking tools; it also hosts authentication-support pages for password reset, email verification and opening the app for guardian-code recovery. The password reset page sends your new password directly to the authentication service (Supabase) and does not store it, and its code library is loaded from the jsDelivr network, which sees the visitor's IP address. Hosting may process technical request logs for operation and security. App and website connections to our servers use HTTPS; Agora carries live-lesson audio and video over its own network; passwords are not stored as readable text. Images, receipts, attachments and certificates are private and accessed through temporary links. Sensitive operations are logged. Security cannot be guaranteed absolutely.
Requests and updates
Available fields can be edited under My information; guardians edit student details. Contact the support team through the Help and Support page for copies, correction, deletion, objections or withdrawal of consent. Ownership may require verification without a password. This policy does not restrict legal rights or complaints to a competent authority. We update it when practices change and obtain required consent where applicable.
Account recovery
If you forget your password, we email a link to your registered address that opens the reset page on tajalwaqar.app. Your sign-in email cannot be changed in the app; administration changes it at your request after verification and notifies both the old and new addresses. Google users can create a password under My information. A student who signs in with a device code needs a new pairing code from their guardian; pairing a new device revokes the old one.