This Privacy Policy explains how Qadri LLC (“we”, “us”), operator of the Tatastu desktop application (“Tatastu” or the “App”), handles information. Tatastu is a local-first desktop app: by design, the large majority of your data stays on your own device. This Policy covers the App, Tatastu account and optional hosted-service data, historical subscription records, and the tatastu.dev website, except where the Website relies on a separate provider as noted below.

Summary (the short version)

Tatastu stores local workspace data and local credentials on your device unless you explicitly start an optional hosted run.
Tatastu contains no advertising, tracking, or behavioral profiling. We do not build a profile of you.
AI features use your own AI provider account or local model. Local runs connect from your device; optional hosted runs use Tatastu-operated infrastructure and the scoped credentials and workload material needed to perform the run.
We process limited account, authorized-device, optional hosted-run, support, and historical subscription data as described below. Payment details are handled by our merchant of record, not us.

1. Data stored locally on your device

The following is created and stored on your device and is not transmitted to us unless you explicitly include it in an optional hosted run or support request:

Your projects, chats, messages, and generated/edited files
App settings and preferences
API keys and credentials you enter for AI providers and other services you connect (stored encrypted using your operating system’s secure storage)
Your AI provider authentication tokens (for example for Claude, ChatGPT, OpenRouter or OpenCode Go)
Local speech models and dictation audio (dictation is transcribed on your device and its audio is not sent to us)

You can delete this data at any time by removing it within the App or deleting the App’s data directory.

2. Data sent to third parties you configure

For local runs, the App communicates directly from your device to services you choose to connect, using your credentials. We do not intermediate, store, or receive that local-run traffic. Examples:

Your AI provider (for example Anthropic, OpenAI, OpenRouter or OpenCode Go): receives the prompts, code, and context you submit. Governed by that provider’s privacy policy. If you choose a local model, those requests stay on your device.
Developer services you connect (e.g., GitHub, and optional integrations): receive only what you direct, using your credentials.

We are not responsible for the privacy practices of third-party services. Review their policies.

3. Data we (and our payments provider) process

For the limited personal data we process on our own servers, Qadri LLC is the data controller. We process the following data to provide and secure account and optional hosted services, service historical purchases, and support users:

Tatastu account and authorized devices. We process account sign-in information (including account email and session data), an account or relay identifier, authorized-device identifiers and credentials, and records used to bind or revoke a device. We use them to authenticate and protect account and optional hosted-service access, associate work with the correct account, enforce service capacity, support recovery, and investigate misuse. A device identifier is not a hardware fingerprint and is not used to track you across apps or the web.
Purchases and historical subscriptions. Past purchases were processed by Polar, acting as merchant of record. Polar collects the information needed for payment, tax, refunds, and purchase support (such as name, email, billing and payment details). We do not receive or store your full payment details. We retain historical Tatastu subscription, license-key, activation, and purchase records only as needed for refunds, support, disputes, and legal obligations; they do not determine Software feature access. Polar acts as an independent controller for its payment processing; see Polar’s privacy policy.
Phone companion. If you pair a phone, we process the pairing records, phone and desktop device credentials, and a push-notification subscription for that phone. Traffic between your desktop and your phone passes through our relay as encrypted frames that the relay cannot read, and notification contents are encrypted on your desktop before they reach us. The relay still sees connection metadata such as account and device identifiers, timing, and message size.
Download reminders on the website. If you enter your email address on tatastu.dev from a phone, we store that address with the time you submitted it and use it to send you the download link. Contact us to have it deleted.
Support. If you email support, we receive the information you choose to send.
Optional hosted execution. When you start a hosted run, we process the code, files, prompts, context, outputs, checkpoints, operational metadata, capacity and run-ownership records, and encrypted scoped provider or repository credentials needed to perform it. We use this data to provide, secure, troubleshoot, and account for the requested service. We schedule deletion of terminal hosted checkpoint objects and transcript details 30 days after a run ends. Limited run status, ownership, and capacity records remain subject to the retention terms in Section 7. You can revoke connected credentials at their source.

Categories of recipients. Besides Polar (above), we use a content-delivery network and hosting providers to operate api.tatastu.dev and cdn.tatastu.dev (currently Cloudflare), an email delivery provider to send sign-in links, download reminders, and support notifications (currently Resend), and, if and when enabled (see Section 5), an error-reporting provider. These act as our processors under appropriate data-processing terms.

4. What we do not do

