Trust, data portability & deliverability

Your data is yours — provably

The push industry has burned people: "free forever" providers shut down with subscriber bases locked inside, and the biggest free tier historically monetized by sharing interaction data with advertisers. WingBlaze's answers are concrete, not promises:

• One-call full export. GET /v1/apps/:appId/export streams your entire audience as NDJSON — every subscriber with devices and tags inline, your suppression list, and a summary line with counts. Any size, any time, no support ticket. Per-subscriber export exists too (GET /v1/apps/:appId/subscribers/:id/export, includes recent events).
• Real deletion. Deleting a subscriber cascades through devices, tags, inbox items, and journey state. Deleting an app removes everything it owns.
• No ad monetization. Ever. Your subscribers are not the product; the subscription is. Nothing is shared, sold, or "anonymized and aggregated" to third parties.
• Standard formats in. Importers for OneSignal (CSV) and AWS Pinpoint (endpoint JSONL) — switching to us is easy, and the export above means switching away stays easy. We'd rather keep you with the product.

Where your data lives

Everything is hosted in asia-southeast1 (Singapore) — no cross-region replication. For Malaysian PDPA (2024 amendments) and Indonesian PDP (UU 27/2022) compliance work, in-region hosting means no cross-border transfer assessment for the messaging data path. Security controls (encryption of credentials at rest, RBAC, audit logging, tenant isolation) are documented in the SOC 2 readiness mapping in the repository.

Email deliverability

WingBlaze ships the compliance rails automatically: RFC 8058 one-click unsubscribe headers on every marketing email, automatic bounce and complaint suppression (checked before every send, transactional included), and a strict transactional/marketing separation — transactional mail never carries an unsubscribe offer and never queues behind campaigns.

What you configure on your side:

1. Verify your sending domain (not a shared one) in SES via the setup flow: SPF (include:amazonses.com), the three DKIM CNAMEs, and a DMARC policy — start with p=none; rua=mailto:you@domain, tighten to p=quarantine once reports look clean.
2. Warm up gradually. New domains should ramp over ~2–4 weeks; use segments to send to your most-engaged subscribers first (the _engagement auto-tag is built for exactly this).
3. Watch the suppression list (GET /v1/apps/:id/suppressions): rising complaint suppressions mean content or targeting problems — fix those before they become reputation problems.
4. Keep marketing off transactional traffic. The lanes are separate so receiver reputation systems see consistent behavior per stream.