Cirrana

Security & Privacy

Plain language. No legal boilerplate. Here's exactly what Cirrana does and doesn't do with your Salesforce org.

What Cirrana reads

Metadata only, by default. When you connect your org, Cirrana reads object definitions, field names and types, validation rules, flows, automation configurations, page layouts, and permission summaries — the structural description of your org, not your records.

Record data only when you explicitly ask a data question. If you ask "how many open Opportunities are in my pipeline?" Cirrana runs a read-only SOQL query against your org to answer it. It reads the result, uses it to answer your question, and does not store it.

What Cirrana never does

  • Write to your org, create records, modify configuration, or deploy changes.
  • Store your Salesforce record data on our servers. Query results are used in-context and discarded.
  • Train AI models on your data. Your org's information never becomes part of any model's training set.
  • Share your data with third parties for advertising or analytics.
  • Retain your data after your account is deleted.

How AI inference works

Cirrana sends prompts to third-party AI providers (currently OpenAI-compatible inference APIs) under zero-data-retention terms. This means the provider does not log, store, or use your prompts for training.

Prompts contain the metadata context relevant to your question (object names, field definitions, etc.) but never your full org data dump. We include only what is needed to answer your specific question.

OAuth connection

Cirrana connects via Salesforce OAuth 2.0. You authenticate directly with Salesforce — Cirrana never sees your Salesforce password.

You can revoke Cirrana's access at any time from your Salesforce org: Setup → Connected Apps OAuth Usage → Revoke. You can also disconnect from within Cirrana's Connectors page.

We request only the scopes needed: read access to metadata and data, plus the refresh token scope so your session stays live. We do not request write or deploy scopes.

Credential storage

OAuth tokens are stored encrypted at rest in our database (Supabase, hosted on AWS). Access is row-level secured: only your user account can read your tokens. They are never returned to the browser — only used server-side to make API calls on your behalf.

Questions about security or a specific data-handling concern? security@cirrana.ai