StoryBee

StoryBee

Policies

Information about the terms and notices that apply to StoryBee.

Privacy Policy

1. Scope and accountability

This Privacy Policy explains how StoryBee Inc. (“StoryBee”, “we”, “us”, or “our”) handles personal information in connection with StoryBee.ca, StoryBee.Space, AP® Knowledge Prep for AP® Macroeconomics and AP® Microeconomics, and their associated reading and support features (together, the “Services”). StoryBee Inc. operates the Services, determines the purposes for which personal information is handled, and receives privacy requests.

West Solution Consulting Corp. and The National Research Institute for Democratized Learning publish or provide certain StoryBee content. They are not described by this Policy as operators of every Service or as having routine access to reader personal information. Information may be shared with a publisher only where reasonably necessary for a specific support, rights, safety, or legal matter and as permitted by law.

2. Public access and member accounts

StoryBee.ca currently offers public reading access without requiring a reader account or sign-up. We do not ask readers to submit an age, gender, school, or precise location merely to read the free illustrated books.

StoryBee.ca also offers member accounts, which are held by adults. An account holder may let a learner aged 13 to 17 study with the account under their supervision, as section 14 explains. Members sign in with a one time code that we send by email through Cloudflare Email Service, and can buy Subject Passes through Stripe, our payment processor. As members study, StoryBee records learning events to show progress, and members can choose to send weekly progress reports (the Progress Passport) to people they pick. Sections 4 to 7 describe what we store for members, and section 11 explains how long we keep it.

StoryBee.Space may provide separate account features using Squarespace authentication and may collect an email address, account identifiers, and authentication information needed for those features.

3. Information we may receive

When you use the Services, StoryBee and its providers may receive standard technical information such as IP address, browser and device type, operating system, requested pages or features, approximate region derived from an IP address, timestamps, security events, and request or diagnostic logs.

When a public StoryBee.ca book opens successfully, Cloudflare provides approximate network-location metadata to StoryBee at the edge. StoryBee immediately reduces available coordinates to an approximately one-degree map cell and does not store the raw IP address, precise coordinates, city, postal code, book-and-location pairing, or an individual event record. We store only the coarse cell’s aggregated open count and a rounded recent-activity time. A coarse area is included in the public map only after multiple opens have accumulated there.

StoryBee.ca also sends small, first-party resource-performance reports from the Landing page, Library, and Reader. These reports describe the resource or interface, not a person: aggregate visits and opens; visible-time durations; successful page exposures; use of selected Reader navigation, display, zoom, thumbnail, full-screen, information, and sharing controls; initialization and painted-exposure durations; and coarse load or feature-failure categories. A page exposure is reported only after the page image has loaded, decoded, and reached the rendered view. Visible time is measured with a monotonic browser clock only while the relevant page is visible, then contributed as a duration segment.

These resource-performance reports do not contain a reader, visitor, session, account, request, or device identifier; IP address or other network value; fingerprint; URL; client timestamp; precise or coarse location; or raw browsing or page-turn history. StoryBee does not attempt to link reports across requests or reconstruct an individual journey. The server assigns the current UTC time bucket and immediately adds each retained report to an aggregate counter or duration total; compatibility-only milestone reports from older cached Reader code are validated and discarded without storage. Book identifiers and page numbers are used only for the book, page-exposure, and reading-time aggregates that require them. Geographic aggregates are collected through the separate coarse map feature and cannot be filtered or joined by book, page, control, or resource-performance date.

We may also receive information you choose to provide, including support messages, rights reports, privacy requests, account information where an account feature exists, and related correspondence. Please do not include unnecessary personal information in a support request.

4. What we store for members

When you have a StoryBee account we store only:

  • your email address;
  • your display name, if you choose to add one;
  • your acceptance of the Terms, with the policy version and the time you accepted;
  • your sign in sessions;
  • your Subject Passes and the payment references Stripe gives us, described in section 7;
  • your saved progress, reading records, and study plan;
  • your learning activity, described in section 5, and daily summaries of it; and
  • exam dates you choose to enter.

