> For the complete documentation index, see [llms.txt](https://docs.ante.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ante.org/privacy.md).

# Privacy

How Ante collects, uses, and discloses information when you use the Ante Vaults app and related services.

### Accounts, email addresses and wallets

You sign in with your email address, or with a Google account. Sign-in is handled by Privy, which verifies your email with a one-time code and keeps your sign-in details. When you first sign in, Privy creates a wallet for you (your Ante Wallet). Your Ante wallet is what signs transactions and manages your vaults. Ante does not hold a key to it.

When you sign in via email or Google login, Privy receives the email address and name of your Google account.

We use your email address to:

* sign you in, with one-time codes,
* send notifications about your vaults: check-ins due and missed, deposits and withdrawals, guardians and recipients added or removed, handoff progress, unrecognised transactions queued in a vault, and changes to vault settings,
* let a vault owner name you as a guardian or recipient of their vault (see People you add to a vault),
* answer requests you send us.
* If you turn on two-factor authentication, Privy holds the passkey or authenticator enrollment.

Your email address is not publicly displayed and does not appear in the public view of any vault. The table below shows who can see your email address inside a vault, and when.

***

### Vault participant visibility

Email visibility inside the application is intentionally restricted.

Depending on a user's role within a vault, limited participant information may be visible to other authorized participants.

<table><thead><tr><th width="128.40625">Role</th><th>Can see</th><th>Cannot see</th></tr></thead><tbody><tr><td><strong>Vault owner</strong><br></td><td>The email address a vault owner entered for each guardian and the recipient, marked as entered by an owner, since Ante does not confirm that it belongs to that person's wallet; and whether each has answered Ante's verification email</td><td>Vault owner can see all information</td></tr><tr><td><strong>Guardians</strong><br></td><td>The vault, its owner by wallet address and email, and the other guardians by wallet address</td><td>Other guardians' email addresses, the recipient's email address</td></tr><tr><td><strong>Recipient</strong></td><td>Nothing about the vault until the owner asks them to confirm their role or a handoff to them is under way; from then on, the vault and its owner by wallet address and email address</td><td>Guardians' email addresses</td></tr><tr><td><strong>Anyone else</strong><br><br></td><td>That a vault exists at an address on a network, the wallet addresses involved (owner, guardians and recipient), since these are onchain, and whether a handoff is under way or complete</td><td>Any email address, and who is behind those wallet addresses unless they already know that person's email address (see Finding a wallet from an email address, below)</td></tr></tbody></table>

A person who is both a guardian and the recipient of the same vault is treated as a guardian.

Guardians and the recipient see the owner's email address only when the owner's own Ante account made or imported the vault and no one else's account holds one of its keys. Otherwise they see the owner by wallet address only.

#### Finding a wallet from an email address

Anyone signed in to Ante can enter an email address, as a vault owner does to name a guardian or recipient, and see the wallet Ante made for it. Wallet addresses are public on Ethereum, so someone who already knows your email address can find the vaults where that wallet appears, as owner, guardian or recipient. The same holds for the email addresses you give for your guardians and recipient.

To keep your vaults apart from the email address you use every day, see "Can someone find my vault from my email address?" in the [FAQs](https://docs.ante.org/faqs.md).

***

### Email notifications

When you name a guardian by email address, they will receive an email notification with a single-use link; opening it confirms their role, and no sign-in is needed. The email names the owner by email and displays the complete vault address. If an owner enters an email address for a guardian's or recipient's wallet and that address does not belong to that wallet, Ante does not send it any email.

When the owner asks a recipient to confirm their role, the recipient receives an email notification that includes the owner’s email address. Otherwise, recipients do not receive any notification until the handoff process has begun. Once the handoff process begins, the recipient will receive a notification that includes the owner’s email address and the full vault address. There is no action required by the recipient.

These emails name the owner by email address under the same condition as above; otherwise they say "the owner".

### Analytics and diagnostics

**Product analytics.** We use [Segment Analytics](https://www.twilio.com/en-us/segment) to understand how Ante Vaults is used. For each interaction we may record:

* the application version,
* the page where the action happened, as its path, together with any campaign parameters from the link you arrived through,
* the type of interaction, such as a button click or a transaction submission,
* the vault address and network where applicable,
* a referral code, if you arrived through one,
* your Privy user identifier.

The rest of a page's address, such as sign-in and confirmation parameters, is not sent. Segment adds technical metadata of its own, such as browser and device type, timestamps and an approximate location derived from your IP address; see the Segment tracking documentation. Segment forwards this data to Amplitude, where we analyze it. Analytics data does not include your email address.

**Error reports:** We use [Rollbar](https://rollbar.com/) to learn about errors in the app and on our servers. A report from the app carries the error, the page path where it happened, the sequence of clicks and requests that led to it, the application version and your Privy user identifier. It does not carry what you typed into any field, the parameters of the page address, or any email address. Your IP address is shortened to its network prefix before it is stored.

**Bug reports you send:** if you send us a bug report from the app, your description travels as you wrote it, together with the page path, your browser and screen size, your language setting, your Privy user identifier, and a list of the app's most recent requests to our servers (their identifiers, methods and outcomes).

**Server logs:** our servers keep a log of requests: time, request identifier, your IP address, and the request path with sensitive parts removed. These logs are used for security, abuse handling and troubleshooting and are kept for a limited period.

**Location:** we determine the country you connect from, using your IP address, to apply regional restrictions on the service. The country is read from our hosting provider's connection information where available, and otherwise looked up through an IP geolocation service. We do not keep a history of your location.<br>

***

### Blockchain Data

Because the app and services interact with public blockchains, certain information is inherently public and permanently accessible, including:

* wallet addresses,
* submitted transactions,
* smart contract interactions,
* blockchain balances and activity.

Vault addresses and the wallet addresses of their participants are among this data. We do not control how third parties index or process publicly available blockchain data, and we cannot remove it.

***

### Information kept on your device

The app keeps some information in your browser so it can open quickly and resume what you were doing:

* your Privy user identifier, wallet address and username,
* the addresses of your vaults, aliases you give them and settings you choose,
* transactions you have queued and vault setups you have not finished, by address,
* a form you are in the middle of filling in, for up to a day, which may hold an email address you typed.

Your email address and other people's contact details are otherwise not stored on your device. Your withdrawal allowlist is stored on our servers encrypted with a key derived from a signature of your wallet, which the app keeps only for the life of the browser tab. Privy's software stores its own sign-in session in your browser; see Privy's privacy policy.

***

### Service providers

We rely on providers that process information on our behalf to operate the app and services. Each has its own privacy policy.

<table data-header-hidden data-search="false"><thead><tr><th>Provider</th><th>What it does for us</th><th>What it handles</th></tr></thead><tbody><tr><td>Provider</td><td>What it does for us</td><td>What it handles</td></tr><tr><td><a href="https://www.privy.io/">Privy</a></td><td>Sign-in and embedded wallets</td><td>Your email address, your wallet address, your user identifier</td></tr><tr><td><a href="https://www.twilio.com/en-us/segment">Segment</a></td><td>Product analytics</td><td>The interaction data listed above</td></tr><tr><td><a href="https://amplitude.com/">Amplitude</a></td><td>Analytics reporting</td><td>Interaction data forwarded from Segment</td></tr><tr><td><a href="https://rollbar.com/">Rollbar</a></td><td>Error reporting</td><td>The error reports described above</td></tr><tr><td><a href="https://aws.amazon.com/">Amazon Web Services</a></td><td>Sending email</td><td>Emails we send you and their delivery status</td></tr><tr><td><a href="https://www.netlify.com/">Netlify</a></td><td>Hosting the web app</td><td>Requests for the app's pages and files, including your IP address</td></tr><tr><td><a href="https://www.alchemy.com/">Alchemy</a></td><td>Reading blockchain data and submitting transactions</td><td>Requests sent to the blockchain (handles addresses) and your IP address for logs</td></tr></tbody></table>

### How long we keep information

| Information                           | Kept                                                                                                        |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Account and profile                   | As long as your account exists                                                                              |
| Vault records and activity            | While the vault exists, and after it is archived                                                            |
| Email confirmation links              | 72 hours after they expire; such a link is valid for a year                                                 |
| Guardian and recipient invitations    | 90 days after an unconfirmed invitation expires or is withdrawn; a confirmed role for as long as it is held |
| Record of one-off announcement emails | The fact that an announcement went to your account, by account identifier, without the address              |
| Server request logs                   | A limited period                                                                                            |
| Analytics and error reports           | According to each provider's retention                                                                      |
