Privacy Policy
Version 1.9 · Effective 12 October 2026
Applies to tutors, to parents, guardians, adult learners and students using the Client Portal, and to visitors to tutello.ae.
1. Controller and contact
HCIT DIGITAL AND AI CONSULTING, Economic Licence CN-6345766, Abu Dhabi, United Arab Emirates, operates tutello.ae. Privacy enquiries and data subject requests should be addressed to support@tutello.ae.
No Data Protection Officer has been appointed, none being required by the scale or nature of the processing.
2. Roles
In respect of tutor account data and Portal User account data, the Operator acts as controller.
In respect of personal data entered by a tutor concerning that tutor's clients, the tutor acts as controller and the Operator acts as processor. A parent, guardian, adult learner or student seeking correction or erasure of such data should contact their tutor in the first instance.
The Operator also acts as controller when it keeps the register of parents' and guardians' mobile numbers described in clause 3.8, when it uses telephone numbers recorded by tutors to match an invitation to an existing Portal User account, to keep one Portal User account for each mobile number or to offer an account the families that record its number, under clause 3.8, and when it administers accounts under clause 9.4.
3. Categories of personal data processed
Tutor account data: name, email address and profile image, obtained from federated sign-in or provided by the tutor; telephone number, business name and address where provided; currency, timezone, default rate and cancellation-window settings; the other usual settings the tutor chooses, such as work days and hours, the usual session length, whether a late cancellation is charged, the usual payment method, how many days after its date an invoice is due, how new families are invoiced, whether new session notes start private or shared and how parents are invited; how far the tutor has gone through the set-up; report card settings, and the date on which the tutor confirmed the report cards notice described in clause 4.2; subscription status and payment-provider identifiers; where the tutor connects a calendar, the connection data described in clause 6.3; and the sign-in data described in clause 3.7.
Client personal data entered by tutors: family and contact names; email addresses and telephone numbers; addresses where provided; student names, education levels (such as a school curriculum and year, with any exam and exam board, a university year, or adult learner), subjects and applicable rates; session dates, durations, statuses and notes, whether a session is marked as held online, and which students share a session (clause 3.11); where a tutor uses report cards, the records described in clause 3.10; invoices, amounts and payment records.
Portal User data: the email address by which an invitation was accepted; the name and profile image obtained from federated sign-in, or the name the Portal User gives in their profile; the mobile number the Portal User gives when accepting an invitation, and whether it is the reference of their account under clause 3.8; the association between that account and the relevant tutor, family or student; the invitations addressed to that account and the answers given to them; for each tutor whose records the account can view, the date on which the Portal User last opened that tutor's part of the Client Portal, which that tutor is shown; which report cards the Portal User has opened, used only to mark the report cards that are new to them and never shown to a tutor; and the sign-in data described in clause 3.7.
Technical data: server logs comprising network address, user agent, timestamp and requested path; short-lived rate-limiting records; records of wrong password attempts, which hold a keyed hash of the network address rather than the address; authentication cookies; and records of acceptance of the Terms of Service or Portal Terms.
The Operator uses Vercel Web Analytics to measure aggregate use of tutello.ae. It records page views and derived technical attributes only; it sets no cookie and no identifier on the visitor's device, does not follow visitors across other websites, and is not capable of identifying an individual visitor. No advertising or behavioural tracking technologies are deployed, and no personal data entered by a tutor is passed to it.
Support and feedback data: the content of messages sent to support@tutello.ae and of feature requests submitted within the Service (including a tutor's report that a topic list is wrong, which carries the list's name and version and the tutor's words, never anything about a student), the account from which they were sent and the time of sending, and notes recorded by the Operator when handling support and administration of an account.
Sign-in data: for each email address used to sign in, a record that may comprise a session counter used to sign the account out on every device, the date the address was verified, the date and method of the most recent sign-in, counts of wrong passwords and the times of any resulting lock, and, where the account holder chooses to set one, a password, held only as a salted one-way hash, together with the date it was last changed. Where a federated sign-in account is linked, the Operator also holds the provider's identifier for that account and the tokens the provider issued when it was linked. Records of sign-in, sign-up confirmation and password-reset links sent by email hold the email address, what the link is for and its times, and only a hash of the link itself; the record of a sign-up confirmation link may also hold the pending sign-up of clause 3.9 and a count of wrong passwords tried with it.
Parent account checks and invitations: a tutor may check whether a telephone number or email address belongs to an existing Portal User account that can be invited, and may invite an account it finds. A telephone number is matched only where a tutor has recorded it for a family or student to which that account holds access. The Operator keeps a register of the mobile numbers tutors record for the contacts of their families, each with a reference to the family that recorded it and, once a Portal User's account holds it, to that account; the register holds no name, email address or child's details, and a number leaves it when no family records it and no account holds it. A tutor who enters a mobile number is told only whether it is in that register through another tutor's family or an account, never which one, except the name shown on an account found as described above in this clause 3.8, and each answer counts as one of the tutor's checks. A number can be the reference of one Portal User account only, and can become it only once the record of a family to which that account holds access, or which the invitation being accepted relates to, lists the number the Portal User gave; a person accepting an invitation who gives a number that is already another account's reference, where the record the invitation relates to lists it, is asked to sign in with that account or to give their own number, and is told nothing else about that account. When an account's reference is a number another tutor has recorded for the contact of one of its families, the Portal User may be shown that tutor's business name with an offer to join that family, and receives access only if they accept and that tutor confirms it is them; until the Portal User accepts, that tutor is told nothing about the offer. The Operator may release a number from an account, or correct an account's mobile number, at the account holder's request or to resolve a dispute over a number, under clause 9.4. Where a tutor answers that the person who accepted an invitation sent to an account found by telephone number was not the person they meant, that answer is kept with the number the tutor entered, and that account is not matched to that number again for any tutor. The tutor learns only whether an account was found and, where it was, the name shown on that account, never its email address or telephone number; or, where that account already has access to one of the tutor's own families or has a pending invitation from that tutor, may be shown which family that is instead. If the tutor then adds the family with an invitation to that account, that name is recorded as the family's contact name and, where the tutor gave the family no name, the family is named after the surname in the Portal User's name when that Portal User receives access to it. Checks are limited in number and recorded with the tutor, the kind of check, its outcome and a keyed hash of the number or address, never the number or address itself. On acceptance of an invitation created when a tutor adds a family after such a check, the Portal User's name, mobile number and email address are shared with the tutor and fill empty contact details of that family record; details filled in this way, and a contact name recorded from the check, are removed from the record when that Portal User's access to the family is removed, unless the tutor has changed them since. A contact name recorded from the check is also removed if the Portal User declines the invitation or withdraws their acceptance, or if the tutor answers that it was not them, or if the tutor or the Operator cancels the invitation, unless the tutor has changed it since. Where the account was found by telephone number, the name and email address are shared when the Portal User accepts, so that the tutor can confirm who accepted, and the name is removed from the invitation if the Portal User withdraws, if the tutor answers that it was not them, or if the invitation is cancelled. Where a Portal User has access to a family as a parent or guardian and the tutor's record of that family lists the Portal User's email address for its contact or its second contact, a change of the Portal User's own name, made in the Client Portal or in a tutor account with the same email address, also changes that contact's name in the record; when that Portal User's access to the family is removed, the family's contact name goes back to the name the record held before, unless the tutor has changed it since.
Sign-up requests: where an email address is entered at sign-up and the Operator's sending limits allow it, a confirmation email is sent to it, and the address and the chosen password, held only as a salted one-way hash, are kept as a pending sign-up until confirmed. An unconfirmed sign-up is deleted within one day after its confirmation link expires, and the record of the link itself (clause 3.7) is kept for the period set out in clause 7. Where the address already belongs to an account, a security notice is sent to it instead.
Progress records and report cards: where a tutor turns report cards on for a student: a topic list for each of the student's subjects, and the topics marked as covered before; for each session, the topics covered and, where the tutor records them, the student's level in each topic, chosen from four words (Just started, Making progress, Confident and Beyond the goal), whether homework was done, and test scores (the name and type of each test, the marks or grade, and a short note); for each subject, the exam the student is preparing for and a target grade; test scores and school results, such as a mock exam grade, that the tutor adds outside a session; whether the student's own portal account shows their report cards; and report cards, which hold the tutor's words with a summary the Service prepares from these records and the student's sessions, and every version the tutor publishes, with the date it was published and the family it was published to, or that the student was billed directly. Where a tutor leaves report cards off for a student, none of these is recorded about that student.
Sessions with several students: where a tutor records one session for several students, the Service records a separate session for each student, with that student's own time, price, status, notes and progress, and links those sessions together. A Portal User is shown only the sessions of the students to which their access relates, and nothing about another student in that session, save a note that the tutor writes for the whole session and marks as shared: that note is shown, as the tutor wrote it, to the Portal Users of every student in the session, and the Service warns the tutor when it names another student in it. A session note that the tutor marks as shared to invoice, whether the session has one student or several, is shown to Portal Users as a shared note is, and is also printed on the invoice of each student's own family, or of a student who is billed directly, under that student's own session only: on the invoice page, on its PDF, including a PDF attached to an invoice email that the tutor sends or has sent automatically, and on the invoice in the Client Portal. Invoices are shown in the Client Portal only to parents and guardians and to a student who is billed directly, never to a student's portal account linked to a family. No note is printed on an invoice that the tutor lists as one total. The note is read from the session each time the invoice is opened or its PDF is made, so a later change by the tutor changes what is printed from then on. Invoices and report cards count each student's own time.
4. Personal data relating to minors
The Service is used to record tutoring provided to students who may be minors. The Operator does not knowingly collect personal data directly from a child, other than the account and sign-in details a student gives when using a portal account, the date they last opened the Client Portal and which report cards they opened (clauses 3.3 and 3.7). Student portal accounts exist only where created at a tutor's instruction and are limited to scheduling information, notes marked as shared and, unless the tutor turns this off, the report cards the tutor publishes about that student, together with the student's own account details.
The tutor is responsible for obtaining any parental or guardian consent required for the recording of a minor's personal data, including progress records, and for the publication of report cards. Before a tutor first turns report cards on, the Service asks the tutor to confirm that they are responsible for any consent this needs, and records the date of that confirmation. Where a tutor connects a calendar under clause 6.3, the provider of that calendar receives students' first names and subjects, which may be those of minors, at the tutor's direction, and the tutor is responsible, as controller, for any consent or notice this needs.
Client personal data is not used for product analytics, for marketing, or for the training of machine-learning or artificial-intelligence models, in any circumstances.
Where the Operator is notified that a minor's personal data is held without a lawful basis, it shall act with the relevant tutor to procure its erasure.
Progress records and report cards are written by the tutor, who decides what to record and whether to publish it. A progress record is seen by the tutor alone until it appears in a report card the tutor publishes. The Service prepares a draft report card only from the tutor's own records. The Operator does not write, check or change report cards and does not use artificial intelligence to write them, and the Service gives no grade or rating of its own and makes no automated decision about a student. A report card is shown in the Client Portal only after the tutor publishes it, and only in the version published most recently: to the parents and guardians of the family the student belonged to when that version was published, while the student remains in that family; to the student's own portal account linked to that family, on the same conditions, unless the tutor turns this off; and, for a version published while the student was billed directly rather than through a family, to the student's own portal account while the student is still billed directly. The Service puts no fees, rates, balances, invoices or payments on a report card. The Operator sends report cards to no one. A report card the tutor shares outside the Service, as a link, a PDF or a picture, is shared by the tutor; a PDF or picture of a report card is made each time it is requested and is not stored. The tutor can unpublish a report card at any time, delete a report card that is not published, with every version of it, and delete all of a student's progress records and report cards at once. Removing a student also deletes their topic lists. Progress records and report cards are not used for product analytics, for marketing, or for the training of machine-learning or artificial-intelligence models.
Subjects and a tutor's comments can reveal a student's religion or health, for example a Quran recitation class or a comment about an illness. The Service never suggests a religious subject, though when a tutor types one it may offer a template for its topics, and it asks tutors to leave health details out of report cards. The tutor decides what to record, as controller. A calendar that the tutor connects under clause 6.3 receives the subject of each session with the student's first name; the tutor decides whether to connect one, as controller.
5. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Provision of the Service and the Client Portal | Performance of a contract |
| Preparing progress records and report cards at a tutor's instruction, showing published report cards in the Client Portal and marking those a Portal User has not yet opened | Performance of a contract |
| Showing a tutor when each of their Portal Users last opened the Client Portal | Legitimate interests |
| Keeping a tutor's own calendar up to date with the tutor's sessions, at the tutor's request, where the tutor connects one (clause 6.3) | Performance of a contract |
| Collection of fees and prevention of fraud | Contract; legitimate interests |
| Service communications, including sign-in links, invitations, account security notices and material notices | Performance of a contract |
| Security, rate limiting and abuse prevention | Legitimate interests |
| Evidence of acceptance of the applicable terms | Legitimate interests; legal obligation |
| Aggregate measurement of site usage | Legitimate interests |
| Responding to support requests, administering accounts and considering feedback on the Service | Legitimate interests |
| Matching an invitation to an existing Portal User account and confirming who accepted it | Legitimate interests |
| Retention of accounting records | Legal obligation |
The Operator does not sell personal data, does not disclose personal data for advertising purposes, and does not use personal data to train artificial-intelligence models.
Any marketing communication shall be sent only with prior consent, which may be withdrawn at any time without affecting service communications.
6. Sub-processors and international transfers
| Sub-processor | Function | Processing location |
|---|---|---|
| Vercel Inc. | Application hosting, serverless execution and aggregate site analytics | European Union (Frankfurt) |
| MongoDB, Inc. (Atlas) | Database hosting | European Union (Frankfurt, eu-central-1) |
| Stripe, Inc. | Payment processing | European Union / United States |
| Plus Five Five, Inc. (Resend) | Transactional email delivery and receipt of email sent to tutello.ae addresses | European Union (Ireland) |
| Google LLC | Federated authentication | United States / global |
Personal data is stored within the European Union, save for the copy of an erased account described in clause 7, which the Operator keeps on its own equipment. Where a sub-processor transfers personal data outside the European Economic Area or the United Arab Emirates, that transfer is made pursuant to recognised safeguards, including the European Commission's Standard Contractual Clauses.
Changes to this list are published on this page not less than thirty (30) days before the additional sub-processor commences processing.
Calendars a tutor connects: where the Operator offers it and a tutor connects a Google or Microsoft calendar account, the Service creates a calendar named Tutello in the tutor's account with that provider and writes the tutor's scheduled and completed sessions to it: each student's first name (and, where two students in one session share a first name, a last initial), the subject and the start and end times. No amount, note, family name, address, telephone number or email address is written, and no one is invited to any event. The provider receives this data at the tutor's direction, as the tutor's own service provider and not as a sub-processor of the Operator; it holds that calendar under its own terms, and may hold it outside the European Union. The Operator stores, for each connection, the provider account's email address and identifier, the permissions the provider granted, the identifiers of the Tutello calendar and of the events it wrote, the titles and times it last wrote, an encrypted credential that allows it to update that calendar, the state of the connection, such as when the calendar was last updated and whether an update failed, and a record of when the tutor connected and of the versions of the notice shown, of the Terms of Service and of this Privacy Policy then in force. The Service never reads any other calendar or event. A tutor can disconnect at any time in Settings, which stops all updates, erases the credential and the other data stored for the connection and, where it still can, asks the provider to end the Service's access and, if the tutor chooses, to delete the Tutello calendar; a calendar that is kept, or that could not be deleted, stays with the provider as it was last written, and the tutor can delete it there. A tutor can also remove the Service's access with the provider, at myaccount.google.com/connections for a Google account, or at account.live.com/consent/Manage or myapps.microsoft.com for a Microsoft account. For a Microsoft account, the permission this feature needs technically allows reading the tutor's other calendar events; the Service does not read them. Tutello's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Retention
| Category | Retention period |
|---|---|
| Active account data | Duration of the account |
| Data following account deletion | Erased from production systems within 30 days; from backups within 90 days, including the copy the Operator makes, before erasing an account, of every record it erases or changes, so that an erasure made in error can be undone. Invoices and payment records entered by the tutor are erased with the account. Records of acceptance, and the Operator's own financial records required for accounting, are kept for the periods in this table; the record of a Founding Lifetime Access purchase or reservation or of a tester code redeemed, and alerts about operational problems that name the account, are also kept |
| Accounts in Read-Only Mode | Not less than 12 months, then deletion on 30 days' notice |
| Portal User accounts | Duration of the account; erased on request where no active membership remains, and when the account of the last tutor whose records it can view is erased, unless its email address also holds a tutor account |
| Register of parents' and guardians' mobile numbers | While a tutor's active family records the number, a Portal User account holds it, or the Operator has released it from an account |
| Offers to join a family | While the account exists; an offer declined, withdrawn or refused by the tutor is reduced after 180 days to a keyed hash that identifies no one, kept so that it is not shown again |
| Progress records, topic lists and report cards, with every published version | Duration of the account, unless the tutor deletes them sooner |
| PDFs and pictures of report cards | Not stored; made each time one is requested |
| The date a Portal User last opened a tutor's part of the Client Portal | While the Portal User has access to that tutor's records |
| Records of which report cards a Portal User has opened | Until the report card or the Portal User account is deleted |
| Calendar connections (clause 6.3) | Until the tutor disconnects or the account is deleted; a credential the provider refuses is erased at once; a connection that is started and not completed is deleted within one day |
| Server logs | Up to 90 days |
| Rate-limiting records and records of wrong password attempts | Automatically expired within one day of the last request |
| Records of acceptance of the applicable terms | Duration of the account plus 5 years |
| Support correspondence, feature requests, administrative notes and records of administrative access | Duration of the account |
| Sign-in data | Duration of the account; where one email address holds both a tutor account and a portal account, until neither remains; where it holds neither, until erased on request |
| Unconfirmed sign-ups | Deleted within one day after the confirmation link expires |
| Sign-up confirmation and password-reset link records | Deleted 7 days after the link expires |
| Email sign-in link records | Deleted when used, or within one day after the link expires |
| Parent account check records | 90 days |
| Financial records required for accounting | 5 years, as required under UAE law |
8. Rights of data subjects
Data subjects may request access to, rectification of, erasure of, restriction of or objection to the processing of their personal data, and may request its transmission in a structured, commonly used, machine-readable format.
Requests should be sent to support@tutello.ae. The Operator shall respond within thirty (30) days, extendable by a further sixty (60) days for complex requests, in which case the requester shall be notified within the initial period.
The Operator shall take reasonable steps to verify the identity of a requester proportionate to the sensitivity of the data concerned.
Tutors may exercise the right to portability at any time, without making a request, by using the export function within the Service. The export includes whether the tutor has set a password, and the dates of email verification, the last password change and the most recent sign-in with its method, but never a password hash, a link, a counter or a lock. The export also includes education levels, topic lists, progress records and test scores, every report card, whether a draft, published, unpublished or skipped, with every published version, and the date each Portal User last opened the Client Portal; a report card the tutor deletes leaves the export. Where a tutor has connected a calendar, the export also includes the provider, the account's email address, when it was connected, the state of the connection and when the calendar was last updated, but never the credential or an identifier of the calendar or of an event.
Where the Operator acts as processor, requests are referred to the relevant tutor as controller, and the Operator shall assist that tutor in responding.
Data subjects in the European Union or United Kingdom may lodge a complaint with their supervisory authority. Data subjects in the United Arab Emirates may lodge a complaint with the UAE Data Office under Federal Decree-Law No. 45 of 2021 concerning the Protection of Personal Data.
9. Security
Personal data is encrypted in transit using TLS and at rest by the Operator's hosting providers or, for the copy described in clause 7, by full-disk encryption on the Operator's own equipment.
Access control is enforced at the data layer: every request is scoped to the authenticated tutor's own records or, in the case of a Portal User, to the specific family or student to which their membership relates. The exceptions are the register and the comparisons described in clauses 3.8 and 9.4, which disclose none of the records compared to any other tutor beyond whether a mobile number is in the register, administrative access under clause 9.4, and data that a tutor directs the Service to write to the tutor's own calendar under clause 6.3.
Authentication is by federated sign-in, by single-use email link or, where offered and chosen by the account holder, by password. A password is stored only as a salted one-way hash, from which it cannot be read. Wrong passwords lead to locks, which end after a set time or, after very many wrong passwords in a row, only once the password is reset, the account holder signs in another way or the Operator lifts the lock; sign-up confirmation and password-reset links are single-use and expire within one hour; and an account holder can sign out of every device.
Administrative access is limited to the owner of the Operator and is exercised only where necessary to operate the Service, to respond to a support request, to investigate a security concern or to act on a tutor's request. The administrative tools show: for tutors, their names, account email addresses, business names, currency and timezone settings, sign-up date and onboarding status, plan, subscription and payment-provider details, and the number of records each holds; for Portal Users, their names, account email addresses, the telephone number each gave, whether a tutor has recorded that number, whether it is the reference of their account and how many times, in the last 30 days since it became so, someone else's acceptance was refused because of it, and may release that reference or correct the account's mobile number, and their acceptance of the Portal Terms; the names of families and students, portal access and invitations; sign-in status, including whether a password or federated sign-in is set up and when the password was last changed, any lock, and the date and method of the most recent sign-in; flags of possible access problems, which the tools work out by comparing the email addresses and telephone numbers of tutor accounts and Portal User accounts with each other, comparing email addresses also with open invitations and with the contact email addresses in tutors' family records, and checking that each portal access still points to an active family or student of the same tutor (for example, a tutor and a Portal User sharing a telephone number, or a student account using a parent's email address); administrative notes; feature requests, with the tutor account that sent each; alerts about operational problems that name a tutor account, such as an email that could not be sent; and the record of administrative actions. They do not show the content of sessions, notes, rates, invoices or payments recorded by tutors, or students' education levels or subjects, topic lists, progress records or report cards, and the Operator does not view any of them unless a tutor asks it to in a support request. For the same purposes the Operator may sign an account out on every device, remove a password, lift a sign-in lock, disconnect a federated sign-in, send a password reset link, cancel an invitation or remove a Portal User's access. Each such action is recorded with the reason given, and opening a Portal User, family or student record, or a list of them, in those tools is recorded, as is each Portal User account named in the flags shown, at most once in any five minutes for the same record, list or account. The tools can also download some of these details as a file, to operate the Service and to send notices about it: for tutors, their names, account email addresses, business names, sign-up dates, plan details and onboarding status; for Portal Users, their names and account email addresses only; and feature requests. Each download is recorded.
No system is entirely secure. In the event of a personal data breach the Operator shall notify affected data subjects and the competent supervisory authority without undue delay and, where required by applicable law, within seventy-two (72) hours of becoming aware of it.
10. Cookies
The Service uses cookies and similar storage in your browser for authentication and security, and to remember choices you make on a device, such as the colour theme, the calendar view you last chose on a phone, whether to show the install button or a banner you closed and, in the Client Portal, which tutor you are viewing. It also keeps in your browser, and nowhere else, the page to go back to from the guide or after resetting a password, and the answers to a form that you have not yet sent. No analytics, advertising or tracking cookies or similar storage are used, and accordingly no consent mechanism is required.
Blocking these cookies will prevent sign-in.
11. Amendments
Amendments are published on this page with a revised effective date and version number. Material amendments are notified by email not less than thirty (30) days in advance.