Privacy Policy

SECTION 01

Who This Policy Applies To

This policy applies to individuals who purchase or use a Vexo Band and the Vexo App, visitors to our Site, and developers who build on the Vexo platform. If you are under the age of 16 (or the minimum age of digital consent in your jurisdiction), you may not use the Services, and we do not knowingly collect data from you (see Section 12).

SECTION 02

The Short Version

The essentials at a glance. The rest of this document is the long version.

Voice

Captured by the Band while listening is on, including the conversations around you, or by a phone microphone feature you enable. You can stop listening at any time with the Band's button, by saying "Vexo, stop listening", or in the App. Audio is sent to a cloud speech provider for transcription. Transcripts may be synced to your Vexo account and used by the assistant.

Your phone's mic

Phone voice features use microphone permission when needed. You can control this permission in your phone's settings.

Advertising and your data

We never sell or use your conversations or connected-account data for advertising. The Site separately shares limited browsing information with X and Meta for advertising in supported regions, and tells Meta about orders. You can opt out.

Sharing you approve

External assistants and connected apps receive your Vexo data only after you authorize access and only within the permissions you approve. You can revoke access.

Providers that operate Vexo

Hosting, authentication, email, cloud AI and speech providers process data to operate Vexo and deliver enabled features. Site and App analytics are described below. Google data has the additional Limited Use restrictions below.

Analytics / trackers

The App collects product analytics (screens, taps, feature use and app errors). The Band and App contain no advertising SDKs. The Site uses product analytics and privacy-masked session replay. Separately, selected marketing pages use the X and Meta advertising pixels in supported regions, subject to your privacy choices.

SECTION 03

The Information We Collect

Voice & Speech Information

The Band includes a microphone that listens continuously while listening is on. While it is listening, it hears the conversations around you, including what other people say, not only your own speech. You can stop it at any time: press the Band's button, say "Vexo, stop listening", or tap stop in the App. Press the button again to start. You can delete any conversation, or your whole account, in the App (see Section 9).

How your voice is handled. Please read this carefully:

• Audio from the Band reaches your phone over Bluetooth. Features such as phone voice input may instead use your phone's microphone with microphone permission.
• Transcription streams Band audio from your phone to our speech provider, AssemblyAI, which returns text. Speaker-separation features may also stream audio to pyannoteAI.
• Speech providers process audio outside your phone under their processing and retention terms. To stop audio leaving your phone, press the Band's button to stop listening.
• The resulting text transcript may be stored on your phone, synced to your Vexo account, and provided to our cloud AI service to answer your requests or prepare notes and actions.

Recording others. Because the Band hears the people around you while it is listening, you are responsible for complying with applicable laws when recording. Some jurisdictions require the consent of all parties to a conversation before recording ("two-party" or "all-party" consent). You must obtain any consent required by law before recording other people, and you must not use Vexo to record anyone unlawfully. Stop listening wherever recording is not allowed.

Profile Information You Provide

When you set up the App, you may provide your name / display name and preferences for how you use Vexo.

Memories, People, Preferences, and Saved Records

Vexo processes synced transcripts and saved notes to organize your history and answer questions. It can derive facts, summaries, preferences, people and other entities, topics, commitments, and reminders. Derived information can be incomplete or incorrect. It is not an independently verified record.

• Conversation content and people: spoken words, quotations, speaker labels, names, aliases, relationships, and descriptions of people or other entities mentioned in your records.
• Memories and preferences: factual statements, supporting excerpts, subjects, topics, daily narratives, preference names, values, and categories.
• Commitments, notes, and reminders: titles, saved text, structured summaries, original spoken requests, counterparties, task status, due dates, schedules, recurrence settings, and completion information. Structured summaries can contain nested fields from the saved record.
• Context and source information: record identifiers, dates, times, timezones, update times, source types, speaker attribution, and confidence estimates. These help retrieve records, distinguish sources, and interpret their meaning and timing.

Your recordings and saved content can contain contact details or sensitive information about you or other people. Such information can also appear in derived memories and responses to an assistant you authorize. This differs from importing your phone's contacts or tracking its location.

Account & Identity Information

To create and secure your account (via our authentication provider), we collect your email address (and one-time verification codes), your phone number if you use SMS sign-in, your Apple account identifier if you use Sign in with Apple, your Google account identifier if you use Google sign-in, and authentication tokens stored securely in your device's Keychain.

We do not receive your Apple or Google password. If you use Sign in with Apple, Apple may provide us a private relay email address rather than your real one, at your choice.

