Our privacy policy

When a gym becomes a customer, MaverStudio reads data from the systems that gym connects: members and contacts, memberships, plans and their prices, class schedules, check-ins, appointments, ad campaign structure, spend and performance, form submissions and calls.

If the gym uses the Workspace, it also holds the text messages, call recordings and call transcripts its team creates.

On the gym's own website, and on landing pages we host for it, the product records the ad click or source that brought a visitor, the form they sent, and page views by page and by where the visit came from. Query strings are never stored, and a page view names a browser, never a person. Landing page forms also store proof of text-message consent: the exact sentence shown, the time, the IP address and the browser.

That data belongs to the gym. We process it to provide the product to them and for nothing else.

Each customer's data is held in its own tenant and is never pooled with another customer's, for reporting, for benchmarking, or for training anything. Inside a customer's account, each location's Workspace data stays with that location.

Credentials for connected providers are encrypted at rest and are never displayed back to anyone, including our own operators.

More detail is on our security page.

We do not sell personal data. We do not give identifiable data from one customer's account to another customer, and we do not use it to advertise for another customer.

We do not upload a customer's contact lists or identifiable offline conversion data to an ad platform unless that customer approves it separately and confirms the required privacy notice and opt-out process are in place.

This website sets no cookies.

The product at app.maverstudio.com sets a session cookie that keeps a signed-in user signed in, and small preference cookies, such as whether the side menu is collapsed and which location the Workspace last showed.

The tracking snippet a customer installs on its own website sets two first-party cookies on that customer's domain. They hold where a visitor first and last came from, so a form sent days later can still be joined to the ad click.

Landing pages we host for a customer use those two cookies too, and a sealed cookie that lasts five minutes and keeps what a visitor typed when a form asks them to correct something. They can also run that customer's own Google Ads tag and Meta pixel, which set their own cookies, under Google's and Meta's terms, for that customer's advertising.

None of these cookies is used for MaverStudio's own advertising or analytics.

• The infrastructure that runs the product: our server, and Cloudflare, which carries traffic to it and stores our off-site backups.
• An email delivery service, which sends the product's account emails and new-lead alerts, and tells us when an enquiry arrives.
• The providers a customer chooses to connect: for example PushPress, Mindbody, GoHighLevel, Google Ads, Meta and Twilio. Twilio carries the customer's calls and texts, and transcribes calls where the customer switches it on.
• Stripe, which takes our customers' payments for MaverStudio.

We do not add third-party services to the product without telling customers.

Write to [email protected] and say what you want removed. If you sent us an enquiry and would rather we did not keep it, that is a one-line email and we will delete it.

If you are a gym's lead or member, the gym holds your data and decides what happens to it. Ask the gym first; we will help them act on your request.

When what we collect or how we use it changes, this page changes with it, and the date at the top moves.

Questions about privacy: [email protected].