Voyager
Request early access

Voyager Privacy Policy

Effective date: August 19, 2026

Voyager is operated by Talon Global LLC and, where applicable, an affiliated Talon entity identified in an order form, subscription, app-store listing, or other customer agreement (“Voyager,” “we,” “us,” or “our”). This Privacy Policy explains how Voyager collects, uses, stores, discloses, and otherwise processes personal information when people use Voyager websites, web applications, desktop applications, mobile applications, business workspaces, personal or family experiences, integrations, communications features, automation and AI features, and related services (collectively, the “Services”).

This Policy is designed to apply across Voyager’s business and personal products. Some features and integrations described below may be optional, limited to certain plans, in development, or available only when a user or workspace administrator chooses to enable them. Voyager processes data from a connected service only when the relevant connection, permission, or feature is enabled.

1. Who is responsible for your information

For personal-account information, product telemetry, billing administration, security, support, marketing, and Voyager’s own website/app operations, Talon Global LLC or the Talon affiliate identified in your agreement generally acts as a controller or business.

For content placed in a business workspace by an organization, the organization may be the controller or business and Voyager may act as its processor, service provider, or contractor. This can include employee, customer, prospect, vendor, project, communications, file, CRM, calendar, or other workspace information. In those situations, requests concerning organization-controlled content may need to be directed to the organization.

For personal and family workspaces, Voyager generally acts as the controller for the personal information processed to provide the service.

Privacy contact: hello@voyagerhubs.com

Mailing address: 407 Lincoln Rd. Suite 6H166, Miami Beach, FL 33139, United States

2. Information we collect

Depending on the features you use, Voyager may process the following categories.

Account and identity information

Name, username, email address, phone number, profile photo, organization or household affiliation, authentication identifiers, sign-in methods, account recovery information, role, permissions, and workspace memberships.

Business and workspace information

Organization names, teams, roles, projects, work items, requests, opportunities, sales records, CRM records, relationships, notes, research, product-development information, files, records, approvals, decisions, audit information, and other content users place in Voyager.

Communications and collaboration information

Email messages and metadata, attachments, chat or collaboration messages, SMS or messaging content, call or voicemail information, meeting information, transcripts, replies, delivery events, click or access events, scheduling communications, and other communications users choose to connect, send, receive, or record through the Services.

Where Voyager records or transcribes audio, video, calls, meetings, screens, or other activity, the applicable feature must provide appropriate notice and, where required, obtain consent. Users are responsible for complying with laws that require consent from call or meeting participants.

Contacts and relationship information

Names, email addresses, phone numbers, company and job information, addresses, birthdays, notes, communication history, relationship metadata, address-book data, CRM records, and other contact information imported, synchronized, uploaded, or entered by users.

Calendar, scheduling, reminders, and task information

Calendar events, attendees, availability, meeting links, reminders, task lists, schedules, travel or appointment information, and related metadata.

Files and document information

Files, folders, filenames, metadata, permissions, document content, signatures, shared links, and related activity from Voyager or connected file-storage and document services.

Sales, marketing, and outreach information

Lead and prospect records, campaign membership, communication sequences, newsletter activity, consent and opt-out status, delivery events, email opens and clicks where enabled, replies, scheduling events, marketing attribution, source information, and evidence events associated with communications.

Billing, subscription, and financial information

Plan, subscription, invoice, payment status, billing contact, tax information, and transaction identifiers. Payment card information may be collected directly by a payment processor such as Stripe rather than by Voyager. When a user connects accounting or financial systems, Voyager may process accounting records, invoices, customers, vendors, payments, balances, tax-related records, or similar information as necessary to provide the connected feature.

Device, usage, and diagnostic information

IP address, browser type, device type, operating system, app version, device identifiers, language, time zone, logs, crash reports, performance information, authentication events, security events, page and feature usage, and similar technical information.

Location information

Approximate location derived from IP address and, where a user grants device permission, precise or background location for features that clearly require it. Voyager requests only the level of location access necessary for the selected feature.

Personal and family information

Household members, family relationships, shared lists, grocery or household information, reminders, birthdays, gifts, travel plans, appointments, school or activity schedules, package information, subscriptions, warranties, personal notes, and other information an adult user chooses to place in a personal or family workspace.

Health and wellness information

If Voyager introduces health or wellness features that connect to Apple Health, HealthKit, Android Health Connect, medical or fitness services, or user-entered health information, Voyager may process only the health or fitness data types required for the user-facing feature and only after the permissions required by the relevant platform and law are obtained. Health information is treated as sensitive information and is subject to the additional restrictions described below.

