Reliability & Operations
This page explains how Synaptyx stays dependable — the safety nets, how updates ship without downtime, and how your data is handled. For the uptime promise itself, see The SLA Explained.
Layered redundancy
Reliability is built in independent layers, so a single failure rarely reaches your visitor:
| Layer | What it protects |
|---|---|
| Global edge | Serves redirects close to visitors; survives routine restarts and incidents. |
| Automatic fallback | If the edge can’t answer something, the request is handled transparently. |
| Durable clicks | Clicks are held safely and replayed if anything downstream is briefly busy. |
| Campaign safeguards | Monitor failover and offer caps keep your funnels resilient to third-party failures. |
The full breakdown is on Failover & Outages.
Updates without downtime
New releases ship continuously without taking the platform down. Updates are rolled out so that a problem with a release can’t interrupt the redirects and tracking that are already running — your traffic keeps flowing while we improve the product behind the scenes.
Status & monitoring
Synaptyx continuously monitors its own health and publishes a public System Status page so you can check service health at a glance.
Data retention
Your data is retained for your plan’s window, then automatically pruned — and visitor IPs are anonymized over time for privacy:
| What | Retention |
|---|---|
| Clicks, conversions, pixel events | Your plan’s window — 90 / 180 / 365 days (Starter / Pro / Scale); 90 days when inactive |
| IP anonymization | Visitor IPs are anonymized after 30 days (the record is kept for analytics, but the precise IP is removed) |
This happens automatically — nothing for you to manage.
Security posture
| Area | What we do |
|---|---|
| Your secrets | Connected credentials (ad accounts, payment providers, bots) are encrypted at rest. |
| Your account | Sessions can be revoked instantly — at the device, account, or whole-workspace level — plus optional two-factor authentication. |
| Outbound calls | Postbacks, webhooks, and notifications are sent through safeguards that prevent them from being abused to reach private systems. |
| The dashboard | Hardened against common web attacks; machine-to-machine endpoints are verified by signatures and secrets. |