Privacy Policy
Last updated 18 November 2026
This policy explains what ContenderMap (contendermap.com) collects about you, why, who else processes it, how long we keep it and what you can ask us to do with it. The short version: we collect what we need to run your analyses and your account, we don’t run ads or tracking, and we don’t sell your data.
Who we are
ContenderMap is run by [Company legal name], [Registered address, country] (registration [Company registration number]). We are the controller of your personal data. For anything in this policy, write to [contact email, e.g. [email protected]].
What we collect
Your account
- Your email address and name.
- Your password, stored only as a one-way hash. If you sign in with Google, we instead receive your Google account ID, email address and name from Google.
- When you created the account, when you last used it, whether your email address is confirmed, and your plan.
What you put into an analysis
- Your product description, website or app store links, markets, your answers to the questions we ask, competitors you add or remove, name ideas and positioning copy you write.
- The results we produce from it: competitors, features, pricing, reviews, positioning, brand, store listing and name checks, and the weekly watch if you turn it on.
Please don’t put personal data about other people, or confidential information you are not allowed to share, into an analysis.
Payments
If you subscribe, Stripe handles the payment. We never see or store your card details. We keep your Stripe customer and subscription IDs and the subscription’s status (for example active or cancelled).
Newsletter
If you sign up for news, we keep your email address, when you gave consent, when you confirmed it and whether you unsubscribed. Sign-ups that are never confirmed are deleted after 30 days.
Technical data
- Two session cookies that keep you signed in (see Cookies below), and sign-in, email confirmation and password reset tokens, stored only as hashes.
- Server logs with your IP address, browser and the pages requested. We use them to keep the service secure, stop abuse and fix errors.
We don’t use analytics, advertising or tracking tools, and we don’t build profiles of you.
Why we use it, and on what legal basis
- To provide the service you asked for (performance of our contract with you): your account, running analyses, share links, billing, and emails you need such as account confirmation, password reset and the weekly watch digest.
- To keep the service safe and working (our legitimate interest): rate limits, abuse prevention, security and fixing errors.
- To send news (your consent), which you can withdraw at any time with the unsubscribe link in every email.
- To meet legal obligations, such as keeping payment and tax records.
Who processes it for us
These providers process data on our behalf, under contracts that limit them to doing so:
- Amazon Web Services: hosting, database, backups and sending email. Our servers are in Stockholm, Sweden (EU).
- Cloudflare: DNS, and delivering the site to your browser.
- Anthropic: the AI that reads sources and writes the analysis. It receives what you put into an analysis together with public information about competitors. Under its commercial terms, Anthropic does not use this data to train its models.
- DataForSEO: web and app store search. It receives search terms built from your product description.
- Stripe: payments and invoices, if you subscribe.
- Google: sign-in, only if you choose Sign in with Google.
To find and compare competitors we also read public sources such as competitors’ websites, the App Store, Google Play, Product Hunt, Hacker News and public review sites. We send them search terms and requests, never your account details.
Some of these providers are based outside the European Economic Area, mainly in the United States. Where data leaves the EEA, it is protected by the EU Standard Contractual Clauses or the EU-US Data Privacy Framework.
We don’t sell or rent your data, and we don’t share it with anyone else except where the law requires it.
Share links
If you create a share link for an analysis, anyone with the link can see that analysis, and, if you allow it, the first signed-in person to open it can take it over into their own account. You can revoke a link at any time, after which it stops working.
How long we keep it
- Your account and your analyses: until you delete them. Deleting your account (on the Account page) deletes your analyses, share links, settings and weekly watches, and cancels any subscription straight away.
- Database backups: up to 30 days, after which deleted data is gone from them too.
- Server logs: up to 30 days.
- Payment records: as long as tax and accounting law requires, which is several years. Stripe keeps its own records under its privacy policy.
- Newsletter: until you unsubscribe; unconfirmed sign-ups for 30 days.
Your rights
Under the GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, and receive it in a portable format. You can withdraw consent to news at any time. You can delete your account yourself on the Account page. For anything else, email [contact email, e.g. [email protected]]; we answer within one month.
You can also complain to the data protection authority in your EU country, or in [country], where we are established.
Cookies and local storage
We use two cookies, contendermap_at and contendermap_rt, that keep you signed in. They are strictly necessary, can’t be read by the page’s scripts and are removed when you sign out. We also remember whether you chose the light or dark theme in your browser’s local storage. There are no advertising, analytics or third-party cookies, which is why we don’t show a cookie banner. If you use Sign in with Google or pay with Stripe, those services set their own cookies on their pages.
Children
ContenderMap is not meant for anyone under 16, and we don’t knowingly collect their data.
Security
Traffic is encrypted with HTTPS, passwords are hashed, sign-in tokens never reach the page’s scripts, stored integration keys are encrypted, and access to the servers is limited to the people who run them.
Changes
If we change this policy, we update the date at the top. If a change matters for how we use your data, we tell you by email before it applies.