This policy covers quantivo.com (the marketing site and its contact form) and the client dashboard at quantivo.com/dashboard. It is written from the code that runs the site, so every data flow described here is one that actually exists. If you find a gap, email privacy@quantivo.com.
The short version: the public site has no analytics, no ad pixels and no tracking cookies. The contact form emails us what you typed. The dashboard stores the company details, keywords and prompts a client gives us, plus the results we gather about them, and (only if the client connects it) a read-only key to their Google Analytics property.
1. Visiting the public site
We do not run Google Analytics or any other analytics product, advertising pixels, heatmaps or session recording on quantivo.com. Two things do load on every page:
- Vercel hosts the site. Like any host it sees your IP address, user agent and the pages you request in order to serve them and keep request logs for a short period.
- Clerk, our sign-in provider, loads its script on every page because the whole site shares one layout. For signed-out visitors it may set a cookie that records "not signed in" so that the Client Login link knows what to show. It does not track you across other sites.
The contact form on the homepage also loads a Cloudflare Turnstile widget. Turnstile checks that a submission comes from a person rather than a script. To do that Cloudflare receives browser signals and, when you submit, your IP address and the challenge token.
2. The contact form
When you submit the partnership application form we receive your name, email address, the budget range you picked, your website URL (optional) and the text you wrote about your search challenge. The form sends it to our API, which verifies the Turnstile token with Cloudflare and then emails the submission to hello@quantivo.com through Resend, with your email set as the reply-to address.
We do not write form submissions to a database. The copy we keep is the email in our mailbox, and Resend keeps its own delivery logs under its retention policy. We use what you send to reply to you and to decide whether we are a fit. We do not add you to a mailing list; there is no newsletter.
3. Client accounts and the dashboard
There is no public sign-up. We create a client record for you after we agree to work together, and you sign in through Clerk. Clerk handles the credentials, email address, name, multi-factor settings and session cookies; its own privacy policy covers how it stores them. On our side the clients table stores your Clerk user ID, company name and domain, the GA4 property ID you enter, and the Google token described in section 4.
What you add in the dashboard, and what we generate from it:
- Keywords (up to 50). Each day a scheduled job sends your keywords and your domain to DataForSEO, which returns Google rankings and whether an AI Overview appeared. We store the position, the AI Overview flag and a snippet of the AI Overview text.
- Prompts (up to 50) and competitors (up to 20). Each day we send each prompt, together with your company name and competitor names, to AI models through Vercel's AI Gateway: OpenAI gpt-4o-mini (used for the ChatGPT and Copilot columns), Perplexity sonar, and Google gemini-2.0-flash. We store whether your brand appeared, where, a snippet of the answer, a sentiment label and which competitors were mentioned.
- Brand perception scans. We ask the same models what they know about your company name and domain, and store the answer snippet, sentiment, descriptors, a flag for apparent hallucinations and a recommended action. This runs daily and again when you change your company name or domain.
- Alerts we generate from the above, and whether you have read them.
The model providers receive your company name, domain, competitor names and prompt text. They do not receive your Google Analytics data, your email address or your Clerk identity. Calls go through Vercel's AI Gateway, which records usage per request on our account.
4. Google user data (Google Analytics connection)
This section exists because the dashboard can read your Google Analytics 4 property through Google's APIs, and Google requires us to be specific about it. Our use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
What we ask for
One scope: analytics.readonly. We cannot change anything in your Google Analytics account. When you click "Connect Google Analytics" in Settings, Google asks you to approve this scope and then gives us a refresh token, which we store in your client record.
What we read
Aggregated reporting data for the one GA4 property ID you entered: sessions and purchase revenue by channel group and by session source, over a date range. The job runs daily at 3am UTC. We store the totals per period (organic sessions, AI-referred sessions, organic revenue, AI-referred revenue). We do not read user-level, event-level or audience data.
What we do with it
We show it to you on the Revenue page of your dashboard, next to your rankings and AI citation data. That is the only use. We do not sell Google user data, do not use it to serve or target ads, do not use it to train or improve any model, and do not let humans read it except with your consent, for security, to comply with law, or in aggregated form that cannot identify a person. The only parties that see it are the sub-processors needed to run the dashboard: Neon (database) and Vercel (hosting). It never goes to the AI model providers or DataForSEO.
Legacy service account keys
The Settings API also accepts a Google service account key as an older alternative to the OAuth connection. If you supplied one, it is stored in the same table and used only for the same GA4 reads. The disconnect action below clears it along with the OAuth token.
How to disconnect
Open Settings in the dashboard and click "Disconnect" next to the Google Analytics status. That calls Google's token revocation endpoint and clears the token and any legacy key from your record, so no further GA4 reads can happen. You can also remove Quantivo from your Google account permissions; the next scheduled read then fails and nothing new is stored. Revenue figures already collected stay in your dashboard until you ask us to delete them or delete your account.
5. Cookies
- Clerk session cookies (names starting with
__session,__client_uatand similar): keep you signed in to the dashboard. Strictly necessary. google_oauth_state: set for ten minutes while you connect Google Analytics, so the callback from Google can be matched to the browser that started it. Deleted on completion.
There are no analytics, advertising or preference cookies.
6. Sub-processors
These are the companies that process data on our behalf, and what each one touches.
- Clerk: authentication, user profile and session cookies.
- Neon: the Postgres database holding client records and all dashboard data.
- Vercel: hosting, serverless functions, scheduled jobs, and the AI Gateway that routes model calls.
- OpenAI, Perplexity and Google (Gemini): receive prompts, company name, domain and competitor names.
- Google (Analytics Data API): the GA4 reads described in section 4, only if you connect.
- DataForSEO: receives your tracked keywords and domain for ranking checks.
- Resend: delivers contact form emails.
- Cloudflare: Turnstile bot check on the contact form.
7. How long we keep things
- Contact form emails: kept in our mailbox while the conversation is live and deleted when it is no longer needed, or sooner on request.
- Client record (Clerk ID, company, domain, property ID, Google token): while your account is active. Deleted within 30 days of a deletion request.
- Rankings, AI Overview appearances, prompt snapshots, brand mentions, revenue totals and alerts: kept while your account is active so your charts have history, and deleted within 30 days of a deletion request. Deleting the client record deletes all of them, because every table references it with cascade on delete.
- Google refresh token: until you disconnect or your account is deleted.
- Clerk account: deleting it triggers a webhook that deletes your client record and everything attached to it.
8. Security
Traffic is served over HTTPS with HSTS. Dashboard routes require a Clerk session, and every query is scoped to the signed-in user's client record. Admin and scheduled-job endpoints require a bearer secret. Database access is limited to the application and the Quantivo team. No system is perfectly secure, and we would rather say that than promise otherwise.
9. California residents (CCPA/CPRA)
This section applies if you live in California. It repeats the facts above in the categories the law uses.
Categories of personal information collected in the last 12 months
- Identifiers: name, email address, IP address, Clerk user ID. Source: you, Clerk, your browser.
- Account and contact details: company name, website domain, budget range. Source: you.
- Commercial information: the service you use with us, keywords, prompts, competitors and the results we gather about them. Source: you, DataForSEO, the AI model providers.
- Internet or network activity: request logs at our host, Turnstile signals, dashboard session cookies. Source: your browser.
- Geolocation: none beyond the coarse location implied by an IP address in server logs. We do not derive or store location.
- Inferences: none about you as a person. The sentiment labels and hallucination flags we store describe how AI models talk about your company, not about you.
- Sensitive personal information: none. The Google token is a credential we hold for you, not information about you.
Purposes
Replying to inquiries, running the dashboard you signed up for, keeping the service secure, and meeting legal obligations.
Sale or sharing
We have not sold personal information and have not shared it for cross-context behavioral advertising in the last 12 months, and the code contains nothing that would. We do not sell or share the personal information of anyone, including consumers under 16.
Retention
As described in section 7, per category.
Your rights
- Know and access what we hold about you, including the categories and sources above.
- Delete it.
- Correct it. Company name, domain, keywords, prompts and competitors can be edited in the dashboard; anything else, ask us.
- Opt out of sale or sharing. There is none, so there is nothing to opt out of; the right still exists.
- Limit the use of sensitive personal information. We collect none.
- Not be discriminated against for exercising any of these rights.
How to make a request
Email privacy@quantivo.com, or use the contact form and say it is a privacy request. We respond within 45 days.
To verify a request we match it to the email address on your account or on the form submission you are asking about, and may reply to that address with a confirmation step. For dashboard accounts, a request sent from the signed-in email is enough. An authorized agent may submit a request for you if they provide your signed permission, and we may still confirm directly with you.
Global Privacy Control and Do Not Track
We do not sell or share personal information and run no analytics, so a Global Privacy Control signal has nothing to switch off; we treat it as an opt-out request all the same. We do not respond to Do Not Track headers because there is no cross-site tracking on this site for them to affect.
Shine the Light
California Civil Code section 1798.83 lets residents ask which personal information a business disclosed to third parties for their direct marketing. We disclose none for that purpose. You can still ask at the address above.
10. Children
The site and dashboard are for businesses. We do not knowingly collect personal information from anyone under 13, and if we learn that we have, we delete it. If you believe a child has sent us information, email privacy@quantivo.com.
11. Changes
When our practices change we update this page and the date at the top. For changes that affect dashboard clients, we also email the address on the account.
12. Contact
Privacy questions and requests: privacy@quantivo.com. Everything else: hello@quantivo.com or the contact form.