Security
We sign in for you. Here's what keeps that safe.
Rindler signs in to sites on your behalf, so the honest starting point is that a credential is handed over. This page is what happens to it after that: where it is stored, what a session can reach, what is written down, and how you end it.
What we are certified for today: nothing.
We do not claim certifications we have not earned. Rindler is not currently SOC 2, HIPAA, or PCI certified. Rindler is actively working toward SOC 2 certification. It isn't certified yet, but the process is underway. We are happy to walk an enterprise procurement team through our actual posture on request.
How signing in works
For most sites Rindler never sees your password. You sign in yourself, once, and Rindler keeps only the session that sign-in produced.
You do the sign-in, in a real browser
Rindler opens a single-use link, which expires in 15 minutes, to a Rindler-managed browser on the site's own login page. You sign in there and finish any verification the site asks for, including MFA, then click "I'm logged in."
Two-factor codes are not stored
On most sites you complete 2FA yourself in that managed browser and Rindler never sees the codes. On sites that mandate a fresh one-time code every time, Rindler collects the code for the current task only and never saves it.
Stored credentials are opt-in, per site
For a limited set of sites you can let Rindler store your credentials so it can sign in for you. That option is opt-in, chosen per site, and encrypted. It is not the default and it is not required.
How credentials and sessions are stored
Credentials are encrypted the moment you enter them and stay encrypted through every run. They are never shown to the models doing the work.
AES-256-GCM under a per-user key
Session cookies are extracted from the managed browser, encrypted with AES-256-GCM under a key derived per user, and stored encrypted. They are decrypted only when a run reuses that authenticated session on your behalf.
The key is not in the database, the logs, or the API
The encryption key is held in our secrets manager. It is never logged and never returned in an API response.
Production access is limited and recorded
Access to the encrypted production database is limited to the engineering team through signed-in Porter access, and we record an audit trail of any direct database session.
What one connection reaches
Each site's access is handled separately. Connecting one never grants another, and disconnecting ends it.
Scoped to you and to one site
A stored session is scoped to your account and to the single site it was created on. There is no shared pool and no cross-site reuse.
It reaches only what you could reach yourself
Rindler acts on sites you already have access to, signing in with your own account the same way you would in your own browser. It does not create accounts and it does not defeat access you do not have.
Memory is scoped per user
The durable memory an agent uses to carry site quirks across runs is scoped per user and never returns another user's data.
What a session can and cannot do
A session reads records and takes the actions a site exposes. The boundary on what it changes is deliberate.
Nothing changes without your instruction
Nothing books, pays, reorders, or changes a record without your explicit instruction. Rindler does not move money on your site accounts on its own.
Card details never reach Rindler
Rindler does not receive or store payment-card numbers. Third-party carts hand off so you check out on that site yourself, and Stripe separately collects and processes card details for Rindler subscriptions.
Downloads expire
When an action captures a file, the result carries a direct link that expires in about 30 minutes rather than a permanent public URL.
What is logged
Every run shows up in your account with what it did, so nothing happens out of sight.
Runs are visible to you
Each run is recorded in your account against the site it touched, including the runs that end a connection. Nothing about a disconnect happens off the books.
Operational telemetry is redacted before it leaves
We keep operational logs, aggregate counters, and crash reports. Sensitive fields are redacted server-side before a crash report is sent to Sentry, and PII-bearing fields are redacted before persistence.
No session replay, no fingerprinting
Rindler uses no ad trackers, no fingerprinting and no session-replay, and does not sell or share your personal information with advertisers or data brokers.
What the models receive
Credentials are never shown to the models doing the work. Your messages, system prompt and tool results are sent to the model provider, with training and default retention opted out.
Training and retention are opted out
Anthropic's default API tier does not train on inputs, and OpenAI requests are sent with store:false to opt out of default retention.
You are not identified to the provider
Your name, email and Clerk ID are never sent as request metadata.
Revocation and retention
You can end any connection yourself, and the record of it is deleted rather than deactivated.
Revoking deletes the encrypted record
Revoke any authenticated session and the encrypted cookie record is deleted, so we can no longer act on your behalf at that site.
Expired sessions are not silently refreshed
Encrypted browser sessions are retained until the underlying third-party cookie expires or you revoke the session. When one stops working the next call returns an expiry signal and you re-authenticate through the same one-time flow.
Deletion, and a clock on it
We honor access, correction and deletion requests within 30 days. Chat history can be set to auto-delete after 7, 30 or 90 days. Operational telemetry is retained for up to 12 months for reliability work.
Running a security review?
Send us the questionnaire and we will fill it in. Email [email protected], the same address that answers data-deletion and privacy requests.
Reporting a vulnerability instead? Our security.txt carries the same contact in the machine-readable form RFC 9116 describes. For what we collect, who processes it, and your rights over it, see the privacy policy and the security & privacy FAQ.
Automate the sites your work depends on.
Book a scoping call and we'll scope your sites, volume, access, and terms, then tell you exactly what we would deploy.