Operator: RileyQuest LLC (“RileyQuest”, “we”, “us”)
Contact: privacy@riley-quest.com
RileyQuest is a family app that helps a parent track a child’s reading, chores, and earnings. This policy explains what we collect, why, and the rights you and your child have. We designed RileyQuest to collect as little about children as possible and we never sell personal information or use it for advertising.
Who our service is for
RileyQuest accounts are created and controlled by a parent or legal guardian who is 18 or older. Children use the app only through a child profile that a parent sets up. We do not knowingly let children create accounts, make purchases, or provide personal information directly to us beyond what they enter inside their own quest (reading progress and summaries).
Information we collect
From the parent (account holder)
- Name and email address (for sign-in, account recovery, and notifications).
- Subscription status and a billing reference. Payment card details are handled by our payment processors (Apple, Google, or Stripe) and are never stored by RileyQuest.
About the child (entered by the parent or child)
- The child’s first name and birth year(used to personalize the child’s screen — e.g. “{Name}’s Quest” — and to gauge age-appropriate reading level).
- A login username and PIN for the child’s profile (the PIN is stored only as a one-way hash).
- Reading activity the child enters: books, pages read, and short summaries of what they read.
- Chore completions, a pet-reminder timer, and an earnings ledger (an in-app tally — see “Earnings are not real payments” in the Terms).
- If a co-parent is added for the child, the custody schedule the parents set (which days the child is with each parent), used to route chores to the correct household.
- Dictionary words the child looks up in the word explorer (stored so the parent can see what was searched, and used for the word game).
- If the child turns on the optional reading reminder on a device, a push-notification subscription for that device (it can be turned off on the same screen at any time, and we delete subscriptions that stop working).
Automatically
- Basic technical and security data (e.g., session cookies, IP address, device and app-version info, error logs) needed to operate and secure the service.
We do notcollect a child’s email, phone number, precise location, photos, or contacts, and we do not use advertising or third-party tracking SDKs in the child experience.
How we use information
- To provide the service: track reading, chores, and earnings, and personalize the child’s screen with their first name.
- To analyze reading comprehension: when a book is marked complete, an AI model reviews the child’s own session summaries against the book to flag possible skimming to the parent. It never makes the final decision — the parent does.
- To send the parent notifications (e.g., a daily summary) to their email, and — only if the child turned it on — an evening reading reminder to that child’s device.
- To process and manage subscriptions.
- To secure the service, prevent abuse, debug, and comply with law.
Verifiable parental consent (COPPA)
Because RileyQuest knowingly collects limited information from children under 13, we obtain verifiable parental consentduring setup before any child data is collected. The consenting parent, the consent method, and the disclosure version are recorded. A parent may review the child’s information, refuse further collection, or request deletion at any time (see “Your rights”).
How we share information — and how we don’t
We do not sell personal information, and we do notshare it for advertising or for others’ marketing. We share data only with service providers (“subprocessors”) who process it on our behalf under contract, and only as needed to run RileyQuest:
| Provider | Purpose |
|---|---|
| Supabase | Database, authentication, storage |
| Vercel | Application hosting |
| Resend | Sending notification emails to the parent |
| Google (Gemini API) | Reading-level and comprehension analysis |
| Open Library (Internet Archive) | Book search — receives the search terms typed in the book finder |
| Free Dictionary API (dictionaryapi.dev) | Word definitions — receives the word the child looks up |
| Browser push services (Google, Apple, Mozilla) | Delivering the optional reading-reminder notification to a device |
| Stripe | Web subscription billing |
| RevenueCat | Subscription entitlement management |
| Apple / Google | In-app subscription billing (mobile apps) |
We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer (with notice).
Sharing within your family
Adults the family owner invites can see a child’s information according to the role and permissions the owner gives them:
- Helpers (such as a grandparent or another adult in the home) see only what the owner allows — for example, reading progress but not chore approval.
- Co-parents.The owner can invite a child’s other parent to co-parent a specific child. A co-parent has their own household with its own chore list and earnings tally for that child, and can view the child’s shared reading activity. The custody days the parents agree on (a repeating schedule and one-off day swaps) are stored so each day’s chores are routed to the right home. A co-parent must approve the child’s content-safety filters before any loosened setting takes effect. Co-parents are invited by email and use RileyQuest free — the family owner’s subscription covers the child.
One adult can belong to more than one family (for example, running their own family while co-parenting a child in another); each family’s data is kept separate. These visibility rules are enforced in our database, not just hidden in the interface. For a plain-English overview of accounts and roles, see our Help page.
International data transfers
RileyQuest is offered in multiple countries and languages. Information may be processed in the United States or other countries where we or our subprocessors operate. Where required (e.g., for EU/EEA/UK users), we rely on appropriate safeguards such as Standard Contractual Clauses.
Data retention and deletion
- We keep information for as long as the account is active.
- A parent can delete a child profile or the entire family account at any time from the dashboard. Deleting a child removes that child’s reading logs, summaries, chore records, and earnings ledger. Deleting the family removes all associated data.
- We may retain limited records as required for legal, security, or accounting purposes (e.g., billing records), then delete or anonymize them.
Your rights
Depending on where you live, you (the parent) may have the right to access, correct, delete, export, or restrict processing of your and your child’s information, and to withdraw consent. Under COPPA, a parent may review the child’s personal information, direct us to delete it, and refuse to permit further collection. Under GDPR/UK GDPR, you also have the right to lodge a complaint with a supervisory authority.
To exercise any right, contact privacy@riley-quest.com. We may need to verify that you are the account-holding parent before acting.
Security
We use measures such as encryption in transit, hashed credentials, row-level database access controls that isolate each family’s data, and least-privilege access. No system is perfectly secure, but we work to protect your information and will notify you of a breach as required by law.
Changes to this policy
We may update this policy. If we make material changes, we will notify the parent (e.g., by email or in-app) and update the effective date. For changes that expand the collection or use of a child’s information, we will obtain new parental consent where required.
Contact
Questions or requests: privacy@riley-quest.com
RileyQuest LLC, 212 N. 2nd St., STE 100, Richmond, KY 40475