Privacy Policy

1. About This Policy

This Privacy Policy explains how MAMAKO LLC ("we", "our", "us") handles personal information when you use the MAMAKO website (the "Service"). By using the Service you agree to this policy and to our Terms of Service.

2. Audio and Transcripts from a Live Session

When a teacher starts a live session, the device microphone captures classroom audio. On the teacher’s device, a filter set to the teacher’s speaking level replaces quieter sound with silence before the audio is sent, unless the teacher turns the filter off. It does not run at a staff or department meeting, or when the browser cannot measure the microphone. An automated speech-to-text service turns the audio into text in real time, and the text appears as captions on the teacher’s screen, where the class reads it, and, when the teacher turns on Student Screens, on students’ laptops (below). We do not retain the raw audio. Where a teacher has entered a class roster, MAMAKO stars those names out of the captions and transcript on the teacher’s device, before anything is stored, wherever the transcription recognises them. Accented names are matched by their base letters. Very short names, names written in non-Latin scripts, and names the transcription mishears can still appear, and a teacher can choose to start a session without the roster if it cannot be loaded.

We do not keep a permanent word-for-word record either. The transcript, and a cleaned copy made from it with filler, private remarks, unclear passages and talk that is not part of the lesson taken out, stays available for one week so that the teacher can review it and generate lesson materials from it. No other MAMAKO user can open it. A school that licenses MAMAKO can ask us to shorten that week to as little as one day. After that both are deleted automatically, together with any sentences quoted from them and any caption lines the teacher saved as notes before MAMAKO turned notes off on 2 October 2026. What remains is the lesson summary: the topics covered and how long each took, key points, words from the lesson with definitions and translations, short grammar notes and action items. Cleaning is automatic. It can miss something or remove too much, so the cleaned copy is labelled as not verified, and the teacher can restore any line.

Pages a teacher shares.A teacher can create a link to a lesson page, to a class glossary and to a weekly summary. Nobody needs an account to open any of them, so anyone holding a link can read the page, and the teacher can turn a link off at any time, which takes the page down at once. A lesson page carries the lesson recap and the words from the lesson. Once the teacher shares it, a recap can also show short phrases with their meanings and a few sentences said in class, which are deleted with the transcript. A lesson from before recaps carries its summary and grammar notes and, until the transcript is deleted, a few sentences said in class that the teacher approved. A class glossary carries the words from the class’s lessons with their definitions and translations, grouped by unit and by lesson, with flashcards and quizzes; definitions and translations a lesson did not already have are written automatically. A family update was a short note on what the class learned that week, with the week’s words, written automatically from the teacher’s lesson summaries and approved by the teacher before anyone could read it. Family updates are paused, so teachers cannot write new ones, but the links teachers already shared keep working until the update is deleted. An update names no student, and a translation is made the first time a family opens it in one of the class’s languages. A weekly summary is a tool the teacher uses however they like. For this week or last week, it gives a short overview of the week, then each lesson with its date, a title, its topics, its key points and its key terms with their meanings. We draft it only when the teacher asks, from the unit titles, the titles of the lesson parts (leaving out any part MAMAKO marked as not lesson talk) and the key points in that week’s lesson summaries, and from each lesson’s word list. It never draws on the recap’s paragraphs or on the transcript. MAMAKO removes any line of a draft that names a student on the class roster, refuses an edit that adds a name from the roster, and checks for those names again when the teacher shares the summary. The teacher can edit it, copy it as plain text, print it, and ask us to translate it into any of the class’s languages, one at a time, keeping the key terms in English with the home-language word in brackets. A shared summary shows the English and any translation the teacher made, search engines do not index it, and opening it sends nothing to our AI provider. When the teacher stops sharing it or deletes it, the page comes down at once. That cannot recall text someone already copied or printed from it. None of these pages asks who is reading it, and none carries the roster, audio or anything a student typed. Study progress on a glossary page is kept only in the browser that did the studying and is never sent to us.

Meetings and Parent Conferences

