Security and trust

How Pharos protects your data.

Pharos uses read-only reporting access to retrieve billing and usage data. Review every endpoint it calls, how it isolates workspaces, where data is processed, and which assurances are in place today.

Controls

Read-only reporting scope

Every connector signs in with a reporting or billing key and calls usage and cost endpoints only. Pharos never writes, never runs a model, and never touches your account settings. Revoke the key at the provider and Pharos loses access at once, without asking us.

Prompts and completions are never read

The endpoints below return totals: tokens, requests, line items, and amounts, grouped by model, project, key, or member. None of them return message content, and Pharos calls no endpoint that does.

Your workspace is separated in the database

PostgreSQL row-level security keeps each workspace apart. Every table carries a policy that ties a row to one workspace, so the database enforces it rather than the app. A test suite runs those policies against a live database.

Credentials encrypted before storage

Provider keys and webhook secrets are encrypted with AES-256-GCM before they reach the database, each with its own key. You can also keep them in a dedicated secrets store instead of the application database.

No language model computes a figure you are shown

Code computes every number you see, from stored provider records, in whole micro-dollars. The agent explains the evidence and drafts what to do next. When Pharos sends an agent request to a model provider, it asks for zero data retention.

Sign-in controls

You verify your email before a workspace is created. Sign-in, sign-up, and recovery are rate limited per account and per address, in fifteen-minute windows. Sessions live in signed, HTTP-only cookies.

Every endpoint Pharos calls

12 sources connect directly. For a provider with no billing API, you upload an invoice or a usage export, and Pharos holds no key for it at all.

OpenAI: /v1/organization/usage/*/v1/organization/costs
Anthropic: /v1/organizations/usage_report/messages/v1/organizations/cost_report
Cursor: /teams/daily-usage-data/teams/spend/teams/filtered-usage-events
OpenRouter: /api/v1/credits/api/v1/activity/api/v1/keys
Amazon Bedrock: Cost ExplorerCloudWatch metrics
Snowflake: /api/v2/statements
Databricks: /api/2.0/sql/statements
Fireworks AI: /v1/accounts/{id}/billingUsage
Fal.ai: /v1/models/usage
GitHub Copilot: /organizations/{org}/settings/billing/usage

Subprocessors

Neon: Managed PostgreSQL. Stores spend records, workspace records, and encrypted credentials.
Neon Auth: Identity provider for sign-in, email verification, and password recovery.
Redis: Rate-limit counters and short-lived cache. No spend records.
OpenRouter: Routes agent requests to model providers. Pharos asks for zero data retention.
Resend: Email: verification codes, recovery codes, and the alerts you turn on.

Independent assurance

Pharos does not hold a SOC 2 report today. The controls above are built and testable now. An independent audit is a different claim, and it will appear here with its date when we have one.

For a security review, a questionnaire, or a signed data processing agreement, see the data processing terms or write to security@pharoslabs.ai.