Connected Google Accounts: Gmail and Google Calendar

Connecting a Google account is optional and separate from signing in to Vexo. Google shows the permissions requested before you authorize a connector. We receive OAuth access and refresh tokens, not your Google password. Vexo stores these credentials encrypted and refreshes them only to provide the features you enable. Some connections are held for us by our connection service, Nango, under the same restrictions; we are moving Google connections onto Vexo's own servers.

• Gmail: read access lets Vexo find and read messages needed for inbox assistance, summaries, and answers. Send access lets the assistant send an email only when you explicitly ask it to send that email; it shows you the text first. Vexo does not create or edit drafts in your Gmail. Data can include subjects, participants, dates, message content, and the emails you ask Vexo to send, depending on the feature used.
• Gmail onboarding: after you connect Gmail in this flow, Vexo immediately reads a sample of recent subjects, senders, recipients, dates, and message/thread identifiers to suggest three opening questions and tentative context. This step reads up to 60 distinct threads from the past 90 days and does not fetch message bodies, snippets, or attachments. Relevant metadata is processed by our AI provider. These suggestions can be incomplete or wrong and are not verified facts about you.
• Google Calendar: read access supports schedule and availability questions; event access supports creating or updating events at your request. Data may include calendar names and event titles, dates, times, descriptions, and participants.

We use Google user data only to provide and improve the user-facing features described above, which you choose to use in the App. We do not use it for any other purpose. In particular, we do not use Google user data for advertising, marketing, analytics, user research, or to determine credit-worthiness, and we do not sell it. Relevant Google data and results may pass through our backend, hosting and connection infrastructure, and AI service providers. We do not use Google data for advertising, sell it, or use it to develop, improve, or train generalized AI or machine-learning models. Providers processing it on our behalf must follow these same restrictions. Our AI providers process Google user data only to answer your request, under terms that do not allow them to use it to train their models. Google user data is encrypted in transit (TLS) and at rest, OAuth tokens are stored encrypted, and access is limited to the systems that run the features you use.

Vexo's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. We transfer Google user data only as needed to provide or improve these features, for security purposes, or to comply with applicable law. Humans can read Google user data only with your explicit agreement for specific data, when needed for security purposes such as investigating abuse, or to comply with applicable law.

Band Device Information

To operate and maintain your Band, we collect its serial number and hardware identifiers, firmware version, battery level, and connection timestamps. The Band itself stores only its own settings; it does not retain a history of your voice data. Your phone is the primary store.

Reminders

If, and only if, you tap to route a note into Apple Reminders, the App requests access to your Reminders and writes the item you selected. We do not read your existing reminders and do not access this data on our servers.

Information Collected With Your Permission

With your permission, the App may also collect:

• Approximate location. If you allow location access, the App sends your approximate location and place name with your requests so Vexo can answer questions about places near you. You can turn location off in your phone's settings.
• Contacts. If you allow contacts access and choose to sync, names, phone numbers and email addresses are saved to your Vexo account to recognize names and find recipients.
• Photos. Images you choose to share with Vexo.
• App errors. Error reports that help us fix crashes, sent to our analytics provider.

Information We Do Not Collect

For clarity, the current Services do not collect:

• Phone microphone audio without microphone permission.
• Advertising identifiers. The Band and App embed no advertising SDKs.

The Site

Our marketing and developer-documentation website uses analytics to understand page visits, referral and campaign attribution, clicks, scroll depth, product and checkout interactions, performance, and errors. We also use session replay, which records how pages render and how visitors interact with them. We mask all form inputs in replay, do not record payment pages hosted by Stripe, and mask checkout-session identifiers in captured URLs. The Site uses a first-party cookie and browser storage to maintain an anonymous visitor and session identifier. We do not use product analytics or session replay for advertising or combine them with voice data. The separate X and Meta advertising pixels are described below. Standard server logs may also be generated by our hosting provider for security and reliability.

Site Advertising and Your Choices

Selected marketing pages use the X pixel to build audiences of Site visitors and show them Vexo ads on X. X receives browser and cookie identifiers, an IP address, device information and visits to those pages. We send only the page path, without query strings or fragments. We disable automatic form matching and do not send your email address, payment details, conversations or connected-account data to X. We do not load this pixel on payment confirmation pages or privacy-choice pages.

Selected marketing pages also use the Meta pixel to show Vexo ads to Site visitors on Facebook and Instagram and to measure those ads. Meta receives browser and cookie identifiers, an IP address, device information, the page address including ad campaign parameters, and two product events: viewing the Band and starting checkout. We turn off Meta's automatic event setup and do not load the Meta pixel on payment confirmation pages or privacy-choice pages.

