Keys originate on device
The server does not generate the encryption key or receive it in plain text.
Local SELFLEX will not go away. The planned SELFLEX Sync feature will ship off by default and will work only when you explicitly enable it.
Under the target model, data is encrypted before it leaves your device. The transport and storage layer handles ciphertext only; SELFLEX cannot read its contents.
This will not be treated as a marketing phrase. A release must satisfy the technical boundaries below.
The server does not generate the encryption key or receive it in plain text.
Your selected records become unreadable on-device before a network request begins.
Only devices you authorize can open the ciphertext. The server cannot search its contents.
If a recovery key is lost, SELFLEX may be unable to restore the data. Setup will explain this clearly.
Dates will remain uncommitted until the security model and store reviews are complete.
Safari, Chrome, and Firefox dashboards with detailed analysis, categories, privacy controls, and local backup.
Optional, application-layer end-to-end encrypted sync across iPhone, iPad, macOS, and Safari. The release is in App Store review; it will be announced here once approved.
A device-pairing model that keeps the same zero-knowledge boundary across Chrome, Firefox, and Apple devices.
SELFLEX already runs on Android through Firefox: add the extension to Firefox for Android and you get the full dashboard. Firefox is the only mainstream Android browser that runs extensions, so reaching the others requires a separate SELFLEX app; a local dashboard and optional encrypted Sync are being evaluated against platform constraints.
You will continue to use SELFLEX without an account or synchronization. Enabling Sync will not automatically upload existing local records; you will still choose each data group.