EDmango AI

Privacy Policy

Last updated: November 15, 2026

This Privacy Policy describes what information EDmango LLC ("we," "us," or "our") collects through the EDmango AI service (the "Service"), how we use it, and the choices you have. EDmango AI is used by adults — parents, caregivers, and educators — to get AI-assisted support around a child in their care; it's the adult who creates an account and uses the Service, never the child.

1. Information we collect

Account information

When you create an account, we collect your email address and a password (handled by our identity provider - see section 4). We don't ask for or collect your name or date of birth. If you choose to get your sign-in codes by email, we send them to that email address. If your account still uses text-message sign-in codes, which are ending, we also hold your mobile phone number. It is held by our identity provider, not in our own database.

Learner-profile information

If you create a learner profile, it holds information about that learner, such as names, behavioral or developmental observations, and your conversations with the Service about that learner. This is information you choose to share about a child, provided by you as the adult using the Service — the child never submits anything directly.

Messages and content

We collect the messages you send to the Service and the responses it generates, so we can provide the Service and maintain conversation context.

Technical and usage information

When you use the Service, we (and the analytics provider described below) automatically collect information such as: your IP address, and an approximate location derived from it (country, and where resolvable, region/city); your browser, operating system, and device type; the pages you view and, where relevant, the links you click or files you download; and a randomly generated identifier stored in your browser to recognize repeat visits (see Section 5 Cookies & similar technologies). We send your IP address, with that approximate location, to our analytics provider each time you view a page or click a link to another site.

2. How we use information

  • To provide, maintain, and improve the Service, including generating AI responses to your messages;
  • To operate your account, including authentication and account security (e.g., the second sign-in step, including emailing you sign-in codes if you choose that, and sending sign-in codes by text message to accounts that still use them). We use your phone number only to send you sign-in codes. We don't use it for marketing, we don't send you any other text messages, and we don't call you.
  • To send you service-related communications, including account-dormancy warnings before any data would be affected, and — if you've opted in — product updates;
  • To understand how the Service is used, in aggregate, so we can improve it (see Section 6, Analytics);
  • To detect, prevent, and address technical issues, abuse, or violations of our Terms & Conditions.

3. How AI processing works

To generate a response, your message (and relevant context from your learner profiles and conversation history, if applicable) is sent to one of our two AI providers, Anthropic and OpenAI, for processing. Each of our AI features uses Anthropic or OpenAI, and we may move a feature from one to the other. Each provider processes this information under its own commercial terms as our service provider — we don't currently make a specific data-retention or model-training commitment on either provider's behalf beyond what we actually have under contract with them, and we'll update this section if and when that changes. During a conversation about a learner, and again after it, the AI may add short notes to the learner's summary sheet or update notes it added earlier. After the conversation, a separate automated process sends that conversation, together with the learner's existing notes, to one of these AI providers to do this. You can see, edit, and delete those notes. See Section 7 for how long we keep messages and notes. Some messages are also sent to automated safety screening by one of these AI providers, when our own checks cannot rule out that a message describes someone at risk, so the Service can respond appropriately.

4. Third-party service providers

We rely on the following categories of service providers to operate the Service:

ProviderPurpose
Google CloudHosts the Service and stores its data, including backups
Firebase / Google Identity PlatformAccount creation, sign-in, and the second sign-in step, including sending sign-in codes by text message to accounts that still use them. Google also stores and uses the phone numbers it receives this way to prevent spam and abuse across its own services, under its own policies.
Google reCAPTCHAChecks that a request for a text-message sign-in code comes from a person, not an automated program
AnthropicGenerates the Service's AI responses and actions, and screens some messages for safety, alongside or instead of OpenAI
OpenAIGenerates the Service's AI responses and actions, and screens some messages for safety, alongside or instead of Anthropic. If you use the microphone, it also turns your recording into text.
Google Workspace (Gmail)Sends account emails, including sign-in codes, from @edmango.com addresses. Also receives what you send us through the contact form or by email to any of our addresses. Copies of these emails are kept in those mailboxes
BrevoKeeps our mailing list and sends emails to it, including product updates if you've opted in
Google AnalyticsAggregate usage analytics (pages viewed, IP address and approximate location, device/browser, link clicks)
JotformRuns the feedback form we ask testers to fill out, and stores the answers they send through it

