Skip to content
ExamplesWorkflowsServicesApproachSecurityAbout
Resources
Agency AI AuditMap and rank agency AI opportunitiesPrompt LibraryPractical prompts for medcomms teams
Find the friction →

Legal

Cookie Policy

A plain-language account of the browser storage and related technology used on kepler26.com.

Policies

Privacy PolicyTerms of UseCookie PolicyAccessibility

Last updatedAugust 6, 2026

Questionssupport@kepler26.com

1. Current position

Kepler26 uses Google Analytics 4 to understand aggregate website use and improve the site. The Google tag does not load, send measurement requests or set analytics cookies unless you choose “Allow analytics.”

We do not use advertising cookies, enable ad personalization, build cross-site advertising profiles or sell information about visitors. Declining analytics does not affect access to the website.

2. Consent and local storage

The website uses browser local storage, which is similar to a cookie but is stored separately by your browser, to remember two choices.

Keykepler26-industry
PurposeRemember the industry example you selected.
DurationUntil you clear browser site data.
Data received by Kepler26None. The preference stays in your browser.
Keykepler26-analytics-consent
PurposeRemember whether you allowed or declined analytics.
DurationUntil you change the choice or clear browser site data.

3. Google Analytics cookies

If you allow analytics, Google Analytics may set cookies including:

_gaDistinguishes visitors for aggregate measurement; typically expires after up to two years.
_ga_*Maintains session state for the measurement property; typically expires after up to two years.

Cookie names and durations may change as Google updates its service. The measurement property used by this site isG-D8BWVYCGRN.

4. Contact form information

Information typed into the contact form is not stored in a cookie, local storage or a Kepler26 website database. The form prepares an email in your email application, or copies the brief to your clipboard, only when you choose the relevant action.

5. Supabase authentication cookies

When you use secure resource access, Supabase sets strictly necessary authentication cookies. Their names begin withsb- and include the Supabase project reference. They hold signed session tokens and PKCE verification data needed to complete a magic-link sign-in, refresh the session and protect gated routes.

These cookies are used only after you request or complete sign-in and are necessary for the requested authentication service. Blocking or deleting them signs you out or prevents resource access. Their expiry follows the configured Supabase session and token lifetime.

6. Hosting and security technology

Our hosting, content-delivery and security providers may process standard request logs and may use strictly necessary technical mechanisms to deliver and protect the website. These can include IP address, request time, browser details and security signals. Such processing is used for service delivery, abuse prevention and diagnostics rather than advertising.

A provider may change its technical implementation over time. We will update this policy if the website begins using a cookie or similar technology that materially changes visitor choices.

7. Managing your choice and browser storage

Use “Cookie settings” in the website footer to allow or decline Google Analytics at any time. If you withdraw permission, the site disables analytics collection, removes the Google tag from the page and attempts to remove Google Analytics cookies for this domain. The tag will not load on future visits while your choice remains declined.

You can also remove analytics cookies and saved preferences through your browser’s controls for cookies and site data. Blocking local storage may prevent the website from remembering your choices, but the main site content should remain available. Browser controls differ by provider and device; look for settings named “cookies,” “site data,” “privacy” or “storage.”

8. Changes and contact

We may update this policy when website features or service providers change. The date shown on this page identifies the latest version. Questions may be sent to support@kepler26.com.

Kepler26

AI workflow strategy, engineering and secure implementation for medcomms, pharma and life-sciences teams.

ExamplesWorkflowsServicesApproachSecurityAboutContact

Toronto, Canada · Working globally

© 2026 Kepler26 is a division of Mody & Associates, Inc.

Security & PrivacyResponsible AIPrivacy PolicyTerms of UseCookie PolicyAccessibility