Cookies Policy
Please read this cookies policy carefully as it contains important information on who we are and how we use cookies on our Services. This policy should be read together with our Privacy Policy, which sets out who we are, how to contact us, what data is collected, how and why we collect, store, use and share personal information generally, as well as your rights in relation to your personal information and details of how to contact us and supervisory authorities if you have a complaint.
Last updated: 30 June 2026
Who we are
BotanicalMapper is operated by Virescent Ltd (trading as BotanicalMapper), a company registered in England and Wales (company number 17206041).
Registered office: 8 Acreman Street, Cerne Abbas, Dorchester, Dorset DT2 7JX, United Kingdom.
For privacy and cookie enquiries, contact info@botanicalmapper.com.
In this policy, Services means botanicalmapper.com and the BotanicalMapper application.
Cookies
A cookie is a small text file which is placed onto your device (for example your computer, smartphone or other electronic device) when you use our Services.
Cookies help us to recognise you and your device and allow us to store some information about your preferences or past actions. For example, we may monitor how you use our Services and which parts of the Services you visit. This information helps us to understand use of the Services by our users. Some of this data will be aggregated or statistical, which means that we will not be able to identify you individually.
For further information on our use of cookies, including a detailed list of the cookies we and others may set, please see the table below.
For further information on cookies generally, including how to control and manage them, visit the guidance on cookies published by the UK Information Commissioner's Office at ico.org.uk, aboutcookies.org or allaboutcookies.org.
We also use similar technologies such as local storage and session storage in your browser for limited app features. These are described in the section Browser storage (not cookies) below.
Consent to use cookies and changing settings
We only place cookies or similar technologies that are essential for us to provide you with a service that you have requested (for example to allow you to remain logged in to the Services as you navigate within the Services and use the Services' functionalities).
We do not use non-essential analytics, advertising or tracking cookies. For that reason we do not show a separate cookie consent pop-up or category toggles on the Services.
We do not use cookies for third-party advertising or to sell your browsing data.
Our use of cookies
The table below provides more information about the cookies we use and why:
| The cookies we use | Name | Purpose | Essential / consent |
|---|---|---|---|
| Clerk (authentication) | __session, __client, and related Clerk session cookies | Clerk provides sign-in, sign-up, session management, and organisation (workspace) context for authenticated areas of the Services. The __session cookie is a short-lived session token on our domain; the __client cookie is a longer-lived HttpOnly cookie on Clerk's domain used for session state and revocation. This collects information linked to your account session, including identifiers needed to keep you signed in. Typical duration: session and persistent cookies as set by Clerk (the session token is refreshed frequently). Read Clerk's privacy documentation. | Yes, essential (we will therefore not request your consent before placing these cookies) |
| Next.js (application platform) | Application security and routing cookies (for example draft/preview mode cookies) | Required for secure operation and routing of the application. If you use an authorised Sanity Studio preview link, a short-lived draft/preview cookie may be set so editors can view unpublished content. Typical duration: session. | Yes, essential when you use the relevant feature (we will therefore not request your consent before placing these cookies for core operation) |
| Stripe (payments) | Cookies set on Stripe's own domain when you subscribe or manage billing | When you subscribe or manage billing, you are directed to Stripe (our payment processor). Stripe may set cookies on its domain to prevent fraud, process payments, and remember your checkout session. We do not store full card numbers on BotanicalMapper servers. Typical duration: as set by Stripe. Read Stripe's cookie policy. | Yes, essential when you choose to subscribe or manage billing (consent is not requested separately for payment processing you initiate) |
Features that contact third parties
When you use certain features, your browser may send requests to third-party services. Those providers may use cookies or similar identifiers on their domains when you interact with them directly. On BotanicalMapper, common integrations include:
| Provider | Used for |
|---|---|
| MapTiler | Map tiles, geocoding, historic weather, and related map/insights data when you use the map and forecast features. |
| OpenWeather | Optional weather data where configured as a fallback for forecasts. |
| Supabase | Storing and retrieving your workspace data; authenticated API calls use your Clerk session token rather than a separate BotanicalMapper login cookie. |
| Sanity | Articles and marketing content (images and assets may be served from Sanity's CDN). |
| Cloudflare CDN | Delivery of third-party styles used on the site (for example weather icon styles). |
Public maps (/p/...) and other public pages may load map and content assets without requiring you to sign in. Featured maps and articles are similarly available without an account, subject to visibility rules in the product.
Browser storage (not cookies)
In addition to cookies, we use browser storage for limited functionality:
- local storage — for example remembering a recent spreadsheet import batch so you can undo an import on the same device.
- session storage — for example short-lived flags during account closure or admin workflows.
This storage stays on your device and is not used for advertising.
Marketing preferences
Optional marketing emails are controlled in your account settings and stored in your user profile metadata after you opt in at sign-up or in settings. That preference is not managed through advertising cookies.
How to turn off all cookies and consequences of doing so
If you do not want to accept any cookies, you may be able to change your browser or device settings so that cookies (including those which are essential to the services requested) are not accepted. If you do this, please be aware that you may lose some of the functionality of our Services, including sign-in and workspace features, and of other services you use on your device.
To manage marketing email preferences, use Settings in the app when signed in, or contact us at info@botanicalmapper.com.
For further information about cookies and how to disable them, please go to the guidance on cookies published by the UK Information Commissioner's Office at ico.org.uk, aboutcookies.org or allaboutcookies.org.
Changes to this policy
This policy was published on 30 June 2026 and last updated on 30 June 2026.
We may change this cookies policy from time to time. When we do, we will inform you via the Services or by sending an email to the email address you provided when you signed up to the Services. We will also post the revised version here and change the "Last updated" date above.
More information
For how we process personal data, see our Privacy Policy. For the rules governing use of the Services, see Terms.