About WarpLink

Last updated: October 10, 2026

In short. We run WarpLink as link infrastructure for mobile teams, covering deep linking, install attribution, and real-time analytics. Monitoring runs around the clock, every release is dated in the changelog, and our commitments on notice, refunds, and breach reporting are published.

How we run the service

Automatic monitoring runs around the clock and alerts us at any hour, so we do not wait for a customer to report an outage. The redirect service exposes health checks for liveness and readiness. For a production outage reported to support@warplink.app, we aim to acknowledge within 4 hours, 7 days a week. Every other request gets a reply within one business day on paid plans and three business days on Free.

Service-wide incidents are posted in the changelog. The Support page has the full reply targets, and Architecture and failure modes describes what keeps working when a dependency is down.

How we ship

Releases are dated in the changelog, which starts on June 6, 2026 and holds more than ten entries. The iOS, Android, React Native, and Flutter SDKs are open source under the MIT license, and each is at version 1.1.0.

Each SDK major version and each API version keeps working for at least 12 months after its replacement ships. You get at least 90 days' email notice before anything stops working. The deprecation policy has the details.

Our commitments

  • If we ever discontinue WarpLink, we give at least 90 days' notice by email and refund prepaid fees for time after the service ends.
  • We notify customers of a personal data breach within 72 hours of becoming aware of it.
  • Your custom domains belong to you. You can point them elsewhere at any time.
  • You can export your link configurations and click analytics at any time. The data portability guide lists what you take with you.

Where we are

We are based in Toronto, Ontario, Canada. Write to the address that fits your question.

Free tools

Three checkers run without an account on the free tools page. The AASA validator fetches an apple-app-site-association file the way iOS does. The assetlinks.json validator fetches a Digital Asset Links file the way Android does. The legacy link checker tests whether an old page.link address still redirects, and where it lands.