We don't sell your personal information, and we don't share it with third parties for their own independent marketing purposes.

5. Cookies & similar technologies

Apart from the Google security check described in (8), the Service doesn't use traditional tracking cookies. Instead, it stores a small number of items directly in your browser's storage: (1) a randomly generated visitor identifier, to recognize repeat visits for analytics; (2) an analytics session identifier, which is cleared when you close your browser; (3) when you sign in, your sign-in credentials, managed by our sign-in provider (Google Identity Platform, see Section 4). These keep you signed in, including after you close your browser, until you sign out or are signed out; (4) if you choose to remember a device, a device-recognition token; (5) a few small settings the Service needs to work, such as a notice you have dismissed; (6) a chat message you have typed but not yet sent, so it can be restored if you reload the page or are signed out for inactivity. It is kept only in that browser tab, for your account, and we never receive it unless you send it. It is removed when you send it or sign out from that tab, and it is not restored after 24 hours. Your browser normally also removes it when you close the tab. (7) A message you sent that the Service could not accept, for example because you had reached a usage limit, stays in the conversation marked "Not sent" so you can copy or resend it. We don't keep it on our servers. It is kept in this browser, for your account, including after you close the browser. It is removed when you resend it or when you are signed out, including when you are signed out for inactivity. After 7 days it is no longer shown, and it is removed the next time you open EDmango AI in that browser. (8) If your account still uses text-message sign-in codes, Google's reCAPTCHA service checks that a person, not an automated program, is asking for a code. It may set its own cookies and collect information about your browser and device, under Google's Privacy Policy and Terms of Service. You can clear all of these at any time through your browser's own settings. Doing so signs you out and means we no longer recognize your browser. If you use a shared computer, sign out when you're done.

6. Analytics

We use Google Analytics to understand, in aggregate, how the Service is used — which pages are visited, what links are clicked, and general device/location trends. This helps us prioritize what to build and fix. Analytics data is sent from our own servers rather than directly from your browser to Google, but Google Analytics still receives your IP address, an approximate location, and device information for each visit, as described in Section 1. Some browsers send a "Do Not Track" signal. The Service does not currently respond to it.

