Privacy policy
On this page
P-1. Who is responsible
Data controller: Maplith ApS, CVR 46843290, Ørnekulsvej 15, 2920 Charlottenlund, Denmark. Contact for anything in this policy: [email protected]. Maplith has no data protection officer; it is not required to appoint one.
This policy covers the processing for which Maplith is the controller: your account, your use of the service, Maplith's own operations, and the website maplith.com. It does not cover the personal data inside the export files a customer uploads or inside the map built from them: for that data the customer is the controller, Maplith is its processor, and the Data Processing Agreement and the Processing and security description apply. If your data appears in a customer's map, contact that customer; Maplith will help it respond.
P-2. What we collect, why, and on what legal basis
| Data | Where it comes from | Purpose | Legal basis (GDPR) |
|---|---|---|---|
| Account data: email address, name, the identity provider's user identifier if you sign in with Google, Microsoft or GitHub, and, if you turn on two-factor authentication, the authenticator app you register (see below) | You, or the workspace admin who invited you | Sign-in (one-time links or single sign-on), workspace membership, roles and grants, service messages about your account and your runs | Performance of the contract with the customer you act for, Article 6(1)(b); for invited users, Maplith's legitimate interest in operating the workspace the customer set up, Article 6(1)(f) |
| Organisation profile: your organisation's name, legal name, VAT number, address and website, and the contacts it names: a contact person's name and a billing, a legal and a privacy contact email address, which name you where you are that contact. The organisation's members can read it; its owners and admins change it under Settings → Organisation | An owner or admin of your organisation. The contact person and the billing address are suggested from the signed-in owner's or admin's own account, and the legal contact is the address given when the organisation accepts these documents | Knowing who the customer is and how to reach it: the controller named in the Data Processing Agreement and its address for notices, the notice when Maplith staff open access to one of its workspaces (to the privacy contact, with the owners), and invoicing once payments are live | Performance of the contract with the customer, Article 6(1)(b); for a contact person, Maplith's legitimate interest in reaching the customer, Article 6(1)(f) |
| Usage data: sign-in events, funnel events (which steps of the product you complete, and how a sign-up arrived: see below), agent-key and MCP usage, your use of the in-app assistant (one row per model call: the time, the model, the number of tokens and their cost), agent-action audit rows, and the audit trail of privileged changes to your organisation's account (identifiers and event kinds only) | Your use of the app and the MCP endpoint | Security, abuse prevention, fair-use caps, audit of agent actions on the customer's behalf, and understanding how the product is used | Legitimate interest in running a secure and working service, Article 6(1)(f) |
| Sign-in bot check: where Maplith has switched it on, the sign-in and sign-up page runs Cloudflare Turnstile, which receives your IP address and signals from your browser to tell a person from an automated script; Maplith does not store the result | Your visit to the sign-in page | Keeping automated sign-ups and sign-in abuse out of the service | Legitimate interest in a secure service, Article 6(1)(f) |
| Website data: server-side visit counts by referrer host: how many visits maplith.com had from each referring site per day, which Maplith reads from its edge provider (Cloudflare) out of the request data the proxy already handles for every request. Maplith receives the counts only, never an IP address or anything else that identifies a visitor, and no cookie is set and nothing runs in your browser for them, so no consent is asked. AI-exposure signals (whether a visit comes from an AI agent or crawler). The analytics that need your consent are in the next row | Your visit | Understanding how the site is found and used | Legitimate interest, Article 6(1)(f) |
| Website analytics, with your consent: on maplith.com only, and only once you have accepted them on the cookie banner: the pages you view, how you arrived (the referring site and the campaign tags on the link you followed), which of the site's calls to action you use, and technical details of your browser and device (such as their type and version, language, time zone and screen size), recorded by PostHog against a random identifier kept in your browser (see *Cookies and analytics*). PostHog is set to discard your IP address, after it may have derived an approximate location from it. Never what you type, never the content of a customer's workspace, and nothing from the app, which runs no analytics; Maplith does not link the analytics to an account or to anything else it holds about you. Cloudflare's cookieless page views and aggregate visit statistics, where they are switched on, also load only with your consent. The cookie declaration says which analytics are switched on | Your visit, once you have accepted | Understanding which pages and campaigns bring visitors and sign-ups | Your consent, Article 6(1)(a), which the Danish cookie rules also require before anything that is not strictly necessary is stored in or read from your browser. You can withdraw it at any time, as easily as you gave it, with the Cookie settings link at the foot of the pages of maplith.com, or with the Change your choice button on the cookie declaration; withdrawing does not affect what was collected before |
| Questions to the demo company: when the "Ask the demo company" widget is shown on maplith.com, the question you type into it, and your IP address, held in memory to limit how many questions one visitor asks (see *Ask the demo company* below) | You, as a visitor; no account is needed | Answering your question from the map of a fictional company, and keeping the demo from being overused | Legitimate interest in showing what the product does to people considering it, Article 6(1)(f) |
| Sales contacts: your name, company, role and contact details, and notes from our conversations about your company possibly becoming a customer | You, an introduction by someone you know, or public professional profiles. When you book a call with Maplith through Cal.com, what you enter there | Following up a possible customer relationship | Legitimate interest in following up a possible customer relationship, Article 6(1)(f). You may object at any time (see *Your rights*) |
| Maplith Bridge updates: your email address, the consent wording you agreed to and its version, when you signed up, confirmed and unsubscribed, and when you were last mailed. After you unsubscribe: a proof of your consent that holds a keyed hash of your address instead of the address (see below) | You, when you sign up on maplith.com | Sending security notices and release news about Maplith Bridge to the people who asked for them; the proof, showing that Maplith had your consent for the updates it sent | Your consent, Article 6(1)(a). You can withdraw it at any time with the unsubscribe link in every mail, or by writing to [email protected]. The proof: Maplith's legitimate interest in being able to show that it had your consent (Article 7(1)), Article 6(1)(f) |
| Public activity on Maplith Bridge: when you star or fork Maplith Bridge's public repository on GitHub, or open an issue, a pull request or a discussion there, your public GitHub user name, what you did and the title you gave it | GitHub's public record of the repository | Following how far Maplith Bridge reaches, and answering you in public where you wrote | Legitimate interest in knowing how Maplith's open-source software is received and in answering the people who engage with it, Article 6(1)(f). You may object at any time (see *Your rights*) |
| Operational logs: request metadata and IP addresses at the edge and in the application | Your requests | Security, reliability and troubleshooting | Legitimate interest, Article 6(1)(f) |
| Correspondence: what you write to [email protected] and Maplith's other addresses, and what we reply | You | Support, requests under this policy, sub-processor notices, sorting incoming mail (see *Sorting Maplith's own mail* below), and describing Maplith's own recurring work in its own workspace in Maplith (see *Maplith's own workspace* below) | Legitimate interest in answering you and in running Maplith's own operations, Article 6(1)(f); legal obligation where you exercise a right, Article 6(1)(c) |
| Feature suggestions: a suggestion for Maplith's product that an agent of your organisation files through the service: its title and description, kept in Maplith's own issue tracker, hosted by GitHub. Maplith adds no identifier of the workspace, the agent key, the organisation or a person, asks the agent to describe the capability and never data, and tries to mask personal data in the text when it is filed | Your organisation's agents | Improving Maplith's product; feedback you give about the service may be used without obligation or attribution (Terms, section 9.6) | Legitimate interest in improving the service, Article 6(1)(f) |
| Payment and billing data (not live): billing identity, invoices, payment status; card details are held by Stripe and never seen by Maplith, and invoices are kept in the bookkeeping system named on the sub-processor list | You, once payments are live | Invoicing and payment | Contract, Article 6(1)(b); bookkeeping obligations under the Danish Bookkeeping Act, Article 6(1)(c) |
| Operational notifications: workspace identifiers, organisation names, the email address of a new sign-up with the campaign tags and referring site it arrived by (never Google's click identifier), the email address of a workspace's admin when its first map is built, connector and GitHub account names, run and payment events, and, in a notice of public activity on Maplith Bridge, a public GitHub user name and the title of an issue, a pull request or a discussion | The app | Maplith's own monitoring of the service, in its internal Slack workspace, and describing Maplith's own recurring work in its own workspace in Maplith (see *Maplith's own workspace* below) | Legitimate interest in operating the service, Article 6(1)(f) |
Sorting Maplith's own mail. Mail sent to Maplith's addresses may be sorted by an AI agent that works for Maplith. It reads each incoming message to tell a possible customer, a support request and an invoice or receipt from everything else, labels the message in Maplith's mailbox, files an invoice for Maplith's bookkeeping, and drafts a reply or a next step; a reply is sent, and a message from a possible customer becomes a sales contact (above), only once a person at Maplith has approved it. To read the message, the agent sends its content to Anthropic's API in the United States (see *Where it lives, and what leaves the EU*). Apart from the invoices it files and what a person at Maplith approves, Maplith records outside the mailbox only the kind of message, the sender's domain and the thread's identifier, never the content. The purpose is answering and handling Maplith's correspondence, and the basis is Maplith's legitimate interest in doing so promptly, Article 6(1)(f); you may object (see *Your rights*).
Maplith's own workspace. Maplith runs its own operations in Maplith, in a workspace of its own. It may read its own mail and its own operational notifications into that workspace, so that Maplith's service, with Anthropic as its language-model provider (see *Where it lives, and what leaves the EU*), describes Maplith's own recurring work from them. What that workspace keeps is kept as the Processing and security description states for any workspace. The basis is Maplith's legitimate interest in running its own operations, Article 6(1)(f); you may object (see *Your rights*).
Maplith Bridge updates. Signing up is double opt-in: you first receive a mail asking you to confirm, and only a confirmed address receives updates. Every update carries a link to unsubscribe at once, and a mail app's own unsubscribe button works too. The mail is sent through Resend, with open and click tracking turned off, and no IP address is stored with a sign-up. When you unsubscribe, your address is deleted, but Maplith keeps a proof of your consent for 2 years: a keyed hash of your address instead of the address, the version of the consent wording, and when you signed up, confirmed and unsubscribed (see *How long we keep it*).
Public activity on Maplith Bridge. Maplith may read the public activity on Maplith Bridge's repository on GitHub, post a short notice of it, with the public user name, in its internal Slack (below), and answer you in public where you wrote. It keeps the user name nowhere else, and your activity there never adds you to the Maplith Bridge updates or to any other mailing list: only you can sign up for those.
How a sign-up arrived. When a sign-up creates a new organisation, Maplith records with the organisation and with that sign-up's funnel event how the visitor arrived: the campaign tags on the link they followed (utm_source, utm_medium, utm_campaign, utm_term and utm_content), the referring site and, after a click on a Google ad, Google's click identifier (gclid), each cut to at most 200 characters. They are taken from the link alone, with no cookie, tag or pixel, are never sent back to Google, and are used only to see which campaigns and sites bring sign-ups. The basis is Maplith's legitimate interest in knowing how it is found, Article 6(1)(f), and they are kept as the organisation profile and the funnel events are (see *How long we keep it*).
Two-factor authentication. If you turn on two-factor authentication, our authentication provider (Supabase) keeps the authenticator app you register — the name you give it, its type, when you added it, and the shared secret your app uses to make codes — until you remove it or your account is deleted.
Where the basis is legitimate interest you may object (see *Your rights*). Providing account data is necessary to use the service; without an email address there is no account. Maplith does not make automated decisions with legal or similarly significant effects about you. Maplith does not knowingly collect data from consumers or children; the service is for businesses.
P-3. Where it lives, and what leaves the EU
Hosting, database and file storage run in the EU: Supabase (Frankfurt) and Railway (EU West, Amsterdam), with Cloudflare in front for DNS, TLS and DDoS protection. Transactional mail is delivered through Resend's EU infrastructure in Ireland, but the provider itself processes in the United States. The sub-processor list lists every provider, what it receives, where it processes it and on what basis.
Eight of Maplith's own recipients are outside the EU, or may process data outside it:
- Resend (United States) delivers Maplith's transactional mail — sign-in links, build notifications, the acceptance record, notices to a person added to a workspace or given another role in it, workspace and account deletion confirmations, approval notices, legal-version reminders, inactivity reminders, broken-rule notices, agent-key deletion notices, staff-access notices, sub-processor notices, material-change notices — and the Maplith Bridge updates to the people who signed up for them, through its EU infrastructure in Ireland, while its own processing takes place in the United States, under its data processing addendum with the standard contractual clauses.
- Cloudflare (global edge network) sees request metadata and IP addresses for every request, under Cloudflare's data processing addendum with the European Commission's standard contractual clauses.
- Slack (United States) receives the operational notifications listed above — workspace identifiers, organisation names, the email address of a new sign-up with the campaign tags and referring site it arrived by (never Google's click identifier), the email address of a workspace's admin when its first map is built, connector and GitHub account names, run and payment events, and the public GitHub user names in notices of public activity on Maplith Bridge — in Maplith's internal workspace, after Maplith has tried to mask personal data in them (the notice of a new sign-up or a first map shows those email addresses in full), under Slack's data processing addendum with the standard contractual clauses. Slack never receives the contents of your exports or the map.
- Anthropic (United States) receives a visitor's question to the demo company and the demo map's metadata, to write the answer (see *Ask the demo company* below), where Maplith uses its mail-sorting agent, the content of mail sent to Maplith's addresses (see *Sorting Maplith's own mail* above); and, where Maplith reads its own mail and operational notifications into its own workspace in Maplith, their content (see *Maplith's own workspace* above). For this data Anthropic is Maplith's processor, under the provider's Commercial Terms of Service, which incorporate its Data Processing Addendum and, through it, the Commission's standard contractual clauses (Decision (EU) 2021/914), module two (controller to processor). Read from the provider's published terms on 2026-09-30.
- Cal.com (United States) receives what you enter when you book a call with Maplith through its booking page — your name, email address, the time you choose and any note you add — and Maplith reads back the bookings made, only to count them for its weekly internal report. Cal.com, Inc. processes in the United States and states that it relies on the EU-U.S. Data Privacy Framework, and on the standard contractual clauses where appropriate (read from the provider's privacy policy on 2026-10-10).
- Google Workspace (Google Cloud EMEA Limited, Ireland, which may process the data in the United States and elsewhere) hosts Maplith's own mailbox, calendar and files: the mail you send to Maplith's addresses and our replies, meetings with you in Maplith's calendar, and, where Maplith uses its mail-sorting agent, the invoices and receipts it files in a Drive folder. Basis: Google's Cloud Data Processing Addendum, under which transfers to Google's subprocessors outside the EU use the standard contractual clauses or another transfer solution Google has adopted (read from Google's published terms on 2026-10-11).
- PostHog (PostHog, Inc., United States) receives the website analytics you accept on maplith.com (see *What we collect* above), as Maplith's processor. It hosts them in its EU cloud, on servers in Frankfurt, Germany, and states that it may process them in the United States and elsewhere. Basis: PostHog's data processing agreement, with the Commission's standard contractual clauses (Decision (EU) 2021/914), module two (controller to processor), and, as that agreement states, PostHog, Inc.'s participation in the EU-U.S. Data Privacy Framework (read from the provider's published terms on 2026-10-17).
- GitHub (GitHub, Inc., United States) hosts Maplith's own issue tracker, which holds the feature suggestions your organisation's agents file (see *What we collect* above); Maplith adds no identifier of the workspace, the agent key, the organisation or a person to them, and tries to mask personal data in their text. GitHub is also on the sub-processor list, for the hosted agent. Basis: GitHub's Data Protection Agreement, with the Commission's standard contractual clauses (read from the provider's published terms on 2026-09-09).
You can ask for a copy of the safeguards at [email protected].
For customers' file content, the picture is different, and the DPA and the Processing and security description govern it rather than this policy: model inference runs in the United States. To build a map, and for the features that use a language model — answering a question about the map, the in-app assistant, drafting a proposed playbook — content from the customer's files, the map's metadata and what the customer's users and agents write are sent to Anthropic's API under the provider's standard contractual clauses, after Maplith has tried to mask identifiers in them. The provider deletes what it receives within 30 days, and its commercial terms exclude training on customer content. The customer instructs those transfers by accepting the DPA. They are mentioned here so that no one reading only this policy is surprised.
P-4. Ask the demo company
When the "Ask the demo company" widget is shown on maplith.com, you can ask a demo company a question in plain language, without an account. The widget is not always shown; this section describes the processing whenever it is. The company, its customers and every row of its data are fictional, invented for the demo. Please do not type personal data into the question.
- What is sent where. To write the answer, your question (at most 300 characters) and the metadata of the demo company's map are sent to Anthropic's API in the United States. Anthropic processes them as Maplith's processor, under the terms named in *Where it lives, and what leaves the EU* above: its Commercial Terms of Service, which incorporate its Data Processing Addendum with the Commission's standard contractual clauses, module two (controller to processor). Before sending, Maplith tries to mask the local part of email addresses, Danish CPR numbers, IBANs and payment card numbers in the question, as a safeguard that cannot guarantee that every identifier is caught. The provider deletes what it receives within 30 days, and its commercial terms exclude training on it.
- What Maplith keeps. Not the question and not the answer. For each question Maplith keeps one usage row — the time, the model, the number of tokens and their cost — for 12 months, and a count of the demo's calls per day, also for 12 months. Neither says who asked.
- Limits. Your IP address is used in the application's memory to limit how many questions one visitor can ask in a given period, and the demo as a whole answers a limited number of questions a day. The IP address is not written to Maplith's database for this; like every request, the request appears in the operational logs described above.
- Legal basis. Maplith's legitimate interest in showing what the product does to people considering it, Article 6(1)(f). You can object as described under *Your rights*.
P-5. What we never do
We do not sell data. We do not use your data, or customers' data, to train models. We do not send data to any provider that is not on the sub-processor register or disclosed in this policy (the providers for Maplith's own operations, Google Workspace among them, are named under *Where it lives, and what leaves the EU*), and we tell customers before adding a sub-processor; the sub-processor list always lists every one in use. We do not run advertising on the site or in the product, and nothing on either follows you across other sites. The site's analytics run only with your consent (see *Cookies and analytics*), and the product runs none.
P-6. How long we keep it
| Data | Kept for |
|---|---|
| Account data | While your account exists. Closing an account is not self-service yet: write to [email protected] and Maplith's operator deletes it within 30 days and confirms the deletion to you in writing, keeping only the acceptance record (3 years, Terms section 13), billing records under the Bookkeeping Act, the record of the deletion itself, the entries of the audit trail of privileged changes (below), and, in each workspace you were a member of, its history of who could see what and the identifiers that record who did what in it, which are kept and deleted with that workspace. The record of the deletion, the audit trail and the workspace's records name you only by an identifier. The connections you gave an assistant by consenting to it in the app end with your account, as they do when you leave a workspace, except one made before Maplith recorded who consented that can no longer be traced to you, which an admin of the workspace can revoke in Settings. If your organisation's profile names your email address as its billing, legal or privacy contact, the deletion reports it to Maplith's operator, who tells the organisation's owners so that they can replace it; the profile is the organisation's record, and the deletion does not change it |
| Organisation profile | While your organisation's account exists. When an organisation is closed, Maplith's operator keeps its record, the profile included, as long as its acceptance record (3 years, Terms section 13), and then deletes it |
| Funnel events, agent-key and MCP usage, in-app assistant usage, agent-action audit rows (with the signed grants issued for them) | 12 months from the event, or until the workspace is deleted, whichever is earlier |
| Audit trail of privileged changes to your organisation's account (event kind, time, origin, the identifier of the user or agent key that acted, the identifier of what changed, changed-field markers — no contact details, no IP addresses) | 5 years from the event, or until the organisation is deleted, whichever is earlier; kept when a workspace is deleted. Security and accountability, Article 6(1)(f); retained against erasure requests within the period under Article 17(3)(e) and, in support, Article 17(3)(b), because the entries are the record of who changed the account and are hash-chained as evidence |
| Two-factor authenticators | Until you remove one, or your account is deleted |
| Sign-in events | Held in the authentication provider's own log (Supabase Auth) under that provider's retention; not yet covered by the daily control below |
| AI-exposure signals on the marketing site | 90 days |
| Questions to the demo company | Not kept. One usage row per question (time, model, tokens, cost) and a daily count of the demo's calls, 12 months each |
| Server-side visit counts by referrer host | Not stored by Maplith: read as counts for Maplith's weekly internal report, which appears in its internal Slack (below). Cloudflare keeps its own request analytics under its retention |
| Website analytics, with your consent | At most 13 months: Maplith deletes them at least once a year. They are tied only to the random identifier in your browser, which is removed when you withdraw your consent |
| Cookieless page-view statistics at Cloudflare, where switched on, with your consent | Aggregate only; the provider's retention |
| Sales contacts | 24 months after the last contact or change to the record. If your company has an account with Maplith, what is noted about it is kept while that account exists and deleted with it |
| Sales pipeline views and changes: which Maplith staff member opened or changed the sales contacts, and when | 24 months from each entry |
| Operational logs | The hosting provider's log retention. Maplith intends 30 days; until that setting is confirmed, the provider's default applies |
| Correspondence | 3 years after the matter is closed, so that we can show what was agreed. What the mail-sorting agent records outside the mailbox (the kind, the sender's domain and the thread's identifier) is kept no longer. What Maplith's own workspace in Maplith keeps from its mail and its operational notifications is kept as the Processing and security description states for any workspace |
| Feature suggestions in Maplith's issue tracker | As long as Maplith offers the product, as the record of what it was asked for. Maplith adds no identifier of a person to a suggestion and tries to mask personal data in its text when it is filed; if one names you, you can ask Maplith to delete it (see *Your rights*) |
| Maplith Bridge updates | While you are subscribed. Once you unsubscribe, you are not mailed again, and your address is deleted within 7 days. The proof of your consent (a keyed hash of the address, the version of the consent wording, and when you signed up, confirmed and unsubscribed) is kept for 2 years after you unsubscribe, and then deleted. A sign-up that is not confirmed is deleted 7 days after it was made |
| Public activity on Maplith Bridge | Not stored by Maplith: a public GitHub user name appears only in the notice in its internal Slack, which is kept as the operational notifications are (below) |
| Billing data (once live) | 5 years after the end of the financial year, as the Danish Bookkeeping Act requires |
| Operational notifications in Slack | The workspace's Slack retention setting. Maplith intends 12 months; until that setting is made, Slack's default applies |
| A workspace that no member signs in to for 12 months | Deleted, with its map and runs, after reminders to its admins (Terms, section 8) |
The schedule is checked by the product every day. Deletion is switched on by Maplith's operator once the first reports have been checked; until then rows past their period are counted, not deleted. A workspace is never deleted for inactivity without written reminders to its admins (Terms, section 8).
P-7. Your rights
Under the GDPR you can ask Maplith for access to your personal data, for correction, for deletion, for restriction of processing, for a copy of the data you gave us in a machine-readable form (portability), and you can object to processing based on legitimate interest, including at any time to direct marketing. Maplith may contact people at businesses one to one, by email or on LinkedIn, about Maplith. You can object to this at any time by replying or by writing to [email protected], and Maplith then stops. If Maplith got your details from a public professional profile, it tells you so and points you to this policy no later than its first message to you. Maplith's only consent-based mailing list is the Maplith Bridge updates (above). Write to [email protected]. We answer within one month; if a request is complex we may take up to two further months and will tell you why.
In the product: a workspace admin can export the map as JSON under Settings → Data, and an owner or admin of your organisation can delete a workspace there; a deletion is confirmed in writing to the workspace's admins, to at most three confirmed addresses. Deleting your account or your organisation is not yet self-service: write to [email protected], and Maplith's operator carries it out within 30 days and confirms in writing.
You can complain to Datatilsynet, the Danish supervisory authority (Carl Jacobsens Vej 35, 2500 Valby; www.datatilsynet.dk), or to the supervisory authority of the EU country where you live or work.
P-8. Cookies and analytics
Under the Danish cookie rules, cookies and browser storage that are strictly necessary for a service you ask for need no consent; anything else is stored in or read from your browser only after you accept it.
Strictly necessary. The app (app.maplith.com) sets one cookie when you sign in, named sb-tieewndphupfnrhqwzcl-auth-token (stored in numbered parts when it is long), which holds your session for 30 days from your last visit, is sent only over HTTPS and only to the app, and is removed when you sign out. During sign-in it also sets short-lived cookies: ml_next (15 minutes), which remembers the page to return to and is removed on arrival, and sign-in verifier cookies, whose names begin with sb-tieewndphupfnrhqwzcl-auth-token and end in code-verifier, which prove that the sign-in that comes back is the one your browser started; they are removed when the sign-in completes, and one left by a sign-in you do not finish expires after 30 days. When Maplith is updated while a page of the app is open, the page reloads itself, and two entries in your browser's session storage carry, across that one reload, the notice that Maplith was updated and what you had selected; they are removed as the page reloads and never kept after you close the tab. Where the website asks for your consent, a cookie named ml_consent remembers your answer for 6 months, with a short code of what the banner listed when you answered, so that the banner asks again when that list changes. Where the sign-in bot check is switched on, the sign-in page loads Cloudflare Turnstile, which is used only to tell a person from an automated script.
Analytics, only with your consent. The app loads no analytics. On the website (maplith.com), and only there, Maplith uses analytics only once you accept them on the cookie banner. Until you do, nothing for them is stored in your browser and nothing is sent to PostHog. Once you accept, PostHog sets an analytics cookie and keeps entries in your browser's storage, which hold a random identifier for your browser, your current visit and how you arrived, and whether you accepted, so that page views and calls to action can be counted (see *What we collect*); the cookie is set for the website only, never for the app, and lasts 180 days from your last visit. Your answer counts for what the banner listed when you gave it: once it has expired, or the list has changed, the analytics no longer start, the banner asks again, and what they kept in your browser is removed on your next visit. If you decline, nothing is stored for them. You can withdraw your consent at any time with the Cookie settings link at the foot of the pages of maplith.com, or with the Change your choice button on the cookie declaration: the analytics then stop, and what they kept in your browser, the random identifier included, is removed. Cloudflare's cookieless page-view statistics, where they are switched on, also load only after you accept. There are no advertising cookies and no advertising pixels, and nothing that follows you across other sites, on the website or in the app.
The cookie declaration lists every cookie and every entry in your browser's storage with its purpose, duration, provider and category, and shows which analytics are switched on.
P-9. Changes to this policy
Material changes are announced in the app and by email to workspace admins before they take effect. Other changes are announced in the app when they are published. Every version is kept with its date and provided on request.
P-10. Legal documents
Terms & Conditions · Data Processing Agreement · Processing and security description · Sub-processor list. Each carries its version and the date it last changed.