Legal

Terms, privacy, accessibility, and cookies

Privacy Policy

Draft — pending legal review. This is a good-faith placeholder reflecting what Marco Map actually collects and stores. Formal policy language will replace this page after legal review.

Effective date: 2026-10-15 (draft)

What we collect

Account data

  • Email address
  • Username (display name)
  • Hashed password (bcrypt; we never see your plain-text password)
  • Account creation and last-login timestamps
  • If you sign in with Google: the email address and name your Google account shares with us when you choose to. We use them only to find or create your Marco Map account. We never receive your Google password.

Usage data

  • Search queries typed into the global search bar, stored in app.searched_address
  • API request logs (URL path, response status, duration), stored in app.apirequestlog
  • Client IP address, captured on each request for rate-limiting and abuse detection

User-generated content

  • Custom regions you draw or save (app.saved_regions)
  • Composite Index definitions and results
  • Map Builder projects and uploaded geometry files
  • Feedback you submit via the in-app feedback form

Authentication cookies

  • jwt — session token, set by the LB4 auth backend after login
  • agent_key — optional API-key cookie used by automated testing agents

What we don't collect

  • Browsing activity outside Marco Map
  • Third-party marketing trackers or pixels
  • Device fingerprinting beyond standard HTTP headers
  • Anything from your Google account beyond the email address and name above, if you sign in with Google

How we use your data

  • Providing the Service (authentication, saving your work, rendering analyses)
  • Debugging and performance tuning (looking at logged API latency, error rates)
  • Preventing abuse (rate-limiting, identifying scraping activity)

We do not sell your data or license it to advertisers. We share it with a third party only where a feature you use needs it (see the Road Trip Planner below, which sends the places you type to Google) or as required by law.

Road Trip Planner

The Road Trip Planner (/road-trip) works without an account. Here is what happens to what you give it:

  • The places you type are sent to Google. As you type a starting point, a destination or a stop, the text goes through our server to Google to find suggestions, and the places you choose go to Google to work out the route. If you choose "use my location", your browser asks your permission, and your current location is sent the same way to work out the route.
  • Your saved choices, never an address. The planner remembers choices such as your vehicle, your phone carrier, meal times and favorite brands. If you are not signed in, they are kept in a cookie in your browser (marco_trip). If you are signed in, they are kept with your account, or in that same cookie on this browser if your account cannot hold them yet. Signing out removes the cookie. The places you plan between are never saved in it or in your account; the page's own address carries the trip so a reload or a bookmark brings it back.
  • A daily count of planning requests. To keep the planner affordable to run, we count how much planning each signed-in account, and each network without an account, asks for in a day. For a network, the count is kept under a one-way, keyed hash of its network address, never the address itself. These counts are deleted after about 30 days.
  • Server logs. Our web server's access logs record the address of each request, which can include the text of address suggestions as you type. A trip link keeps its places after a "#" in the web address, a part your browser does not send to us; an older trip link that carried them before the "#" is logged like any other address.

Retention

  • Account data is kept for the life of your account.
  • API request logs are retained for 90 days then aggregated into anonymized summary metrics.
  • Search history is retained for 365 days unless you request deletion sooner.
  • Road Trip Planner daily request counts are deleted after about 30 days.
  • Exported ZIPs and Map Builder uploads are retained for 30 days after last access.

Your rights

Under CCPA (California), GDPR (EU/UK), and comparable regimes, you can:

  • Access — request a copy of the data we hold about you
  • Port — receive it in a machine-readable format (JSON / ZIP)
  • Correct — ask us to fix inaccuracies
  • Delete — ask us to erase your account and associated data

To exercise any of these rights, email [email protected] with the email address on your account. We will respond within 30 days.

Note

the in-app /account page will automate these requests once its backend endpoints land. Until then, email is the canonical channel.

Security

Passwords are hashed with bcrypt. Sessions use HTTP-only, secure cookies. All traffic is served over TLS. Staff access to production data is restricted and audit-logged.

Despite these precautions, no system is perfectly secure. If you believe your account has been compromised, email [email protected] immediately.

Children

Marco Map is not directed at children under 13. We do not knowingly collect data from children.

Changes to this policy

Material changes will be announced on /changelog and reflected in the Effective date above.

Contact

Privacy questions or data-subject requests: [email protected].


See also: Terms of Service · Accessibility Statement · Cookie Policy