When you place an order from a browser where advertising tracking is allowed, our server tells Meta about the purchase after payment is confirmed. We send the order value and currency, a hashed copy of your email address, your billing country and postal code (also hashed), your browser's user agent and Meta's cookie identifiers. Hashing turns each value into a fixed code that Meta can match to its own records. We do not send your name, shipping address, payment details, conversations or connected-account data to Meta.

These pixels operate in the United States, Australia and supported Canadian provinces and territories outside Quebec. Other countries, Quebec and locations we cannot identify remain excluded. We determine the region from our hosting provider's IP-based country and province information. The page remains usable if you opt out or block the pixels.

To stop X and Meta advertising tracking on this browser, including purchase reports to Meta, use Do Not Sell or Share My Personal Information in the footer. We honor Global Privacy Control and Do Not Track signals. We save your opt-out in browser storage and a first-party cookie that lasts one year. Repeat your choice on other browsers or after clearing storage. X and Meta may process information outside your country under their own privacy policies (X, Meta). You can also use X's advertising privacy controls and Meta's ad preferences.

Launch Updates

If you sign up for launch updates on the Site, we collect the email address you enter and use it only to email you about the Vexo Band launch. Our email provider, Resend, delivers your sign-up to our inbox. We count sign-ups in our Site analytics without recording your email address. To unsubscribe or have your address deleted, email support@vexoai.com.

SECTION 04

How Your Data Flows (Band → Phone → Cloud)

Understanding the architecture is the best way to understand your privacy:

• On the Band. The microphone listens while listening is on, as described above. The Band transmits over Bluetooth to your paired phone and stores no history.
• On your phone. The App receives wearable data, displays your information, and handles local processing. It also streams audio to our speech provider for transcription. Some features may buffer audio on-device while processing.
• In the cloud. Our services store synced account data and process enabled assistant features. Connected Google data passes through Vexo's backend and, for some connections, our Nango connection service; the data relevant to a request may also be sent to our AI provider. These services are subject to access controls and the use restrictions in this policy.

SECTION 05

How We Use Your Information

We use your information to:

• Provide the core Services: organize your transcripts, memories, notes and reminders; generate summaries and assistant responses using local or cloud processing as applicable; and carry out connected-account actions you request.
• Sync and back up your data to your account so you don't lose it.
• Operate your Band: manage pairing, firmware updates, and battery/connection status.
• Authenticate and secure your account and detect abuse or fraud.
• Communicate with you about your account, security, and material changes, and send launch updates if you sign up for them.
• Comply with law and enforce our terms.

We do not sell or use your conversations or connected-account data to build advertising profiles. The Site separately uses limited browsing and purchase information for X and Meta advertising, as described above. You can opt out of this sharing.

Google user data you connect (Gmail and Google Calendar) is used only as described in Connected Google Accounts above. The communication, Site improvement, and analytics purposes listed here never apply to it.

SECTION 06

Legal Bases for Processing (EEA/UK Users)

Where GDPR or UK GDPR applies, we rely on the following legal bases:

• Consent (Art. 6(1)(a)): for voice-derived transcripts, launch-update emails you sign up for, and any sharing you initiate. You may withdraw consent at any time (Section 9).
• Contract (Art. 6(1)(b)): to provide the Services you request.
• Legitimate interests (Art. 6(1)(f)): to secure our Services, understand Site usage, improve Site usability and conversion (never using Google user data), diagnose technical issues, and prevent abuse, balanced against your rights.
• Legal obligation (Art. 6(1)(c)): to comply with applicable law.

SECTION 07

Who Can Access Your Information

You choose which external assistants and apps can access your Vexo data. They receive access only after you approve a connection and only within the permissions you grant. You can revoke access. Providers that operate Vexo and limited legal or business disclosures are described separately below.

Providers That Operate Vexo

We use service providers for database, authentication, storage, and backend hosting. Our Nango connection service manages OAuth connections and authenticated requests to connected services. Cloud AI features use Anthropic, directly or through Amazon Bedrock, to process relevant prompts, context, and tool results. Speech features use AssemblyAI and pyannoteAI as described above. An analytics service provider processes Site and App product analytics and privacy-masked session replay. Resend delivers launch-update sign-ups from the Site to our inbox. Authentication codes may be delivered through our authentication provider's email or SMS services. We share only data needed for the enabled service. Separately, the Site uses X for website advertising in supported regions, as described in the Site advertising section.

