1. Scope
These rules cover the landing site, web app and device storage / access technologies. Cookies and local storage can support sessions, sign-in, preferences, security, analytics or advertising. These are possible categories, not a claim that each is currently used.
2. Confirmed technologies and inventory
The web app uses Firebase Authentication with default browser sign-in persistence: a session can survive closing the window until sign-out or clearing site data. Firebase SDK may use IndexedDB and other browser storage; exact keys and behaviour need browser verification.
Audit actual cookies, storage keys and SDKs separately for the landing site, login, application and checkout. The final inventory must identify names, vendors, purposes, duration, categories and recipients. Without an audit, neither necessity nor the absence of analytics can be assumed.
3. Optional technologies and choices
Where consent is required, optional analytics and advertising must remain disabled until an active choice. Refusal must be available and withdrawal as easy as consent. Continued browsing and acceptance of the terms are not substitutes.
This update does not add analytics / advertising scripts or consent controls. If such technologies exist or are added in the app, appropriate configuration and consent interfaces are required before they run.
4. Browser controls and external platforms
You can clear cookies and site data in your browser; this may sign you out or reset preferences. Blocking all cookies may disrupt login or payments. Paddle, Google Play, Apple and social networks apply their own policies on their services. Contact: wellcabulary@gmail.com.