Privacy Policy

Effective 27 June 2026

1. What we collect

  • Account data — name, email address, organisation name. Collected at sign-up via Clerk.
  • Pipeline run data — step names, row counts, column schemas, null percentages, duration, anomaly signals. Sent by the pipelinehub library you instrument.
  • Billing data — payment method and transaction records are handled entirely by Dodo Payments. We store only your plan tier and subscription status.
  • Usage data — API request logs (timestamp, endpoint, status code) retained for up to 30 days for debugging.

2. What we do not collect

We do not receive the actual row-level contents of your dataframes — only aggregate statistics (counts, null rates, schema). Do not configure the library to send columns containing personal data.

3. How we use data

  • Display your pipeline run history and anomalies in the dashboard
  • Send alert emails when anomalies or failures are detected
  • Improve the Service and diagnose bugs
  • Process billing and prevent fraud

4. Third-party processors

  • Clerk — authentication and user management
  • Dodo Payments — payment processing and subscription management
  • Railway — cloud infrastructure (PostgreSQL database, API hosting)
  • Vercel — dashboard and landing page hosting

Each processor is bound by its own privacy policy and applicable data protection law.

5. Data sharing

We do not sell your data. We do not share pipeline run data with any third party except the processors listed above as required to operate the Service.

6. Data retention

Pipeline run data is retained according to your plan (Solo: 30 days, Team: 90 days, Business: unlimited). Account data is deleted within 30 days of account deletion. Billing records are retained as required by law.

7. Your rights

You may request access to, correction of, or deletion of your data at any time by emailing us. You may delete your account from dashboard settings; this triggers deletion of all associated pipeline data.

8. Security

Data is encrypted in transit (TLS) and at rest. API access requires a bearer token. We follow security best practices including non-root container processes and rate limiting.

9. Changes

We may update this policy. Material changes will be communicated by email. Continued use constitutes acceptance.

10. Contact

Privacy questions: hello@pipelinehub.cloud.