Privacy policy

Last updated: 2026-10-17. This policy covers the Geocode & Maps for Sheets add-on and this website. A Spanish version is available at /es/privacidad/; if they differ, the Spanish text prevails.

Who is responsible

Marc Duran López · tax ID (NIF) 47894988H · Calle Jacinto Verdaguer 13, 08620 Sant Vicenç dels Horts (Barcelona) · contacto@engranalab.com

In short

• Your addresses and coordinates stay in your spreadsheet and with the geocoding service you use. The add-on runs inside your Google account. Nothing in your sheet is sent to our servers, with one exception you trigger yourself: a shared map (Pro).
• A shared map uploads only what you choose to publish: its title and, for each point, latitude, longitude, label and group. Anyone with the link can see it until it expires or you delete it.
• We receive one anonymous usage ping per installation per day (random id, version, language and counters). You can turn it off.
• If you use Pro (free during the beta), we receive the email of your Google account to know you have it. If you join the Pro beta or waitlist on this website, we store your email and the answers you choose to give.

What the add-on processes

• Addresses you geocode. When you use GEOCODE, REVERSE_GEOCODE, DISTANCE, DRIVETIME or the Geocode a column sidebar, the address text is sent from Google's servers, with your Google account, to the Maps service of Google Apps Script. That service answers with coordinates, a normalized address and a precision level, and Google's own terms and privacy policy apply to it, not ours. straight distances are computed locally and call nothing.
• Your own API key (Pro). If you add a key for Google Maps Platform, OpenCage or Geoapify, the addresses you geocode go to that provider with your key instead, and the provider's terms and privacy policy apply. The key is stored in your user properties inside your Google account, never in the sheet and never on our servers.
• The active spreadsheet. The add-on only asks for access to the spreadsheet where you use it (spreadsheets.currentonly scope) to read the selected cells and write results. It does not read other files, your Drive, your Gmail or your contacts.
• What it stores, and where. Results are kept in a hidden Geocode cache tab of your own sheet and, for up to 6 hours, in Google's cache service. The state of a column run and your settings live in the document's properties in your Google account. None of this is sent to us.
• The map. The map dialog draws your points in your browser with Leaflet and OpenStreetMap tiles. Your browser asks the OpenStreetMap tile servers for the tiles of the area shown, so OpenStreetMap sees your IP address and the tiles requested, not your data. KML and GeoJSON exports are built in your browser and never uploaded.
• Scopes requested: spreadsheets.currentonly, script.external_request (ping, Pro licence, shared maps and the providers of your own key), script.container.ui (menu, sidebar and dialogs), script.scriptapp (to create the triggers of Pro auto-geocode), and userinfo.email and openid (to read the email of your Google account and prove it to our server for Pro). None of them is a restricted scope.

Anonymous usage ping

• What we receive: once per day at most, per installation: a random installation id, the add-on version, your interface language, and counters ( how many times GEOCODE, REVERSE_GEOCODE, DISTANCE and DRIVETIME ran, how many rows and runs of the column sidebar, how many times the map was opened or exported, and how many errors and quota errors occurred ). We store a SHA-256 hash of the id (never the id itself), the UTC day and those values.
• What we never receive: URLs, queries, headers, keys, responses, sheet data, your name, your email or your Google account.
• Purpose: to know whether the add-on is used and which version, so we can decide how to keep improving it. Legal basis: our legitimate interest in measuring adoption (art. 6.1.f GDPR) with data that does not identify you.
• IP address: the server uses it only to rate-limit requests, in memory, and it is not stored with the ping.
• How to turn it off: in Google Sheets, open Extensions → Geocode & Maps for Sheets → Usage statistics and switch it to off. The add-on stops sending pings.
• Retention: each daily record is deleted automatically 400 days (about 13 months) after the day it refers to; after that we only keep aggregate totals with no installation id (for example, daily active installations). Because the records do not identify you, we generally cannot link them to you; if you want records removed sooner, turn statistics off and write to us.

Shared maps (Pro)

• What is stored: the title you give the map; for each point (up to 2,000) its latitude, longitude, label (up to 120 characters) and group (up to 40); the creation and expiry dates; and a SHA-256 hash of your Google account email, so that only you can list and delete your maps. We never store your email in that table, nor the sheet or its name.
• Who can see it: anyone who has the link (an unguessable 22-character code). The page is not indexed by search engines. Do not publish points or labels you would not give to everyone with the link: addresses are personal data when they identify a person.
• How long: it expires after the 30, 90 or 180 days you choose and is then no longer served; a daily job deletes expired maps. You can delete a map earlier from the add-on. You can have up to 50 live maps. If you stop using Pro, the maps already published stay until they expire.
• Purpose and legal basis: providing the sharing you request (art. 6.1.b GDPR).

Pro: account email and licence

• Account email (licence). Sheets Pro by Engranalab is one subscription shared with the other Engranalab add-ons for Sheets, so the licence is kept in the same place for all of them. When you open the Pro panel, the add-on sends our server a Google identity token, which proves the email of your Google account. We use that email to know whether you have Pro or the free beta, and to send you what you asked for. We do not receive your name, your contacts or any other Google data. Purpose and legal basis: providing the service you request (art. 6.1.b GDPR). We keep it while you use Pro and for 12 months after you leave it.
• Where things are stored. Auto-geocoding runs entirely in your Google account (installable triggers) and its settings are kept in your document's properties.

Pro beta and waitlist (this website)

• Data: email address, optional answers (what you are interested in, how much you would pay, personal or company use) and proof of your consent.
• Purpose: to confirm your sign-up (double opt-in) and to email you about the launch of Pro, with its price and date. If you activate the free beta from the add-on, your email is already verified by Google and no confirmation is needed. Legal basis: your consent (art. 6.1.a GDPR), which you can withdraw at any time.
• Retention: until you unsubscribe, or 12 months after the waitlist closes; unconfirmed sign-ups are deleted after 30 days.
• Unsubscribe: every email has an unsubscribe link, and you can write to us.

Website

The website uses no advertising or tracking cookies. We measure audience with aggregate statistics that use no cookies or personal identifiers (Cloudflare Web Analytics). The shared map page loads Leaflet from cdnjs (Cloudflare) and map tiles from OpenStreetMap; the page asks the browser to send only the site's origin, not the map link, to those services.

Providers and data sources

Google Maps (geocoding and routes through Google Apps Script, or Google Maps Platform with your own key), OpenCage and Geoapify (only if you add your own key), and OpenStreetMap (map tiles; map data © OpenStreetMap contributors, available under the Open Database Licence). Each of them is an independent controller of what you send them; read their terms before relying on their results. Coordinates obtained from Google are shown with the notice Geocoding by Google and the add-on records the provider of every row in a provider column, so you can tell which results come from which source.

Google API Services User Data Policy

Geocode & Maps for Sheets's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.

In practice: we use the access to your spreadsheet only to provide the features you ask for, directly in your sheet. We do not transfer that data to anyone, we do not use it for advertising, and nobody at our end reads it, because it is never sent to us.

Recipients

Providers acting as data processors under a contract: hosting, email delivery (Resend) and aggregate analytics. We do not sell or share your data with third parties except where the law requires it or you consent. Some providers may transfer data to the United States under the EU-US Data Privacy Framework or standard contractual clauses.

Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction and portability by writing toprivacidad@engranalab.com. You can also lodge a complaint with the Spanish Data Protection Agency (www.aepd.es) or your local supervisory authority. General questions: geocode-sheets@engranalab.com.

Changes

If this policy changes in a relevant way, we will update the date above and, if the change affects what the add-on collects, we will say so in the changelog.