Loading Marketior
Legal / Data Practices
A launch-safe data practices foundation covering essential cookies, authentication, analytics, observability, and future marketing technologies.
Last updated: [Insert date before launch]
Essential cookies may support security, routing, session continuity, authentication, and core website functionality. These are generally required for the website and Marketior OS 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.
Marketior may use analytics events, request correlation IDs, error monitoring, and operational logs to understand reliability, conversion flow, and platform health. These systems should avoid secrets, raw prompts, private notes, token material, and unnecessary PII-heavy payloads.
Future advertising, retargeting, or marketing attribution cookies should not be enabled until consent, disclosure, regional requirements, and provider lists are reviewed and approved.
Visitors can usually control cookies through browser settings. Blocking some cookies may affect authentication, security, or platform functionality. Final user-choice language and consent tooling must be reviewed before launch.
Provider-specific cookie and tracking behavior may depend on the final configuration of Vercel, Supabase, Sanity, Resend, Upstash, Sentry or another observability provider, and future analytics or marketing tools.