This document
v4.5 · Oct 26, 2026
- Last updated
- Oct 26, 2026
- Version
- v4.5
- Reading time
- 17 min
This privacy policy explains how Serplyze, the keyword rank tracking app at serplyze.com, accesses, uses, stores, protects, shares and deletes your information, including the data we receive from Google APIs when you sign in with Google, connect Google Search Console and, optionally, connect Google Analytics 4. Serplyze is operated by Codenova, LLC, 30 N Gould St, STE R, Sheridan, Wyoming 82801, United States (“Codenova”, “we”, “us”). It applies to the Serplyze website, web app, emails and API.
01Summary
- Serplyze reads your Google Search Console data with Google’s read-only permission (webmasters.readonly), only to show you rankings, reports, alerts and answers about your own sites. It cannot change anything in your Search Console.
- We never sell your data, never use it for advertising, never pass it to data brokers and never use it to train AI or machine-learning models.
- If you choose to connect Google Analytics 4 (optional), Serplyze reads aggregated reports from the property you pick with Google’s read-only permission (analytics.readonly): Google organic sessions, purchases, revenue and the key events you choose, per landing page and day. We use them only to show you how much revenue and how many conversions your organic search traffic brings. Serplyze cannot change anything in your Google Analytics.
- Our AI chat sends only the question you type to OpenAI, never your Search Console or Google Analytics data. Answers are calculated by Serplyze from your data on our own servers.
- Your data is stored in the EU (Frankfurt, Germany), encrypted in transit and at rest; Google access tokens are additionally encrypted with their own keys.
- You can revoke Serplyze’s access at any time at https://myaccount.google.com/permissions or by disconnecting in Settings, and delete your projects or your whole account in the app or by writing to info@serplyze.com.
02Who we are
Serplyze is a product of Codenova, LLC, a Wyoming limited liability company, 30 N Gould St, STE R, Sheridan, Wyoming 82801, United States, EIN 30-1441589. Codenova, LLC is the controller of the personal data described in this policy. For personal data contained in the Search Console data of the sites you connect (for example a person’s name typed into Google as a search query), you are the controller and we process it on your behalf under our Data processing agreement (https://serplyze.com/legal/dpa).
Questions about this policy or your data: info@serplyze.com. General support: info@serplyze.com.
03Information we collect
We collect only what we need to run Serplyze:
- Account data: your name, email address, password (stored only as a salted hash) or Google sign-in, profile picture, workspace name, team role and settings such as language, time zone and notification preferences.
- Google sign-in data: when you choose “Sign in with Google”, your Google account email address, whether Google has verified it, your name and your profile picture (see the next section).
- Google Search Console data: the data described in the next section, for the Search Console properties you choose to connect.
- Google Analytics 4 data (optional): if you connect Google Analytics 4, the data described in the next section, for the Google Analytics properties you link to your projects.
- Content you add: tracked keywords, keyword groups and rules, notes, alert rules, report schedules and recipients, brand terms, backlinks you import, questions you ask in the AI chat and, if you connect it, a Google BigQuery service account key you upload for bulk Search Console exports (stored encrypted).
- Billing data: billing name and address, VAT or tax ID, plan, invoices and the card brand and last four digits. Full card details are entered on Stripe’s page and never reach our servers.
- Technical and usage data: IP address, browser type, sign-in times, security events, audit records of changes in your workspace, and server and error logs. We derive an approximate country from the IP address on our own servers, with an offline database and without sending the address to any third party, for security, fraud prevention and operating the service. Inside the signed-in app we do not use third-party analytics or advertising trackers.
- Website visit data on our public pages: on the marketing pages of serplyze.com and on the sign-in and sign-up screens we use Google Tag Manager, Google Analytics 4 and the Meta Pixel to measure visits and the results of our own advertising, and Microsoft Clarity to see how those pages are used. They receive the address of the page you view, the referring page, your IP address, browser and device details and cookie identifiers (see Cookies). Microsoft Clarity also records how you interact with those pages (clicks, scrolling, mouse movement and the page layout) as session recordings and heatmaps; what you type into form fields is masked by Clarity before it leaves your browser. These tools are not loaded anywhere in the signed-in app, and no workspace, project, keyword or Search Console data is ever sent to them.
- Campaign data: if you arrive from a link with utm_ campaign parameters, we store the campaign and the referring website’s host name in a first-party cookie and attach them to your account if you sign up. We skip this when your browser sends Do Not Track or Global Privacy Control.
- Communications: emails you send us and our replies.
04Google user data we access
Serplyze uses Google OAuth. Signing in with Google, connecting Search Console and connecting Google Analytics 4 are separate steps, and Google shows you on its consent screen exactly which permissions Serplyze asks for. We request only these scopes:
The Search Console scope is read-only: Serplyze cannot add or remove sites or users, submit sitemaps, request indexing or change any setting in your Search Console. We only read data for the properties you select in Serplyze, and we do not request access to Gmail, Google Drive, Google Ads or any other Google service. If you connect Google BigQuery for bulk Search Console exports, you upload a service account key you created; it gives read access to the dataset you name and is stored encrypted.
Google gives us an access token and a refresh token for the Search Console connection so that Serplyze can refresh your data once a day without asking you again. These tokens are encrypted before they are stored and are never shown in the product.
Connecting Google Analytics 4 is optional and separate from connecting Search Console. The scope is read-only: Serplyze cannot change settings, users, properties, tags or data in your Google Analytics account. We read only the aggregated reports described above, for the properties you link; Google Analytics does not give us, and we do not request, data about individual visitors. Landing-page addresses are stored without their query parameters, except parameters you explicitly ask us to keep (for example a product id). Its refresh token is encrypted with its own key before it is stored, is decrypted only by our background sync service and is never shown in the product. This is separate from Serplyze’s own use of Google Analytics on its public marketing pages, described under Technical and usage data.
05How we use Google user data
We use Google user data only to provide and improve the user-facing features of Serplyze that you see in the app:
- Rank tracking: daily positions, clicks, impressions and CTR for your tracked keywords, grouped by your keyword groups, devices and countries.
- Traffic, content and AI search analysis: page and query breakdowns, content decay, cannibalisation, rising queries and Google update markers for your sites.
- Alerts and scheduled reports: emails and PDF reports with your own figures, sent only to the people you choose.
- Forecasts and AI chat answers: calculated by Serplyze from your stored data on our own servers.
- AI-assisted keyword grouping and brand-term suggestions, described in the section “AI features and OpenAI”.
- Revenue and conversions (optional, Google Analytics 4): organic Google sessions, purchases, revenue and key events per landing page from your Google Analytics property, and an estimate of the revenue and conversions per search keyword that Serplyze calculates from your Google Analytics and Search Console data on our own servers. Estimates are labelled as such in the app, reports and API.
- Your API keys, MCP connections and Google Sheets links, which return your own data to you (Google Analytics figures only through your workspace’s own keys and connections).
- Account and security: signing you in, keeping your account and workspace secure, and troubleshooting problems you report to us.
We do not use Google user data for advertising, retargeting or personalised or interest-based ads, we do not sell it, we do not transfer it to data brokers or information resellers, we do not use it to determine creditworthiness or for lending, and we do not use it to develop, improve or train generalised or non-personalised AI or machine-learning models, ours or anyone else’s.
06Limited Use of Google user data
Serplyze's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
The Google API Services User Data Policy is available at https://developers.google.com/terms/api-services-user-data-policy. In line with it:
- we use Google user data only to provide or improve the user-facing features described in this policy;
- we transfer it to others only as needed to provide or improve those features (to the subprocessors listed below), to comply with applicable law, for security purposes, or as part of a merger, acquisition or sale of assets after obtaining your explicit prior consent;
- no person at Codenova reads your Google user data unless you have given us explicit permission for specific data (for example when you ask support to look at a project), it is necessary for security purposes such as investigating abuse, it is necessary to comply with applicable law, or the data has been aggregated and anonymised for internal operations;
- we transfer Google user data to an AI assistant only when you connect that assistant to Serplyze and ask it for the data, a user-facing feature you start yourself (see “AI assistants and connectors (MCP)”);
- Google Analytics data is shown only to members of your workspace with access to the project (and, only if a workspace owner or admin turns it on for a project, to your clients and to recipients and share links of reports you set up); our staff tools show only whether a connection works and how much data is stored, never the values.
07AI features and OpenAI
Serplyze uses the OpenAI API for three features. In each case OpenAI only processes the request to return a result to us; under OpenAI’s API terms it does not use API data to train its models. Neither we nor OpenAI use your data to train AI models.
- AI chat: OpenAI receives only the question text you type (and up to four of your earlier questions with the type of calculation chosen for them), a neutral description of the screen you are on and today’s date. It never receives your Search Console or Google Analytics data, domain, project names, keywords or numbers. OpenAI only chooses which built-in calculation answers the question; Serplyze then runs that calculation on your data on our own servers and shows you the answer. The chat panel tells you this.
- AI keyword grouping (paid plans, started by you or in project setup): OpenAI receives the text of the keywords (search queries) to be grouped, your brand terms and the names of your existing groups, and suggests a group structure that you review before it is applied. It never receives clicks, impressions, CTR, positions or other metrics.
- Brand-term suggestions (project setup): OpenAI receives your site’s domain and up to 200 of its top search queries as text and suggests the words people use for your brand. Suggestions are shown to you and saved only if you keep them.
Your questions are stored in your Serplyze chat history so that you can see earlier answers; only you can see them.
08AI assistants and connectors (MCP)
You can connect an AI assistant such as Claude, ChatGPT, Cursor or Claude Code to Serplyze through our MCP server (https://serplyze.com/mcp), either by signing in to Serplyze from the assistant and approving the connection, or with an API key you create. The connection is read-only: it cannot change anything in Serplyze, Google Search Console or Google Analytics.
When you ask the assistant a question, it can read, through the connection, the Serplyze data of the workspace you approved, limited to the projects you can access: project names and domains, tracked keywords and keyword groups, Search Console figures (clicks, impressions, click-through rate and positions) by query, page, country, device and search appearance, alerts, chart notes, AI search estimates and, if Google Analytics 4 is linked to a project and you can see its revenue, revenue and conversion figures. Search queries are the words people typed into Google and can include names.
The assistant’s provider (for example Anthropic for Claude, or OpenAI for ChatGPT) receives this data because you asked the assistant for it, and processes it under your own agreement and settings with that provider; it is not a Serplyze subprocessor. Serplyze returns only what a tool call asks for. How the provider stores or uses your conversations depends on your account and settings with that provider.
We do not receive your conversations with the assistant, only the tool calls it sends (the tool’s name and parameters such as a project, dates and filters), which we answer and do not store. For each connection made by signing in, we keep the name the app gave itself, the address it returns to, the workspace, who approved it, when it was approved and when it was last used, and we record approvals, denials and disconnections in your workspace’s audit log. Access tokens expire after one hour and refresh tokens after 30 days; we store only hashes of them. Our server logs record technical errors, not the parameters or results of tool calls.
You can disconnect an app at any time in Settings → API and Sheets → Connected apps; resetting your password or signing out everywhere also disconnects every app, and leaving a workspace ends your connections to it. Workspace owners and admins can revoke API keys in the same place. We do not use data read through these connections to train AI models.
09How we use other information
We use account, billing, technical and usage data to:
- provide the service and the features you use, and send the emails you asked for (sign-in links, alerts, reports, invoices);
- process payments and keep the billing and tax records the law requires;
- keep Serplyze secure, prevent fraud and abuse, and fix errors;
- answer your support requests;
- understand in aggregate which features are used, so we can improve them;
- send product and service announcements about your account; we do not send marketing emails without your consent, and every such email has an unsubscribe link.
If you are in the European Economic Area, the United Kingdom or Switzerland, our legal bases are: performance of our contract with you (providing the service), our legitimate interests (security, fraud prevention, product improvement in aggregate), compliance with legal obligations (tax and accounting records) and your consent where we ask for it (for example optional cookies). We never build advertising profiles.
10Sharing and subprocessors
We do not sell or rent your personal data or Google user data, and we do not share it for cross-context behavioural advertising. We share data only with the service providers below, who process it on our behalf under contracts that require them to protect it and use it only to provide their service to us:
Website visit data from our public pages (the marketing pages and the sign-in and sign-up screens), described under Technical and usage data, is also received by Google (Google Analytics and Google Tag Manager; USA), Microsoft (Microsoft Clarity session recordings and heatmaps; USA) and Meta (Meta Pixel advertising measurement; USA). This never includes your account, workspace or Search Console data.
Inside Serplyze, data is shared only with the people you give access: members of your workspace (limited to the projects you choose) and the recipients and share links of reports you set up. Revenue figures from Google Analytics are not shown in the client portal, in client reports or in shared report links unless a workspace owner or admin turns that on for the project. We may also disclose data when the law requires it, to protect the rights and safety of our users or the public, or, with your prior consent for Google user data, as part of a merger or acquisition. We give at least 30 days’ notice of a new subprocessor in the DPA.
11How we store and protect data
- Hosting in the EU: our database runs on Neon in Frankfurt, Germany, and our application and sync servers on DigitalOcean in Frankfurt, Germany.
- Encryption: all traffic uses HTTPS (TLS 1.2 or later). Data is encrypted at rest (AES-256). Google OAuth access and refresh tokens (Search Console and Google Analytics) and BigQuery keys are additionally envelope-encrypted with separate keys before they are stored, and are never shown in the product or written to logs.
- Workspace isolation: every workspace’s data is separated at the database level with row-level security, so one customer’s queries cannot read another customer’s data. Within a workspace, members can be limited to selected projects.
- Access control: production access is limited to the few Codenova staff who operate the service, with two-factor authentication and audit logs. Staff do not read Google user data except as described under Limited Use.
- Account security: passwords are stored as salted hashes, sign-in attempts are rate-limited, and you can turn on two-factor authentication.
- Backups: encrypted backups are kept for up to 35 days.
No system is perfectly secure. If a breach affects your personal data, we will tell you without undue delay and as required by law.
12Retention and deletion
We keep data only as long as it is useful to you or required by law:
When you delete a project, a workspace or your account, the data is removed from our live database immediately and from our encrypted backups within 35 days. Disconnecting Google stops all further access and daily syncs; data already imported stays in your projects until you delete them, so you can keep your history, or ask us to delete it. Deleting your account deletes every workspace in which you are the only member, with all of its projects and data, revokes their Google connections and cancels their subscriptions.
13Revoking access and deleting your data
- Revoke Google access: open your Google Account → Security → Your connections to third-party apps & services (https://myaccount.google.com/permissions), select Serplyze and remove its access. Serplyze can then no longer read any Google data.
- Disconnect in Serplyze: Settings → Search Console → Connected Google accounts → Disconnect. We revoke the token at Google and delete it.
- Disconnect Google Analytics in Serplyze: Settings → Integrations → Google Analytics 4 → Disconnect. We delete the token and all stored Google Analytics data at once and revoke Serplyze’s access at Google, unless the same Google account still connects Search Console (then remove access at https://myaccount.google.com/permissions if you want to stop both). Unlinking a single project deletes that project’s Google Analytics data.
- Delete a project: Settings → Project → Delete project, with the option to disconnect its Google account too.
- Delete your account: Settings → Profile → Delete account. This deletes your account and the workspaces you alone belong to.
- Ask us: write to info@serplyze.com from your account’s email address to request access, export, correction or deletion of your data. We confirm within five working days and complete requests within 30 days.
14Cookies
The signed-in app uses only first-party cookies that keep you signed in, protect sign-in flows and remember choices such as your active workspace, plus an optional campaign cookie described above. On the public pages of serplyze.com and on the sign-in and sign-up screens, Google Analytics, Microsoft Clarity and the Meta Pixel also set analytics and advertising-measurement cookies; they are not loaded inside the app. Sign in with Google and Stripe’s payment page set their own cookies under their own policies. Details: Cookie policy (https://serplyze.com/legal/cookies).
15Your rights
Depending on where you live, you have some or all of these rights, and we honour them for every user:
- access the personal data we hold about you and receive a copy in a portable format;
- correct inaccurate data;
- delete your data;
- restrict or object to processing, including processing based on our legitimate interests;
- withdraw consent at any time, without affecting earlier processing;
- not be discriminated against for exercising your rights.
EEA, UK and Swiss residents (GDPR / UK GDPR) may also complain to their local data protection authority. California residents (CCPA/CPRA): in the past 12 months we collected the categories identifiers, commercial information (billing), internet activity (usage data) and the Search Console data described above, for the business purposes in this policy; we do not sell or share personal information for cross-context behavioural advertising and do not use sensitive personal information to infer characteristics. You or an authorised agent can make a request at info@serplyze.com; we verify requests by confirming control of your account’s email address.
16International transfers
Codenova, LLC is based in the United States; your data is stored in the EU. Some subprocessors (Resend, Stripe, OpenAI, Google, and Cloudflare’s global network) process data in the United States or other countries. For transfers of personal data from the EEA, the UK or Switzerland we rely on the EU–US Data Privacy Framework where the recipient is certified, or on the European Commission’s standard contractual clauses (with the UK addendum), together with the safeguards described in this policy.
17Children
Serplyze is a business tool and is not directed to children. You must be at least 16 years old to use it. We do not knowingly collect personal data from children; if you believe a child has given us personal data, write to info@serplyze.com and we will delete it.
18Changes to this policy
We may update this policy when our product or the law changes. The current version and its effective date are shown on this page, together with a version history. We will notify account owners by email at least 14 days before a material change takes effect, and we will ask for your consent before using Google user data in a way not described here.
19Contact
Codenova, LLC, 30 N Gould St, STE R, Sheridan, Wyoming 82801, United States. EIN 30-1441589.
Privacy questions and requests: info@serplyze.com. Support: info@serplyze.com.
Effective date: Oct 26, 2026 (version 4.5).
Version history
PrivacyWho operates Serplyze
Serplyze is a product of Codenova, LLC, 30 N Gould St, STE R, Sheridan, Wyoming 82801, United States. EIN 30-1441589.
Questions about your data?
Write to our privacy team. We answer within five working days and handle access and deletion requests within 30 days.
info@serplyze.com