Loading Marketior
Legal / Privacy
A launch-safe privacy foundation for how Marketior handles website, intake, account, portal, analytics, and operational data.
Last updated: [Insert date before launch]
When a visitor submits a Private Growth Audit request, Marketior may collect contact details, company information, website URL, role/title, industry, company size, selected services, growth challenge, optional investment range, message content, consent confirmation, and related submission metadata.
This information is intended to help Marketior evaluate fit, route the request into CRM workflows, and prepare a relevant follow-up. Final collection language, consent language, and retention periods must be approved before launch.
Marketior OS uses authenticated accounts for internal users and client portal users. Account-related data may include identifiers, email-based authentication records, workspace memberships, roles, access permissions, and operational activity connected to the workspace.
Client portal visibility should remain limited to explicitly shared records and should not expose internal CRM notes, private activity logs, token material, or administrative configuration.
Marketior may use server-side analytics events, request correlation IDs, rate-limit logs, and operational observability to monitor reliability and security. These systems should avoid raw prompts, private notes, secrets, tokens, and PII-heavy payloads.
Operational logging may involve providers such as Vercel, Sentry or another observability service if configured. Final provider list and retention practices must be confirmed before launch.
Marketior OS includes AI-assisted content and strategy workflows. In mock mode, no external AI provider is required. If real AI provider mode is configured, prompts and generated outputs should be handled under approved data-processing rules and should not include unnecessary sensitive information.
The website and platform may use essential cookies for authentication, security, routing, and session management. Analytics or observability tooling may use additional identifiers depending on final configuration.
A separate Cookie Notice / Data Practices page should describe essential, analytics, observability, and future marketing cookies in more detail.
Current or planned providers may include Supabase, Sanity, Resend, Vercel, Upstash, Sentry or another observability provider, and an AI provider if real mode is enabled. This list must be reviewed against the actual production configuration before launch.
Data retention periods, user rights, deletion workflows, and regional privacy obligations must be finalized with qualified legal counsel.
Contact method: [Insert privacy contact email or business address before launch].