Privacy notice

Who we are

PipelineMap is operated by Seeded Health Ltd (“we”, “us”). We are the controller of the personal data described in this notice. Contact us at hello@pipelinemap.co.uk.

What we collect and why

• Opportunity Scanner. The domain you enter and the report we generate from that website's public pages. We use this to show you the report you asked for, to protect the scanner from abuse, and to understand which kinds of websites use it. Lawful basis: legitimate interests — namely providing the free report you requested, keeping the service secure, and improving what we offer to businesses like yours. This is balanced against your interests: the scanner only reads pages that are already public, and we don't build profiles of individuals.
• Follow-up requests and pilot applications. Your email address, name, role, company size, website and any message you send. We use this to reply to you and assess whether PipelineMap is a fit. Lawful basis: legitimate interests, or steps prior to entering a contract.
• Marketing emails. Only if you tick the consent box and then confirm using the link we email you. Up to three emails about your report, commercial search and PipelineMap. Lawful basis: consent, which you can withdraw at any time using the unsubscribe link.
• Accounts. Your name, email address, company name and a securely hashed password (we never store your password itself). Lawful basis: contract.
• Search Console data. If you connect Google Search Console or upload an export, we store search performance data (queries, pages, clicks, impressions, positions) for the properties you choose, plus an encrypted access token. We use it only to provide PipelineMap to you. Lawful basis: contract.
• Payments. Payments are handled by Levy & Loom, our payment gateway, which uses Stripe to take the payment. We receive confirmation of payment and the amount, but never your card details.
• Reading your own pages. When a page on a website you've added is involved in an opportunity we've found, we fetch that page and record what's on it — the title, headings, visible text, calls to action, links and whether it allows indexing — so we can tell you whether the page actually answers what searchers want. We only read pages on websites you've added, we honour your robots.txt, and we identify ourselves in the request. We don't read anyone else's website on your behalf. Lawful basis: legitimate interests — namely giving you an accurate analysis of your own site, balanced against your interests by limiting this to your own pages, a handful per analysis, and no more often than once a fortnight.
• Reading other companies' public pages. To tell you what buyers are being offered elsewhere, we sometimes read the public pages of competitors you have named or whose names appear in your own search data. We read what any visitor sees, honour their robots.txt, identify ourselves, and stop if a site blocks us. We do not read anything behind a login and we never try to get around a block. Lawful basis: legitimate interests — giving you an accurate picture of your market, balanced by keeping this to a handful of public pages and recording what we could not see.
• Commercial outcomes you send us. If you connect a source of signups, leads, demos or sales, we store the events it sends — what kind, when, and where supplied the page, search term, quantity and value. We never require a value and never estimate one. You choose what to send; we do not read your CRM. Lawful basis: performance of our contract with you.
• Approvals. When you approve, defer or decline a change we have prepared, we record which account made that decision and when, so the history of what was agreed is complete.
• What you tell us about a change. When you record that you've implemented a recommendation, we store what you said you did and the date you gave, so we can compare the search data before and after. This is your own statement, kept as such. Lawful basis: performance of our contract with you.
• Usage analytics. We record page views and key product events (such as a scan being completed) using a daily-rotating, one-way identifier derived from your IP address and browser. We don't set analytics cookies, don't store your IP address and can't link visits across days. Lawful basis: legitimate interests — namely understanding whether the product and its pages work, and detecting abuse, using the least identifying method available. This is balanced against your interests: the identifier is one-way, rotates daily and can't be used to contact or track you.

Cookies

We use one strictly necessary cookie to keep you signed in, and a short-lived cookie to protect the Google connection process. We don't use advertising or analytics cookies.

Google user data

PipelineMap requests read-only access to Google Search Console (webmasters.readonly) and your Google account email address. We use this data solely to analyse search performance for the websites you add to PipelineMap, and to show you the results in your account.

