Optional Product Learning

Revision 2026-10-21-product-learning-v3.

This separate disclosure covers the optional desktop choice introduced in R4.6. The existing Alpha Privacy Notice continues to describe account and service processing. Its historical statements that the then-current desktop sent no usage analytics do not describe an R4.6 account that explicitly enables this new purpose.

A separate, optional choice

Help improve Orcheri by sharing a limited picture of how the app works. This is a new Product Learning choice, separate from earlier Alpha participation or launch-news choices. Setup offers one optional, initially unchecked choice. After sign-in, Orcheri associates it with your verified account and service only when its Windows-user and account provenance are clear; the service must acknowledge it before sharing starts. If attribution is uncertain, sharing stays off and the authenticated app offers a short resolution. Declining does not affect installation, activation, updates or ordinary use. Settings > Privacy & data remains available for later changes and withdrawal.

What is shared

Your Alpha account and installation can be linked to app version and channel, recent app connectivity and whether a window is visible or minimized, coarse daily launch and usage totals, interaction and execution time ranges, days on which you started meaningful work, broad feature and single-agent or team use, runtime families discovered, ready or used, bucketed attempt and outcome counts, fixed connection or reliability problem categories, and update presentations, dismissals or handoff failures. Connectivity means an app reached the service; it does not prove a person is present. Orcheri does not inspect activity in other applications.

What stays out

No conversation or prompt text, answers, project names, file names or paths, files, screenshots, clipboard contents, exact team rosters, commands, raw errors, model names, native session contents, provider credentials or token and cost records enter Product Learning. It does not copy your Rooms to the cloud or start provider work for measurement. Support content is sent only through the separate support choices you make.

Who can see it

Orcheri uses these observations to improve onboarding, runtime connections, reliability, updates and broad product adoption. Account-linked learning views are restricted to the authorized Owner role in Operations; ordinary support access does not expose them. There is no analytics export. Duration views describe a cohort only, after at least five participating accounts contribute; there is no individual hours-worked view or productivity score. The operator, service providers and privacy contact are identified in the Alpha Privacy Notice.

Your continuing control

Settings → Privacy & data shows the account, service and current choice. Turning sharing off stops this PC's optional recording immediately, clears its pending optional data and requests withdrawal for the account. If offline, the request is shown as waiting and is retried; the service cannot erase data until it receives the request. Other PCs may retain a previously acknowledged policy for at most 24 hours while offline. Once withdrawal reaches the service, it refuses old-policy uploads and removes the account-linked learning history. A reinstall, sign-in or replayed Setup receipt cannot silently turn it back on.

Retention and deletion

Local optional queues are bounded and expire after seven days. Recent presence and duplicate-delivery receipts are retained for seven days; daily learning summaries for 90 days. Necessary new installation or update-delivery receipts are retained for 30 days. Current consent proof and minimal withdrawal records remain to honor your choice, prevent replay and avoid restoring erased learning. Withdrawal deletes linked learning from active storage; Privacy Settings reports the result or a delay. Hosted backups are scheduled to expire after 30 days and exported recovery journals after 90 days, with provider deletion potentially completing later. Restore replays withdrawals and expiry before optional collection can resume. These schedules are not a promise of immediate physical erasure from backups.

Separate service records

Account, application, approval, activation, release download and access records are separate from Product Learning. Where enabled and justified for service delivery, a small installation receipt can report that the app reached a usable launch, a fixed launch problem, or Windows accepted an update-page open request. These receipts do not prove installation completed, a download finished or a person used the app. Declining optional learning does not remove records needed to provide access, downloads, security or requested support. Existing service-record retention is described in the Alpha Privacy Notice.

Questions or requests

Use the privacy contact in the Alpha Privacy Notice to ask about the operator, applicable basis, countries where processing occurs, your information, correction or deletion. Do not send passwords, sign-in codes, provider credentials or an entire Room. Local Rooms and provider-held information have their own controls and are not erased by a hosted Product Learning withdrawal.

Operator and contact

Orcheri

Privacy questions: support@orcheri.com.

Manage this choice in the Orcheri desktop's Settings → Privacy & data. This page does not enroll you or change your Alpha application or access.