Privacy Policy

This Privacy Policy explains how Blue Blink One, SL (CIF B44518892) (“Blue Blink One”, “we”, “us”), Av. del Mar, 55, 12003 Castellón de la Plana, Spain, processes personal data when you use Measure Map Online — our websites, the web application at app.measuremaponline.com, our APIs and embeddable components (together, the “Service”). Blue Blink One, SL is the data controller for the processing described here, except where noted in Section 7: an organisation is the controller of its members’ data in its workspace, and a subscriber is the controller of its guests’ data, and we process that data on their behalf. Even then, we remain the controller of what we process for our own purposes — keeping accounts and the Service secure, billing and invoicing, and product usage events. Section 17 explains how we handle the details of businesses we contact to offer them the Service.

Contact for privacy matters: support@blueblinkone.com.

1. Data We Collect

• Account data — email address, name, password (stored in hashed form by our authentication provider), profile photo, language, and the company, address and phone number if you add them; if you sign in with Google, the basic profile information Google shares with us; if your organisation uses single sign-on, the identity its provider confirms (your name and email address, updated from the provider when you sign in). If you turn on two-step verification, its settings and your recovery codes (stored hashed).
• Billing data — billing address, country and fiscal identification (VAT/tax ID, national ID or passport number), which Spanish invoicing law requires us to collect and show on invoices; your plan, seats, plan changes, invoices and payment history. Card details are collected directly by our payment processors — we never see or store full card numbers.
• Content you create — projects and their geometries (polygons, polylines, spots) including their geographic coordinates, measurements, imported files and reference layers, products, prices and product images, cost estimates, descriptions, comments, and photos you attach (photos may contain metadata such as capture location if your device embeds it).
• Sign-in sessions — for each device you use: IP address, approximate location (country, region and city, derived from the IP address), time zone, browser, operating system, device type and when it was last active. You can see this list in your profile and sign devices out.
• Technical logs — a record of each request to our servers (time, the part of the Service called, the result and how long it took, the account making it, the browser or app and the website it came from), and error reports for failed requests, which keep that request’s headers (including the IP address, approximate location and browser) and its content. Passwords, access tokens and API keys are removed from logs.
• Product usage events — which features are used (for example that a project was created, an export format, a plan change), recorded on our servers against a pseudonymous account identifier, together with your plan and country. They do not contain your name, email address or IP address.
• Embeds and API — for embedded projects, the websites that load them and how often. For the developer API, a log of each call made with a subscriber’s API key: the address called, the request headers (including the caller’s IP address and browser or client), and the request and response bodies, with passwords, keys and tokens removed. Because the bodies are kept, the log can contain the names and email addresses of users the subscriber creates or changes through the API.
• Single sign-on requests — when an organisation asks us to connect its identity provider: the provider’s addresses and signing certificate, or for OpenID Connect its client ID and client secret, the email domains to allow, the name and email address of the technical contact, any notes, and who sent the request and when. The request is also sent to our support team as a ticket (the client secret is not included).
• Communications — messages you send us (support requests, feedback) with the app version, device and language they are sent from; the emails and in-app notifications we send you, and your notification preferences.
• Consent records — your cookie choices and when you made them, kept as proof.

2. Why We Process It (Legal Bases)

Purpose	Examples	Legal basis (GDPR)
Providing the Service	Account management, storing and rendering your projects, sharing, collaboration, organisations, notifications, support	Performance of a contract (Art. 6(1)(b))
Billing and invoicing	Subscriptions, seats, payments and bank authentication, invoices with buyer identification, usage metering on metered plans	Contract (Art. 6(1)(b)) and legal obligations (Art. 6(1)(c)) — Spanish tax and e-invoicing rules, including VeriFactu
Security and abuse prevention	Sign-in sessions, two-step verification, technical logs, error reports, fraud prevention, enforcing plan limits	Legitimate interests (Art. 6(1)(f)) in keeping accounts and the Service secure
Improving the Service	Product usage events and the statistics built from them (for example how many projects are created, which features are used, how plans change); diagnosing errors	Legitimate interests (Art. 6(1)(f)) in understanding and improving the product — pseudonymous, never used for advertising; you can object (Section 12)
Google Analytics in the app	Aggregate statistics about visits	Consent (Art. 6(1)(a)), see Section 13
Communications	Security, billing and account emails; replies to your requests; optional emails such as estimate requests from your guests or budget alerts, which you can turn off in your profile	Contract; legitimate interests; your preferences
Offering our product to businesses	Finding businesses on the public web, writing to them, reading and answering their replies, and noting when a business we contacted signs up (Section 17)	Legitimate interests (Art. 6(1)(f)) in offering our product to businesses
Proof of consent	Keeping a record of your cookie choices	Legal obligation (Art. 6(1)(c) with Art. 7(1))

