Legal / cookies

Cookie Policy

Maitro uses strictly necessary session/security cookies on authenticated surfaces and cookieless aggregate analytics on the public site. No advertising or profiling cookies are intended.

Strictly necessaryNo advertising cookiesCookieless analyticsNo retargetingBrowser controls

Read privacy policy Contact privacy

Claim discipline

Premium does not mean reckless.

This page separates current controls, roadmap targets, illustrative tools, gated economics, and agreement-controlled terms so senior leaders can evaluate Maitro without mistaking posture for guarantee.

Necessary

Auth/session

Authenticated surfaces may use Clerk session cookies needed to keep users signed in.

Aggregate

Cookieless analytics

Public pages use first-party pageview events and configured cookieless analytics.

Policy

No ad cookies

The public policy states no ad networks, retargeting pixels, or profiling cookies.

Version

Policy version

30 April 2026 / Version 1.0 / presentation refreshed 26 May 2026

Presentation has been upgraded for readability. Legal meaning should remain subject to founder/legal review before being treated as final advice.

1. Cookies we use

Name	Provider	Purpose	Duration	Category	Notes
__session	Clerk	Maintains authenticated session	Session / provider-controlled	Strictly necessary	Only where authentication is used.
__client_uat	Clerk	Session freshness and auth security	Provider-controlled	Strictly necessary	Authenticated surfaces.
CSRF/security token	Maitro / framework	Protects state-changing forms where applicable	Session-scoped	Strictly necessary	Implementation-dependent.
maitro_privacy_notice_dismissed	Maitro localStorage	Remembers privacy notice dismissal	Until browser storage is cleared	Preference / notice	Local storage, not a cookie.

2. Analytics transparency

Maitro sends first-party pageview events to /api/analytics and may load configured cookieless analytics such as a Talpro-operated Umami endpoint. Optional Google Analytics or Microsoft Clarity scripts load only if deployment environment IDs are configured; policy and notice should be updated before any such deployment is used in production.

3. What we do not use

Maitro does not intend to set Meta Pixel, Google Ads retargeting, Hotjar, FullStory, ad-network, cross-site profiling, or social retargeting cookies on the public site.

4. Browser controls and changes

You can manage cookies in your browser. Disabling strictly necessary cookies may prevent sign-in or authenticated services from working. If Maitro adds new cookie categories, this policy should be updated before launch use.

FAQ

Cookie Policy FAQ

Does Maitro set advertising cookies?

The public site states no advertising cookies, retargeting pixels, or profiling cookies.

Does Maitro use analytics?

Yes. The site uses first-party pageview events and may use configured cookieless analytics. Optional GA or Clarity scripts require public IDs and policy updates before launch use.

Related policies

Route-safe next steps for review, application, trust, and policy context.

PrivacyData categories, rights, retention, vendors.TermsBase terms and agreement hierarchy.CookiesStrictly necessary cookies and analytics.RefundsCancellation, duplicate charges, and refund review.DeliveryDigital delivery and access timelines.Royalty templateCommercial structure, not public economics.

Policy route

Need this reviewed for your situation?

Use the correct Maitro lane for billing, privacy, legal, or security questions. Do not send confidential idea/IP content through open email.

Read privacy policy Contact privacy