Help center

readolia / Legal & trust

Cookie policy

Cookies, local storage and tracking transparency

Last reviewed for the beta: 9 October 2026

This is a beta cookie disclosure based on the readolia source-code audit. It is not a complete live-browser cookie inventory.

What these technologies do

Cookies and browser storage can preserve an authenticated session, keep a necessary user preference or support technical operations. Similar technologies such as localStorage can store tokens.

Strictly necessary authentication storage

The Base44 SDK supports authentication and uses session/browser storage. The app code references localStorage keys such as base44_access_token and token for session handling.

A sidebar component contains optional sidebar-state cookie code. This does not establish that it is loaded on every page. The exact domains, lifetimes and classifications must be verified in a browser after deployment.

Analytics, marketing and advertising

readolia provides first-party counts of successful PDF opens for publishers through its separate backend reporting service once deployed. These counts do not set tracking cookies or store stable visitor IDs, and they are not unique-person measurements. Separately, readolia has consent-gated Google Analytics 4 code prepared for activation. GA4 remains inactive without a verified Measurement ID and consent. readolia keeps Base44 SDK client-side analytics disabled and does not intentionally enable Meta Pixel or advertising tags.

Base44 and related infrastructure may still create server-side request logs or diagnostics; disabling SDK client analytics does not establish that hosting providers collect no technical information. Do not assume zero provider-side collection.

External fonts and embeds

The app requests Google Fonts stylesheets/typefaces; these can generate network requests to that provider. Embedded publications are also subject to the hosting site's policies and integrations.

Consent and preferences

readolia provides a consent choice for optional Google Analytics 4 once a verified Measurement ID is configured. Analytics is denied by default and a notice offers Accept or Reject, with changes possible at any time via Footer → Cookie Settings. Necessary authentication storage cannot be disabled while remaining signed in.

If additional optional cookies, advertising pixels or tracking are introduced later, they must be audited and blocked pending valid prior consent where required, with an accessible withdrawal mechanism and updated disclosure.

Browser controls and future audit

You can sign out, inspect browser site data, block cookies or clear stored data via browser settings. Restricting essential storage may prevent sign-in.

This policy and the Cookie Settings panel will be updated after a full production cookie scan confirms providers, names, purposes, expiration and permissions.

Questions or requests?

Signed-in publishers can open a support request. A verified public contact and finalized legal/operator disclosures remain required before full launch.

Open support desk
Support