Spuffi Privacy Policy and Data Handling
Last updated: January 2025. Clear, transparent commitments regarding your personal data, privacy, and media handling.
No IPs, no link history
Logs record a pseudonym that changes daily instead of your IP, and only a link's host - never the full URL.
Short-lived files
Your file is written to disk while it is prepared, then deleted automatically within 15 minutes.
Zero advertising trackers
No tracking cookies, marketing beacons, or third-party behavioral analytics scripts.
1. Our foundational privacy commitment
At Spuffi, we believe privacy is not an optional feature or marketing slogan; it is an engineering requirement. When you use an online media extraction tool, you should never have to surrender your personal data, browse through advertising trackers, or worry about your viewing habits being cataloged by data brokers. Spuffi was architected specifically to eliminate data retention at every stage of the extraction pipeline.
2. Data we do not collect
We do not require account registration, email addresses, names, or passwords, and we never store your IP address or the full URLs you submit. What we do keep is deliberately minimal and short-lived: operational logs carry a pseudonym derived from your IP with a key that rotates every day, plus the host of the link (for example youtube.com) so we can tell which extractor is failing. The job record holds that same host, a timestamp and the job state for thirty minutes so the page can report progress, and is then deleted. When our server talks to YouTube, TikTok, Instagram or X, the request carries no user identifier of yours.
3. Cookies and local device storage
Spuffi does not use tracking cookies, cross-site behavioral cookies, or marketing beacons. We only utilize local browser storage (localStorage) for user interface preferences, such as your chosen language and color theme, so they stay consistent between visits. This data remains strictly stored on your own device hardware and is never transmitted back to our servers or shared with any third party.
4. Media file handling and server storage
Spuffi does not host, archive or index media. To trim and remux reliably we cannot stream straight through: the server downloads the requested video or audio from the source CDN to a temporary file, packages it as MP4 or MP3, and serves that file to you. A cleaner running every minute deletes it once it is 15 minutes old, whether or not you fetched it, along with any partial files left by an interrupted job. Nothing is kept on permanent storage and no backups of media are made.
5. Third-party services and infrastructure
Our infrastructure runs on cloud compute instances behind TLS 1.3. We do not partner with advertising networks, affiliate click brokers, or analytics vendors that profile identities. For page-level statistics we run our own Umami instance on our own domain: it is cookieless, records no cross-site identifier and never sees the links you paste. When you paste a link, the upstream connection exists only to fetch the public media manifest from that platform.
6. Open source verification
Trust is established through transparency, and the claims above are meant to be checkable rather than taken on faith. The complete source code is open: the log formatting, the IP pseudonymisation, the retention timers and the cleaner are all readable, and the test suite asserts that no raw IP or full URL reaches a log line. Security researchers and privacy advocates are invited to verify this directly.
7. User rights and direct inquiries
We hold no account data and nothing that identifies you personally, so there is no profile to export or erase. The one thing tied loosely to you is the daily log pseudonym, which cannot be reversed to an IP and stops being linkable when the key rotates. For technical or security questions about our infrastructure, encryption or media processing, review the repository documentation or open a public discussion.