Legal Privacy
Privacy Policy.
What we collect, why, and the choices you have. Your files stay on your device unless a request needs them.
Last updated September 27, 2026
Overview
This Privacy Policy explains how Orch ("Orch", "we", "us") collects, uses and shares information when you visit orch.live (the "Website") or use the Orch Code desktop application (the "App"). Together we call these the "Services". If you have questions, email sameer@orch.live.
Information we collect
Account information. When you sign in with Google on the Website or in the App, we receive your name, email address, profile photo and a unique account identifier from Google.
Content you publish. If you write for the Orch blog, we store your drafts, submitted posts, cover images, tags and any review comments.
Messages. If you contact us, we store your name, email address and the content of your message.
Telemetry and crash reports from the App. The App sends usage events (such as app version, operating system, feature usage and performance timings) and crash reports (such as stack traces and device state at the time of a crash) so we can fix bugs and improve reliability.
AI usage records. To apply your monthly AI credit, we record the number and size of requests you make and the model used.
Technical data from the Website. Our hosting provider processes standard server logs such as IP address, browser type and pages requested, for security and reliability.
Your files, prompts and integrations
Orch Code runs on your computer. Files in the folders you open stay on your device unless a request needs them.
When you ask the agent to do something, your prompt and the file or integration content needed for that request are sent to the AI model provider that handles the request (OpenAI or Anthropic) to generate a response.
Access tokens for Google Drive, Gmail, Notion, Slack, Jira, GitHub and other integrations are stored on your device. Orch does not store these tokens on its servers. The App uses them to talk to those services directly on your behalf.
We do not sell your files, prompts or integration data, and we do not use them to train our own models.
How we use information
- Provide, maintain and secure the Services
- Apply and measure your monthly AI credit
- Review, publish and moderate blog content
- Respond to messages
- Diagnose crashes, fix bugs and improve performance
- Prevent fraud, abuse and violations of our Terms
- Comply with legal obligations
Who we share information with
We share information only with service providers that help us run the Services, under contracts that limit their use of it:
- Google Firebase and Google Cloud: authentication, database, file storage and hosting
- OpenAI and Anthropic: processing AI requests you make in the App
- Email delivery providers: delivering contact form messages to us
- Crash and telemetry processing tools used by the App
We may also disclose information if required by law, to protect the rights and safety of users or Orch, or as part of a merger or acquisition, in which case this Policy continues to apply.
Published blog posts, including your name and profile photo as the author, are public.
Cookies
The Website uses a single first-party cookie, __session, to keep you signed in to the writing and review tools. We do not use advertising or cross-site tracking cookies.
Retention
We keep account and content data for as long as your account is active. Messages are kept for up to 24 months. Telemetry and crash reports are kept for up to 18 months. You can ask us to delete your data at any time.
Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict certain processing, and to withdraw consent. To exercise these rights, email sameer@orch.live. We will respond within 30 days. You may also complain to your local data protection authority.
You can turn off optional telemetry in the App's settings where available.
Security
We use encryption in transit, access controls and least-privilege rules to protect data. No system is perfectly secure, so we cannot guarantee absolute security.
International transfers
Our service providers may process data in the United States and other countries. Where required, we rely on appropriate safeguards such as standard contractual clauses.
Children
The Services are not intended for anyone under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided us data, contact us and we will delete it.
Changes to this policy
We may update this Policy. If changes are material, we will notify you on the Website or in the App before they take effect. The date at the top shows when it was last updated.
Contact
Orch · sameer@orch.live · orch.live