Security — Antelog

Security

For security reviewers. This page lists how the guard works, what leaves a computer, and where it goes.

How the guard protects

The hosted AI check is different. If it can’t be reached, the action is not blocked for that reason. The rules decide alone, so an action no rule stops is allowed.

What leaves your computer, and when

What What is sent Why Kept?
Hosted AI check (on by default) Every action that no rule stops outright (a command, a file read, write, edit or search, or another tool call), plus the text of any script it runs, up to 20,000 characters in all, with secrets removed, and a random install id. Goes to app.antelog.dev, which asks an AI model (Jev) through the Vercel AI Gateway. A second look at actions no rule knows. Not by Antelog. Antelog keeps only daily and monthly counts, under a one-way hash of the install id and of the network address. The AI providers handle it under their own terms.
Hosted judge (on by default) Only when something is stopped: the stopped action and any script it runs (up to 12,000 characters), the agent’s session id and the folder it is working in, the name of the rule that stopped it, and your latest request in that session (up to 2,000 characters), with secrets removed. Goes to app.antelog.dev, which asks Anthropic’s Claude Haiku. Not used if you add your own Anthropic key. To catch false alarms. Not by Antelog. Only the same counts. Anthropic handles it under its own terms.
Your own AI keys (optional) An Anthropic key: the same as the hosted judge. A Vercel AI Gateway or Cloudflare key: the same as the hosted AI check. Sent straight from your computer under your own account. You chose your own key. Never reaches Antelog.
Team dashboard (only if you connect a machine) The action history: time, session, tool, a summary of the action (its first line, cut short), the decision and the reason, with secrets removed. The log’s tamper check result. A one-way hash of the install id. So your team sees every machine in one place. Yes, in the dashboard’s database. The dashboard shows 14 days on Free; on Team, as long as agreed.
Sign-in Your email and name. If you sign in with GitHub: that account’s id, profile picture link and sign-in token. Your sign-in sessions, with the network address and browser. Codes are sent by email through Amazon SES. To sign you in to the dashboard. Yes.
Payments Card details go to Stripe and never reach Antelog. Stripe Tax adds US sales tax. To pay for a paid plan. Antelog keeps your plan status. Stripe keeps the payment details.
Emails Sign-in codes and invitations, sent through Amazon SES. To reach you. Your email address (see Sign-in). Invitations, with the invited address and role, are kept in the dashboard’s database.
Contact form Your name, work email, company, team size and message. Emailed to us through Amazon SES. To reply to you. Yes, in the dashboard’s database.
Website analytics (antelog.dev only) Page visits and which pages and buttons people use, through Vercel Web Analytics and Google Analytics. Google Analytics sets cookies. The Antelog software sends no analytics. To see what people use. By Vercel and Google.

Data that leaves your computer

All traffic uses HTTPS.

How to turn each off

Where data is stored

Outside services we use

What we never get

Report a security issue

Email support@antelog.dev.

Need a security questionnaire or a data processing agreement (DPA)? Book a call.