Cookie Notice + Data Practices

Essential cookies may support security, routing, session continuity, authentication, and core website functionality. These are generally required for the website and authenticated tools to function correctly.

Authenticated dashboard and client portal experiences may use Supabase-related session cookies or similar authentication mechanisms. These should be handled as sensitive session material and should not be shared, logged, or committed.

Depending on implementation details, some authenticated experiences may also rely on session or local browser storage for continuity, preferences, or workflow state. Implementation details may vary by production configuration and authenticated workflow needs.

Marketior may use analytics events, internal operational analytics, request correlation IDs, error monitoring, and operational logs to understand reliability, conversion flow, support needs, and platform health. These systems should avoid secrets, raw prompts, private notes, token material, and unnecessary PII-heavy payloads.

Where configured, providers such as Vercel, Sentry, Supabase, or Upstash may process limited technical metadata needed to operate hosting, observability, authentication, or rate limiting functions.

Future advertising, retargeting, or marketing attribution cookies may be enabled only with appropriate consent, disclosure, and provider configuration.

Visitors can usually control cookies through browser settings. Blocking some cookies may affect authentication, security, or platform functionality. User-choice controls and consent tooling may vary by region, browser, and production configuration.

Provider-specific cookie, storage, and tracking behavior may depend on the final configuration of Vercel, Supabase, Sanity if used, Resend, Upstash, Sentry or another observability provider, OpenAI-compatible AI providers for internal workflows if enabled, LinkedIn connection or publishing features if enabled, and future analytics or marketing tools.