Legal

Privacy Policy

Last updated 18 October 2026

Introduction

GrowthHasten (“we,” “our,” or “us”) respects your privacy and is committed to protecting your personal data. This privacy policy explains how we collect, use, store, share and protect your information when you visit growthhasten.com, use the GrowthHasten product at app.growthhasten.com, or contact us.

It applies to the GrowthHasten website, the GrowthHasten product and its account system, the Hasten LinkLens browser extension, and any Google account you choose to connect to the product.

The GrowthHasten Product

You can start using the GrowthHasten product at app.growthhasten.com on the free plan, which covers one website of up to 500 pages. The free tools on growthhasten.com (the Website SEO Checker, the AI Humanizer and the Hasten LinkLens browser extension) need no account at all.

The rest asks you to sign up, and we want to be direct about why: it is for authentication. Creating an account asks for a name, an email address, a password and the domain you want analyzed, and nothing else. There is no company size question, no phone number and no request for payment details. You may also sign in with your Google account instead of setting a password.

The domain is on that form because it is what the product runs against. You are giving us a website address so we can read the pages it already publishes in public, analyze them, and show you a complete audit of that site’s technical health, content and performance. Your results are then saved to your account so you can reopen an audit and compare it against the next one instead of starting over.

We do not sell that data. We do not share it with advertisers or data brokers. We do not use it to build a marketing profile of you, and we do not analyze websites nobody has asked us to analyze.

Google Account Connections: Search Console And Analytics

GrowthHasten can connect to your Google Search Console and Google Analytics 4 accounts. A public crawl tells us what a page says. It cannot tell us what that page actually does in search: which queries it wins, where it is slipping, or what visitors do after they land. Connecting Google is what turns a static audit into a prioritized one.

The connection is optional, it is never made automatically, and the product works without it. You start it yourself from inside the app, and Google shows you a consent screen listing exactly what you are granting before any data reaches us. We request read-only scopes only. We cannot create, change or delete anything in your Google account, and we cannot see any Google service you have not granted.

The scopes we request, and what each one is for

Sign in with Google (openid, userinfo.email, userinfo.profile): used only to create and authenticate your GrowthHasten account. We receive your name, email address and profile picture, and we use them to identify your account, show you who is signed in, and contact you about that account.
Google Search Console, read-only (webmasters.readonly): used to list the properties you own so you can choose one, and to read Search Analytics data for the property you choose. That data is queries, pages, countries, devices, clicks, impressions, click-through rate and average position. We use it to show how your site is genuinely performing in Google Search alongside the technical audit of that same site.
Google Analytics, read-only (analytics.readonly): used to list the GA4 properties you have access to so you can choose one, and to read report data for the property you choose. That data is sessions, users, traffic channels, landing page performance and any conversion events you have configured. We use it to connect search visibility to what visitors actually do after they arrive.

How We Use Google User Data

We use the data we read from Google Search Console and Google Analytics for one purpose: to produce the reports and recommendations you asked the product to produce, for the property you selected, for you. Specifically, we use it to:

Show your live search performance next to the technical audit of the same site, so a finding can be weighed against the traffic it actually affects
Identify pages and queries that are losing clicks, impressions or average position over time
Prioritize audit findings by the pages that carry real traffic, instead of by raw severity alone
Recommend content topics and page improvements based on queries the site already ranks for
Save the resulting reports to your account so you can reopen them and compare one period against another

Limited Use Of Google User Data

GrowthHasten’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms, that commitment means all of the following, and we hold to it whether or not anyone is checking:

We do not sell, rent or license Google user data to anyone, and we never transfer it to data brokers, information resellers or advertising networks.
We do not use Google user data for serving advertisements, including retargeting, personalized advertising or interest-based advertising.
We do not use Google user data to determine creditworthiness or for any lending purpose.
We do not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models. Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models.
We do not allow humans to read your Google user data, except where you have given us explicit permission to look at a specific report in order to support you, where it is necessary for security purposes or to comply with applicable law, or where the data has been aggregated and anonymized so that it is no longer linked to you or to your site.
We do not use one customer’s Google user data to produce another customer’s report, and we do not pool it into any shared dataset.
We transfer Google user data only where it is necessary to provide the features you are using, where the law requires it, or as part of a merger, acquisition or sale of assets, and in that last case only with prior notice to you.

