Family reading, together

Privacy Policy

Effective date:
Version: RS-PRIVACY-2026-11-18

1. ReaderShip and this policy

JAM Design LLC operates ReaderShip’s marketing website at readershipapp.com and family reading application at launch.readershipapp.com. This ReaderShip-specific policy describes website processing separately from the application’s family workflows. It does not change other JAM Design products’ policies.

The application is an alpha. Adults may create empty family workspaces, but child onboarding remains blocked. Selection of a parental-verification method is intentionally deferred. Hosted parental-consent onboarding and audited alpha enrollment are unfinished. The family workflows below describe the intended parent-managed service; this page does not establish that family onboarding is ready or authorize child collection.

2. Website, signup, and cookies

The website’s adult updates form sends the email you enter, provider form fields, and any submitted honeypot fields to GoDaddy’s signup service. GoDaddy receives the request and associated network/browser information to process the signup. Joining this list is for product updates, not family enrollment or child-data consent. Please do not submit a child’s email. You can ask us to stop updates using the contact below.

The home page loads DM Sans from Google Fonts, which sends Google the network request, including an IP address and browser request information. Images, videos, and the Amatic SC font are served as website assets. Instagram, JAM Design, and application links lead to separate destinations when followed.

The inspected website source contains no analytics SDK, advertising scripts, cookie-setting code, or browser-storage use. This source audit does not establish what the hosting infrastructure or GoDaddy may log or set. Website delivery and provider requests may involve IP addresses, request times, browser/device details, and access/security logs. Browser cookie controls apply to provider cookies; application session storage is separate from this static website.

3. Application and support information

4. Purposes and limits

ReaderShip uses information to operate family accounts, maintain protected child sessions, organize reading, show authorized progress, support parent-reviewed Reader Checks, manage invitations and optional rewards, respond to support/privacy requests, and protect the service. Adult signup information is used for requested product updates.

There are no public child profiles, public leaderboards, advertisements, or child-to-child messages. ReaderShip does not sell personal information. Child participation must not require information beyond what is reasonably necessary for the activity.

5. Who receives information

Family and sponsors: parents manage private child profiles. Only invited adults with permission for a specific child may receive authorized progress, propose books, or send encouragement subject to parental controls. Optional sponsor sharing is a separate choice; declining it must leave the core family experience available. Parents can revoke access. Revocation cannot undo what a recipient has already seen.

Current backend: Supabase provides the deployed sandbox backend for application data and access. This is separate from website delivery. Authorized operator personnel may access information as needed for service support, security, or privacy requests.

Implemented but disabled integrations: OpenAI (AI Reader Checks), RevenueCat (purchase/subscription management), Resend (application email), and Expo push (notifications) exist in the application, but paid/live provider operation is currently disabled. Their presence in code does not mean they actively receive family data. Website signup via GoDaddy is a separate existing flow.

For future enabled AI checks, the intended provider payload uses permitted book/source context and excludes child names, emails, identifiers, and reading histories. This is not a guarantee about provider retention or model training. Provider processing, safeguards, and any additional disclosures must be reviewed and reflected in notice and required consent before activation.

Information may also need to be disclosed to comply with legal obligations or protect against misuse. Any such disclosure must be limited to its lawful purpose.

6. Retention and deletion

Retention must serve a specific purpose: adult signup information for requested updates; family profiles and reading records for the authorized reading experience; invitation records for access control; support and security records for the request or incident; and limited consent evidence for demonstrating authorization and withdrawal. Child information must not be retained indefinitely or reused for unrelated purposes.

Approved retention periods and operational deletion procedures have not yet been established for the alpha. This policy therefore makes no fixed deletion-deadline or backup-erasure promise. A purpose-based, timed retention schedule and tested deletion process must be approved before family onboarding.

Parents can request deletion using the contact below. Current deletion requests restrict access; they do not prove completed deletion from the database, backups, or vendors. Access restriction and confirmed erasure are different steps. We must verify request authority and report the actual status, including any necessary legal retention, rather than describe a request as completed erasure.

7. Security

ReaderShip’s design uses private profiles, protected child sessions, and parent-controlled access. No online system is completely secure. Credentials and invitations should be protected, and suspected unauthorized access should be reported through the contact below. Provider safeguards and the operator’s written security program require operational review before real-child enrollment.

8. Parent and adult controls

Parents can review child information, request correction or export, withdraw consent for further collection/use, revoke sponsor access, and request deletion. Contact hello@jamdesign.io from your adult account email and describe the request without sending sensitive child information. We may verify your authority through the adult account before releasing or changing records. Sponsors cannot use this process to obtain records outside their authorization.

Withdrawing consent stops authorization for further child collection/use and may make child features unavailable. Optional sponsor sharing can be stopped separately. Adults may also request access, correction, deletion, or stopping updates; additional rights may apply depending on location. The app team must complete and test the request workflow before family enrollment.

9. Location and service scope

ReaderShip is initially intended for US families in English. That does not establish that all processing stays in the US. No specific data-residency guarantee is made here.

10. Children and parental consent

ReaderShip is designed for parent-managed participation by readers approximately ages 6–14, including children under 13. Adults own family accounts; children use protected sessions. Before required child collection, parents must receive direct notice and complete a verifiable parental-consent process. Ordinary email confirmation, a checkbox, adult registration, or this static notice alone does not establish verified parental consent.

Terms acceptance, verified consent for core processing, and optional sponsor disclosures must be distinct. Optional sharing must remain off until separately authorized through the required verified process. Read the concise Notice for Parents for data and control choices. Real-child onboarding remains subject to completion of the application’s notice, consent, and operational requirements.

11. Policy changes

Approved versions will be posted here with their effective dates and preserved for review. Materially different child-data collection, use, or disclosure requires direct notice and renewed consent where required before the change begins. Continued use is not blanket authorization.

12. Operator and privacy requests

JAM Design LLC
Email: hello@jamdesign.io
Company website: jamdesign.io