English

DRAFT — NOT FOR ACCEPTANCE OR PUBLICATION. Version 0.1 · Prepared September 5, 2026.

This package proposes terms for a U.S. invitation-only family beta for learners aged 14–17 and their parents or legal guardians. Notatky is the product name; Notatky is the repository name. These drafts are not evidence of compliance, a signed agreement, or a substitute for state-specific legal review. The proposed family beta is free, without automatic conversion to a paid service; the operator must approve that commercial assumption before publication. No effective date is assigned yet.

Publication blockers and actual status

The current local prototype stores the study library in the browser and offers export. Its local processing can extract material, transcribe audio and generate explanations. It is not a verified external beta. Cloud-library and study-safety changes have separate review histories; their existence does not establish production deployment. Verified guardian admission, a parent dashboard, dependable parent alerts, production deletion and vendor contracts have not been demonstrated. Do not present the following proposed operational commitments as available until they are implemented and tested.

Complete these fields throughout this package: [[OPERATOR_LEGAL_NAME]], [[OPERATOR_STATE]], [[POSTAL_ADDRESS]], [[PRIVACY_EMAIL]], [[SUPPORT_EMAIL]], [[LAUNCH_STATES]], [[EFFECTIVE_DATE]], [[RETENTION_SCHEDULE]], [[PROCESSOR_REGISTER]], [[GUARDIAN_VERIFICATION_METHOD]], [[SAFETY_REVIEW_PROCESS]]. Do not collect acceptance against drafts containing these placeholders. Additional school, vendor and billing fields appear in the conditional schedules.

1. Terms of use and family beta participation

Operator and scope. These terms govern the Notatky family beta operated by [[OPERATOR_LEGAL_NAME]], organized in [[OPERATOR_STATE]], at [[POSTAL_ADDRESS]]. Contact [[SUPPORT_EMAIL]]. Available functions and limitations are identified inside the service. The service assists with learning, organizing materials, explanations and study practice. It does not award qualifications or make school admission, grading or disciplinary decisions.

Eligibility. This beta admits invited learners aged 14–17 in [[LAUNCH_STATES]] after guardian verification and the learner's separate assent. Accounts are personal; do not share credentials or misrepresent age or guardianship. People under 14 are not eligible. Discovery of underage use triggers restricted access and an appropriate privacy response, not an invitation to enter a different age. A guardian's participation does not eliminate a child's statutory rights. Adult and institutional access require the applicable separate onboarding route.

Learning and conduct. Use explanations to develop your own understanding and follow your teacher's assignment and AI-use rules. Do not impersonate another person, harass, bypass security, upload malware, seek harmful instructions or infringe others' rights. We may limit an affected feature or suspend access for a substantiated violation, security incident or legal requirement. Where safe and lawful, we will explain the reason and provide a review route through [[SUPPORT_EMAIL]]. An automated safety flag alone is not proof of misconduct.

Your material. You retain rights you hold in uploads, notes and additions. You grant us a nonexclusive permission to process, store, reproduce and transform that material only as needed to provide your requested functions, protect the service and meet applicable obligations, through the processors disclosed in the privacy notice. This is not a transfer of ownership, permission to sell your content or permission to train a general-purpose model. Processing permission ends on deletion except for specifically disclosed, necessary retention obligations. Do not upload material you have no authority to use. AI output may be inaccurate, similar to others' output or ineligible for copyright protection.

Beta limitations and price. This proposed beta has no fee, card requirement or automatic paid renewal. Features may change or be interrupted. Check the source material and keep an export of important work. We do not promise grades, perfect AI answers, uninterrupted availability or permanent storage. These statements do not exclude obligations or remedies that cannot lawfully be excluded.

Leaving and changes. You or an authorized guardian may request account closure and the applicable access, export and deletion process. Revoking beta permission ends optional participation; it does not automatically erase records that must lawfully be retained. We will identify those records and their purpose. Material changes will be explained before they apply, with new consent where required; changes do not retroactively authorize new uses of previously collected data. Before normal service closure, provide a reasonable export opportunity where feasible. Urgent security or legal restrictions may require earlier suspension.

Rights and disputes. Contact support to seek a resolution; this does not restrict access to regulators or courts. These beta terms contain no mandatory arbitration, class-action waiver, transfer of a child's rights or broad user indemnity. Applicable mandatory consumer and privacy protections remain effective. A court's invalidation of one provision does not remove the remaining lawful provisions. English and Spanish are intended to have equivalent meaning; language discrepancies must not diminish nonwaivable rights.

2. Privacy notice and notice at collection

