Privacy Policy

Who is responsible

Optimization Services, LLC, organised in Indiana, United States, operates this service and is responsible for the data described here. Contact us at the support address in the footer.

What an account holds

The name and email address you register with, and billing details held by our payment processor rather than by us.

A record of your usage: which endpoint was called, when, and how many billed units it cost. This is what your invoice is computed from and what the usage export shows you.

What the usage record does not contain

It does not contain the coordinates you send. The record holds the consumer, the tier, the method, the path, the operation, the unit counts, the status, a timestamp and a request identifier — and there is no field in it that could hold request content.

There is one place your coordinates are touched and deliberately not kept. A directions request in its GET form carries coordinates in the URL, and we must read them to count what the request costs. That arithmetic happens in memory and returns a number; the number is stored and the coordinates are discarded.

Request content, and where we are still checking

We do not retain the coordinates you send as product data. That is true of the metering record by construction, as described above.

Operational logs are a separate question, and the answer differs by how you call us. Matrix requests are always POST and request bodies are never written to a log, so the endpoint most customers use puts no coordinates anywhere at any point.

A directions request in its GET form carries coordinates in the URL, and a URL does appear in an access log. On the routing server those logs are the only place request content can appear, they record the request line and nothing else, and they are deleted when they rotate — daily, keeping fourteen days.

We are still confirming the equivalent for the hosted API gateway in front of it, which is a setting on that platform rather than something we configure. This section will state its window plainly once we have it, and we would rather publish a policy that matches the systems than one that reads better than the truth.

How long we keep things

Account, billing and usage records are kept for as long as you have an account, and afterwards for as long as tax and accounting law requires us to.

Operational logs on the routing server are kept fourteen days and then deleted. The gateway's window is the one figure still being confirmed, as described above.

We do not keep your coordinates as a product record at any point, so there is nothing of that kind to delete on request.

Who else sees it

Infrastructure providers process data on our behalf in order to run the service: the hosting platform serving this website, the API gateway in front of the routing service, and the cloud provider hosting the routing server itself. Payment and sign-in providers process data for those functions when those features are live.

We do not sell personal data, and we do not share it for advertising.

This website, specifically

This site sets no cookies and runs no analytics. That was verified by loading it and checking, not assumed.

Three third-party hosts are contacted when you load a page. Two are Google's font services, which serve the typefaces and will see your IP address. The third is OpenFreeMap, which serves the map tiles on the playground and sees the tile requests your browser makes.

The playground stores one value in your own browser to space out its free runs. It never leaves your device and we cannot read it.

Your choices

You can ask for a copy of your account data, ask us to correct it, or ask us to delete your account and the records that are not required for tax purposes. Write to the support address and we will answer.

Closing your account stops future processing. It does not undo invoices already issued.

Changes

We will publish changes here with a new date. Where a change materially affects you and we have your address, we will tell you.