Privacy notice

Pipeline Habit stores account details, legal acceptance date and document version, project settings, team memberships, lead and contact records, imported existing-customer/trial/partner relationships and their outreach policy, archive state, message templates, drafts, immutable sent-message snapshots and template-version attribution, import metadata, daily habit snapshots, sales activity, optional automation delivery attempts, inbound communication context, suppression records, and subscription state needed to provide the service. When an owner connects a mailbox, the provider, sender address, login identity, verification time, and an encrypted mailbox credential are also stored. Non-empty source columns that are not mapped to a standard lead or relationship field may be retained as imported source context.

Session and basic technical data are processed to authenticate users, verify email ownership, protect project access, diagnose failures, and operate the application. Authentication throttling stores HMAC-pseudonymized request keys rather than raw email and IP combinations. Public signup verification stores a single-use token hash for up to 24 hours, and password recovery stores a single-use token hash for up to 30 minutes; raw tokens are sent by email and are not stored.

Project data is used to build the daily action queue, render editable outreach drafts, track follow-ups and outcomes, calculate project analytics, and measure the project sales habit. Sending is manual by default. A project owner may explicitly enable paced email automation where that optional setting is available; Pipeline Habit retains delivery and suppression records, stops future automated contact after an opt-out, and does not automatically send Instagram or LinkedIn direct messages, posts, submissions, or replies.

Google Sheets, Google Docs, CSV, and Excel sources are used for one-way import. Pipeline Habit becomes the working record after import unless you run another import or supported status sync.

Pipeline Habit relies on infrastructure and service providers including Vercel for application hosting, Neon for managed database hosting, Stripe for billing and tax calculation, Resend for account verification, project invitations, and password recovery email, the project owner’s connected email provider for owner-enabled outreach and inbox synchronization, Meta for read-only Instagram conversation synchronization when connected, and Google services when a project owner connects or imports a Google source. These providers process only the data needed for their role.

Pipeline Habit does not sell project or lead data and does not use it for third-party advertising.

When you register through a campaign link, we may retain its campaign labels and public landing-page path with your account to understand which sources lead to verified signups and product use. This attribution does not include advertising click identifiers or full referring URLs, does not require an advertising cookie, and is removed with account deletion. We do not send your project or lead content to advertising networks.

Project access is limited by workspace membership. Owners can export project data as JSON, permanently delete a project, and delete their personal account from Account. Account deletion removes solely owned projects and revokes access to projects that remain with another owner. Archiving removes a lead from the active queue and plan count while preserving its history and analytics until restored or deleted.

Data is retained while the account or project is active and as reasonably needed for security, billing, tax, legal obligations, and provider backup cycles. An abandoned unverified public signup and its empty personal project may be removed after the verification link has been expired for 30 days; an existing invitation to another project is preserved. Contact the address below for corrections or requests that are not available in the product.