Information from connected services

When you connect a third-party account, Voyager may receive account identifiers, tokens, permissions, content, metadata, and other data the connected service makes available within the permissions you approve. Connected services may include Google, Microsoft, Apple/iCloud or CardDAV/CalDAV-compatible services, Slack, Dropbox, Box, Zoom, Meta services, WhatsApp Business, Telegram, Viber, SMS or voice providers, email delivery providers, document-signature providers, accounting services, CRM services, automation platforms, and other services users choose to connect.

Information used for AI and automation

Prompts, instructions, selected records, messages, files, calendar items, CRM data, research inputs, tool outputs, workflow state, approvals, agent actions, and resulting content may be processed to provide AI-assisted features, summarization, search, drafting, classification, recommendations, workflow automation, or user-authorized agent actions.

3. Sources of information

We collect information directly from users; from workspace administrators or other users; from connected services a user authorizes; from devices and browsers; from communications participants; from service providers; from public or commercially available sources where lawful; and from business customers that upload or synchronize information into Voyager.

Users who import or provide information about another person must have authority or a lawful basis to do so.

4. How we use information

We may use information to:

  • create, authenticate, secure, and administer accounts and workspaces;
  • provide business, personal, family, scheduling, communications, CRM, sales, marketing, project, research, product-development, file, billing, and collaboration features;
  • synchronize data with connected services at the user’s direction;
  • send, receive, route, organize, search, summarize, or analyze communications;
  • provide AI-assisted or automated user-facing features;
  • execute user-approved workflows and agent actions;
  • process subscriptions, billing, and payments;
  • provide customer support and troubleshoot problems;
  • detect fraud, abuse, security incidents, and violations of our Terms;
  • maintain logs, audit trails, provenance, and evidence events;
  • improve reliability, usability, accessibility, and performance;
  • measure product usage and understand feature adoption;
  • communicate service notices and product updates;
  • send marketing communications where permitted and honor opt-outs;
  • measure advertising and marketing performance where permitted;
  • comply with law, enforce agreements, and protect rights and safety; and
  • perform other purposes disclosed at collection or with consent.

5. Legal bases for EEA, UK, and similar jurisdictions

Where required, Voyager relies on one or more of the following legal bases:

  • Contract: processing necessary to provide the Services you request.
  • Legitimate interests: security, fraud prevention, service improvement, business administration, and certain business-to-business communications where those interests are not overridden by individual rights.
  • Consent: optional integrations, non-essential cookies or tracking, certain marketing, precise location, device permissions, health data, recording, or other processing where consent is required.
  • Legal obligation: tax, accounting, legal-process, regulatory, and compliance obligations.
  • Vital interests or public interest: only where applicable under law.

Consent may be withdrawn without affecting processing that occurred before withdrawal.

6. Google data

Google Workspace integrations

When a user connects Google Workspace features, Voyager may access or process data from services such as Gmail, Google Calendar, Google Drive, Google Contacts/People, Google Meet, Google Chat, and related Google Workspace services only for the user-facing Voyager features the user enables and only within the scopes granted.

Examples include displaying and managing email, sending user-requested messages, synchronizing calendars, showing contacts, searching or working with Drive files, displaying collaboration information, generating user-requested summaries, or coordinating work from connected Workspace data.

Voyager’s use and transfer of information received from Google Workspace APIs will adhere to the Google Workspace User Data and Developer Policy and the Google API Services User Data Policy, including the Limited Use requirements.

In particular, Google Workspace data obtained through sensitive or restricted scopes:

  • is used only to provide or improve the appropriate, visible, user-facing feature for which access was granted;
  • is not sold;
  • is not transferred to advertising platforms, data brokers, or information resellers;
  • is not used for retargeting, personalized advertising, interest-based advertising, or other advertising purposes;
  • is not used to determine creditworthiness or for lending;
  • is not used to create, train, or improve a generalized machine-learning or artificial-intelligence model. It may be used only as permitted for the specific user’s personalized, user-facing feature;
  • is not made available for human review except with the user’s explicit permission for the specific content, where necessary for security or abuse investigation, where law requires it, or where otherwise expressly permitted by Google policy;
  • is protected using appropriate security measures; and
  • is deleted, disconnected, or access is revoked when required by the user, the connected-service lifecycle, law, or Google policy.

Users can disconnect Google access through Voyager when the relevant settings surface is available and can also revoke Voyager’s access from their Google Account permissions.

7. Microsoft data

