Privacy & Trust
How FileKit handles your files, what happens to uploaded data, and what you can expect from this service.
What happens to uploaded files
When you upload a file to FileKit, it is temporarily stored on the server for processing. The file is used only for the specific tool operation you requested (compression, conversion, metadata inspection, etc.). Once processed, the original upload and the output files are stored as part of a job record.
🔒 No data leaves this container. All file processing happens inside the FileKit server. Uploaded files and generated outputs are never sent to external APIs, third-party services, or used for training.
Retention and cleanup
Jobs and their associated files expire automatically after the configured retention period. Expired files are permanently removed from the server and cannot be recovered.
- Job retention: configurable (default 1 hour)
- Draft workspace retention: configurable (default 7 days)
- No manual cleanup is needed — the system handles it automatically
- If a job expires before you download, rerun the tool with the same file
If you need to keep a file permanently, download it to your device. Files you keep via the browser's working set or favorites are stored in your browser's local storage, not on the server. These persist across sessions as long as you don't clear your browser data.
📦 Recovery options for expired jobs:
• Use the same tool again — reprocess your file to create a new job
• Check your browser's working set for files you previously kept
• Files on the server cannot be recovered after expiry
What is stored on your device
FileKit uses your browser's localStorage to remember your preferences and activity across sessions:
- Working set — files you've chosen to keep across sessions
- Favorites — starred files for quick access
- Recipes — saved tool configurations
- Drafts — unsaved workspace setups
- Session metadata — visit count, last activity, recent tools
- Event tracking — local analytics for product improvement
All of this data stays on your device. It is not uploaded, shared, or accessible to us. Clearing your browser data or local storage will remove it.
No account required
FileKit works without sign-in, user accounts, or personal data collection. There is no tracking network, no analytics SDK, and no third-party cookies. Your use of the product is anonymous by design.
What we do not do
- We do not collect personal information
- We do not use third-party analytics or tracking
- We do not sell or share your data
- We do not use uploaded files for training or model improvement
- We do not send files to external services
- We do not require accounts or sign-in
- We do not set tracking cookies
Current product boundaries
FileKit is a file processing tool, not a storage service. Important boundaries to be aware of:
- Upload limit: 100 MB per file
- Job retention: 1 hour — download outputs before they expire
- No end-to-end encryption (files are processed server-side)
- Not all tools have active execution adapters — some are planning-only
- Session-based — there is no persistent user identity across devices