Your work stays on your device
MoxiKit's core tools run inside your browser. Your files, text, code, and results are not uploaded for processing. This page explains the exact boundaries—including the network requests that can still occur.
Looking for an intuitive trust overview?
Visit the MoxiKit Trust Center for dynamic tool processing types, AI model mechanics, local storage inventory, and network boundaries.
The privacy contract
Local processing
PDFs, images, credentials, code, and text are processed with browser APIs, JavaScript, WebAssembly, or local workers on your device.
Privacy-Guarded Analytics
MoxiKit uses privacy-controlled, aggregated traffic and minimal product usage metrics (GA4 & Cloudflare) to optimize performance. Your files, raw text, and tool outputs are strictly forbidden from leaving your device or reaching analytics services.
No account required
Core tools work without registration. MoxiKit does not need an identity profile to process your content.
What may use the network or local storage
Local processing does not mean every feature is network-free. These limited data flows are separated from your actual content.
Optional model downloads
OCR and AI-assisted tools may download model files on first use. Processing remains local after the required assets are available and cached.
Storage on this device
Theme, favorites, PWA state, offline assets, temporary OCR pages, and image-editor drafts may be stored in browser storage. They remain under your browser profile and can be removed through site-data controls.
Feedback you choose to send
The feedback form sends the message, feedback type, page, language, optional contact details, and optional diagnostics only after you submit it. Do not include confidential content.
Content we do not collect
- File names, local paths, or file contents
- JWTs, cookies, private keys, or credentials
- OCR text, code, diffs, or exported results
- Cross-site advertising or behavioral profiles
Your controls
You can clear MoxiKit data using your browser's site-data settings. Individual tools should also release temporary files and previews when a task is cleared or the page is closed.
Opening the site still makes normal requests for pages and static assets. Installing the PWA or using model-based tools may cache those assets for offline use.
Architecture statement reviewed: August 2, 2026.