Travel creators with numbers you can trust.

The reason creator platforms end up leaking accounts is almost never a clever attack. It is scope creep: a product asks for publishing permission “for later”, keeps it for years, and one breach turns into thousands of hijacked profiles. So we decided the boundary before writing the integration, and we publish it.

We request analytics read access. We do not request publishing, deletion, messaging or social graph permissions — not because we have no ideas for them, but because a permission that was never granted cannot be abused if our own systems fall over.

Tokens never reach the browser. They are not in local storage, not in a cookie, not in a client bundle, and never in a URL. They live encrypted in a vault separated from the application database, with the key held outside it, and they are redacted from every log and error report. Even our own staff interface shows only a connection status and an expiry date.

And there is no scraping. No cookie sharing, no headless login, no third-party data broker. Official APIs or nothing — which occasionally means a metric is unavailable, and we would rather show a gap than a number we obtained in a way that puts your account at risk.