We do not store IP addresses or browser details with your account. To limit abuse, we keep short lived, salted fingerprints that cannot be read back into an address.

Your email address is used to send sign in codes, account notices you ask for, and the progress reports you choose to send.

5. Study data and learning activity

As you study AP® Knowledge Prep, StoryBee saves study data to your account. This includes the readings and nodes you open, the practice questions you answer, the answer you chose, whether it was correct, and which wrong option you chose, along with your attempts, the time spent, and whether you opened a hint. It includes flashcard activity, the free response items you open, and the scores you give your own free response answers, which are labelled self reported. It includes your practice exam results, such as your section scores, and your timing and pacing, such as the time used on a section and on questions.

We use this to show your progress, suggest what to review next, show insights about your own study, and build your weekly summary and Progress Passport. This analysis runs only inside StoryBee’s own systems. We may also use de-identified information, which does not identify you, to understand how the Services are used and to improve the questions, explanations, and features.

6. Progress reports you choose to share (Progress Passport)

You may choose to send a weekly summary of your progress, called the Progress Passport, to people you pick, such as a parent or tutor. Each report contains:

  • your display name;
  • the period the report covers;
  • your study and reading time;
  • the nodes and gates you completed;
  • your accuracy by unit;
  • your latest Practice Exam score;
  • any FRQ scores you entered yourself, labelled self reported;
  • the books you read; and
  • your upcoming study plan items.

A report contains no link that signs anyone in, does not include your email address, and has no tracking pixels or other tracking.

Each recipient must confirm by email before any report is sent. Every report includes a one click unsubscribe link, and you can remove a recipient at any time.

7. Payments

Stripe processes all payments for StoryBee. When you buy a pass, you give your payment details, including your card number, to Stripe and not to StoryBee, and Stripe’s own privacy policy applies to that information. We do not receive or store your card number.

What we receive from Stripe is the payer email address, the amount, the currency, the payment status, and the reference numbers for the payment and the Checkout session, together with the subject you bought. We keep these with your Subject Pass so we can give you access and handle refunds and disputes. Stripe may also send you a receipt by email.

8. How we use information

We use personal information to operate and deliver the Services; provide account features, Subject Passes, progress, and progress reports; process payments and handle refunds and disputes; respond to support, privacy, and rights requests; maintain security and prevent abuse; diagnose technical problems; comply with legal obligations; enforce our Terms; and protect users, rights holders, and the Services.

We may use aggregated or de-identified information to understand whether StoryBee’s Landing page, Library, books, pages, and Reader controls are performing as intended; compare independent aggregate counts and visible-time segments; improve accessibility, reliability, content presentation, navigation, and features; and display the approximate global reading-activity map and estimated cumulative read count. Separate resource counts are presented independently rather than as a unique-reader conversion or tracked funnel. The map does not identify a reader or disclose which book was opened in an area. We do not sell or rent personal information.

StoryBee does not show advertising and does not use third party trackers.

9. Sharing and service providers

We may provide information to service providers that host, secure, authenticate, display, or support the Services; to authorities or other parties when required by law or reasonably necessary to protect rights, safety, or security; to a successor in connection with a lawful corporate transaction; or to another party at your direction or with your authorization.

Current providers include Cloudflare for StoryBee.ca hosting, storage, infrastructure, and security, Cloudflare Email Service for sending sign in codes, account notices, and progress reports, Stripe for payments, Squarespace for StoryBee.Space and its account features, and FlipHTML5 for certain book displays. Providers may process technical or account information in accordance with their services, agreements, and applicable policies. We seek to limit provider access to what is reasonably necessary for the relevant service.

Cloudflare Email Service receives the recipient’s email address and the message content so that it can deliver each email.

10. Cookies and local storage

The Services and their providers may use cookies, local storage, and similar browser technologies for security, sign in, preferences, acknowledgement of policy notices, performance, and temporary caching of public content. When you sign in, a secure session cookie keeps you signed in. AP® Knowledge Prep also keeps your progress and any unfinished practice exam drafts on your device so that your work is not lost. Details appear in our Cookies and Local Storage Notice.

11. Retention