When a user or organization connects Microsoft services, Voyager may access or process data from Microsoft Entra ID, Microsoft accounts, Outlook/Microsoft 365 mail, calendars, contacts, OneDrive, SharePoint, Teams, and other Microsoft Graph or Microsoft 365 services within the permissions granted by the user or tenant administrator.

Voyager follows a least-privilege approach and uses Microsoft-connected data to provide the specific user-facing integration, synchronization, communication, search, workflow, collaboration, or automation feature selected by the user or organization.

Voyager does not use the content of Microsoft mail, files, calendars, chats, Teams conversations, contacts, or other connected Microsoft work data for third-party advertising or data-broker purposes. Enterprise administrators may control consent, permissions, retention, and access according to their Microsoft tenant policies.

Users and administrators can revoke permissions through Microsoft account or Entra controls and, where available, through Voyager integration settings.

8. Meta, Facebook, Instagram, WhatsApp, and related platform data

If a user connects Meta products, Voyager may process Platform Data made available for the enabled feature, such as account identifiers, Page or business information, messaging content and metadata, Instagram or Facebook business information, WhatsApp Business messaging information, advertising or conversion event information, and access tokens.

Voyager uses Meta Platform Data only for the connected user-facing feature, platform administration, security, legal compliance, or other uses permitted by Meta’s terms and applicable law.

Voyager provides a method for users to request deletion of data received from Meta. See the Voyager Data Deletion page. Where required by Meta, Voyager will implement or maintain a data-deletion callback or deletion-instructions URL and will process valid platform deletion requests.

9. Apple, iCloud, contacts, calendars, reminders, and Health

Voyager may offer integrations with Apple services or device frameworks such as contacts, calendars, reminders, files, iCloud-compatible protocols, EventKit, or Apple Health. Access occurs only after the user grants the applicable device or account permission.

Apple Health / HealthKit

If a Voyager mobile application accesses HealthKit or Apple Health data:

  • access is requested only for health or fitness features that are clear to the user;
  • the user can grant or deny access by data type;
  • HealthKit information is not used for advertising, retargeting, profiling for ads, or similar marketing services;
  • HealthKit information is not sold to advertising platforms, data brokers, or information resellers;
  • HealthKit information is not disclosed to third parties except as permitted by Apple’s requirements, the user’s express authorization, and applicable law;
  • health data is not used to make employment, insurance, credit, or other unrelated eligibility decisions; and
  • Voyager will provide any platform-required notices, usage descriptions, and privacy disclosures before requesting access.

10. Android, Google Play, contacts, location, and Health Connect

Voyager mobile applications may request Android permissions only when needed for the feature being used. Where platform policy requires a privacy-preserving picker or one-time permission mechanism for contacts, photos, video, or location, Voyager uses that mechanism rather than requesting broader access.

If Voyager accesses Health Connect information, Voyager will request only data types required for the disclosed health or fitness feature, maintain the required Google Play disclosures and declarations, and not use sensitive health information for advertising, unrelated profiling, employment or insurance eligibility, or unauthorized sharing.

11. Slack and collaboration services

If a workspace connects Slack or another collaboration service, Voyager may process workspace identifiers, channel or conversation metadata, messages, files, user information, and events within the permissions granted. Data is used to provide the integration, search, notifications, workflow coordination, audit, or automation selected by the workspace.

12. File-storage and document services

Voyager may connect to Dropbox, Box, OneDrive, SharePoint, Google Drive, iCloud-compatible storage, document-signature services such as DocuSign or Dropbox Sign, and similar providers.

Voyager accesses only the files, folders, metadata, signatures, or permissions needed for the user-facing feature and the access granted. Connected file contents are not used for unrelated advertising.

13. Accounting, payments, and financial integrations

Voyager may integrate with Stripe, QuickBooks, Xero, and other billing, accounting, finance, or payment providers.

Payment processors may collect payment-card data directly under their own privacy policies. Voyager generally receives payment status, subscription, customer, invoice, or transaction identifiers rather than complete card credentials.

When users connect accounting systems, Voyager uses the accounting and financial information only to provide the requested finance, reconciliation, reporting, workflow, CRM, project, or related business features. Connected accounting data is not used for unrelated advertising.

14. CRM, automation, signing, conferencing, and other integrations

Voyager may support services such as HubSpot, Salesforce, Zapier, Make, n8n, Zoom, DocuSign, Dropbox Sign, and similar services. Data exchanged depends on the workflow and permissions the user enables.

