Security

Access controls

• Roles. Each workspace member is an owner, admin, operator or viewer. Viewers can see work but not act on it; approving work needs at least an operator; the approval policy, billing and members need an admin or owner.
• Sign-in. Passwords are stored only as scrypt hashes. Sign-in and sign-up attempts are rate-limited. “Continue with Google” is available, and Anthenos keeps no Google token.
• Sessions live in a cookie scripts cannot read, sent only over HTTPS. Anthenos stores only a keyed hash of each session’s secret, so a copy of the database cannot be used to sign in, and every session ends 30 days after it began.

Encryption

• In transit. Anthenos is served only over HTTPS, and tells browsers, with HSTS, never to reach it any other way.
• Secrets at rest. Credentials, signed-in sessions, API keys and references to connected accounts are encrypted with AES-256-GCM, each bound to the record it belongs to, under a key the application refuses to start without in production.

Credential and token protection

• When you sign in to a portal through Anthenos’s secure sign-in, what you type is encrypted while it waits to be entered, and deleted as soon as it has been.
• Stored credentials are decrypted only on Anthenos’s servers, when a workflow needs them, and are never sent to the browser or to an AI model.
• Access tokens for connected email and business accounts are held by Composio, the connection provider; Anthenos keeps an encrypted reference to the connection. Disconnecting an account deletes the connection there too.
• Logs are written with passwords, tokens and keys removed.

Approval controls

• Every action Anthenos can take in a portal is named, and your workspace’s policy says which run automatically, which wait for a person, and which Anthenos never does on its own.
• Some limits cannot be relaxed: Anthenos never changes where a customer’s money is paid — bank or remittance details — on its own.
• An approval shows what Anthenos found and recommends, and is refused if the facts it was based on have changed since.
• When a portal asks for a person — a CAPTCHA or another security check — Anthenos stops and asks you. It never tries to get past it.

Audit trails and verification

• Every work item keeps a timeline of what happened, who or what did it, and when.
• After acting, Anthenos reads the portal back and keeps what it saw as evidence. A result it cannot verify is marked as such, not reported as done.
• A security audit log records consequential events — sign-ins, role changes, policy changes, connections, approvals and work items created or cancelled. The database refuses to change or delete its entries.

Isolation between organizations

Every piece of a workspace’s data carries its workspace, and every query is scoped to the workspace of the person asking. That workspace comes from their session, never from the request, so a request cannot name another workspace. Automated tests create overlapping workspaces and check that each read returns only its own data.

Application safeguards

• A strict Content-Security-Policy: pages load scripts, styles, images and fonts from Anthenos alone, and cannot be framed by another site. The one exception is Whop’s marketing pixel, which the public pages load only once you have allowed marketing, and which no page inside your workspace loads at all.
• Requests Anthenos makes to addresses it is given are checked before they are made and again on every redirect, and refused if they point at a private network.
• Uploaded files are checked against their contents before they are stored, and nothing in them is executed.
• Text read from a portal or a document is treated as data, never as an instruction.

Monitoring

The service has health checks that the hosting platform uses to detect and restart failed processes, structured logs of requests and errors, and operational alerts for the people who run it. Consequential actions are recorded in the audit log described above.

Incident handling

If we learn of a security incident, we investigate it, act to contain it, and fix its cause. If it affects your data, we notify you without undue delay, with what we know and what we are doing about it, as the law and our Data Processing Addendum require.

Data retention controls

• Disconnect a system, or remove its credentials, at any time.
• Download a copy of your data from Settings.
• Delete your account in Settings, which deletes the workspaces you alone own and everything in them.
• Ended sessions, finished background jobs and closed secure sign-ins are deleted on a schedule. The Privacy Policy sets out how long each kind of information is kept.

Certifications

This page describes the safeguards Anthenos has today. It does not claim any third-party certification or audit. When that changes, this page will say so.

Reporting a security problem

Send reports to hello@aethric.llc. The same address is published in /.well-known/security.txt. Please include what you found and where, the steps to reproduce it, what somebody could do with it, and how to reach you.

• Test only with your own account and your own workspace.
• Do not open, change or delete anybody else’s information. If you come across it, stop and tell us.
• Do not disrupt the service: no denial-of-service testing, no flooding, and no messages sent to other people.
• Please do not make a problem public before it has been fixed.

Anthenos does not run a bug bounty.

What you can do

• Use a password of at least 12 characters that you use nowhere else.
• Give each person their own account, with the least role they need.
• Keep sensitive actions on “Needs approval” until you trust how they run.
• Disconnect portals and systems Anthenos no longer needs.
• Review exceptions and approval requests before you act on them.