Data Handling Policy
FixDQ is a client‑side (GitPages) application. All data stays local in your browser; nothing is sent to FixDQ servers because we don’t run a server for this app yet.
Overview
FixDQ is built to operate fully in the user’s browser. Any preferences, lightweight notes, or calculated outputs exist only on your device. We do not receive, process, or retain that data remotely.
Data Lifecycle
Storage
- Local Only: Data (e.g., preferences, progress flags, recent choices) is stored in browser storage (LocalStorage and/or IndexedDB).
- No Server Collection: Nothing is transmitted to FixDQ or any cloud provider.
Retention
- Browser-Controlled: Data persists only while it remains in your browser’s storage.
- User-Cleared: Clear site data (cache / storage) in browser settings to remove everything instantly.
- Session Only (ephemeral values): Some temporary calculations may exist only for the active tab/session (in-memory) and disappear on refresh or close.
Deletion
- User-Initiated: You fully control deletion by clearing site storage.
- Automatic: Browser resets, profile removals, or storage purges (including private browsing session end) erase all FixDQ data.
Future Enhancements
- Optional Cloud Sync: If we later add authentication or syncing, we will publish a detailed update covering what is stored, retention schedules, and user deletion controls.
- Timers & Expiry: Planned features may introduce automatic expiry for transient operational data (e.g., recent calculators or draft inputs).
Key Point for Users
Everything stays on your device. We don’t see or store your data. If/when this changes, the policy will be versioned and clearly highlighted.
