Last updated: September 2026
To operate DMflux we rely on the providers below. Each processor listed here processes personal data only on our instructions, under the terms of their data protection agreements with us. Paystack is not a sub-processor: it is an independent controller for the payment data it collects, and is listed for completeness. This list is kept current; material additions are announced per the Privacy Policy.
| Provider | Service | What they process | Role | Location |
|---|---|---|---|---|
| Vercel | Application hosting | Account holders’ requests and session cookies; request logs | Processor | Global edge network |
| Supabase | Database & authentication | Account records, organizations, campaigns, click records | Processor | EU (Ireland) |
| Cloudflare | Click redirect worker & edge network | Click requests (IP, user-agent, language header, coarse location) and short-lived dedup records | Processor | Global edge network |
| Backblaze | Object storage | Support screenshots attached to help requests | Processor | EU Central (Amsterdam) |
| Resend | Transactional email | Recipient email addresses and message content for invites, receipts, and payment notices | Processor | United States (email-sending region selected per account) |
| Paystack | Payment processing | Subscriber email, name, and payment details. Paystack is the data controller for payment card data it collects | Independent controller (payments) | Nigeria / Global |
Account data. For your DMflux account — registration email, subscription and billing metadata, and support requests — DMflux is the data controller: we decide why and how that data is processed to operate the service. This is covered by the Privacy Policy.
Campaign measurement data. For the click records and campaign analytics collected through your tracking links, DMflux is the data processor and you (the campaign owner) are the data controller. We process that data only to provide the analytics you configure.
Security and fraud data. For fraud prevention, abuse detection, security logs, and the operation of DMflux itself, DMflux acts as an independent controller, as described in the Privacy Policy.
People who click tracking links never create an account with us. The data recorded about a click, and why, is described in the “Data about ad campaign visitors” section of the Privacy Policy.