Spuffi Privacy Policy and Data Handling
Last updated: January 2025. Clear, transparent commitments regarding your personal data, privacy, and media handling.
No personal logging
We do not track, catalog, or associate your IP address with the media URLs you submit.
Ephemeral processing
Media chunks are processed dynamically in temporary memory buffers and deleted immediately.
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 user account registration, email addresses, names, or passwords. We do not maintain databases of submitted video links, download timestamps, or user IP addresses. When our backend server communicates with public media platforms like YouTube, TikTok, Instagram, or X, the request is executed through isolated server connections that do not forward user identifiers. Once your media stream is delivered to your browser, all temporary memory allocations are wiped clean.
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 keeping your chosen color theme 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, store, or archive copyrighted media files on permanent disk storage. Our service operates as an active proxy demuxer: when a media stream is requested, our server reads the video or audio chunks from verified source content delivery networks, packages the container format into standard MP4 or MP3, and pipes the data directly to your client connection. Temporary scratch files used during clip trimming operations are purged automatically by scheduled cleanup routines.
5. Third-party services and infrastructure
Our application infrastructure is hosted on secure cloud compute instances protected by standard transport layer security (TLS 1.3) encryption. We do not partner with programmatic advertising networks, affiliate click brokers, or analytics vendors that profile user identities. When you paste a link, the upstream connection is made strictly to retrieve public media manifest data from the respective social network.
6. Open source verification
Trust is established through transparency. The complete source code for Spuffi is open and available for independent security auditing. Security researchers, software developers, and privacy advocates can review our API adapters, frontend client code, and network routing configurations to verify that our zero-logs policy is faithfully upheld.
7. User rights and direct inquiries
Because we collect zero personal identifiers, we do not hold personal data archives to inspect, modify, or delete. If you have technical inquiries or security questions regarding our server infrastructure, network encryption, or media processing algorithms, you can review our repository documentation or open a public discussion.