Tracking & Storage Transparency EU ePrivacy & GDPR

Cookie & Local Storage Policy

Effective Date: September 29, 2026 Last Updated: September 29, 2026 Covers: VeloCalc Web & Mobile Applications

Summary of Our Storage Practices: VeloCalc does not use intrusive tracking cookies, third-party spyware, or cross-site tracking beacons. On the web and in mobile apps, we strictly utilize local device storage (such as browser localStorage and mobile operating system SharedPreferences) to remember your chosen theme, number formatting preferences, and calculation history.

1. Technologies Employed

When you access VeloCalc through our web portals or mobile applications, small data files or storage records may be created on your device:

HTTP Cookies: Small text files placed in your browser directory to maintain session continuity or remember basic display preferences.
Web Storage (localStorage and sessionStorage): Browser-based key-value stores that hold larger volumes of data locally without transmitting that data to the web server with every HTTP request.
Mobile SharedPreferences / App Sandbox: Secure, native operating system storage areas isolated to the VeloCalc mobile application on Android and iOS.

2. Storage Categories, Purposes & Retention

Technology	Key / Name	Category	Purpose	Retention
`localStorage` / SharedPreferences	`VeloCalc_theme`	Strictly Necessary / Functional	Stores your interface visual theme (Light, Dark, or System Default).	Persistent until cleared by user.
`localStorage` / SharedPreferences	`VeloCalc_number_format`	Functional Preference	Stores your chosen numeric grouping (Indian Lakhs/Crores vs International Millions/Billions).	Persistent until cleared by user.
`localStorage` / SharedPreferences	`VeloCalc_haptics`	Functional Preference	Stores your vibration toggle preference for keypad button presses.	Persistent until cleared by user.
`localStorage` / SharedPreferences	`VeloCalc_history_tape`	Core Utility	Maintains up to 500 recent calculation formulas and results for instant verification.	Persistent; user can wipe anytime via "Clear All History".
Session Storage	`VeloCalc_active_calc`	Strictly Necessary	Preserves in-progress input values during active browser tab navigation.	Session only (cleared upon closing tab).
HTTP Cookies (Web Portal)	`__cf_bm` / `_security`	Strictly Necessary	Security and DDoS mitigation cookies deployed by CDN/backend load balancers.	30 minutes to 24 hours.

3. Advertising Identifiers & Third-Party SDKs

In the ad-supported edition of VeloCalc, Google AdMob / Google Mobile Ads SDK may be integrated:

Advertising Identifiers: Mobile operating systems provide resettable hardware-independent advertising identifiers (Google Advertising ID - GAID on Android; Identifier for Advertisers - IDFA on iOS).
EU/EEA & UK Consent (IAB TCF v2.2): Within European jurisdictions, Google User Messaging Platform (UMP) displays a GDPR-compliant consent modal before loading ads, allowing users to choose between personalized ads, non-personalized ads, or to refuse consent.
US State Privacy Rights: In California, Virginia, and other US states, users may opt out of cross-context behavioral advertising directly within app settings.

4. How to Manage, Block, or Clear Cookies & Local Storage

You have full authority to restrict or erase local data at any time:

In-App Controls: Navigate to Settings > Tap "Clear All History" or "Reset Preferences" to instantaneously purge stored records.
Web Browsers:
- Google Chrome: Settings > Privacy and Security > Delete browsing data > Cookies and other site data.
- Apple Safari: Settings > Safari > Advanced > Website Data > Remove All.
- Mozilla Firefox: Settings > Privacy & Security > Cookies and Site Data > Clear Data.
- Microsoft Edge: Settings > Cookies and site permissions > Manage and delete cookies.
Mobile Device Settings:
- Android: Settings > Apps > VeloCalc > Storage & Cache > Clear Storage.
- iOS: Deleting the VeloCalc application completely purges all local sandbox storage.

5. European Union ePrivacy Directive & GDPR Compliance

Under the EU ePrivacy Directive (Directive 2002/58/EC as amended) and GDPR Article 6:

Exemption for Strictly Necessary Storage: Storage required exclusively to deliver the utility requested by the user (such as calculation history, session navigation, and display formatting) does not require prior consent under Article 5(3) of the ePrivacy Directive.
Prior Consent for Advertising: Any non-essential tracking or advertising technologies are withheld until the user provides unambiguous, affirmative consent through a certified Consent Management Platform (CMP).

6. Amendments to this Policy

We may update our Cookie and Storage Policy periodically to reflect technological changes or regulatory updates. Any changes will be posted here with an updated "Last Updated" timestamp.