Retention periods vary according to the type of information and why it is needed. We consider the duration of an account or support matter, security and fraud-prevention needs, provider settings, backup and logging cycles, legal obligations, dispute requirements, and whether information can be deleted or de-identified.

For member accounts, we keep data as follows:

  • Sign in codes: deleted 1 day after they expire.
  • Sign in sessions: deleted 7 days after they expire or are revoked, for example when you sign out.
  • Report recipients who have not confirmed: deleted after 14 days.
  • Learning events: kept for 24 months, then deleted.
  • Daily summaries of your activity: kept for as long as your account exists.
  • Inactive accounts: an account with no sign in for 24 months is deleted.
  • Payment records: kept for accounting, with your account details removed so they no longer identify you.

You can delete your account and data at any time from your dashboard. To request a copy of your data, email support@storybee.space.

The resource-performance feature does not retain individual reports or raw event histories. During daily maintenance, page-exposure aggregates older than 7 days in hourly form and older than 90 days in daily form are removed; other resource-performance aggregates older than 35 days in hourly form and older than 400 days in daily form are removed. Because cleanup runs once each day, deletion may occur during the following daily maintenance run. Completed UTC days are rolled into daily aggregates before the shorter-lived hourly rows are removed. New Reader builds do not create reading-milestone reports; previously accumulated milestone aggregates remain subject to the same ordinary retention schedule while older cached Reader code is accepted without adding new milestone rows.

The separate reading-activity map does not retain individual open records. Coarse cell counts may be retained as cumulative, aggregated statistics; each cell holds only its total and rounded latest-activity time.

When personal information is no longer reasonably required, we take reasonable steps to delete, de-identify, or securely dispose of it, subject to lawful retention, security, backup, and operational requirements.

12. Security

We use administrative, technical, and organizational safeguards designed to protect personal information, including encrypted connections, one time sign in codes, secure session cookies, and limits on who can reach stored data. We keep card details out of our systems by using Stripe. No transmission, provider, or storage system is completely secure, and we cannot guarantee absolute security. If you believe an account or personal information has been compromised, contact support@storybee.space.

13. Access, correction, and deletion requests

Subject to applicable law, you may ask whether we hold personal information about you and request access, correction, or deletion. You can change your display name and delete your account from your dashboard. We may need to verify your identity and authority before responding. Some information may be retained or withheld where permitted or required for security, legal obligations, fraud prevention, accounting, dispute resolution, or the rights of another person.

Send privacy requests to StoryBee Inc. at support@storybee.space. Please describe the Service and interaction involved so that we can locate relevant records.

14. Children

Our books are created or curated for children, but StoryBee accounts and memberships are held by adults. Children may read under adult selection and supervision but may not independently create or manage an account. Reading the free illustrated books does not ask a reader to submit their age.

An adult account holder may let a learner aged 13 to 17 study with their account under their supervision. When a learner uses an adult’s account, the study activity recorded belongs to that account. The adult can view it and delete it from the dashboard at any time, or email support@storybee.space to request a copy. We ask the adult to tell the learner what is recorded, as described in sections 4 to 7.

StoryBee does not knowingly collect personal information from children under 13, and no one under 13 may use member features or AP® Knowledge Prep.

Like other public websites, a child’s visit may generate limited technical information needed to deliver and secure the site. We do not knowingly ask children to submit profiles or direct support requests. If you believe a child has provided personal information directly to us without appropriate adult involvement, contact us so that we can review it.

15. International processing and third-party services

Providers, including Cloudflare and Stripe, may process information in Canada, the United States, or other countries where they or their infrastructure operate. Information may be subject to the laws of those jurisdictions, and courts and authorities there may be able to access it. Third-party websites and services have their own privacy practices, and we encourage you to review them before providing information.

16. Changes and contact

We may update this Policy to reflect changes to the Services, practices, providers, or legal requirements. Updates take effect when posted unless a different date is stated. Where required, we will provide additional notice or obtain consent before applying a material new practice.

Questions, concerns, or privacy requests may be sent to StoryBee Inc. at support@storybee.space.

Last updated: