Last updated: July 03, 2026. This policy explains how Operon collects, uses, stores, shares, and protects information when you use the Operon website, workspace, connectors, outputs, and workflow automation services.
This policy applies to Operon users, workspace administrators, team members, and visitors who interact with Operon public pages, signup, authentication, dashboards, workflow configuration, connectors, outputs, support, and related services. Operon is the service operator for the purposes of this policy.
Questions about this policy or privacy requests can be sent to support@operon.aionquartz.com.
Operon collects account and workspace information such as names, email addresses, authentication identifiers, workspace names, team membership, selected verticals, workflow configuration, review thresholds, subscription state, trial state, billing metadata, and privacy acceptance records.
Operon collects workflow information that you or your connected systems submit to the service, including uploaded files, emails, attachments, documents, structured fields, extracted values, validation results, review decisions, comments, output mappings, delivery attempts, and audit history.
Operon collects operational telemetry such as route views, feature interactions, approximate IP-derived location, user agent, browser, operating system, device type, timestamps, service logs, error details, usage events, security events, and diagnostic metadata. Operon does not collect browser device MAC addresses or use covert browser fingerprinting.
Operon uses information to create accounts, provision workspaces, authenticate users, enforce team access, configure workflows, run intake and extraction, validate data, support human review, deliver approved outputs, maintain audit logs, secure the service, detect abuse, provide support, measure product health, and improve user-facing workflow features.
Operon may use aggregated or de-identified operational data to understand reliability, performance, feature adoption, and service quality. Sensitive document contents are not placed into product analytics events.
Workflow content may be processed by configured AI, OCR, connector, storage, delivery, and infrastructure providers only as needed to provide the workflow features enabled in your workspace. These providers may process text, images, documents, metadata, extracted fields, and output payloads according to workspace settings and the role they perform for the service.
Operon does not use Google user data for model training unless a separate feature clearly asks for explicit consent and the privacy policy is updated to describe that use. If a provider offers controls to disable training or retention for customer content, Operon configures those controls where available and appropriate for the service.
If you choose to sign in or sign up with Google, Operon may receive your Google account identifier, email address, profile name, and basic profile information made available through the sign-in flow. Operon uses this data to authenticate you, create or locate your Operon account, associate you with a workspace, and maintain secure sessions.
Google sign-in profile data is not used for advertising, retargeting, credit-worthiness decisions, or sale to third parties.
If a workspace administrator connects Gmail, Operon requests access only to the Google scopes configured for that Gmail connector. Operon uses Gmail data to monitor selected labels or message lists, retrieve messages and attachments, normalize workflow intake, extract operational data, and create review or delivery records visible in the Operon workspace.
Gmail data may include message identifiers, label identifiers, sender and recipient metadata, timestamps, subject lines, message bodies, attachments, and related metadata. Operon stores Gmail-derived workflow records, audit events, selected configuration, and encrypted OAuth tokens only as needed to provide and maintain the connected workflow feature.
If a workspace administrator connects Google Drive, Operon uses Drive access to read files and metadata from configured folders or files for workflow intake. Drive data may include file identifiers, file names, MIME types, timestamps, folder identifiers, document contents, images, PDFs, and related file metadata.
Operon uses Drive data to ingest documents, extract structured workflow information, run validation, support human review, and create output records. Operon does not use Drive data for unrelated product features, advertising, retargeting, credit-worthiness decisions, or sale to third parties.
If a workspace administrator connects Google Sheets as an output, Operon uses Google Sheets access to append or write approved workflow output into the configured spreadsheet and range. Sheets data may include spreadsheet identifiers, sheet ranges, output rows, field values, delivery status, and account metadata for the connected Google account.
Operon uses Google Sheets data only to deliver configured workflow outputs, test configured output mappings, maintain delivery history, troubleshoot delivery failures, and secure the connection.
Operon's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Operon uses Google user data only to provide or improve user-facing features that are visible in the Operon interface and configured by the workspace.
Operon does not sell Google user data, does not use Google user data for advertising, retargeting, personalized advertising, interest-based advertising, or credit-worthiness decisions, and does not transfer Google user data to data brokers, advertising platforms, or information resellers.
Operon transfers Google user data only as necessary to provide the connected workflow feature, comply with law, protect security, investigate abuse, or complete a merger, acquisition, or sale of assets after any consent required by applicable law and Google policy. Operon personnel, contractors, agents, and successors must handle Google user data consistently with these commitments.
OAuth access tokens, refresh tokens, API keys, webhook secrets, and similar connector credentials are stored as workspace-scoped secrets and encrypted before persistence where the application supports secret storage. Operon uses these credentials only to maintain the configured connector or output, refresh access when allowed, and perform authorized workflow actions.
Workspace administrators should disconnect providers, rotate credentials, or remove team members when access is no longer needed.
Operon may share information with infrastructure, authentication, analytics, payment, email, AI, OCR, storage, connector, output, monitoring, and support providers that help operate the service. These providers are permitted to process information only for the services they provide to Operon or the workspace.
Operon may also disclose information if required by law, to protect rights and safety, to investigate abuse or security incidents, or as part of a business transaction subject to appropriate legal requirements.
Operon retains account, workspace, workflow, audit, billing, telemetry, and support data for as long as needed to provide the service, meet security and audit requirements, resolve disputes, comply with law, and enforce agreements. Retention periods vary by data type, workspace configuration, and legal requirement.
Workspace administrators may delete or disconnect configured providers and may request deletion or export assistance by contacting support@operon.aionquartz.com. Some records may be retained where required for security, legal, billing, backup, or audit purposes.
Workspace owners and administrators can manage team access, configure connectors and outputs, disconnect providers, update workflow settings, review audit history, and control which operational systems are connected to the workspace. Users can contact Operon to request access, correction, deletion, export, or other privacy assistance.
To make a privacy request, contact support@operon.aionquartz.com. Operon may need to verify your identity and workspace authority before acting on a request.
Operon uses administrative, technical, and organizational safeguards designed to protect information, including tenant isolation, role-based access patterns, encrypted secret storage, audit logging, security headers, and operational monitoring. No internet service can guarantee absolute security, but Operon works to reduce risk and respond to issues promptly.
Operon may update this policy as the service, legal requirements, or provider policies change. Material updates will be reflected on this page with a new last-updated date. Continued use of Operon after an update means the updated policy applies to later use of the service.
The Operon Terms and Conditions describe additional service terms.