Your Choices & Rights
Consent & Cookies
How we use cookies and similar tech, and how you can manage your consent.
Purpose of this page
This page explains how AIM uses cookies and similar technologies, how our consent experience works, and what choices you have. It complements Data & Sources, Purposes & Legal Bases, Retention, and Recipients & Transfers.
Bubble: Clarity first, no surprises.
Your choice at entry (consent experience)
On first visit you choose between:
Accept and continue — we set non-essential trackers (e.g., analytics, advertising) with your consent and you access the service.
Continue without tracking (Subscription) — you access an equivalent experience without non-essential tracking via a paid, tracking-free option.
If you refuse and do not choose the subscription, access is not granted. You can withdraw consent at any time via the persistent Privacy link.
Bubble: Two paths: accept tracking or choose a tracking-free subscription.
What we mean by “cookies and similar technologies”
We use cookies, HTML5 storage (e.g., localStorage), and SDK identifiers to operate AIM and to improve reliability.
Strictly necessary (no consent needed): session continuity, load balancing, security/CSRF, authentication, and basic service protection.
Typical names includeaim_session
,csrf_token
,lb_route
, and Supabase session/auth tokens (cookie or localStorage depending on environment).Non-essential (consent-based): analytics/measurement (Google Analytics), advertising/visibility tags (Google Ads and similar boosters), and optional tools such as a support chat widget (Intercom) when classified as non-essential.
We do not set cookies for precise device location; approximate IP-based signals for performance are handled as described in Purposes & Legal Bases.
Bubble: Necessary runs by default; everything else waits for consent.
Technologies we use at launch
Analytics: Google Analytics runs only with your consent. Provider retention is configured to 14 months.
Advertising & visibility: Google Ads and comparable boosters are consent-based and load only if you accept tracking (or until you switch to the tracking-free subscription).
Support chat: Intercom is optional; you can use the service without it. If enabled on your visit, it loads only with consent. You can always email us at support@aim-ai.tech.
Performance/bug capture (RUM): not used at launch. We may enable it later and will treat it as consent-based if required.
We always offer login alternatives (e.g., Apple, email + password) alongside Google Sign-In. The Google button is provided for convenience; we load only what’s needed for authentication and avoid non-essential tracking unless you consent or actively use the provider.
Bubble: Choice of login, minimal code by default.
How we capture, store, and prove consent
When we ask: on first visit and whenever a material change occurs.
How we record: we store your consent string in a first-party cookie and/or server-side for up to 13 months so we can demonstrate compliance.
How to change your choice: use the Privacy link to withdraw consent or switch to the tracking-free subscription at any time.
Where we show the banner: by default in the EEA/UK/CH and the United States. Outside those regions, we may display it as a global default where required or appropriate.
Frameworks: we do not currently use IAB TCF 2.2; we may adopt it later if it improves transparency.
Bubble: Your choice is logged (13 months) and reversible.
Third-party integrations & AI providers
If you connect Google integrations (e.g., Gmail, Calendar), AIM accesses only what’s strictly necessary to fulfill your request; you can revoke access in your Google account at any time, and we do not reshare that data for unrelated purposes.
For AI outputs, AIM may route your prompts to providers such as OpenAI, Anthropic, Google, DeepSeek, Flux, Perplexity, Meta, Mistral, Moonshot, Qwen, and others. Where supported, we honor and propagate your training opt-out.
Bubble: Optional integrations; revocable by you.
Retention & deletion (cookies context)
Consent proof: kept up to 13 months, then we ask again.
Analytics data (GA4): 14 months at the provider level.
Strictly-necessary cookies/local tokens: retained only as long as needed for session/security. When you sign out or close your account, active use stops and any remaining data follows our Retention policy.
Bubble: Short lifecycles; strict need-to-keep.
Your choices that matter
Pick Accept and continue or Continue without tracking (Subscription) at entry.
Use the Privacy link to withdraw consent at any time.
Revoke third-party integrations directly in your provider account.
Prefer support by email? Write to support@aim-ai.tech.
Bubble: Simple controls, always available.
Contact
Questions about cookies or consent? support@aim-ai.tech
Conclusion
AIM’s Consent & Cookies page makes your choices clear: pick Accept and continue or Continue without tracking (Subscription), change your mind anytime via the Privacy link, and know that only strictly necessary technologies (session, security/CSRF, load balancing, Supabase auth tokens / localStorage) run by default. Non-essential trackers—Google Analytics, Google Ads, and optional Intercom—load only with consent. We record a consent string for 13 months and configure GA4 retention to 14 months. The banner is shown in the EEA/UK/CH and the United States (site accessible globally). We don’t use IAB TCF 2.2 today, but may adopt it later if it improves transparency.
Effective date: {YYYY-MM-DD} • Last updated: {YYYY-MM-DD}
Join our Community Forum
Any other questions? Get in touch