We do not sell your personal data, we do not use it for advertising, and we do not use your Content to train AI models.

3. Location & Map Data

The coordinates of the shapes you draw are part of your Content and are stored with your projects. When you view maps, your browser requests map tiles, satellite and 3D imagery, Street View images and elevation data from the map provider you have selected (Google Maps by default; optionally Bing Maps, Mapbox, HERE, TomTom, OpenStreetMap and OpenStreetMap-based maps such as Thunderforest, Esri ArcGIS, USGS, or national mapping agencies such as IGN Spain, IGN France, swisstopo, PDOK, basemap.at, Kartverket and Geoportal Poland). These providers receive your IP address and the map area you are viewing, under their own privacy policies. Place and address searches are sent from your browser to Mapbox, with the text you type and the area the map shows. To draw your projects’ thumbnails, our servers send the outlines of their shapes to Google Maps Platform. When you look up land parcels, our servers query the respective data source (for example the Spanish Catastro, French cadastre services or Regrid in the USA) for the area you are viewing, so the source does not receive your IP address; names and addresses of owners, buyers and sellers that some sources include are removed on our servers and never reach you. Some things are loaded by your browser directly from the source, which then receives your IP address: cadastral map overlays (for example from the Spanish Catastro or HM Land Registry), and the photos shown with a parcel (from the Spanish Catastro, Regrid or Google Street View). If you use your device’s location feature to centre the map, your position is used in your browser and is not stored by us unless you place it into a project.

4. AI Features

Some AI features run entirely in your browser (for example outlining a shape you click on the map). The “find in imagery” detection runs on our servers: when you use it, the addresses of the map tiles you are viewing and the words you type describing what to find are sent to our servers, which fetch those tiles from the map provider and analyse them with a model we run ourselves on Google Cloud in the European Union. The imagery and your words are processed only to return the shapes found and are not stored. We count your detections: a daily count, kept for three days, applies the daily limit, and a monthly total of runs and shapes found is kept with your account. No third-party AI provider receives your data, and your Content is not used to train AI models.

5. Service Providers & Recipients

Our service providers. We use a small number of service providers to run the Service. They process personal data only on our instructions, under data processing terms. They are also the sub-processors we use for our business customers (Section 7). Transfers outside the European Economic Area are protected as described in Section 9.

• Google Cloud / Firebase (Google) — authentication (including single sign-on), databases, file storage, hosting, our servers (including the AI detection model) and logs. Location: the United States (our database and servers: the US multi-region and Iowa) and the European Union (AI detection in the Netherlands; a relay for European parcel sources in Belgium, which handles map areas only).
• Google Workspace (Google) — sending our emails (account, security, billing and notification emails, replies to support requests, and our emails to businesses we contact) and receiving replies to them. Location: the United States and other Google locations.
• Stripe (Stripe Payments Europe, Ltd., Ireland, with Stripe, Inc.) — payment processing, bank authentication (3-D Secure) and invoices. Your billing details and fiscal identification are registered with Stripe to issue compliant invoices. Location: the European Union and the United States.
• PayPal (PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg) — payments for some legacy subscriptions only. We no longer accept PayPal, and we are cancelling the remaining PayPal subscriptions as we retire it (see Section 3.3 of our Terms). Location: the European Union and the United States.

Only with your consent. Google Analytics — aggregate statistics about visits to the app, loaded only if you agree (Section 13).

Only for contacting businesses. Anthropic — the AI models (Claude) we use to find businesses that may need our product, write our messages to them and sort their replies (Section 17). It receives the business details we find and the replies businesses send us. It does not receive our users’ or customers’ data, and it is not one of the sub-processors we use for our business customers. Location: the United States; the transfer is protected by the European Commission’s Standard Contractual Clauses (Section 9).

Providers you use through the Service. These are not our sub-processors: they provide content under their own terms and privacy policies.

• Google Maps Platform — maps, satellite and 3D imagery, Street View, elevation and project thumbnails; and the other map, imagery and cadastral providers you select (Section 3).
• Mapbox — place and address search (Section 3).
• Google Fonts — the app loads its icon font from Google’s servers, which receive your IP address when it loads; no cookies are set.
• Plugins — if you open a third-party plugin from the map, it receives the project’s identifier and its own privacy policy applies.

