People sign in.
Actual readouts require authentication. Choose who can open a readout: yourself, named teammates, a space, or your business.
Security
Your work.
The right people.
Sharing a useful update should feel straightforward. Here's how Aptarium protects the work you bring into it.
Shared updates have a byline.
A shared readout is a dated edition, published once by a named person. It says whose access supplied its data and when it was captured, and you share it deliberately with the people who need that update.
Live views run as you.
Aptarium reads from connected tools without writing changes back, and there is no shared standing credential. When a readout reads live, it uses each viewer's own connected account.
The details, when you need them.
How are workspaces separated?
Postgres row-level security isolates workspace records. Published readouts use restrictive content-security and sandbox headers, and deployments are scanned for secrets and external origins.
How does agent access work?
Agent credentials have specific permissions and can be revoked from your workspace. Sharing management is an explicit opt-in. You can review setup and credential details in the agent setup guide.
Can I share with a guest?
Guests receive expiring access to a specific readout. They can read published editions, not live data or the skills catalog. Sharing access can be revoked.
What records does Aptarium keep?
Publishing, sharing, connections, agent credentials, editions, and administrative actions are recorded. Our privacy policy and retention policy explain storage and deletion.
Is Aptarium SOC 2 certified?
We are not yet SOC 2 certified. Contact us for factual information about the current service and any data-processing questions.
Get in touch
A question or a concern?
Email support@aptarium.app. For a security report, describe the issue without including credentials or customer data.
Check service status →