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
- Parents and other adults: account and contact information supplied during account creation or support, authentication/session information, and records of invitations, permissions, terms acceptance, verification, consent, and withdrawal. These support account access, authorization, and privacy requests.
- Child profiles: a parent supplies a nickname, age band, and preset avatar. Children do not have independent email/password accounts. ReaderShip does not request exact birthdate, school, home address, child email, photos, or voice recordings.
- Reading information: parents, authorized sponsors, and child activity supply books, assignments, reading activity, goals, Reader Check responses/results, verified accomplishments, and rewards. These support family reading plans, progress, checks, and celebrations. Information linked to a profile can be personal information even without a real name.
- Sponsors: invited adult account/contact information, invitation relationships, book proposals, and encouragement support parent-authorized participation.
- Technical information: application/backend requests and sessions can involve IP addresses, device/browser details, identifiers, timestamps, and security/error logs to provide and protect access.
- Support: messages and information you choose to send us are used to answer questions and handle account/privacy requests. Please avoid sending child details or identity documents by email.
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.
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 LLCEmail: hello@jamdesign.io
Company website: jamdesign.io