Legal
Privacy
Last updated .
This page says exactly what this website stores about you and why. It covers wardensec.ai and its dashboard. Warden itself runs in your own cluster and sends nothing to us.
Who we are
This draft does not yet name the operator of wardensec.ai, who is responsible for the data described here. It will before the site launches.
The short version
- We store the least we need to give you an account and your licenses.
- We do not share or sell anything.
- There are no trackers, ads, analytics scripts or third-party scripts on this site.
- We count requests, but never in a way that identifies you. How we count.
What we store
If you only read the site, we store nothing that identifies you. If you start to sign up, sign in or recover an account, create an account, or request Defend access, we store:
| What | Why |
|---|---|
| While you sign up | Your name and email address are held with the sign-up request until you create your passkey. The request expires after five minutes. If you do not finish, it is deleted soon after and no account is created. |
| Your name | To show on your account and to put in your license as the licensee. |
| Your email address | To contact you about your account, and to recover your account with a recovery code. We do not verify it and we do not send marketing. |
| Passkey public keys | To sign you in. For each passkey we keep its public key, its id, its name (one we give it or one you choose), a counter, its transports, its backup flags, and when it was created and last used. Each account also has a random user handle that your passkeys store for this site. The private key never leaves your device. |
| License records | To list, renew and retire your licenses: the estate label, the optional hub AWS account id, the plan, the dates, the status, and the signed license file itself, which carries your name as the licensee. |
| The issuance book | To account for every license our signing key has signed. The separate service that holds the key writes one entry per license: the license id, the plan and its features, the key id, whether the license names a hub account (yes or no, not which one), the dates, and a SHA-256 hash of the signed file. It holds no name, email, estate label or account id. Entries are kept for as long as the service runs and are never changed. |
| Recovery codes, as hashes | To let you back in if you lose your passkeys. We cannot read the codes themselves. |
| Sessions, as hashes | To keep you signed in for up to 14 days. The cookie holds a random token; we store only its hash. |
| An audit log | To protect your account. Sign-ups, sign-ins and sign-outs, failed sign-ins, recoveries, passkey and recovery code changes, and license events, each with the time, the account, details such as which passkey or license it concerns, a keyed hash of your network address (the IP address, or for IPv6 its first 64 bits) and the browser's user agent (first 200 characters). Failed sign-ins and failed recoveries are logged the same way even when they match no account. License downloads are recorded in the audit log like other license events. The latest entries are shown to you on your account's security page. Entries are deleted after one year. |
| Rate-limit counters | To slow down abuse. Counts keyed by a keyed hash of the network address, by account, or, for mail we send you, by a keyed hash of your email address, deleted once their window (at most a day) has passed. |
| If you Get early access | Your email address, and the company and estate size if you gave them, with the words shown under the button when you pressed it. Used only to send you early access and to check the address an invite is for; the mail it causes is listed below. A sign-up holds only these fields and is not tied to an account unless you open one with an invite we send (see below). It is kept until you ask us to delete it at support@wardensec.ai. |
| If you Request Defend access | Your email address, and the company, estate size and license id if you gave them, with the words shown under the button when you pressed it. Used only to contact you about a Defend license and to check the address an invite is for; the mail it causes is listed below. A request holds only these fields and is not tied to an account unless you open one with an invite we send (see below). It is kept until we have issued your license or you ask us to delete it at support@wardensec.ai. |
| If we approve your request | An invite: a hash of its one-time link (never the link itself), which request it is for, when it was made, when it expires, and when it was withdrawn or used. Once you use it, the invite records the account it opened, so from then on your request is linked to that account, and the account is marked as one that may create licenses. Deleting your request makes an unused invite unusable; deleting your account removes that mark. |
| A record of each mail we send | Which mail it was, the id of the request, invite or account it was for, when, and whether it was sent or why not. Not your address and not the message. Deleted after one year. |
We never store your IP address in the clear. Sessions end after 14 days at most. Account and license records are kept until you delete your account.
Mail we send
We send these emails and no others. None of them is marketing.
- A confirmation, at most once per request, when you Get early access or Request Defend access: that we received it and that requests are approved by hand. Asking again sends no second one.
- An invite, if we approve your request: the one-time link that opens your account.
- A welcome, once your account is open: how to sign in, and a reminder to keep your recovery codes safe.
- To us, not to you: a note for each new request, and one when you ask again after an invite we sent you expired or was withdrawn, with the kind of request and the company you gave, if any. It does not carry your address.
They are sent through Cloudflare Email Service, from an address on wardensec.ai, which hands them to your mail provider. They carry no tracking images or tracking links, and link only to wardensec.ai. Replies go to support@wardensec.ai.
Counting
For counting, we count requests by page type, by kind of client (browser, command line, declared robot) and by result; reading pages also by kind of referring site per day. For counting, we never store your address, your browser's name, the page address you asked for, your country or where you came from. Account and license pages are counted per day only. Our code logs nothing about downloads; the hosting platform keeps its standard request records for its stated retention period. Release files, served under /releases, are not counted, and serving them writes nothing to our database. Feed files, served under /feed/, are not counted and our code logs nothing about them. The status page at /feed is an ordinary page and is counted like any other. There is no analytics script, and nothing on this site asks your browser to report to anyone else.
The audit log described above is separate from counting. It records account actions such as sign-ins, recoveries and license events, and it keeps what the table says.
Cookies
One cookie, __Host-wd_s, set only when you sign in. It keeps you signed in. It is
HttpOnly, Secure and SameSite=Lax, and it is deleted when
you sign out. There are no other cookies.
The verify page
When you check a license on the verify page, the check runs in your browser. The license you paste is not uploaded.
Sharing
We do not share or sell your data. Our hosting provider, Cloudflare, runs the site and its license signing service, stores their databases, and sends the mail listed above, as any host must. We use no other service that receives your data.
Deleting your account
You can delete your account from the dashboard. This deletes your name, email, passkeys, recovery codes and sessions, and the estate labels, hub account ids and files of your licenses. We keep each license id and its status, without your personal data, so that a license that was issued can still be accounted for; active licenses are marked retired. The issuance book keeps its entries, which hold no personal data. Your audit log entries keep the event, its time, its details and the account's random id, but lose the network hash and the user agent. They are deleted when they reach one year, like every other entry. Failed attempts that matched no account are not linked to you and are not changed.
Contact
Questions about this page: support@wardensec.ai.