What we store, and who sees it.
Zafari Academy hosts other people’s academies. Most of what is stored belongs to a teacher and their students, and each academy is kept apart from every other.
Who decides
Zafari Academy is run by Zafari Academy LLP.
- Inside an academy, the academy decides what it asks you and what it does with your learning: your progress, answers, homework, questions and attendance. It is in charge of that information, and we handle it for them. Ask the academy first; we will help it answer.
- For your account and this website, we decide: your sign-in, security records, what teachers buy from us and how visitors find us.
- At our own academy, where we teach free courses, we decide, as any academy does for its own.
What we collect
- Your account: name, e-mail address, a salted hash of your password (never the password), whether your address is confirmed, and your Google account id if you sign in with Google.
- Only if an academy asks: your date of birth and countries, kept for that academy alone; and whether you are a man or a woman, if an academy that teaches them separately asks. That answer is kept on your account, so other academies that teach them separately use the same one. You can change these on your account page.
- Your learning: steps finished, assessment answers and scores, time spent on hosted videos, flashcard reviews, your study plan and streak if you set them, and time in live classes.
- What you write or send: questions to teachers and replies, homework, ratings, applications and “I’ve paid” notes, requests for an academy’s downloads, messages to the study assistant, problem reports, and account recovery requests (your name, old and new e-mail address and your message). A problem report can carry a screenshot and details of your browser, screen, connection, time zone and the page you were on.
- If you teach: your teaching profile, photo and credentials, your academy’s details and content, and a log of what the studio assistant read and proposed for you.
- Your device: your time zone, and if you switch on notifications, the address your browser gives for them. Sign-in limits keep a hash of your e-mail address or network address for about a day. Our hosting keeps request logs (your IP address, browser and the page asked for) for security and finding faults.
- Which link brought you: visitors to our own pages are counted with no name attached. If you then make an account, apply to a course or open a free lesson, the link that brought you is kept with it, and the academy sees which link brought its applicants and preview visitors.
We hold no card or bank details. Students pay their academy directly.
Why we use it
Each use, and what makes it lawful:
- To run the service you asked for (our contract with you): your account, your courses, your academy.
- To keep it safe (our legitimate interest in a safe service): sign-in limits, security records, request logs, stopping abuse.
- To improve it (our legitimate interest): counting how visitors find us and where set-up gets stuck.
- With your consent: notifications, reminder e-mails and streaks. You can withdraw it at any time with the switch or the stop link in the e-mail; that does not undo what was done before.
- When the law requires it (a legal obligation).
We do not sell personal information, we do not show advertising, and we make no decisions about you by automated means alone.
Who can see it
- The academy’s team sees your name and e-mail address, the details it asked for, and what you do there: progress, answers, homework, your questions, problem reports, attendance, whether you are keeping your study plan, your ratings (with your name), what you downloaded and which link brought you. Your study-assistant chats can be read by the academy. The team can download attendance and progress lists.
- Other academies see nothing of it. Separation is enforced in the database itself, not by each page remembering to filter.
- Other students do not see your questions or answers. In a live class, the others in the class see your name, anything you share by camera, microphone or chat, and when you raise your hand.
- A few of our staff can reach academy data, only to give support, keep the service safe, or when the law requires.
- Anyone can see a teacher’s card and credentials on the academy’s pages, a certificate (your name, the course, the academy, the date and its number) if they have its link, and a rating’s words with your first name only, once the teacher chooses to show it.
- If you teach: until you set a contact address in Settings, replies to your academy’s mail go to your own e-mail address, which your students then see. The contact address and WhatsApp number you publish are public.
Services we use
These handle information for us. Each applies only where the feature is used.
- Google Cloud (USA): hosting and the database, for everything.
- Google Vertex AI: the study assistant, the teacher’s assistant (which can read the academy’s student list to answer a teacher), building courses and labs from a teacher’s material, and turning recordings into captions, readings and questions.
- Google sign-in, if you choose it.
- Google reCAPTCHA, on sign-in and sign-up pages, to tell people from scripts. Google’s own privacy terms apply to it.
- Bunny.net: storing and playing hosted video and audio. Your browser loads the player from them.
- Resend: sending e-mail.
- Your browser’s push service (Google, Apple or Mozilla), if you switch on notifications.
- Our live-class server on DigitalOcean, in Frankfurt, Germany: passes camera, microphone and screen between people in a class as it happens. Nothing is recorded.
- Zafari AI: writes course material from what a teacher gives it. It receives no student information.
- jsDelivr: your browser downloads Python from it for coding steps.
- YouTube and Vimeo: when a teacher uses their videos, the preview picture loads from them, and their player only after you press play.
AI apps a teacher connects. If an academy’s owner switches on AI connections, a member of its team may connect an AI app they choose (such as Claude or ChatGPT) to read the academy. That app can read its courses, progress, and students’ first names. It never receives e-mail addresses, answer keys or what an applicant wrote, and it cannot change anything. What it reads goes to that app’s company under its own terms, and the academy chose it. Off unless the academy switches it on.
Payment pages belong to each academy’s own payment provider, and that provider’s policy applies. The same goes for a class on the teacher’s own Zoom, Meet or Teams link, and for audio or video the teacher hosts elsewhere.
Where it is stored
Our database is in the United States (Google Cloud, us-central1). Some services we use process information elsewhere, including Bunny.net for video and Google AI services that may run outside the US. Live classes pass through our server in Frankfurt, Germany. If you are elsewhere, this means your information leaves your country.
How long we keep it
- Your account and your learning are kept while your account and the academy exist.
- Sign-in limits are cleared about a day later. Reset and confirmation links expire within a day; invitations within the time shown on them.
- Leaving a course you have not finished removes your place, your step progress, your assessment attempts and your homework in it. Your questions, assistant chats and attendance stay with the academy. Ask us to remove those too. A finished or mandatory course cannot be left.
- A security record of who did what, and when, is kept after an account is removed. It can hold an e-mail address.
- The record of what a connected AI app asked for (which tool, when, how many rows) is kept for 90 days. It never holds what the app read.
- Deleted information can stay in our database backups until they roll over.
Your rights
You can ask to see, correct, delete or take a copy of your information, or object to how we use it. You can change your e-mail address and the details an academy asked for on your account page. For anything else, follow the steps on our Contact page. You can also ask us to limit how we use it, or withdraw a consent you gave. There is no delete or download button yet, so we do it for you. We may need to check it is you. We answer within one month, or longer where the law allows for a complex request, and then we tell you why.
For your learning at an academy, ask the academy too: it decides. You can also complain to the data protection authority where you live.
Children
Academies may teach children. A learner under 13, or under the age of consent where they live if that is higher, may use an academy only with a parent’s or school’s permission; in India, anyone under 18 needs a parent’s verifiable consent. A parent may make the account for their child, with the parent’s own e-mail address, and acts for the child. The academy is responsible for getting that permission.
Cookies and your device
We set no advertising cookies and use no third-party pixels. Our own cookies:
- lms_session: keeps you signed in, for 7 days.
- lms_oauth_state and lms_handoff: protect signing in with Google and moving between an academy’s addresses, for minutes.
- za_src and za_v: remember which link brought you, for 30 and 180 days. They hold only the source, such as “linkedin”.
- build_full: remembers full-screen building for teachers, for a year.
Reading size, theme, drafts and lab work are kept in your browser and never sent to us. Google reCAPTCHA may set its own cookies on sign-in pages, and so may the video players (Bunny.net, and YouTube or Vimeo once you press play).
Keeping it safe
- Each academy’s data is walled off in the database with row-level security.
- Passwords are stored as salted hashes, and sign-in links as hashes.
- Assessment answers stay on the server until a learner’s own answer is fixed.
- Video and audio hosted with us play through short-lived signed links.
- Everything travels over encrypted connections.
If a breach puts your information at risk, we tell the regulator and you as the law requires.
Changes
If we change this page in a way that matters, we will post the change here, with its date, before it takes effect, and tell account holders where we can.
Contact
Questions about privacy? Please follow the steps on our Contact page.
Last updated 10 November 2026.