Data you give Partizan

• account email and authentication data;
• product descriptions, public product links such as websites, apps, bots or repositories, markets, goals, budgets and customer-cost limits;
• channel preferences, approvals and integration choices;
• clarification answers, project settings and content you ask Partizan to prepare.

Data generated while Partizan works

• research evidence, acquisition opportunities, test plans and learning history;
• visits, signups, activations, paid-customer events and attribution identifiers when your product sends them;
• spend, revenue and related economics when the relevant source is connected;
• operational logs needed to diagnose failures, protect the service and reconcile execution.

Payments and connected services

Stripe handles checkout and payment processing. Partizan stores the billing status and identifiers needed to reconcile purchases and acquisition-budget funding, not raw payment-card details. When you connect a channel or provider, Partizan processes the credentials or tokens needed to use that connection within your permissions. Provider credentials are handled server-side and are not intended to be embedded in customer-facing pages.

How the data is used

Partizan uses this data to build Product Understanding, research evidence-backed acquisition opportunities before funding, operate the workspace, support optional deeper research, attribution, measurement, billing reconciliation, continuous learning, safety controls and support. Research evidence can suggest what to test; only measured customer outcomes are treated as conversion evidence.

Service providers

Partizan may send the minimum data required to infrastructure, model/search, billing and connected-channel providers when those services are needed to fulfil your request. Partizan is not designed to sell customer project data as an advertising product.

Retention and deletion

Project and account records are retained while needed to operate the workspace, preserve experiment history, reconcile billing and meet security or legal obligations. During beta, deletion requests are handled manually. Use the Contact page and do not put sensitive data into a public support issue.

Cookies and sessions

When you sign in, Partizan uses a first-party session mechanism to keep you authenticated and to enforce project ownership. The product does not need a third-party advertising cookie to provide the core workspace.