BETA privacy

OneMind BETA Privacy Policy

This policy explains how OneMind handles information during the public BETA across our website, apps, accounts, team Mind, AI connections, billing, and related test services.

Last updated: August 25, 2026

Who is responsible

This policy applies to onemind.team, OneMind apps and command-line tools, and the hosted OneMind BETA service. OneMind is responsible for account, service, security, and direct-contact information processed for the BETA. A customer organization may separately control content its members place in a shared workspace; OneMind then processes that content to provide the service, and the team administrator is normally the first contact for workspace-content requests.

Information we collect

  • Account and authentication information: email address, login name, display name, team, role, password verifier, session and invitation records, and email-verification status.
  • Google sign-in information: Google's stable account identifier (sub), email address and verification status, and display name when Google provides it. OneMind does not receive your Google password.
  • Team and service content: shared Mind content, proposals, project information, Mind files and paths, comments or decisions, notifications, and related version or activity records that you or your team submit.
  • AI connection information: provider name, API origin, model, encrypted API credential, consent settings, and limited run metadata such as source type, source count, status, and error code.
  • Billing information: Paddle customer and subscription identifiers, plan or price identifier, seat quantity, subscription status, billing-period dates, scheduled changes, and billing-event metadata. Paddle, as Merchant of Record, receives and processes payment details, tax information, receipts, and refund information under its own privacy terms; OneMind does not store complete payment-card details.
  • Device and operational information: device name, platform and architecture used for device authorization; timestamps; security, audit, rate-limit, and diagnostic records; and IP address where needed to protect forms and authentication.
  • Waitlist and contact information: information you choose to submit, such as your name, email, phone number, company, role, team size, use case, and message.

BETA testing and diagnostics

Because OneMind is an incomplete BETA, we may use service events, error codes, feature usage, compatibility information, support reports, and limited diagnostic records to reproduce defects, protect users, and decide what to improve or discontinue. Authorized personnel may review these records and, only when reasonably necessary to investigate a reported problem, related account or workspace information. Do not place production secrets, regulated data, highly sensitive personal information, or irreplaceable records in the BETA.

Purposes and legal bases

We process information as needed to perform our contract by providing accounts, workspaces, storage, synchronization, requested AI analysis, subscriptions, and support. We process security, audit, capacity, reliability, product-improvement, and fraud-prevention information for our legitimate interests in operating and protecting the service, balanced against user rights. We process information where you give consent, including optional AI connections, and where necessary to comply with law, accounting requirements, or valid legal process. You may withdraw consent without affecting processing already carried out, although a feature that depends on that information may stop working.

AI services and user-configured providers

When you enable analysis and request or authorize it, OneMind may send the selected source material, instructions, and necessary context to the AI provider and endpoint configured for your account. That provider processes the request under its own terms and privacy policy. OneMind encrypts stored provider API credentials and does not return the raw credential after it is saved. Do not connect a provider or submit content unless you are authorized to do so.

Google sign-in data flow

Google receives browser requests needed to display its official sign-in control and authenticate the account you select. OneMind verifies the resulting credential for its configured OAuth client and uses the stable Google account identifier—not an email address alone—to recognize a linked identity. This sign-in flow does not request access to Google Drive, Gmail, Calendar, or other Google product data, and OneMind does not send project or shared Mind content to Google through the sign-in flow.

How information is shared

OneMind does not sell personal information, does not sell Google sign-in information, and does not use Google sign-in information for advertising. Information may be shared with authorized members and administrators of your team; hosting, database, delivery, security, and email providers including Alibaba Cloud services used to operate OneMind; Google for the sign-in flow; Paddle for orders and subscriptions; an AI provider and endpoint only when you configure and authorize that connection; professional advisers under confidentiality duties; a successor in a business transfer; or authorities when disclosure is legally required or reasonably necessary to protect people and the service. Each provider receives only the information reasonably needed for its role and is subject to its own terms and applicable data-protection duties.

Product analytics, VibeLoft telemetry, cookies, and local storage

OneMind uses authentication state and browser storage to keep you signed in, remember interface preferences, protect sessions, and provide requested features. We also use privacy-minimized first-party product analytics to understand page views, unique visitors, sessions, interface-language mix, and which normalized pages are used. The browser creates random visitor and session identifiers; the visitor identifier rotates every 30 days. OneMind hashes those identifiers on receipt and stores only the normalized route, interface language, category, and server receipt time. In this first-party system, analytics events do not store an IP address, user agent, query string, account identity, or customer content, and raw events are removed after 400 days. Aggregated daily reports are emailed only to the configured OneMind development recipient. Separately, OneMind loads VibeLoft's origin-bound public-page telemetry only on anonymous public pages at the exact origin https://onemind.team. VibeLoft uses anonymous device and IP identifiers to deduplicate visits daily and does not use browser fingerprinting. OneMind does not receive VibeLoft's deduplication identifiers. When the browser sends a Do Not Track (DNT) signal, OneMind disables its first-party analytics and does not load VibeLoft. OneMind does not use data from either system for behavioral advertising.

Retention and deletion

We retain account and subscription information while the account or commercial relationship is active. Workspace content remains until an authorized user deletes it or the workspace is closed. Security, audit, transaction, tax, and dispute records are retained only for the period reasonably necessary for security and applicable legal or accounting obligations. When a team administrator removes a member, OneMind revokes authentication state and deletes that member's Google identity link, saved AI credential, and analysis consent; limited inactive-account and historical team records may remain to preserve workspace integrity and meet legal obligations. Deleted information may remain temporarily in access-controlled backups until routine overwrite. We periodically review retained information and delete or de-identify it when no business or legal purpose remains.

Security

We use access controls, scoped team permissions, credential hashing or encryption, session expiration and revocation, transport security for hosted services, and audit records designed to protect information. No system is completely secure, so you remain responsible for protecting your credentials, devices, provider keys, and the content you choose to submit.

Your choices and requests

You can update certain settings, sign out, remove configured AI credentials, delete individual Mind files, and manage a paid subscription through the controls available to your role. Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, consent withdrawal, or review of a privacy complaint, and may complain to your local data-protection authority. Submit requests through the private OneMind privacy-request form; never place personal information in a public GitHub issue. We may verify your identity, explain any lawful limitation, and direct customer-controlled workspace requests to the relevant team administrator. For Paddle transaction data, contact Paddle Buyer Support.

International transfers

OneMind, Paddle, configured AI providers, and infrastructure providers may process information outside your country. Where required, we use contractual or other recognized safeguards intended to provide protection comparable to applicable law. A customer must not upload information whose transfer or processing is prohibited.

Age restriction

OneMind is a business and professional collaboration service and is not intended for anyone under 18. Do not create an account for, or submit personal information about, a child unless OneMind has expressly agreed in writing to a lawful organizational arrangement.

Data-protection contact

Use the private privacy-request form for questions, complaints, or rights requests. Requests enter OneMind's access-controlled management queue and may require identity verification before action is taken.

Changes to this policy

We may update this policy as the service changes. We will update the date above and provide additional notice when required by law. Material changes apply prospectively.