1. Essential storage and optional analytics
Interactive Calendar uses browser storage that is necessary for sign-in, security, preferences and the installable PWA. On our public-facing informational pages, we also offer optional Google Analytics to understand which pages are useful and improve them. Google Analytics is not loaded until you choose Accept analytics. The authenticated calendar app itself is not measured with Google Analytics.
2. Session cookie
In production, Interactive Calendar uses the cookie __Host-IC_SESSION.
- Purpose: maintain your authenticated session, secure Google OAuth state and protect state-changing requests against CSRF.
- Type: strictly necessary first-party session cookie.
- Duration: browser session; it is not configured with a persistent expiry date.
- Security: Secure, HTTP-only, SameSite=Lax, host-only, path
/.
Public legal pages do not need this session cookie. A new app session is created when required for sign-in or authenticated application functionality.
3. Cookie-consent preference
Your choice is stored locally in your browser under interactive_calendar_cookie_consent_v2. It records whether you selected essential storage only or accepted analytics, together with the time of that choice. The preference is treated as expired after approximately 180 days so that we can ask again when appropriate.
We also use ic-language to remember your language and ic-sidebar-collapsed to remember whether you collapsed the sidebar. These values do not contain calendar event content.
4. PWA cache storage
If your browser supports Progressive Web Apps, the service worker may cache static files such as CSS, JavaScript, logos and the offline shell. Interactive Calendar does not intentionally cache personal calendar events or authenticated API responses for offline use.
5. Google Analytics
If you consent, Interactive Calendar loads Google Analytics using measurement ID G-EY4NSLWFBE on public-facing informational pages only. Google Analytics may process page-view, interaction, browser/device and approximate geographic information and may set cookies such as _ga and _ga_*. These cookies are commonly configured for up to two years and may be refreshed while analytics consent remains active.
We configure analytics without Google Signals and without ad-personalization signals. We do not intentionally send Google Calendar event content, OAuth codes or tokens, payment-card details, or other calendar content to Google Analytics.
6. Google and Stripe
When you choose to sign in with Google or manage payment through Stripe, your browser is redirected to domains operated by those providers. Google and Stripe may use their own cookies or browser storage under their respective policies. Those provider-controlled cookies are separate from the optional Google Analytics cookies described above.
7. Managing or withdrawing consent
You can change your analytics choice at any time. Choosing essential storage only stops Analytics from loading on future public-page views and the site attempts to remove Google Analytics cookies that it can access on this domain. You can also clear cookies, local storage and cached site data from your browser settings.
8. Changes
If we change the analytics provider, add advertising technology or introduce other non-essential storage, we will update this policy and the consent mechanism before using it where consent is required.
9. Contact
Interactive Net Solutions
interactivenet.app
[email protected]