- P-7.1
The register
- Processor cookies. Set by Whop inside its own card frame, to carry the payment through and to screen it; Whop’s policy governs them; no card clears without them.
- Vector cookie. Written only when a personal payment vector, handed to you by the person holding it, is opened in this browser. Contents: an opaque reference to that holder. Life: ninety days. Nothing about you inside it.
- Console cookie. Written when the desk operator signs in to the back office. Signed, HttpOnly, eight hours. A buyer never receives one.
- P-7.2
Why nothing asks your permission
Consent is owed for cookies that watch. Three entries, each one load-bearing for a thing you asked the site to do, and none of them reading anything back about you, is not a case a banner improves. So there is no banner, no overlay and no preference centre to wade through.
- P-7.3
Refusing them
Any browser can block or wipe this domain’s cookies, at any point, without telling the desk. Every page here reads the same afterwards. The card frame is the exception: refuse the processor’s and it will not complete a payment.
- P-7.4
Not present
Nothing for advertising. No measurement pixels, no tag manager, no session recorder, no outside analytics suite, no retargeting list, no profile stitched across sites. The register above is the whole of it.
- P-7.5
Where to ask
[email protected] settles anything this page leaves open. For the wider question of what the desk holds about a buyer, read P-6 Data Protocol.
- P-7.6
Footnote: what a cookie is
A short value a site parks in your browser and reads back on a later request. That much is neutral. What makes the word notorious elsewhere is the second use, where the value is a handle on a person and the reading back is done by companies the reader never visited.
questions on this document · [email protected]