Users should review the permission screen before connecting a service. Third-party services remain subject to their own terms and privacy practices.

15. Email, SMS, messaging, calling, and outreach

Voyager may support email, newsletters, sales outreach, SMS, voice calls, WhatsApp, Telegram, Viber, social messaging, and other communications channels.

Depending on the channel, Voyager may process contact details, message content, attachments, delivery information, timestamps, opt-in and opt-out information, reply status, call or message metadata, recordings or transcripts when enabled, and engagement evidence such as link access or email click events.

Users and business customers are responsible for ensuring that their communications, contact lists, recordings, marketing campaigns, and automated outreach comply with applicable consent, anti-spam, telemarketing, call-recording, privacy, and platform rules.

Voyager maintains or supports suppression and opt-out mechanisms where required by the applicable feature. Users must not use Voyager to evade opt-outs, Do Not Call requirements, platform messaging windows, or other recipient protections.

Mobile messaging privacy

When you provide a mobile number and opt in to SMS from Voyager, we may use the number and related consent records to send verification codes, security and sign-in alerts, account and workspace notifications, service updates, and customer-support communications that you have requested or authorized.

Voyager does not sell or share mobile phone numbers or SMS opt-in consent data with third parties or affiliates for their own marketing or promotional messaging. We may disclose this information to service providers acting on our behalf only as needed to deliver messages, operate and secure the Services, provide support, prevent fraud or abuse, or comply with law.

We may retain records of SMS consent, the source and time of opt-in or opt-out, suppression status, and delivery events as needed to honor messaging preferences, prevent messages after an opt-out, resolve disputes, and demonstrate compliance. Replying STOP opts the mobile number out of messages under the applicable SMS program unless and until the user completes a permitted re-enrollment flow.

16. AI, agents, and automated processing

Voyager may use artificial intelligence and machine-learning systems to provide user-facing features such as summarization, drafting, classification, search, extraction, recommendations, workflow assistance, research, and user-authorized agents.

AI features may process the content a user selects or that is required to carry out the requested task. Depending on the feature, that information may be sent to an AI service provider acting on Voyager’s behalf.

Voyager does not permit protected Google Workspace data obtained through sensitive or restricted scopes to be used to create, train, or improve generalized AI or machine-learning models. Similar restrictions apply to health data and other data categories where platform terms or law prohibit such use.

AI outputs may be inaccurate. Users should review important outputs and decisions. Voyager should not be used as the sole basis for medical, legal, credit, employment, insurance, or other high-impact decisions unless a specific compliant product is expressly designed for that purpose.

17. Analytics, advertising, tracking, and marketing technologies

Voyager websites and applications may use analytics, attribution, advertising, social-media, customer-engagement, and measurement technologies where legally permitted and, where required, after consent.

These technologies may include first-party analytics and services from providers such as Google Analytics or Google Ads, Meta Pixel or Conversions API, Microsoft Advertising/UET, LinkedIn, TikTok, Reddit, Pinterest, X, customer-engagement tools, and similar providers that may be added or removed over time.

Depending on the technology and user choices, these services may receive online identifiers, device or browser information, IP address, page views, conversion events, campaign information, and similar website or app activity.

Protected connected-service content is excluded from advertising uses. Voyager does not use Google Workspace message/file/calendar/chat content, Microsoft work-content integrations, HealthKit/Health Connect data, private file contents, or connected accounting records for targeted advertising or data-broker purposes.

Voyager does not sell personal information for money. However, some advertising or cross-site measurement activities may be considered “sharing,” “targeted advertising,” or a “sale” under certain privacy laws even when no money changes hands. Where applicable, Voyager will provide required consent or opt-out controls and honor legally recognized opt-out preference signals such as Global Privacy Control.

See the Voyager Cookie & Tracking Notice for more information.

18. Cookies and local technologies

Voyager may use cookies, local storage, SDKs, pixels, tags, device identifiers, and similar technologies for authentication, security, preferences, analytics, support, performance, communications measurement, and advertising.

Where law requires prior consent for non-essential technologies, Voyager will not activate those technologies until the required consent is obtained. Users can change choices through the available privacy or cookie controls.

19. When we disclose information

Voyager may disclose information:

  • to service providers and subprocessors that provide hosting, databases, security, communications, customer support, billing, analytics, AI, infrastructure, and other services on Voyager’s behalf;
  • to connected services at the user’s direction;
  • to workspace administrators where appropriate for business accounts;
  • to professional advisers and auditors subject to confidentiality;
  • in connection with a corporate transaction, subject to applicable law and platform-specific restrictions;
  • to comply with legal process or protect rights, security, and safety; or
  • with the user’s direction or consent.