A teacher can also caption a parent meeting, set either to One Family (a parent conference) or to Group (many families at once), or a staff meeting, filed as Staff or Department. MAMAKO keeps each meeting apart from the teacher’s classes, and only the teacher who ran it can open it: no student, parent or colleague account can read it, and no link opens its record. The one exception is the phone captions described below, which show people at the meeting its captions and, for a group parent meeting, a staff meeting or a department meeting, the summary the teacher approved, if the teacher chooses to show it there. The teacher can switch between One Family and Group during the meeting, and what MAMAKO keeps follows the setting the meeting ends with. As with a lesson, we do not retain the raw audio.

During a meeting MAMAKO stores the caption transcript, a record of how caption translation worked in the browser (counts and the browser’s name, with no words in it), and, at a parent conference, the replies the parent speaks into their phone, described below. Names on the teacher’s list of names to hide are starred out on the teacher’s device before any of this is stored, wherever MAMAKO recognises them in English letters. A parent cannot type a reply during a meeting.

Spoken replies at a parent conference.The parent can speak a reply into the phone captions page described below, in English or in the language the captions are translated into. The page shows the microphone only when MAMAKO’s server says a reply can work. The first time a parent taps the microphone on a phone, the page says in their language what is sent and that no recording is kept, and records nothing until they tap Continue; the phone remembers that choice for that meeting code in its browser storage. The phone records only from the parent’s first tap until a moment after the second, and keeps the recording only until MAMAKO confirms it arrived. MAMAKO sends the recording to our speech-to-text provider (section 6) with the setting that keeps it out of the provider’s model training. For a reply in another language than English, MAMAKO then sends the words it heard, with the last few caption lines and replies for context, to our AI provider for an English translation. A reply in English is stored as heard, and nothing about it goes to our AI provider. MAMAKO keeps no audio.It holds the words heard and their English with the meeting while the teacher’s device stars the names to hide out of them, which takes a moment while the teacher’s screen is open, and then stores them with the meeting’s replies. They are deleted with the replies. A reply a parent typed on the conference screen before MAMAKO stopped taking typed replies is deleted the same way. When MAMAKO turns a spoken reply down (for example, because the meeting has taken as many as it can), it logs the reason, never the words, and keeps the latest reason and its time with the phone code, so the teacher’s screen can say why. It is deleted with the code.

Private questions at a group parent meeting.At a parent meeting set to Group, while the teacher takes questions, a parent can type a question on the phone captions page and send it to the teacher who runs the meeting. The parent may add an optional name, or leave the name box blank to ask without one. MAMAKO stores the question as typed, its language (English or the meeting’s caption language, which the parent can choose), the name if the parent gave one, and when it was sent, with the meeting, where only the teacher who ran the meeting can see it. A question never appears on the board, the phone captions, the summary, the phone link or any page anyone else can open. MAMAKO does not star names out of a question. The teacher’s browser translates a question into English; when it cannot, MAMAKO sends the question’s words, never the name, to our AI provider once for an English translation. The teacher can answer a question aloud or reply privately: a private reply is translated on the teacher’s computer, and only the phone that asked can read it, or see whether the question was answered. That phone proves it asked with a secret MAMAKO gave it for that question, which MAMAKO keeps only as a one-way code made from it (a hash). The phone keeps its own questions in its browser storage, and the phone page deletes them there once they are seven days old or their code is gone, the next time it opens. MAMAKO counts how many questions each phone sends, under a one-way code made from a random ID the phone created. It keeps those counts on the phone code’s own record, which the teacher cannot read, and deletes them with it. No question carries the one-way code, so the teacher cannot tell which questions came from the same phone. MAMAKO deletes the questions 90 days after the meeting, or sooner when the teacher deletes the meeting. A meeting that ends set to One Family keeps only its approved summary, so its questions are deleted with its transcript.

