Skip to content
DeployFlare
Legal

Privacy Policy

Last updated 8 October 2026

DeployFlare ("we", "us") operates the deployflare.com website and the SEO platform behind it, from India. This policy explains what we collect, why we collect it, who we share it with, and what you can ask us to do about it. It is written in plain language and is not a substitute for legal advice.

Who this covers

This policy applies to three groups of people, and not every section applies to all of them:

  • Visitors to our marketing pages and the free rank checker, who never create an account.
  • Customers who hold an account and use the platform.
  • Your clients, whose websites and keywords you track, and who may receive a white-label report from you.
  • People your workspace contacts or lists: your customers who receive a review request, journalists in your media contacts, businesses in lead finder results, and people who message an agency through our directory or a lead widget.

Where you use DeployFlare to process data about your own clients, you decide what goes in and why. You are the controller of that data and we process it on your instructions.

What we collect

Information you give us

  • Account information: your email address, and your name if you provide one.
  • Waitlist: the email address you leave on the waitlist page. We use it only to invite you when your account is ready, and delete it if you ask.
  • Billing information: billing country (the country of your IP address at your first checkout, used to set your currency and how tax applies), billing state, and GSTIN if you supply one for tax invoices. Card and UPI details go to our payment processor and never touch our servers.
  • Content you enter: the domains, keywords, locations, competitors and projects you track, plus any client names or branding you add to reports.
  • Support correspondence: whatever you write to us, and our replies.

Information we collect automatically

  • Technical data: IP address, user agent, browser and device type. We use these for security, abuse prevention and per-IP rate limiting on the free tools.
  • Log data: requests to our servers, errors and timing, retained for debugging and security.
  • Analytics data: see the analytics section below.

Information from connected services

Every connection is optional and starts only when you sign in to that service from DeployFlare. Depending on what you connect, we receive:

  • Google: Search Console performance data, Google Analytics 4 reports, your Business Profile locations, posts, reviews and performance, files the app creates in your Google Drive (Sheets and Docs exports), and Google Ads results. The Google section below covers this in detail.
  • YouTube: your channel's views and subscribers, and permission to upload Shorts you schedule.
  • Meta, LinkedIn, X, Threads, Pinterest, TikTok and Bluesky: permission to publish the posts you schedule, and your accounts' followers, engagement, reach and post figures. For Meta, also your ad accounts' campaign results and permission to create paused campaigns you push.
  • WordPress, Mailchimp, HubSpot and Microsoft Advertising: what that connection's button in Settings says it unlocks, such as campaign results or contacts and deals counts in client reports.

We encrypt every access token before we store it, using a key held outside the database. Disconnecting in Settings, Integrations deletes the token. Figures from social platforms are kept only as long as each platform's terms allow, and Business Profile insights for 30 days.

Google user data

Connecting Google Search Console is optional. Nothing in this section happens unless you start that connection yourself.

Each Google connection asks for only the permission its feature needs, and only when you connect that feature:

  • Search Console (webmasters.readonly): read your properties and their search performance. We cannot change anything in Search Console.
  • Google Analytics 4 (analytics.readonly): read sessions, conversions and revenue per landing page.
  • Business Profile (business.manage): read and edit your profiles, publish posts you approve, and post review replies you approve or that you've consented to automate.
  • Sheets and Docs (drive.file): create files when you export, and reach only the files DeployFlare created. We cannot see the rest of your Drive.
  • Google Ads (adwords): read campaign results for client reports.
  • YouTube (youtube.readonly, yt-analytics.readonly, youtube.upload): read your channel's figures, and upload Shorts you schedule.

We do not ask for access to your Gmail, Calendar or contacts. We use Google data to show it back to you inside DeployFlare, to carry out the actions you ask for, and to include it in reports you generate.

DeployFlare's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We limit our use of Google user data to providing and improving the user-facing features that are visible in DeployFlare.
  • We do not transfer Google user data to advertisers, data brokers or information resellers.
  • We do not use Google user data for advertising, credit decisions or any similar purpose.
  • We do not allow humans to read Google user data, except with your explicit consent for a specific issue you have raised with us, where security or abuse requires it, where the law requires it, or where the data has been aggregated and anonymised.

Your Google access and refresh tokens are encrypted before they are stored, using a key held outside the database. You can disconnect any Google connection at any time in Settings, Integrations, or Search Console from its own page. Disconnecting deletes our token and stops any further access. You can also revoke DeployFlare independently from your Google account permissions page.

Analytics and cookies

We use a small number of cookies and three analytics tools.

Essential cookies

These are required for the service to function and cannot be switched off:

  • Session cookie (authjs.session-token): keeps you signed in. Expires after 30 days.
  • OAuth state cookies (df_gsc_state, df_gsc_next, df_connect_pkce): short-lived anti-forgery values used only while you connect a service.
  • Two-factor cookie (df_2fa): if you turn on two-factor sign-in, it records that this browser passed the check. It lasts 30 days.
  • Workspace cookies (df_org, df_invite): remember which workspace you last opened, and an invitation you're accepting. They last up to a year.