Other recipients: the people you share projects with (Section 6); the organisation your account belongs to, or the business whose guest link you use (Section 7); tax authorities (including through VeriFactu) and others where the law requires it, for example under a court order; and a buyer or successor in a corporate transaction (merger, acquisition), in which case this Policy continues to apply.

6. Sharing You Control

You decide who sees your projects. Private projects are visible only to you and members you invite (and, if your account belongs to an organisation, its owner, administrators and managers; see Section 7). If you set a project to view-only or public, anyone with the link can see its contents (including any photos, descriptions, prices and comments in it), and public projects may allow comments. Comments you post on a shared project are visible to everyone who can see it. When you comment, the project’s owner and the people it is shared with are notified, with your name, email address and profile photo, and, if the owner has set up webhooks, your name and email address also reach their own systems. On public projects people without an account can comment under the name they type. If you embed a project on a website, visitors of that website can view it. Think before sharing Content that contains personal data — once shared or embedded, it may be viewed and copied by others.

7. Guests, Organisations & Business Customers

• Guest links and embeds — subscribers on eligible plans can let their own clients measure without an account, through a guest link or an embedded project. Guests use an anonymous session, and the projects they draw are stored in the subscriber’s account. If a guest asks for an estimate, the name, email address, phone number and message they give are sent to the subscriber by email, shown in the subscriber’s dashboard and stored with the project (where anyone who can open that project can see them), and can also reach the subscriber’s own systems through webhooks and the developer API; the same applies to details the subscriber puts in a guest link. For this data the subscriber is the controller and we act as its processor, processing it only to provide the Service; the subscriber’s own privacy notice applies, and you can exercise your rights with them (we will help them respond).
• Organisations (Enterprise) — if your account belongs to an organisation, its owner and administrators can see your profile (including any address, phone number and billing details you have entered), your role and teams, whether you are online, when you were last active and your local time zone (not your device, IP address or location); the owner, administrators and managers can open and edit every project you create, including projects you created before joining and Private ones. The owner and administrators can create your account, change your role, set a new password for you, sign you out, suspend you and transfer your projects to another member. They can also delete your account — including an account you had before joining. Your profile and other personal data are then erased as described in Section 10, but the projects and folders you created, including those from before you joined, pass to the organisation’s owner, in a folder named after you. If they unlink you instead, your account and its projects continue on their own. Through its developer API, an organisation can create and change member accounts and sign in as you. Actions in the organisation are recorded in an activity log that its owner and administrators can see.
• Single sign-on — if your organisation uses single sign-on, its identity provider tells us who you are. The first time you sign in through it with an address on one of the organisation’s approved domains, your account is created and added to the organisation automatically, and your name and email address are kept up to date from the provider. The organisation can be told through its webhooks that you joined. The organisation decides how it manages its members, and its own privacy rules also apply.
• Developer API and webhooks — subscribers can connect their own systems to the Service. Data they send us through the API, and data we send to the webhook addresses they configure (for example new projects, comments, guests’ details and new members), is processed on their instructions. Once it reaches their systems, their own privacy notice applies.
• Who is responsible — for the data an organisation or subscriber manages in the Service (its members, guests and clients), it is the controller and we are its processor, under our Terms and, for Enterprise and API customers, a Data Processing Agreement available on request. For what we do for our own purposes — security, billing and product usage events — we are the controller, as described in this Policy.

8. Access by Our Staff

Access to account data is limited to a small number of authorised staff, and only as needed for support, security, billing and our legal obligations. To resolve an issue you report, support may view the Service as you see it. Changes staff make to your account or Content, each time staff sign in as you, and look-ups in our internal database browser are recorded in an internal audit log, which we keep for 2 years.

9. International Transfers

Our servers run on Google Cloud, including in the United States, and some of our providers (for example Google and Stripe, and Anthropic for the businesses we contact, Section 17) process data outside the European Economic Area. Where they do, transfers are protected by an adequacy decision (such as the EU–US Data Privacy Framework, where certified) and/or the European Commission’s Standard Contractual Clauses, together with appropriate supplementary measures.

10. Data Retention