After the meeting, MAMAKO writes a summary from the transcript and the parent’s replies: a few sentences, the decisions, the action items and the key terms. The teacher checks it, can edit it, and approves it. Approving keeps only the summary:MAMAKO deletes the transcript, the replies and the translation record at that moment, and keeps the approved summary and the meeting’s details (its type, date and times, its caption language, whether a list of names to hide was used, and when the summary was approved) until the teacher deletes the meeting. MAMAKO does not keep an unapproved parent conference summary past 48 hours: if the teacher has not approved a parent conference’s summary 48 hours after the meeting ends, MAMAKO deletes the transcript, the replies, the translation record and the summary automatically, and keeps only the meeting’s details. A staff or department meeting keeps its summary:if the teacher has not approved it 7 days after the meeting ends, MAMAKO deletes the transcript and the translation record automatically, and keeps the summary and the meeting’s details until the teacher deletes the meeting. A group parent meeting keeps its summary the same way. The deletion runs every hour, so it happens within the following hour. A parent conference’s summary is about one student, and only the teacher can see it. The summary is written from the transcript and the replies only, never from a parent’s private questions.

Phone Captions at a Meeting

During a meeting, the teacher can show a code on the screen. People at the meeting scan it and read the captions on their own phones, in English or in the one language the teacher’s browser translates the captions into. They need no app and no account, and the page asks nothing about them. Phone captions are for meetings only, never for lessons. The page’s own words follow the language the phone reads the captions in, picked from the phone’s language settings, which MAMAKO does not store.

The short code:beside the code, the teacher’s screen shows six letters and numbers a person can type at mamako.app/m instead of scanning. They open the same page, work only while the code they belong to works, and MAMAKO deletes them when that code stops or expires. MAMAKO limits how many short codes each network address can try in a minute, and how many wrong ones it answers in a minute from everyone together. It counts the wrong ones by the minute, with no address and no code, and deletes each count an hour later.

What the phone page shows:the meeting’s type (for example “Staff Meeting”), the last 40 caption lines and the line being spoken, with the same names starred out as on the teacher’s screen. Phones get only what is said while phone captions are on: nothing said before the teacher showed a code, or while phone captions were stopped or a code had expired. If someone is speaking as the teacher shows a code, phones start once that person pauses. It never shows the whole transcript or who is at the meeting. At a parent conference, a phone that sends a spoken reply shows that reply and its English, and no other phone sees it. At a group parent meeting, a phone that sends a private question shows that question, where it stands and the teacher’s private reply, and no other phone sees any of it. MAMAKO keeps a separate copy of those few lines for the phones and deletes them when the meeting ends or the code expires, or at the latest a few hours after the code was made if the teacher’s browser closes without ending the meeting.

Who can open it:anyone holding the code or its link. That is why a code opens the captions for three hours at most, the teacher sees how many phones are reading, a new code stops the old one at once, and “Stop phone captions” stops the code and deletes the copy. The teacher can also lock a code to new phones: a phone that opens the link or types the short code after that, or reloads the page, is told the meeting is closed to new phones, while phones already reading keep reading. The lock works on MAMAKO’s page only, so someone who copied the code could still read the captions another way; a new code or “Stop phone captions” cuts off every phone. While a phone reads, MAMAKO counts it under a random ID made for that visit and removes the ID when the phone leaves. As with any web page, our hosting and database providers see the phone’s network address when it connects (section 6).

After the meeting:the same link shows the summary of a group parent meeting, a staff meeting or a department meeting (its sentences, decisions, action items and key terms, never a parent’s question) only if the teacher chooses that when approving it, and then until seven days after the code was made. The approve step says who could read it and until when, and leaves it off unless the teacher ticks it. The teacher can turn the link off at any time from the meeting’s page: the link then stops showing the summary, and a phone with the page open checks again every minute while the page is on screen. A parent conference’s summary never appears there. Approving deletes the phones’ copy of the captions. When the teacher deletes the meeting, or MAMAKO deletes the transcript of a meeting nobody approved (48 hours after a parent conference, 7 days after a staff or department meeting), MAMAKO deletes the codes as well, and the link says the meeting is gone. A group parent meeting’s codes go after 7 days like a staff meeting’s.

Student Screens in Class

Student Screens are off until a teacher turns them on for a class, and a school can switch them off for all its teachers. With them on, students in that class can follow a live lesson on a laptop: a student opens mamako.app/join and types the class code, or opens the link the teacher shares. They need no account, and the page asks nothing about them: no name and no email address. Student Screens work in Chrome or Microsoft Edge on a laptop or desktop, whose browser translates the captions on the laptop itself, so the translated text never reaches us. A phone or another browser sees a short message and no captions.