Sharing You Initiate: External AI Assistants (MCP)

Vexo lets you connect an external AI assistant through the Model Context Protocol (MCP) and OAuth sign-in. Examples include Claude, ChatGPT, and Meta's Muse. When you approve a connection, the assistant receives read-only access to your transcripts, memories, people, preferences, commitments, saved notes, and reminders.

• This happens only when you turn it on. It is off by default.
• An assistant only ever sees your own account, and only within the permission you approve (today, read-only `vexo:read`). Technical details for developers are at vexoai.com/developers/mcp.
• The shared server URL is not a credential. The assistant receives access tokens after authorization; it does not receive your Vexo sign-in code or your Apple or Google password.
• You can disconnect an assistant in Vexo settings, which revokes future reads. Disconnecting does not remove copies already returned to that assistant.
• Once your data reaches a third-party assistant, its handling is governed by that provider's privacy policy, not ours. Older personal connection links, where still enabled, remain credentials and can be disabled in the App; keep them private.

What MCP Requests and Responses Can Contain

We process the assistant's search text, requested dates, timezone, source references, and page cursors to retrieve your records. Tools can search records, return context, fetch a source, list transcript days, or read and search transcripts. Depending on the tool and available records, responses can contain the categories below.

• Record content: transcript text, excerpts, derived translations, memory statements, supporting evidence, summaries, preferences, and saved notes or reminders. Responses can include complete structured summaries, including nested fields, and quotations from the source.
• People and relationships: names, aliases, speaker labels, subjects, people mentioned, and commitment counterparties. These support questions about who said something, a particular person, or a commitment involving that person. Contact details or other personal information can appear when present in the underlying content.
• Timing and meaning: conversation dates and times, timezones, record and update times, due dates, and dates when a fact or commitment starts or ends. Responses can also include topics, preference categories, status, direction of a commitment, modality, and confidence estimates. Modality describes whether a statement records an intention, possibility, or another form of expression. These fields help interpret chronology, attribution, and uncertainty.
• Source references and pagination: source identifiers, titles, URLs, source types, content versions, page numbers, and references to earlier or later pages. References can encode an internal record identifier, a date or text position, a content version, and a page number. They support citations, source retrieval, checks for changed content, and continuation through long records. They are not anonymous identifiers or authorization credentials; source retrieval still requires account authorization.
• Service status and diagnostic metadata: response dates, latest transcript dates and times, memory processing progress, available source categories, and whether semantic search is enabled. Semantic search finds content by meaning. Responses can include record counts, date ranges, timezone settings, search availability, recent-record fallback status, and pagination or truncation indicators. They can also identify unavailable sources, partial results, response size limits, and guidance about evidence. These fields describe search coverage, freshness, and limitations.

These disclosures cover information in response text, structured results, and nested metadata. The context tool can also return recent conversation excerpts and background memories, such as preferences, people, and open commitments. This background supports continuity and can extend beyond records that directly match the search text.

The MCP retrieval tools do not return your authentication profile as a separate record. Account credentials are not included as response metadata. However, information spoken or saved in your content can appear in returned excerpts. Review the receiving assistant provider's privacy policy before connecting it.

Sharing You Initiate: Marketplace Apps

Third-party "mini-apps" may request scoped, revocable access to specific data categories (such as transcripts and saved notes). Access is deny-by-default: an app receives only the scopes you approve, and you can revoke them. These features operate only on your explicit, per-grant consent.

Apple Reminders

We write to Apple Reminders only when you explicitly route a note there.

Legal & Safety

We may disclose information if required by law, subpoena, or legal process, or where we believe in good faith it is necessary to protect the rights, safety, or property of you, us, or others.

Business Transfers

If Vexo is involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction. We will notify you and honor the commitments in this policy.

We do not sell personal information for money. Sharing Site identifiers and browsing activity with X and Meta, and purchase information with Meta, for targeted advertising may be considered a sale or sharing for cross-context behavioral advertising under U.S. state privacy laws. You can stop this sharing through Do Not Sell or Share My Personal Information. Your conversations and connected-account data are excluded.

SECTION 08

Data Retention

