Privacy Policy
Beadbar is made by Aprative LLC (“we”). This policy covers the Beadbar website and app.
The short version
- Adults use Beadbar. Children never have accounts and never sign in.
- A school’s data belongs to the school. We use it only to run Beadbar for that school.
- We do not sell data, show ads, or train artificial intelligence on your data.
- Our public sales pages measure visits so we can see what brings people to Beadbar. Signed-in pages never run that measurement, and children’s information never goes into it.
- Beadbar’s data is stored in the United States.
- A school can download or delete its data at any time. Anyone can delete their own account.
Our role
- School accounts: we handle data on the school’s behalf and follow its instructions, as the School Data Agreement sets out. That agreement controls if it differs from this policy. For a school covered by the federal student privacy law (FERPA), we act as a “school official” under the school’s direct control.
- Family accounts (for teaching at home): the parent who sets up the account controls it and enters their own children’s information. We use it only to provide Beadbar to that family, as this policy describes.
- Accounts without a school or family: we decide how your account data is used, as this policy describes.
What we collect, why, and how long we keep it
We collect only what is listed here. Before we collect anything new, we update this policy. Before we collect a new category of school data, we tell schools first, as the School Data Agreement describes.
| Data | From | Why | Kept |
|---|---|---|---|
| Name, email address, state | You | To sign you in, show the right standards, and email you about your account | Until you delete your account |
| Google account ID and profile photo address | Google, if you sign in with Google | To sign you in and show your photo next to your name | Until you delete your account |
| Counts of recent sign-in attempts and invites sent, by IP address, email address, or account, each stored as a scrambled code that can’t be turned back into the address | Your browser and your use of the app | To block repeated sign-in attempts and stop invites being used to send unwanted email | 1 day |
| Your confirmation that you are 18 or older, and which versions of these documents you accepted, when, from which IP address and browser | You and your browser | To show what was agreed | While your account exists, then until 3 years after you accepted |
| Sign-in sessions: IP address and browser | Your browser | To keep you signed in and to detect misuse | Until the session ends, at most 30 days after your last visit |
| Sign-in codes | Us | To sign you in | Work for 10 minutes; stored only in a form that cannot be read back; deleted by the next daily cleanup |
| Two-step sign-in, if you use it (school staff must): your passkeys (a public key from your device; your face or fingerprint never leaves the device) and your backup codes (stored only in a form that cannot be read back) | You | To check your second step when you sign in | Until you remove a passkey, turn two-step off, or delete your account |
| Which children’s records and reports each person opened or downloaded, and when (staff and family members alike) | Your use of the app | So the head of school can see who looked at or downloaded a child’s records | 1 year, or until the school is deleted |
| Emails we send | Us | To sign people in, invite staff and family members, tell family members a report is ready, and tell you about your account | Our email service keeps a copy up to 45 days |
| Favorites | You | To build your binder | Until you remove them or delete your account |
| School name, state, and settings, including the school’s skills checklist | The head of school | To run the school’s account | Until the school is deleted |
| Billing for a paid plan: the payer’s name, email address, billing address, card, and any discount code used | The person paying, on Stripe’s payment page | To take payment and work out sales tax | Stripe holds these; we never see card numbers. Stripe keeps payment records as tax and financial laws require |
| The plan, its status and renewal date, the number of classrooms paid for, and Stripe’s account numbers for the school or family | Stripe | To know which features the account has paid for | Until the school or family account is deleted |
| A school’s answer to “Is your school exempt from sales tax?” | The head of school | So we ask once and remind only until it is answered | Until the school is deleted |
| A school’s sales-tax exemption certificate: the organization’s legal name and address, type of organization, reason for exemption, state, exemption ID number, the school’s confirmation that it pays from its own funds, and the name and title of the person who signed it, with the time it was signed and revoked | The head of school | To leave sales tax off the invoices the exemption covers, and to keep the record tax law requires of us as the seller. Stripe is told only whether the next invoice is exempt | While it is in effect. After the school revokes it, or the school is deleted, 5 years, then deleted |
| Charter plan waitlist: your name, email address, and school name | You, on the waitlist page | To email you when the Charter School plan opens, and to gauge interest | 2 years after you last joined, or sooner if you ask |
| Staff: name, email address, role, classrooms | The head of school and staff | So each person sees only what their role allows | Until the person leaves the school, or the school is deleted |
| Staff training progress: items studied, presentations a staff member is signed off to give, and who signed them off | Staff and guides | To train new staff | Until the person leaves the school, or the school is deleted |
| Staff invites: email address, role, classrooms | The head of school | So staff can join | Links work for 14 days; the record is deleted 30 days after that |
| Family members the school invites: name, email address, and which child they can see | The school, and the family member when they sign up | So a family can see their child’s progress and shared reports | Until the school removes them, they leave, or the child or school is deleted |
| Family invites: email address and child | School staff | So a family member can join | Links work for 14 days; the record is deleted 30 days after that |
| Children: name, preferred name, birthdate (optional), classroom, and an ID from another system if the school imports one | School staff, or the parent in a family account | So guides can plan and record lessons | Until the school deletes the child or the school |
| Lesson records, weekly plans, notes, skills checklist ticks (skills a guide has seen a child do, including social-emotional and movement skills, with dates), and family reports, with a saved copy of each finalized version (a title, dates, the guide’s words, reading level and current book, conference date, and teacher’s name) about a child | School staff | To plan lessons, track each child’s progress, and report it to the family | Until the school deletes the child or the school. A lesson mark that staff remove is archived for 2 years so it can be restored, then deleted |
| Change log: who added, changed, or removed a record, and which fields (never the values) | Our system | So the school can see who changed a record | Until the school is deleted |
| Deletion records: what was deleted, when, at whose request, and how many records (no names or content) | Our system | To confirm a deletion when asked | While we operate Beadbar |
| Visits to the public sales pages (home, pricing, the charter waitlist, and sign-in): a random visitor ID, pages viewed, the page, link, or ad that sent you, and browser type | Your browser, through getem’s script | To see which pages, searches, and ads bring people who sign up | getem keeps the visitor ID cookie up to 400 days; see “Measuring where customers come from” |
| For account holders other than family members a school invites: how you heard about us (if you answer), and when you sign in, start a trial, record your first lesson mark, or pay, with the plan and amount | You and your use of the app | To see which marketing brings people who use and pay for Beadbar | getem holds it under its own retention schedule |
The Data Retention and Deletion Policy gives the full schedule.
Children’s privacy
Beadbar is not directed to children and does not let children sign in. Adults at a school enter children’s information for the school’s educational use only, under the school’s authority. In a family account, a parent enters their own children’s information, and can see, correct, download, or delete it at any time. If we learn that a child has made an account, we delete it.
A school can give a child’s family members read-only access to the child’s progress and the reports it shares. Family members never see staff notes, plans, or other children.
A parent who wants to see, correct, download, or delete their child’s information should contact the child’s school. The school can do each of these in Beadbar, and we help the school within 30 days of its request, or sooner if the law sets a shorter deadline. If a parent writes to us, we pass the request to the school.
How we use data
We use data only to provide, secure, and support Beadbar, and to tell account holders about their account and the service.
We never:
- sell, rent, or trade personal data;
- show ads in Beadbar, use children’s or family members’ data for marketing or to target ads, or build profiles of children, families, or staff for any purpose other than running Beadbar or measuring our own marketing as described below;
- put tracking, analytics, or session-recording tools on signed-in pages, or anywhere children’s records appear;
- use your data or any child’s data to train or build artificial intelligence models, including data with names removed;
- try to identify a person from data that has had identifying details removed.
Measuring where customers come from
We use getem, a marketing measurement service run by our own company, Aprative, to see which pages, searches, links, and ads bring people who sign up and pay.
- On the public sales pages only. getem’s script runs on the home pages, pricing, the charter waitlist, and the sign-in pages, and only when you are not signed in. It records a random visitor ID, the pages you view, the page, link, or ad that sent you, and your browser type. It never runs on signed-in pages, so it never sees children’s records.
- When you create an account, we tell getem your account number, your email address, the visitor ID from your browser, and your answer to “How did you hear about us?” if you give one. When you set up or join a school, we also tell it the school’s name and account number. Later we tell it, with only your account number, when you sign in, start a trial, record your first lesson mark (not which child or lesson), or pay (the plan and amount).
- Never children or invited family members. No child’s name, age, or records, and nothing about family members a school invites to see a child, is sent to getem.
- Ads. If we connect an ad account (Meta, TikTok, Snap, or Google Analytics), getem tells that platform when a visitor who came from one of its ads signs up or pays, with a one-way scrambled (hashed) email address, so we can see which ads work. Visitors in Europe are asked first, and nothing goes to an ad platform for them unless they accept advertising cookies. Wherever you are, a Global Privacy Control signal from your browser turns this off. We never use ad platforms to show ads to children.
getem’s own privacy policy describes how it stores this data. It is in the Outside services list.
Artificial intelligence
Beadbar does not use artificial intelligence on your data. Before we add any feature that does, we will: list the service that runs it on Outside services; require that service not to keep the data or train on it; use it only to serve the school or account holder the data belongs to; let each school turn it off; and treat it as a material change under “Changes” below.
Who else handles data
A small number of outside services help run Beadbar, such as hosting, email, and card payments. Each handles data only on our instructions and is bound by a written agreement to protect it and not sell it. The Outside services page lists each one, what it handles, and where. We add a service to that page, and email heads of school, at least 30 days before it handles school data.
We share data with anyone else only when the school directs us to, or when the law requires it, such as a court order. If the law requires us to hand over a school’s data, we tell the school first unless the law forbids it.
If Aprative or Beadbar is sold or merged, the new owner must keep the promises in this policy and the School Data Agreement for data we already hold. We tell schools as the School Data Agreement sets out.
Cookies and data on your device
Beadbar uses the cookies it needs to work: to keep you signed in, to complete Google sign-in, to remember which school you are working in, and to tell public pages that you are signed in and whether your account is on a paid plan (so they don’t show you offers you can’t use).
The public sales pages also set getem’s measurement cookies when you are not signed in: kit_vid (a random visitor ID, 400 days), kit_attr (how you first arrived, 90 days), kit_click (the last ad click ID, 90 days), kit_cid (the campaign code of this visit, 12 hours), and kit_consent (your advertising cookie choice, 365 days). Visitors in Europe see a notice that asks before advertising cookies are used. getem honors the Global Privacy Control signal; “Do Not Track” signals change nothing. Signed-in pages set no measurement cookies.
So that recording works without a connection, the Record screen keeps a copy of your classroom’s children and marks, and any marks not yet sent, on your device. Signing out removes it.
Security
Data is encrypted while it travels and while it is stored. The database itself keeps each school’s data separate, and staff see only what their role allows. If a breach affects a school’s data, we notify the school within 72 hours of confirming it. Security has more.
Your choices and rights
- See or download: a head of school can download all school data and any child’s record.
- Correct: staff can correct records their role allows them to edit. Anyone can correct their own name and state on Your account.
- Delete: a school can delete a child or the whole school, and anyone can delete their own account. The Data Retention and Deletion Policy says how long each takes.
- Ask us: write to privacy@aprative.com. We answer within 30 days. We may ask you to confirm who you are first.
These choices are open to everyone, wherever you live.
Changes
We post each version here with its date and a change log. Before a material change, such as a new use of data, we email account holders at least 30 days ahead and ask you to accept again at sign-in. A change never applies to data collected before it without the consent of the school, or of the account holder for an account without a school.
Contact
Aprative LLC · privacy@aprative.com · 1674 N 840 W, Salem, Utah 84653
Change log
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-09-25 | First version for the pilot. |
| 1.1 | 2026-09-26 | Added our mailing address. |
| 1.2 | 2026-09-26 | Paid plans: added the billing details Stripe handles for the person paying, and the plan details we keep. |
| 1.3 | 2026-09-27 | Added sales-tax exemption certificates that schools file, and the setup question about tax exemption. |
| 2.0 | 2026-09-27 | Skills checklists: the skills a guide ticks for a child, including social-emotional and movement skills, and the new family report details (reading level, current book, goals, suggestions for home, conference date, teacher’s name). Sales-tax exemption certificates also record the school’s confirmation that it pays from its own funds. |
| 2.1 | 2026-09-27 | Family reports: a saved copy of each finalized version, so what a family was given never changes. |
| 2.2 | 2026-09-28 | Sign-in and invite limits also count by email address and account, stored only as scrambled codes and deleted after a day. |
| 2.3 | 2026-09-30 | Two-step sign-in with a passkey (required for school staff), and a record of who opened or downloaded children’s records, which heads of school can see. |
| 2.4 | 2026-10-03 | The charter plan waitlist, and discount codes on a paid plan. |
| 2.5 | 2026-10-03 | A cookie that tells public pages whether the account is on a paid plan. |
| 3.0 | 2026-10-25 | Measuring where customers come from with getem: visits to the public sales pages, and sign-ups, sign-ins, trials, first lesson marks, and payments by account holders (never family members a school invites). An optional “How did you hear about us?” question at sign-up. Never children’s or invited family members’ data, and never on signed-in pages. |