• Access. Read-only, for the properties you choose. PipelineMap cannot change anything in your Google account. Your access token is encrypted (AES-256-GCM) before it is stored.
• Storage. The search performance figures we import (queries, pages, clicks, impressions, positions) are stored in our database in Ireland while your account is open.
• Sharing. We don't sell this data, use it for advertising, or transfer it to anyone except the providers listed above who host and run the service for us.
• Human access. People at PipelineMap only look at it when you ask us for support, or where it is necessary for security, to investigate abuse, or to meet a legal obligation.
• No AI training. This data is never used to develop, improve or train artificial intelligence or machine-learning models.
• Your control. Disconnect at any time from the Data sources page, or revoke access in your Google account settings. Deleting the website or your account removes the imported data.

PipelineMap's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who processes your data for us

These are the only providers that handle data for PipelineMap. They act on our instructions and may not use your data for their own purposes. We don't sell personal data.

• DigitalOcean — hosting for the application. Our app runs in DigitalOcean's London (LON1) region, behind Cloudflare's network, which serves and protects the site.
• Turso — the database that stores accounts, sites, search data and reports. Our database is located in Ireland (AWS eu-west-1).
• Resend — sending transactional email, such as confirmation and password-reset messages. We use Resend's Ireland (eu-west-1) region.
• Levy & Loom — our payment gateway, operated by Seeded Health Ltd. It handles checkout, refunds and payment records for PipelineMap.
• Stripe — payment processing, used by Levy & Loom to take the payment. Stripe handles card details directly; we never receive them.
• Google — Search Console, when you choose to connect it. Google processes that data as your own provider; we read it with your authorisation.

PipelineMap does not use artificial intelligence or machine-learning services to process your data or your Google Search Console data. The analysis is produced by our own deterministic software, and your data is never used to train any model.

Where your data is processed

Your data is stored in the United Kingdom and Ireland, as set out above. The companies behind these services are based in the United States, so their staff may access data from outside the UK for support, security and administration. Where that happens, the transfer is governed by the data protection terms in our contract with each provider, which use the UK International Data Transfer Addendum to the European Commission's standard contractual clauses, or another mechanism permitted under UK data protection law.

You can ask us which mechanism applies to a specific provider by emailing hello@pipelinemap.co.uk.

Retention

• Scanner reports: up to 12 months.
• Follow-up requests and pilot applications from people who don't become customers: up to 24 months after you submit them, unless you ask us to delete them sooner. Customers' records are kept while they are customers.
• Copies of emails we send: up to 6 months; unsent queued emails are removed after 3 months.
• Usage analytics events (pseudonymous, no IP addresses): up to 24 months.
• Account and Search Console data: for as long as your account is open. We keep the raw imported rows for your eight most recent imports of each website; older raw rows are removed automatically when a new import replaces them, while the findings stay until the website or account is deleted.
• Records of what we observed at each analysis: up to 24 months. These are small summaries — a date, a priority, and the clicks, impressions and position at that moment. They are what lets us tell you whether something improved after you changed it, and they are deleted automatically once they pass 24 months.
• Pages we have read on your own website: the most recent reading of each page, refreshed at most every 14 days, kept until the website or account is deleted.
• Deleting a website, or your account in Account settings, removes that data from our systems immediately. Backups held by our infrastructure providers expire on their own schedules.
• Unsubscribe records: kept so we can continue to honour your choice.

How the time limits are applied

The periods above are maximums. A scheduled clean-up job deletes data once it passes them. If you want something removed sooner, email hello@pipelinemap.co.uk and we'll do it manually.

Security

Passwords are hashed with scrypt, session tokens and reset tokens are stored only as hashes, and Search Console tokens are encrypted at rest with AES-256-GCM. Access to production data is restricted.

Your rights

Depending on where you live, you can ask to access, correct, delete or export your personal data, object to or restrict processing, and withdraw consent. Email hello@pipelinemap.co.uk. If you're in the UK you can also complain to the Information Commissioner's Office (ico.org.uk).