Google User Data And Artificial Intelligence

We want to be exact here, because a vague answer is worth less than an honest one. Some of the explanations, recommendations and drafts in the product are written by a large language model, which we use through a provider under terms that prohibit training on anything submitted to it. Everything it writes is labeled in the product as AI-written. Depending on the feature, it receives the findings being explained, the content of the page a draft is for (including images, when drafting image descriptions), and the answers you gave about your business. Where a recommendation concerns your search or analytics performance, the relevant figures from your connected Search Console or Analytics property are sent to that model so it can write an explanation specific to your site rather than a generic one.

That happens only when you run a report that needs it, and only for the property you selected. We use the model provider under terms that prohibit the use of data submitted through their API to train or improve their models. We do not train any model of our own on Google user data, and we do not contribute Google user data to any generalized or non-personalized model, as stated in our Limited Use commitment above.

If you would prefer that your Google data never reaches a model provider, do not connect your Google account. Every part of the product that does not depend on a Google connection stays available to you.

Disconnecting Google And Deleting Your Data

You can disconnect a Google account from GrowthHasten whenever you like, and you do not need to contact us or explain why.

In the product: open your account settings and disconnect Google Search Console or Google Analytics. We delete the stored refresh token for that connection immediately, and we delete the Search Console and Analytics data cached against it.
From your Google account: go to myaccount.google.com/permissions, select GrowthHasten and remove access. That revokes our token at Google’s end straight away, and no further request we make can succeed.
Deleting your account entirely: open Settings in the product and delete your account. Running analyses are canceled and the account, its websites, its Google connections, the stored tokens and every report held under it are deleted. You can also write to support@growthhasten.com and we will do it for you within 30 days.

How We Protect Your Data

We apply technical and organizational measures appropriate to the sensitivity of what we hold, and we apply the strictest of them to Google user data and to the credentials that can reach it.

Technical measures

Encryption in transit: every connection to growthhasten.com, to app.growthhasten.com and to the Google APIs uses TLS 1.2 or higher. We serve over HTTPS only and redirect plain HTTP.
Access tokens are never stored: a Google access token is minted for each sync, held only in memory for the duration of that sync, and discarded when it completes. It is never written to disk or to any database.
Refresh tokens are encrypted before storage: the refresh token that keeps a connection alive between visits is encrypted by our application with AES-256-GCM before it is written to the database. Every stored value gets its own random 96-bit initialization vector, and the authentication tag is verified on every read, so a tampered value is rejected rather than used.
Key handling: the encryption key is derived using scrypt from an application secret held in our server environment, never in our source code and never beside the data it protects. It is salted separately per provider, so the key protecting a Search Console connection is not the key protecting an Analytics connection.
Fail closed: if the encryption key is unavailable, the connection is refused outright. A Google token is never written in plaintext as a fallback, under any circumstance.
Encryption at rest: connection records and report data are held in a managed PostgreSQL database that is encrypted at rest, with the encrypted refresh tokens stored as ciphertext inside it.
Server-side sessions: sign-in sessions are stored server-side rather than as stateless tokens, which is what makes it possible to revoke a single session immediately.
Scope minimization: we request read-only Google scopes only, so even a compromise of our credentials could not be used to alter anything in your Google account.

Organizational measures

Access control: access to production systems is restricted to the few people who need it, on a least-privilege basis, and is protected by multi-factor authentication.
No routine human access: our people do not read your Google user data in the normal course of running the service. The only exceptions are the ones listed in our Limited Use commitment above.
Isolation between accounts: every connection and report is scoped to the account that created it, and one customer’s data is never used to serve another.
Vendor review: we review the security posture and data handling terms of the providers we rely on, and we deliberately keep that list short.
Ongoing review: we review our security practices and dependencies regularly, and we patch promptly.

Information We Collect

Information You Provide

Contact information (name, email address, company name)
Messages and inquiries submitted through our contact form or by email

Product Account Information

Your name, email address and a password, used to sign you in
The domain you ask us to analyze
Optional answers about your business, audience, market and objective, used to make topic recommendations relevant
The analyses you run and the reports they produce, saved so you can return to them

Google Account Information, only if you connect it