7. How long we keep information

  • Your chats: Chats sent from November 15 on are kept until you delete them. Messages sent before then are still deleted after about a week. You can delete any chat at any time in the Service, and it is removed from our live database straight away. Your chats are also deleted when you delete, retire or start fresh the learner profile they belong to, and when your account is deleted, whether by you or because the account went unused (see below). Starting a learner profile fresh first saves a copy of the chats in that learner's Documents (see below). Each reply is stored with technical details of how the Service produced it, such as which guidance it drew on, and these are deleted with the chat. We use your chats only to provide the Service to you, as this policy describes, and we protect them in the same way as the rest of your information (see Section 10). Deleting a chat does not delete the notes on the learner's summary sheet, the strategies that were made from it, or any saved document that contains it. Those stay until you delete them (see below). Apart from those, we don't keep a summary or condensed copy of a deleted chat. Copies made for a testing program or a report are kept separately, as described below. Database backups that still contain a deleted chat expire on a rolling schedule, and no backup is retained for more than 30 days.
  • Testing programs: If you take part in a testing program, we keep a copy of your conversations, with details of how the Service produced its replies, so authorized members of our team can review them for accuracy and safety. We delete each copy 90 days after it is made. We may turn reviewed replies into anonymous examples, with names and identifying details removed, and keep those to improve the Service.
  • Reports: If you report a reply or a technical problem within the Service, we keep a copy of the report so authorized members of our team can review it for accuracy and safety, and to fix problems. A report about a reply includes the conversation involved and details of how the Service produced the reply. A report about a technical problem includes technical details about your device and the app. Both include anything you write in the report. We delete each report 90 days after it is made. We may turn reviewed replies into anonymous examples, with names and identifying details removed, and keep those to improve the Service.
  • Notes on a learner's summary sheet: whether you wrote them or the Service added them (see Section 3), notes are kept until you delete them, start the learner profile fresh, or the learner profile or your account is deleted, whether by you or because the account went unused (see below). The Service may update the wording of a note it added. When it does, the earlier wording is not kept. It does not change a note once you have edited it.
  • Your phone number, if your account still uses text-message sign-in codes: kept by our identity provider for as long as text messages are your way of signing in. It is removed when you switch to an authenticator app or to emailed codes, when text-message codes end and we switch your account to emailed codes, or when you delete your account. Google may keep its own copy for spam and abuse prevention, under its own policies, which we don't control.
  • Documents: documents saved in a learner's Documents, including the copy made automatically when you start a learner profile fresh, can contain your chats and notes word for word. They are kept until you delete them, or until the learner profile or your account is deleted, whether by you or because the account went unused (see below).
  • A learner profile that goes untouched: we'll send advance-warning emails well before anything happens, and the profile is only suspended from active use (not deleted) after an extended period of inactivity — you choose whether to keep, retire, or delete it. Its chats are kept with it until you delete or retire it.
  • An account with no sign-ins for an extended period: we'll send multiple advance-warning emails before deletion. If the account is ultimately deleted, it becomes inaccessible to you immediately and is removed from our live database straight away. Short-term database backups that still contain it expire on a rolling schedule, and no backup is retained for more than 30 days. Copies held in the storage systems of our cloud infrastructure provider are removed on that provider's own published schedule, which we do not control.

8. Your choices and rights

  • Access & export: you can request an export of your account and learner-profile data, including your learner notes and your chats, through the Service or by contacting us.
  • Correction: you can update your learner-profile information directly in the Service at any time.
  • Deletion: you can delete a chat or a learner profile, or request deletion of your entire account, at any time — through in-product controls where available, or by contacting us at help@edmango.com.
  • Marketing emails: any marketing email we send includes an unsubscribe link. Account and security-related emails (like dormancy warnings) aren't marketing and will continue as long as you have an account.

Depending on where you live, you may have additional rights under local law (for example, under California or other US state privacy laws). Contact us and we'll do our best to help, regardless of where you're located.

9. Children's privacy

The Service is intended for use by adults and is not directed to children. We don't knowingly collect personal information directly from a child. Learner-profile information is provided about a learner by the adult using the Service, under that adult's own representation that they have appropriate permissions to share it (see our Terms & Conditions) — it is not collected from the learner. If we become aware that a child has directly submitted personal information to us (for example, by creating their own account), we'll delete it.

10. Data security

We use reasonable technical and organizational measures to protect your information. These include encrypted connections and a second sign-in step on every account, in which you enter a sign-in code after your password. If you get your sign-in codes by email, your email account also protects your EDmango AI account, so keep it secure. If you choose to remember a device, we won't ask for your sign-in code when you sign in on that device, as long as it connects from roughly where it last did and has been used in the last 30 days. You can remove a remembered device at any time from your account page. No method of transmission or storage is completely secure, and we can't guarantee absolute security.

11. Where your information is processed

The Service is operated from the United States, and your information may be processed there and by service providers located elsewhere. By using the Service, you understand your information may be transferred to and processed in a country different from where you live.

12. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we'll update the "Last updated" date above and, where appropriate, notify you directly.

13. Contact

Questions about this policy, or want to exercise any of the choices above? Reach us at help@edmango.com or through our Support page. EDmango LLC

Jenna Mamidi, founder of EDmango AI

Meet the founder

EDmango AI is built by Jenna Mamidi, M.S., CCC-SLP, a speech-language pathologist with nearly two decades of clinical experience. She created it to bring that same clinical insight out of the therapy room and into the everyday moments where learning actually happens. Read more →