Privacy

What AgentTracer stores.

Last updated November 18, 2026.

Who operates AgentTracer

AgentTracer is hosted software for recording what an AI agent did. It is operated by Aurora Lab LLC.

Questions about this page or an account go to hello@agenttracer.net.

Account and sign-in

You create an account with an email address and a password. A name is optional. If you leave it blank, the account stores a short label from the part of the email before the @, or the word there. The password is stored as a scrypt hash. Creating an account with email does not send an email verification message.

You can also sign in with GitHub. We receive your name, email, and avatar from GitHub.

A session cookie keeps you signed in. The cookie is marked secure when the site is served over HTTPS. A session row can store the IP address and user agent for that sign-in. The app reads the address from the x-real-ip or x-forwarded-for header.

Rejected sign-up and sign-in attempts are counted by client address so the form can be rate-limited. Those counters are not campaign records. Windows older than about a day are deleted on a best-effort schedule.

A password reset email contains a single-use link that expires after one hour. The reset page answers the same way whether or not the email matches an account. Saving a new password replaces the hash and deletes that account's sessions.

Projects, API keys, and events

Signing up creates a project named Default. You can create more projects from the dashboard. Each project has a name, a slug, and an optional description.

An API key is shown in full once, when you generate it. The database stores a SHA-256 hash of the key and a short prefix, the first 16 characters, so you can tell keys apart. A revoked key stops working on the next request.

The ingest API stores what your agent sends: event type, name, timestamp, and JSON payload, plus any agent or run identifiers in that request. The payload is the data your agent included. It is kept with the project that owns the key. Prompts and outputs are not stored as their own fields, and the payload is not redacted.

In the app, only the signed-in project owner can see a project's events.

Aurora Lab staff can access stored data only when needed to operate the service, investigate abuse, or respond to support requests.

Campaign labels

If the sign-up address includes utm_source, utm_medium, utm_campaign, utm_content, or utm_term, we store the values that are 1 to 64 characters and use only letters, numbers, dots, underscores, and hyphens. We keep the first accepted set for that account. Later sign-in does not replace it.

A first-party cookie named at_campaign keeps those labels for 30 days (SameSite=Lax, and Secure on HTTPS) so sign-up can use them when the form address has none.

We also keep aggregate counts: a UTC day, a step name, utm_source, utm_medium, utm_campaign, and a count. Those rows have no IP address, user agent, or account id.

We do not store the full referrer, an ad click id, your email, your IP address, an API key, or an event payload in that record. We do not load an X advertising pixel, send a hashed email to X, or use another third-party analytics tag.

Email we send

The app can send a password reset, a one-time note about a day after sign-up if no project has received an event, a Monday weekly digest, an anomaly alert, and usage notices at 80% and 100% of the included monthly events. The one-time note is not sent again. Digest and anomaly mail can be turned off on the email settings page. The one-time note and usage notices stay on.

A week with no events and no open anomalies does not get a digest. When email delivery is configured, messages go out through Resend. If that API key is not set, the send is skipped. Reset mail uses AgentTracer <auth@agenttracer.net>. Digest and alert mail use the From addresses configured for those messages, or digest@agenttracer.net and alerts@agenttracer.net. The one-time note uses the digest From address. Replies to that note go to hello@agenttracer.net.

Billing

Free includes 50,000 events in a UTC month and then stops, after 1,000 extra events so one batch that crosses the cap can still land. Pro includes 500,000 and Team includes 5,000,000. Above the included amount, Pro and Team keep accepting events and report overage to Stripe at $5 per 100,000 events.

Checkout and the customer portal are on Stripe's pages. We store a Stripe customer id, subscription id, price id, plan, and status. We do not store a card number. The monthly usage counter in our database is not reduced when old events are deleted.

How long events stay

A daily job deletes events whose timestamp is older than the plan window: 14 days on Free, 30 days on Pro, and 90 days on Team. The timestamp is the one your agent sent. Runs that no longer have events and that started before the same cutoff are deleted too. An account without a billing row uses the Free window.

Deleting a project or an account

You can delete a project from the dashboard. The dialog asks you to type the project name. That removes the project, its events, and its API keys. It cannot be undone. The month's usage count does not go down.

There is no button to delete the whole account. Email hello@agenttracer.net from the account email and ask for the account to be deleted. Include that email address. We delete the account and its projects when we process the request. We don't promise a time.

Where the code sends data

The app is set up to build and run on Vercel. The scheduled digest, anomaly check, retention job, first-event note, and demo-project tick are the cron entries in the repository.

Account, project, and event data is stored in Postgres. The repository's setup uses Neon for that database.

Paid checkout, the customer portal, and metered overage use Stripe. Email delivery, when configured, uses Resend.

Those are the providers this code calls. This page does not list a region, a retention period inside a provider's own systems, or a contract term.

What this page is

This page describes what this version of the application does. It is not a security certification, and it does not add access-request steps or deletion deadlines beyond the project and account deletion described above.

hello@agenttracer.net