Your name, email address and profile picture, if you choose to sign in with Google
The Google Search Console properties and Google Analytics 4 properties you can access, so that you can choose which one to analyze
Read-only Search Console performance data for the property you select: queries, pages, countries, devices, clicks, impressions, click-through rate and average position
Read-only Google Analytics data for the property you select: sessions, users, traffic channels, landing page performance and configured conversion events
An encrypted Google refresh token, held so the connection keeps working between visits. Access tokens are not stored at all.

Information Collected Automatically

Device and browser information
IP address and general location data, used to serve pages and, on the pricing page, to choose the currency shown. We do not store it for that purpose
Pages visited, time spent on our website, referral source and interaction data, if you allow analytics cookies
Campaign parameters (such as utm_source) on the link that brought you here, kept in your browser for the session and passed to the sign-up page so we know which campaign worked
If you use the Website SEO Checker at growthhasten.com/tools/website-seo-checker: the address you enter and the snapshot we produce, kept for 30 days so it can carry over if you sign up, and your IP address, counted for one hour to limit abuse. The check reads only public pages of that website

How We Use Your Information

We use the information we collect to:

Sign you in and keep your session secure
Run the analyses you ask for and show you the results
Read your connected Google Search Console and Google Analytics data to produce the reports you requested
Save your reports so you can reopen and compare them
Respond to your questions and support requests
Improve our website, the product and the user experience
Send relevant communications about the product (with your consent)
Comply with legal obligations

What We Never Do

There is a shorter list worth stating plainly. We do not sell personal data, website data or Google user data to anyone. We do not track you across other websites, we run no advertising network and we place no advertising cookies. We do not use Google user data to train generalized AI models. We do not analyze a website unless somebody has asked us to analyze it, and we do not use one customer’s data to serve another.

Hasten LinkLens Chrome Extension

This part of the policy applies to the Hasten LinkLens Chrome extension, version 2.0 and later.

Hasten LinkLens (“the extension”) is a Chrome extension made by GrowthHasten. It checks the links on the web page you are viewing and shows their status and SEO details on that page. The sections below explain what data the extension handles, why, where it is kept, and what leaves your device. In summary:

Hasten LinkLens runs only when you start a check: by clicking its icon, pressing its keyboard shortcut, or using its right-click menu.
Everything it reads is processed inside your browser.
GrowthHasten never receives the pages you check or the links on them. The extension contains no analytics, tracking or advertising code.
To check a link, your browser sends a request directly to that link’s own website. Beyond that, data reaches us only as an ordinary visit when one of our pages opens, such as the welcome page after you install, and those visits never include the address, domain or links of the page you checked (see “Links that open GrowthHasten pages” below).
We do not sell, rent or share user data.

What Data Hasten LinkLens Handles

Website content, read when you start a check

