Bazinet Vault

An English version is provided. .

Privacy Policy

Last Updated: August 2026

1. Overview

Bazinet Vault (bazinet.net) is designed as a zero-knowledge password manager. Vault contents are encrypted on your device, before storage, under a key derived from your master password. We have never held that password. In normal operation we cannot read your entries, your notes, your attachments, your authenticator codes, or your Mission sessions.

That is arithmetic rather than a promise about our conduct: the server cannot decrypt what it never had a key for. Everything else described here — your email address, when you signed in, from which country — is ordinary account data that we can read, and this policy exists to say exactly what we do with it.

The Service is experimental and under active development. It has not necessarily undergone an independent security audit, and no software, infrastructure provider, or cryptographic implementation can be guaranteed free of bugs or vulnerabilities. We cannot promise that unauthorized access or disclosure will never occur.

2. What this policy covers

bazinet.net, the Bazinet Vault web app, the browser extension, the desktop app, Bazinet Aim Trainer, and Horaire CVM.

Horaire CVM requires a Bazinet account, and your agenda is stored on it. It reads the schedule PDF you download from Omnivox — that file is parsed in your browser and is never uploaded, whatever else happens. What IS stored on your account is the result: your courses, your tasks and your term dates.

It is encrypted on your device before it leaves, with AES-256-GCM, under a key derived from your account password using a key-derivation label reserved for this purpose. We hold a verifier for a different key derived from the same password, so we cannot derive this one: what we store is ciphertext, a nonce and a revision number. We cannot read your courses, your teachers, your rooms or your timetable. A copy is also cached in your browser so the agenda opens offline.

That key is derived when you sign in and kept in your browser's storage, so the agenda does not ask for your password again on every visit. It is stored in a form the page can use but cannot read back out or copy elsewhere. It never reaches us. The practical consequence is worth stating plainly: anyone who can unlock this browser can read your schedule, as with any calendar app. Signing out erases the key and the cached copy, and deleting your account deletes the copy we hold.

3. What we collect

Account

Vault contents (encrypted; unreadable to us)

Authentication

Technical and security

Usage

Billing (Pro)

4. Features that move data through us

Masked email aliases (Pro)

If you create a masked alias, mail sent to it passes through our systems on its way to your real inbox. This is inherent to forwarding: unlike your vault, forwarded mail is not end-to-end encrypted, and we are technically able to read it in transit. What we actually do with it is limited to the following.

If you would rather no mail passed through us at all, do not create aliases. Deleting an alias stops forwarding for it immediately.

Breach checking

Your password is never sent to us or to anyone else. Your device hashes it and sends only the first five characters of that hash, which we relay to Have I Been Pwned; the matching is done again on your device. We can see that an account ran a check, the five-character prefix, and when. We cannot derive the password from it.

If you ask us to email you the report, that email contains the counts and the names of the entries you chose to include — entry names, never passwords, leave your device in readable form so the report can name them. Sending the report is entirely your choice; the scan works without it.

Emergency access (Pro)

The contact you designate is another Bazinet account. We store the pairing, the waiting period you set, the timestamps of any request and its approval or rejection, and your vault key encrypted to your contact's public key. We cannot decrypt that wrap; only your contact's own unlocked account can.

Mission sessions (Pro)

A Mission is a small, separately-keyed vault protected by its own passcode. We hold the ciphertext, a verifier for that passcode, an expiry, and — if you set one — a geofence that is itself encrypted. We cannot see which entries a Mission contains, or where it is fenced to.

Bazinet Aim Trainer

The app signs in with your Bazinet account through your browser, so the app never sees your password; what it receives is a session token. Downloads are served as a redirect to GitHub, which will therefore see the download request. Match data comes from the official Riot Games API and from your own local game client, and is handled by the app on your machine — it does not pass through bazinet.net.

5. What we never collect

6. How information is used

We do not sell personal information.

7. What support can see

Support staff work from a console. What they can reach is deliberately narrow, and the part that is not narrow requires your permission.

Without asking you, support can see account state (verified or not, plan, whether a vault exists), counts of entries, attachments, sessions and trusted devices, when you last signed in, addresses your account has been seen from recently, the labels of your passkeys, and internal support notes. They cannot see your vault, and nothing in the console would decrypt it.

Your full security log, a repair diagnosis, and any repair require your consent. Support must state a reason, which is quoted to you word for word; you are emailed a link and nothing is shared unless you approve it. Access ends automatically after a fixed window, you can end it sooner at any time, and every single look is counted and written into your own security log, where you can read it.

An integrity report — which of your records will not decrypt on your device — is uploaded only if you press the button, and only while such a permission is live. It carries problem codes from a fixed list and record identifiers we already hold. It never carries contents, and the server refuses free-text error fields precisely because that is how plaintext leaks into a log.

Support can also do the things that help someone get back in: resend a verification email, send a reset link, clear a lockout, reset an authenticator, remove a passkey, or sign devices out. Support can reset a vault, which destroys it — it cannot recover one, because nobody can. Every one of these actions is written to the log.

8. Third-party providers

These providers process information according to their own privacy policies and legal obligations.

9. Cookies

This site carries no advertising and no third-party tracking of any kind. We serve no ads, we run no analytics SDK, and our Content Security Policy permits no third-party script origin.

We use only strictly-necessary cookies, for authentication, security, fraud prevention, and operation of the Service. They do not track you for advertising. There is no advertising cookie to consent to, and therefore no cookie banner.

One additional non-tracking cookie, bz_geo, holds only your region (for example "CA-QC") so the site can be shown in the right language. Your language choice itself is kept on your device.

10. Retention and deletion

Information is kept for as long as reasonably necessary to operate and secure the Service or to meet a legal obligation.

You can delete your account yourself, at any time, from account settings. Deletion removes your entries, attachments, vault manifest, Mission sessions, masked aliases, emergency-access grants, sessions, trusted devices, passkeys, support records, and the account itself. It is irreversible, and it is not a request you have to send us.

Two things deliberately survive deletion. Security-log entries remain, because a log that can be erased by the person it records is not a security log. And if a machine was blocked for abuse, the hashed machine identifier stays blocked — otherwise deleting an account would be a way to undo the block.

Encrypted backups you exported are files on your own device. Deleting your account does not touch them, and they remain restorable with the passphrase you set on them.

11. Security

Vault contents are encrypted on your device with AES-256-GCM, under a key derived from your master password with Argon2id. The vault is authenticated as a whole, so records cannot be removed, reordered, or substituted without detection. We apply rate limits, lockouts after repeated failures, automatic blocking of abusive sources, and security logging.

No security system is perfect, no method of transmission is completely secure, and no software can guarantee confidentiality, integrity, or availability. You accept these risks by using the Service.

12. Children's privacy

The Service is not directed toward children and should not be used by them. We do not knowingly collect personal information from children in violation of applicable law.

13. International processing

Your information may be processed or stored on servers outside Québec, in the jurisdictions where our infrastructure providers operate. Those jurisdictions may offer privacy protections different from those where you live.

14. Your rights

Under Québec's Act respecting the protection of personal information in the private sector, you may ask for access to the personal information we hold about you, ask for it to be corrected, and complain to the Commission d'accès à l'information. Most of it is already self-serve: your security log, your active sessions, and an export of your vault are all available from within the app, and account deletion is a button.

For anything else, write to support@bazinet.net.

15. Changes

We may update this policy. The updated version takes effect when published, and continued use of the Service after that constitutes acceptance.

16. Contact

support@bazinet.net