"Where do my files go when I use your tools?"

Nowhere. That's the answer, and here's why it's true.

The architecture

Every functional tool on Craftisle follows the same pattern:

User drops file → File loaded as ArrayBuffer → Processed in browser → Download result

There is no server that receives your file. No middleware that reads it. No S3 bucket it gets stored in. The tool page loads static assets from a CDN, then everything that happens to your data happens in your browser tab.

What technology makes this possible

• Web Crypto API — AES-GCM, SHA-256, PBKDF2. Browser-native crypto. No custom crypto library, no third-party crypto server.
• Canvas API — image resize, crop, format conversion. Same API photo editors use.
• WebAssembly — pdf-lib and qpdf.wasm for PDF processing. C++ compiled to WASM, running in a browser sandbox.
• localStorage — resume builder data, favorites, settings. No server-side user database.

What we do collect

Not much:

• Page views — anonymous, via a self-hosted analytics instance (Plausible). No cookies, no fingerprinting, no cross-site tracking.
• Error logs — client-side errors reported to the browser console only. No remote error collection. If something breaks, we rely on GitHub Issues.

No email collection, no newsletter tracking, no ad retargeting. If you're not signed in, you're an anonymous visitor.

What we don't do

• No file upload to any server (functional tools).
• No cloud storage of user data.
• No analytics tied to individual users.
• No third-party scripts in the tool workspace (the /tools routes have minimal external JS).

The limits of client-side privacy

Client-side processing is private by default, but it has trade-offs:

• Performance ceiling. Your browser, not a server farm, does the heavy lifting. Large files slow down.
• No collaboration. Real-time co-editing requires a server. Craftisle doesn't do it.
• Memory limits. Chrome tabs have ~2-4GB of usable memory on a typical machine. A 500MB file won't load.

Third-party subprocessors

The site is hosted on Vercel. CDN assets are served through Vercel's edge network. Payments (if enabled for premium features in the future) would go through Stripe.

No other third parties process Craftisle user data.

FAQ: Privacy & Client-Side Processing

How to process PDFs without uploading to server?

Use pdfcraft — all 67 PDF tools run in-browser via WebAssembly. Files never leave your machine. No server receives your file.

Is Craftisle safe for sensitive documents?

Yes — all tools are client-side. No file upload, no server storage, no analytics tied to individual users. Open DevTools Network tab, use a tool, confirm: zero outbound data.

How to remove EXIF GPS data from photos free?

Use Strip Metadata tool — removes EXIF, GPS coordinates, camera model. Batch mode available. Run before posting photos to public forums.

Read the full Privacy Policy and Terms of Service. Try any tool at craftisle.com/tools — confirm zero outbound data.