What RedPuller processes and stores
Understand how RedPuller handles submitted public identifiers, requested streams, browser preferences, and operational metadata.
Quick answer
RedPuller processes the public URL, profile name, or media ID you submit to resolve metadata and prepare a requested stream; media bodies are not written to permanent server storage, while browser state and operational metadata have separate boundaries.
Steps
- Submit only the public RedGifs identifier needed for the request.
- Review the privacy and preview controls before displaying or downloading a result.
- Clear browser storage or stop the local queue when you no longer need the saved preference or job state.
Limits to keep in mind
- Operational logs and metrics may include status, timing, byte counts, and rate-limit outcomes; the workflow does not promise that no network or operational records exist.
- Browser downloads, local queue metadata, and preferences can remain on your device until you clear them; provider visibility and third-party URLs can also change.
Common questions
Do I need a RedPuller account?
No account is part of the current public-media workflow; RedPuller resolves the identifier submitted for the request.
Does RedPuller keep the downloaded file on its server?
The server streams the requested body and does not write it to permanent media storage. Your browser still controls its own download and local history.