Privacy Policy

Effective · Version 2026-11-10

acre does most of its work on your own device and keeps little about you. This policy explains exactly what we do collect, why, who else is involved, and the choices and rights you have.

1. Who we are

acre is the web map at useacre.app. In this policy, "we" and "acre" mean the operator of that service, which decides how and why your personal data is handled. Every question, request or complaint about privacy goes to [email protected].

2. What we collect and why

Personal data we handle
What Why
Your email address To create your account, send sign-in codes and recognise you when you come back.
Sign-in events and timestamps To run sign-in (codes are stored only as hashes), keep you signed in for 30 days and detect abuse.
Your acceptance of the Terms and this policy, with the time and version To show that you agreed when you created your account.
What you choose to save on our servers: projects, places, notes, coordinates, records To provide the saved-places features and let your work follow you across devices. Only stored on our servers if you choose that; see where your saved data lives.
Technical request data, such as your IP address, in server logs To keep the service secure, prevent abuse and fix faults.
Anonymous analytics events To see which pages and features are used so we can improve acre. See analytics.

3. What we do not collect

  • Passwords. acre has none; you sign in with an emailed code.
  • Payment information.
  • Advertising profiles. We do not run ads or use advertising cookies.
  • Your location. See below: it stays in your browser.

When the map opens it asks your browser for your location, and your browser shows its own permission prompt. If you allow it, the map opens there and shows a dot. The position is used only in your browser to place the map. It is never sent to acre's servers or stored by acre. The map data services listed below still receive the area your browser asks them for, as with any other map view.

If you switch on Navigate, your browser reads your device's position (with your permission) to show it on the map, work out speed and course, steer you to a point and watch an anchor circle. That position, and the track you record, stay in your browser on this device and are never sent to acre. A recorded track is kept on the device until you clear it. If you choose Save to Places, the track is stored like any other saved place, following the storage choice you made in Account and data.

3b. Saving maps for offline use

If you save an area in Places > Offline, your browser downloads that area's map tiles, terrain, sea floor, charts, sea marks, fonts and place names directly from the public services listed below and keeps them on this device (in the browser's IndexedDB). Which area you saved, and its name, stay on this device and are not sent to acre. The services that serve the tiles see the downloads as they see any map view. The app itself is also kept by a service worker so it opens without a connection, and the last weather forecast your browser fetched is kept so it can be shown, with its age, when there is no signal. Delete a saved area from the same panel, or clear this site's data in your browser, to remove it.

4. Public data services your browser contacts

