Privacy Policy
Scope of Data
Rocen does not collect, transmit, or process personal data. The app operates strictly on-device. No accounts, no profiles, no identifiers.
On-Device Storage
All notes, timeline segments, and configuration values are written into a local Hive NoSQL container on internal device hardware. The OS sandbox is the only boundary in play.
No Telemetry / No Analytics
- > NO ANALYTICS SDK ............... CONFIRMED
- > NO CRASH REPORTING ............. CONFIRMED
- > NO ADVERTISING IDENTIFIERS ..... CONFIRMED
- > NO THIRD-PARTY TRACKERS ........ CONFIRMED
- > NO BACKGROUND NETWORK CALLS .... CONFIRMED
User Rights
Because nothing leaves the device, no request, export, or deletion process is required. Uninstalling the app removes the data set in full.
Recovery & Offsite Backup
Rocen derives the vault key from your password with Argon2id and seals every note with AES-256-GCM using a random per-write nonce. A 12-word BIP-39 recovery phrase (standard 2048-word English wordlist) is generated on-device so you can rebuild the key on a new install.
Optional offsite backup pushes the already-encrypted vault blob to a private GitHub repository under your account via a fine-grained personal access token that you create and hold. The 12-word phrase and the GitHub token live only on your device and in your GitHub account — Rocen has no server, no key escrow, and never sees either value in plaintext.