• Synced transcripts, memories, notes, reminders, profile information, and device data is retained in your account until you delete the specific data, delete your account, or request deletion, so your history stays available across devices.
• Local app data, including any buffered audio, can be removed by clearing the App's data or deleting the App. This does not by itself delete synced account data or data already processed by a cloud provider.
• MCP responses held by an external assistant: the receiving provider controls retention of copies it receives, including content and metadata. Disconnecting Vexo prevents future reads through that connection. It does not delete copies already held by the provider. Use that provider's controls or contact it to request deletion of those copies.
• Google connections and derived results: credentials are retained while a connection is active. Disconnecting removes that connection's stored credentials and stops future Vexo access through it. Stored assistant conversations, notes, or files you chose to create may remain until you delete them or request deletion. Gmail onboarding context is cleared when its Vexo connection is disconnected.
• Site and App analytics and session replays are retained according to our configured analytics retention periods and are not joined to voice data.
• Launch-update email addresses are kept until you unsubscribe or ask us to delete them.
• We retain limited records as required to comply with legal obligations, resolve disputes, and enforce agreements.

SECTION 09

Your Rights & Choices

Depending on where you live, you may have rights to access, correct, delete, export/port, restrict, or object to processing, and to withdraw consent. Vexo honors these rights for all users regardless of location, to the extent practicable.

You can exercise many of these directly:

• Access / view: your data is visible in the App.
• Correct: edit your profile in the App.
• Disconnect external AI access: revoke the assistant connection in Vexo settings, or disable an older personal connection link.
• Disconnect Google: use the connector controls in Vexo or remove Vexo's access in your Google Account connections. Revocation stops new access after it takes effect; it does not automatically erase prior assistant results. Contact us to request deletion of retained Google data or derived results.
• Revoke app grants: manage scoped permissions in the App.
• Stop collection: press the Band's button, say "Vexo, stop listening", or tap stop in the App. You can also power down or unpair the Band, and revoke Bluetooth, microphone, speech, or other permissions in your phone's settings.
• Site analytics: enable your browser's Do Not Track setting; our Site is configured to honor it. You may also contact us to exercise applicable rights over Site analytics data.
• Site advertising: use Your Privacy Choices to stop sharing with X and Meta. Global Privacy Control and Do Not Track also disable both pixels and purchase reports to Meta.
• Delete your account: use Delete account in the App's settings. This deletes your synced transcripts, memories, notes, reminders, profile information, and device data. You can also email us to request deletion.
• Export your data: email us and we will provide a copy on request.

To make a rights request, email support@vexoai.com. We will verify your identity (typically by confirming control of your account email) before acting, and respond within the timeframe required by applicable law (generally 30 to 45 days). You will not be discriminated against for exercising your rights.

California residents (CCPA/CPRA): You have the rights to know, delete, correct, and to limit the use of sensitive personal information. We use sensitive information only to provide the Services and do not use it to infer characteristics for advertising. You can opt out of the Site advertising sharing described above through Your Privacy Choices. We honor Global Privacy Control signals.

EEA/UK residents: You may also lodge a complaint with your local data protection authority. Authorized agents may submit requests on your behalf with proof of authorization.

SECTION 10

Security

We protect your information with technical and organizational measures, including:

• Encryption in transit (TLS/HTTPS) between the App and our backend, and secure Bluetooth between the Band and your phone.
• Encryption at rest for account data stored in our cloud database, including transcripts, memories, notes and reminders, and for its backups.
• Per-user access controls (row-level security) so each account's data is isolated and readable only by that account and services it authorizes.
• Secure credential storage: mobile authentication uses platform secure storage; server-side secrets and OAuth credentials are access-controlled.
• Purpose-limited processing: connected-account data is used for the features you enable. Gmail onboarding reads a bounded set of message metadata rather than message bodies or attachments.
• Access logging with redaction of sensitive fields such as tokens and transcript text.

No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and regulators as required by law.

SECTION 11

International Data Transfers

Some features involve international data transfers. Where required, we use appropriate safeguards, such as the European Commission's Standard Contractual Clauses. You can request information about these safeguards using the contact details below.

SECTION 12

Children's Privacy

The Services are not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child has provided us information, email support@vexoai.com and we will delete it.

SECTION 13

Third-Party Services

The Services integrate with Apple, Google (including Gmail and Google Calendar when you connect them), and external assistants or apps you choose. Your direct use of third-party services is subject to their terms and privacy policies. Our handling of Google user data remains subject to the Google Limited Use commitments in this policy.

SECTION 14

Changes to This Policy

We may update this policy from time to time. If we make material changes (for example, to the categories of data we collect or how we share it), we will notify you through the App or by email before the change takes effect, and we will update the "Last updated" date. Your continued use of the Services after an update means you accept the revised policy.

SECTION 15

Contact Us

If you have questions, requests, or complaints about this policy or your data, contact us:

Vexo: email support@vexoai.com