Rote Privacy Policy

Effective Date: May 28, 2026 Last Updated: August 14, 2026

1. Introduction

This Privacy Policy ("Policy") describes how Modiqo Inc., a Delaware corporation ("Modiqo," "Company," "we," "us," or "our"), collects, uses, discloses, and protects information in connection with the rote software, services, websites (including https://www.modiqo.ai and https://rote.dev), and related offerings (collectively, the "Service").

By accessing or using the Service, you acknowledge that you have read and understood this Policy. If you do not agree with this Policy, you must not use the Service.

BETA NOTICE: The Service is currently in beta. Features, data practices, and this Policy may change as the Service evolves. We will notify users of material changes. By participating in the beta, you acknowledge that the Service is under active development and data handling practices may be refined over time.

2. Information We Collect

2.1 Information You Provide

Account Information: When you create an account, we collect your name, email address, and authentication credentials (via OAuth providers such as Google or GitHub).
Profile Information: Organization name, role, and other optional profile details you choose to provide.
Payment Information: If you subscribe to paid tiers, payment details are processed by our third-party payment processor (Stripe). We do not store full credit card numbers.
Communications and Sales Inquiries: When you contact us for support, feedback, or a sales inquiry, we collect the information you submit. The website sales form currently asks for first and last name, work email, company website, selected tier, billing preference, team size, number of organizations, what you need, where you are in your evaluation, and your message.
Registry Contributions: If you publish adapters, skills, or flows to the rote registry, we collect the content you submit and associated metadata (author name, description, version).

2.2 Information Collected Automatically

Usage Telemetry: Pseudonymous usage data tied to your registered account identifier and to a randomly generated installation identifier created on first use. Telemetry events describe actions you initiate through the Service, including: the name of the command invoked, the names (but not the values) of any flags you pass, the command's outcome (success, failure, or cancellation) together with a coarse error category, the duration of execution, and product-funnel signals indicating which stages of the Service you have used (such as completing onboarding, creating an adapter, executing a probe or call, exporting a workflow, or publishing to the registry). For certain registry and invitation events, fields that may identify third parties (such as email addresses and shared workflow names) are subjected to a one-way salted transformation before transmission; this transformation reduces identifiability but is not irreversible anonymization. Telemetry does not include the content of your API requests, responses, or workspace data, the values of command arguments or flags, file paths, request URLs, verbatim error messages, or the contents of files you process. You may opt out of telemetry (see Section 6.4).
Log Data: Server logs including IP address, browser type, operating system, referring URLs, access timestamps, and pages viewed when you visit our website or use cloud features.
Website Analytics: We use Plausible Analytics to measure aggregate website activity. Depending on the page or action, this may include the page URL, referrer, browser, operating system, device type, approximate country derived by Plausible, scroll depth, and anonymous events such as section views, CTA clicks, video progress, pricing selections, and form outcomes. We configure our event properties to exclude names, email addresses, form contents, account or organization identifiers, and other free text. Plausible does not use cookies or persistent identifiers for this measurement, and Modiqo does not use these analytics to build cross-site or cross-day visitor profiles.
Device Information: Operating system family, processor architecture, rote CLI version, whether the Service is running in a continuous-integration environment, and the name of the host environment driving rote (for example, an IDE extension or terminal agent), drawn from a fixed allowlist.
Authentication Tokens: OAuth tokens for third-party services you connect through rote are stored locally on your device by default and encrypted at rest. Tokens synced via the vault feature are encrypted end-to-end.

2.3 Information We Do NOT Collect

Workspace Data: By default, all workflow data, cached API responses, and workspace state are stored locally on your machine. We do not have access to this data unless you explicitly use cloud sync features.
API Request/Response Content: The content of API calls made through rote adapters is not transmitted to Modiqo servers. This data remains local to your environment.
Command Arguments and Flag Values: The values of arguments and flags you pass to rote commands (including file paths, identifiers, search queries, and free-text inputs) are not transmitted as part of telemetry. Only the names of flags used are recorded.
Verbatim Error Content: Full error messages, stack traces, and diagnostic output remain local to your machine. Telemetry records only a coarse category label describing the type of failure.
Third-Party Credentials: API keys, passwords, and tokens for third-party services are stored locally and obfuscated in logs. We do not collect or have access to your third-party credentials.

3. How We Use Information

We use collected information for the following purposes:

3.1 Service Operation

Providing, maintaining, and improving the Service
Authenticating users and managing accounts
Processing transactions and managing subscriptions
Operating the registry and community features

3.2 Service Improvement, Quotas, and Product Analytics

Measuring usage volume on a per-account basis to administer plan limits, fair-use thresholds, and quotas applicable to your subscription tier
Analyzing pseudonymous usage patterns, tied to your registered account, to understand adoption of features and stages of the Service
Identifying and fixing bugs and errors based on outcome categories and execution metrics
Developing new features based on observed usage trends across the user base

3.3 Communication

Sending service-related notices (security alerts, maintenance windows, account notifications)
Responding to support requests and inquiries
Sending product updates and announcements (with opt-out available)

3.4 Safety and Compliance

Detecting, preventing, and addressing fraud, abuse, or security incidents
Enforcing our Terms of Service
Complying with legal obligations

We do not sell your personal information. We may share information in the following limited circumstances:

4.1 Service Providers

We share information with third-party vendors who perform services on our behalf (e.g., hosting, payment processing, analytics), subject to confidentiality obligations. Current and planned service providers include:

Cloudflare: Website hosting, content delivery, security, and serverless request processing
Plausible Analytics: Privacy-preserving, aggregate website analytics
Resend: Delivery of website sales inquiries and transactional email
Supabase: Authentication and database services for account and product features
Stripe: Payment processing for paid subscriptions when checkout is available

Not every provider processes information during every visit. Supabase is involved when you use an account or hosted product feature; Stripe is involved when you begin or manage a paid transaction.

4.2 Registry Content

If you publish adapters, skills, or flows to the public registry, your author name and contribution metadata are publicly visible. Do not include personal information in registry content.

4.3 Legal Requirements

We may disclose information if required by law, legal process, or government request, or if we believe in good faith that disclosure is necessary to protect rights, safety, or property.

4.4 Business Transfers

In the event of a merger, acquisition, or sale of assets, user information may be transferred as part of the transaction. We will notify affected users before their information becomes subject to a different privacy policy.

We may share information for purposes not described in this Policy with your explicit consent.

5. Data Storage and Security

5.1 Local-First Architecture

Rote is designed with a local-first architecture:

Workspace data (cached API responses, workflow state, command history) is stored on your local machine and is not transmitted to Modiqo.
Authentication tokens for third-party services are stored locally and obfuscated in logs.
Cloud features (registry, sync, vault, and telemetry of the kind described in Section 2.2) transmit only the specific data required for those features. Pseudonymous telemetry events, when enabled, are transmitted to telemetry-ingestion infrastructure operated by or on behalf of Modiqo.

5.2 Security Measures

We implement industry-standard security measures including:

Encryption of data in transit (TLS 1.2+)
Encryption of data at rest for cloud-stored information
Access controls and authentication mechanisms
Regular security reviews
Header obfuscation for sensitive values (Authorization, API keys, tokens)

5.3 Data Retention

Account data: Retained while your account is active and for a reasonable period after deletion to comply with legal obligations.
Usage telemetry — raw events: Pseudonymous telemetry events tied to your registered account or installation identifier are retained for no more than ninety (90) days, after which they are deleted or reduced to aggregated form that no longer references your account.
Usage telemetry — aggregated metrics: Aggregated and statistical metrics derived from telemetry, which do not identify any individual account, may be retained indefinitely for product-improvement and historical-trend purposes.
Log data: Server logs are retained for up to twelve (12) months.
Website analytics: Aggregate website analytics are retained according to the retention period configured for our Plausible subscription. They do not contain the personal identifiers prohibited by Section 2.2. We review the configuration at least annually and may delete analytics earlier when no longer needed.
Sales inquiries: Sales-form submissions and the resulting email are retained only as long as reasonably necessary to respond, manage the prospective business relationship, and meet legal or security obligations. You may ask us to delete an inquiry by contacting [email protected].
Local data: Workspace data stored on your machine is under your control. You may delete it at any time using the storage-management facilities provided by the Service.

5.4 Beta Data Practices

During the beta period:

Data practices may evolve as the Service matures.
We may collect additional diagnostic data (with notice) to improve stability and performance.
We will notify users of material changes to data collection practices.
Beta participants may be asked to share anonymized usage data to help improve the Service. Participation is voluntary.

6. Your Rights and Choices

6.1 Access and Portability

You may request a copy of the personal information we hold about you by contacting [email protected].

6.2 Correction

You may update or correct your account information through the Service or by contacting us.

6.3 Deletion

You may request deletion of your account and associated personal data by contacting [email protected]. We will process deletion requests within 30 days, subject to legal retention requirements. Note that:

Local data is under your control and not affected by account deletion.
Registry contributions published under Apache 2.0 may persist as they are independently licensed.
Pseudonymous telemetry events that reference your registered account identifier will be deleted or severed from your account upon deletion, in accordance with the retention periods set out in Section 5.3.
Aggregated and statistical metrics that do not identify you may be retained.

6.4 Opt-Out of Telemetry

You may opt out of telemetry collection and upload at any time through the telemetry-control facilities provided by the Service, including a dedicated configuration command and recognized environment variables (such as the industry-standard "Do Not Track" signal). When you opt out, no further telemetry events are recorded locally or transmitted to Modiqo.

Essential operational data necessary to maintain service functionality and security — for example, authentication requests to your account, enforcement of subscription quotas, and records required for billing or to comply with legal obligations — may still be collected while your account remains active.

6.5 Communication Preferences

You may opt out of non-essential communications by using the unsubscribe link in any marketing email or by contacting us. Service-related notices (security alerts, account notifications) cannot be opted out of while your account is active.

7. International Data Transfers

Your information may be transferred to and processed in the United States, where our servers and operations are located. By using the Service, you consent to the transfer of your information to the United States. We take reasonable steps to ensure your information receives adequate protection in accordance with this Policy regardless of where it is processed.

8. Children's Privacy

The Service is not directed to individuals under the age of 18 (or the age of majority in your jurisdiction). We do not knowingly collect personal information from children. If we become aware that we have collected information from a child, we will take steps to delete it promptly. If you believe a child has provided us with personal information, please contact us at [email protected].

9. Third-Party Services

The Service enables connections to third-party APIs and MCP servers (e.g., GitHub, Gmail, Slack, Stripe). This Policy does not apply to information collected by third-party services. We encourage you to review the privacy policies of any third-party services you connect through rote. Modiqo is not responsible for the privacy practices of third-party services.

10. Google API Services — Limited Use Disclosure

Rote's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

10.1 What Google Data We Access

When you connect Google services to the Service, you select which Google API scopes to authorize. Rote may access:

Gmail API (gmail.readonly, gmail.compose, gmail.send) — Email metadata and content, for user-initiated actions such as reading, composing, and sending email through automation flows.
Google Calendar API (calendar) — Calendar events and scheduling data, for user-initiated actions such as viewing schedules and creating events.
Google Docs API (documents) — Document content and metadata, for user-initiated actions such as reading, summarizing, and creating documents.
Google Sheets API (spreadsheets) — Spreadsheet content and metadata, for user-initiated actions such as reading data and updating cells.

Rote only requests the scopes you explicitly select during setup. You are never required to authorize all scopes.

10.2 How Google Data Is Used

Google user data is used solely to execute the automation flows you explicitly initiate. Specifically:

Data retrieved from Google APIs is processed locally on your machine to fulfill your requested action (for example, retrieving your unread email or creating a calendar event).
The content of Google API requests and responses is not transmitted to Modiqo servers, and is not included in the pseudonymous usage telemetry described in Section 2.2.
Google data is not used for advertising, data mining, or profiling.
Google data is not shared with third parties except as necessary to provide the Service functionality you requested.

10.3 How Google Data Is Stored

OAuth tokens (access tokens, refresh tokens) for Google services are stored locally on your machine, encrypted at rest using a machine-bound key.
Google API response data (emails, calendar events, documents) is cached locally in your rote workspace for the duration of your session. Cached data may be cleared at any time through the storage-management facilities provided by the Service.
No Google user data is stored on Modiqo's servers.

10.4 How Google Data Is Shared

Google user data is not shared with any third party. All processing occurs locally on your device. Modiqo does not have access to your Google data at any point.

10.5 Token Revocation

You may revoke rote's access to your Google account at any time, either through the token-management facilities provided by the Service or by visiting your Google Account Permissions page and removing rote from the list of apps with access.

Upon revocation, all locally stored OAuth tokens for Google services are deleted. Cached Google API response data in your workspace may be removed through the storage-management facilities provided by the Service.

11. Cookies and Tracking

11.1 Website

Our public websites currently use Plausible Analytics without analytics cookies, local-storage identifiers, cross-site tracking, or advertising profiles. Plausible's default measurement derives a short-lived, daily-changing identifier to calculate aggregate visitor counts; Modiqo does not receive or store a persistent visitor identifier from Plausible.

The website may use local or session storage for visitor-requested preferences, such as theme and documentation-navigation state. These values are not used for advertising or cross-site tracking. Account authentication and checkout may use storage that is necessary to keep a user signed in, secure a requested transaction, prevent fraud, or remember a requested preference when those features are enabled.

Because the current analytics configuration is cookieless and does not use persistent identifiers, we do not display an analytics-consent banner solely for Plausible. We will reassess this approach before adding advertising technology, session replay, persistent browser identifiers, non-essential personalization, or any other technology that requires consent under applicable law. This disclosure describes our current implementation and is not a waiver of rights available under applicable privacy law.

11.2 CLI Tool

The rote CLI does not use cookies. Telemetry data collection is described in Section 2.2.

12. California Privacy Rights (CCPA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act:

Right to Know: You may request information about the categories and specific pieces of personal information we have collected.
Right to Delete: You may request deletion of your personal information.
Right to Opt-Out of Sale: We do not sell personal information.
Non-Discrimination: We will not discriminate against you for exercising your CCPA rights.

To exercise these rights, contact [email protected].

If you are in the European Economic Area, United Kingdom, or Switzerland, you have additional rights under the General Data Protection Regulation:

Legal Basis: We process personal data based on consent, contract performance, legitimate interests, or legal obligations.
Rights: You have the right to access, rectify, erase, restrict processing, data portability, and object to processing.
Data Protection Officer: For GDPR-related inquiries, contact [email protected].
Supervisory Authority: You have the right to lodge a complaint with your local data protection authority.

14. Disclaimer of Liability

14.1 Beta Service

THE SERVICE IS PROVIDED IN BETA ON AN "AS IS" AND "AS AVAILABLE" BASIS. WHILE WE IMPLEMENT REASONABLE SECURITY MEASURES, WE CANNOT GUARANTEE THAT THE SERVICE WILL BE FREE FROM SECURITY VULNERABILITIES, DATA BREACHES, OR ERRORS DURING THE BETA PERIOD.

14.2 Local Data

You are solely responsible for the security and backup of data stored locally on your machine, including workspace data, cached responses, and authentication tokens. Modiqo is not responsible for loss or compromise of locally stored data.

14.3 Third-Party Services

Modiqo is not responsible for the data practices, security, or privacy of third-party services accessed through rote. Your use of third-party services is governed by their respective privacy policies and terms.

14.4 Community Content

Registry contributions from third-party authors may collect, process, or transmit data in ways not controlled by Modiqo. You are responsible for reviewing community content before use. Modiqo is not liable for data handling by community-created adapters, skills, or flows.

15. Changes to This Policy

We may update this Policy from time to time. We will notify you of material changes by:

Posting the updated Policy with a revised "Last Updated" date
Sending notice through the Service or via email for material changes

Your continued use of the Service after notification constitutes acceptance of the updated Policy. If you do not agree with the changes, you must stop using the Service.

16. Contact Information

For questions, concerns, or requests regarding this Privacy Policy:

Modiqo Inc. Email: [email protected] General Support: [email protected] Legal: [email protected] Website: https://modiqo.ai Product: https://rote.dev