Data handling

A plain-language summary of how Parsaa handles your data. For the full detail, see the Privacy Policy.

Where your data goes

• Parsaa-hosted models: your prompt and the code you share go over TLS to our servers, which forward the request to a third-party AI model provider. The response streams back to the app.
• Bring Your Own Key (BYOK): requests using your own provider key go straight from the app to that provider and never pass through Parsaa servers.
• On-device models: when enabled, inference runs entirely on your Mac. Nothing is sent to us or a provider.

What stays on your Mac

These live locally in Parsaa’s application-support folder on your Mac, and we cannot read them:

• Your chat history.
• Codebase indexes and embeddings (vectors). To create embeddings, code chunks are sent to our servers and a third-party provider; the resulting vectors are stored on your Mac, not on our servers.
• App settings, and your BYOK keys and session tokens (in the macOS Keychain).

Uninstalling the app does not delete this folder. Use Settings to clear local data, or delete the folder manually.

What we keep, and for how long

Retention of your AI content depends on your Privacy Mode in the app:

• Training Mode (default): we may keep your chat requests and autocomplete to run and improve Parsaa. Full-codebase indexing is off by default. Each of these can be turned off.
• Private Mode: your content is used only to generate the response and is not kept afterward.
• BYOK: not kept by us, since it never reaches our servers.

Operational logs are short-lived (around 30 days, with prompt and error text sampled and truncated). Account and billing data are kept while your account exists and as tax law requires. See the Privacy Policy for the full retention table.

Who processes your data

We rely on a small set of third-party providers to run the service: AI model providers (for chat, voice transcription, autocomplete, embeddings, applying code edits, and search ranking), cloud infrastructure and hosting, payment processing, email delivery, and product analytics. We share only what each provider needs for its function. A current list of subprocessors, with their roles and jurisdictions, is available on request — see the Privacy Policy.

Where a provider supports it, we use no-training and reduced-retention settings.

Analytics and telemetry

• Our analytics provider records which features you use and your plan, never your code or prompts. You can turn it off in Settings.
• Session replay: on the website, we may record a replay of your interface interactions (with text inputs masked) to help us fix issues. It is gated by the analytics cookie consent.
• We do not run crash-reporting that captures your code.

Deleting your data

• Local data: Settings, then clear local data, or delete the app support folder above.
• Account data: delete your account in the app or at parsaa.app. This removes your account and associated records.
• Questions or requests: hello@parsaa.app.

Where it is hosted

Our API, database, and website run on third-party cloud infrastructure, primarily in the United States. Most AI providers are in the United States or the European Union.