Privacy Policy

1. Information We Handle

Account and communications

We handle information such as:

• the adult account holder’s email address;
• account confirmation, sign-in, and email-preference information;
• waitlist or checkout information submitted before an account is completed; and
• messages, feedback, support requests, and privacy requests.

RWB uses email-based sign-in. We store authentication and session records needed to operate and protect the account.

Child and family content

Information provided through a family account can include:

• a child’s name, character/avatar, and optional birth date;
• reading, writing, building, activity, challenge, progress, reward, and project information;
• attendance, Learning Log entries, Highlights, curriculum, weekly goals, progress reports, and parent narratives;
• dates, subjects, duration, location, organization, notes, titles, and links; and
• photos, work samples, certificates, project images, and other uploaded media.

Free-text fields and photos can contain more information than RWB requires. Please submit only information you are authorized to provide and that is reasonably useful for your family’s use of the service.

Subscription and payment information

RWB and Stripe handle information related to checkout and membership, including the checkout email, offer, trial and subscription status, cancellation status, amounts, dates, limited referral or campaign information, and Stripe customer, checkout, subscription, and invoice references.

Stripe hosts payment collection. RWB does not store complete payment-card numbers or card security codes in the application database.

Technical and usage information

When the website or service is used, RWB and its providers may process:

• IP address, browser or device information, user agent, request time, and requested page;
• referring page and limited campaign parameters;
• timezone, theme, session, checkout-continuity, and other necessary cookie or browser-storage information;
• authentication, security, rate-limit, application, and operational logs; and
• delivery, bounce, complaint, unsubscribe, and, where enabled, limited email-engagement information.

Feedback submitted from a signed-in account may also include the account email, the page or context from which feedback was sent, timezone, user agent, and IP address.

2. How We Use Information

We use information to:

• create, authenticate, secure, and support the adult-managed account;
• provide Homeschool Records, Activity Hub, Challenges, reports, uploads, and related family features;
• organize information by child and school year;
• process checkout, trials, subscriptions, billing, cancellation, refunds, and account access;
• send sign-in, account, billing, cancellation, weekly recap, onboarding, and support messages;
• respond to feedback, privacy, security, and legal requests;
• prevent abuse, fraud, duplicate subscriptions, and security incidents;
• troubleshoot and improve RWB;
• measure public-site acquisition and checkout performance; and
• comply with law and protect users, RWB, and others.

We do not intentionally use private child or family record content or private product-page activity to build advertising audiences.

3. Analytics, Cookies, and Similar Technologies

Necessary website technology

RWB uses cookies or browser storage for sign-in sessions, security, timezone display, theme preferences, checkout continuity, and limited interface state. Disabling necessary cookies may prevent account, checkout, or security features from working.

Google measurement on public pages

RWB uses Google Analytics on approved public marketing, public-content, and checkout pages, and Google Ads measurement on approved public marketing and checkout pages. Google may receive information such as the public page URL, page title, referrer, campaign parameters, browser or device information, network information, cookies or similar identifiers, and limited conversion data.

RWB is designed not to load Google Analytics or Google Ads tags on signed-in account, feedback, child, Activity Hub, Challenge, signed-in Homeschool Records, family-record, or admin pages. We do not authorize private family records, photos, account emails, authentication tokens, or Stripe identifiers to be sent through those Google tags.

Limited server-side product analytics

RWB uses a limited server-side PostHog integration to understand whether families can get started and use core recordkeeping features. It is limited to six actions: account creation, adding a child, adding curriculum, creating a weekly goal, opening a new Learning Log entry, and saving a new Learning Log entry.

These events include the time, a random event identifier, an environment/schema label, and a stable coded account identifier. The two Learning Log events also include limited labels describing where the editor was opened and a random attempt identifier. The coded account identifier is pseudonymous, not anonymous.

The event payload does not include names, email addresses, raw account or child IDs, child details, record text, photos, media paths, private URLs, or browser identifiers. This integration does not use a browser SDK, automatic click or pageview capture, session replay, or advertising-audience synchronization. RWB asks PostHog not to add location data to these events, and PostHog’s project-wide setting to discard client IP data from events is on. That setting does not establish retroactive deletion, absence of transient processing, or absence of IP addresses in provider operational logs. Project-level GeoIP behavior and operational IP/log retention remain unverified, so RWB does not claim that PostHog never processes IP information.

4. When We Provide Information to Others

We use service providers to operate RWB. Depending on the feature, these include:

• Fly.io for application, database, networking, and operational infrastructure;
• Tigris for private family-media storage and separate public asset storage;
• Stripe for hosted payment collection, subscriptions, billing, refunds, and the customer portal;
• Mailgun and Customer.io for authentication, account, recap, onboarding, and lifecycle email;
• Google Analytics and Google Ads for approved public-page and checkout measurement;
• PostHog US Cloud, after the approved rollout, for the limited server-side product analytics described above; and
• Slack and other internal tools for limited operational, support, security, or billing alerts.

