Cookie Policy
Last updated: 11 October 2026
We would like to use Google Ads cookies to measure our adverts, and to tell Google which orders came from them. The site works the same if you reject.
Your choice: Not answered yet
This policy lists what our website stores on your device, and why. We say "cookies" for short. Here the word also covers similar storage in your browser, such as local storage.
1. The short version
- Our site needs a little storage to work. It keeps you signed in, carries your order to payment, remembers your cookie choice and protects our forms.
- We would also like to use Google Ads cookies to measure our adverts, and to tell Google which orders came from them. We do both only if you press Accept.
- The site works the same without the advertising cookies. You lose nothing if you reject them.
- If you make no choice, we treat that as a rejection.
2. What we store
| Name | Set by | Purpose | How long | Consent needed? |
|---|---|---|---|---|
__Host-pp_session | Us | Keeps you signed in to your account. Only our own systems can read it, not the scripts on our pages | 30 days, or until you sign out | No. You cannot sign in without it |
pp_in | Us | Tells our pages that you are signed in, so that they show "Dashboard" and lead you to your account. It holds only the number 1, and nothing about you | 30 days, or until you sign out. We set and remove it with the sign-in cookie | No. It is part of signing in |
pp_consent | Us | Remembers whether you accepted or rejected advertising cookies | 6 months | No. It records your choice |
primed-flow in session storage | Us | Keeps your order, your tick and your place while you sign up and pay, and a key that keeps one order from being paid twice. Until you enter the code, it also keeps your name, your email address, your choice about marketing emails and any referral code, never your password. After you accept advertising cookies, it also notes the orders this tab has shown as paid, so that Google counts each payment once | Until you close the tab. Most of it goes sooner, once it has done its job | No. It does what you asked |
primed-ref, primed-draft and primed-flash in session storage | Us | Keep the referral code you arrived with, what you typed into the sign-up form, and a one-time message for the next screen | Until you finish, or until you close the tab | No. It does what you asked |
| None. Turnstile gives each form a one-time token | Cloudflare | Checks that a person, not a script, is using our forms. Cloudflare receives your IP address and browser details | One use | No. It keeps the forms secure |
__stripe_mid, __stripe_sid and m | Stripe, on its own payment pages | Help Stripe detect fraud when you pay | 1 year, 30 minutes and 2 years | No. Stripe sets them on its site, not ours, and treats them as essential |
_gcl_au and other cookies that start with _gcl_, such as _gcl_aw | Google, through the Google Ads tag on our site | Record that you came from one of our adverts, so that Google can count the orders that follow | 90 days | Yes |
_gcl_ls in local storage | Google, through the same tag | The same purpose | Until you reject or clear your browser | Yes |
pp_attr in local storage | Us | Keeps the code of the Google advert you clicked, its campaign tags and the page you arrived on, so that we can count which adverts lead to orders | 90 days | Yes |
pp_click | Us | Keeps the same advert code as pp_attr, in a cookie that only our own systems can read, so that an order you place later still counts if your browser clears pp_attr | 90 days | Yes |
Google's own cookies, for example IDE, test_cookie and Conversion | Google, on its own domains doubleclick.net and googleadservices.com | Google's side of advert measurement | 13 months, 15 minutes and 90 days | Yes |
The law lets us store the "No" items without asking, because the site needs them to work or to stay secure. We list them so that you know about them.
Stripe's payment pages may set other cookies. Stripe lists them in its cookie settings.
3. Advertising cookies and Google
- If you press Accept, the Google Ads tag loads. Before that, it does not load at all.
- Google then stores the cookies above. It receives the cookie identifiers, the advert click you came from, the pages you visit, your IP address and your browser details. It also learns when you place an order, and the order's value.
- If you press Accept, our own site also keeps the code of the advert you clicked, with its campaign tags and the page you arrived on. If you then create an account or place an order, we keep them with it. When you pay, we send Google that code with the time and value of your order, so that Google can count the orders that come from our adverts.
- With the order we also send your email address, in a scrambled form called a hash. Google uses it for us, to match the order to an advert click. If your browser removed the advert code, we send the advert's campaign number, the time you arrived and your browser details instead.
- We use the results to see which adverts lead to orders. We see totals, not a report about you.
- We do not use these cookies to show you personalised adverts.
- Google also uses the data for its own purposes, under its own privacy policy. See how Google uses information from sites that use its services.
4. If you reject
- We store nothing from the "Yes" rows. The Google Ads tag does not load.
- Everything on the site still works: prices, your account, payment and your dashboard.
- We remember your choice, so that we do not ask you on every page.
5. How to change your choice
- Use the Reject and Accept buttons on this page. The "Cookies" link at the foot of our public pages brings you here. When you are signed in, use the "Cookies" link under Legal on the Account page.
- If you reject after accepting, we stop the tag, delete the
_gcl_items,pp_attrandpp_clickfrom your browser, and delete the advert code we kept with your account. We send Google no more of your orders. Orders we already sent to Google stay with Google under its own terms. - Cookies on Google's own domains stay until they expire, or until you delete them in your browser settings.
- We ask you again after 6 months.
- Your browser can also block or delete cookies. If you block the sign-in cookie, you cannot sign in.
6. Other sites
Stripe's payment pages, Discord, Trustpilot and our help documents on GitBook are separate sites. They set their own cookies under their own policies.
7. Questions
Email hello@primedproxies.com or use our contact form. Our Privacy Policy explains how we use personal data.
Questions? Write to us.