Privacy Policy
Last updated: July 16, 2026
This policy explains what data SerpCue ("we") collects, why, and how we store it. We aim to collect only what is necessary to run the product, measure whether our marketing is working, and improve the onboarding and SEO workflow.
1. Account data
When you register, we store your name, email address and password. Passwords are stored cryptographically hashed; we do not store or see them in readable form. We use account data for sign-in, product communication, support and billing when you choose a paid plan.
2. Sites and analyses
We store the domains you add, competitors you enter, and SEO analysis results such as on-page audit results, content gap results, technical audit results, rankings and opportunity reports. These analyses are based on public pages we crawl and, when you connect it, data from your Google Search Console account.
3. Google Search Console data
This is the most sensitive product integration, so we want it to be clear:
- When you connect a Google account, we receive access credentials that are stored encrypted in our database and tied to a specific SerpCue project.
- We use those credentials only to read Search Console data for sites you have access to, such as clicks, impressions, CTR, average position, pages and queries.
- We do not change anything in your Google account or website, and we do not access Gmail, Drive or other Google services.
- You can revoke access at any time with the disconnect option in SerpCue or in your Google account at myaccount.google.com/permissions.
- SerpCue's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google Search Console data for advertising, do not sell it, and do not allow humans to read it except with your consent, for security purposes, or where required by law.
4. Advertising and attribution
We may use advertising platforms, including Meta, to understand which campaigns, ads and landing pages lead to product actions such as registration, adding a website, connecting Google Search Console or starting a subscription. This helps us measure ad performance and avoid optimizing only for clicks that do not become real SerpCue users.
When you arrive from an ad or tracked link, SerpCue may store attribution information such as:
- UTM parameters, including utm_source, utm_medium, utm_campaign, utm_content, utm_term and utm_id.
- Ad platform identifiers and URL parameters, including fbclid, _fbp, _fbc, campaign_id, adset_id, ad_id and placement where present.
- For paid landing page visits, we may store the landing page, referrer, campaign fields, Meta click identifiers, and hashed technical identifiers such as session, IP address and user-agent hashes.
- We store first-touch and last-touch attribution so we can understand both the first ad or campaign that introduced a user to SerpCue and the most recent paid touch before signup.
This attribution data may be stored in a temporary SerpCue attribution cookie and, when you register, saved on your user account. Paid landing page visit records may also be linked to your user account after registration so we can report which creative or ad led to signup and later activation.
5. Meta Pixel and Conversions API
SerpCue uses Meta Pixel on public pages, landing pages and app pages when the Meta Pixel is configured. The Pixel sends browser-side measurement data to Meta, including PageView events. SerpCue also sends certain product events to Meta through browser-side Pixel events and/or the server-side Meta Conversions API.
The Meta events currently implemented in the application are:
- PageView - sent by the browser Meta Pixel when configured.
- CompleteRegistration - sent when a user completes registration.
- WebsiteAdded - sent when a user adds a website/project.
- SearchConsoleConnected - sent when a user completes the Google Search Console connection flow.
- Subscribe - sent after a billing success browser redirect and server-side after Lemon Squeezy confirms an active or trialing subscription by webhook.
Server-side Meta Conversions API events may include hashed email, hashed user ID, hashed first and last name when available, IP address, user agent, _fbp and _fbc where available, event name, event time, event ID for deduplication, source URL and limited event details such as value and currency for subscriptions. We do not send your Google Search Console performance data to Meta.
Meta processes this information under its own terms and privacy policy. You can read Meta's privacy information at facebook.com/privacy/policy.
6. Cookies and similar technologies
We use essential cookies for sign-in, sessions and CSRF protection. We also use advertising and attribution cookies or similar identifiers when advertising measurement is enabled.
- sc_attr is a SerpCue attribution cookie that stores ad click and UTM attribution for up to 90 days.
- Meta may set or use _fbp and _fbc identifiers for ad measurement and attribution.
- Ad click parameters such as fbclid may be captured from the URL and stored with attribution data.
7. Third parties
We use third-party services only where they support a product feature, payment, infrastructure, analytics or advertising measurement. These may include Google for Search Console and PageSpeed, Meta Platforms, Inc. for advertising measurement and attribution, Lemon Squeezy for billing, email providers for transactional email, and AI providers for text generation. We send each provider only the data needed for the relevant feature or measurement flow.
We do not sell your personal data.
8. Retention and deletion
We keep your account and product data while your account is active. You can delete your account at any time from your profile settings. Account deletion removes the user account and data stored directly on that account, including the attribution snapshot saved on the user record and stored Google Search Console credentials.
Some paid landing page visit records may remain after account deletion for aggregate advertising reporting, with the user link removed. These records are used to understand campaign performance and may contain campaign parameters, landing page information, Meta click identifiers, and hashed technical identifiers. Account deletion does not delete advertising event data that Meta has already processed on Meta's systems.
9. Changes
If we make material changes to this policy, we will announce them in the app or by email and update the date at the top of this page.
10. Contact
For any privacy questions, email us at uros@serpcue.com.