Security
iExport is built so message content never leaves your device.
Architecture
Parsing message files happens in the browser via JavaScript and WebAssembly. No server receives message content and no cloud staging occurs.
Transport
Everything we fetch is static assets and a payment receipt. Traffic is encrypted with modern TLS.
Third parties
- Payment: handled by our payment provider (card numbers never reach iExport).
- Analytics: aggregated anonymous events only — never message content.
- Error reporting: used for stability, no message data included.
Verify for yourself
Open DevTools → Network. Run a full export. No request should contain message content.
Frequently asked questions
- How can I verify messages aren't sent?
- Open DevTools → Network while using iExport. You will not see message content in any request.
- Is the service encrypted?
- All traffic between the browser and our services uses HTTPS with modern TLS.
- Where is purchase data stored?
- With our payment provider. We keep only an anonymized reference to tie purchases to downloads.