Privacy Policy

Last updated: 16 October 2026

This policy explains what RevCruise does with personal data. It covers three different groups of people, and the difference matters:

  • Visitors to revcruise.io, including anyone who requests a free AI visibility check for their business.
  • Merchants — people who create a RevCruise account and use it to generate and publish pages.
  • Shoppers — members of the public who visit a page a merchant has published. Shoppers never signed up for anything, so we deliberately collect as little about them as possible.

Who we are

RevCruise is operated by Random Unicorn SIA, a company registered in Latvia under registration number 40203681590, with its registered office at Paleju iela 52 - 2, Marupe, Marupes novads, LV-2167, Latvia. We are the data controller for the processing described below.

You can reach us about anything in this policy at help@revcruise.io.

What we collect when you request a visibility check

When you ask for a free AI visibility check on revcruise.io, we collect:

  • The business you pick. As you type, we look the business up on Google, so the text you type is sent to Google to find matching listings. When you pick one, we store the details Google holds for that listing: its name, address, city, the categories Google files it under, and its Google place ID. This is public information about the business.
  • Your email address, which you give us so we can send you the report.
  • Your answers to the short questions on the scan page: your role, who handles your marketing, whether you had checked AI before, what frustrates you most, and roughly what the business turns over. Each answer is saved as you give it, so we keep the answers you gave even if you stop partway.
  • Which ad or link brought you to us, from the campaign tags in the link you clicked (for example the ad name).

We use this to run the check, send you the report, and understand which of our ads reach the right businesses.

How the check runs. We ask ChatGPT ten questions a customer in your city might ask about your kind of business, through DataForSEO, and use OpenAI to pick out the business names in the answers. Only the business's name, city and category go to them, never your email address or your answers. We also look up the businesses ChatGPT names, and the pages it cites, on Google and on the public web.

We use your email address only to confirm we received your request and to send you the report. We do not add it to a mailing list or email you about anything else.

Before 12 October 2026, the questions were asked through a form hosted by Typeform, which collected the same answers and your email address.

Analytics and session recordings on revcruise.io. We use PostHog to see how visitors use the site: pages viewed, buttons clicked, how far you scroll, and each step of the visibility check. PostHog also records sessions on the site, which captures how you move through the pages so we can see where people get stuck. Anything you type into form fields, such as your email address, is hidden in recordings.

Advertising and the Meta Pixel

We advertise RevCruise on Facebook and Instagram, and we use the Meta Pixel on revcruise.io and in the RevCruise app to measure whether those ads work and to show them to people more likely to be interested.

What the pixel sends to Meta:

  • that you viewed a page;
  • that you started a visibility check (a "lead"), and that you gave your email address on the scan page (a "registration");
  • technical details your browser sends with any request, such as your IP address and browser type;
  • identifiers stored in Meta's cookies on our site (_fbp, and _fbc if you arrived from a Meta ad), which let Meta connect these events to an ad you saw and, if you use Facebook or Instagram, to your account there.

When you give us your email address on the scan page, the pixel also sends it to Meta in hashed (scrambled) form, so Meta can match the event to your Facebook or Instagram account. Meta uses it for that matching and says it deletes it afterwards. The pixel does not send your answers to the questions.

Meta also receives a server-side copy of the same events through its own Conversions API service, which forwards what the pixel sends; we do not send Meta any additional data from our servers.

Meta uses this information under its own terms, including to improve its ad delivery. You can control how Meta uses data from other websites in your Facebook or Instagram settings under Your activity off Meta technologies, and you can block the pixel by blocking third-party cookies or using a tracker blocker. You can also email help@revcruise.io and we will tell you what we have sent about you.

What we collect from merchants

Account data. Your name and email address. If you sign in with Google we receive your name, email address and profile picture from Google — we never see your Google password. If you sign in with a password, we store only a hashed version of it. We also store a workspace record created automatically for you when you sign up.

Content you create. The product details and brand information you enter, the Shopify Buy Button embed code you paste, and the page content generated from them. We keep a record of each generation request (the inputs, the model used, and the output) so we can debug problems and improve quality.

Payment data. If you subscribe, payment is handled by Stripe. We never see or store your card details. We store the identifiers Stripe gives us — a customer ID, a subscription ID, the price you bought and its status — so we know what you have access to.

Product analytics. We use PostHog to understand how the product is used: pages viewed, actions taken (for example generating or publishing a page), and which of the three page types you choose. This is linked to your account, so it is personal data.

Session recordings. PostHog also records sessions inside the RevCruise app. This captures your interactions — clicks, navigation, and text you type into the app — so we can see where people get stuck. It does not cover pages you publish, and it does not capture card details, which are entered on Stripe's own hosted checkout rather than in our app. If you would prefer not to be recorded, email help@revcruise.io and we will exclude your account.

Support correspondence. Anything you send us by email.

What we collect from shoppers on published pages

