Private by default. Clear by design.

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

The host computer connects directly to the provider you chose — Claude, Codex, OpenCode, Cursor, Antigravity, Grok, Droid, and so on — using your own existing logins. That provider receives the prompts and code needed for the session, governed by their privacy terms. Synara does not proxy normal provider requests through its own model service. When you use a managed remote connection, Cloudflare transports chat and file traffic between your approved device and the host computer before the host contacts the provider.

Local desktop use does not require a Synara account. Signing in enables account features and managed device connections. Authentication uses WorkOS; the account API and managed tunnels use Cloudflare. Approved devices can access the selected host, including its chats and files, through that connection. You can revoke device access. Information you choose to publish on your profile is public; saved Inbox recaps are private.

Stable and Beta product analytics are off by default. Synara Remote from version 1.0.6-remote.18 and the 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 this switch also controls crash and error diagnostics. Another computer or account does not change your local choice.

While signed in, events include a one-way hash of your Synara account identifier so that your devices can count as one person. The identifier itself, name and email are not sent. This hash is pseudonymous, not anonymous: an operator holding the account list could recompute it. We do not use advertising, cross-app tracking or data brokers.

Raw product events are stored in Cloudflare D1 for up to 30 days behind an authenticated dashboard. 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; it cannot recall data already received. Usage counters are best-effort observations, not billing records or complete account totals. Custom model and command names are reduced to fixed categories rather than sent as free text.

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.

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 Beta path, whose retention policy is independent of the 30-day product-event policy. See the diagnostics documentation for its field allowlist and storage details.

The in-app Feedback Synara dialog sends only when you press Submit. It includes the text you wrote, app version, operating system, provider and model, runtime modes, and session/turn status so we can understand the conditions around a problem.

Feedback context excludes chat messages, prompts, project paths, repository contents, session logs and screenshots. Feedback reports are delivered through our website and email provider to the Synara maintainer for support and product improvement, rather than being added to an analytics profile.

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 for privacy requests.

Synara is open source under the MIT license. If a sentence on this page isn't enough, you can verify every claim yourself — read the code on GitHub.

This marketing site (the page you're reading) uses privacy- friendly Vercel Web Analytics for anonymous, aggregate visit counts. No cookies, no cross-site tracking, no selling of data.