How FLO.W Core handles account, purchase, entitlement, and device authorization data.
2026/10/24
This notice applies to the FLO.W Core website, accounts, purchases, redemptions, downloads, and device authorization.
When FLO.W Core checks for updates (when you check manually, or during the daily automatic check; your purchase status is re-verified about every 7 days as part of it), it sends the signed authorization credential, an irreversible digest of the current computer, and this computer's Core version, Obsidian version, system type (macOS, Windows, or Linux), and whether the check was manual or automatic.
If the same vault has also been used with FLO.W Core on a phone or tablet, the computer also submits those devices' usage records from the last 90 days: a digest of a randomly generated device ID, system type (iOS or Android), device category, Core version, Obsidian version, and date of use.
We use this information to count how many devices run each version and to spot problems in new versions early. We do not collect or upload the contents of your Obsidian notes, vault names, or local paths.
We use this data to complete purchases and delivery, verify entitlements, manage computer quota, prevent duplicate ledger entries, handle refunds and support requests, and detect system problems. We do not sell your email address or other personal data.
If you choose Google sign-in, Google processes the sign-in request and provides the basic account information needed to authenticate you. Uploaded avatars are stored in a Cloudflare R2 bucket dedicated to FLO.W Core and displayed through a public URL. Do not use sensitive images as avatars. Payment, mail, sign-in, storage, and hosting providers process data only to the extent needed to provide their respective services, subject to their own agreements.
Orders, purchase snapshots, entitlements, redemptions, computer-authorization history, and audit evidence are permanent ledger records. We retain them to prove the purchase relationship, verify long-term entitlements, and reconcile the ledger. When a computer is unbound, its row remains in the ledger to preserve computer-quota history and rotation counts. Version records submitted during update checks (when each device was first and last seen on each version) are kept with the entitlement ledger and used only for per-version counts.
One-time codes, expired sessions, device pairing requests, sent-mail records, and diagnostic logs are removed under our internal retention schedule. Unsent mail is not deleted by expiry cleanup.
Custom avatars are retained while the account uses them. Replacing an avatar does not immediately delete the previous file; it remains until backend cleanup or a deletion request.
You may contact eryidebiji@gmail.com to request access to or correction of your account information, or to make another request available under applicable law. Ledger and audit evidence serves as purchase proof and prevents duplicate entries, so it is not removed through a general data deletion request.
For privacy questions, contact eryidebiji@gmail.com.