Welcome to Vauz, a secure password manager offered by Sealzi. This Privacy Policy sets out what we collect, what we do with it, and what we never receive in the first place.
One point belongs at the top, because the rest of this document rests on it. Your vault stays on your own device. The Vauz application does not send it to us, does not tell us anything about it, and does not report on your use of it. The Vauz 2 beta does one thing more, set out in section 2: it asks our website, when it starts and then once a day, whether there is a newer version, a request that carries nothing from your vault but does show our servers that a copy of Vauz is running at your internet address. What we hold is an account record, and the records a sign-in page cannot work without: which sessions you have open, so signing out can end them everywhere, and short-lived counters that let us slow down someone guessing at an account or a family's invite code. They are listed in full below, and none of them is a log of your sign-ins. The one time we keep is when each passkey was last used, overwritten on each use and shown to you. Our website does not behave identically to the application, so the two are described separately throughout, because they are not the same thing.
2. Information We Collect
The Vauz application on your device
For Vauz 1.x, nothing. The application transmits no vault contents, no entry counts, no list of the sites you saved, no usage statistics, no error or crash reports, and no check-in of any kind — not to us, and not to anyone else. Choosing a support or documentation item from its menu opens your own browser or mail client, and any request made after that belongs to that program rather than to Vauz.
For the Vauz 2 beta, the application makes requests of its own for one purpose only, its updates:
- Shortly after it starts, and then once a day while it runs, it asks our website, vauz.sealzi.com, whether there is a newer version, by reading the list of versions and its signature. A check that gets no answer it can trust is tried again an hour later.
- Updates download from vauz.sealzi.com too. A newer beta, the release that follows the beta, and any security update download and install by themselves, whatever you chose in Settings, then Updates. Any other new version downloads by itself only if you chose Auto-install. With Notify, the default, it downloads when you press Update.
- These requests carry no account, no identifier and nothing from your vault, and a check does not say which version you are running. Like any request for a file on our site, they reach our servers with your IP address, and our servers record them.
- You can stop all of these requests. Turn on “No outbound requests”, in Settings, then Security, and the application makes no requests at all, just like Vauz 1.x. The one exception is Check for updates: when you press it, Vauz asks you first, and only then reads the list of versions and its signature. “No outbound requests” is off until you turn it on.
Apart from that, the Vauz 2 beta transmits nothing either: no vault contents, no entry counts, no list of the sites you saved, no usage statistics and no error or crash reports. Its Help menu opens our support pages in your own browser, or a new email to our support team in your own mail app, with the Vauz version, your macOS version and your Mac's chip written into it for you to keep or remove. Nothing is sent until you send it. Send Feedback, in the same menu, and the beta's Feedback button open our feedback form in your own browser with the same three details filled in, and they reach us only if you send the form. Each of these requests belongs to your browser or your mail app rather than to Vauz.
Your Vauz account, if you create one
- Your name and email address.
- Public half of your passkeys: a public key, the identifier the authenticator gave it, a counter used to detect a cloned device, and whatever nickname you gave it. The private half never leaves your device and we never see it.
- For each passkey, whether it is the kind that syncs to your other devices, as it reports about itself. That is why we can warn you when a passkey exists on one device only. We do not keep which model of authenticator it is or how it connects. We also record whether it was added normally or through an emailed recovery link (or an account-setup link used after the account already had a passkey), or while signed in with a passkey that was, because a passkey added that way is restricted for seven days (one day for changes to your plan or card). If a recovery link is used on the account again in its first two weeks, we note when, because its restrictions then start again from that time.
- For each passkey added after your first, a one-way code for the This wasn't me button in the email that tells you about it, never the button's link itself. For two weeks after the passkey was added, unless it is confirmed or removed sooner, your dashboard shows it as new to every other passkey. It is deleted with the passkey, when a passkey you had before confirms on the dashboard that it is yours, or once the button stops working two weeks after the passkey was added.
- For each passkey, when you added it and when it was last used to sign in. Both are shown to you on your dashboard, because they are how you recognise a passkey that is not yours. The last-used time is a single value that is overwritten each time, not a list of your sign-ins — there is no history behind it, and it records no IP address and no browser details.
- A reference that identifies your customer record with our payment processor. We never store your card details — not the number, not the last four digits, not the expiry date, not the security code (CVV). When your dashboard shows your card, or our payment page shows the card you have just saved (its brand, last four digits and expiry), it asks the payment processor at that moment and keeps nothing afterwards.
- Which subscription you have, the dates it runs between, and any change you have scheduled.
- For each payment: the amount, the tax, the date, whether it went through, and when we saw that it had. If a payment is later refunded or voided, how much and when. This is what your payment history, your receipts and our receipt emails are made from.
- Which of our payment emails we have sent you — a receipt, a notice that a payment did not go through, is about to be tried for the last time or has paused your plan, a notice that your plan has been paused or renews again, a notice that a payment was refunded or voided, or a notice that your plan has ended — and when, so that none is sent twice. Nothing else about the email is kept, and these records are deleted after 400 days.
- Each time you agree to a charge — buying a plan, upgrading, switching, or resuming one — the exact words you agreed to, which version of the terms was in force, when, and the IP address and browser you agreed from. The IP address and browser are encrypted at rest. Like the record of your acceptance of the terms, this is read only to answer a payment dispute. The IP address and browser are deleted once the plan has ended and 540 days have passed since its last payment, the longest card networks allow for some disputes, or straight away if it ended without a payment. The words, the version and the time are kept.
- If you join a family, the fact that you are a member of it, when you joined, whether you hold a seat on its plan, and whether the owner has named you a guardian. Everyone in a family sees who else is in it — each member's name, or a partly hidden email address for a member who has not set one — and who pays for its plan, who has a seat and who is a guardian. When the family's plan is set not to renew, everyone in the family also sees the date it ends and which plan, if any, the family has after that. While it renews, nobody but the person paying sees its dates or its price. When someone joins a family, its owner and guardians get an email with the new member's name, or a partly hidden email address if they have not set one.
- Your acceptance of the terms: when you ticked the box at signup, which version you accepted, and the IP address and browser you accepted from. Encrypted at rest, and read only to answer a payment dispute. The IP address and browser are kept while your account exists, and deleted once it has been deleted and 540 days have passed since your last payment, or as soon as it is deleted, if you never paid for a plan. Section 4 of our Terms of Service says the same.
If you sign up with your email address, we hold that address, encrypted, while the link we send you is valid — 72 hours — and delete it once the link has expired. Your account is only created when you open the link and confirm. If you ask for a sign-in link for an address that has no account, we send that address one email saying so, and keep nothing about it.
If the owner or a guardian of a family invites you by email from our website, your address is used to send that one invitation and we do not save it. The Join button in that email carries your address itself, encrypted so that only our server can read it, and works for 24 hours: pressing it sets up your account, or signs you in, and adds you to the family. The page it opens names the family, not your address. If it sets up an account, and once someone joins with it, we keep a one-way fingerprint of the link for each until it would have expired, so that it cannot do either again — nothing that says who it was for. As with every email we send, our mail server's delivery log records where it went, and if the address turns out not to exist, the bounce notice comes back to our support mailbox. We count how many invitations each owner sends in a day, but not who they went to.
If you delete your account, we first cancel your subscription with our payment processor and ask it to remove your saved card, then erase your name and email address from our record of you, sending one last email to that address to confirm the account is gone. Payment records and the records of what you agreed to are kept after that, because tax law and payment disputes require them to be.
Children
A Vauz account is for someone 14 or older, as our Terms of Service say. We do not knowingly hold an account for anyone younger, and we never ask for a date of birth. If you are the parent or legal guardian of a child under 14 who has an account, write to us at support@vauz.sealzi.com and we will delete it, with everything we hold about them that the law does not require us to keep. If we learn in another way that an account belongs to a child under 14, we delete it too.
Our website, including the sign-in and dashboard pages
- A cookie holding a security token, set when you use the sign-in or dashboard pages. It exists to protect those pages against forged requests, not to follow you between visits.
- A cookie that keeps you signed in, and a record on our side of the sessions it belongs to, so that signing out ends them everywhere. That record holds no IP address and no browser details, and there is no log of sign-ins: we keep no list of when or from where you signed in. Session records are deleted once the sessions they describe have expired, so they do not accumulate into one. The one time we do keep is the last-used stamp on each passkey described above, which is overwritten rather than appended to. When you confirm it is you before adding or removing a passkey, confirming that a new passkey is yours, buying, upgrading or switching a plan, adding or replacing a card, or deleting your account, a record that you did, and with which of your passkeys, tied to that sign-in: it stops counting after five minutes, and is deleted along with expired sign-in challenges.
- While someone is repeatedly failing to sign in, a short-lived counter that lets us slow them down. It is keyed by a one-way code derived from the address or identifier being tried, never by the value itself, and it is deleted once the attempts stop. Each sign-in is counted while it is being checked, so that one we could not count is refused. A successful sign-in then deletes the counter, so successful sign-ins are not recorded.
- While someone is joining a family — by typing its name and invite code, or through an invitation's Join button — a short-lived count of those attempts, the successful one included, by account and by internet address. It is keyed by one-way codes rather than by either, and deleted once the attempts stop.
- Each time the card form on our payment page is opened, or a link to that page is refused, a short-lived count against the internet address it came from, so that the page cannot be used to test stolen card numbers. It is kept the same way as the sign-in counter — a one-way code, never the address itself — and it is deleted once the attempts stop.
- Each time one of our forms sends an email — a sign-up or sign-in link, a reply to the contact form, a support or feedback message — a short-lived count by the address it goes to, by the internet address it came from, or by your account, so that the forms cannot be used to send someone mail over and over. And each time your dashboard reads your saved card from our payment processor, a short-lived count against your account, so that one account cannot use up the processor's limits for everyone. And each time a family join notice goes to an owner or a guardian, a short-lived count by the account it goes to, so that joining and leaving over and over cannot fill their inbox. All of these are kept the same way as the sign-in counter — one-way codes, never the address or account itself — and deleted once the requests stop. For the sign-up and sign-in forms the count is kept as a time, the same way, by the account a sign-in link is for, or by the address for a sign-up link or a note: up to five of each go out at once, then one every five minutes however often anyone asks. Counting a link by its account means that someone else asking over and over, at your address or any spelling of it, cannot keep you from getting a working link.
- Our servers record web requests in the ordinary way, which includes IP addresses.
- If you send the contact form on our homepage, we receive what you typed — your name, your email address and your message — as an email in our support mailbox, and send one automatic reply to the address you gave. If the form is sent several times in a short while with the same address, the later ones get no automatic reply. We delete the conversation within two years of our last exchange.
- If you send the feedback form for the Vauz 2 beta, we receive what you typed — what it is about, your message and, if you give one, your email address — and the details the app filled in that you left in: the Vauz version, your macOS version and whether your Mac has Apple silicon. Nothing from your vault is sent, and the app sends nothing itself: your browser sends the form when you press Send. It arrives as an email in our support mailbox and is kept as the contact form's messages are. An automatic reply goes only to an address you gave.
- If you send feedback or a support request from the dashboard, we receive what you wrote, along with the name and email address on your account.
- If you email our support team, from the Vauz 2 beta's Help menu or from your own mail app, we receive your email and the address it came from, and keep the conversation as the contact form's messages are.
- When you add or replace a card, you do it on a page of ours at pay.vauz.sealzi.com, which is kept separate from your account on purpose (section 6). Two short-lived cookies there, holding random values and nothing else, connect that page to your dashboard for up to an hour, and no longer than the sign-in that opened it: our record of that page notes which of your sign-ins that was. The billing address you type there is passed to our payment processor and not kept by us.
The Vauz browser extension
For Vauz 1.x, the extension sends us no vault data and no record of the pages you visit. It does load our logo image from our own server in order to draw its autofill button, and that request reaches us in the same way as any other request for a file on our site.
For the Vauz 2 beta, the extension (Vauz Autofill 2.0) makes no network request at all, so nothing it handles reaches us or anyone else. Its logo is built in. It talks only to the Vauz app on your computer, and that connection is encrypted end to end:
- When you ask it to fill a sign-in form, it tells the app the address of that page (the site's name, not the full page address), so the app can find the logins you saved for that site.
- After you approve in the app, the app sends back the usernames saved for that site. When you pick one, the app sends that login's password, and the extension fills both into the page.
- If you saved more than eight logins for a site, what you type in the site's username field, or in the extension's own search, while the list is open is sent to the app too, so it can find the rest.
- In your browser, the extension keeps the paired app's public key, its own key pair, your autofill settings, and whether it needs reconnecting. It keeps no password or other login.
- It reads the shape of sign-in forms on the page, to find where to fill, and sends it nowhere.
In Firefox, the browser itself checks our website about once a day for a newer version of the extension, as it does for any extension installed from outside Mozilla's add-ons site. That request reaches us in the same way as any other request for a file on our site, so our servers record it with your IP address. Like any request from a browser, it carries Firefox's version and your operating system, and Firefox sends it without cookies. Beyond that, it tells us only that this Firefox has the extension: no page you visit and nothing from your vault. Chrome and Edge update the extension from their own stores, so those checks go to Google and Microsoft, not to us.
3. Use of Information
We use what we hold to:
- Provide and maintain our services.
- Process transactions and manage subscriptions.
- Answer you when you contact us, and act on feedback you choose to send.
- Communicate with you about your account, security notices, and support.
- Ensure compliance with our terms of service and legal obligations.
We do not build usage profiles, and we hold no analytics from which one could be built. There is no advertising on our website, and we do not sell your information.
4. Data Security
For Vauz 1.x, your vault is encrypted on your own device and is readable only on that device. The encryption is built on an algorithm regarded as among the strongest in the field, with a further algorithm of our own creation applied in addition to it. We do not publish how either is put together. A detailed account of a defence tends to be worth more to the person trying to get past it than to the person relying on it.
For the Vauz 2 beta, your vault is encrypted on your own device too, with established, published algorithms and no algorithm of our own creation. While your vault opens automatically, without a V-Key, it is readable only on that device. Once you set a V-Key, your vault, and the backups Vauz makes of it, open with that V-Key on another computer too, which is what lets you restore them there. A backup made as an encrypted export opens with its own passphrase instead. Backups go only to a folder you choose, and if another program syncs that folder, they go wherever that program takes them.
The account information described in section 2 is transmitted only over encrypted connections. What our design protects you from, and what it deliberately does not, is set out in our threat model.
5. Sharing of Information
We do not sell your personal information, and we do not share it with third parties except as necessary to provide our services or to comply with legal obligations. This includes:
- Our payment processor, Helcim, when you add a card or pay for a plan: your name, email address and billing address, and the plan you choose. Your card number goes from your browser to Helcim directly and never passes through us. Signing in is not on this list: we handle it ourselves.
- Our hosting company. Our website, its database and our mailbox are on a server it runs for us, and it keeps them on our behalf.
- Legal authorities, if required by law or to protect our rights and safety.
Where your information is kept. Our website, its database and our mailbox are on a server in Germany, rented through a hosting company in Ukraine whose staff may reach the server from there. Helcim may keep its records in Canada, the United States and other countries, under its own privacy policy. Information kept outside Canada is covered by our agreements with those companies, but the authorities of those countries may be able to obtain it under their laws. You can ask us for our written practices on this at the address in section 9.
Your vault is not on that list, and cannot be. We never receive it, so there is nothing for us to produce — including in response to a legal demand.
6. Cookies, Tracking and Third-Party Content
We use no analytics, no advertising, and no tracking cookies. There is no third-party analytics service anywhere on our website and no cross-site tracking. The only cookies we set are the ones described in section 2: the security token and the sign-in cookie on the sign-in and dashboard pages, and the two short-lived cookies on the card page.
Our pages load their fonts, icons, stylesheets and images from our own servers. Nothing about how a page looks is fetched from anyone else. Our delivery network, cdn.sealzi.com, serves the shared page furniture. It is our infrastructure, not a third party.
One service provider, named in section 5, is contacted only on the pages that need it:
- Helcim (helcim.com) — payment. Its card form runs only on our card page, pay.vauz.sealzi.com, which holds nothing of your account: Helcim's code never runs on the pages where you are signed in. It is Helcim, never us, that receives your card details. Our server also talks to Helcim directly, to set up, change and check your subscription, and to see whether a payment was refunded or voided.
Signing in involves no third party at all. Passkeys are handled by Vauz, on our own servers. There is no identity provider behind the sign-in page, nothing is sent to one, and no component on that page reports to anyone. Signing in used to be handled by an outside company, it no longer is, and is handled by Vauz itself now.
Helcim carries nothing about your vault, and we do not use it to identify you. If you never add a card or buy anything, no request leaves our servers on your behalf — and signing in does not send one either.
Helcim keeps its own customer record and payment history, under its own privacy policy. Your receipts come from us. If a payment does not go through, Helcim may email you about it as well as we do. We cannot delete Helcim's records for you. Deleting your account cancels your subscription and asks Helcim to remove your saved card.
7. Your Data Rights
Depending on where you live, you may have certain rights over the personal data we hold, including:
- Access: Request a copy of your data.
- Correction: Correct any inaccuracies in your data.
- Deletion: Request the deletion of your data.
- Portability: Receive the information you gave us in a common, structured format, or have it sent to someone you name.
- Withdrawing consent: Withdraw your consent to anything we do with your information on the basis of it. Some of it, such as the records of payments, we must keep while the law requires.
These rights cover the account record described in section 2. They cannot extend to your vault, because we do not hold it. A copy of your vault is something only you can produce, from your own device, and deleting your account removes our record of you without touching anything on your machine.
To exercise these rights, please contact us at support@vauz.sealzi.com. We answer in writing within 30 days, at no cost to you.
If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca), to the Office of the Information and Privacy Commissioner of Alberta (oipc.ab.ca), or, if you live in Quebec, to the Commission d’accès à l’information (cai.gouv.qc.ca).
8. Changes to This Policy
We may update this Privacy Policy. The date at the top of this page shows when it last changed, and earlier versions stay available at vauz.sealzi.com/legal. Before any change takes effect, we show a notice of it on this website, and before a change to how we use your information takes effect, we also email account holders about it. We never start using information we already hold for a new purpose, or share it with a new kind of recipient, without your agreement, unless the law requires it.
9. Contact Us
Vauz is made by Sealzi Inc., of Alberta, Canada. Our Privacy Officer is responsible for how we handle personal information. If you have any questions or concerns about this Privacy Policy or our data practices, please contact them at:
Email: support@vauz.sealzi.com.