Privacy notice
What we collect, why, where it goes, how long we keep it, and what you can make us do about it.
Last revised .
This notice describes how Mohamed Nasri (“we”) handles personal information in Deedstone. Canada is the governing jurisdiction, so PIPEDA applies, and Quebec’s Law 25 applies to residents there. It is written to be read; where something is not yet true of the running system, it says so rather than describing the intention.
What we collect
Four categories, and nothing outside them:
- Account. Your email address, your name, a hash of your password (Argon2id — the password itself is never stored), and your multi-factor secret.
- Household. Property addresses, rooms, equipment, serial numbers, purchase dates, service history — the record the product exists to keep.
- Documents. The files you upload, and the values read out of them: vendor, date, amount, model, expiry.
- Operational. IP address, browser user agent, and an append-only audit entry for every sign-in, permission change, document access, and export.
We do not collect payment card numbers. Subscriptions run through Stripe’s own hosted checkout; we store a customer reference and nothing else. There is no code path in this system that could receive a card number.
We do not collect location. Photographs routinely carry GPS coordinates in their EXIF metadata; that metadata is stripped when a file is ingested rather than stored and ignored.
Why this data is unusually sensitive
Taken together, the above is a complete, structured, searchable inventory of what is valuable inside a specific address — with the dates its occupants are likely to be away. That is a burglary planning tool if it is breached, and it is why the controls below are what they are rather than an industry-standard minimum.
Where your documents are processed
Document text is sent to a third-party model provider when a document is read. That is how the vendor, the amount, and the expiry date get out of a photograph and into your record. It is the single most consequential thing this product does with your papers, so it is stated here rather than in a table.
That provider processes the text outside Canada. Our contract with them forbids using your content to train general models and requires it not be retained beyond the request. Documents the local text-recognition chain cannot read may additionally be sent to a cloud recognition service under the same terms.
The primary database and the object storage holding your files are in Montreal, Canada. Encrypted backup copies are stored in the United States (US East), with a different provider, so that losing the server in Montreal does not lose your records.
Reminder and account emails are sent through an email delivery provider in the United States, which sees the recipient address and the message.
How long we keep it
- Records you delete: 30 days, then permanently purged. The window exists so a deletion nobody authorised can be undone.
- After you delete your account: the household is marked and purged 30 days later — every record and the stored document files themselves.
- Audit entries: seven years. These are append-only and cannot be edited or deleted through the application by anyone, including us.
- Operational logs: 30 days, with personal information redacted before anything is written.
Asking to be forgotten anonymises you rather than deleting you. Your email and name are scrubbed, the account is deactivated, and sessions and MFA devices are destroyed — but the user row stays, so seven years of audit entries still resolve to a user that exists and no longer says who it was. Deleting the row would either cascade the audit trail away or leave it pointing at nothing, and neither of those is an audit trail.
How it is protected
- Separation between households is enforced by the database, through row-level security policies on every table carrying household data, with the application connecting as a role that cannot bypass them. It is not a filter in application code that somebody could forget to write.
- Passwords are hashed with Argon2id, with a twelve-character minimum.
- Multi-factor authentication is available and can be required.
- Document files are held in private storage and reached only by short-lived signed links.
- Uploads are scanned for malware before they can be read back.
- Personal information is redacted before anything reaches a log or an error report.
One gap, stated plainly: account and policy identifiers are encrypted at rest with keys held by the application rather than in a dedicated key management service. That protects against a leaked backup or a database read; it does not put the keys outside the reach of the application process itself.
Who else can see your household
Only people you have given access to. Members are granted specific capabilities — a person can work with the home’s records without seeing its finances. Contractors can be given read-only sight of one property for a fixed number of days, and that access revokes itself on a nightly sweep rather than waiting for somebody to remember.
Every access is written to the audit log, which you can read.
What you can require of us
- A copy. A full export produces every record you have access to as JSON, with a manifest naming each section and its row count. You can run it yourself; you do not need to ask.
- Correction. Every extracted value carries the document and the page it was read from, and can be corrected in place.
- Deletion. Available from your account settings, subject to the 30-day window above.
- An explanation, or a complaint. Write to us at the address below. If our answer does not satisfy you, you may complain to the Office of the Privacy Commissioner of Canada, or to the Commission d’accès à l’information du Québec if you are a Quebec resident.
Contact
Mohamed Nasri — privacy@hiveqore.com
375 River Ave, Winnipeg, Manitoba R3L 0B5, Canada
Governing jurisdiction: Manitoba.