Security & Data Architecture
A technical breakdown of our local-first paradigm.
1. Local-First Paradigm
Unlike traditional software-as-a-service (SaaS) web platforms, Workflare Track operates under a **local-first** architecture. Data remains on the client device. This completely eliminates server-side vulnerabilities, data leaks, and third-party sniffing.
2. Browser Isolation & Sandboxing
Local storage parameters are sandboxed and scoped per-subdomain. Only code served directly from the exact domain (`track.workflare.in`) can read, write, or access your saved keys. No cross-site scripting (XSS) from other web pages can read these keys due to the browser's Same-Origin Policy.
3. Safety Reset Verification
To prevent accidental local storage data wipes, the application implements a code-verification check. To clear your timeline, users must type the exact alphanumeric key sequence: notstoryworthy. This prompt stops automated browser cleaners or slips of the finger from destroying history.
4. Schema Structuring
Backups are structured into standard, open JSON schemas. This enables complete data portability. The export file contains simple, plain-text arrays and key-value objects, allowing you to write your own custom scripts to backup, parse, or move data to other tools without lock-in.