Trust and Reliability
The evidence behind WarpLink's speed, reliability, and accuracy claims: methods, failure behavior, attribution testing, data portability, and plan changes.
This section answers the questions a team asks before it depends on link infrastructure. Each page states what we measured or what the code does, with dates and sample sizes where a number appears. Where we have not measured something yet, the page says so.
| Question | Page |
|---|---|
| What does "sub-10ms" measure, and how big are the SDKs? | Performance and methodology |
| What happens when the database, the API, or the click queue is down? | Architecture and failure modes |
| How accurate is install attribution, and how do I test it on my devices? | Attribution accuracy |
| Can I leave, and what do I take with me? | Data portability and leaving WarpLink |
| What happens to my links when I cancel, downgrade, or miss a payment? | Plan changes and billing transitions |
How these pages are kept
- A number appears only with its measurement date, its sample size, and how to repeat it.
- A behavior appears only when it is in the code we run.
- When a number changes, we update the page and its date instead of adding a second page.
Flutter API Reference
The complete Dart API reference for the WarpLink Flutter SDK: configure, deep link events, deferred checks, attribution, and error types.
Performance and Methodology
What WarpLink's sub-10ms redirect figure measures, a dated warm-link test with its sample size, client latency from one location, and measured SDK sizes.