Apollo Cookie Policy

Last updated: 7 August 2026

This Cookie Policy explains how APOLLOUI LTD (Apollo, we, us, our) uses cookies and similar technologies on our website and application in accordance with applicable UK law, including rules on cookies and similar technologies under the Privacy and Electronic Communications Regulations (PECR) and UK data protection law.

This policy should be read with our Privacy Policy. It does not mean Apollo is “GDPR compliant” or “PECR compliant” as a marketing badge.

Related documents:

• Privacy Policy — how we handle personal data
• Terms and Conditions — contract for use of Apollo
• Data Processing Agreement — tenant processor processing (cross-reference only)
• Disclaimer — platform scope and limits

1. About this Cookie Policy

1.1 This Cookie Policy describes:

• what cookies and similar technologies are;
• how Apollo uses them;
• the choices you have on our public marketing website;
• cookies and storage used when you sign in and use the workspace or client portal.

1.2 Scope. The cookie banner and Cookie settings described in sections 10–11 apply to our public marketing pages and the signed-out home page (/). They do not currently appear on workspace, client portal, login, signup, or invite routes.

1.3 Third-party sites. If you follow a link to Stripe, Google (for sign-in), or another third party, that site’s own cookie and privacy policies apply there — not this policy.

1.4 We may update this Cookie Policy from time to time. The “Last updated” date at the top shows when it was last revised.

2. Who we are

Apollo is operated by:

APOLLOUI LTD
A private limited company registered in England and Wales
Company number: 17093007
Registered office: 38 Mercer Avenue, Ebbsfleet Valley, Swanscombe, England, DA10 1BR

General contact: hello@apolloui.co.uk
Privacy contact: hello@apolloui.co.uk

3. What cookies and similar technologies are

3.1 Cookies are small text files placed on your device when you visit a website. They are widely used to make sites work, remember choices, or understand how a site is used.

3.2 Similar technologies include:

• localStorage and sessionStorage in your browser — data stored locally on your device;
• scripts loaded from Apollo or from third-party domains (for example analytics or advertising tools);
• authentication tokens held by the browser or application libraries.

3.3 Cookies may be first-party (set by Apollo) or third-party (set by a provider such as Google, Microsoft, or Meta).

3.4 Cookies may be session cookies (deleted when you close your browser) or persistent cookies (remain for a set period or until you delete them).

4. How Apollo uses cookies

4.1 We use cookies and similar technologies to:

• operate and secure the Apollo website and application;
• remember your sign-in session;
• remember limited first-party display or application choices (for example light/dark theme after you change it);
• ask for your consent before loading optional Analytics or optional Marketing technologies on our public marketing website;
• measure campaigns where you have granted Marketing consent;
• help protect early-access forms against automated abuse.

4.2 We do not currently use a third-party cookie consent management platform (CMP). Consent is handled by Apollo’s own banner and Cookie settings on marketing pages.

4.3 Joining early access by email is separate from Marketing cookie consent. Submitting Register Interest (or the early-access popup form) is a deliberate action and does not require you to accept Analytics or Marketing cookies. See our Privacy Policy.

5. Cookie categories we use

We group cookies and similar technologies into the categories below. This matches the choices in our marketing cookie banner.

Rejecting Analytics and Marketing does not stop you using our website, and it does not stop you joining early access by email.

There is no separate “Preferences” category in the marketing cookie banner.

6. Necessary cookies and storage

6.1 Necessary cookies and storage are required for essential website operation and security. They cannot be switched off through Apollo’s Cookie settings.

6.2 Examples include:

• the __session cookie when you sign in (see section 13);
• hosting and security processing by our infrastructure providers (which may involve technical cookies or logs at the network edge);
• Cloudflare Turnstile on Register Interest and the early-access popup, used to reduce automated abuse before optional Analytics or Marketing consent applies;
• Sentry error and performance monitoring on eligible public routes (configured without Session Replay, Logs, profiling, or user-feedback widgets). Sentry may still show coarse geography derived from network context even when Apollo disables storing full IP addresses — we do not claim that no location information can ever be derived.

6.3 Necessary cookies may be set when you use login, the workspace, or the client portal, even though the marketing cookie banner is not shown on those routes.

7. Analytics cookies and similar technologies

7.1 Analytics technologies help Apollo understand how people use signed-out public pages so we can improve the website. They are optional and off by default.

7.2 When you grant Analytics consent on our marketing website, Apollo may load:

• Google Analytics 4 (GA4) via Google Tag Manager (GTM) on eligible public paths;
• Microsoft Clarity via GTM on eligible public paths;
• Vercel Speed Insights (direct integration) for Core Web Vitals / real-user performance measurement.

7.3 GTM itself is a tag delivery shell. It loads only when Analytics or Marketing consent is granted (and Apollo’s public tracking gate allows it). Child tags still respect their own consent categories.

7.4 After a successful early-access registration that Apollo treats as a new registration, Apollo may also send a privacy-limited GA4 Measurement Protocol generate_lead event from our servers when Analytics consent and a browser GA client identifier are available. That server event does not send your email address, name, or IP address as conversion identifiers.

7.5 Cookie names commonly associated with these tools include _ga / _ga_* (Google Analytics) and _clck / _clsk (Microsoft Clarity). Durations follow the relevant provider documentation and account settings (Google’s defaults for Analytics cookies are typically up to about 2 years, subject to browser limits and property configuration). Clarity cookie lifetimes should be read from Microsoft’s Clarity documentation rather than invented here.

