Security

Last updated 23 October 2026

You're trusting PhysicsBase with the keys to your APIs. This page explains how we protect them, what we store, and what we don't do yet. If anything here is unclear, ask us at support@physicsbase.ai.

Your API keys

• Encrypted at rest. Every credential you put in the vault is encrypted with AES-256-GCM before it is written to the database.
• The encryption key lives somewhere else. It is kept in our hosting provider's secret settings, not in the database or its backups, so a copy of the database alone can't open the vault.
• Agents never see them. PhysicsBase adds the credential to the request on its way out. The agent only ever holds its own identity, so a prompt injection or a leaked agent log can't expose your Stripe key.
• Never shown again. After you save a credential, the dashboard and the API show only its last four characters. You can rotate or remove it at any time, and every agent uses the new one at once.

Agent identities

• Each agent has its own key pair. Its tokens are signed with Ed25519, last five minutes and are bound to the agent's key, so a copied token is useless on its own.
• Hosted agents (connected by URL, with nothing installed) have their private keys encrypted in the vault, like your API credentials.
• Secrets we issue are stored as one-way hashes: enrollment keys, API tokens, connector tokens, sign-in codes and session IDs. We can check them but can't read them back.
• Revocation is immediate for calls through PhysicsBase: a revoked agent is refused on its next call. Revoking a policy or enrollment key revokes every agent it registered.

Calls to other APIs

• Only to APIs you connected, and only for agents whose policy allows it.
• Never into a private network. The address each outgoing connection actually reaches is checked at the moment it connects, so internal addresses, cloud metadata services and DNS-rebinding tricks are refused. Redirects are not followed.
• Limited. Per-agent limits per minute and per day, a 30-second timeout and a 5 MB response limit stop runaway loops and oversized responses.
• Signed. Outgoing calls carry Web Bot Auth signatures so the receiving site can verify they came from your agent through PhysicsBase.
• Bodies are not stored. Request and response bodies pass through; the activity log keeps the agent, API host, method, path, status and the reason the agent gave.

Your account and organisation

• No passwords. You sign in with a passkey or a one-time email code.
• Roles. Owners, admins and viewers. Only admins can connect apps, change policies or manage credentials. API tokens can never manage people, other tokens or the organisation itself, and never do more than the person who created them.
• Separate organisations. Every query is scoped to your organisation.
• Your data, your call. Export your organisation's data or delete it, and your account, from the dashboard at any time. Activity is kept for 365 days; backups are kept for up to 14 days.

Running the service

• HTTPS only, with HSTS, a strict content security policy and secure, HTTP-only cookies.
• Monitored. We check the service from outside every hour and are alerted to errors and crashes automatically.
• Tested. Every change runs an end-to-end test suite that includes attacks: stolen tokens, replayed requests, calls to internal addresses, cross-site requests and revoked agents.
• Daily backups of the database. The vault encryption key is not in them.

What we don't have yet

PhysicsBase is young. We haven't had an independent security audit or penetration test, and we don't have SOC 2 or ISO 27001 certification yet. We'll list them here when we do. If your company needs any of these before it can use a vendor, talk to us.

Reporting a vulnerability

Email support@physicsbase.ai with what you found and how to reproduce it. We'll reply within three working days, keep you updated while we fix it, and credit you if you'd like. Please don't access other people's data or degrade the service while testing. Our security.txt has the same details.