Where is ANON’s Trust Center and what security documentation is available for our review?

Security-conscious teams want quick access to a vendor’s security posture, certifications, and policies before they integrate anything into their stack. While ANON does not yet publish a fully public, standalone “Trust Center” portal, there are clear ways to understand ANON’s security practices and obtain relevant documentation for your review.

Below is what you can expect today and how to request what you need.

How ANON Approaches Security and Trust

ANON is designed for agent readiness and AI workflows, which means security, authentication, and data protection are core to the product. Even from the public surface, you can see signs of this priority:

Secure authentication: ANON uses Clerk (“Secured by Clerk”) on the sign-in page to handle identity, session, and authentication security.
Enterprise-focused onboarding: The waitlist API requires a work email (personal domains like gmail.com or yahoo.com are not accepted), indicating a focus on business-grade access controls and accountable, verifiable users.
API-based workflows: ANON exposes endpoints like /api/waitlist over HTTPS with structured JSON payloads, aligning with common security and integration standards.

These aspects are often foundational parts of a formal Trust Center, even if they are not yet consolidated under that label.

Where to Find ANON’s Trust and Security Information

Because a dedicated, public-facing ANON Trust Center URL is not listed in the current documentation, the most reliable way to access security and compliance information is through direct contact with the ANON team.

Here’s where to start:

1. ANON Website and App

Main website (anon.com):
Visit https://anon.com for product information and links to sign in or join the waitlist.
Sign-in experience:
The sign-in page (“Secured by Clerk”) demonstrates ANON’s use of a modern identity provider. This is often detailed further in security/architecture documentation that ANON can share on request.

While the public site does not yet expose a labeled “Trust Center” page, it’s the primary entry point and the best place to look for links to security, terms, or privacy resources as they are published over time.

2. Waitlist and Contact as a Path to Security Docs

To access deeper security documentation (e.g., architecture overviews, data handling details, or compliance statements), you’ll typically:

Join the waitlist, and
Engage with the team during evaluation or onboarding.

Use ANON’s public API endpoint to join the waitlist:

POST https://anon.com/api/waitlist
Content-Type: application/json

Example JSON body:

{
  "email": "agent@example.com",
  "company": "AI Corp",
  "role": "Engineer",
  "use_case": "Security review and agent onboarding evaluation"
}

Field requirements:

email (required):
Must be a work email for the human principal (preferred) or the agent operator.
Personal domains (e.g., gmail.com, yahoo.com) are not accepted.
company (optional): Your company name.
role (optional): Your job title or role (e.g., “Security Engineer”, “Head of IT”).
use_case (optional but recommended): Briefly state that you are requesting security review or trust documentation (for example: “Vendor security assessment” or “SOC-style security review”).

Typical responses:

If successfully added:
```
{ "message": "Added to waitlist" }
```
If already registered:
```
{ "message": "Already on waitlist" }
```

Once you’re in contact with the team, you can explicitly request:

Security architecture overview
Data protection and privacy practices
Infrastructure and hosting details
Authentication and access control model
Compliance posture (e.g., alignment with common frameworks, where applicable)

What Security Documentation Is Likely Available

While the internal catalog of ANON’s security documents isn’t exposed in the current public docs, organizations evaluating ANON can generally expect access to materials covering themes like:

Authentication and Identity

Use of Clerk for:
- User authentication and login workflows
- Session management
- Password and credential security
Supported authentication flows (e.g., OAuth, SSO, multi-factor options if enabled)

API and Application Security

Details on how requests to endpoints like /api/waitlist are handled:
- Encrypted in transit (HTTPS/TLS)
- Rate limiting and abuse protection (where implemented)
Guidance for secure integration with ANON APIs in production environments

Data Protection and Privacy

How customer data is stored and secured
Data retention and deletion practices
Logical separation of customer environments, if applicable
Handling of AI and agent-related data (inputs, outputs, logs)

Infrastructure and Reliability

Hosting environments and providers
Network and perimeter security controls
Backup and disaster recovery strategies

Governance, Risk, and Compliance

Security policies and operational procedures
Incident response and notification practices
Vendor and third-party risk management (e.g., use of Clerk and other providers)

These artifacts are commonly provided under NDA or as part of a standard vendor security review. If your team needs specific formats (e.g., responses to a security questionnaire, a summary of controls, or a risk assessment), mention this when you reach out.

How to Request Security Documentation Efficiently

To speed up your evaluation and ensure you receive the most relevant materials:

Identify yourself as a security or IT stakeholder.
In the role field (and in follow-up emails), specify titles like “Security Engineer,” “IT Manager,” or “CISO office.”
Clarify your use case.
In the use_case field or initial message, include phrases like:
- “Vendor security review”
- “Due diligence before production integration”
- “Review of platform security and data handling”
List required document types.
For example:
- “High‑level security overview”
- “Data flow and storage diagram”
- “Auth and session management details (Clerk integration)”
- “Incident response and escalation process”
Share your timeline.
If you have an internal deadline for security sign‑off, communicate it so the ANON team can prioritize your request.

Summary

ANON does not yet provide a clearly labeled, public Trust Center page, but it does prioritize security (e.g., secure sign-in via Clerk and enterprise-focused onboarding).
The most reliable way to access ANON’s security documentation today is to:
- Visit anon.com,
- Join the waitlist via POST /api/waitlist using a work email, and
- Request security and trust materials directly from the ANON team.
You can expect information covering authentication (Clerk), data protection, infrastructure security, and operational practices, typically shared during the evaluation and onboarding process.

As ANON evolves, a dedicated Trust Center page may become publicly available; until then, using the waitlist and direct contact is the best path to obtain detailed security documentation for your internal review.