What a student’s screen shows:the last 40 caption lines and the line being spoken, with the same names starred out as on the teacher’s screen, and the lesson’s key words in English. It never shows the whole transcript or who is in the class. MAMAKO keeps a separate copy of those lines and words for the laptops and deletes that copy when the lesson ends, or, if the teacher’s browser closes without ending the lesson, within six hours of the lesson’s code being made. When a student picks a language, the page asks us for the translations of the lesson’s key words that MAMAKO already holds in that language. The language travels in a hidden part of the request (a header), so it never appears in a web address, and MAMAKO keeps no record of which language anyone picked. The language and text size a student picks are kept in that browser only.

Who can open it:anyone holding the class code while a lesson with Student Screens is running. The teacher sees how many laptops have the lesson open on MAMAKO. That count covers the MAMAKO page only: someone who has the class code can read the copy another way and is not counted. “Stop student screens” stops every laptop at once and deletes the copy. To shut out someone who should not have the class code, such as a student who left the class, the teacher makes a new class code, in the class settings or during the lesson: the old code stops working, every laptop stops at once, and students type the new code to follow again. While a laptop follows, MAMAKO counts it under a random ID made for that visit and removes the ID when the laptop leaves. As with any web page, our hosting and database providers see the laptop’s network address when it connects (section 6). When the lesson ends, the page says so and, once the teacher shares the lesson recap, links to it; a laptop the teacher stopped, or shut out with a new class code, gets no link. The lesson’s code (which holds the teacher’s ID, the class, the lesson, and when the code was made, expires and was stopped, and nothing about a student) is deleted twelve hours after it was made.

Teachers are responsible for obtaining any consent required by law before activating a live session. See our Terms of Service.

3. Classes in the AP Business Course

The AP Business with Personal Finance course can be read by anyone, with no account. If you create an account, we remember which lessons and quizzes you have finished so you can pick up where you left off. That record is yours alone. No teacher, and no other user, can see it.

This changes only if you enter a class code your teacher gives you. Doing so links your account to that teacher’s class, and from then on that teacher can see, next to your name and email address:

• which topics you have finished and which you have not
• your best score on each topic quiz, and how many times a quiz has been attempted
• which specific questions you answered incorrectly

Entering the code is the whole of that decision, and nothing happens before it. Work you did before joining becomes visible to the teacher once you join, because the record is attached to your account rather than to the class. If you would rather your teacher did not see this, do not enter the code — the entire course, every video, every note, every practice question and the glossary, works exactly the same without an account at all.

A teacher only ever sees the students in their own class. They cannot see anyone else, and they cannot see anything you do outside the course — not what you search for, not which videos you watch, and not how long you spend on anything.

Unit diagnostics are excluded on purpose. Diagnostic answers and the study plan they produce never leave your browser, are never transmitted to us, and are never visible to a teacher, whether you are in a class or not.

4. Information We Collect

