Privacy Policy

Account data: email, name, hashed password, session information, preferences (e.g., daily reports).

App data: personas, contacts, sequences, templates, workflows, and related settings.

Email data: sender alias, recipient address, subject, timestamps, delivery status, and activity such as opens and unsubscribes.

Tracking data: open tracking via a 1×1 image pixel and unsubscribe tokens processed through our tracking endpoints.

Integration data: Google OAuth tokens and granted scopes to send email, read specific messages for reply detection, and fetch aliases. We only access data within the permissions you authorize.

System data: logs, queue processing metadata, and Redis connection status for workflow automation.

Authenticate users and maintain sessions.

Manage personas, contacts, sequences, templates, and workflows you configure.

Send emails via connected Gmail accounts using authorized scopes and aliases.

Poll for replies to measure campaign performance and update contact states.

Track opens and unsubscribe actions to provide reporting and compliance tooling.

Schedule and queue automation tasks using Redis-backed workers.

Improve reliability and user experience using aggregated, non-identifying analytics.

We process data to fulfill our contract with you (providing the application), based on your consent (e.g., integrations), and for legitimate interests (improving security and service functionality).

Session cookies used for authentication and maintaining logged-in state.

Tracking pixel for email open detection embedded in campaign emails.

Unsubscribe links with tokens to honor opt-out requests.

You can manage cookies in your browser settings; unsubscribes are processed instantly through the provided links.

The application integrates with Google services (Gmail APIs) to enable email sending, alias management, and reply/bounce detection for campaign workflows.

We do not share Google user data with third parties, nor do we sell it.

If you configure external email providers (e.g., SendGrid or Brevo) for non-Gmail sending, those providers only receive the email content you send through them and not your Google account data.

Gmail content and tokens are not transferred to third-party providers.

Access and refresh tokens are stored in our server-side database tied to your account and are used solely to perform authorized actions.

Passwords are hashed (e.g., bcrypt). Password reset tokens are hashed server-side before storage.

Transport security (TLS/HTTPS) is enforced in production deployments; server access is restricted and monitored.

We apply least-privilege access and log only what's necessary for reliability and auditing.

We retain account and application data for the duration of your use of the service and as necessary to comply with legal obligations.

Tokens and Google integration data are retained while the account remains connected.

You can disconnect your Gmail account at any time from the Integrations page, which removes associated tokens and disables access.

You may request deletion of your account and related data by contacting support.

Some logs and aggregated analytics may persist for security and service integrity.

We rely on providers such as Google (Gmail APIs), Redis-backed queueing, and optional email services like SendGrid or Brevo if configured. Use of these services is subject to their terms; we access only within your granted permissions.

For questions about these terms or privacy practices, contact our support team.

This policy reflects features present in the current application, including email automation, tracking, integrations, and workflow scheduling. If your deployment includes additional services, those may be covered by supplemental terms.