Privacy

01Data we process

• Lead identity: name, phone, email, campaign metadata
• Consent artifacts and form text versions
• Call metadata, transcripts, and recordings when enabled
• Qualification inputs and outcomes
• Suppression phone numbers (do-not-call)
• Waitlist entries and support tickets
• Account users: name, email, role membership
• Sealed OAuth tokens for connected CRMs/calendars (stored encrypted, not plaintext)
• First- and last-touch campaign parameters and referring domain for demo attribution

02Site storage and analytics

• We use essential HttpOnly cookies for sign-in and first-party local storage for theme and this notice
• Campaign attribution (first/last-touch parameters and referring domain) loads only after you Accept
• Optional Plausible analytics receives event names and non-PII attribution fields only after you Accept
• Forms do not send names or email addresses as analytics properties

03Purposes

• Lead contact
• Qualification
• Booking
• Product analytics for the customer org
• Security
• Abuse prevention

We do not sell lead lists.

04Retention

• Leads: default 365 days per workspace retention settings then anonymized; workspace override applies.
• Call transcripts and recordings (when enabled): follow plan defaults — launch 30 / growth 90 / scale 365 — unless workspace retention override applies.
• Audit / security logs: same plan defaults (launch 30 / growth 90 / scale 365) unless workspace retention override applies.
• Legal hold: when workspace retention hold is enabled, retention wipe is skipped.
• Accounts: deletion is deactivation. If you were the sole owner, workspace lead data is anonymized. Contact support for residual copies (CRM, backups). Not an automatic 90-day wipe.
• Demo/synthetic data: labeled and may be wiped without notice.

Export and deletion

Customers are typically controllers of lead data; MinuteOne acts as processor. Access, correction, export, and deletion of lead data is via the tenant operator (workspace owner) or via contact. Owners can export workspace JSON and deactivate accounts in Settings. Sole-owner close anonymizes workspace leads; residual CRM/backups still need support.

05Subprocessors

Depending on configuration we may use:

• Hosting providers for compute/storage
• Stripe (billing)
• LiveKit (realtime voice)
• Mailcow (email)
• n8n (automation)
• Optional LLM providers for support chat

A current list is published at /subprocessors.

06GDPR / rights

Where GDPR or similar law applies, customers are typically controllers of lead data and MinuteOne acts as processor under their instructions. Data subjects may request the following via the customer organization (controller) or our privacy request form:

• Access
• Correction
• Export
• Deletion

This page is not a substitute for counsel-reviewed policy and does not claim certification.

07International transfers

Some subprocessors are in the United States. The current list is on /subprocessors. Standard contractual clauses and EU–US Data Privacy Framework participation are not claimed here until counsel executes them. See International transfers.

08EU representative

No Art. 27 representative appointed. If MinuteOne is established in the EU (recommended: host API/DB/recordings in EU), Art. 27 may not apply. Until establishment or a named representative, we do not offer this as GDPR-complete.

09Contact

Privacy questions: use the contact form or email the address provided during onboarding. DPA requests: see the unsigned DPA template or note “DPA” in the contact subject.