Who and how to contact us. [[OPERATOR_LEGAL_NAME]] is responsible for the processing described here. Privacy requests: [[PRIVACY_EMAIL]] or [[POSTAL_ADDRESS]]. Effective date: [[EFFECTIVE_DATE]]. This notice must be available before collecting the relevant data. Acknowledging that a notice was received is not blanket consent to every processing activity.

Collection, purposes and recipients. For the proposed hosted beta, the following schedule must be completed against the deployed system:

Information and source	Specific purpose	Limited recipients
Learner account identifier, email, age eligibility result and selected language, from learner/onboarding	Account access, eligibility, communication and language settings	Contracted account/hosting processors; authorized support
Guardian contact, verified relationship result and dated permission record, from guardian/verification process	Admit a minor and administer the agreed relationship	Contracted verification/account processors; authorized privacy staff
Uploaded PDFs, images, recordings and extracted text, from learner	Requested extraction, transcription and note creation	Only processors required for that selected function
Notes, additions, subjects, saved reading position and study activity, from learner and service	Study library, progress and user-requested synchronization	Contracted storage processors; limited guardian summaries if separately disclosed
AI questions, necessary source excerpts and generated responses	Explanations and safety checks	Listed AI/moderation processors; authorized reviewers only when necessary
A possible safety concern, category and review/delivery record	Evaluate a concern and perform the disclosed safeguarding process	Authorized reviewer and verified safe recipient as described in section 5
Minimal security logs such as time, IP address, error and account identifier	Abuse prevention, diagnosis and account protection	Hosting/security processors and authorized operators

Do not collect government identity documents, precise location, contacts, advertising identifiers or voiceprints by default. If a verification method requires additional information, disclose the minimum fields, provider, purpose and retention before collecting it. Voice recordings can contain sensitive personal information even when no voiceprint is created. Do not ask learners to upload medical records or other people's private information.

Storage modes. Browser storage can be lost when a device or browser is cleared. Export files remain wherever the user saves them and are not deleted by clearing the application. Current local processing sends requests to the local application server; it is not a promise that all processing occurs inside the browser. Before hosted use, replace this paragraph with the verified locations and data flows in [[PROCESSOR_REGISTER]], including whether each AI or speech function sends content to another provider. A Supabase account is not evidence that the prototype already backs up every note.

Restrictions. The proposed beta does not sell or share personal information for cross-context behavioral advertising, serve targeted ads, or use learner content to train general-purpose AI models. These restrictions must also bind the relevant vendors; an unreviewed free AI tier must not receive learner content. Necessary operational storage must be distinguished from optional analytics or marketing. Optional tracking cannot be enabled by accepting these terms. Any applicable separate choice must be offered before use.

Sharing. Do not publish libraries or give a guardian automatic access to the complete chat history. Disclose the exact progress fields and safety information shared before admission. Service providers may process only for documented purposes. Disclosures compelled by law or necessary to address a serious safety threat require an appropriate basis, minimum necessary data and documented review; notice is provided where lawful and safe. A change of operator does not itself authorize unrelated new data uses.

Retention and security. The published [[RETENTION_SCHEDULE]] must give a duration or intelligible criterion for each row above, including raw uploads, temporary files, model/provider logs, safety records, backups and consent evidence. Keep information only as necessary for disclosed purposes or applicable obligations. Identify deletion and backup expiration timing and any narrowly scoped legal hold. Encryption, access control and recovery claims must be supported by deployment evidence. No system can promise perfect security or recovery; this does not excuse reasonable safeguards or required incident notices.

Requests and choices. Request access, correction, export or deletion, withdraw an optional consent, or challenge a safety decision at [[PRIVACY_EMAIL]]. Depending on applicable law, additional rights may include opt-outs, restriction of sensitive processing and an appeal. Verify identity proportionately; do not demand unrelated sensitive documents. Explain a refusal and any applicable appeal route and respond within the applicable legal deadline. Do not discriminate for exercising a protected right. A guardian's authority and a learner's independent rights must be checked, not assumed. Any required state supplement must identify its exact scope and process before those residents are admitted.

Underage use and adulthood. Under-14 users are not admitted. If under-13 collection is discovered, stop further covered collection and apply the legally required COPPA response, including deletion or valid authorization where applicable; the age label alone is insufficient. At 18, reassess guardian access and obtain the adult user's authorization for optional sharing. School-record rights may transfer on a different applicable basis, including attendance at a postsecondary institution.

3. Guardian permission record

