MoxiKit Trust Center
Understand how MoxiKit handles files, AI models, local cache, and network requests.
Files Stay on Your Device
Most file tools execute directly inside your browser. Files are not uploaded to MoxiKit servers.
Transparent Network Boundaries
Tools requiring model downloads or network access are clearly labeled. Page assets and user data are strictly segregated.
Local Data Under Your Control
Model caches, drafts, and preferences are fully visible and can be purged locally at any time.
Tool Processing Matrix
All tools in MoxiKit are categorized according to their verified data flow profiles, dynamically generated from the local registry:
| Tool Name | Processing Type | Data Flow & Network | Local Persistence | Action |
|---|---|---|---|---|
JSON Formatter | Local Processing | No upload · Offline | Memory only | Open → |
SQL Formatter | Local Processing | No upload · Offline | Memory only | Open → |
JSON to Code | Local Processing | No upload · Offline | Memory only | Open → |
SQL to Code | Local Processing | No upload · Offline | Memory only | Open → |
cURL Converter | Local Processing | No upload · Offline | Memory only | Open → |
Cron Studio | Local Processing | No upload · Offline | Memory only | Open → |
Timestamp Converter | Local Processing | No upload · Offline | Memory only | Open → |
Regex Tester | Local Processing | No upload · Offline | Memory only | Open → |
CSV Explorer & Cleaner | Local Processing | No upload · Offline | Memory only | Open → |
YAML / JSON Converter | Local Processing | No upload · Offline | Memory only | Open → |
UUID Generator | Local Processing | No upload · Offline | Memory only | Open → |
Diff Checker | Local Processing | No upload · Offline | Memory only | Open → |
3-Way Text Merge | Local Processing | No upload · Offline | Memory only | Open → |
Code Diff Viewer | Local Processing | No upload · Offline | Memory only | Open → |
Base64 String Encoder | Local Processing | No upload · Offline | Memory only | Open → |
Base64 File Converter | Local Processing | No upload · Offline | Memory only | Open → |
URL Encoder / Decoder | Local Processing | No upload · Offline | Memory only | Open → |
HTML Entity Encoder | Local Processing | No upload · Offline | Memory only | Open → |
URL Parser | Local Processing | No upload · Offline | Memory only | Open → |
Markdown Studio | Local Processing | No upload · Offline | Memory only | Open → |
Color Studio | Local Processing | No upload · Offline | Memory only | Open → |
Image Color Palette | Local Processing | No upload · Offline | Memory only | Open → |
Image Editor | Local Processing · Local Draft | No upload · Offline | Local draft | Open → |
Image Compressor | Local Processing | No upload · Offline | Memory only | Open → |
SVG Optimizer | Local Processing | No upload · Offline | Memory only | Open → |
QR Code Studio | Local Processing | No upload · Offline | Memory only | Open → |
AI Background Remover | Local Processing · Model Download | No upload · Download model | Model cache | Open → |
Batch AI Eraser | Local Processing | No upload · Offline | Memory only | Open → |
Batch Watermark & Rename | Local Processing | No upload · Offline | Memory only | Open → |
Image Upscaler | Local Processing | No upload · Offline | Memory only | Open → |
SVG Vector Tracer | Local Processing | No upload · Offline | Memory only | Open → |
Image Converter | Local Processing | No upload · Offline | Memory only | Open → |
Audio Trimmer & Cutter | Local Processing | No upload · Offline | Memory only | Open → |
Audio Converter & Resampler | Local Processing | No upload · Offline | Memory only | Open → |
Audio Compressor & Size Optimizer | Local Processing | No upload · Offline | Memory only | Open → |
Video Frame Extractor | Local Processing | No upload · Offline | Memory only | Open → |
Video Trimmer & Cutter | Local Processing | No upload · Offline | Memory only | Open → |
Video to GIF Converter | Local Processing | No upload · Offline | Memory only | Open → |
PDF Sanitizer | Local Processing | No upload · Offline | Memory only | Open → |
PDF Split & Merge | Local Processing | No upload · Offline | Memory only | Open → |
PDF Compressor | Local Processing | No upload · Offline | Memory only | Open → |
Private OCR Studio | Local Processing · Model Download | No upload · Download model | Model cache | Open → |
Scan to Word | Local Processing · Model Download | No upload · Download model | Model cache | Open → |
Hash Generator | Local Processing | No upload · Offline | Memory only | Open → |
JWT Decoder | Local Processing | No upload · Offline | Memory only | Open → |
EXIF Stripper | Local Processing | No upload · Offline | Memory only | Open → |
Data Flow & Memory Lifecycle
When you upload files, paste text, or perform operations in MoxiKit, data is read directly into the temporary memory of the browser main thread or Web Worker (such as ArrayBuffer, Blob, OffscreenCanvas).
Once completed, temporary data is automatically reclaimed by JavaScript garbage collection or tab unload. Except for tools explicitly designed with local draft support, MoxiKit writes no files to disk or remote servers.
AI & OCR Model Transparency
Select tools (such as background removal and OCR text extraction) utilize deep learning models. Here is how they operate:
Where are models downloaded from?
Model weights (.onnx files) are hosted on same-origin static storage or dedicated CDNs. Downloads consist solely of model parameters without transmitting user data.
When does the download trigger?
Only when you first open and run an AI-assisted tool, or when you explicitly pre-download models in the Local Resources panel.
Where does inference run?
Inference executes directly on your device CPU/GPU via WebAssembly and ONNX Runtime Web. Your images and documents never leave your browser.
How are models stored after download?
Downloaded models are persisted in browser CacheStorage so that subsequent runs execute instantly and offline.
Browser Local Storage Inventory
MoxiKit utilizes standard browser Web Storage APIs only where necessary to enhance user experience:
LocalStorage
Stores non-sensitive preferences: theme, locale, PWA status, recent tool IDs (up to 10 IDs; identifiers only without content), and favorite tool IDs.
SessionStorage
Stores transient session flags (such as dismissing PWA installation prompts for the current session).
CacheStorage
Caches offline AI/OCR model files and PWA shell assets for instant and offline capability.
IndexedDB
Utilized only by specific tools (such as Image Editor drafts and OCR history) for client-side persistence, entirely stored on your device.
How to purge local data?
You can clear all site data at any time in your browser settings (Privacy & Security -> Clear Site Data), or individually delete cached models in MoxiKit's Local Resources panel.
When Does MoxiKit Make Network Requests?
We strictly differentiate between page assets and user data streams:
- •Page Loads & Static Assets: Necessary HTML, CSS, JavaScript chunks, and font files requested when visiting the site.
- •AI Model Downloads: Initial downloads of model weights when running OCR or background removal tools.
- •User-Initiated Feedback: When you explicitly submit feedback or bug reports, the message body and basic diagnostics are transmitted to the server.
Search & Discovery Privacy
Built upon the MoxiKit PX-03 architecture, the command palette and discovery system operate client-side:
Telemetry & User Feedback Disclosures
Analytics & Metrics: MoxiKit uses privacy-conscious, aggregated analytics (Cloudflare Web Analytics for performance/CWV and Google Analytics 4 for traffic sources and minimal tool events). Default consent is set to denied. We strictly enforce privacy boundaries: tool processing content (files, OCR text, JSON/CSV data, error stacks) is never collected, and data is never used for advertising personalization or cross-site profiling.
Feedback: Only when you actively open the feedback modal and click submit, the entered text, optional contact, and basic diagnostics (UserAgent, viewport, PWA mode) are sent to help resolve issues. User files are never included.
Security Practices & Responsible Reporting
Security Architecture: Enforced HTTPS encryption, browser sandbox isolation (Web Worker / WASM execution), and zero server-side file persistence.
Security Reporting: If you identify potential security vulnerabilities or privacy concerns, please contact us via the feedback channel (selecting Bug/Security category). We review and respond promptly.
Privacy Policy & Legal Terms
The Trust Center provides an intuitive overview of product architecture. For comprehensive legal terms and formal policies, please visit our Privacy Policy page.