When a merchant publishes a page with RevCruise, that page includes a small analytics script. It is deliberately minimal, and we want to be specific about what it does and does not do.

It collects:

  • that the page was viewed, and that a "Buy Now" button was interacted with;
  • the referring URL, if the browser sends one;
  • a coarse device category — mobile, tablet, or desktop, derived from the browser window width.

It does not:

  • set any cookies;
  • store IP addresses;
  • fingerprint the device or browser;
  • attempt to identify the visitor or follow them across sites.

Because of this we cannot identify individual shoppers, and the data is not linked to a person. It tells a merchant how many people saw a page and how many showed buying intent — nothing more.

Note that "Buy Now" counts are an approximation. Shopify renders its buy button inside an iframe, which our script cannot see into, so interest is inferred rather than measured exactly. Actual orders are recorded by Shopify, not by us.

When a shopper clicks through to checkout, they leave RevCruise. The checkout is the merchant's own Shopify store. We do not process the order, see the shopper's payment details, or receive their personal information. Shopify's and the merchant's own privacy policies apply from that point.

Who we share data with

We use the following providers. Each processes data on our behalf under a contract.

  • Railway — application hosting and database (United States)
  • Netlify — hosting merchant-published pages (United States)
  • Stripe — payment processing (United States / Ireland)
  • Resend — transactional email: sign-in links, verification, notifications, and visibility reports (United States)
  • PostHog — product analytics and session recording (United States)
  • OpenAI — generating page content from your inputs, and reading ChatGPT's answers for the visibility check (United States)
  • DataForSEO — asking ChatGPT the visibility-check questions; receives only the business's name, city and category
  • Google — sign-in, if you choose Google, and looking up businesses for the visibility check (United States)
  • Typeform — the visibility-check questions, until 12 October 2026 (Spain / United States)

The product details and brand information you enter are sent to OpenAI to generate page content. Do not enter anything confidential that you would not want processed by a third-party AI provider.

Meta Platforms (Ireland / United States) receives the advertising data described under "Advertising and the Meta Pixel". Unlike the providers above, Meta also uses that data for its own purposes, such as improving ad delivery, so it is not only processing it on our behalf.

We do not sell personal data for money. Sharing data with Meta through the pixel to measure and target our ads can count as "sharing" for advertising under some US state privacy laws, such as California's; you can opt out of it as described under "Your rights".

International transfers

Our providers are largely in the United States. Where data leaves the European Economic Area, those transfers rely on the safeguards offered by the provider, typically the EU Standard Contractual Clauses or an adequacy decision such as the EU–US Data Privacy Framework.

Legal bases for processing

  • Performance of a contract — running your account, generating and publishing your pages, taking payment, and running the visibility check you asked for and sending you the report.
  • Legitimate interests — product analytics, session recordings, security, and preventing abuse. We limit these to what is needed to run and improve the service.
  • Legitimate interests: advertising measurement with the Meta Pixel. We advertise only in the United States and use the pixel to measure whether those ads work. You can block it as described under "Advertising and the Meta Pixel".
  • Consent — where we ask for it specifically.
  • Legal obligation — keeping records we are required to keep, such as for tax.

How long we keep it

  • Visibility-check data (the business, your email address and your answers): 24 months after your request, or sooner if you ask us to delete it. The report itself, including the Google ratings in it, is deleted after 30 days; ChatGPT's raw answers after 90 days.
  • Account and content data: while your account exists, and for a short period afterwards.
  • Generation records: retained to debug quality issues.
  • Session recordings: retained for a limited period, then deleted automatically.
  • Payment records: retained as long as tax and accounting law requires, typically several years.
  • Shopper analytics on published pages: retained in aggregate. It contains no identifiers, so it cannot be traced back to a person.

Your rights

If you are in the EEA or UK you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or provide it in a portable format. You can also withdraw consent where processing relies on it, and complain to your local data protection authority — in Latvia, the Data State Inspectorate.

If you are in the United States, you can ask us to stop sharing your data with Meta for advertising, and to see or delete what we hold about you. Email help@revcruise.io with the subject "Do not share" and we will delete what we hold about you, including your email address. The pixel itself runs in your browser, so to stop it sending page views, block third-party cookies or use a tracker blocker, as described under "Advertising and the Meta Pixel".

Email help@revcruise.io and we will respond within one month.

Cookies

The RevCruise app and marketing site use cookies that are necessary to sign you in and keep you signed in, cookies set by PostHog for analytics and session recording, and cookies set by the Meta Pixel (_fbp, and _fbc if you arrived from a Meta ad) to measure our ads. Pages published by merchants through RevCruise set no cookies at all.

Children

RevCruise is a business tool and is not intended for anyone under 16. We do not knowingly collect data from children.

Changes

If we make a material change to this policy we will update the date at the top and, where the change is significant, tell account holders by email.

Contact

help@revcruise.io