Privacy Policy
Last Updated: October 29, 2026 (notice of changes taking effect on 1 December 2026)
At Multraverse.ai, we are committed to protecting your privacy and the privacy of your customers. This Privacy Policy explains how we collect, use, disclose, and protect information when you use our software-as-a-service platform (the "Platform") for SMS messaging, email communications, payment processing, tax documentation, booking, calendar integration, and business automation services.
Changes taking effect on 1 December 2026
The changes below take effect on 1 December 2026. Until then they do not apply: we do not use PostHog, and the rest of this policy applies as written. We are giving this notice more than 30 days ahead, as section 19 says.
Section 8, Third Party Service Providers: added
- PostHog: Website analytics, error tracking and session recordings on multraverse.ai and journey.multraverse.app, only after you click Accept on our cookie banner (see below) (PostHog Privacy Policy)
Section 17, Cookies and Tracking Technologies: added
Analytics and error tracking (PostHog)
If you click Accept on our cookie banner, we use PostHog, a service of PostHog Inc. (United States), to understand how this site is used and to find and fix errors. PostHog collects the pages you visit, what you click, your device and browser type, and technical errors that occur. With your consent, it also records your visit as a session recording, which replays your clicks, scrolling and navigation so we can improve the site. What you type into form fields is never recorded, and payment card details are entered in Stripe's secure form and are never captured. Where our pages show your name, email address or phone number, that text is hidden in recordings, and we do not send them to PostHog as data.
PostHog starts only after you click Accept. If you click Reject, or do nothing, it does not load and sets nothing on your device. You can change your mind at any time with "Cookie settings" in the footer: choosing Reject stops PostHog and removes what it stored on your device. Our own developers' visits are not recorded.
On multraverse.ai, sign-in pages, password reset, the client portal, and pages opened from a private link (such as a quote, payment, invitation or appointment link) are never recorded, and the private part of such a link is removed before anything is sent. Sessions of Multraverse staff in our staff area are recorded to help us support them and improve those screens, with customer details hidden.
Your website progress page (journey.multraverse.app). The private page we send you a link to, where you follow your new website and ask for a preview, uses the same PostHog service under the same rules, with its own cookie banner and "Cookie settings" link: nothing starts unless you click Accept on that page. If you do, PostHog collects which steps you take there (opening the page and the stage your website is at, starting and sending the preview request form, opening your preview, and errors such as an expired link), what you click, and your device and browser type, and records your visit as a session recording in which all text on the page and everything you type is hidden, so it shows only the layout, your clicks, scrolling and navigation. Your private link is removed from the page address before PostHog starts, and it, your business name, your answers and your contact details are never sent to PostHog. Our own code on that page stores only your cookie choice (mv_consent, kept 6 months), your unsent answers to the preview request form while you fill it in (mv_journey_draft, described below), and, on our own team's devices, mv_no_track, which keeps PostHog off there; our team's visits are excluded only on devices where it is set. If you click Accept, PostHog also sets its own cookies and storage there (names starting ph_), as described below.
We keep this data for 30 days, then it is deleted. Data is processed in the United States.
What we store on your device
This is everything our own code stores in your browser. All of it is strictly necessary or functional: it is used whether or not you click Accept, none of it is sent to PostHog, and only your unsent preview request form (below) holds your name, email address or phone number.
- Your cookie choice (
mv_consent, local storage, on multraverse.ai and journey.multraverse.app): whether you clicked Accept or Reject, and when. Kept 6 months, then we ask again. - Your sign-in (local storage), if you sign in: keeps you signed in until you sign out.
- Partner credit (
mv_partner_attribution, local storage): if you reach our site through a link one of our partners shared (an address starting multraverse.ai/r/), the partner's link name, the campaign label if the link had one, and the time you followed it. Kept 30 days. We use it only to credit the partner who referred you if you then contact us or sign up, and it is sent to us only with a form you choose to submit. - Partner visit code (
mv_partner_visitor, local storage): a random identifier stored on your device the first time you follow a partner link, so that we can attribute each visit to the partner who referred it and count it once a day. It is not linked to your name, email address, phone number or account. It is sent to us each time you follow a partner link, and we keep only a one-way hash of it combined with the link and the day, so it cannot be used to follow you across days or links. With each visit we also record the campaign label if the link had one, the kind of device (phone, tablet or computer) and the name of the website you came from. It is kept 12 months, then replaced with a new random code. - This notice (
mv_policy_notice_dismissed, local storage): that you closed the notice about this update. - Promotional code (
promo_code_and the plan name, session storage): a promotional code from a link you followed, so it is applied when you sign up. Gone when you close the tab. - Welcome animation (
multraverse_splash_shown, session storage): that the opening animation has played, so it plays once. Gone when you close the tab. - App install prompt (
pwa-banner-dismissed, session storage): that you closed the "install the app" prompt. Gone when you close the tab. - Staff recording notice (
mv_staff_notice_seen, session storage, Multraverse staff only): that the notice about recordings in our staff area has been shown this session. - Your unsent preview request (
mv_journey_draft, session storage, journey.multraverse.app only): what you have typed into the preview request form, including the name, phone number and email you give for contacting you, so a reload or a trip to another app does not lose it. It stays on that tab: it is deleted when you send the form or close the tab, it is never sent anywhere except with the form you choose to send, and your private link is never stored. - Analytics off (
mv_no_track, local storage, on multraverse.ai and journey.multraverse.app, only on devices used by our own team): keeps PostHog off on that device. - Payment pages: when you pay, Stripe sets its own cookies for fraud prevention (see section 6).
On devices used by Multraverse staff, our admin and staff tools also keep display preferences and unsent drafts.
PostHog's own cookies and storage (names starting ph_) are set only after you click Accept and are removed if you change your choice to Reject. To clear everything above, clear your browser's site data (cookies and site storage) for multraverse.ai and journey.multraverse.app in your browser's settings.
1. Definitions
- "Platform Users" or "Tenants" means businesses and individuals who register for and use the Multraverse.ai Platform.
- "End Customers" means customers, clients, or contacts of Platform Users who receive communications or services through the Platform.
- "Personal Information" means information that identifies or can be used to identify an individual.
- "We," "Us," or "Multraverse" means Multraverse.ai and its affiliates.
2. Information We Collect
We collect information in several ways:
Information You Provide
- Account registration information (name, email, phone number)
- Business information (company name, address, tax ID, business type)
- Payment and banking information for receiving disbursements
- Tax documentation (W-9, TIN, EIN, SSN)
- Service preferences and configuration settings
- Communications with our support team
Information Collected Automatically
- Device information and browser type
- IP address and location data
- Platform usage data and analytics
- Log files and error reports
End Customer Information Processed on Your Behalf
- Contact information (names, phone numbers, email addresses)
- Appointment and booking data
- Payment transaction records
- Communication history (SMS, email content)
- Consent records and preferences
3. How We Use Your Information
We use the information we collect to:
- Provide, maintain, and improve the Platform and its services
- Process transactions and send related information
- Send SMS messages and emails on your behalf to your End Customers
- Process payments and disbursements through our payment processor
- Generate tax documents as required by law
- Manage bookings, appointments, and scheduling
- Respond to your inquiries and provide customer support
- Send you service announcements and updates about the Platform
- Monitor and analyze trends, usage, and activities
- Detect, prevent, and address fraud and security issues
- Comply with legal obligations
4. SMS Messaging Privacy
SMS Opt-In Data and Consent
When you or your End Customers provide phone numbers and opt-in to receive text messages through the Platform:
- Mobile phone numbers collected for SMS purposes will NOT be shared with third parties or affiliates for marketing or promotional purposes
- SMS opt-in consent data will NOT be shared with or sold to any third party
- Message frequency varies based on account activity and service engagement
- Standard message and data rates may apply from mobile carriers
- Recipients may opt out at any time by replying STOP to any message
- Reply HELP for assistance with the messaging service
This non sharing commitment applies to all SMS related data processed through the Platform, including phone numbers, consent records, and messaging preferences. This commitment is absolute and applies regardless of any other data sharing described in this Privacy Policy.
5. Email Communications Privacy
When we send emails on your behalf:
- Email addresses are used only to deliver your communications
- We track delivery status, open rates, and click rates to provide you with analytics
- Unsubscribe requests are honored and maintained in a suppression list
- Email content and recipient information are stored securely and retained as necessary for service delivery and legal compliance
6. Payment Information Privacy
Payment processing is handled by Stripe. When you or your End Customers make payments:
- Multraverse.ai does not store credit card numbers or bank account details
- Payment information is collected and processed directly by Stripe, including card details read by Stripe's software in the Multraverse POS app (see section 11)
- Stripe's handling of payment data is governed by the Stripe Privacy Policy
- We receive only transaction confirmations and limited payment details (last 4 digits, card type); for in-person payments taken with the Multraverse POS app, the details listed in section 11
6.1 Platform Billing Transactions
Multraverse.ai currently offers fixed monthly subscription pricing to all new clients. To bill you for your subscription and any usage-based overages (such as SMS, email, or AI usage above your plan limits), we collect and process the following billing related information:
- Your Stripe customer ID and the payment method token issued by Stripe
- Your selected tier, billing cycle, and subscription status
- Aggregated usage counters (e.g., SMS sent, emails sent, AI tokens consumed) used to calculate overage charges
- Invoice history, payment status, and any refund or chargeback records
This information is used solely to operate your account, calculate fees, issue invoices, and meet our tax and accounting obligations. It is not used for advertising or sold to third parties.
6.2 Grandfathered Revenue Share Plans
A limited number of clients remain on legacy revenue share (percentage-based) plans entered into prior to April 2026. For these clients, we additionally process:
- The gross transaction volume processed through your connected Stripe account
- The platform's contractual percentage share of those transactions
- Reconciliation records used to compute and collect the platform fee from your Stripe payouts or via direct invoice
This information is collected from Stripe via the Stripe Connect API only to the extent necessary to administer your existing plan. Revenue share processing will continue under the original terms of your agreement until you migrate to a current fixed monthly tier or your agreement otherwise terminates. New signups are not offered the percentage based model.
7. Data We Process on Your Behalf
As a Platform, we process certain data on behalf of our Tenants (business customers). This includes:
- End Customer contact information (names, emails, phone numbers)
- Appointment and booking data
- Payment transaction records
- Communication history (SMS and email content)
- Consent records and preferences
For this data, Tenants are the "Data Controllers" and Multraverse.ai acts as a "Data Processor."
Tenants are responsible for:
- Providing appropriate privacy notices to their End Customers
- Obtaining necessary consents for data processing
- Responding to data subject access requests from their End Customers
- Ensuring lawful basis for processing End Customer data
8. Information Sharing and Disclosure
We do not sell your personal information. We may share information in the following circumstances:
Third Party Service Providers
We use the following services to operate the Platform:
- Stripe: Payment processing (Stripe Privacy Policy)
- Twilio: SMS and voice communications (Twilio Privacy Policy)
- Resend: Email delivery (Resend Privacy Policy)
- Google: Google Calendar integration for availability and booking sync (Google Privacy Policy)
- Expo: App update delivery for the Multraverse POS app (Expo Privacy Policy)
Other Sharing
- When required by law, subpoena, or legal process
- To protect our rights, property, or safety, or that of our users
- In connection with a merger, acquisition, or sale of assets (with notice)
- With your explicit consent
Important Exception: All categories above exclude SMS text messaging originator opt-in data and consent. This information will NOT be shared with any third parties under any circumstances, except as required by law.
9. Google Calendar Integration and Google User Data
The Platform offers an optional Google Calendar integration. A Tenant's authorized staff member may choose to connect their Google account so the Platform can show accurate availability and keep bookings in sync with their calendar. This feature is initiated only by an authorized staff user and is never enabled for a Tenant's End Customers.
Google Data We Access
With the connecting user's consent, we request the following Google Calendar scopes:
- Free/busy information (
calendar.freebusy) read-only busy times, used to display accurate availability and hide times that are already booked. - Calendar events (
calendar.events) used to create, update, and cancel the appointment events that correspond to bookings made through the Platform.
How We Use, Store, and Share Google Data
- We use Google Calendar data solely to provide the availability and booking features the user requested.
- We do not use Google user data for advertising, and we do not use it to develop, improve, or train generalized artificial intelligence or machine learning models.
- We store the OAuth access and refresh tokens issued by Google encrypted at rest so the Platform can continue to read availability and manage booking events on the user's behalf. We do not copy or retain the contents of your calendar; only the identifiers needed to manage events the Platform creates are stored within the relevant Tenant's own application.
- We do not sell Google user data, and we do not share it with third parties except as necessary to transmit requests to Google's APIs to provide the feature, or as required by law.
Revoking Access
You can disconnect the integration at any time from within the connected application, or revoke the Platform's access directly from your Google Account at myaccount.google.com/permissions. Disconnecting or revoking access deletes the Google tokens we store. Events already created on your calendar remain there unless you delete them.
Limited Use Disclosure: Multraverse.ai's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
10. Facebook, Instagram and WhatsApp Data
A Tenant may connect its own Facebook Page, Instagram professional account and WhatsApp Business account to the Platform through Facebook Login for Business. A connection is made only by a person who manages that account for the Tenant and chooses to connect it.
What We Store
- Connection details: the identifiers of the connected Page, Instagram account, WhatsApp Business account and phone number, their display names, the permissions granted, the app-scoped Facebook user ID of the person who connected them, and the connection's status and dates.
- Access tokens: the token Meta issues for each connection, kept encrypted in a secrets vault and never in ordinary database tables. It is used only by our servers to act for the Tenant that connected the account.
- Notification log: when Meta notifies us of activity on a connected account (for example a new message or a lead ad submission), we record which account it concerns, the kind of event, its time and Meta's identifiers for it. This log does not contain message text, names, phone numbers, e-mail addresses or lead form answers. The ID of the person who sent a message, and Meta's identifier for each message (which for WhatsApp can contain a phone number), are kept only as keyed one-way hashes. Log entries are deleted after 30 days.
Why We Use It
We use this data to link activity on a connected account to the right Tenant and, as the Tenant turns on the features that use it, to show its messages in the Tenant's inbox and deliver its lead ad submissions to the Tenant. We do not sell this data and we do not use it for advertising. As with other data we process for Tenants (see section 7), the Tenant is responsible for the messages and leads it receives through its own accounts.
Disconnecting and Deleting
- If you remove the Multraverse app from your Facebook account (in Facebook's settings, under Business integrations or Apps and websites), Meta tells us and we revoke every connection you made and erase its access token.
- If you ask Facebook to delete the data Multraverse holds about you, Meta sends us the request and we revoke the connections you made, erase their access tokens, remove your Facebook user ID from them and delete the notification log entries received through them. You receive a confirmation code and can check the request at any time on our data deletion status page. We keep a record of each deletion request (its confirmation code, status and dates, and how many items were removed) for 400 days as proof that it was handled; a keyed one-way hash of your Facebook user ID is kept with it for two days only, so that a repeated request is recognised.
- You can also ask us directly at privacy@multraverse.ai.
11. Multraverse POS App
Multraverse POS is a mobile app that a Tenant's staff use to take in-person card payments for that Tenant. This section describes what the app and our servers collect when it is used. As with other data we process for Tenants (see section 7), the Tenant is the Data Controller for the staff, sales and customer information described here, and Multraverse.ai acts as a Data Processor.
Staff Who Use the App
- Staff details: the name and, if given, the mobile number and email address entered when a staff member is added to a Tenant's POS account, with their role and permissions. Today staff members are added by Multraverse at the Tenant's request.
- Signing in: if a mobile number is on file, it is used to send you a sign-in code by text and to find the Tenants that added you. The code is sent and checked by Twilio. You can instead sign in with a one-time pairing code from the Tenant. We store pairing codes and sign-in tokens only as one-way hashes, and the app keeps your sign-in in the phone's secure storage.
- The phone: a random identifier the app creates when it is first opened, and the phone's make and model, operating system version, app version and app ID. We use these so that a sign-in works only on the phone it was made on, to apply the Tenant's limit on phones, and so a lost phone can be removed. Today Multraverse removes a phone when the Tenant asks, and staff can also remove a phone from the app's settings.
- Activity log: a record of sign-ins, sales, refunds and changes to staff, phones and settings, with the staff member and phone involved, kept for the Tenant.
Card Payments
- Cards are read by Stripe's Terminal software (Tap to Pay) using the phone's contactless (NFC) reader, and the card details go to Stripe. Neither the app's own code nor Multraverse.ai receives or stores the card number, expiry date or security code.
- From Stripe we keep, with the sale, the card brand, the last 4 digits, whether a phone or watch wallet was used, the card details that card receipts must show (such as the card's application name), the link to Stripe's receipt, Stripe's identifiers for the payment and, if a payment is declined, Stripe's decline reason.
- The Platform's Stripe event handling, which serves all of a Tenant's Stripe payments, also records each POS payment in the Tenant's payment and transaction records: the amount and fees, the payment type, the sale's description, Stripe's receipt number and link, and the result of Stripe's fraud checks. It also sends Multraverse administrators a notice of the payment. If Stripe already holds an email address for the payment at that point, these records and the notice include it.
- The app asks for the phone's location for Stripe's Terminal software (approximate location on Android 12 and later, precise location on earlier Android versions), and card payments cannot be taken without it. Stripe's software receives the location and uses it for its location reporting and fraud checks. The app does not send the phone's location to Multraverse.ai.
- On Android 12 and later, the app also asks for the Bluetooth "nearby devices" permissions that Stripe's software asks for, and card payments cannot be taken without them. On iPhone, the app's settings also declare Bluetooth and local network access for Stripe's software. The app never connects to a Bluetooth or network card reader: payments are taken on the phone itself.
- Stripe also collects information about the phone and each payment. Stripe's handling of this data is governed by the Stripe Privacy Policy.
Sales
- For each sale we keep its number, the items, prices and quantities, the amounts and tax, any refunds and their reasons, any note added, the times, the staff member who took it and the phone used. These are kept for the Tenant as transaction records.
- If the Tenant has its own app connected to the Platform, we notify that app when a sale is paid, canceled or refunded. The notice carries the sale's items and amounts, but no customer details and no staff names.
Receipts
- A receipt is sent only when the customer asks for one and gives a mobile number or email address at the counter.
- Text receipts are sent through Twilio in the same way as other texts the Tenant sends (see section 4). Our messaging log keeps the number and the message, as it does for every text sent for a Tenant. Replying STOP works as for any other text, and because the log records that the Tenant texted the number, a reply from that number can be passed to the Tenant.
- Email receipts are sent by Stripe, not by us: we give Stripe the address for that payment, and Stripe keeps it with the payment.
- The POS receipt record itself keeps only a one-way hash of the number or address and a masked hint, such as the last two digits of a phone number. We do not add the customer to any contact list or send them anything other than the receipt.
Connection Details and App Updates
- Our servers log each request from the app with its IP address, the app version, the user agent the phone's software sends, the time and the result, for security and troubleshooting. These logs are deleted after 30 days. Short-lived counters used to limit repeated sign-in and session-renewal attempts also hold the IP address; they are normally cleared within a day.
- The app shows the Tenant's logo, which it loads from the web address the Tenant chose for it. The server at that address sees the phone's IP address when the logo loads.
- The app checks Expo's update service for updates to the app. Each check sends Expo the phone's IP address, details of the app and platform, and a random identifier that Expo's software creates for the installation and keeps until the app is uninstalled or its data is cleared. Expo's handling of this data is governed by the Expo Privacy Policy.
- Apart from the Stripe and Expo software described above, the app contains no advertising, analytics or crash-reporting software, and it does not use the camera, contacts or photos.
Retention and Deletion
- We do not delete POS records automatically. Staff and phone records, sales, refunds, receipt records and the activity log are kept for as long as the Tenant's account exists, and sales are also kept as financial and tax records (see section 14).
- When a staff member or a phone is removed from a Tenant's POS account, every sign-in for it ends. Removing does not erase the record.
- A staff member's record cannot be deleted once they have taken a sale, because the Tenant's sales records refer to it. If you are a staff member, we can end your access, correct your details, and remove your mobile number and email address; with the Tenant's agreement we can also replace your name with a label that does not identify you. To ask, contact the Tenant you work for, or us at privacy@multraverse.ai.
- If you are a customer, contact the business you paid (see section 16), or us at the same address.
12. International Data Transfers
The Platform is operated from the United States. If you access the Platform from outside the United States, your information may be transferred to, stored, and processed in the United States or other countries where our service providers operate. By using the Platform, you consent to such transfers.
13. Data Security
We implement appropriate technical and organizational measures to protect your information, including:
- Encryption of data in transit and at rest
- Access controls and authentication requirements
- Regular security assessments and monitoring
- Employee training on data protection
However, no internet transmission is completely secure, and we cannot guarantee absolute security.
14. Data Retention
We retain information for the following periods:
- Account information: Duration of account plus 3 years
- Transaction records: 7 years (tax compliance)
- SMS consent records: 4 years (TCPA compliance)
- Communication logs: 2 years or as required by law
- Tax documents: 7 years (IRS requirements)
- Multraverse POS staff and phone records and activity logs: Duration of the Tenant's account
- Multraverse POS sales, refunds and receipt records: Duration of the Tenant's account, and at least as long as transaction records
- Multraverse POS request logs: 30 days
Upon account termination, you may request export of your data within 30 days. Data may be deleted after 90 days following termination.
15. Your Rights
Depending on your location, you may have the right to:
- Access and receive a copy of your personal information
- Correct inaccurate or incomplete information
- Request deletion of your personal information
- Object to or restrict certain processing
- Data portability (receive your data in a structured format)
- Opt-out of marketing communications
- Opt-out of SMS text messages by replying STOP
- Withdraw consent where processing is based on consent
To exercise these rights, contact us at privacy@multraverse.ai.
16. End Customer Privacy
If you are an End Customer who has received communications from a business using the Multraverse.ai Platform:
- The business that contacted you is the Data Controller for your information
- For questions about how your data is used, please contact that business directly
- To opt-out of SMS messages, reply STOP to any message
- To unsubscribe from emails, use the unsubscribe link in any email
- For data access or deletion requests, contact the business that has your information
17. Cookies and Tracking Technologies
We use cookies and similar technologies to:
- Maintain your session and authentication
- Remember your preferences
- Analyze Platform usage and performance
- Provide security features
You can configure your browser to refuse cookies, but some Platform features may not function properly.
18. Children's Privacy
The Platform is not directed to individuals under the age of 18. We do not knowingly collect personal information from children. If we learn that we have collected information from a child under 18, we will delete that information promptly, with one exception: a Multraverse POS staff record that a Tenant's sales refer to cannot be deleted (see section 11). For such a record we will end its access and remove the mobile number and email address, and with the Tenant's agreement replace the name with a label that does not identify the person.
19. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email or through the Platform at least 30 days before the changes take effect. The "Last Updated" date at the top indicates when the policy was last revised.
In October 2026 we published notice, on this page and through a notice on the Platform, of the changes listed under "Changes taking effect on 1 December 2026" above. They take effect on 1 December 2026; until then, this policy applies without them.
20. Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us at:
Privacy Inquiries: privacy@multraverse.ai
General Inquiries: contact@multraverse.ai