To draw the map, your browser contacts public data services directly. They are not our processors and acre's server does not store these requests. The one exception is airport weather reports (METAR and TAF) and marine buoy readings: the NOAA services that publish them do not accept requests from web pages, so acre's server asks for them on your behalf and keeps each answer in memory for a few minutes. When you use those layers our server therefore sees the area you are looking at (and, for a forecast, the airport code) together with your IP address for that request; we do not log or keep the area, and the IP address is handled as described in section 2. Each service receives your IP address and the area you asked for (and, for search, the text you typed), and handles it under its own privacy policy. They include:

  • NASA (Blue Marble, VIIRS night lights, GIBS, EONET)
  • Esri (World Imagery and Wayback aerial photos)
  • OpenFreeMap and OpenStreetMap contributors (the Streets, Topographic and Ocean maps, and place names), NOAA NCEI and GEBCO (sea-floor depths)
  • Microsoft Planetary Computer (Sentinel-2, NAIP, Landsat, Sentinel-1)
  • EUMETSAT, NOAA (GOES) and JMA (Himawari), the latter two via NASA GIBS
  • RainViewer
  • Open-Meteo (forecasts, marine forecasts, past weather and the places you set alerts for or look up spots at)
  • NOAA Aviation Weather Center and National Data Buoy Center (airport and buoy reports, asked for by acre's server), NOAA, Canadian Hydrographic Service nautical charts, GEBCO and EMODnet sea-floor maps
  • The Overpass service for OpenStreetMap, when you press Find spots
  • USGS (earthquakes and National Hydrography)
  • OpenFreeMap and OpenStreetMap, including OpenStreetMap Nominatim (search)
  • OpenSeaMap
  • GDACS (natural hazard events)
  • Open oil and gas infrastructure inventories

Which of them are contacted depends on the layers you switch on. You can reduce what they see by keeping layers off, or by using a VPN.

5. Legal bases

Where the law (such as the UK or EU GDPR) requires a legal basis, we rely on:

  • Contract: to provide the account and saved-places features you ask for.
  • Legitimate interests: to secure the service, prevent abuse, keep logs, and understand and improve how acre is used with anonymous analytics. We think this is proportionate because the analytics carry no email, coordinates, place names or note text, and honour Do Not Track.
  • Legal obligation: where we must keep or share data to comply with the law.
  • Consent: where it is needed, for example if you allow your browser to share your location with the map. You can withdraw consent at any time.

6. Who processes data for us, and where

We use a small number of service providers, who process data on our behalf:

  • Railway hosts the acre service and its database.
  • Cloudflare delivers the sign-in emails (from [email protected]).
  • PostHog (US cloud, us.i.posthog.com) provides anonymous product analytics.

These are US-based cloud services, so your data may be processed in the United States and other countries where they operate. If you are in the UK, the EEA or Switzerland, this means your data may be transferred outside your region. Where required, we rely on the safeguards the providers offer, such as standard contractual clauses or other approved transfer mechanisms. We do not sell personal data. We may also disclose data if the law requires it, or to protect the safety and security of the service and its users.

7. How long we keep data

  • Account data (email, saved data you stored on our servers): until you delete your account, then removed from our systems. Backups age out on the hosting provider's backup schedule.
  • Sign-in codes: stored only as hashes and deleted after they expire (10 minutes).
  • Sessions: 30 days.
  • Server logs: kept for a limited period set by our host, then removed.
  • Analytics events: kept according to PostHog's retention settings for our project.
  • On-device data: stays in your browser until you clear it or delete it in the app.

8. Security

Your account email and all saved user data on our servers (projects, places, notes, coordinates, records, settings) are encrypted at rest with AES-256-GCM. The keys are held in the application's configuration, separate from the database, and email lookups use a keyed hash. Sign-in codes are stored only as hashes and expire in 10 minutes. The session cookie is HttpOnly, SameSite=Lax and Secure, and lasts 30 days.

We want to be honest about what this does and does not do. Application-level encryption protects your data if the database or a backup leaks. It does not stop the running service from reading your data, because the service has to decrypt it to show it to you. No system is perfectly secure, and we cannot guarantee that data will never be accessed without authorisation. If you find a security problem, please tell us at [email protected].

9. Where your saved data lives, export and deletion

You choose where your saved data lives:

  • On our servers: stored encrypted, and available on every device you sign in on.
  • On this device only: stored in your browser's own storage and never sent to acre's servers. Authentication and your account email are always on the server.

In the app you can export everything we hold or keep on your device to a JSON file, import it again later, and delete your account and all data held on our servers. For data kept only on your device, clearing your browser's site data removes it.

10. Cookies and browser storage

  • One strictly necessary cookie, acre_session, keeps you signed in (30 days). It is HttpOnly, SameSite=Lax and Secure. It does not need your consent because the service cannot work without it.
  • Local storage and IndexedDB hold your saved preferences (layers switched on, panel state), cached map data, areas you saved for offline use (map tiles and place names) and your saved data if you chose "on this device only". A service worker keeps the app's own files so it can open without a connection.
  • No advertising cookies and no third-party trackers.

11. Analytics

We use PostHog (US cloud, us.i.posthog.com) for anonymous product analytics: page views and feature usage events, for example which layer was switched on. It is set up to not set cookies or store identifiers in your browser (data is kept in memory only), with no session recording and no automatic capture of text or inputs. It respects your browser's Do Not Track setting. We never include email addresses, coordinates, place names or note text in analytics events. This helps us improve the product. You can avoid analytics entirely by turning on Do Not Track in your browser.

12. Your rights

Depending on where you live, you may have the right to access your personal data, correct it, erase it, receive it in a portable format, restrict or object to how it is processed, and withdraw consent at any time. Much of this you can do yourself in the app (export and delete). For anything else, email [email protected]; we may need to confirm that you control the email address before we act, and we will answer within the time the law requires. You also have the right to complain to your local data protection supervisory authority.

13. California and similar laws

We do not sell your personal information and we do not share it for cross-context behavioural advertising. You can ask us to access or delete your information, and we will not treat you differently for doing so.

14. Children

acre is not for anyone under 16 and we do not knowingly collect personal data from children under 16. If you think a child has given us personal data, write to [email protected] and we will delete it.

15. Changes to this policy

We may update this policy. When we do, we will change the version and effective date at the top and, for changes that matter, say so on this site.

16. Contact

Privacy requests, questions and complaints: [email protected]. See also the Terms of Service and how acre works.