Privacy Policy

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 helps Marketior evaluate fit, route the request into CRM workflows, and prepare a relevant follow-up.

Marketior 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 is intended to 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, internal operational analytics, request correlation IDs, rate-limit logs, and operational observability to monitor reliability, support, and security. These systems should avoid raw prompts, private notes, secrets, tokens, and unnecessarily PII-heavy payloads.

Operational logging and request handling may involve providers such as Vercel, Sentry or another observability service if configured, Supabase for application data, and Upstash for rate-limit enforcement. Provider use and retention practices may change as Marketior updates its production configuration.

Marketior includes internal, operator-led AI-assisted content and strategy workflows. Where configured, prompts and generated outputs may be processed by an OpenAI-compatible provider and should be handled under approved data-processing rules without unnecessary sensitive information.

AI-generated material is intended to support internal drafting and review workflows rather than final autonomous decision-making, and human review should occur before external use.

Marketior may use authenticated portal workflows to share reports, approvals, content previews, and strategy summaries with client users on a selective basis. Only records explicitly marked for sharing are intended to appear in the client portal.

If LinkedIn connection or controlled publishing features are enabled internally, account authorization, connection status, and publish-attempt metadata may be processed to operate that workflow. These features are intended for internal operator control and are not a broad client-facing publishing service.

The website and platform may use essential cookies for authentication, security, routing, session management, and similar platform continuity functions. 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 Vercel for hosting and deployment, Supabase for authentication and application data, Resend for notification email, Upstash for rate limiting, Sentry or another observability provider for monitoring, and an OpenAI-compatible provider for internal AI-assisted workflows where configured. LinkedIn may also process account authorization or publishing data if controlled internal publishing features are enabled.

This provider list may change as Marketior updates hosting, analytics, communications, security, or platform operations.

Data retention periods, user rights, deletion workflows, and regional privacy obligations may vary based on applicable law and operational context.

For privacy-related requests, contact Marketior through the Private Growth Audit form or the primary contact details published on the website.