Privacy Policy

Last updated: 14 October 2026 · Previous versions

1. Introduction

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. 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

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.

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, a few technical details it reports about itself: which model of authenticator it is, if it volunteers that (we do not ask for it), how it connects — USB, NFC, Bluetooth or built in — and whether it is the kind that syncs to your other devices. That last one is why we can warn you when a passkey exists on one device only. 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), because a passkey added that way is restricted for a day.
• - 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. 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, 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.
• - 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.
• - 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. Section 4 of our Terms of Service covers how long it is kept.

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.

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 a passkey or deleting your account, a record that you did, 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. Both 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, a phone number if you gave one, and your message — together with your IP address and your browser's user-agent string. Those last two are included so that we can identify abuse of the form. The whole of it arrives as an email in our support mailbox.
• - 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.
• - 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

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.

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

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.

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.
• - Legal authorities, if required by law or to protect our rights and safety.

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.

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.

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@sealzi.com.

8. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, the date at the top of this page changes with it, and it is worth reviewing periodically.

9. Contact Us

If you have any questions or concerns about this Privacy Policy or our data practices, please contact us at: Email: support@sealzi.com.

By using Vauz, you agree to this Privacy Policy.