What FFast measures to keep the route responsive
FFast records bounded operational facts such as the public source, resolver stage, coarse duration, status, selected output, and transferred byte count. Privacy-protected visitor signals enforce fair-use limits and diagnose slow paths without becoming public analytics profiles. Temporary media expires, support messages remain private, and browser preferences are controlled from your device.
Last revised 26 August 2026. FFast records only what the workflow needs, and this page identifies those records and their purpose.
1. What this policy covers
FFast covers direct-link checks, temporary delivery, the source guide and submitted support requests. It does not extend to the accounts or policies of upstream platforms.
2. Information processed
- Submitted links: the public URL is sent to the resolver so it can detect the source and return formats.
- Operational data: request identifiers, coarse timing, status, byte totals and privacy-protected visitor or IP hashes help prevent abuse and diagnose failures.
- Contact messages: name, email, subject, optional public URL and message are stored in the private control center.
- Continuation links: an opaque token maps to the cleaned public media URL in the control database. The URL is not embedded in the token or QR code.
- Device-only preferences: recent-link history, format preference and private-mode choices stay in browser storage unless you clear them.
- Local media tools: a file selected on the local-tools page is read into temporary WebAssembly memory in your browser and is not uploaded to FFast. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
FFast reads a small operational trail to complete the requested handoff, apply traffic limits and find slow or failed stages. Support and anti-abuse work use the same protected evidence.
4. Temporary media and retention
FFast releases temporary media from storage after delivery expires. It retains failure evidence only as long as operations require and keeps contact messages until answered. Support can also invalidate a persistent continuation record.
5. Service providers and upstream platforms
FFast contacts the source and its configured delivery stack to complete a handoff. Enabled ad or contribution services are distinct providers, while network secrets and private routes remain hidden.
6. Cookies and local storage
FFast places a first-party cookie for rate and abuse controls. The browser may retain preferences or recent addresses for convenience, with Private Mode and clear-site-data controls available.
7. Your choices
FFast processes only what you choose to send. A private session limits local history, browser controls remove preferences and support can review access, correction or deletion matters. Open the contact form.
8. Children, security and changes
FFast is not directed at anyone under 13. Sensible technical measures protect the workflow, though internet risk remains, and significant notice changes will be timestamped here.