DailyScore Cookie and Similar-Technologies Notice
Version: 2026-10-18.1
Effective date: 18 October 2026
Public page: https://thedailyscore.app/cookies
Privacy and support contact: info@thedailyscore.app
About this document
This notice explains how DailyScore websites and any DailyScore web app use cookies, browser local storage, caches and similar technologies. It also gives limited information about comparable on-device storage in the native mobile app. It supplements the Global Privacy Policy, Teen Privacy Notice and the applicable Regional Privacy and Consumer Schedule.
DailyScore is operated by Yash Purandare, an individual in India.
Postal address: 75/76 Sector A, Indore, Madhya Pradesh 452018, India.
In this notice, Yash Purandare is called “DailyScore”, “we”, “us” or “our”.
1. The short version
- The DailyScore app contains one third-party advertising SDK, Google AdMob, which shows contextual, non-personalized banners in the Free Friends feed (Privacy Policy section 4.14). It contains no behavioural-tracking, attribution, crash-reporting or product-analytics software.
- DailyScore does not currently use cookies or similar technologies to sell information, build advertising profiles, follow people across unrelated services or target advertising.
- If a DailyScore web app is offered, it uses browser local storage for necessary sign-in, security, preferences, account-scoped offline operation and pending synchronization.
- The web app may cache code, fonts, images and other assets so it can load reliably and update correctly.
- Optional storage or tracking will remain off unless it is approved, disclosed here and, where required, the person gives a valid choice first.
- Declining optional technologies will not block the core habit-tracking service. Technologies that are strictly necessary for a feature the person requests may operate without optional consent where law permits.
- External services opened by the user, such as Apple or Google, control their own websites and storage under their own notices.
We will not add a new tracker without updating this notice first.
2. What these technologies are
A cookie is a small file that a website asks a browser to store. Similar technologies include browser local storage, session storage, IndexedDB, software-development kits, pixels, tags, device identifiers, cached files and other ways of storing information on or reading information from a person's device.
These technologies can have different purposes. Some are needed to sign in, protect an account, remember a requested setting, save work while offline or load the service. Others can measure audiences, personalize advertising or track activity across services. DailyScore treats the purpose and effect—not only the technology's name—as important.
3. Where this notice applies
This notice applies to:
-
thedailyscore.appand other DailyScore-controlled web pages that link to it; - any DailyScore web app made available through an approved domain; and
- comparable device storage in the DailyScore iOS or Android app, where this notice says so.
It does not govern a third party's separate website or app. If the person chooses Apple or Google sign-in, visits an app store, opens a social-sharing destination or follows another external link, that third party may use its own cookies or similar technology. Review its notice before continuing.
4. Categories we use or may use
Strictly necessary and security
These technologies support a service or feature the person requests, such as sign-in, authentication flow integrity, fraud and abuse prevention, secure session continuity, load balancing and remembering a privacy choice. Blocking them may prevent the requested feature from working.
Functional and preference storage
These remember requested choices such as language, accessibility settings, text size, reduced motion, tutorial completion and app configuration. A choice may be stored locally so the person does not have to repeat it.
Offline and synchronization storage
The web app can retain account-scoped app state and a bounded queue of actions that still need to reach the server. This helps the app recover from a weak or interrupted connection. Depending on the feature used, local records may include habit names, schedules, progress, preferences, avatar choices and pending app actions. Habit names can reveal sensitive information, so this storage must be treated as private account data rather than harmless website preferences.
Performance, analytics and crash reporting
No third-party product-analytics or crash-reporting provider is approved or active in the inspected client. DailyScore will not add one merely because a person accepts a general privacy policy. A future provider requires a defined purpose, data minimization, security and child/teen assessment, vendor review, regional legal basis, updated notice and any required prior choice.
Advertising, attribution and cross-service tracking
The website does not use an advertising or marketing-attribution tracker. The mobile app is designed to use Google AdMob only for contextual, non-personalized Friends-feed banners on Free accounts. It does not request an advertising identifier, send DailyScore habit/profile data for targeting, or perform cross-service behavioural tracking. Final Google SDK storage/network behavior and the UMP privacy-choice record must be inserted after production verification.
5. Current implementation inventory — production verification required
DailyScore uses the following technologies:
| Technology or category | Location and provider | Purpose and information | Expected duration or control | Current classification |
|---|---|---|---|---|
| Supabase authentication session | Browser local storage in a DailyScore web app; Supabase Auth | Stores access and refresh session information so a signed-in person can stay authenticated and the app can secure requests | Until sign-out, session invalidation, approved expiry or browser-data clearing; final production session configuration must be inserted | Strictly necessary for signed-in web-app use |
| PKCE authentication-flow value | Browser storage in a DailyScore web app; Supabase Auth | Temporarily links the browser that began an approved sign-in flow to the returning authorization response | Intended for the authentication flow; exact key and cleanup behavior must be verified in production | Strictly necessary for the selected sign-in flow |
| DailyScore preferences and setup state | Browser local storage in a DailyScore web app; DailyScore/Flutter shared preferences | Remembers language, accessibility choices, app settings, limited eligibility draft and tutorial status | Until changed, cleared by the app or browser, or removed under the approved cleanup lifecycle | Strictly necessary or functional, depending on the exact item |
| Account-scoped offline state | Browser local storage in a DailyScore web app; DailyScore | Supports offline-first habits, schedules, progress, avatar/profile settings and related app state | Until synchronized and removed under the approved local-data lifecycle, account deletion cleanup or browser-data clearing; final duration requires verification | Necessary for requested web-app/offline functions; contains personal data |
| Pending synchronization queue | Device storage in supported clients; DailyScore | Holds bounded pending and rejected gameplay commands so interrupted actions can reconcile with the server | Until acknowledged, resolved, removed under bounded cleanup or device/browser data is cleared | Strictly necessary for reliable synchronization |
| Web application cache | Browser cache, Cache API or service worker; DailyScore/Flutter | Caches app code, fonts, images and static assets for reliable loading and updates | Browser- and release-controlled; old app assets should be replaced or purged during update | Strictly necessary for the installed web-app experience where enabled |
| Privacy-choice record | Device storage in the mobile app; Google User Messaging Platform | Remembers the person's advertising-privacy choices, including the IAB consent string in the European Economic Area, so the choice is respected | Until the person changes it in the app's privacy options, clears app data or deletes the app | Strictly necessary to remember the person's privacy choice |
The table does not yet describe production hosting, content-delivery, bot- protection or load-balancing technology because those services have not been frozen and verified. No blank row authorizes deployment. A technology must be added to the inventory before it is enabled.
6. Browser and server information that is not a cookie
When a device requests a web page or service endpoint, ordinary network and security records may include IP address, time, requested URL, response code, browser or device information and limited error or abuse signals. These records are not necessarily stored on the device, but they can still be personal data and are governed by the Global Privacy Policy and Data Retention and Deletion Policy.
DailyScore's eligibility design may use an IP address transiently to obtain a country-only consistency signal. The raw IP is not intended to enter the eligibility database. That network processing is explained in the Age Eligibility and Country Availability Notice; it is not permission to use the IP for advertising or general tracking.
7. Choices and consent
Where applicable law requires consent before a non-essential technology is stored or accessed, DailyScore will:
- keep that technology off until a valid affirmative choice is recorded;
- explain the categories and material providers before the choice;
- make Reject optional as clear and accessible as Accept optional;
- avoid pre-selected optional choices, inactivity or continued browsing as consent;
- allow category-level choices where appropriate;
- make withdrawal as easy as acceptance and stop future optional use after withdrawal; and
- keep a minimal record needed to demonstrate and respect the choice.
Accepting the Terms or Privacy Policy is not consent to optional tracking. Purchasing Quest Pass, enabling push notifications or using a social feature does not activate unrelated analytics or advertising.
Necessary storage will be explained even where separate consent is not required. DailyScore will not label a technology “necessary” merely because it is useful to DailyScore, measures product performance, supports advertising or would be inconvenient to remove.
8. Children and teens
DailyScore is intended only for people who have reached the minimum age for their country (never below 13; see the Minimum Age by Country page). Teen-facing explanations and choices must use clear language and avoid pressure, misleading button design, repeated prompts or settings that encourage a young person to give up privacy.
Teen Mode does not permit behavioural advertising or marketing profiling. DailyScore does not offer a parent consent process, so no non-essential purpose that would need a parent's consent is switched on for a young user.
9. Browser, device and platform controls
A person can usually clear or block cookies and site data through browser settings. Clearing DailyScore site data may sign the person out, remove unsynchronized actions, reset preferences or delete the local offline copy. The server-side account may remain until the person uses the account-deletion process.
On a shared device, sign out after use and clear DailyScore site data if other people can access the same browser profile. Merely closing a tab or window may not remove locally stored account information.
Browser privacy signals can supplement, but do not replace, a compliant DailyScore choice mechanism. Because DailyScore does not sell personal data, use behavioural advertising or deploy cross-service tracking, there is currently no such optional activity for a Global Privacy Control or similar signal to switch off. If that changes, we will update this notice and honour any legally required signal before the change takes effect.
10. External providers
The following services may be reached as part of a requested feature, but their separate pages can apply their own storage rules:
- Apple or Google for platform sign-in and app-store services;
- Supabase for authentication and backend services;
- RevenueCat and the relevant app store for Quest Pass entitlement and purchase management;
- an external sharing destination chosen by the person; and
- a link intentionally opened from support, legal or safety pages.
A provider's presence in this list does not mean that its tracking is approved inside DailyScore. The final Subprocessor and International-Transfer Notice will identify the approved production providers, roles and locations.
11. Retention and security
DailyScore limits browser and device storage to the purpose described and the approved retention lifecycle. Authentication tokens and account-scoped local records require protection against unauthorized scripts, shared-device access and accidental persistence after sign-out or deletion.
No browser storage is perfectly secure. A person who controls an unlocked device or browser profile, malicious software, or a successful website-script attack may be able to access locally stored information. DailyScore therefore uses account scoping, minimizes durable fields and must apply secure hosting, dependency, content-security and session controls before a web launch.
12. Changes to this notice
The live notice will show its effective date and current inventory. We will update it before materially changing a purpose, provider, category or choice. Where a new use needs consent, it will remain off until the required new choice is obtained. An older general acceptance does not authorize a new tracking purpose.
13. Contact
For questions or complaints about cookies, browser storage or similar technologies:
Email: info@thedailyscore.app
Postal address: 75/76 Sector A, Indore, Madhya Pradesh 452018, India.
The Privacy Rights and Account Deletion Page explains how to exercise an applicable privacy right. The Regional Privacy and Consumer Schedule will identify relevant supervisory-authority and regulator routes.