Vercel Web Analytics

We use Vercel Web Analytics to understand which pages people visit. It sets no cookies. Visitors are identified by a hash derived from the incoming request, and that hash is discarded after 24 hours. Each data point may record the timestamp, the URL and route pattern, the referrer, filtered query parameters, approximate geolocation to city level, operating system, browser, and device type. It does not store your IP address and cannot follow you to other websites.

Vercel Speed Insights

We also use Vercel Speed Insights to measure how fast pages load for the people actually loading them. It sets no cookies and stores no identifier. Each measurement carries the route, the performance timings your browser reports, and coarse details such as device type and connection speed. We read it to find slow pages, and it cannot follow you to other websites.

Google Analytics

We use Google Analytics 4 to measure how people find and move through the site. It does not load until you accept it in the cookie notice, and nothing reaches Google before you do. Accepting sets a pair of cookies whose names start with _ga. They hold a pseudonymous identifier for your browser so Google can recognise return visits, and they last up to two years. Google processes this data as our service provider, and may use its own infrastructure across multiple countries to do so.

We grant Google Analytics permission to store analytics cookies and nothing else. Advertising storage, ad personalisation and Google signals stay switched off, so we cannot use your visit to build an advertising profile.

We record page views, how far down a page you scroll, and a handful of actions: a run of the free rank checker, a waitlist signup, a new account finishing setup, a contact form, and a sign-in. Google deletes event and user data after 14 months.

Change your mind at the foot of this page. Choosing "Essential only" stops collection and expires the _ga cookies. We store your choice in your browser's local storage under the name df-consent, which is not a cookie and never leaves your device. You can also opt out across all sites using Google's browser add-on.

White-label client reports carry no analytics at all. A report opened from a share link loads none of the three tools above, so your client's visit stays between you and them.

We do not run advertising or retargeting pixels, and we do not sell or share personal data for behavioural advertising.

How we use your information

  • To deliver the toolkits you use: rank tracking, research, audits, backlinks, AI visibility, local, content, advertising, social, PR, traffic research and reporting.
  • To carry out actions you ask for in connected services, such as publishing a post, replying to a review or sending a review request or pitch.
  • To create and secure your account, and to sign you in.
  • To take payment and issue invoices.
  • To send service messages such as sign-in links, rank alerts and billing notices.
  • To detect abuse, enforce rate limits and keep the platform available.
  • To understand aggregate usage so we can decide what to build next.
  • To meet our legal and tax obligations.

Where the GDPR applies, we rely on performance of a contract for delivering the service and taking payment, legitimate interests for security, abuse prevention and product analytics, consent for non-essential analytics cookies and for connecting Google Search Console, and legal obligation for tax records.

Search data and our shared cache

Rank tracking works by pulling public search results. To keep the price low, we cache those results and key the cache by the search itself, meaning the keyword, location, language and device, and never by who asked for it. When two customers track the same keyword in the same place, one pull serves both.

That cache holds public search engine results. It does not hold your account details, your project structure or anything that identifies you, and no customer can see what another customer tracks.

People you contact through DeployFlare

Some tools hold data about people outside your workspace. You decide who goes in, and you must have a lawful reason to contact them.

  • Review requests: the names, phone numbers and email addresses of customers you upload or add. We send each request by the channel you choose, never ask the same person twice in 30 days, and keep a record of anyone who opts out (STOP replies, unsubscribe links) so later imports can't message them again.
  • Media contacts and pitches: journalists' names, outlets and email addresses you import or add. Discovery reads bylines on public pages about your topic and finds names and outlets, never email addresses. Every pitch carries an unsubscribe link, and we record opens, clicks and bounces to show you pitch analytics.
  • Lead finder: public Google Maps business listings and a quick check of each business's public website.
  • Agency directory and lead widget: a message sent to an agency through its listing or its lead widget goes to that agency, and we keep a copy in its leads inbox.

Browser extension

DeployFlare SEO for Chrome stores your extension token, one setting and a one-day cache of site numbers in your browser. On Google results pages it sends the hostnames of the results (for example example.com) and your token to deployflare.com, to show each site's numbers. It doesn't send your search query, full result URLs, your browsing history or the content of any page. The page audit runs in your browser; to check robots rules it requests the audited site's own robots.txt and the page's headers, and sends nothing to us. We keep a count of how many sites you looked at each day (to apply the daily allowance) and the numbers we fetched for each site, which we share with every workspace because they describe public websites, not you. Disconnect the extension in its settings or in DeployFlare, Settings, App and extension, and the token stops working.

If you turn on push notifications in the installable app, your browser's push service (run by Google, Mozilla or Apple, depending on your browser) delivers our ranking alerts to your device.

Crawling your websites

When you run a site audit, our crawler visits the pages of the domain you entered and records what a search engine would see: status codes, titles, headings, metadata, links and page performance. Only run audits on sites you own or are authorised to audit. Our crawler respects a reasonable request rate and identifies itself in its user agent.

Who we share data with

