Data & Security
Golemry runs automations on your real accounts. This page documents what we store, where, for how long, and who processes it.
Last updated: June 2026
Security is the whole point
Golemry only makes sense if it is safe to hand an agent your accounts.
That makes security the product, not a feature bolted on later. Those accounts are your inbox, your payments, your customer data, so we hold them to the highest standard we can: the agent never sees your credentials, and every job gets only the access it needs. Where we find a gap, we close it.
How we keep your accounts and data safe
The agent never holds your keys
When a job uses a connected account, the action runs in a separate, isolated service that holds the credential. The agent only ever sees the result, never the account or its credentials.
Your connections in a vault
The accounts you connect are held by Composio, a dedicated connections provider, in a workspace scoped to your account. Golemry stores the connection reference, never your passwords or raw access tokens.
Per-job least privilege
The agent can only act through the specific tools each job is granted, nothing more. A job set up to draft email replies is handed only that action, so it cannot read your inbox, send mail, or reach any other connected account.
Sandbox & tenant isolation
Each run executes in an isolated, sandboxed environment that is torn down when the run ends. One job's run cannot reach another's.
Every run is reviewed
An independent overseer agent reviews every run, recording a verdict and flagging suspicious behavior or signs of prompt injection so it surfaces to you.
Your data is yours
Your automation configurations, outputs, and feedback belong to you. We never use your data to train general-purpose AI models or share it across accounts.
Encryption at rest
Credentials you provide directly, such as your model key, are encrypted at rest with strong, industry-standard encryption and isolated per account.
Bounded retention
Run data, including transcripts, artifacts, logs, and observability traces, is kept for 30 days and then deleted.
Where your data goes when a job runs
When a job runs, here is how your data is handled, where it lives, and how long it stays.
- 1
Your connected accounts
To do its work, the agent reads from or writes to the accounts you connected, such as Gmail or Stripe.
Where
Held by Composio, scoped to each jobRetention
Until you disconnect the account - 2
The run sandbox
Each run happens in a fresh, isolated sandbox in the cloud. Your data is only there while the job runs.
Where
Google Cloud (US)Retention
Erased when the run ends - 3
The AI model
The agent sends your prompt and the content it works on to your chosen model, using your own key.
Where
The provider you choose: OpenAI, Anthropic, Google, or routed via OpenRouterRetention
The provider's own policy applies - 4
Run traces
A step-by-step record of each run, used to debug and diagnose problems when something goes wrong.
Where
Langfuse (EU)Retention
30 days - 5
Golemry's storage
Your job setup, run history, transcripts, and results are saved so you can return to them.
Where
Supabase (US); files in Google Cloud Storage (US)Retention
Run outputs are kept 30 days
What we store and for how long
| Category | Where | Retention |
|---|---|---|
| Account info | Supabase (US) | Account lifetime |
| Job config, schedules & executions | Supabase (US) | For the life of the job |
| Agent conversation transcripts & memory | Supabase (US) | 30 days |
| Run artifacts | Google Cloud Storage (US) | 30 days |
| Logs | Google Cloud (US) | 30 days |
| Observability traces | Langfuse (EU) | 30 days |
| Analytics & session replay | PostHog (EU) | Analytics retained long-term; recordings ~3 months |
Core application data and job execution are hosted in the US (Supabase, Google Cloud, Temporal Cloud, Fly.io). Observability (Langfuse) and product analytics (PostHog) are EU-hosted. We do not claim EU residency for the overall data path.
Subprocessors
Every external service that processes customer or job data, with its purpose, region, retention, and a link to its own data or security documentation.
| Service | Purpose | Region | Retention |
|---|---|---|---|
| Connectors | |||
| Composio | Connectors and third-party tool access | US | Until you revoke the connection |
| Hosting & infrastructure | |||
| Supabase | Database, storage and authentication | US | Account and job lifetime; run outputs 30 days |
| Vercel | Hosts and serves the web application | US | Operational logs, short-term |
| Cloudflare | Bot protection (Turnstile), privacy-friendly web analytics, and MCP server hosting | Global edge | Per Cloudflare's policy |
| Google Cloud (Cloud Run) | Agent runtime for job execution | US | Ephemeral, no job content persisted beyond the run |
| Temporal Cloud | Schedule execution and orchestration | US | Account and job lifetime |
| Fly.io | Hosts the Temporal worker | US | Ephemeral compute |
| AI models | |||
| OpenAI | Model inference for the model you choose, with your own key | US | Per the provider's own policy |
| Anthropic | Model inference for the model you choose, with your own key | US | Per the provider's own policy |
| Model inference for the model you choose, with your own key | US | Per the provider's own policy | |
| OpenRouter | LLM provider routing for the model you choose, with your own key | US (routes to your chosen provider) | The LLM provider's own policy applies |
| Observability & analytics | |||
| Langfuse | Observability and tracing | EU (Frankfurt) | 30 days |
| PostHog | Product analytics and session replay | EU (Frankfurt) | Analytics retained long-term; session recordings ~3 months |
| Billing | |||
| Autumn | Billing and subscription management | US | Account term |
| Stripe | Payment processing | US | Account term plus statutory payment-record retention |
| Resend | Transactional email and contact-form delivery | US | Per data processing agreement |
Where personal data is processed in the US, those transfers rely on appropriate safeguards (Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework). Composio, our connections provider, is SOC 2 and ISO 27001:2022 attested and publishes a public trust center.
What we don't claim
We hold no SOC 2 report, ISO 27001 certification, published penetration-test summary, status page, or bug-bounty program for Golemry yet. Instead, we show you exactly how your data is handled today. The safeguards above are real and in place.
Security contact
Found a vulnerability or have a security question? We read every report.
security@golemry.com