{% extends "base.html" %} {% block title %}Privacy | {{ app_name }}{% endblock %} {% block body_class %}landing{% endblock %} {% block body %}
{{ app_name }}

Privacy

Updated 25 October 2026 ยท What {{ app_name }} stores, why, and how to delete it.

{{ app_name }} is operated by Sanchit Pandey under the Orrico Labs name. For privacy questions or requests, contact {{ contact_email }}.

What the SDK sends

What the SDK does not automatically send

The SDK does not automatically send your prompts, the model's replies, source code, file contents, or model provider API keys. Your agent calls the model provider directly. Do not put secrets or private content in task names, progress notes, test IDs, or other fields you supply: those fields are sent as written.

What we store about you

We store your email address and a scrypt hash of your password to provide and protect your account. The secret values of API keys, login session tokens, and password-reset tokens are stored as hashes, so those values cannot be read back from the database. We also keep key names, prefixes and usage times, session and reset expiry times, and account creation time. A session cookie keeps you signed in; a short-lived form-security cookie helps protect login and signup forms.

We also store your workspace name, supervision rules, model prices you configure, and any alert email address or Slack webhook you save. We use these settings to supervise runs, show estimated spend, and deliver the alerts you request. Anyone with access to your workspace settings can update its alert destinations, so treat a Slack webhook as a secret.

How long it's kept

To improve setup and detection during beta, we measure account and API-key creation, first event receipt, flags, and weekly workspace activity using server records. We store event receipt times, an internal/testing or outside-user workspace classification, and any flag verdicts or missed-loop reports you submit. Feedback records include the submitting account ID and can be updated by workspace members. The operator sees workspace activation and aggregate usage and feedback counts. These records are linked to your workspace; they are not anonymous. No external analytics service or additional tracking cookie is used.

Run data, associated activity receipt times and feedback, and unexpected server-error records are removed from the active database after {{ retention_days }} days. Error records contain an exception type, route pattern, stack locations, and occurrence times and counts; they exclude exception messages and request contents. Account details and workspace classification stay in the active database until you delete your account.

Encrypted database backups are retained in GitHub Actions for up to 30 days. Neon recovery snapshots and isolated restored branches can retain older copies until they are deleted. Data removed from the active database can therefore remain in these recovery copies.

Deleting your data

Settings, then Delete account, removes your workspace, runs, events, API keys, settings, and login from the active database. Historical recovery copies are not changed immediately. Contact us to request help with data in retained backups or restored branches.

Who processes it

The website runs on Vercel and its active database is hosted by Neon. These providers may process request information, such as IP address and browser details, to deliver and protect the site. The site loads its Inter font from Google Fonts, which also receives a request from your browser. Encrypted database backups are stored in GitHub Actions.

Run alerts go to the Slack webhook and email address you set; email delivery uses Resend. New server-error alerts go to the site operator's configured Slack webhook and email address. Copies delivered to those destinations are governed by the recipients' and providers' retention settings; deleting your Agent Supra account does not remove those copies.

Questions and requests

For privacy questions, access or deletion help, or concerns about an alert destination, contact {{ contact_email }}.

{% endblock %}