• Account info: name, email, and profile photo when you sign in. If you sign in with Google, we store the name and email address Google gives us for your account. Students do not need an account to read the captions in class.
• Service usage: classes you create or join, transcripts produced during your sessions, vocabulary you save, your language and study preferences, and, for the AP Business course, which lessons you have finished and your quiz scores. See section 3 for exactly who can see the last of these. If your school provides MAMAKO, the administrators your school names can see counts of your use: lessons captioned and their minutes, summaries, key words, how often the pages you shared were opened, and how much of the school’s lesson allowance is used. If your school turns on the weekly report, those administrators and the team leaders your school names also see, for each of your classes that met that week, the class name, the lesson dates, the topics and key terms from the lesson recaps you approved and still share, and whether you sent a family update or made a weekly summary for the class. When you stop sharing a lesson, its topics and key terms leave the report. The weekly email they receive carries only counts and class names, so the topics and key terms stay behind sign-in. They never see a transcript, a sentence said in class, any measure of how you speak, or anything about a student.
• Class roster: if a teacher chooses to enter one, the first names or display names of the students in a class, and each student’s home language. The teacher supplies this list. It is used to star recognised student names out of live captions and transcripts, to keep those names off weekly summaries and family updates, and to offer translation in the languages the class speaks. We do not keep an English-proficiency level or any other assessment of a named student. It is stored where only our servers can read it, is shown only to the teacher who entered it, and is never shown to students.
• Class glossary: if a teacher shares one, the words from that class’s lessons with their definitions and translations and the date and unit of the lesson each came from, and for a shared glossary the link and the translation languages the teacher chose. It is built from the lesson records described in section 2 and holds no roster and nothing a student typed.
• Family updates: a weekly note on what a class learned and the week’s words that a teacher shared before family updates were paused, drawn from the teacher’s lesson summaries and approved by the teacher, with its translations and its link. It names no student, and teachers cannot write new ones.
• Student Screens: if a teacher turns them on for a class, a record that they are on, who turned them on and when, and for each lesson the code laptops use to follow it (the teacher’s ID, the class, the lesson, and when the code was made, expires and was stopped). None of it names a student, and no record is kept of who followed a lesson.
• Weekly summaries: if a teacher makes one, a summary of a class’s week (an overview, then each lesson’s date, title, topics, key points and key terms with their meanings), drafted from the teacher’s lesson summaries and word lists, with the teacher’s edits, its translations and, if the teacher shares it, its link. MAMAKO keeps the names on the class roster out of it.
• School accounts: if your school or district licenses MAMAKO, the school gives us the email addresses of the teachers it wants to have access. We keep a record of which school each of those teacher accounts belongs to, and counts of how much captioning time each teacher account and each school uses in a month, and how many lessons and meetings have been started against the school’s allowance. These counts contain no audio and no words. If the school uses the weekly report, we also keep the names of its teams, which teachers are on each team, the email addresses of the team leaders the school names, the school’s time zone, and a record of which weekly emails went out. If the school gives us its logo or colour, the pages its teachers share show them with the school’s name.
• Purchases: a reference to your customer record at our payment processor, and a record of what you bought and whether it is currently active. Never your card number. See section 7.
• MAMAKO Academy and newsletter emails: if you sign up on our website, we keep your email address, the wording you agreed to, and the dates: when you signed up, when you confirmed, when each lesson was sent, and when you unsubscribed. We also keep where the signup came from (the page, which form, and any tag in the link, such as one showing you came from a LinkedIn post), and an error code if an email fails to arrive. We do not ask for your name, and we do not store your IP address with this record. Signing up on that form is the only way onto this list.
• Technical data: basic information needed to operate the Service securely (such as authentication state and session timestamps).

We do not collect device identifiers, advertising IDs, precise location, or any data unrelated to the Service.

5. How We Use Your Information

We use your information to:

• Provide and operate the Service for you
• Generate live transcripts, translations of captions and replies, meeting summaries, and study materials
• Save your account, classes, and vocabulary
• Process payments and unlock what you have purchased
• Respond to support requests and security issues
• Send the MAMAKO Academy lessons you signed up for, and keep the record that you asked for them
• Comply with applicable law

6. Third-Party Providers (Subprocessors)

We rely on the providers below to operate the Service. Each processes information on our behalf, under contractual obligations, only to provide its part of the Service. All of them store and process data in the United States. We do not sell your personal information, and we do not share it for advertising or profiling purposes. We update this list before any change takes effect.

• Google Cloud Platform / Firebase (Google LLC) — database, authentication and storage of account information, classes, rosters, transcripts, summaries, saved vocabulary and course progress. United States regions.
• Vercel — application hosting and server functions; request logs; page-view counts with no identifiers. United States.
• Transcription software — speech-to-text for live captions, and for a parent’s spoken replies at a parent conference. Audio is processed as it arrives and is not recorded by MAMAKO. United States.
• Anthropic — AI generation of lesson recaps and summaries, cleaned transcripts, words from the lesson, grammar notes, weekly summaries and their translations, translations of the family updates teachers already shared, class glossary translations and definitions, vocabulary help, meeting summaries, and English translations of a parent’s spoken replies in another language than English, from the words the speech-to-text service heard and the last few caption lines and replies, and of a parent’s private question at a group parent meeting when the teacher’s browser cannot translate it (the question’s words only, never the name). Inputs and outputs are deleted within 30 days and are not used to train models. United States.
• Resend — email for account verification, sign-in and teacher notices, and the MAMAKO Academy lessons. United States.
• Stripe: payments for purchases made on our sites; billing details only, never student data. United States. See section 7.