Data	How long we keep it
Account data and Content	While your account exists. When you delete your account you are signed out at once; your profile, projects, photos, products, notifications, sessions, settings and usage records are erased 14 days later (when an organisation deletes a member’s account, the projects the member created pass to the organisation instead; see Section 7), together with the backup copies of your projects; copies that remain in our database recovery systems expire within a further 30 days. Comments you posted on other people’s projects stay in those projects as part of their Content. Projects you delete stay in your trash until you delete them permanently.
Inactive accounts	We may delete an account that has not been signed into for 12 months, if it is more than 12 months old, holds no projects, has no paid subscription still running and is not part of an organisation. We email its address when we do; the erasure then follows the steps in the row above.
Data not yet erased automatically	A few things are not yet covered by the automatic erasure described in the first row: accounts deleted before 29 October 2026; the photos, map layer files and thumbnail of a project you delete permanently; files that older versions of our apps, or our mobile apps, saved outside your projects’ folders; and records of emails we sent you before we began storing them in scrambled form. They are kept until you ask us to erase them, which you can do at any time (Section 12), or until we extend the automatic erasure to them.
Invoicing and tax records	For the periods required by Spanish tax and commercial law (generally up to six years), also after the account is deleted
Subscription history and discount codes used	While your account exists, and afterwards with our invoicing and tax records (row above)
Sign-in sessions	90 days after the device was last active
Links to undo a change of sign-in email	7 days. When your sign-in email changes we send the previous address a link to undo it; we keep the previous address, the date and a scrambled form of the link (not the link itself).
Technical request logs	30 days
Developer API call log	90 days
Error reports	90 days
In-app notifications	180 days
Records of the emails we send you	400 days, stored in scrambled form, to avoid sending the same email twice
Product usage events	13 months; a summary of which days and weeks your account was active is kept while your account exists; statistics that no longer relate to any account may be kept longer
Detection counts	Daily count: 3 days. Monthly totals: while your account exists
Comments you delete	30 days, so they can be restored, then erased
Your activity log (what you did in your account)	While your account exists
Guests’ estimate requests	With the subscriber’s project, until the subscriber deletes it or their account
Support correspondence	As long as needed to handle your request and any related claim
Consent records	As proof of the choices you made, also after the account is deleted
An organisation’s activity log	For as long as the organisation’s account exists, also after a member leaves
Single sign-on request	While single sign-on is requested or on; erased with the organisation owner’s account. The OpenID Connect client secret is removed from our records once the connection is switched on.
Webhook settings and delivery status	While the webhook is set up
Export files	With the project, until it is deleted. The download link we give you expires after 24 hours.
Backups	Each project’s last 30 daily copies (written on days it changed) and restore points up to 30 days old; deleted with the project or the account
Staff audit log	2 years
Businesses we contact (prospects, Section 17): their details, our messages, their replies and contact-form screenshots	12 months: a business’s details from when we found it; each message, reply and screenshot from when it was written, received or taken
Prospects’ do-not-contact list (the domain or email address of each business that asked us not to contact it)	Indefinitely, so that we never contact the business again
Records of our prospecting runs (searches, pages read, the businesses found or written to and our emails’ subjects)	Indefinitely

11. Security

We protect data with encryption in transit (TLS); authentication; database access rules that limit every account to its own data, to what has been shared with it and, in an organisation, to what its roles allow; per-project access levels; logs with credentials removed; audited staff access; and the security infrastructure of our cloud providers. Photos, exports and other files are stored at addresses that we do not publish, but anyone who has a file’s address can open it. Single sign-on certificates and client secrets are stored only on our servers, never in the app. You can turn on two-step verification, see the devices signed in to your account and sign them out. No system is perfectly secure: please use a strong, unique password, and contact us immediately if you suspect unauthorised access to your account.

12. Your Rights

Under the GDPR and Spanish data protection law (LOPDGDD), you can ask us for access to your personal data, rectification, erasure, restriction of processing, data portability, and you can object to processing based on legitimate interests — including the product usage events in Section 1, which we will stop recording for your account. Where processing is based on consent, you may withdraw it at any time without affecting prior processing. You can do several of these yourself: correct your details and choose your emails in your profile, download a copy of your data from your profile (Download my data), export any project, and delete your account. Deleting a project permanently needs an active plan; otherwise write to us and we will delete it. For anything else, email support@blueblinkone.com; we may need to verify your identity. You also have the right to lodge a complaint with your supervisory authority — in Spain, the Agencia Española de Protección de Datos (aepd.es).

13. Cookies

The Service uses cookies and similar technologies:

• Essential — sign-in sessions, security and remembering your settings (for example your theme and language). These are required for the Service to work.
• Analytics — Google Analytics, used to understand aggregate usage and improve the product. Google Analytics is not loaded until you agree: you can accept or reject it in the cookie banner, and change your mind at any time from Cookie settings (on the sign-in page, in the dashboard menu and in the map settings). Withdrawing switches it off and deletes its cookies.

