Privacy & FAQ
Transparency and security are at the core of filetype.co. Here is how we protect your data.
Privacy Policy
At filetype.co, we prioritize your security. Our tool is designed to inspect files without compromising your data. We adhere to a strict "no-persistent-storage" policy. Our servers act only as transient processors to provide immediate file analysis.
verified_user The "No-Copy" Guarantee
We never store your file contents on disk. Once the inspection is complete and the results are delivered to your browser, all related temporary data is purged from server memory.
In-Memory Processing
Your file is read into server memory for analysis and discarded immediately after. Nothing is written to disk, database, or cloud storage at any point.
Zero Third-Party Sharing
No file data is ever sold, shared, or transmitted to third parties. We use no marketing trackers, advertising pixels, or analytics that capture file contents.
No Logging of File Contents
Server logs record only request metadata (timestamps, response codes) for operational purposes. File names, file contents, and analysis results are never logged.
Disclaimer: This tool provides informational file analysis only. It is not a security scanner, antivirus, or malware detection service. Results should not be used as the sole basis for trust decisions about files. Always exercise caution with files from untrusted sources.
Frequently Asked Questions
Yes. The web tool is free for individual and commercial use with no account required. We may offer premium API tiers in the future for high-volume automated access, but the manual inspection tool will remain free.
The current limit is 20 MB per file. This covers the vast majority of documents, images, and archives that need inspection. We may increase this in future updates.
We can identify encrypted archives (like password-protected ZIP or 7z files) and flag them accordingly, but we cannot inspect the contents within them without the decryption key.
We use magic byte analysis (reading the binary signature at the start of the file) rather than relying on the file extension, which can be easily faked. This is done server-side using the open-source file-type library.
Have more questions?
If you have questions about our security practices or technical details, feel free to reach out.
Contact Us