Cookies & Similar Technologies
We use cookies to make GoldenPrediction work smoothly, keep you secure, and improve the product. This page explains what we set, why, and how to control your choices.
Effective: Sep 28, 2025
What are cookies?
Cookies are small text files stored on your device by your browser. They help remember preferences, authenticate you, and collect anonymous analytics. Similar technologies include localStorage, sessionStorage, and fingerprinting tokens (we avoid invasive fingerprinting).
Cookie categories & examples
Below are categories we use and example cookie names. Your site may show additional vendor cookies (replace with your real names).
| Category | Purpose | Typical cookie names & retention |
|---|---|---|
| Essential / Strictly necessary | Required for authentication, security, and core site functions (sign-in, CSRF). | sessionid — session cookie (session)csrftoken — CSRF protection (90 days) |
| Security | Detect and prevent fraud, abuse and protect your account. | __s_security — fraud token (30 days)auth_token — encrypted token (rotates) |
| Performance & Analytics | Understand product usage to improve reliability and performance. | _ga, _gid (Google Analytics) — 2 years / 24 hoursamplitude_id — analytics (persistent) |
| Functionality / Preferences | Remember UI choices and user preferences (language, theme). | gp_theme — theme preference (1 year)me_tab_view — last tab (90 days) |
| Marketing / Advertising | Deliver and measure ads, track conversions (used only with consent and limited for logged-out ad features). | _fbp (Facebook Pixel) — 3 monthsads_tracking — vendor-specific |
Third-party cookies & vendors
We use some third-party providers to deliver services. These providers may set cookies when you use our site. Typical examples (replace with your stack):
- Payments: Paystack, Stripe (payment processors — we only receive metadata).
- Emails: SendGrid / Postmark (email delivery / tracking for sent transactional emails).
- Analytics & monitoring: Google Analytics / Amplitude / Sentry / Datadog.
- Embeds: Map or social widgets may set cookies (if you use map embeds or social previews).
You can manage third-party cookies by revoking consent here or via your browser settings.
How we use cookies (short)
- Authenticate you and keep your session secure.
- Persist preferences and UI choices so the product feels personal.
- Protect against fraud and abuse (security tokens, rate limiting).
- Collect aggregate analytics to improve site performance and product features.
- With consent, enable marketing & measurement features.
Legal basis & consent
Essential cookies are necessary to provide the service (performance of contract). For performance, analytics, and marketing cookies we rely on your consent where required by law. You can accept or decline non-essential cookies below.
Retention & deletion
Cookie retention depends on the cookie type (session vs persistent). Example retention ranges are in the table above. You can delete cookies via your browser at any time (see section below).
How to delete or block cookies
You can control cookies in your browser settings. Below are pointers — see your browser help for exact steps:
- Chrome: Settings → Privacy and security → Cookies and other site data → See all cookies and site data.
- Firefox: Options → Privacy & Security → Cookies and Site Data → Manage Data.
- Safari (macOS): Preferences → Privacy → Manage Website Data.
- Mobile browsers: Check browser settings; many show site data per site.
Note: blocking essential cookies may break sign-in or core features.
More technical notes (for devs)
If integrating: set a single cookie (e.g., gp_cookies_pref) with JSON like {"analytics":true,"marketing":false,"func":true}. Read that cookie server-side or on page load to gate analytics vendor initialization. Example:
{
"analytics": true,
"marketing": false,
"func": true
}
Your analytics loader should check the flag before loading vendor scripts. For GDPR regions, delay vendor JS until consent is given.