Trust Center
Where to find what Aardvark does about security, privacy and customer data, what is not in place, and each policy.
The product of an aardvark build is a directory of static files that you own and host. Aardvark cloud (the dashboard and the gateway API) is a separate service, and a site sends data to it only for the cloud features you turn on. The Security page describes the security architecture, including what talks to Aardvark cloud and when.
Turning on the AI assistant turns on other cloud features with it. The privacy policy lists what each cloud feature sends and stores, and which are on by default, under What we process for our customers about their readers.
Find an answer
Each topic links to the section that states it.
- Independent audit: SOC 2 status
- Penetration testing: Secure development and supply chain
- Sign-in and team access: Authentication, Team security in the dashboard
- Payments and card data: What we collect
- No AI training on your data: Your content in the Terms
- What Aardvark cloud may not be used for: Acceptable use in the Terms
- Model providers: Model providers
- Where data is processed: Where data is processed
- How long data is kept: Retention schedule
- Closing an account and erasure: Closing an account, Erasure
- How personal data is used: How we use personal data
- Privacy requests: Your rights
- Security incidents: Security incidents
- Subprocessors: The list, changes to it
- Availability: Availability
- What is not in place: each section of the SOC 2 page lists it.
Documents
What personal data Aardvark collects, why, who receives it, and how to exercise your rights.
Whether Aardvark has been audited, what is in place, and what is not.
The vendors that handle customer data for Aardvark cloud, and what each one receives.
How long each kind of record is kept, what closing an account does, how erasure works, and which exports exist.
The terms that apply when Aardvark processes personal data on your behalf.
The agreement for using Aardvark cloud: accounts, fees, acceptable use, liability and termination.
The security architecture: what talks to Aardvark cloud and when, and how to report a vulnerability.
What personal data Aardvark collects, why, who receives it, and how to exercise your rights.
Whether Aardvark has been audited, what is in place, and what is not.
The vendors that handle customer data for Aardvark cloud, and what each one receives.
How long each kind of record is kept, what closing an account does, how erasure works, and which exports exist.
The terms that apply when Aardvark processes personal data on your behalf.
The agreement for using Aardvark cloud: accounts, fees, acceptable use, liability and termination.
The security architecture: what talks to Aardvark cloud and when, and how to report a vulnerability.
Contact
For privacy, security and legal questions, and for data requests, email support@aardvarkdocs.com.
To report a security vulnerability, see Reporting a vulnerability.