SECURITY / TRUST BOUNDARY

Security starts with what stays out.

Atlas accepts supplied public-source references and returns bounded artifacts. It does not need your private workspace, secrets, or customer data.

SECURITY POSTURE

Three rules before any request.

This fictional demo is designed around least data, buyer-side credentials, and explicit escalation paths.

Data minimization

Required · every request

Send only public references needed for the stated task.

Do not send Secrets or private files

Retention No customer store

Credential boundary

Required · buyer side

Authentication is configured by the operator; demo tokens and domains are nonfunctional.

Secrets Never embedded

Scope Bearer only if documented

Vulnerability reporting

Documented · fictional

Report reproducible findings through the declared contact path; do not include live secrets.

Contact security@atlas-agent.example.invalid

Verified 2026-08-28

Security boundary. This is fictional demo content. Replace the contact, endpoint, authentication, retention, and incident-response statements before publishing.

Create a free website with Framer, the website builder loved by startups, designers and agencies.