When a teacher turns on caption translation, the teacher’s own browser translates the captions, into one language or two. MAMAKO does not send caption text to its servers or to anyone else to be translated. A browser that cannot translate on its own shows the captions in English. At a parent conference, the last few caption lines go to our AI provider only as context for translating a parent’s spoken reply.

Our own relay for speech-to-text runs on Google Cloud in the United States and is operated by us. We do not use your data to train AI models.

7. Payments and Billing

Payments are processed by Stripe. You enter your card details on Stripe's own pages and they go directly to Stripe. MAMAKO never receives, sees, or stores your card number, expiry date, or security code.

What we store against your account is a Stripe customer reference and a record of what you purchased: which product it was, when you bought it and whether it is active. These purchase records are kept per account, and they are what unlock what you bought when you sign in.

Stripe handles your payment information under its own privacy policy, and may collect a billing address or location where tax rules require it. We keep our own purchase records for as long as the account exists, and afterwards only where accounting and tax rules require us to.

Schools and districts pay under the order form or quote they accept. A teacher whose account is provided by their school has no payment record with us.

8. Lesson Videos and YouTube

Lesson videos on the course pages are hosted on YouTube and embedded in privacy-enhanced mode, through the youtube-nocookie.com domain. In that mode YouTube does not set its usual viewing-activity cookies when the page loads.

Playing a video still contacts YouTube, so Google receives what any web request carries, such as your IP address and browser details, and can link the playback to your Google account if you are signed in to Google in the same browser. That playback is covered by Google's privacy policy rather than this one. Nothing else on the course page depends on the embed, so you can block it and still use the rest.

9. Children

MAMAKO is designed for use in schools. When the Service is used by students under the age of digital consent in their country, the school or teacher is responsible for obtaining the consent required by applicable law (for example, parental consent under COPPA in the United States, or equivalent local law). When MAMAKO is used by a U.S. educational institution, we operate as a school official with a legitimate educational interest under FERPA.

Parents or guardians who would like to review or delete a child’s data can email us, or contact the child’s teacher, who can remove the student from the class. Removing a student ends the teacher’s access to that student’s progress immediately; it does not delete the student’s own record of what they have finished.

For live sessions, a teacher may keep a class roster (section 4). A teacher can remove a student from it in the class settings, and the name and home language are removed from the roster immediately. When a session is started with the roster loaded, the names on it at that moment are starred out of the captions and transcript before they are stored; a name added during a lesson is hidden from the next session.

A student can also leave a class themselves at any time, from the same card on the course page where they entered the code, with the same effect. Deleting the account removes the record entirely — see section 11.

10. Retention