Proposed agreement; only after verification. I confirm I am the parent or legal guardian authorized to make this decision for learner [[LEARNER_REFERENCE]]. I have received the Terms, Privacy Notice, AI/Safety Notice and the exact parent-sharing summary in a language I understand. I understand the beta's limitations and give permission for the learner's participation and the processing necessary for the functions I approve. I do not grant permission for advertising, sale of data, public sharing, voice cloning or general-purpose model training.

I understand that the learner must also assent; participation is voluntary. I can ask questions and withdraw permission through [[SUPPORT_EMAIL]]. Withdrawal can end participation but does not waive statutory access or deletion rights. I understand which data are visible to me and that access to the entire private library or chat is not automatic. Safety flags may be wrong, and the service is not an emergency-monitoring service. A safeguarding review may need to use a different safe adult if disclosure to me could expose the learner to harm.

Record guardian name, verified account reference, relationship and verification receipt, learner reference, document versions, language, explicit decision and timestamp. An email confirmation or checked box alone does not establish guardianship. Do not retain identity-document copies unless necessary and specifically approved. Separate any optional feature choices. Provide the guardian a copy and a withdrawal route. This record is not a blanket waiver of the learner's rights and does not establish compliance with every state's minor-contract rules.

4. Learner assent — plain language

Notatky helps you understand schoolwork. It can explain a passage, make study notes and help you practice. It is AI, not a person, teacher or counselor, and it can get things wrong. Check important information in your class material or ask your teacher.

You choose what study material to add. Do not upload passwords, private information about classmates or recordings you do not have permission to make. You can correct your notes and ask for help deleting or exporting your information. Save an export of work you need to keep.

Your parent or guardian must approve this beta. Before you join, we will show exactly what information they can see. If a message suggests serious harm or another prohibited harmful request, the safety process may involve an authorized reviewer and a verified safe adult. A school question about biology, history or staying safe is not automatically a violation. A safety concern is not a diagnosis or proof that you did anything wrong.

The prototype does not currently send dependable parent alerts. Do not use it to get emergency help. You can stop participating or ask questions at [[SUPPORT_EMAIL]]. Saying yes does not give up your legal rights.

Proposed separate unchecked assent: “I understand these explanations, had a chance to ask questions, and want to join the beta.” Store the learner's own decision separately from the guardian's permission. Refusal must not silently become agreement.

5. AI acceptable use and safety/parent-alert notice

Scope. AI assistance is for education, academic development and study guidance. It should explain reasoning, use the available source material and support practice. It must not present unsupported output as a verified fact. Ordinary unrelated requests are redirected toward study.

Restricted assistance. The service must not provide erotic roleplay or sexual exploitation material; instructions enabling violence, self-harm, dangerous drug use or eating-disorder behavior; scams, credential theft or other harmful cyber abuse; targeted hate or extremist recruitment; or personalized medical, legal or financial directives. Calling a request “homework” does not make harmful instructions acceptable. Age-appropriate factual education about health, sexuality, history, literature or prevention remains eligible. Asking for help with abuse or distress must receive supportive guidance, not punishment.

Safety process proposed for launch. Potentially dangerous requests and credible safety concerns may create a restricted review event. An authorized process considers context, severity, uncertainty and whether the linked guardian is a safe recipient. When appropriate and lawful, send the verified guardian a minimal notice that a concern needs attention, with a secure route for further information; do not send full transcripts through email or SMS. A report that implicates the guardian requires an alternate safeguarding route, not automatic delivery to the alleged abuser. Any required reporting obligations must be assessed independently by the designated responsible person.

Honest status. This workflow is a launch requirement, not a claim of existing delivery. The current prototype does not provide verified guardian notifications. Before activation publish [[SAFETY_REVIEW_PROCESS]], including available hours, responsible team, escalation routes, recipient verification, delivery-failure handling, appeal and retention. Never label a queued or failed message as delivered. Tell families what is monitored and shared before use. Do not send an alert merely because an AI output was blocked or a learner asked an ordinary off-topic question.

Limits and support. Automated checks can miss concerns or flag harmless content. They are not diagnoses, disciplinary findings, continuous human supervision or guaranteed protection. In immediate danger in the U.S., call 911; for suicide or mental-health crisis support call or text 988. Seek a trusted safe adult directly. The service does not contact emergency responders merely because a user writes in the chat. Report an incorrect decision through [[SUPPORT_EMAIL]].

6. Recording, uploads and optional feedback

Before each recording. Obtain any required permission from the teacher, school and other participants before activating the microphone. Follow applicable recording law and school rules. A guardian's beta consent does not authorize recording other people. The product's default is permission from all affected participants, even where a narrower legal exception might exist. Stop when permission is absent or withdrawn and offer a text/upload alternative. The interface must clearly show recording, stop and discard controls.

