QuickClip
Turnstile Privacy Addendum
This addendum forms part of the QuickClip Privacy Policy and explains the processing associated with Cloudflare Turnstile on parsing forms.
Why we use Turnstile
QuickClip uses Cloudflare Turnstile to identify and block suspected automated abuse, protect the parsing endpoint, and maintain service security. QuickClip processes a parsing request only after Turnstile verification succeeds.
Information processed by Turnstile
Cloudflare states that Turnstile may process client-side signals such as the client IP address, TLS fingerprint, User-Agent, sitekey, and associated origin. Cloudflare uses these signals to provide bot detection and blocking and to improve its detection capabilities.
Verification flow
The Turnstile widget runs in your browser and generates a single-use verification token. QuickClip's Worker sends that token and necessary request network information to Cloudflare's Siteverify endpoint and continues parsing only after a successful response. The Turnstile secret key is never sent to the browser.
Cloudflare terms
Cloudflare's processing of Turnstile signals is governed by its Privacy Policy and Turnstile Privacy Addendum. Cloudflare may update those documents, so its official website controls the current version.
Questions and privacy requests
Contact QuickClip if you have questions about how this site uses Turnstile. For Cloudflare's own processing or related rights requests, use the contact information in Cloudflare's Turnstile Privacy Addendum.