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.

If you arrived through an advertisement or a link, the campaign values your own browser recorded on your first visit, attached to the account at the moment you create it. What those are, and why they are collected before you have an account at all, is in 'This website, specifically' below.

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 no field in it holds 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

We may process and retain the content of your requests and the results we return, including coordinates, in order to operate, secure, debug and support the service, to investigate misuse, and to develop and improve how the service works. Anything we hold is held under the retention rules in the next section.

The rest of this section describes how the service works today. It is a statement of current practice, not an undertaking about how the service will always work. At present the metering record holds no request content and we keep no product record of the coordinates you send; if that changes, the change is published here with a new date.

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.

The API gateway in front of it keeps its own access logs, to the retention window set by the platform that hosts it.

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.

Request content we hold is kept only as long as the purposes above require. At present there is no product record of your coordinates, so there is none 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. We do share limited data with analytics and advertising providers so we can measure how well our advertising works — which advertisements led to accounts, and what they cost us. That is the only advertising purpose we use it for.

This website, specifically

This site and the developer portal use cookies and similar identifiers for three purposes: to keep the service secure, to understand how people use the site, and to measure whether our advertising works.

Analytics. We use analytics tools to count visits, see which pages are read, and see which actions people take, such as running the playground or creating a key. Some are cookieless. Others set a cookie holding a randomly generated identifier, written on the domain this site and the developer portal share, so one browser counts as one visitor across both.

Session recordings. We may record how visitors interact with a page (clicks, scrolling, navigation) to see where it is confusing. Recordings hide what you type, and the coordinates and results the playground shows.

Advertising measurement. Advertising platforms we buy ads from may set cookies or read an identifier they added to the link you clicked, so they can tell us which advertisements led to visits and accounts. Some of these companies can connect that identifier to what you do on other sites that use their services. We use this only to measure our own advertising, and we do not sell personal data.

Third-party hosts. Loading a page contacts a few outside services, which see your IP address: the providers of our fonts, map tiles, analytics and advertising measurement.

Providers we currently use: Plausible and Google Analytics (analytics); Amplitude (analytics and session recordings); Google Ads (advertising measurement); Google Fonts (typefaces); OpenFreeMap (playground map tiles). This list changes as our tools change, and the date at the top of this page shows when it last did.

Besides any cookies or storage the tools above use, the site itself keeps two things in your browser's own storage, which only this site can read.

The first is the playground's: one value recording when you last ran a request, so the page can space out its free runs. It never leaves your device and we cannot read it.

The second records how you arrived. On your first visit the page stores the campaign parameters that were in the address you came in on — the utm_ ones an advertisement or a newsletter adds, and the click identifier an advertising service adds — with the address of the page that linked you, the page you landed on, and the time. That first record is never changed afterwards; the most recent one is kept beside it.

That one is for us rather than for you, so it is worth being exact about. It is advertising measurement. Nothing is sent to us while you are only reading; if you create an account, those values are attached to it, which is how we tell whether an advertisement paid for itself. At that point the record stops being anonymous, because the account has your name on it. It is collected on the first visit rather than at sign-up for the plain reason that by sign-up it is gone: the address you arrived on is not recoverable later from anything we hold.

Clearing this site's data in your browser removes all of these, and nothing on the site stops working without them. Your browser's own controls for blocking cookies and scripts work here too; the site is built to work with them blocked.

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.

This page states our practices as they are now. They may change as the service develops, and this page is where that is published.