AETHER AIPortal
AI Products
AETHER-PREDATORQuantum Red Team EngineAETHER-SCRAMBLERGhost Protocol MTD
Trading
AETHER PROTOCOL-LQuantum Commitment LayerAETHER PROTOCOL-CCSPRNG Commitment LayerAETHER PROTOCOL-TTEE Attestation Layer
Sign inSign up
Contact
PortalAI Products

CyberSecurity

AETHER-PREDATORAETHER-SCRAMBLERTrading

Protocol Family

AETHER PROTOCOL-LAETHER PROTOCOL-CAETHER PROTOCOL-T
Sign inSign up
Contact

Access Control Policy

Last updated: 2026-07-19

1. Purpose

This policy describes how access to AetherCloud's production systems, customer data, and source code is granted, reviewed, and revoked.

2. Principle of least privilege

Access to any production system, database, or secret is granted only for a specific, documented purpose, and scoped to the minimum permissions that purpose requires. Standing broad-admin access is avoided in favor of task-scoped credentials where our tooling supports it.

3. Authentication

  • Production infrastructure access requires key-based (not password-based) authentication over an encrypted mesh network.
  • Customer-facing authentication (Supabase Auth) supports standard email/password and OAuth flows with session tokens scoped and expired appropriately.
  • Secrets and credentials are never committed to source control; they're injected via environment configuration and rotated when there's reason to believe they've been exposed.

4. Authorization

Row-level security policies enforce data isolation at the database layer — a user's access to another user's data is denied by default, not merely hidden by application logic. Team-tier role-based access (owner / admin / member) is planned as part of upcoming team-management features (see our Trust page's control-mapping table) and will be enforced at both the API and database layers when shipped.

5. Review and revocation

Because AetherCloud is operated by a single founder-engineer today (see our Trust page for how we handle the solo-operator structure), access review is continuous rather than a scheduled quarterly process — every credential and access grant that exists is one the operator personally provisioned and can enumerate. As the team grows, this policy will be updated to include periodic formal access reviews and a documented offboarding checklist.

6. Logging

Access to customer vault data is logged in an append-only, cryptographically hash-chained audit trail (Protocol C) that vault owners can view directly via the audit endpoint. See our Trust page for how this maps to SOC 2 criteria.

Site footer

Follow what ships

Read the product release notes, or contact the team with a question.

Release notesContact the team
Aether AI

Secure desktop AI for agents, files, automations, and signed proof.

Product

  • AetherCloud
  • Pricing
  • Agents
  • Vault
  • Audit Trail

Resources

  • Documentation
  • Blog
  • Comparisons
  • Docs
  • Protocol Family
  • ATS
  • Glossary
  • Whitepaper: Unlimited Context
  • Whitepaper: Protocol-C
  • Whitepaper: Aether Atlas
  • Weekly Dispatch: July 15, 2026
  • Journal: Inside AetherATS 2.0

Company

  • App / Sign in
  • Contact
  • Demo

Legal

  • Privacy
  • Terms
  • Billing Policy
  • Trust
  • Do Not Sell My Info

© 2026 Aether AI LLC. All rights reserved.