Proposed just-in-time confirmation: “I have the permissions required to record and process this material for my private study. I understand this may include other people's voices.” This is the learner's confirmation, not proof that the other participants actually consented. School deployments must provide a practical mechanism to obtain and document required permissions.

Uploads and copyright. Upload only material you own or are permitted by the rights holder or law to use for the requested processing. Educational purpose alone does not automatically make every copying or upload lawful. Do not bypass access restrictions or upload exams contrary to school rules. Do not publish another person's work or recordings through this service. No voice cloning, impersonation or biometric identification is authorized by this agreement.

Feedback is optional. You may send suggestions or bug reports without including private student material. If you voluntarily submit feedback, you permit us to use the suggestion to improve the product without payment or attribution. This does not grant rights to market your name, likeness, recordings or private notes. A testimonial, research study, identifiable screenshot or public quote requires separate specific permission and, where applicable, guardian permission and learner assent. Ordinary beta participation is not consent to research.

7. Conditional vendor data-processing agreement

NOT EXECUTED — customize and sign with each provider before transferring real learner data. Parties: [[OPERATOR_LEGAL_NAME]] and [[VENDOR_LEGAL_NAME]]. Attach a completed processing schedule specifying services, duration, instructions, data categories, subjects, locations, approved subprocessors, security measures, retention and deletion. A public privacy policy alone is not this agreement.

The vendor shall process personal information only on documented lawful instructions for the scheduled service; maintain confidentiality and appropriate technical and organizational safeguards; restrict staff access by role; and prohibit sale, behavioral advertising, independent profiling and training of general-purpose models on the information. It shall not combine customer data for unrelated purposes. No sensitive learner content may be transferred to a free tier whose terms contradict these restrictions.

The vendor shall provide the information and assistance reasonably necessary for rights requests, security assessments, applicable impact assessments and regulatory duties. It shall notify the operator of a personal-data incident without undue delay and within [[AGREED_INCIDENT_NOTICE_PERIOD]], provide available facts and updates, preserve relevant evidence and cooperate on remediation. That contractual period must allow the operator to meet applicable legal deadlines; it is not a replacement for them.

Subprocessors must be disclosed, bound to equivalent obligations and subject to the agreed advance-notice and objection process [[SUBPROCESSOR_CHANGE_PROCESS]]. The vendor remains responsible for their contracted performance. At service end, return or delete data as instructed, including a documented backup-expiration process; identify any legally required retention and restrict further use. Provide deletion confirmation and appropriate audit evidence. Inform the operator of legally compelled disclosure where permitted and challenge requests when appropriate. Notify the operator if an instruction appears unlawful.

Complete agreement hierarchy, term, termination rights and liability allocation in [[VENDOR_MASTER_AGREEMENT]]. Add applicable state processor/service-provider clauses and transfer terms after counsel determines applicability. Signatures, authorized signatories and date: [[OPERATOR_SIGNATURE]] / [[VENDOR_SIGNATURE]] / [[DATE]]. This draft does not amend Supabase or any AI vendor's existing terms unilaterally.

8. Conditional school data-protection addendum

INACTIVE FOR DIRECT FAMILY BETA. Before school-directed use, identify [[SCHOOL_LEGAL_NAME]], authorized signatories, permitted educational purposes, student-record categories and the school's legal basis for disclosure. An educator's individual click is not assumed to authorize a district contract.

The operator shall process school-provided records only for the documented educational purpose and the school's lawful instructions, under the school's required direct control over use and maintenance where the FERPA school-official exception is relied upon. Do not use records for advertising, general-purpose model training or unrelated commercial purposes, and do not redisclose except as authorized by the school and applicable law. Support school-managed access and correction requests and the correct holder of education-record rights. Do not promise parents access to postsecondary records without checking authority.

Attach security, subprocessor, incident-notification, return/deletion and audit schedules consistent with section 7. Include state student-privacy requirements and district procurement terms for [[SCHOOL_STATE]]. Identify retention duration, contract-end export and deletion confirmation, school contact and complaint route. No integrations, rostering or school imports until the completed addendum is executed and controls are tested. This document is not a FERPA certification.

9. Copyright complaint procedure — publication draft

Send a copyright concern to [[COPYRIGHT_CONTACT]]. Identify the work, the material in this service and enough information to locate it, your contact details and the basis for your concern. Do not send unrelated children's private information. We review complaints, restrict access where appropriate and provide a route to contest errors. Repeated infringement may result in termination in appropriate circumstances.