The product usage events in Section 1 are recorded on our servers and use no cookies or browser storage. Every cookie and item of browser storage the Service uses — who sets it, why and for how long — is listed in our Cookie Policy.

14. Automated Decisions

We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects. Automatic steps such as applying plan limits, retrying a failed payment or stopping new guest projects when a monthly budget is reached follow the settings and plan you chose.

15. Children

The Service is intended for professional use and is not directed at children under 14. We do not knowingly collect personal data from children; if you believe a child has provided us personal data, contact us and we will delete it.

16. Changes to this Policy

We may update this Policy as the Service or the law evolves. The current version is always available at this page; for material changes we will notify you (for example by email or in-app notice) before they take effect. Version 2.1, effective 29 October 2026, replaces version 2.0 of 19 August 2026. It describes in more detail the data we record for security and product improvement, how AI detection works, the service providers we use, who can see and do what in organisations (including deleting accounts, what happens to a deleted member’s projects, and single sign-on) and guest links, the developer API log, what comments and webhooks share, staff access, when inactive accounts are deleted, exact retention periods, and how we handle the details of businesses we contact.

17. Businesses We Contact

To offer Measure Map Online to businesses that may need it (for example paving, roofing or landscaping companies), we look for them ourselves and write to them. This Section covers the details of those businesses and of the people who work for them. It is about business contact details we find on the public web, not about the data of our users and customers: Anthropic does not receive that data, and we use it here only to note when a business we contacted signs up, as described below.

Where the data comes from. We look for businesses on the public web using AI tools from Anthropic, which search the web and read the businesses’ own websites. We take contact details only from a business’s own website, as it publishes them for enquiries.

What we record. The business’s name and website; what it does, who it works for, the area it covers, its approximate size and a few details from its website; how it quotes its work today and why our product may suit it; and the email address, phone number and contact form it publishes for enquiries, and the name of a contact person if its website gives one. We also keep the messages we write to it, the replies we receive (with the sender’s name, email address and text), a screenshot of any contact form we fill in, and records of each search and writing run, which name the businesses found and the subjects of our emails.

What we do with it. We may send the business one email about our product, and at most one follow-up if it does not answer; if it publishes no email address, we may leave the same kind of message on its website’s contact form instead, giving only our own details. Our AI tools write each message, and a member of our team reviews and approves it before it goes. Emails are sent from our own email addresses through Google Workspace, and replies come back to our mailbox. Our systems pick out the replies to our emails, keeping nothing about any other mail, and our AI tools sort them (for example interested, a question, not interested, a request to stop, an out-of-office or an email that was not delivered) and draft answers for our team to review. If someone later creates a Measure Map Online account with the business’s email address or an address at its website’s domain, or that account starts paying, we note on our record of the business that our contact led to it, and which account it was.

Legal basis. Our legitimate interest in offering our product to businesses (Art. 6(1)(f) GDPR), within the limits of the rules on electronic commercial communications.

Who receives it. Anthropic, whose AI models (Claude) search the web, read websites, write our messages and sort the replies; and Google, through Google Workspace (sending our emails and receiving the replies) and Google Cloud (where we store the data, and where the browser that fills in contact forms runs). Section 5 describes both and where they process data, which includes the United States; transfers outside the European Economic Area are protected as described in Section 9.

How long we keep it. A business’s details are deleted 12 months after we found it, and each message, reply and screenshot 12 months after it was written, received or taken. If a business asks us not to contact it again, its domain or email address stays on our do-not-contact list indefinitely, so that we never write to it again. Our records of each search and writing run are kept indefinitely, and our staff audit log, which records who approved each message and where it went, for 2 years. Section 10 lists these periods.

Your choices and rights. Every email we send has a link to unsubscribe, and a message we leave on a contact form says how to tell us to stop. You can also reply to any of our messages, or write to support@blueblinkone.com, to object at any time. We then stop at once: your domain or email address goes on our do-not-contact list, which our tools check before they save, write to or answer any business, and we will not contact you again. The other details we hold about the business are no longer used to contact it, and are deleted when their period ends, or sooner if you ask. You also have the other rights in Section 12, including access, erasure and the right to complain to a supervisory authority.

18. Contact

Blue Blink One, SL — CIF B44518892
Av. del Mar, 55, 12003 Castellón de la Plana, Spain
support@blueblinkone.com

---

Version 2.1 — published and effective 29 October 2026. Previous version, available on request: 2.0 (19 August 2026). See also our Terms & Conditions.