We do not sell your personal data. We share it with the service providers we need to run DeployFlare, each handling only what their function requires:

  • Vercel (United States): website and application hosting, plus Vercel Web Analytics.
  • Neon (serverless Postgres): the primary database holding accounts, projects and tracking data.
  • Upstash (Redis): caching, rate limiting and queue state.
  • DataForSEO: our main data provider. It supplies search results, keyword, backlink, business listing, review and news data, and asks the AI engines (ChatGPT, Google AI Mode and AI Overviews, Gemini, Perplexity and Claude) the prompts you track. We send it keywords, domains, business names, prompts and the location and language. We do not send it your identity.
  • Resend: email. It sends sign-in links, alerts and reports to you, and the review requests, pitches and outreach emails you send to others, so it receives those recipients' email addresses and the message. For pitches it reports opens and clicks back to us.
  • Razorpay: payment processing and subscriptions. It receives your billing and payment details directly.
  • Google: the connections you choose (see above), Google Analytics, and PageSpeed Insights, which receives the page addresses of sites you audit.
  • SearchAPI: a backup for AI answers when DataForSEO can't answer. It receives the prompt, not your identity.
  • OpenRouter: routes our AI features to AI models, including Anthropic's Claude. It receives the text each feature needs: AI answers to analyse, and the facts, drafts and notes you write when you ask for a post, a review reply, a pitch, an ad, a brief, an edit in the content editor or a report summary. It does not receive your identity.
  • Apify: reads public profile and post figures of the social accounts you track as competitors or creators. It receives the account handle, not your identity.
  • Copyscape: checks the text you submit for an originality check against the web.
  • fal.ai: makes the images for AI articles. It receives a one-line description of the image, not your identity.
  • WordPress and Google Docs: receive an article when you publish or export it there, through the connection you set up.
  • MSG91 and Twilio: send review requests by SMS. They receive the recipient's phone number, name and the message.
  • Meta (WhatsApp): sends review requests by WhatsApp. It receives the recipient's phone number, name and the message.
  • Social networks you connect (Meta, LinkedIn, X, Threads, Pinterest, TikTok, Bluesky, YouTube, Google Business Profile): receive the posts, photos and videos you publish to them.
  • Vercel Blob: stores images and videos you upload for posts and reports.
  • OpenFreeMap: serves the map tiles on Local rankings. Your browser loads them straight from OpenFreeMap, through Cloudflare's network, so they see your IP address and which part of the map you're looking at. OpenFreeMap sets no cookies.
  • Sentry: error monitoring. Error reports may include a request path and an organisation identifier.

We also disclose data where the law requires it, where we must defend a legal claim, or where we need to protect the platform or another person from harm. If DeployFlare is ever acquired or merged, account data would transfer as part of that transaction, and we would tell you before it happened.

Where your data goes

DeployFlare is operated from India, and several of the providers above store and process data in the United States, the European Union and elsewhere. When personal data leaves its country of origin, we rely on our providers' standard contractual clauses and equivalent safeguards.

How long we keep things

  • Account and project data: for as long as your account is open, and for 90 days after you close it, so you can change your mind.
  • Billing and tax records: eight years, as Indian tax law requires.
  • Search result cache: short-lived and rotated continuously. It is keyed by search, not by person.
  • Social and Business Profile figures: as long as each platform's terms allow (Business Profile insights 30 days).
  • Opt-outs from review requests and pitches: kept while your workspace exists, so we can keep honouring them.
  • Server and security logs: up to 90 days.
  • Analytics data: as configured in Vercel and Google Analytics, at their respective defaults.
  • Support email: up to two years after the conversation ends.

After those periods we delete the data or anonymise it beyond re-identification.

Your rights

Whatever country you are in, you can ask us to give you a copy of your data, correct it, delete it, or stop a particular use of it. Email us and we will respond within 30 days.

If you are in India, the Digital Personal Data Protection Act 2023 gives you the right to access and correct your data, to have it erased, to nominate someone to exercise your rights if you cannot, and to complain to the Data Protection Board of India.

If you are in the EEA or the UK, the GDPR gives you the rights to access, rectification, erasure, restriction, portability and objection, the right to withdraw consent at any time, and the right to complain to your local supervisory authority.

You can close your account and request deletion at any time. Some records survive deletion where tax law requires us to keep them.

Security

Traffic runs over TLS. Passwords are not stored, because we do not use them: sign-in is a one-time email link or Google. Every customer's data is isolated at the database level by row-level security, so one organisation's queries cannot reach another's rows. Access tokens for connected services are encrypted at rest. Two-factor sign-in with an authenticator app is available to every account. Secrets stay on the server and never reach the browser.

No system is perfectly secure. If a breach affects your personal data, we will notify you and the relevant authority as the DPDP Act and, where it applies, the GDPR require.

Children

DeployFlare is a business tool and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has given us data, email us and we will delete it.

Changes

We will update this policy as the product changes. The date at the top always reflects the current version. When a change materially affects your rights, we will email account holders before it takes effect.

Contact

Email hello@deployflare.com with any privacy question, or to exercise any of the rights above.