# Privacy — Synara

Private by default. Clear by design. Last updated November 9, 2026.

Synara stores workspace history on the host computer. Optional accounts, managed connections and mobile access use additional services. Stable and Beta product analytics are off by default. Synara Remote from version 1.0.6-remote.18 and native iPhone/iPad apps from build 139 share limited usage data by default, with a local switch to turn it off. Synara Beta has separate, always-on crash and release diagnostics.

## Where your data lives

Workspace chats, projects and operational state live in a local SQLite database on the host computer. Approved devices can access that host. Optional Synara account features store profile information, private usage aggregates and saved Inbox recaps in PostgreSQL/Supabase, accessed through our Cloudflare account API. These records are separate from product analytics.

Synara for iOS may cache conversations, images and other files from your computer. Drafts and queued messages may also be stored on the device.

## Where your prompts and code go

The host computer connects directly to the selected coding provider using your existing logins. That provider receives the prompts, attachments and context needed for the work you request under its own privacy terms. For managed remote connections, Cloudflare transports chat and file traffic between your approved device and the host before the host contacts the provider.

Dictation can process recordings on your iPhone. When transcription uses your connected computer, the recording is sent to OpenAI through the computer’s signed-in Codex/ChatGPT session, even if your chat uses another provider. OpenAI’s privacy terms apply to that processing.

## Optional accounts and connections

Local desktop use does not require a Synara account. Authentication uses WorkOS; the account API and managed tunnels use Cloudflare. Approved devices can access the selected host, including its chats and files. Access is revocable. Information you publish on your profile is public; saved Inbox recaps are private.

Where paid subscriptions are offered, Polar handles checkout, payments and tax information. Synara associates your account identifier and email with your billing customer and stores subscription status and billing periods to manage access. Card details go to Polar and its payment processor.

## iOS notifications

Completion previews are enabled by default and may show the chat title, provider and first line of the final answer. Turn previews off in Settings → Notifications in Synara. iOS controls notification permission and Lock Screen visibility.

## Product analytics and Remote diagnostics

Stable and Beta product analytics are off by default. Synara Remote from version 1.0.6-remote.18 and native iPhone/iPad apps from build 139 share limited usage data by default. Settings → Privacy → Share usage and diagnostics turns sharing off on that installation; an existing off choice is preserved. On Remote desktop the switch also controls crash and error diagnostics. Another computer or account does not change your local choice.

Events can include fixed feature, outcome and failure categories, connection mode, a random installation identifier, event identifier and timestamp, version, release channel, surface, platform and bounded durations. Token counts and aggregates by provider, catalogued model, effort, mode, origin and outcome are reported separately by the host.

Starting with build 168, Synara for iOS sends no Synara account identifier or account-derived hash in product analytics. It uses a random installation identifier and does not join installations across devices to count people. Upgrading from older account-linked analytics resets the identifier and discards unsent analytics while preserving your sharing choice and local app data.

Older releases that used account-linked analytics could include a one-way hash of the signed-in Synara account identifier. That hash was pseudonymous and could be matched against an account list. We do not use product analytics for advertising or cross-app tracking, or share it with data brokers.

When the receiver supports it, some iOS events also include a UTC cohort entry day and a fixed entry, first-week or first-month return marker. Aggregate cohort counts have a 90-day cleanup target. These counts describe reporting installations.

Analytics never receive prompts, messages, chat history, code, files, diffs, repository contents, API keys, tokens, provider credentials, names, emails or an IP-based location profile.

Hosted raw product events in Cloudflare D1 have a 30-day retention target from receipt, with daily bounded cleanup. Data can remain longer while a cleanup backlog clears. Self-hosted receivers control their own retention. Local queues are bounded to 500 events and seven days. Turning sharing off clears unsent events, cancels active sends and removes the local analytics identifier. Data already received follows the retention described above.

Remote desktop diagnostics keep known error categories, numeric source locations, process/release health and aggregate usage counters. They exclude error messages, function/file names, log excerpts and raw crash memory dumps. Diagnostic reports have separate, indefinite retention; the 30-day product-event cleanup does not remove them.

## Separate Beta diagnostics

Synara Beta sends crash, error, release-health and daily usage diagnostics automatically. These may include bounded, redacted error stacks, log excerpts and recent diagnostic context. Stable does not send Beta diagnostics. Product analytics consent does not control this separate path. Its retention policy is independent of the product-event policy. See the [diagnostics documentation](https://github.com/Emanuele-web04/synara/blob/main/docs/diagnostics.md) for its field allowlist and storage details.

## Feedback you choose to send

The Feedback Synara dialog sends only when you press Submit. It includes your text, app version, operating system, provider and model, runtime modes, and session/turn status. Feedback context excludes chat messages, prompts, project paths, repository contents, session logs and screenshots. The website and email provider deliver reports to the maintainer for support and product improvement, not an analytics profile.

## Commercial sponsorships on this website

The optional sponsorship service collects your company name, contact email, logo, destination and promotional brief to review and deliver your paid placement. This service is separate from using the desktop app.

Stripe collects billing address, country, tax details when supplied, payment terms consent, and processes your recurring payments; we do not receive your full card details. Supabase stores sponsorship records and private submitted images. When configured and enabled, Resend delivers operational emails. An optional private Discord channel receives review and operational notifications containing the company, destination, contact email, request message and the request identifier. Approved logos, company names, descriptions and destinations appear publicly on Synara and, for Platinum sponsors, on the personal sponsors page.

We process these records to handle your request and contract, prevent abuse and maintain payment records. Private records are accessible only to authorized operators. A private materials link lets its holder view and submit materials for one campaign, without billing data; it expires after seven days, extended through the 23-hour payment window if initial materials are submitted near expiry, and can be revoked. Keep it confidential. We retain transaction records for applicable accounting and dispute requirements; contact us to request access, correction or deletion of other sponsorship data. Providers may process data internationally under their published data protection terms. No sponsorship data is sold.

Contact the seller listed in the [sponsorship terms](/sponsor/terms) for privacy requests.

## Open source

Synara Desktop uses the MIT license. [Read the desktop source](https://github.com/Emanuele-web04/synara).

## About this website

The marketing site uses [Vercel Web Analytics](https://vercel.com/docs/analytics/privacy-policy) for anonymous aggregate visit counts: no cookies, cross-site tracking, or selling of data.

For support or privacy requests, including account deletion, [email Synara support](mailto:emandipietro@gmail.com). Account deletion does not erase workspace files or chat history on your computer.


Canonical URL: https://www.trysynara.com/privacy

[Agent content index](https://www.trysynara.com/llms.txt)
