How the Orcheri Alpha uses your information
Notice 2026-10-03-alpha-3.
R4.6 introduces a separate optional desktop choice. Read the Product Learning disclosure for that new scope and its controls. The dated notice below preserves the earlier Alpha terms; choosing the new scope requires its own explicit account confirmation.
Who operates the Alpha
Orcheri is an independent project released and operated by an independent developer, not an incorporated company. The operator is presented under the Orcheri project name at the end of this notice. Questions about your information can be sent to support@orcheri.com.
This notice describes the current Controlled Private Alpha. It does not claim compliance with a particular jurisdiction or promise a geographic processing location.
Your local work and your AI providers
Orcheri stores Rooms, conversations, memory, decisions and its work records on your PC. Room and work content is not automatically uploaded to the Orcheri online service. Your project files remain where you keep them. Signing in or setting up another PC does not synchronize your Rooms.
When a teammate works, Orcheri supplies relevant context from the Room to that teammate’s runtime. Claude Code, Codex and Cursor process work through their own providers under your accounts, including context and material the runtime gathers. Their own terms and data policies apply. Work and results shared with another teammate may be sent to that teammate’s provider too.
Local backups and exported handoffs are files you choose to save. They are separate from hosted-service backups. A local Orcheri backup is not encrypted by Orcheri and does not include an external project folder; keep it private. An export or backup goes elsewhere only through an action you or another tool takes.
What the online service keeps and why
Applications: your verified email address, optional preferred name, the agents you use, your answer about what you want them to do together, your Windows answer, the application’s status and review history, and the privacy-notice revision shown with your request. These records support manual Alpha review and communication about your request.
Accounts and authentication: your account identifier, email and verification state, sign-in provider and provider identifier, account status, sign-in/session records and your optional choices and their history. The identity service handles passwords and sign-in security; Orcheri does not receive your password. Temporary login records bind the return from that service to the browser that started it.
Access and PCs: approval, suspension or revocation records; installation identifiers, a PC label you supply, one-way fingerprints of installation keys, relevant desktop versions, activation and access-check times, and access expiry. These records let you explicitly activate a PC and let Orcheri check whether it may start new work. Activation is separate from approval.
Releases and downloads: the versions and immutable release files offered through the Alpha channel, their integrity and publication records, short-lived download tickets, and account- or invitation-linked download attempts and outcomes. Update and access checks contact the service automatically while the desktop is running; they do not upload your Room content.
Email: the recipient, purpose, source record, delivery state, retry state and provider delivery references for transactional messages. Providers process the message needed to deliver it. Usable emailed codes may be held encrypted briefly for delivery; validation uses one-way fingerprints, and expired delivery secrets are removed.
Support and contact: the subject, message text, replies, timestamps and account link of support threads; for the public contact form, the email address, optional name, topic and text you supply. Room content, prompts, paths and files are not automatically attached. We receive whatever you choose to type or send, so leave out secrets and private work you do not want to share.
Diagnostics: only when you choose to send a report, its typed installation, version, access and connectivity facts, plus the report’s format and integrity metadata. You can preview it first. It is not an automatic upload of a conversation, repository or raw log.
Operations and security: operator actions, timestamps, record identifiers, outcomes and bounded operational information; short-lived rate-limit counters and security/session records. Hosting and delivery infrastructure also processes connection and request information to operate and protect the service. These records are separate from a diary of your Room work.
Services involved
Cloudflare serves the public website and provides network protection and technical error reporting. Render hosts the Alpha service; Supabase provides its PostgreSQL database; Cloudflare R2 stores release files and service-backup objects. These infrastructure services process the information needed for those roles.
ZITADEL handles Orcheri account authentication. Google is an optional sign-in method where offered through ZITADEL. Google and email sign-in are not permission to merge existing accounts by email address. Resend delivers the service’s transactional email. Your own AI providers separately process the work you give their runtimes.
Providers operate under their own terms and applicable arrangements with the operator. This notice makes no promise that all processing stays in one country. Ask the privacy contact about the current arrangements.
Browser storage and analytics
The public website stores your appearance preference in your browser. Sign-in and account pages use cookies for login security and sessions. Identity-provider pages use their own authentication storage. Cloudflare may collect network-error reports and infrastructure providers keep operational and security records.
Orcheri does not collect desktop usage analytics or automatically ingest Room history for product learning. Transactional email is sent without open or link tracking. Optional Alpha product-learning participation does not authorize silent collection of your work.
Your choices
Launch news and optional Alpha product-learning activity are off unless you choose them. Neither affects your request or access. You can change them from your request or account page. Messages needed for your own application, account, access or support are separate from marketing.
You choose whether to send support messages or diagnostics. You may withdraw an application, remove a PC’s activation, or ask to see, correct or delete hosted information. Removing an activation or ending Alpha access does not delete local Rooms. Local files and provider-held data have separate controls.
Retention and backups
The service’s retention maintenance removes an application whose email was never confirmed once it is over 30 days old. After 90 days from decline or withdrawal, it removes the use-case and agent answers; the remaining contact, Windows and decision records are not all erased by that step. Waitlisted requests are reviewed after 12 months; that review is a human action, not an automatic deletion.
Account, identity, consent, approval and PC records are kept while needed to administer access, security and your choices. They do not all have an automatic fixed expiry. You can ask the privacy contact about removal and any information that must be retained.
Closed support threads are scheduled for removal after 365 days from closure. A new message can reopen a thread. Contact requests are scheduled for removal after 365 days from their last change. Diagnostic report content is removed after 30 days, or earlier on request; metadata describing the attachment stays with its message until that thread is removed.
Finished mail records and operator audit entries are scheduled for removal after 365 days; download attempts after 365 days from the request, once no live ticket refers to them. Short-lived login, session, challenge and ticket records expire separately and are cleared by maintenance, generally after a one-day grace period; rate-limit windows and idempotency records are cleared after expiry.
Orcheri limits the content-free network and security logs it controls to 30 days, with shorter IP rate-limit windows. Infrastructure providers may maintain their own operational and security records under their applicable policies and settings; Orcheri does not control every provider-held copy. Account, consent, operator audit and transactional delivery records have separate retention purposes and policies. Optional daily activity, if introduced with separate default-off consent, has a 90-day policy; the current desktop does not send that activity.
Hosted database backup objects are scheduled for deletion 30 days after their creation in the object store. Exported recovery journal objects are scheduled for deletion 90 days after export or upload. Provider-side deletion may complete after scheduled expiry, so these schedules are not guaranteed physical-erasure deadlines. Orcheri’s periodic cleanup also depends on successful operations runs. Its own cleanup keeps the latest verified backup pair, but the provider lifecycle does not exempt that pair. Primary deletion and backup expiry are different operations. The service journals relevant deletion and revocation acts so restoring an older backup does not intentionally reinstate them. Database journal cleanup remains based on the event’s occurrence; the total age of an exported object can also include the delay before export. Local desktop backups remain wherever you saved them until you remove them.
Questions, correction and deletion
Write to support@orcheri.com to ask what the hosted service holds, correct it or request deletion. We may need to verify that the request belongs to you. We will explain what can be removed and what is retained and why. A public contact-form address alone does not prove ownership of an account.
Deleting hosted account information does not remove Rooms or backups from your PC or data already processed by your AI providers. Use the desktop’s local controls and your providers’ own processes for those. Do not send passwords, sign-in codes, private keys or an entire Room with a privacy request.
Contact
- Operated by
- Orcheri
- Privacy contact
- support@orcheri.com