Cookie Policy
Last updated: 16 August 2026
This Cookie Policy explains how RiseGuide uses cookies and similar technologies on this website, what each one does, how long it lasts, and how you can control it.
It should be read together with our Privacy Policy, which describes how we handle personal data more generally, and our Terms of Use.
Capitalised terms not defined here have the meaning given in the Terms of Use.
1. What these technologies are
A cookie is a small text file a website asks your browser to store on your device and send back on later visits. We also use two related technologies that work the same way in practice, and which this Policy covers on the same footing:
- Local storage — a larger, longer-lived store in your browser, which unlike a cookie is not automatically sent to our servers.
- Pixels (also called tags or beacons) — a small piece of code that loads when you view a page, allowing us or an advertising partner to record that the view happened.
Where the law refers to information "stored on your terminal equipment", it covers all three. So does this Policy.
2. Why we use them
We use these technologies to:
- keep your place in the assessment, so refreshing or coming back does not lose your answers;
- remember which advertisement or link brought you here, so we can tell which of our campaigns work;
- keep you in a single version of the site if we are testing two versions;
- measure how many people reach each step, so we can see where the experience is failing;
- report conversions to the advertising platforms we buy traffic from.
We do not use cookies to build profiles for sale, and we do not sell the data in them.
3. What we set
3.1 Strictly necessary
These are required for the site to function. They cannot be switched off through our site, and no consent is sought for them.
| Name | Type | Purpose | Retention |
|---|---|---|---|
asc_attr |
First-party cookie | Holds a randomly generated session identifier, which version of the site you were shown, the page you landed on, the referring address, the time of your first visit, and the campaign and click identifiers from the address you arrived on (for example utm_source, fbclid, ttclid, gclid). It is written once, on your first request, and read on every page after that. |
90 days |
ascend.quiz.v1 |
First-party local storage | Holds your assessment answers, which step you are on, your computed result, the email address you give us at the results gate, and when the introductory offer window opened for you. This is what allows a refresh mid-assessment to resume where you left off, and what prevents the countdown restarting. | Until you clear it (see section 6) |
The session identifier in asc_attr is generated by us and is not derived from your name, email address, device identifier, or any other identifier you did not give us.
Note that asc_attr is readable by scripts on our own pages. That is deliberate: the conversion-measurement code needs the session identifier to produce a matching event reference on the browser side and the server side, so a single purchase is not counted twice.
3.2 Analytics
| Name | Type | Purpose | Retention |
|---|---|---|---|
| — | First-party, server-side | We record each step transition — session identifier, step, answer, time spent on the step, and site version — against our own systems. This is how we find the questions people abandon on. No additional identifier is stored on your device for this beyond asc_attr above. |
See Privacy Policy |
3.3 Advertising and conversion measurement
We buy traffic from advertising platforms, and we report back to them which visits led to a purchase so that our advertising is charged and targeted correctly. Where these are enabled, they set the following:
| Name | Set by | Purpose | Retention |
|---|---|---|---|
_fbp, _fbc |
Meta Platforms (Meta Pixel) | Identifies your browser to Meta so a purchase can be attributed to the advertisement you clicked, and so Meta can build audiences for our campaigns. _fbc stores the click identifier from the advertisement itself. |
Up to 90 days |
_ttp |
TikTok | The same function for advertising bought on TikTok. | Up to 13 months |
These are the technologies the consent line on our first screen refers to. They are advertising technologies, not necessary ones: declining them does not prevent you using the site or buying a plan.
We also send the same conversion events to these platforms directly from our servers, matched to the browser event by a shared reference so that one purchase is reported once rather than twice. Server-side reporting is not avoided by blocking cookies in your browser; it is governed by your consent choice and by our Privacy Policy, and you can object to it as described in section 6.
3.4 Payment
Payment is taken on a page hosted by our payment provider, CheckoutChamp, on their own domain. That page sets its own cookies under its own policy, including cookies used for fraud prevention. We do not control them, and they are not covered by this Policy. Full card numbers are never stored by us.
4. Consent
Where consent is required for us to set non-essential technologies — which includes visitors in the United Kingdom, the European Economic Area, Switzerland, and any other jurisdiction imposing an equivalent requirement — we do not set the advertising technologies in section 3.3 until that consent is given, and we do not treat continuing to browse as consent.
The strictly necessary items in section 3.1 are set without consent, because the site cannot deliver the service you asked for without them.
You can change or withdraw your consent at any time, with effect for the future, using the controls in section 6. Withdrawing consent does not affect anything done before you withdrew it.
5. Transfers and recipients
The advertising partners named in section 3.3 are independent controllers of the data their own technologies collect, and process it under their own policies:
- Meta Platforms — https://www.facebook.com/policy/cookies/
- TikTok — https://www.tiktok.com/legal/cookie-policy
Where these transfers involve moving personal data outside your country, the safeguards described in our Privacy Policy apply.
6. How to control this
Advertising technologies on this site. Use the cookie preferences control available from any page footer to give or withdraw your consent.
All cookies, in your browser. Every major browser lets you block or delete cookies. The relevant settings are usually under Privacy or Security:
- Chrome — Settings → Privacy and security → Third-party cookies
- Safari — Settings → Privacy
- Firefox — Settings → Privacy & Security
- Edge — Settings → Cookies and site permissions
The local storage entry. Clearing site data for this site in your browser removes ascend.quiz.v1. Doing so mid-assessment will lose your answers.
Mobile advertising identifiers. Your device settings control these separately — "Allow Apps to Request to Track" on iOS, "Ads" under Privacy on Android.
Blocking strictly necessary items will stop parts of the site working: your answers will not survive a refresh, and we will not be able to tell which advertisement brought you here.
7. Changes
We may update this Policy when the technologies we use change. Material changes will be reflected in the date below, and where the change requires it we will ask for your consent again.
8. Contact
Questions about this Policy, or requests relating to the data these technologies collect, can be sent to the controller identified in our Privacy Policy: Celeb Innovations Limited, Georgiou A, 83, Shop 17, Potamos Germasogeias, 4047, Limassol, Cyprus.