Privacy Policy

1. Introduction

Orkas is a local-first AI agent client. This Privacy Policy explains what information we handle when you use the Orkas desktop application, our website (orkas.aiorkas.work), and the services that support them (together, the "Service").

Two design choices shape this policy:

• Local-first. The desktop client runs on your computer. By default, your tasks, files, agent and skill configurations, and many credentials for third-party services you connect are kept on your device. The current public desktop release does not enable the iOS remote-control relay.
• Model and tool routing. You can bring your own model and tool providers. For direct providers, requests travel between your device and the provider you chose. If you choose Orkas-managed features — such as Orkas-managed LLM, search, image, video, voice, speech, or managed connector services — the relevant content is sent to Orkas servers and then to the upstream providers needed to perform the request.

The rest of this policy covers the cases where information reaches our servers: signing in to your account, multi-device sync, managed AI and tool features, billing and credits, authorizing third-party tools, anonymous usage analytics, our website, support communications, and any future relay feature you explicitly enable.

2. Information we collect

2.1 Information you provide

• Account information. To use the Service you sign in with a supported login method shown in the product. Depending on the method, we may receive and store your user ID, email address, display name, profile picture, phone number, provider identity, device ID, and session records to operate your account.
• Billing information. If you subscribe to a paid plan or buy credits, we store subscription tier, entitlement, billing status, payment-provider customer or subscription IDs, credit balances, credit ledger entries, and usage counters. Payment-card details are handled by our payment processor; Orkas does not store full card numbers.
• Download-link requests. If you ask us to email a download link, we store the recipient address, request time, and delivery status to send the link, prevent abuse, retry temporary failures, and troubleshoot delivery.
• Support communications. Messages you send us by email, including any attachments and contact details you choose to include.

Please do not provide us with sensitive personal information (government IDs, financial-account numbers, health, biometric, racial / ethnic, religious, or political data) through the Service or in support emails.

2.2 Information generated by your use of Orkas

• Service activity records. When the desktop client or website talks to our servers — for sign-in, sync, the marketplace, billing, managed tools, connector authorization, or in-product messages — we record standard request information (such as IP address, time, the action being requested, and the result) and use it for security, abuse prevention, and reliability.
• Anonymous usage statistics. We collect page views and a small set of in-product UI events, and use them in aggregate to understand which features are used. These records do not include message contents, prompts, file contents, or credentials, and they are not linked to your account.
• Sync content. When you enable multi-device sync, data related to tasks, projects, agents, skills, connectors, data libraries, saved apps, and similar product data is uploaded to our cloud storage so your other devices can pull it down. Access to sync storage is scoped to your account, and sync data is encrypted at rest in cloud storage. We do not read or otherwise access the contents of what you sync.
• Future relay content. If Orkas offers an iOS remote-control feature in a future release and you enable it, Orkas servers would process the device, command, attachment, and mirrored conversation data needed to provide it. The current public desktop release does not enable this relay.
• Managed AI, media, search, and connector content. When you use Orkas-managed LLM, search, image, video, voice, speech, or managed connector features, we process the content needed to perform the request, such as prompts, messages, attachments, search queries, speech audio, text for speech, image or video prompts, reference images or URLs, connector tool arguments, and connector tool results. We also record metered usage, such as token counts, search calls, generated media, voice seconds, and credits used.

2.3 Information that usually stays on your device

Unless you enable sync or relay, connect server-managed integrations, or choose Orkas-managed AI or tool features, the following are kept on your computer and are not sent to Orkas servers:

• Inputs and prompts — what you type to an agent.
• Generated output — agent replies, files, and other artifacts the agents produce.
• Task history, attachments, agent and skill definitions, project bindings, preferences.
• Access credentials for direct third-party providers you connect, stored securely on your device where supported. Some connector grants are server-managed or held by a managed connector provider, as described below.

For direct model or tool providers that you configure yourself, prompts, Output, and fetched tool content travel between your computer and the provider you direct the agent to use. When an agent uses a connected tool (for example, reading a message or calendar event to answer your question), the relevant content fetched from that tool may be included in the prompt sent to the language-model provider you configured. That direct-provider path does not use Orkas-managed model servers.

2.4 Cookies and similar technologies

Our website uses a small number of cookies and local-storage entries for essential functionality (such as remembering your selected language) and to support the anonymous usage statistics described above. We do not use cookies for cross-site tracking or advertising. The desktop client does not use browser cookies.

3. How we use information

We use the information described above to:

• Provide the Service — authenticate you, deliver sync and relay, host the marketplace, route in-product communications, operate managed AI and tool features, process billing and credits, and operate the website.
• Maintain and secure the Service — detect abuse, defend against attacks, debug failures.
• Communicate with you — respond to support requests, send important service notices.
• Improve the product — understand how the Service is used through anonymous, aggregated statistics.
• Comply with the law — respond to valid legal process and meet our regulatory obligations.

We do not use your content to train AI models. We do not sell personal information. We do not use your information for advertising.

4. How we share information

We share information only in these limited circumstances:

• Service providers. Infrastructure providers (cloud hosting and storage, identity, email, SMS, payment processing, analytics, etc.) that operate the Service on our behalf under appropriate confidentiality and data-protection commitments. They may use the information only to provide their services to us.
• Managed feature providers. If you choose Orkas-managed model, search, media, speech, or connector features, we send the content needed for the request to upstream providers that perform those functions for us.
• Third-party services you connect. When you connect a workspace, developer, messaging, storage, payment, search, or other connector shown in the product, your agent acts on that tool on your behalf. See Third-party integrations.
• Legal and safety. When required by valid legal process, or where we believe in good faith that disclosure is necessary to protect rights, property, or safety.
• Business transfers. If Orkas is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you and the commitments in this policy will continue to apply.