We do not disclose protected Google Workspace data in ways prohibited by Google’s Limited Use requirements, and we do not disclose HealthKit information in ways prohibited by Apple.

20. International data transfers

Voyager may process information in the United States, European Economic Area, United Kingdom, Ukraine, Poland, or other countries where Voyager, its affiliates, or service providers operate.

Where required, Voyager will use an appropriate transfer mechanism such as adequacy decisions, Standard Contractual Clauses, the UK International Data Transfer Addendum, or another legally recognized mechanism, together with supplementary measures where appropriate.

21. Retention

Voyager retains personal information only for as long as reasonably necessary for the purposes described in this Policy, including providing the Services, maintaining security and audit records, complying with legal obligations, resolving disputes, and enforcing agreements.

Retention depends on the data category, workspace configuration, connected-service requirements, contractual commitments, legal requirements, and user deletion requests. Some deleted data may remain temporarily in backups or immutable security/audit records until ordinary expiration.

Connected-service tokens and cached information should be deleted or revoked when no longer required, subject to platform rules and technical constraints.

22. Security

Voyager uses reasonable administrative, technical, and organizational safeguards designed to protect information. Measures may include access controls, logging, encryption, secrets management, authentication controls, tenant isolation, secure transport, backup procedures, vulnerability management, and incident response.

No system is completely secure. Users are responsible for protecting credentials, devices, and access to their accounts.

23. Your choices and rights

Depending on your location and relationship with Voyager, you may have rights to:

  • access personal information;
  • obtain a copy or portability of information;
  • correct inaccurate information;
  • delete information;
  • restrict or object to processing;
  • withdraw consent;
  • opt out of certain targeted advertising or sharing;
  • limit certain uses of sensitive personal information;
  • appeal a privacy-request decision where applicable; and
  • complain to a data-protection authority.

To submit a request, contact hello@voyagerhubs.com or use the privacy controls made available in the Services.

Voyager may need to verify identity before completing a request. For organization-controlled business data, Voyager may direct the request to the relevant organization.

24. California and other U.S. state privacy rights

Where applicable U.S. state privacy laws provide rights regarding access, correction, deletion, portability, targeted advertising, sale, sharing, profiling, or sensitive information, Voyager will provide the rights and notices required in the relevant jurisdiction.

Voyager does not sell personal information for money. Where advertising or measurement technologies constitute “sharing,” “sale,” or “targeted advertising” under applicable law, eligible users may opt out.

Voyager will not discriminate against a user for exercising applicable privacy rights.

Where legally required, Voyager will recognize qualifying browser-based opt-out preference signals such as Global Privacy Control.

Voyager will provide a “Your Privacy Choices” or equivalent mechanism before activating advertising technology that triggers applicable sale, sharing, or targeted-advertising opt-out requirements.

25. EEA, UK, and Swiss rights

Individuals in the EEA, UK, Switzerland, and other jurisdictions may have rights to access, correction, deletion, restriction, objection, portability, and withdrawal of consent.

Where Voyager relies on legitimate interests, individuals may object to processing as provided by law. Where Voyager processes data for direct marketing, individuals may object at any time.

Users may lodge a complaint with their local supervisory authority.

26. Children and family use

Voyager business and personal account owners must be at least 18 years old or the age of legal majority required to enter into the applicable agreement.

Voyager is not directed to children under 13 and does not currently offer child-directed accounts. An adult using family features may choose to enter information about family members, including minors, where the adult has authority to do so.

Voyager will not knowingly use a child’s information for targeted advertising. If Voyager later launches child accounts or child-directed services, it will implement the separate age, parental-consent, platform, and privacy controls required before enabling those accounts.

27. Sensitive information

Voyager may process sensitive information only when required for a user-requested feature and with the additional protections required by law and platform policy.

Sensitive information may include precise location, health or wellness information, financial information, authentication credentials, communications content, information about minors, and other categories defined by applicable law.

Sensitive information is not used for unrelated targeted advertising where prohibited or inconsistent with the context in which it was collected.

28. Changes to this Policy

We may update this Privacy Policy as Voyager evolves. We will change the effective date and provide additional notice when required by law or when changes materially affect users’ rights or our use of information.

29. Contact

Privacy questions and requests: hello@voyagerhubs.com

Legal notices: hello@voyagerhubs.com

Mail: 407 Lincoln Rd. Suite 6H166, Miami Beach, FL 33139, United States