Security

Security at Filo.

Filo runs on Google Cloud in the US. Your records stay in your systems, connection tokens are encrypted, and model providers don’t train on your data.

Read the security policy →Email security@filoagent.com

Where it runs

Filo runs on Google Cloud in the US.

Google Kubernetes Engine in the us-central1 region.
Production and staging are separate, with separate databases, credentials and domains.
Files and logos sit in private Cloud Storage buckets.
TLS in transit; Google Cloud encrypts data at rest.
Secrets live in the cluster’s secret store, never in code or images.
Deploys go from a reviewed branch through a build pipeline. Nothing is built on a laptop.

Access and sign-in

Everyone signs in, and every account has an owner.

Passwords are hashed. Password sign-ups are verified by an emailed code.
Google and Microsoft sign-in are verified by the provider.
Workspaces have owners, admins and members.
A disabled or removed person is turned away on their next request.
The people who run Filo are listed in code. They never read your chats or files without your consent.

Your data

Your data belongs to your account, and only yours.

Every record, file and chat belongs to one account.
A file you upload can be read only by you, in that workspace, unless you share it.
Every change Filo makes keeps the old value, who asked and from which chat.
When you close a workspace we export your data on request, then delete it.

Connections

Connection tokens are encrypted, and you can revoke them.

Tokens for Google, Slack and Fiddle are encrypted with a key kept outside the database.
Each person connects with their own account, and can disconnect at any time.
Filo writes to your systems only as the person who connected them.
Apps run in a sandboxed frame on a separate origin, and never see credentials.

Model providers

Model providers don’t train on your data.

Filo uses models from Anthropic, OpenAI, Google, DeepSeek and OpenRouter.
Your content goes to the provider under its API terms, which don’t allow training on it.
We log each call’s size and cost, not its content.

Email to suppliers goes out from your mailbox, after you approve it.

Filo never emails a supplier on its own.
Account emails and sign-in codes come from filoagent.com through Resend.
Filo never places an order and never pays anyone.

What we don’t have yet.

Filo is new, and some things a larger vendor would show you aren’t done. If one of them is a requirement for you, tell us. It helps us decide what to do first.

SOC 2 report: We don’t have one yet. We plan it and will post the date here once it’s set.
Penetration test: We haven’t had an independent test yet. It’s planned alongside SOC 2.
SAML single sign-on: Not offered yet. Google and Microsoft sign-in work today.
Customer-managed keys: Not offered yet. Google Cloud encrypts data at rest with its own keys.

Found a security problem? Tell us.

Write to security@filoagent.com. We read every report and reply within two business days. Please don’t test against other customers’ data.

The full policy is on the security policy page, and the companies that process data for us are on the sub-processors page.