What Remindify collects, why, and what stays yours. The short version: your register is yours, and the trust layer is optional.
Last updated 22 October 2026Preview draft · counsel review before paid launch
This is a plain-language preview, not legal advice. We will publish a reviewed version before paid availability and before any onchain feature is offered as a production service.
01
What we collect
When you create an account we collect the details you give us: your name and email address, or the profile information Google returns if you choose Google sign-in, or the public address your wallet returns if you choose wallet sign-in. We store a salted password hash if you use email and password; we never store the password itself.
Inside the workspace we store the obligations, owners, backups, risk inputs, proof references, receipts and audit events you create. If you paste text into Capture, it is parsed to produce draft obligations. Raw pasted text is not added to your register unless it becomes part of a saved obligation.
02
What we do not collect
We do not sell personal data. We do not use advertising cookies. We do not upload your source documents to the trust layer. Proof receipts contain hashes and references, not the underlying document. We do not ask for a private key and we cannot sign a transaction for you.
03
How we use it
We use account data to authenticate you and keep your workspace separate from other people's. We use workspace data to calculate risk, show your register, produce receipts and maintain the audit trail. We use limited operational logs to keep the service healthy and investigate abuse.
04
Cookies and sessions
Remindify sets a small number of essential cookies. A session cookie keeps you signed in. A short-lived OAuth state cookie protects the Google sign-in redirect. These cookies are HttpOnly and SameSite=Lax, and the session cookie is marked Secure when the service is served over HTTPS. We do not use them for advertising.
05
Third parties
If you choose Google sign-in, Google processes the authentication request under its own privacy terms. If you choose wallet sign-in, your wallet software handles the signature locally; the server receives only the public address, message and signature needed to verify it. If you anchor a receipt or use escrow, a public RPC provider and the relevant network will see the public transaction you signed.
We may use infrastructure providers to host the service and store the database. We will name material subprocessors before paid availability.
06
Onchain data
Blockchains are public and permanent. If you choose to anchor a receipt or fund an escrow, the transaction, your public wallet address and the proof hash become publicly visible. Do not anchor anything you are not prepared to make public. The underlying evidence is not uploaded by Remindify.
07
Retention
We keep account and workspace data while your account is active. Production workspaces live in a managed Postgres database; local development uses SQLite. If you ask us to delete an account, we will remove the account and its sessions; records already written to a public chain cannot be deleted by us or anyone else.
08
Your choices
You can export your register from the product. You can sign out at any time. You can ask us for access, correction or deletion of your account data by contacting us. If you signed in with Google, you can revoke Remindify's access from your Google account settings.
09
Changes and contact
We will update this page as the product moves from preview to paid service. Material changes will be announced in the product or by email. Questions about privacy can be sent to hello@remindify.app.