Amira Learning's privacy policy governs the voice recordings of roughly 50,000 New Mexico students under a statewide K-2 assessment mandate. It is also a moving target: the version published today is not the version that was published in the spring. This page places the April 12, 2026 capture, the July 20, 2026 version, and the August 4, 2026 version side by side, section by section, with every change marked.
Read it without a thumb on the scale: several July changes strengthen the policy — a consent qualifier on new-product-development use of audio, an explicit no-sell commitment, retention terms the US section previously did not have. Others narrow or relocate commitments. The point this page makes is not that either version is bad: the terms under which children's biometric data is held can change without any of the affected families being asked. That is a fact about governance, not about Amira in particular.
Three published versions in five months, and the trajectory runs one way: toward families. The August version drops the AI-training sentence, adds a parental-consent gate, and promises never to take disability status, living situation, or migrant status. Nobody was compelled to write that last line. Read the columns left to right and one reasonable reading is that people inside that company — people who have children, who take their work as seriously as any of us take ours — saw what was being asked and moved. That is the generous reading, and this page chooses it — as a floor, not a ceiling. And it is why the point stands: a protection that can be written in on August 4 can be written out on some later date, by the same process, by whoever holds the pen next. Good people leave. Terms of service outlive them. Anyone who has architected systems knowing children's data was in their care already understands this — the safeguard has to live somewhere that does not depend on the character of the current staff. That is an argument about where a protection lives. It is not an accusation about anyone's intent.
The families who raised these concerns read the same columns differently, and they have earned more than a polite acknowledgment here. Their movement — the op-ed, the public comment at the legislative hearing, the opt-out campaign that gathered dozens of families — is the reason there is a record to compare at all. Nothing here changed until they made it public: the first revision arrived five days after the hearing and a week after the op-ed; the third, two weeks before a school district put the assessment on its board agenda citing concerns its own parents had raised. Their reading is blunt: language that changes under scrutiny is obfuscation until shown otherwise, and the August sentence is their example. “Used strictly for instructional purposes” constrains nothing by itself — the policy never defines instructional purposes. And they did not have to wonder long whether the practice had changed with the words: seven days after the rewrite, the company’s chief executive told the Albuquerque Journal that the software uses recordings to “train” the program, “but only to improve its own performance.” The sentence left the policy. The practice, on the company’s own account, did not. On the point most in dispute, the record now reads the way the families said it would.
The two readings disagree about intent. They agree about the remedy — and that agreement is the point of this page. Whether the people inside moved or only the language moved, a family’s protection cannot live in a document its author rewrites while under scrutiny. It has to live where neither reading can reach it: in the contract the state signed, in deletion confirmations a district can produce, in terms that bind.
what would settle it
01Written confirmation that stored recordings were deleted — received, not requested.
02The operative contract: whether it names these commitments — FERPA included — and binds the vendor to them.
03A definition, in the policy itself, of “instructional purposes” and “improvement of Amira's Services.” The chief executive has placed model training inside the first — the software uses recordings to “train” the program, “but only to improve its own performance” — but the policy a family can read still defines neither.
04The retention configuration as deployed, which a public records request can produce.
one sentence, three versions
April and July both said the recordings improve Amira's AI models. The August version does not.
April 12
“We also use these recordings to improve our AI models and the Amira App.”
July 20
“We also use these recordings to improve the AI models supporting our Services and the Amira App. Audio recordings will only be used for new product development with appropriate consent as required under applicable law.”
August 4
“We also use these recordings to improve the AI models supporting our Services and the Amira App.”
“Student voice recording and analysis are used strictly for instructional purposes and to aid the teacher.”
Benefit of the doubt is the floor here, not a conclusion — and this rubric scores the document, not the practice. A sentence in a policy is evidence of what a company says, not of what it does; the paper is also the only thing a family can read. On paper, five of these eight are met or nearly so, and the three published versions move in one direction: toward families. The rows that remain open are about durability, not intent, and the last one is not the vendor's to close.
🟡
A child's voice is used to teach that childPartially metVendor
August 4: voice recording and analysis are “used strictly for instructional purposes and to aid the teacher.” July's sentence about improving Amira's AI models does not appear in this version. The limit: the policy never defines “instructional purposes.” If improving the models that deliver instruction counts, the sentence is compatible with the practice July described — the words changed; whether the practice changed is not answerable from the document.
🟡
Any other use of the voice requires a parent's consentPartially metVendor
The gate exists as of August 4 — no use “unrelated to the provision or improvement of Amira's Services” without verifiable parental consent. The seam is that “improvement of Amira's Services” is not defined anywhere in the policy, so the size of the carve-out is unknowable from the document.
✅
Sensitive categories are never collectedMetVendor
August 4 adds an explicit commitment never to take disability status, living situation, or migrant status, and states that Amira “does not create psychographic groups.” Nothing compelled this language.
✅
Student data is not sold or sharedMetVendor
August 4 states plainly that Amira does not “sell” or “share” User data as those terms are defined under applicable law — broader than April, which made the no-sale claim only for children.
✅
Retention is bounded and deletion is honoredMetVendor
The US policy had no retention terms in April. August retains data for the contract term “unless directed to delete by the district,” erases or de-identifies audio once it is no longer needed for its original purpose, and charges no fee for deletion requests.
⬜
Families are told when the terms changeNot yet metVendor
Three published versions in five months. The policy commits to notifying registered users “as required by applicable law,” and the April commitment to post announcements on the website is no longer present. No affected family was asked about any of the three revisions.
⬜
The terms are independently verifiable over timeNot yet metVendor
The Internet Archive holds no capture of this policy after May 14, 2026. Only the April column here has a third-party archive; the July and August copies are ours. A reader who wants to check what the terms said last spring is dependent on whoever kept a copy.
⬜
The protections are binding, not revisable at willNot yet metState / district
Everything scored above lives in a document its author can rewrite — as it has, three times. Whether these commitments also appear in the contract the state and district signed is not answerable from the policy, and is the one row on this list that families cannot resolve by reading anything the vendor publishes.
What moved · 24 changes across two transitions
Each change is placed on a three-position track: whether it moved the balance toward families and students, left it structurally unchanged, or moved it toward the company. The positions that do not apply are greyed. Read down the column of lit icons and the trajectory is visible without reading a word.
April 12 → July 20 · 16 changes · 6 toward families
April: recordings "improve our AI models and the Amira App," full stop. July adds: audio will only be used for new product development "with appropriate consent as required under applicable law." The AI-model-improvement use itself is unchanged.
July adds a bullet stating Amira does not "sell" or "share" User data as those terms are defined under applicable law. April made the no-sell claim only for Children.
The April US policy stated no retention terms at all — retention language existed only in the separate Canada policy. July adds: retention for the duration of the school's contract, a post-termination deletion window of "weeks or a few months," and no-fee deletion requests.
April's US policy had no security section — an equivalent existed only in the separate Canada policy. July adds the full section: encryption at rest and in transit, least-privilege access controls, SOC 2 certification, AWS hosting, and an incident-response plan.
April covered only under-13 "Child" users and adult Educators. July adds a "Minor" class (under 18) and a collective "Student Users" term, extending the policy's coverage — and its collection scope — to all minors.
April's state-specific note named California, Colorado, Connecticut, Nevada, Utah and Virginia. July generalizes it to "a U.S. state which has enacted a consumer privacy law." Broader coverage by default; the substantive commitments are unchanged.
April: "Personalize and improve a Children's experience." July: "Profile, personalize, and improve a Student User's experience." The same section elsewhere states Amira does not build personal profiles other than for authorized educational purposes; the new verb is undefined.
April's US section enumerated the legal bases for processing (contract, consent, legal obligation, legitimate interests). July removes the section from the US policy; comparable language persists only in the EU/UK section.
April: student data used "for authorized educational or school purposes with consent from the Child's school." July: "as allowed under applicable law." The consent reference moves from a named party to a body of law.
April described cookies and web beacons. July describes "first-party cookies" and, in Your Choices, discloses analytics SDKs and states essential cookies cannot be disabled.
July adds a disclosure that support chat may be AI — "you are not communicating with a human representative of Amira" — and that chat content is collected.
April and July both said the recordings improve Amira's AI models. August drops that sentence and its new-product-development clause: voice recording and analysis are now "used strictly for instructional purposes and to aid the teacher," retained "as directed by the district." The largest single move across the three versions.
New in August: no use of voice recordings to identify or authenticate students, or for purposes unrelated to providing or improving the service, without verifiable parental consent. "Improvement of Amira's Services" is left undefined.
New in August: Amira "will never take sensitive demographic information including disability status, living situation, or migrant status." Nothing in the record compelled this sentence.
August replaces "vendors, consultants and other service providers" with "sub-processors." A more precise data-protection term; the underlying permission is unchanged.
July's US page carried no individual-rights list at all. August adds one — access, correction, withdrawal of consent, deletion — but frames each as an "Option to" rather than a right, and commits only to responding "as soon as possible." More than July offered, worded more softly than a right.
The Canada and EU/UK policies, the EU-U.S. Data Privacy Framework statement, and the legal-basis section move off this URL to a separate international page. Verified present there before publishing — relocated, not deleted.
added since the previous columndropped since the previous columnreworded
row chips:◀ toward families◆ unclear• structural▶ toward the company
How to read the marks: April is the baseline and carries none. Each later column is marked against the one immediately to its left — July against April, August against July. A clause introduced in July and left alone in August therefore shows as new once, in July, and is described as carried over in August.
our capture, hosted on this site · live: amiralearning.com/amira-privacy
No Internet Archive capture yet. This is still the live text, so one can still be made.
👥Preamble — who the policy covers
APR→JUL•JUL→AUG—
July adds a definition of personal information, a new under-18 "Minor" class, the collective "Student Users" term, and an educator warranty clause.
April 12, 2026This Privacy Policy explains how Amira Learning Inc. (“Amira,” “we,” “our” or “us”) collects, uses and discloses information about users of our Amira app (“Amira App”), website, and other online products and services (collectively, the “Services”). This Policy addresses our information practices applicable to our Services. Our information practices vary depending upon the type of user and the portion of the Amira App used by that user. Users of the Services include child users (any child under the age of 13 enrolled in school districts and schools that make the Amira App or other Services available) (“Child”) and adult users (including teachers, school administrators, district administrators, and other educators who purchase our Services or work in a district or school that purchased our Services (“Educators”), collectively referred to as Users. A Child may only use the learning portion of the Services. Only Educators can create accounts and subscribe to the Services.
July 20, 2026This Privacy Policy explains how Amira Learning Inc. (“Amira,” “we,” “our” or “us”) collects, uses and discloses personal information about users of our Amira app (“Amira App”), website, and other online products and services (collectively, the “Services”). “Personal information” is defined as information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual or household. Users of the Services include child users (any child under the age of 13 enrolled in school districts and schools that make the Amira App or other Services available) (“Child”); minor users (any individual under the age of 18 enrolled in school districts and schools that make the Amira App or other Services available) (“Minor”); and adult users (including teachers, school administrators, district administrators, and other educators who purchase our Services or work in a district or school that purchased our Services (“Educators”). Child and Minor users will be referred to collectively as “Student Users.” This Privacy Policy collectively refers to Student Users, Educators, and any other visitors to our website or Services (e.g., parents or guardians) as “Users.” A Student User may only use the learning portion of the Services. Only Educators can create accounts and subscribe to the Services. If you are acting on behalf of a School, you represent and warrant that you are at least eighteen (18) years old and have the authority, the right, and the capacity to legally bind the school and have read and understand this Privacy Policy.
August 4, 2026Substantially as in July: the “Minor” (under-18) class, the collective “Student Users” term, the definition of personal information, and the educator warranty all carry over unchanged. The masthead becomes “Amira Privacy Policy - US,” with the Canada and EU/UK policies moved to a separate international page.
🗺️State-Specific Notes
APR→JUL•JUL→AUG—
Six enumerated states become "a U.S. state which has enacted a consumer privacy law."
April 12, 2026If you are a resident of the states of California, Colorado, Connecticut, Nevada, Utah and Virginia, please see our Additional Privacy Notices for U.S. Residents for additional state specific information and disclosures. Please also see our Additional Privacy Rights section below for more information about exercising your eligible privacy rights.
July 20, 2026If you are a resident of a U.S. state which has enacted a consumer privacy law, such as California, please see our Additional Privacy Notices for U.S. Residents for additional state specific information and disclosures. Please also see our Additional Privacy Rights section below for more information about exercising your eligible privacy rights.
August 4, 2026Unchanged from July.
🧒Children's (and Minor's) Information
APR→JUL◆JUL→AUG◀
July moves the consent anchor: "with consent from the Child's school" becomes "as allowed under applicable law." August adds a gate: no use of voice recordings beyond providing or improving the service without verifiable parental consent.
April 12, 2026Except as explicitly described in this Privacy Policy, we do not knowingly collect personal information from Children under the age of 13 without consent from the school. We only collect, maintain, use or share personal information from Children as needed for authorized educational or school purposes with consent from the Child’s school. If we learn that we have collected personal information from a Child under 13 without the school’s consent, we will delete that information. We do not sell personal information of Children. We do not use or disclose information about Children (whether personal information or otherwise) for behavioral targeting of advertisements to Children. We do not build personal profiles of children other than for supporting authorized educational/school purposes.
July 20, 2026Except as explicitly described in this Privacy Policy, we do not knowingly collect personal information from Children or Minors without consent from the school. We only collect, maintain, use or share personal information from Children or Minors as needed for authorized educational or school purposes as allowed under applicable law. If we learn that we have collected personal information from a Child or Minor without appropriate consent, we will delete that information. We do not sell personal information of Children or Minors. We do not use or disclose information about Children or Minors (whether personal information or otherwise) for behavioral targeting of advertisements to Children or Minors. We do not build personal profiles of Children or Minors other than for supporting authorized educational/school purposes.
August 4, 2026Except as explicitly described in this Privacy Policy, we do not knowingly collect personal information from Children or Minors without consent from the school. … We do not sell personal information of Children or Minors. … Please note that Amira does not use voice recordings to identify or authenticate Student Users, or any purposes unrelated to the provision or improvement of Amira’s Services without first obtaining verifiable consent from a Student User’s parent or guardian.
🧑🏫Collection of Information — from Educators
APR→JUL•JUL→AUG◀
July adds a Communications Information category: the content of support emails, calls, and chats. August adds a commitment never to take sensitive demographic information — disability status, living situation, or migrant status.
April 12, 2026Educator Registration Information: We collect registration information, including name, email address, school affiliation and the grade level and names of classes Educators teach. Child Roster Information: We collect information the Educator provides to enable a Child’s use of the Amira App, including the Child’s first name and last name, school email address and password, school name, class name, grade level and local language (e.g. English). We may also collect the Child’s parent’s email address.
July 20, 2026Educator Registration Information: We collect registration information, including name, email address, school affiliation and the grade level and names of classes Educators teach. Student User Roster Information: We collect information the Educator provides to enable a Student User’s use of the Amira App, including the Student User’s first name and last name, school email address and password, school name, class name, grade level and local language (e.g. English). We may also collect the email address of the Student User’s parent or guardian. Communications Information: We may collect the content of your communications for support purposes when you contact Amira via email, call, or via chat features.
August 4, 2026Educator Registration Information … Student User Roster Information … Communications Information … (all as in July). Demographic Information: Only when contractually required by a School, we may receive baseline information, including a Student User’s gender or ethnicity. Amira will never take sensitive demographic information including disability status, living situation, or migrant status.
🎙️Collection of Information — Audio Recordings
APR→JUL◀JUL→AUG◀
The key row. April: the recordings "improve our AI models." July appends a consent qualifier on new-product-development use, AI-training unchanged. August drops the AI-training sentence — recording and analysis are "used strictly for instructional purposes and to aid the teacher."
April 12, 2026Audio Recordings. When a Child interacts with the Amira App, we collect recordings of the Child’s voice. We retain recordings of the Child’s voice when collected from our in-school experience. These recordings enable our AI-driven algorithms to understand their reading strengths and areas where the child would benefit from more practice, evaluate their progress, and customize their experience. We also use these recordings to improve our AI models and the Amira App.
July 20, 2026Audio Recordings. When a Student User interacts with the Amira App, we collect recordings of the Student User’s voice. We retain recordings of the Student User’s voice when collected from our in-school experience. These recordings enable our AI-driven algorithms to understand their reading strengths and areas where the Student User would benefit from more practice, evaluate their progress, and customize their experience. We also use these recordings to improve the AI models supporting our Services and the Amira App. Audio recordings will only be used for new product development with appropriate consent as required under applicable law.
August 4, 2026Audio Recordings. We retain recordings of the Student User’s voice as directed by the district. Student voice recording and analysis are used strictly for instructional purposes and to aid the teacher. [July’s sentence that the recordings “improve the AI models supporting our Services and the Amira App,” and its new-product-development clause, do not appear in this version.]
🍪Information We Collect Automatically
APR→JUL◆JUL→AUG—
Web beacons — described at length in April — are no longer mentioned; the cookies description becomes "first-party cookies."
April 12, 2026Information Collected by Cookies and Other Tracking Technologies: We use various technologies to collect information from our Services, including cookies and web beacons. Cookies are small data files stored on hard drives or in device memory that help us improve our Services and users’ experience, see which areas and features of our Services are popular and count visits. Web beacons are electronic images that may be used in our Services or emails and help deliver cookies, count visits, understand usage and campaign effectiveness and determine whether an email has been opened and acted upon. [Device and Log Information text is unchanged between versions. The Child activity bullet reads: “Our collection of this information through cookies and other tracking technologies (as defined above) is used only to support the internal operations of the Services.”]
July 20, 2026Information Collected by Cookies and Other Tracking Technologies: We use various technologies to collect information from our Services, including first-party cookies. Cookies are small data files stored on hard drives or in device memory that help us improve our Services and users’ experience, see which areas and features of our Services are popular and count visits. [Device and Log Information text is unchanged between versions. The Student User activity bullet reads: “Our collection of this information through first-party cookies and other tracking technologies (as defined above) is used only to support the internal operations of the Services.”]
August 4, 2026Unchanged from July, including the narrowing to “first-party cookies.”
⚙️Use of Information — student data
APR→JUL◆JUL→AUG◀
July adds one verb: "Profile." August appends "Amira does not create psychographic groups." The Educator-use list is otherwise unchanged.
April 12, 2026We use the information we collect from Children to: Personalize and improve a Children’s experience on the Amira App and provide content or features that match the Child’s reading level and interests, as well as to monitor trends, usage and activities, so that we can make the Amira App more helpful to all Children; and Track a Child’s reading progress and usage of the Amira App. We use information collected from both Educators and Children to: Analyze, operate and improve our Services; Detect, protect against, and prevent security incidents and illegal or unauthorized activities, as well as investigate complaints and claims; Comply with applicable laws, legal processes or enforceable governmental requests, and defend against or pursue claims, disputes or litigation – in court or elsewhere; and Enforce our policies, terms and conditions, or other agreements.
July 20, 2026We use the information we collect from Student Users to: Profile, personalize, and improve a Student User’s experience on the Amira App and provide content or features that match the Student User’s reading level and interests, as well as to monitor trends, usage and activities, so that we can make the Amira App more helpful to all Student Users; and Track a Student User’s reading progress and usage of the Amira App. We use information collected from both Educators and Student Users to: Analyze, operate and improve our existing Services; Detect, protect against, and prevent security incidents and illegal or unauthorized activities, as well as investigate complaints and claims; Comply with applicable laws, legal processes or enforceable governmental requests, and defend against or pursue claims, disputes or litigation – in court or elsewhere; and Enforce our policies, terms and conditions, or other agreements.
August 4, 2026Group (for educational purposes), personalize, and improve a Student User’s experience … Analyze, operate and improve our existing Services … (as in July). Amira does not create psychographic groups.
🤝Sharing / Disclosure of Information
APR→JUL◀◀JUL→AUG•
July adds a contractual re-identification ban on recipients of de-identified data and an explicit no-"sell"/no-"share" bullet covering all Users.
April 12, 2026We may share the information we collect from Educators as follows: Between and among Amira and current and future parents, affiliates, subsidiaries and other companies under common control and ownership, provided such entities are subject to the commitments set forth in this Privacy Policy; and With Educator consent or at the Educator’s direction. We may also share aggregated or de-identified information, which cannot reasonably be used to identify any individual. [The service-provider, legal-process, user-agreement, and merger/acquisition disclosure bullets are unchanged between versions.] We do not disclose the personal information of any Child to third parties for any marketing or promotional purposes. Amira Learning does not share mobile information with third parties/affiliates for marketing/promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
July 20, 2026We may disclose the information we collect from Educators as follows: Between and among Amira and current and future parent companies, affiliates, subsidiaries and other companies under common control and ownership, provided such entities are subject to the commitments set forth in this Privacy Policy; and With Educator consent or at the Educator’s direction. We may also share aggregated or de-identified information, which cannot reasonably be used to identify any individual. Where we maintain de-identified information, we take reasonable measures to ensure that the information cannot be associated with a Student User, Educator, or household, maintain the information in de-identified form, prohibit recipients contractually from attempting re-identification, and otherwise comply with applicable law. [The service-provider, legal-process, user-agreement, and merger/acquisition disclosure bullets are unchanged between versions.] Amira takes the privacy of User data seriously and does not process User data as follows: We do not disclose the personal information of any Student User to third parties for any marketing or promotional purposes. Amira does not share mobile information with third parties/affiliates for marketing/promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. Amira does not “sell” or “share” User data as those terms are defined under applicable law.
August 4, 2026Between and among Amira and current and future parent companies, affiliates, subsidiaries … With sub-processors who need access to such information to carry out work on our behalf … de-identification and re-identification-ban language, and the commitment that Amira does not “sell” or “share” User data, all carried over from July.
📜Legal Basis for Processing
APR→JUL◆JUL→AUG•
Present in April's US policy; removed in July. Comparable language persists only in the EU/UK section.
April 12, 2026We process your personal information as follows: To perform our contractual obligations in our Terms of Service or other contracts with you (such as to provide you the Service as described in our Terms of Service); With Educators’ prior consent, which may be withdrawn at any time (we use Educators’ quotes and testimonials for promotional purposes, or other purposes we obtain Educators’ consent for from time to time); When necessary to ensure compliance with a legal obligation to which we are subject; and When necessary for the purposes of our legitimate interests, such as in improving, personalizing, and developing the Service, and for security purposes as described above.
July 20, 2026— section removed in the July version —
August 4, 2026Not on the August US page — as it was not on July's. Relocated rather than deleted: the legal-basis section, the EU-U.S. Data Privacy Framework statement, and the right to lodge a complaint with a regulator are all present on the separate international policy (amiralearning.com/privacy-policy-eu-uk). We checked before publishing this.
🔒Data Security Safeguards
APR→JUL◀JUL→AUG—
Absent from April's US policy (an equivalent existed only in the separate Canada policy). July adds the full section. The SOC 2 claim names no auditor and remains vendor-asserted.
April 12, 2026— section not present in the April version —
July 20, 2026We take data security very seriously and have implemented industry-standard security measures to protect personal information against loss, theft, unauthorized access, and unauthorized disclosure. Key practices include: Encryption (personal information, especially sensitive data like student names and voice recordings, is encrypted both at rest and in transit); Access Controls (least privilege; confidentiality obligations; school-controlled educator accounts); Administrative and Organizational Measures (a dedicated privacy and security team; internal policies for encryption standards, incident response plans, and data-access protocols); Third-Party Security Audits and Certifications (“Amira holds a SOC 2 (Service Organization Control 2) certification, following an audit performed by independent auditors”); Physical and Technical Safeguards (secure AWS facilities; firewalls; intrusion detection; continuous monitoring); Data Minimization; and Incident Response (notification of affected school authorities, individuals, and regulators as required by applicable U.S. laws).
August 4, 2026Unchanged from July: encryption at rest and in transit, least-privilege access controls, SOC 2 certification, AWS hosting, incident-response plan.
🗄️Data Retention & Deletion
APR→JUL◀JUL→AUG◀
Absent from April's US policy — the April US section stated no retention terms at all. July adds contract-duration retention, a short post-termination window, and no-fee deletion requests.
April 12, 2026— section not present in the April version —
July 20, 2026Active School Use: For schools and districts currently using Amira, we retain Student User and Educator information for the duration of the school’s contract or active subscription. Student User reading data and recordings remain available so long as the student is actively using Amira under the school’s license, enabling longitudinal progress tracking. Account Deactivation or End of School Contract: … We either delete the data or irreversibly de-identify it after a defined retention window. This window is usually short (measured in weeks or a few months) to accommodate any potential service reactivation or data export requests from the school. … Audio recordings and detailed student performance data will be securely erased or de-identified once they are no longer needed for their original purpose. Deletion Requests: Schools or parents (via the school) can request deletion of a Student User’s personal information at any time through the Amira App’s interface. … We do not charge any fee for handling access or deletion requests.
August 4, 2026Active School Use: … we retain Student User and Educator information for the duration of the school’s contract or active subscription, unless directed to delete by the district. … Audio recordings and detailed student performance data will be securely erased or de-identified once they are no longer needed for their original purpose. Deletion Requests … We do not charge any fee.
💬Public Posting Areas · AI Chat · SMS
APR→JUL•JUL→AUG—
All new in July. The chat disclaimer discloses that support chat may be AI, not a human.
April 12, 2026— section not present in the April version —
July 20, 2026Disclaimer Regarding Chat Features: Amira may incorporate an interactive chat feature (“Chat Feature”), which may use Artificial Intelligence, for customer support purposes. If you interact with these Chat Features, you are not communicating with a human representative of Amira. Instead, you are communicating with software that generates responses to your input based on machine-learning algorithms. These Chat Features may collect the content of your communications, including any personal information you provide it. [Public Posting Areas and SMS Messaging disclaimers also added; see the archived PDF for full text.]
August 4, 2026Unchanged from July: the public-posting disclaimer, the SMS section, and the disclaimer that a chat feature “may use Artificial Intelligence,” that you are “not communicating with a human,” and that it “may collect the content of your communications.”
☑️Your Choices
APR→JUL▶JUL→AUG◆
The Privacy Rights Request Form is gone (email only). Cookies text now discloses SDKs and states essential cookies cannot be disabled.
April 12, 2026Additional Privacy Rights: … Eligible users can submit a request by completing our Privacy Rights Request Form or emailing us at trust@amiralearning.com. Cookies: Most web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove or reject browser cookies. Please note that if you choose to remove or reject cookies, this could affect the availability and functionality of our Services. Educator Account Information: Please note that we may retain certain Educator information as permitted by law. We may also retain cached or archived copies of the information we collect for a certain period of time.
July 20, 2026Additional Privacy Rights: … Eligible users can submit a request by emailing us at trust@amiralearning.com. Cookies: Amira uses analytics cookies and Software Development Kits to provide its Services. Most web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove or reject optional browser cookies. Essential cookies are required to provide the Services and cannot be disabled. Educator Account Information: Please note that we may retain certain Educator personal information as permitted by law or as required by the School where you are employed. We may also retain cached or archived copies of the information we collect in order to provide the Services or as permitted under applicable law.
August 4, 2026Individuals (or their parents/guardians in the case of minors) have various rights regarding their personal information. Amira is committed to upholding these options … Option to Access … Option to Correction … Option to Withdraw Consent … Option to Deletion … We will respond to all individual requests as soon as possible.
📡Do Not Track · Global Privacy Control
APR→JUL◀JUL→AUG—
Both new in July: DNT explicitly not honored; GPC honored.
April 12, 2026— section not present in the April version —
July 20, 2026Do Not Track Signals: … At this time, we do not recognize or respond to browser-initiated DNT signals because we do not track you across websites. Global Privacy Control (GPC) and Opt-Out Preference Signals: Amira recognizes and honors Global Privacy Control (GPC) and other opt-out preference signals that browsers and browser extensions transmit on your behalf … Amira will respond to verifiable opt-out requests within the timeframe required under applicable law.
August 4, 2026Unchanged from July: DNT signals are not honored; Global Privacy Control is, with responses “within the timeframe required under applicable law.”
✉️Contact Us
APR→JUL•JUL→AUG—
Mailing address changed.
April 12, 2026If you have any questions about this Privacy Policy, please contact us at: trust@amiralearning.com, and Mailing: 5214F Diamond Heights Blvd #3255 San Francisco, CA 94131.
July 20, 2026If you have any questions about this Privacy Policy, please contact us at: trust@amiralearning.com, or by mail to 490 Post St, Suite 500 PMB 2538 San Francisco, CA 94102.
August 4, 2026Unchanged from July: trust@amiralearning.com, 490 Post St, Suite 500 PMB 2538 San Francisco, CA 94102, phone 1-866-883-READ (7323).
Provenance and scope
Scope: this comparison covers the “US School Experience” section of the policy — the section that governs New Mexico students. The Canada and EU/UK sections are omitted; both are available in the linked full documents.
The phrase “to develop new products and updates,” quoted from Amira's policy in public discussion of the New Mexico deployment, appears in none of the three versions shown here. It traces to an earlier revision of the policy. The Wayback Machine holds captures back to November 2024.
Bracketed passages [like this] are editorial condensations of text that is materially unchanged between versions or is available in full in the linked documents. Everything else is transcribed verbatim.
On the archive: The Internet Archive holds captures of this policy on January 9, January 22, February 3, April 12 and May 14, 2026 — and none after. The July and August versions were therefore never independently archived; the copies below are ours, captured from the live page on the dates shown. Both the April 12 and May 14 captures still read “Last Updated: March 9, 2026,” so neither is a record of the July text. This is a limit of the evidence, and we would rather state it than let a hosted PDF imply third-party verification it does not have. The Internet Archive's index for this URL ↗ — check the gap yourself. The August copy was verified against the live page on August 16, 2026.
Timeline, stated without inference: the Santa Fe New Mexican op-ed on Amira ran July 13, 2026. The Legislative Education Study Committee heard testimony from Amira's CEO in Taos on July 15, 2026. The policy's “Last Updated” date changed to July 20, 2026.
The state's own policy analyst reported in May that New Mexico “does not currently have statewide procurement standards for AI tools, student data privacy requirements specific to AI, and a formal evaluation process for AI education tools.” A policy that can change beneath a mandate, with no standard against which to evaluate the change, is the gap this page documents.
Perkins, C. (2026, July). The Amira privacy policy, before and after [Version comparison]. Kinetic Trust Protocol Advocacy. https://kinetic-trust-protocol.net/advocacy/sfps/amira-policy-diff