No tracking pixels, advertising, or behavioral profiling in the App or on the website.
No selling or sharing of personal information for cross-context behavioral advertising (relevant to CCPA/CPRA). You also have the right to non-discrimination for exercising your privacy rights.
No access to code, chats, or local files that remain in the local workspace. Optional hosted-run material is processed as described in Section 3 under controlled operational access.

5. Website analytics, updates & crash data

Website analytics. The tatastu.dev website uses Plausible Analytics, a privacy-first analytics tool. Plausible does not use cookies, does not collect or store personal data, and does not fingerprint visitors. It measures aggregate page views, referrers, and interaction events (such as download button clicks) without identifying individual users. No data is shared with advertising networks. For details, see Plausible’s data policy.

Optional product analytics. Product analytics in the App is off by default and has a separate, revocable switch in Settings. If you enable it, the App sends a pseudonymous installation hash and a closed set of content-free events such as provider connection, first successful task, and hosted-run outcomes. These events cannot include prompts, responses, source code, file paths, secrets, or tool payloads. Disabling product analytics does not change Software feature access or your eligibility for optional hosted services. Purchase, support, security, and hosted-service integrity records needed to provide a service you request are separate operational records.

Update checks. The App periodically requests an update manifest from our content-delivery network (currently Cloudflare). Like any internet request, this transmits your IP address and the App version. Your IP address is personal data under some laws; we use it only to deliver the update file and do not use it to build a profile of you. Edge/network logs may be retained by our CDN provider under their own policies.

Crash reporting. This version of the App does not send crash reports or telemetry to us by default. The App includes an optional crash-reporting component (Sentry) that is disabled unless a build explicitly enables it; even then it can be turned off in Settings. If enabled, it would send only crash diagnostics (error type, stack trace, App version, OS) with secrets and file-path information automatically redacted before transmission; it would not transmit your code, prompts, or files. We will update this Policy and provide notice before activating any such collection, and where required by law we will obtain your consent.

6. Legal bases & your rights

Legal bases (GDPR / UK GDPR). Where GDPR applies, we rely on: (i) performance of a contract (Art. 6(1)(b)) to provide the account and optional hosted services you request, handle refunds and support for Historical Subscriptions, and provide support; (ii) legitimate interests (Art. 6(1)(f)) to deliver software updates and keep the Service secure and functional, balanced against your rights; and (iii) consent (Art. 6(1)(a)) for optional diagnostics or analytics where consent is required, which you may withdraw at any time. The account and device information described in Section 3 is needed when you choose to use account-based or optional hosted services. Purchase information is needed to resolve a request about a Historical Subscription.

Your rights. Depending on where you live, you may have rights to access, correct, delete, or port your personal data, or to object to or restrict processing (GDPR), and rights to know/delete/opt-out (CCPA/CPRA). Because most data is local to your device, you control it directly. For data we hold (account, authorized-device, hosted-service, and Historical Subscription records), contact us at support@tatastu.dev to exercise your rights; you may use an authorized agent where permitted. You also have the right to lodge a complaint with your local data protection supervisory authority.

7. Data retention

Local data persists on your device until you delete it. We schedule deletion of terminal hosted checkpoint objects and transcript details 30 days after a run ends. Account and authorized-device records, and limited hosted-run status, ownership, and capacity records, are retained while needed to provide and secure the account and optional hosted service, and then for a limited period needed for recovery, support, security, or legal obligations. Historical Tatastu subscription, license, activation, and purchase records are retained for 24 months after the Historical Subscription ended to handle refunds, support, and disputes, unless a longer period is legally required. Records of other past purchases made through Tatastu are retained for the period needed to resolve support or refund requests and meet legal obligations. Download-reminder email addresses are kept until you ask us to delete them or we no longer need them to send the link. Records required for tax and accounting are retained for 7 years (or the period applicable law requires). Payment records held by Polar are retained under Polar’s own policy.

8. Children

Tatastu is not directed to children under 13 (or the applicable higher age in your jurisdiction) and we do not knowingly collect their data.

9. International transfers

Our account, authorized-device, optional hosted-service, and Historical Subscription processing, and that of our merchant of record and hosting providers, may occur in the United States and other countries. Where we transfer personal data of EU/UK residents internationally, we rely on an appropriate transfer mechanism (such as the Standard Contractual Clauses or the UK International Data Transfer Addendum).

10. Changes

We may update this Policy; material changes will be communicated in-app, by email, and/or by posting on tatastu.dev with an updated effective date.

11. Contact

Qadri LLC (Tatastu) Email: support@tatastu.dev Mailing address: 304 S Jones Blvd, Las Vegas, NV 89107, United States