We keep your information only as long as needed to provide the Service. Word-for-word transcripts, the glosses and translations attached to their lines, the caption lines a teacher saved as notes, their cleaned copies and sentences quoted from them are deleted automatically seven days after a lesson, or sooner when the teacher’s school has asked for a shorter period (section 2). Lesson summaries, words from the lesson, grammar notes and saved vocabulary remain available until you or your teacher deletes them. When an account is deleted, or a school asks us to delete its data, the associated data is removed within 30 days; copies held by our providers expire on the schedules in section 6. A class roster entered by a teacher is kept until the teacher removes the students from it, and is deleted automatically 30 days after the teacher removes the class from their list. It is not copied into transcripts, summaries or lesson pages. Monthly counts of captioning time are deleted with the account they belong to, or with a school’s data when the school asks us to delete it. A class glossary, its link and its translations are deleted automatically 30 days after the teacher removes the class from their list, on the same schedule as the roster. Counts of a teacher’s use, which hold no lesson content, are deleted after 25 months. Family updates, their translations and their links are deleted automatically 90 days after the week they describe. We delete weekly summaries, their translations and their links automatically 90 days after the week they describe, or 30 days after the teacher removes the class from their list if that comes first, and at once when the teacher deletes one. A weekly parent note written before 2 October 2026 goes 90 days after its week, or 30 days after the teacher removes the class from their list if that comes first, and a class’s old parent note setting goes 30 days after the teacher removes the class from their list. Per-lesson counts of AI requests, kept to hold each lesson within its limits, and records of when a school’s lessons and meetings started are deleted after 30 days. Records of which weekly report emails went out are deleted after 26 weeks, and a school’s teams, logo and colour are deleted with the school’s data when the school asks us to delete it. MAMAKO deletes a meeting’s transcript and a parent’s replies when the teacher approves its summary, and keeps the approved summary until the teacher deletes the meeting. If the teacher has not approved a parent conference’s summary 48 hours after the meeting, MAMAKO deletes all of them automatically, the summary included. If the teacher has not approved a staff or department meeting’s summary 7 days after the meeting, MAMAKO deletes its transcript automatically and keeps the summary until the teacher deletes the meeting (section 2). A group parent meeting is kept the same way. A parent’s private questions at a group parent meeting, with the teacher’s private replies, are deleted 90 days after the meeting, or sooner when the teacher deletes the meeting (section 2). The copy of a meeting’s captions that phones read is deleted when the meeting ends or its code expires, and a phone code seven days after it was made, or sooner with the meeting (section 2). The copy of a lesson’s captions that student screens read is deleted when the lesson ends, and the lesson’s code twelve hours after it was made (section 2). A class’s Student Screens switch goes when the teacher turns it off, when the class is deleted, or 30 days after the teacher removes the class from their list. We keep the Academy signup record while you are subscribed. When you unsubscribe, we stop sending marketing email to that address and keep only your address, the dates and the wording you agreed to, so that nothing reaches you by mistake. If you ask us to stop emailing an address that never signed up, we keep that address and the date and nothing else. To delete either record, ask through mamako.app/contact.

11. Your Rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal information; to object to or restrict certain processing; to withdraw consent; and to lodge a complaint with your local data-protection authority.

Every MAMAKO Academy email has an unsubscribe link at the bottom. Using it stops those emails and any other marketing email from MAMAKO to that address. You can request account deletion at mamako.app/delete-account. For other requests, contact us at mamako.app/contact.

12. Cookies and Analytics

The Service uses no advertising cookies and no cross-site tracking, and we do not sell or share your data for advertising or profiling. We use browser local storage only for functional purposes, such as keeping you signed in and remembering your language preference; on a class glossary page, which cards you marked as known and your best quiz scores; and on a meeting’s phone captions page, the caption size, the language picked and whether a parent tapped Continue before speaking a reply. You can clear it at any time through your browser settings.

To see which pages are being visited, we use Vercel Web Analytics, which is built to measure traffic without identifying people. It counts page views and referrers in aggregate, sets no cookies, and does not follow you across other websites. Visits are counted using a hashed value derived from the request that is rotated regularly and is not stored as a profile of you. On pages with the Academy signup form, it also counts how often the form is shown and how often it is sent, never with your email address.

13. International Users

The Service is available in many countries. By using MAMAKO you understand that your information may be processed in countries other than the one in which you live, and you consent to such processing under this Privacy Policy and applicable law.

14. Security and Incidents

Data is encrypted in transit and at rest. Access is limited by role: teachers see their own classes, students see only what their teacher shares, and rosters are readable by our servers alone. Administrative actions on our infrastructure are logged. No system is perfectly secure; if you believe your account has been compromised, please contact us.

We keep a written incident-response procedure. If we suspect or confirm a security incident involving your data, we contain it, assess it, and notify affected schools and users within 72 hours of discovery with what happened, what data was involved, what we did about it, and what we recommend. Schools can request the procedure, and our data-deletion procedure, at any time.

15. Changes

We may update this policy from time to time. The "Last updated" date above reflects the most recent revision. For material changes that affect existing users, we will provide reasonable notice.

16. Contact

For privacy questions or requests, reach us through mamako.app/contact.