Data handling
This policy explains how Orkestr accesses, uses, stores, protects, and shares personal information, including data connected through Google Workspace.
This policy applies to the hosted Orkestr service available through orkestr.de and its official connection pages. The hosted beta is operated by Orkestr. Contact: Ask the person who invited you..
Independent self-hosted installations are controlled by their respective operators. Unless a self-hosted operator connects that installation to an Orkestr-hosted service, the Orkestr hosted service does not receive data from that installation.
Orkestr processes information needed to provide user-requested workflows: account and contact details, chat messages, files, task outputs, timers, workspace records, connector status, managed-browser activity, security records, and technical service logs. Orkestr does not ask users to provide account passwords through chat.
The public Google integration can request only the capabilities enabled for the deployment and required by the user-requested action. The currently enabled scopes are: openid, userinfo.email, userinfo.profile, https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.send, https://www.googleapis.com/auth/gmail.compose, https://www.googleapis.com/auth/calendar.events.readonly, https://www.googleapis.com/auth/calendar.events.owned.
Orkestr accesses only the Google capabilities required by the user-requested action and granted by Google. It does not retrieve contacts, mailbox settings, or a complete mailbox or Calendar export. If Orkestr introduces a capability requiring additional Google scopes, it will update this policy and the in-product disclosure and obtain new consent before requesting that access.
Orkestr uses Google identity data to display and manage the connected account, authorization data to maintain the connection, selected Gmail data to perform user-requested draft, read, notification, or message workflows, selected Calendar data to list or manage events, and operation metadata to report results. Orkestr requests access for a specific user-facing action; Google is the only consent screen that grants it. Google user data is not used for unrelated purposes.
Orkestr does not sell Google user data. It does not provide Google user data to advertising platforms, data brokers, or information resellers, and does not use it for advertising, credit decisions, or to develop, improve, or train generalized or non-personalized AI or machine-learning models.
Data is disclosed only in these limited circumstances:
Service providers are permitted to process data only for the service purpose for which it was disclosed and must protect it appropriately.
Google OAuth credentials are stored in the connected user's isolated connector storage and retained until the user disconnects the account, the grant is revoked, the account is deleted, or the credentials expire and are no longer needed. A disconnect requests revocation from Google before deleting the local credential record.
Google content used in a requested workflow may remain in the user's Orkestr chat, draft, notification, or task history when it is part of the user-visible result. Orkestr does not maintain a separate complete copy of the user's Gmail mailbox or Calendar. Notification state stores bounded rule configuration, message identifiers used for deduplication, run status, and selected previews. Connection requests are one-time and expire. Encrypted credential records may remain temporarily in protected operational backups until those backups rotate.
No system can guarantee absolute security. Suspected unauthorized access is investigated and affected users and authorities are notified when required.
Orkestr's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace data is used only to provide the user-facing feature requested by the user. Orkestr and its service providers do not use Google Workspace data to develop, improve, or train generalized or non-personalized AI or machine-learning models.
Users can decline Google access and continue using Orkestr without Gmail. A connected account can be disconnected from Orkestr setup, which revokes the Google grant and removes locally stored credentials. Users can also revoke Orkestr from their Google Account permissions page.
Users may request access, correction, export, restriction, or deletion of their Orkestr data through the invitation chat, the data deletion page, or Ask the person who invited you.. Some minimal records may be retained where required for security, abuse prevention, dispute handling, or law.
Depending on the context, Orkestr processes data to provide the service requested by the user, based on the user's consent for optional connectors, for legitimate security and reliability interests, and to meet legal obligations. Providers may process data in countries outside the user's country; Orkestr relies on the provider's applicable contractual and legal transfer safeguards.
Material changes to Google data access, use, or sharing will be reflected here and in the in-product disclosure before new access is requested. Questions or privacy requests can be sent to Ask the person who invited you..