Each link’s address (URL) and its text (anchor text)
The link’s attributes, such as rel (nofollow, sponsored, ugc), target, title and aria-label
The alt text of images inside links
Which part of the page the link sits in, such as the navigation, main content or footer
A short, simplified copy of the link’s HTML, shown in the link’s details view
Whether in-page links (such as #section) point to something that exists on the page
While the panel is open, links the page adds later, such as lazy-loaded sections, are read and checked in the same way.
Hasten LinkLens does not read what you type into forms, and it does not collect the rest of the page’s text.

Web browsing activity

The address of the page you are checking. It is used to tell internal links from external ones, and it appears in exports.
The addresses the page links to. Each one is requested to check it, as described under “What Leaves Your Device When You Use Hasten LinkLens” below.
The check results. These are the HTTP status code, the final address after any redirects, the response time, and the file type the website reports (for example, PDF).
Hasten LinkLens responds to your mouse on highlighted links, when you hover over one or Alt+click it, to show its details. It does not record clicks, mouse movement or keystrokes.

Your settings, saved so Hasten LinkLens can remember them

Domains you asked it to skip
Domains you asked it to check with your cookies
Your “Colour links by” choice: status, follow, or internal and external
Your theme choice (System, Light or Dark). The Settings page also keeps its own copy, so it opens in the right theme.
Whether scan history is on
Where you placed the Hasten LinkLens panel, and whether it is minimized

Scan history (optional, off by default)

If you turn on “Scan history” in Settings, Hasten LinkLens saves the following for each page you check: the page’s address, when it was checked, how many links it had, and the addresses of any links that were broken.
This is used only to show what changed since your last check, for example “2 new broken links, 1 fixed”.
Up to 300 pages are kept, and older records are removed automatically.

Where Hasten LinkLens Keeps Data, And For How Long

Check results stay in your browser’s memory for the tab you checked. They are cleared when you close the Hasten LinkLens panel, close the tab, leave the page, or quit Chrome. To avoid re-checking the same links when you check several pages of one site, results for individual link addresses are also kept in memory for up to 5 minutes. While a panel is open, Chrome’s session memory also holds a note of which tabs have it open, with that page’s address, so the panel can close when the page changes. That note is cleared when Chrome quits.

Settings and scan history are kept on your device, in Chrome’s local extension storage. They are never synced to your Google account or other devices, and never sent to us.

Deleting your data

“Clear history” in Settings deletes your scan history at any time.
Turning “Scan history” off stops new records from being saved.
Uninstalling the extension deletes everything it has stored.

What Leaves Your Device When You Use Hasten LinkLens

Link checks

To find out whether a link works, Hasten LinkLens sends a request from your browser straight to that link’s own website. This is a HEAD request, or a GET request for a single byte when HEAD is refused or does not succeed, and the rest of the response is never downloaded. That website receives the request just as it would if you visited it, including your IP address and browser type.
Checks are sent without your cookies, unless you add the domain under “Check with your cookies” in Settings.
Checks are sent without a referrer, so the website is not told which page the link was found on.
The results come back to your browser only. We never receive them, apart from the one-word summary described under “Links that open GrowthHasten pages”.

“Check with your cookies” (optional)

For domains you list in this setting, Chrome attaches your cookies for that domain to the check. This lets Hasten LinkLens check pages you need to be signed in to see, such as a staging site.
Hasten LinkLens never reads, stores or sends those cookies anywhere; Chrome sends them only to that domain.

Exact redirect codes (optional)

If you turn this on in Settings, Chrome asks you to grant the “webRequest” permission. Hasten LinkLens uses it only to see the redirect steps and network errors of its own link checks.
It ignores every other request, records nothing about your browsing, and never blocks or changes any request.

Links that open GrowthHasten pages

“Start Free Website Audit” opens app.growthhasten.com in a new tab. The link includes tags that say the visit came from Hasten LinkLens, plus a one-word summary of the check: “scanning”, “broken”, “issues” or “clean”. It never includes the address, domain or links of the page you checked.
Install and uninstall pages: when you first install Hasten LinkLens (not when it updates), it opens a welcome page on growthhasten.com. If you uninstall it, Chrome opens a goodbye page there. The Settings page also links to the Hasten LinkLens page on our site.
These are ordinary visits to our website, covered by the rest of this privacy policy.

Exports and copying

“Export” creates a CSV file on your device, and the “Copy” buttons put text on your clipboard. Both happen only when you click them, and Hasten LinkLens does not send the results anywhere.

Hasten LinkLens Permissions And Why They Are Needed

activeTab: to access the current tab only when you start a check.
scripting: to add the scanner, the highlights and the Hasten LinkLens panel to the page you asked it to check.
Access to http and https sites: to send link checks to whatever websites a page links to.
storage: to save your settings, the panel’s position and optional scan history on your device, and to note in session memory which tabs have the panel open.
contextMenus: to add “Check this link” and “Check links in selection” to the right-click menu.
webRequest (optional): only if you turn on Exact redirect codes, to see the redirect steps of its own checks.

How Hasten LinkLens Uses Data

Hasten LinkLens’s use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Data is used only for Hasten LinkLens’s single purpose: checking the links on the page you are viewing and showing their status and SEO details. We do not:

Sell or transfer user data to third parties
Use user data for advertising, profiling, or any purpose unrelated to checking links
Use or transfer user data to determine creditworthiness or for lending purposes
Have people read user data; we never receive the pages you check or the links on them

How Hasten LinkLens Data Is Protected

The pages you check and the links on them never reach our servers, so we hold no copy of them. What Hasten LinkLens stores on your device is kept in Chrome’s extension storage, which websites and other extensions cannot read. All of its code is bundled in the extension, and none is loaded from anywhere else.

Website Analytics

Browsing growthhasten.com requires no account. If you allow analytics cookies, we use Google Analytics 4 on this marketing site to understand which pages are read and where visitors arrive from, reported to us in aggregate. Google Analytics is not loaded at all until you allow it. When it runs, it sets first-party cookies in your browser and processes your IP address. We also use a privacy-preserving page analytics service run by our hosting provider, which sets no cookies and uses no cross-site identifiers, so it needs no consent.

We do not use either for advertising or remarketing, and neither is combined with the data held in your product account. Standard server connection logs may be processed by infrastructure providers for network delivery and security, and are not cross-referenced to identify individual visitors.

One distinction is worth stating plainly: the Google Analytics running on this marketing site is our own measurement of our own site. It is entirely separate from the Google Analytics data you may choose to connect to the product, which is yours, is read only to serve you, and is covered by the Google sections above.

Cookies

We use a small number of cookies, and none of them follow you around the internet. Non-essential cookies are off until you allow them, and declining is as easy as accepting.

Essential cookies keep the website working and keep you signed in to the product. These cannot be switched off without breaking those functions.
Analytics cookies are set by Google Analytics 4 on growthhasten.com, as described above, and only after you choose “Allow analytics” in the cookie banner. You can change your choice at any time from “Cookie settings” in the footer of every page; withdrawing deletes the Google Analytics cookies.
Your browser also stores your cookie choice and, if you pick one, your preferred currency. These stay on your device and are not sent to us.
If you arrive through a partner’s referral link, a first-party cookie (gh_ref) holds that partner’s code for 60 days, so they are credited if you become a paying customer. It holds nothing else and is not used to track you across other websites.
We set no advertising or profiling cookies, and we do not use cookies to track you across other websites.
You can block or delete cookies in your browser settings, and you can opt out of Google Analytics specifically using Google’s browser add-on at tools.google.com/dlpage/gaoptout.

Your Rights

Depending on your location, you may have the right to:

Access the personal data we hold about you
Request correction of inaccurate data
Request deletion of your account and every report stored under it
Disconnect a connected Google account at any time, from inside the product or from your Google account permissions page
Object to processing of your data
Withdraw consent where processing is based on consent
Lodge a complaint with your local data protection authority

support@growthhasten.com

Data Retention

Reports and project settings are kept while your account exists, because being able to compare this month’s audit against last month’s is the reason they are saved at all. On the Free plan the product keeps the current analysis and the one before it for each website, and prunes older ones automatically; paid plans keep the full history. Delete your account and they go with it.

Google user data is kept only while the connection exists, and only for as long as it supports the reports you have saved. Disconnect the Google account and the stored refresh token is deleted immediately, along with the Search Console and Analytics data cached against it. Delete your GrowthHasten account and everything held under it goes with it. We complete deletion requests within 30 days.

Sign-in sessions are stored server-side rather than as stateless tokens, which is what makes it possible to revoke one.

International Data Transfers

GrowthHasten operates from India. Product data is stored in the Asia Pacific region. This website and some of our providers may process data in other countries, including the United States. Where data is transferred across borders, we rely on providers that offer appropriate safeguards for international transfers, and we require them by contract to process the data only on our instructions.

Children’s Privacy

Our website and product are intended for businesses and professionals. They are not directed at children under 16, and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.

Hasten LinkLens is a tool for website owners and professionals. It is not directed at children under 13.

Payments

Payments are processed by a PCI-DSS compliant payment partner. You enter your card, UPI, netbanking or wallet details in its own checkout, named on the checkout itself. They go directly to that partner and never touch our servers, and we do not store your card. To fill in the checkout we pass your name and email address, and the partner asks for your phone number itself. We receive only what we need to record the payment: what you bought, the amount, currency and date, and the partner's references for the order and payment. The partner's own privacy policy covers what it collects.

Changes To This Policy

We may update this privacy policy periodically to reflect changes in our tools, our processing or our compliance obligations. Any update is posted directly on this page with a revised “Last updated” date. If we ever change how we use Google user data, we will update this page before that change takes effect and notify signed-in users.

If we change how Hasten LinkLens handles data, we will update this page and its “Last updated” date before releasing the change.

Contact Us

If you have any questions about this privacy policy, our handling of Google user data, or our extension practices, please contact us at: