Voyager Account & Data Deletion

Effective date: August 19, 2026

Voyager provides processes for users to request deletion of accounts and personal information, subject to authentication, workspace authority, legal retention requirements, security needs, and contractual obligations.

1. Request account deletion

You may request deletion by:

1. using the in-app account-deletion control when available; or
2. contacting hello@voyagerhubs.com with the subject “Voyager Account Deletion.”

Voyager may require identity verification before processing the request.

Google Play-distributed applications that allow account creation will provide an in-app deletion path and a publicly accessible web path for requesting account deletion.

2. Business workspace data

An individual user may not be authorized to delete an organization’s entire workspace.

Where an organization controls workspace content, requests to delete organization-controlled data may need to be submitted by an authorized administrator or directed to the organization.

Removing an individual user does not necessarily delete records that belong to the organization, such as project history, audit events, communications retained under the organization’s lawful instructions, or business records the organization is required to retain.

3. Personal and family workspaces

Authorized owners may request deletion of a personal or family workspace. Voyager will delete or de-identify information associated with the workspace unless retention is required for legal, security, billing, dispute, or backup purposes.

4. Connected services

Deleting a Voyager account does not automatically delete information held independently by a connected provider.

Users should also disconnect Voyager and, where applicable, revoke access through the connected provider’s account settings.

Voyager will revoke or delete connected-service credentials and tokens when they are no longer required, subject to applicable platform rules and technical requirements.

5. Google data

Users may revoke Voyager’s Google access through their Google Account permissions.

Upon a valid deletion request or disconnection, Voyager will delete or revoke Google-connected data and credentials that Voyager is required to remove, subject to legal obligations and Google policy.

Google Workspace data is handled in accordance with the Google Workspace User Data and Developer Policy and Limited Use requirements.

6. Microsoft data

Users or tenant administrators may revoke Microsoft permissions through Microsoft account or Entra controls.

Voyager will remove connected Microsoft credentials and data as required by the user’s deletion request, administrator instruction, contractual retention settings, applicable law, and Microsoft platform requirements.

7. Meta / Facebook / Instagram / WhatsApp data deletion

If Voyager receives information through Meta platforms, users may request deletion through Voyager using this page or through the deletion process Meta provides when a user removes an app.

Where Meta sends Voyager a valid data-deletion request, Voyager will identify the applicable Meta app-scoped user information, delete the Meta Platform Data that must be deleted, and provide or maintain a deletion-status mechanism as required by Meta.

Meta Data Deletion Instructions URL: https://voyagerhubs.com/data-deletion

Meta Data Deletion Callback: where a connected Meta product requires a deletion callback, Voyager will deploy and maintain the required authenticated HTTPS callback before enabling that integration in production.

8. Payment and accounting records

Certain invoice, payment, tax, fraud-prevention, or accounting information may need to be retained for legal or financial-recordkeeping periods even after account deletion.

Complete card data held independently by a payment processor must be managed through that provider.

9. Security and audit records

Voyager may retain limited security, fraud-prevention, abuse, audit, or legal records after deletion where necessary and permitted by law.

Limited SMS consent, opt-out, suppression, and delivery evidence may be retained where necessary to honor opt-outs, prevent unauthorized re-enrollment, resolve disputes, or comply with law. Retaining these records does not authorize Voyager to continue sending messages after an opt-out.

Deletion from backups may occur on the backup system’s normal expiration cycle.

10. Timing

Voyager will respond to verified deletion requests within the period required by applicable law or the relevant platform policy.

If Voyager denies or limits a deletion request because retention is legally required, Voyager will explain the reason where required and permitted.

11. Contact

Deletion requests: hello@voyagerhubs.com

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