These providers receive information reasonably needed for their role and may process it under their own terms and legal obligations.

We may also provide information:

• when the adult account holder directs us to do so;
• when reasonably necessary to comply with law or valid legal process;
• to investigate fraud, abuse, security incidents, or violations of our terms;
• to protect the rights, safety, property, or integrity of users, RWB, or others; or
• as part of a merger, financing, reorganization, sale of assets, or similar business transaction, subject to applicable law.

RWB does not currently offer public child profiles, child-to-child messaging, public comments, or public posting of private family records.

5. Children and Family Use

RWB accounts are intended to be created and managed by an adult parent, legal guardian, or other adult authorized to provide information about the children included in the account.

Activity Hub is kid-focused and designed for family use within a parent-managed account. Parents may record activities for younger children. With parent or legal-guardian supervision, children may use Activity Hub to log their own activities and save projects and photos in the shared family account.

The adult account holder decides what information the family may provide, supervises use, and remains responsible for account settings, privacy and support requests, formal homeschool records, deletion, and billing.

RWB does not provide separate child credentials or technical parent/child roles. The shared signed-in session therefore does not distinguish whether an adult or child typed, uploaded, clicked, or submitted information.

If you believe information was provided without appropriate parent or legal-guardian authorization or supervision, contact hello@readwritebuild.com. We will review the situation and take appropriate steps based on the facts and applicable law.

6. Retention

For lean v1, RWB’s founder handles privacy-request intake, requester verification, case coordination, and periodic family-content reviews through a manual process. RWB does not offer a self-service or fully automated export/deletion system.

RWB plans to retain child and family records and media while paid access is active and generally for no more than 24 months after paid access ends, unless the verified adult account holder requests earlier deletion or a longer period is reasonably needed for a legal, security, dispute, or specifically requested record-preservation reason. Canceling a membership does not immediately delete the account or saved family content.

The 24-month family-content rule does not automatically apply to every other record. We may keep minimized billing, tax, fraud, dispute, legal, security, email-suppression, support, and privacy-request records for as long as reasonably needed for those purposes. Authentication records, operational logs, queued jobs, email-provider information, and analytics data follow their operational needs and verified provider settings where applicable.

If limited PostHog analytics is enabled, its current Free plan makes analytics events queryable for one year. That vendor plan rule is not a guaranteed physical-deletion date, and RWB has not verified a separate automatic retention period for PostHog profiles. Provider documentation indicates that deleting analytics events requires an express event-deletion step in addition to person deletion and completes asynchronously.

Deleted information may remain for a limited time in backups, logs, queued systems, or provider systems until normal rotation or a supported deletion process completes. We do not promise immediate or guaranteed erasure from every backup or provider system.

7. Access, Correction, Export, and Deletion Requests

The verified adult account holder may contact hello@readwritebuild.com to ask about, access, correct, receive a copy of, or delete account and family information.

RWB’s founder handles intake, verification, and case coordination through hello@readwritebuild.com. RWB will usually verify account control through the signed-in account or the current account email and does not ordinarily ask for government identity documents. There is no automatic complete-account export or deletion workflow. Available formats and scope depend on the request, the systems involved, supported provider tools, applicable law, and information RWB must retain.

For a deletion request, RWB will use reviewed, scoped steps available in systems it controls and relevant supported provider workflows. RWB will state what was completed, retained, pending, or unavailable rather than promise complete erasure. It may retain minimized information needed for billing, tax, fraud, disputes, legal holds, security, suppression, or proof that a request was handled.

Canceling a subscription does not itself request deletion. If you want both cancellation and deletion, please say so clearly.

You may unsubscribe from optional email through the method included in the message or by contacting us. Service-related messages, such as sign-in, security, billing, or request-completion messages, may still be necessary.

Depending on where you live, applicable law may provide additional privacy rights. Contact us to make a request or ask a question.

8. Security

RWB uses administrative, technical, and organizational measures intended to protect information in light of the service’s size and the information involved. Those measures include account controls, email-based authentication, private media storage with time-limited access links, and Stripe-hosted card collection.

No storage or transmission method is completely secure, and we cannot guarantee absolute security, uninterrupted availability, or that information will never be lost or accessed improperly. Protect sign-in links and codes, and contact hello@readwritebuild.com if you suspect unauthorized access or another security issue.

9. United States Scope

RWB is currently intended for users in the United States. The public website may be reachable elsewhere, and providers may process information in the United States or other locations where they operate. RWB is not currently offered as a service designed to satisfy non-U.S. localization or privacy-law requirements.

10. Changes to This Policy

We may update this Policy as RWB, its providers, its practices, or applicable law changes. We will post the revised version with a new effective date and provide additional notice when reasonably appropriate or legally required.