> 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

### Authentication and Email Addresses

We use [Privy](https://www.privy.io/) as our authentication and embedded wallet provider.

If you connect or authenticate using an email address, your email address may become associated with your wallet address through Privy's services and our application.

We use email addresses primarily for:

* authentication
* account recovery
* security notifications
* transactional or vault-related notifications

We do not publicly display email addresses (see [details](#vault-participant-visibility) below).

***

### 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 view</th><th>Cannot view</th></tr></thead><tbody><tr><td><strong>Vault owner</strong><br></td><td>Guardian email addresses<br>Recipient email address</td><td></td></tr><tr><td><strong>Guardians</strong><br></td><td>Vault owner email address<br></td><td>Other guardians' email addresses<br>Recipient email address</td></tr><tr><td><strong>Recipient</strong></td><td>Vault owner email address</td><td>Guardian email addresses</td></tr><tr><td><strong>Anyone else</strong><br><br></td><td></td><td>Vault owner email address<br>Guardian email addresses<br>Recipient email address</td></tr></tbody></table>

***

### Analytics and Usage Data

We use [Segment Analytics](https://www.twilio.com/en-us/segment) to understand how the application is used and to improve the user experience.

We may collect limited interaction data, including:

* application version,
* page or URL where an action occurred,
* interaction or event type (such as button clicks or transaction submissions),
* vault address and blockchain network/chain ID where applicable,
* a Privy user identifier.

Segment may automatically collect additional technical metadata associated with requests, such as browser type, device information, timestamps, and approximate location derived from IP address. More information is available in the [Segment tracking documentation](https://www.twilio.com/docs/segment/connections/spec/common?utm_source=chatgpt.com#context).

We do not use analytics data to directly identify users by real-world identity.

***

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

We do not control how third parties index or process publicly available blockchain data.

***

### Third-Party Services

We rely on third-party infrastructure and service providers to operate the app and services. These providers may process certain technical or account-related data on our behalf.

Current providers may include:

* [Privy](https://www.privy.io/) for authentication and wallet services,
* [Segment](https://www.twilio.com/en-us/segment) for analytics and product telemetry.

These providers maintain their own privacy policies and data handling practices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ante.org/privacy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.