Security

Every connection to Phil, and every connection Phil makes out to a service you connect, travels over TLS encrypted HTTPS. Nothing moves between your browser and Phil, or between Phil and a connector, in plain text.

Access tokens and credentials for anything you connect, a Google account, a Slack workspace, an API key you paste in, are encrypted before they are ever written to the database using authenticated encryption. Even someone holding a full copy of the database cannot read a connected account's credentials without the separate encryption key, which is held apart from the database itself.

Every table in Phil's database enforces row level security at the database layer, not just in application code. A query for your workspace's files, chat history, or connections is scoped to your account by the database itself, so one workspace cannot read another's data even if a bug in Phil's own code tried to let it.

Phil's internal admin console, used to look at platform wide statistics and support customers, is gated to a single named account. It is not reachable by any customer, including other signed in users, and it fails closed: if that account is not configured, nobody gets in rather than everybody. Every successful pass through that gate is recorded, described below.

The endpoints that call Anthropic's Claude API, chat and daily report generation, are bounded by a per workspace hourly limit, counted atomically in the database rather than in memory, so the limit holds even across multiple servers. This exists to stop a runaway script or a compromised account from running up unbounded cost, not to police ordinary use, and the default limits are generous enough that a real conversation never comes close.

Phil keeps an audit log of security relevant events: successful and failed logins, account signups, logouts, account deletion, and every admin console access. Each entry records when it happened, who it was, and what happened, and it is stored separately from your workspace data so it survives even a workspace being deleted.

You choose how long Phil keeps your data, between 7 and 90 days, and it is deleted automatically once that window passes, no exceptions and no separate backup copy kept past that point. You can delete any individual file, or your entire account, at any time from Settings, with no need to ask us first. The full detail lives in the Privacy Policy.

Running Phil means a small number of other companies handle your data on our behalf, only to the extent needed to provide the service. Anthropic processes the contents of your files and questions so Phil can read and answer them, and does not use that data to train its models. Supabase provides the database, file storage, and login system. Vercel hosts the platform and handles incoming requests. None of them use your data for their own separate purposes.

If you believe you have found a security issue in Phil, we want to hear about it. Email adam@adafit.info with what you found and how to reproduce it, and we will respond as quickly as we can. Phil does not currently run a paid bug bounty program, and this page will not imply one exists. A machine readable contact for this is also published at /.well-known/security.txt, following the standard convention for security contact information.

The practices above are real and in place today, checked against what Phil's code actually does rather than written aspirationally. They are built around the same principles ISO 27001 is organized around: knowing what data you hold, controlling who can reach it, encrypting what needs encrypting, watching for and recording what happens, and bounding how long anything sticks around. Phil does not hold, and does not claim to hold, a formal ISO 27001 certification or any other third party security audit.