Before representing this as a DMCA section 512 process, counsel must complete [[DMCA_AGENT_NAME_ADDRESS_PHONE_EMAIL]], register and publish the designated agent when required, and implement the statutory notice/counter-notice process. Qualifying notices require a signature, identification of the work and challenged material, contact information, a good-faith authorization statement and the required accuracy/authority statement under penalty of perjury. The operator must not treat an incomplete draft contact as a registered agent.

Counter-notices involve legal representations and disclosure of identifying information. Provide the verified statutory procedure and explain those consequences with an appropriate guardian process before requesting one from a minor. Do not automatically restore content on a made-up deadline; counsel must establish the applicable section 512 timing, lawsuit handling and records procedure before activation.

10. Future subscription and cancellation schedule

INACTIVE — NOT AUTHORIZATION TO CHARGE. This family-beta draft has no automatic paid conversion. The approved internal infrastructure budget of $100/month is not a customer subscription price and authorizes no charge to families.

Before selling a plan, show the adult purchaser [[PLAN_FEATURES_AND_LIMITS]], [[TOTAL_PRICE_AND_TAXES]], [[BILLING_INTERVAL]], [[TRIAL_AND_FIRST_CHARGE_DATE]], whether renewal is automatic, [[CANCELLATION_ROUTE]], the effect of cancellation and [[REFUND_POLICY]]. Obtain the purchaser's separate express informed agreement before billing; provide a durable confirmation. Do not make a minor the default payer or use prechecked purchase consent. A free beta must not become paid through silence.

Provide a working, simple cancellation process, required renewal/change notices and rights required by the purchaser's applicable state and sales channel. Cancellation of future billing, account deletion and refund requests are different actions and must be explained. Do not promise “no refunds” universally or rely on an outdated federal rule. Complete current federal/state subscription review before enabling checkout.

11. Acceptance, retention and release instructions — internal

Required order: show age-appropriate eligibility information → collect only needed eligibility data → verify the guardian relationship → give the guardian current documents and granular choices → obtain the learner's separate assent → enable only approved functions. Record document identifier, exact immutable version/hash, locale, actor/account and role, linked learner, decision, timestamp, verification receipt and later withdrawal. Keep an accessible copy for the family. Do not store sensitive chat text as consent evidence. No prechecked boxes. Privacy-notice receipt, contract acceptance and optional consent must be distinguished.

The retention schedule must resolve each category in section 2 with an owner, purpose, legal basis where relevant, collection trigger, active retention period, backup period, deletion mechanism and verification evidence. “Forever,” “until no longer needed” without meaningful criteria, and “deleted instantly everywhere” are not acceptable placeholders. Exercise access/export/delete, consent withdrawal and age-transition routes with synthetic accounts before real teens are invited.

Release evidence required: operator and working contacts; chosen launch jurisdictions reviewed in STATE-REVIEW.csv; complete processor register and signed necessary contracts; real guardian verification; owner-isolated storage; secure recovery and deletion; tested safety escalation and safe-recipient exception; truthful parent dashboard; verified recording permissions; no unauthorized training or tracking; EN/ES legal-equivalence review; approved final versions and accessible notices. A lawyer reviews applicable state teen privacy, minors' contracting, recording, student-record, consumer-health and breach-notification duties. A separate health-data notice/consent may be necessary if safety processing triggers applicable health-data law. Do not assume HIPAA is the only relevant health privacy law.

These documents may be prepared before the controls exist, but external teen enrollment remains closed until the documented launch gates pass. No agreement cures a missing safeguard or authorizes unlawful processing.

12. Primary sources and applicability — internal

Verified September 5, 2026. This is a selected-source map, not a completed 50-state review. Follow links for current official text; recheck before launch.

• COPPA: 14+ admission does not resolve child-directed design or actual knowledge of under-13 collection. Official source / Fuente oficial.
• CCPA/CPRA: Applicability thresholds and exceptions require review; state-specific notices, rights and minor sale/share rules cannot be replaced by general consent. Official source / Fuente oficial.
• FERPA: Review school-directed services separately from direct family use. Determine lawful record disclosure and institutional control. Official source / Fuente oficial.
• California recording / Grabación en California: Section 632 addresses confidential communications and consent; it is not a statement that every U.S. recording follows one rule. Review participant locations and exceptions. Official source / Fuente oficial.
• DMCA: Some safe-harbor claims require a published and registered designated agent, plus other statutory conditions. Registration has not been verified. Official source / Fuente oficial.
• ROSCA: Online negative-option sales require material disclosures, express informed agreement and simple cancellation; state requirements also need review. Official source / Fuente oficial.
• Washington My Health My Data: Inferred health information may be covered. Safety-event processing needs an applicability assessment before deployment; no blanket exemption is asserted. Official source / Fuente oficial.