8. Marketing cookies and Meta

8.1 Marketing technologies support campaign measurement on public pages. They are optional and off by default.

8.2 When you grant Marketing consent on our marketing website, Apollo may load the Meta Pixel via GTM on eligible public paths. Meta may set browser identifiers such as _fbp and, where applicable, _fbc (Meta documents these identifiers as lasting about 90 days).

8.3 After a successful early-access registration that Apollo treats as a new registration, Apollo may send a privacy-limited Meta Conversions API (CAPI) Lead event from our servers only when:

• Marketing consent is present; and
• at least one valid consent-derived Meta attribution identifier (_fbp and/or _fbc) is available, together with the request user-agent.

If valid Meta attribution is missing or malformed, Apollo skips Meta CAPI delivery (without fabricating identifiers). Apollo does not introduce email hashing, IP forwarding, name/phone advanced matching, or external_id for that Lead event. Meta’s automatic advanced matching and automatic events settings for the Apollo Website dataset are off in Apollo’s account configuration.

8.4 Marketing cookies are not the same as agreeing to receive emails. Early-access signup has its own consent path.

8.5 Mailchimp browser popup scripts (chimpstatic.com / #mcjs) are not used as Apollo’s marketing-cookie tool on public marketing pages. Early-access registration is handled by Apollo’s own forms and a server-only Mailchimp Marketing API call — see the Privacy Policy.

9. First-party display and signed-in application storage

9.1 These items are not separate optional categories in the marketing cookie banner:

• theme (localStorage) — light / dark / system display mode (next-themes default key);
• apollo_portal_context — remembers last selected client portal context after sign-in (HttpOnly cookie);
• apollo_connection_lens — remembers a connection filter preference after sign-in (HttpOnly cookie).

9.2 Turning off Analytics or Marketing in Cookie settings does not remove theme localStorage or signed-in application preference cookies. Those support display or signed-in use cases and are re-validated by the server where access control applies.

10. Cookie consent on Apollo marketing pages

10.1 On public marketing pages (for example /, /features, /pricing, /faq, /about, /contact, /register-interest) and the signed-out home page, we show a cookie banner on your first visit until you make a choice. Visitors with an older consent record may be asked again so choices match the current Analytics / Marketing model.

10.2 The banner explains that Necessary cookies keep the website working securely and that Analytics and Marketing are optional and off by default. It offers three equally visible actions:

• Accept all — enables Analytics and Marketing;
• Reject non-essential — keeps Analytics and Marketing off;
• Choose settings — opens Cookie settings with category controls.

10.3 Reject is as easy as Accept — both are shown with equal prominence.

10.4 Your choice is stored in browser localStorage under key apollo_cookie_consent_v2 (JSON: version, analytics, marketing, updatedAt). Necessary is always on and is not stored as a toggleable field.

10.5 No third-party CMP is used. Implementation is Apollo’s own banner and Cookie settings.

10.6 The banner does not appear on /login, /signup, /invite/accept, workspace routes, or the client portal. Necessary and application cookies may still apply there when you use those parts of Apollo.

11. Changing your cookie preferences

11.1 On marketing pages, click Cookie settings in the website footer to reopen settings and change your choices at any time.

11.2 In Cookie settings, Necessary is Always on. You can adjust Analytics and Marketing, then Save choices. You can also Accept all or Reject non-essential.

11.3 Withdraw optional consent. Choose Reject non-essential, or turn off Analytics and/or Marketing and save. We will stop loading the corresponding optional technologies on future visits to our marketing pages (subject to Apollo’s tracking enablement gates). We may not be able to delete cookies already placed on your device by third parties; you can clear site data in your browser settings.

11.4 Clear all choices. You can clear apollo_cookie_consent_v2 (and other site data) via your browser settings. The banner will appear again on your next visit to marketing pages.

11.5 For broader data protection rights, see our Privacy Policy and contact hello@apolloui.co.uk.

12. Third-party websites

12.1 Stripe. If you subscribe or manage billing via Stripe-hosted pages, Stripe’s policies apply there.

12.2 Google sign-in. If you choose Google to authenticate, Google’s policies apply to that sign-in flow.

12.3 We are not responsible for third-party sites’ cookies or privacy practices. We encourage you to read their notices.

13. Detailed cookie and storage table

The table below lists technologies used in Apollo’s website and application. Provider cookie names and lifetimes can change; where a duration is marked as provider-documented, check the linked provider materials for the current figure.

Not used on Apollo marketing pages as the Marketing cookie tool: Mailchimp chimpstatic.com / #mcjs connected-site popup loader.

Not used in Apollo’s Meta CAPI Lead path: email hashing, IP forwarding, name/phone advanced matching, or fabricated _fbp / _fbc.

14. Updates to this Cookie Policy

We may update this Cookie Policy to reflect changes in law, our services, or our use of cookies. We will post the updated version with a revised Last updated date. Where changes are material, we may provide additional notice (for example on our website or by updating the cookie banner text).

15. Contact us

For questions about this Cookie Policy or cookies on Apollo’s website:

Email: hello@apolloui.co.uk
Post: APOLLOUI LTD, 38 Mercer Avenue, Ebbsfleet Valley, Swanscombe, England, DA10 1BR

For broader privacy questions, see our Privacy Policy.

Related documents: Terms and Conditions · Privacy Policy · Data Processing Agreement · Disclaimer