We do not share personal information with advertisers, data brokers, or any party for advertising purposes.

5. Third-party integrations

Orkas lets you connect external tools so the agents can act on them on your behalf. The connector catalog may change over time; examples include:

• Third-party and managed connector platforms that connect mail, calendar, storage, documents, spreadsheets, tasks, code hosting, issue trackers, CRM, messaging, payment, search, webmaster, and similar services
• Provider-hosted connectors and managed connector providers that handle provider authorization and tool execution on your behalf
• Custom or provider-specific connectors shown in the product catalog from time to time

To use agents you may configure a language-model provider with your own credentials, such as OpenAI, Anthropic, or another provider, or choose an Orkas-managed model where available.

Each provider's privacy policy and terms govern how that provider handles your data on its side.

5.1 Third-party and managed connector data

When you connect a third-party or managed connector, authorization may be handled by the provider, by a managed connector platform, or by an Orkas server-bridge flow. Depending on the connector, Orkas may keep a local grant on your device, an encrypted server-managed grant, or an opaque server-side connection handle. The authorization screen or connector provider shows the exact account, service, and scope being connected.

Connector tool calls may process the content needed for your request, such as account labels, file or message metadata, emails, calendar events, documents, spreadsheets, tasks, code, issues, tickets, CRM records, messages, payment records, search or webmaster data, tool arguments, and tool results. Orkas uses this connector data to provide the connector functionality you request, maintain security and reliability, meter usage where applicable, and troubleshoot failures. We do not use connector data to train AI models, for advertising, or to sell or share with data brokers.

You can revoke connector access at any time from Settings → Connectors in Orkas, from the managed connector provider where applicable, or from the third-party service's own account-permissions page.

5.2 Orkas-managed AI, search, media, and connector providers

When you select Orkas-managed LLM, search, image, video, voice, speech, or managed connector features, Orkas forwards the relevant content to upstream providers that perform those functions, such as model providers, search providers, speech and media generation providers, SMS providers for phone-code login, payment processors, and managed connector providers. We use these providers to deliver the feature, meter credits, prevent abuse, and troubleshoot reliability. We do not use your content to train Orkas models, and we do not sell your content or personal information.

6. Data retention

• Account and billing records — retained while your account is active. After you close your account, we delete or anonymize account records within 30 days, except where longer retention is required by law, payment processing, tax, accounting, dispute resolution, fraud prevention, or security.
• Sync data — retained until you turn sync off, delete the data from your device (which propagates a deletion), or close your account.
• Future relay data — if a future relay is offered and enabled, it would be retained only as needed to provide that experience under the terms shown when enabled.
• Managed feature records — request metadata and service logs are retained for a limited period, while credit ledgers and usage counters may be retained for account, billing, abuse-prevention, and accounting needs. Asynchronous media tasks may retain task payloads and results for a short period so the task can complete and be retrieved.
• Connector grants and handles — local grants remain under your control on the device. Server-managed connector grants, DCR refresh grants, and managed connector handles are retained until you disconnect the connector, close your account, or the provider requires reconnection.
• Service activity records — retained for a limited period (typically up to 90 days), then deleted or aggregated.
• Usage statistics — retained in aggregated form; not linked to your account.
• Download-link requests — recipient and delivery records are retained for up to 180 days, then deleted.
• Support communications — retained for follow-up and historical context.
• Local data — controlled entirely by you. Deleting your local data directory removes it.

We may retain information longer where required by law, or where it is needed to defend legal claims.

7. Your rights and choices

Depending on where you live, you may have rights to access, correct, export, delete, or restrict the processing of your personal information, and to withdraw consent or object to processing. You also have the right to lodge a complaint with your local data-protection authority.

Many everyday choices can be exercised directly in the product:

• Disconnect a third-party integration to revoke its access.
• Turn off multi-device sync to stop further uploads.
• Disable managed features you do not want to use; if a future relay is offered, do not enable it or disable it.
• Sign out, or delete your local data directory, to remove what lives on the device.

For requests that we need to handle — access, export, correction, or deletion of server-held information, or closing your account — email us at [email protected]. We respond within 30 days. We may ask you to verify your identity before fulfilling certain requests.

8. Security

We use industry-standard measures to protect your information, including encryption in transit between clients and our servers, server-side encryption for sync data stored in cloud storage, secure local storage for access credentials where supported, encryption and access controls for server-managed connector grants, and access controls within our infrastructure. No system is perfectly secure; if you believe you have found a vulnerability or that your account has been compromised, contact [email protected].

9. Data location

We store your account data, sync data, relay data, and managed-feature records on infrastructure we operate to host the Service. Managed features and third-party integrations may send content to upstream providers in the jurisdictions where those providers operate. Where the laws of your country provide rights or safeguards regarding cross-border transfer of personal information, we comply with the applicable requirements.

Your account data and sync data are stored on infrastructure located within mainland China. If you choose managed features or third-party integrations, the content needed for those requests may be sent to the selected or configured upstream providers as described in this policy, including providers outside mainland China where applicable and permitted by law.

10. Children

Orkas is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us so we can delete it.

11. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be announced on this page with a revised "Last updated" date, and, where required by law, with additional notice in the product or by email. Your continued use of the Service after the changes take effect means you accept the revised policy.

12. Contact us

For privacy questions, requests, or complaints, email [email protected].