Effective: July 19, 2026
Memr.is, Inc. builds for a community that includes children and teens. We therefore treat minor access as a distinct product and operational responsibility, not as an ordinary account setting.
This policy supplements the Privacy Policy and Terms and Conditions. It describes the controls and restrictions that apply during pre-release testing.
1. Age tiers
Memr.is uses three policy tiers. The current pre-release account flow estimates a tier by subtracting birth year from the current calendar year rather than storing a full birth date. It therefore does not know a user's exact birthday and can move someone into the next tier before that birthday. This estimate is not approved as age assurance for under-13 product access.
| Tier | Intended age | Current pre-release account rule |
|---|---|---|
| Child | Under 13 | An account classified in this tier receives no active session until current consent, verified guardian authority, an active family relationship, and legal clearance are all present |
| Teen | 13 through 17 | An account classified in this tier is also placed into pending guardian consent before an active session is issued |
| Adult | 18 and older | Standard adult account controls, subject to role and organization permissions |
2. Safety baseline for every age
The current product does not include direct messages, public comments, a user-upload stranger feed, advertising SDKs, targeted advertising, a data-sale feature, or an in-product generative-AI surface. These are product boundaries, not settings a child can turn off by mistake.
Backend role and scope checks control access to family, team, organization, and administrative information. Frontend visibility is helpful guidance but is not the security boundary.
3. Guardian notice, authority, and consent
An invitation by itself does not activate child access. A coach, church leader, or organizer may help route an invitation, but that role does not make the person a parent or legal guardian. Memr.is intentionally stores normalized verification decisions, hashes, timestamps, and audit references rather than raw guardian identity documents in the identity service.
- A minor may begin a registration flow, but the current product does not issue an active session while the required guardian process is pending.
- A parent or legal guardian receives the applicable notice and states the relationship to the child.
- Guardian authority must be verified through an approved provider or review process. Development-only verification cannot authorize access for a real child.
- The guardian reviews the current legal version and gives the required child-specific acknowledgements and consent.
- The parent-child relationship is activated only after verification, consent, and the other legal-clearance conditions are satisfied.
4. Names, profiles, leaderboards, and dashboards
- Child public display is intended to use first name and last initial rather than a full name.
- Child leaderboard access fails closed unless membership in the requested team or organization is proven.
- Verified guardians can see a linked child's consent state, safe progress summaries, and the safety controls allowed for that tier.
- Coaches and organization operators can see only the roster, readiness, invitations, and other records allowed by their role and scope.
- Teen global-leaderboard visibility is not enabled as a verified opt-in flow and remains off.
- Organization records may expose an organization contact email; do not use a child's email as that public contact.
5. Live matches and guest access
Account policy presets describe child matches as team- or organization-scoped and teen matches as organization- or sanctioned-event-scoped. The live-match service does not enforce every age-tier room restriction, so organizers must apply the required scope themselves.
The pre-release guest-join path accepts a display name without an account, age tier, guardian clearance, or recorded policy acceptance. That path must not be used by a child under 13. Other guests should use a non-identifying nickname. Organizers are responsible for inviting appropriate participants and must not use guest access to bypass account or guardian controls.
6. Recite-aloud and microphone use
When used, the browser or operating system's speech-recognition service may process microphone audio under its own terms. Memr.is does not intentionally persist the raw recording. Memr.is receives a transcript for grading and may retain derived results such as accuracy, response time, and missed words.
- Child accounts: recite-aloud is unavailable.
- Teen accounts: recite-aloud starts off and may be enabled by a verified guardian where the policy allows it.
- Adult accounts: recite-aloud may be available as a personal choice.
7. Policy presets versus enforced controls
| Control | Current status |
|---|---|
| Guardian consent and child legal clearance | Available only through an expressly approved guardian-cleared flow |
| Child name masking and child leaderboard membership checks | Implemented in the current account and leaderboard paths |
| Recite-aloud availability | Implemented in policy and learning-attempt paths, subject to browser speech-service behavior |
| Quiet hours | Stored and displayed as a policy setting; the current product has no proven notification runtime that enforces every quiet period |
| Daily practice pacing | Stored and displayed as a preset; it is not a hard usage limit |
| Age-tier match-room scope | Modeled in the safety policy but not currently enforced by the match service |
| Automatic birthday transition | No durable automatic rollover; account transitions require review |
8. Parent and guardian controls
A verified guardian can review consent and relationship status, see safe progress summaries, use the adjustable controls allowed by the child's tier, withdraw consent, and request access, correction, or deletion of the child's information.
Withdrawing consent disables the authority that depends on that consent and may restrict the child's account. Complete cross-service erasure and minor deletion are not available in the beta, so under-13 product access remains closed unless Memr.is expressly approves the required deletion and backup handling.
9. Duties of coaches, churches, and organizers
- Use only your assigned team or organization scope and remove access when a role ends.
- Send guardian requests to the actual parent or legal guardian; do not complete consent on a family's behalf.
- Do not place a child's full name, personal email, address, raw evidence, or private circumstances into public fields, guest display names, or free-text notes.
- Do not publish rankings, screenshots, or match records outside the approved audience without appropriate authority.
- Report safety, privacy, account, or guardian disputes promptly and preserve confidentiality while they are reviewed.
- Use an organizer-approved official record and appropriate adult supervision for sanctioned or high-stakes events.
10. Reports, incidents, and emergencies
Report a suspected privacy, consent, unauthorized-access, or safety issue to hello@memr.is. Include enough context to identify the account or event, but do not email passwords, tokens, or raw identity documents. We may verify the reporter's identity and authority before sharing information or changing a child relationship.
Memr.is is not an emergency service and does not continuously monitor users or matches. If a child is in immediate danger, contact local emergency services and the responsible parent, guardian, or safeguarding authority.
11. Changes to this policy
We will update this policy as protections, providers, and product enforcement change. Material changes to the collection, use, or disclosure of child information will receive the notice and renewed consent required by law. The current effective date appears at the top of this page.