Detailed report on the acquisition, encryption, and lifecycle of user vitality telemetry within the Robustly infrastructure.
Robustly operates on a principle of minimal data acquisition. We only ingest biological telemetry that is strictly necessary for the performance of the Vitality Dashboard and the Architect AI feedback loop.
Your identity is bound to a unique Robustly ID, which acts as the primary key for all telemetry logs. This data is never sold, traded, or leased to external marketing brokers.
User telemetry is localized within our managed SQLite3 infrastructure. To maintain system speed and data integrity, the following persistent storage settings are applied to every database transaction:
We utilize Write-Ahead Logging to prevent data corruption during simultaneous write operations, ensuring your mission progress is captured instantly.
Sensitive identifiers, such as password hashes, are processed using modern cryptographic salting and hashing (Werkzeug/BCrypt) before entering the disk layer.
The Architect AI utilizes adaptive Groq inference to analyze your statistics. When generating insights, the system transmits a stateless payload consisting of raw vitality integers (steps, water, sleep) without transmitting your specific user identity or email to the inference engine.
You maintain absolute ownership of your digital footprint. Robustly provides a "Nuclear Purge" command within the user settings, allowing for the complete deletion of your data node.
Your session is protected by a multi-layered security stack. We deploy strict Content Security Policies (CSP) and X-Frame-Options to prevent unauthorized script injection and cross-site data leakage.
All traffic is routed through encrypted tunnels (SSL/TLS) to prevent interception of your vitality telemetry during transit from your device to the Robustly core.
When utilizing Google OAuth, Robustly only requests access to your basic profile information (Email/Name). We do not request or store access to your Google Drive, Contacts, or other sensitive ecosystem data.
The Privacy Architecture is subject to updates as the system evolves. Users will be notified of significant changes via the global Architect Broadcast banner. Continued usage of the terminal following an update constitutes acceptance of the new data protocols.