Verifiable privacy
Privacy Verification Guide
Don't trust us — verify yourself.
Your files are processed in your browser. No document bytes are uploaded to Aladdin for processing. This guide shows exactly how to prove that your file bytes never leave your device.
Open DevTools → Network
Before uploading any file, open your browser Developer Tools (F12 or Cmd+Option+I). Go to the Network tab. Enable "Preserve log" so requests are not cleared when the page updates.
Filter for uploads
Use your file in any Aladdin tool. Watch the Network panel: you should see only static assets (.js, .wasm, fonts, CSS). There must be no POST/PUT requests containing your PDF, image, or document bytes.
Offline / airplane mode test
Turn off Wi-Fi or enable airplane mode — local tools keep working. That proves there is no cloud dependency for supported workflows.
Inspect our source
All tool logic ships as static JavaScript and WebAssembly bundles from Cloudflare CDN. No hidden API endpoints receive file data for local tools. You can view bundled client code in DevTools → Sources.
Verifiable boundaries
Wasm engine
Supported tools use browser APIs, JavaScript, Web Workers, and self-hosted WebAssembly where documented. Processing stays in the current tab.
No document upload
Document operations run in your browser without sending file bytes to Aladdin for processing. You can verify this in DevTools → Network.
Bypass the cloud
Supported workflows avoid uploading document bytes to Aladdin. Runtime depends on your file size and device — not on our servers.
What our servers do
Our servers only distribute static JavaScript and WebAssembly. We never receive, store, or cache your private files for local tools.
Open DevTools → Network before you open a file. You should see only static assets (.js, .wasm, CSS). No POST or PUT requests contain your PDF, image, or document bytes.
What we never do
- Receive, store, or cache your private files on our servers
- Call third-party cloud APIs with your document bytes (for local tools)
- Require registration or login for basic local tools
- Retain GPU batch uploads beyond 10 minutes (Pro optional feature only)
Medical & dental records
Tools like Dental Local Record store data only in your browser's LocalStorage. Clear site data in your browser to remove it — we have no copy.
Common questions
- Are my files private? Do you upload or store them? For local tools: your files are never uploaded, stored, or seen by us. There is no upload step — processing runs in your browser via JavaScript and WebAssembly. Follow our privacy verification guide to prove it with DevTools and offline mode.
- Can I use Aladdin offline? Yes, for supported local tools. After the page loads, turn off Wi-Fi — the tool should still process your file. That is how you prove zero cloud dependency.
- What do your servers actually do? They serve static JS, Wasm, and HTML from Cloudflare. They do not receive document bytes for local tools. Optional Pro GPU batch is the only path where you voluntarily upload — auto-deleted in 10 minutes.
- How is this different from cloud converters? Cloud tools upload your file to their servers. Aladdin local tools keep bytes on your device. Check Network tab: no file payload leaves your machine.