Cookies and Local Storage Notice
1. Scope
This notice explains how StoryBee Inc. and service providers use cookies, local storage, and similar browser technologies in connection with StoryBee.ca, StoryBee.Space, and associated reading features.
A cookie is a small value a website or provider asks a browser to store and return with later requests. Local storage allows a website to store a limited value in the browser without automatically sending it with every request. Session storage works similarly but is limited to the browser tab’s current session.
2. StoryBee.ca policy acknowledgement
When you select “Agree and continue” on the StoryBee.ca policy notice, the site stores the key storybee.ca. and the current policy revision as its only value in your browser’s local storage. It does not store your name, age, identity, account, acceptance time, or browsing history.
The value remains until you clear site data, the browser removes it, or a later acknowledgement replaces it. If it is unavailable or does not match the current revision, the notice may appear again. This local acknowledgement helps avoid repeatedly displaying the same notice; it is not a server-side acceptance record.
3. Reading-content cache
StoryBee’s reading experience may use local storage to temporarily cache already-public educational or book-related content so that repeated views load efficiently. The current learning-content cache is bounded and generally expires successful entries after up to six hours and unavailable-content markers after up to ten minutes. It does not store reader credentials or a reader profile.
4. In-memory reporting safeguards
StoryBee’s first-party resource-performance reports and coarse reading-activity report do not use cookies, local storage, or session storage to identify a reader or preserve a report queue. The current page keeps only short-lived, in-memory state needed to avoid reporting the same book-open or reading milestone repeatedly while that page remains loaded. That state contains no persistent reader or device identifier, is not available to another tab or later visit, and disappears when the page is closed or reloaded.
Resource-performance reports are sent in small, bounded batches on a best-effort basis. They are not saved for later delivery and are not retried or polled. A blocked or failed report does not interrupt reading.
5. Security and authentication
Cloudflare, Squarespace, and other providers may use cookies or similar technologies for security, request integrity, fraud prevention, session management, and authentication where an account or authorized administrative feature exists. Blocking these technologies may prevent account or protected features from working.
6. StoryBee.Space and displayed books
StoryBee.Space currently uses Squarespace, and certain books may be displayed using FlipHTML5. Those providers may place or read cookies or similar technologies under their own applicable notices and settings. Their technologies can differ from the local storage used directly by StoryBee.ca.
7. Aggregate performance measurement and advertising
The resource-performance measurement and coarse reading-activity map described in the Privacy Policy are first-party aggregate features. They do not use advertising cookies, third-party analytics scripts, persistent identifiers, fingerprints, raw event histories, or browser storage. StoryBee.ca does not currently intentionally place advertising cookies through its own Landing, Library, or Reader code. If we introduce optional analytics, advertising, or another non-essential tracking technology, we will update this notice and provide any notice or choice required by applicable law before using it.
8. Browser controls
Most browsers allow you to inspect, block, or clear cookies and site storage. Clearing StoryBee.ca storage will remove the policy acknowledgement and temporary public-content caches, so notices may reappear and public content may need to load again. It does not clear or reset a persistent telemetry identity because StoryBee’s current first-party aggregate reporting creates none. Blocking essential provider technologies may affect security or account features.
9. Changes and contact
We may update this notice as the Services and technologies change. Questions may be sent to StoryBee Inc. at [email protected].