DQHubdqhub.io

Privacy Policy

Last updated: May 27, 2026

1. Overview

DataQ, Inc. ("we," "us") operates DQHub (dqhub.io). This Privacy Policy explains how we collect, use, and protect your information when you use our service.

Key principle: Your test data never leaves your browser. We do not collect, transmit, or store any data you upload for testing.

2. Information We Collect

2.1 Account Information

When you sign in via OAuth (GitHub, Google, GitLab, or Bitbucket), we receive:

  • Name and username
  • Email address
  • Profile picture URL
  • OAuth provider ID

We do not receive or store your password from any OAuth provider.

2.2 Usage Data

We collect anonymized usage data to improve the service:

  • Pages visited and features used
  • Rule packs viewed and downloaded (format selected)
  • Search queries (to identify gaps in our pack library)
  • Browser type, device type, and general location (country level)

2.3 Content You Publish

When you create and publish a rule pack, we store the pack metadata, template structure, and associated tags. Published packs are publicly visible.

2.4 Data We Do NOT Collect

  • Test data: CSV files and data you upload in the Playground or Pack Testing features are processed entirely in your browser using JavaScript. This data is never transmitted to our servers, never stored, and never accessible to us.
  • Passwords: We use OAuth — we never see or store your passwords.
  • Payment information: DQHub is currently free. We do not collect payment data.

3. How We Use Your Information

  • To provide and maintain the service
  • To display your profile on published packs (username, avatar)
  • To send service-related communications (account notifications, pack updates)
  • To analyze usage patterns and improve the service
  • To identify popular search queries and build new packs

We do not sell your personal information to third parties.

4. Data Storage and Security

  • Account data is stored in a PostgreSQL database hosted on Neon (US-East region, AWS infrastructure)
  • All data is encrypted in transit (TLS/HTTPS) and at rest
  • We use industry-standard security practices including parameterized queries, CORS restrictions, and rate limiting
  • Template files are stored in Cloudflare R2 (S3-compatible object storage)

5. Third-Party Services

We use the following third-party services:

  • Vercel: Hosting and deployment (vercel.com)
  • Neon: Database hosting (neon.tech)
  • Cloudflare: DNS, CDN, and R2 storage (cloudflare.com)
  • GitHub/Google/GitLab/Bitbucket: OAuth authentication
  • Anthropic: AI features for rule generation (api.anthropic.com)

Each third-party service has its own privacy policy. We encourage you to review them.

6. Cookies

We use essential cookies for:

  • Session management (keeping you signed in)
  • CSRF protection

We do not use advertising or tracking cookies. We do not participate in cross-site tracking.

7. Your Rights

You have the right to:

  • Access: Request a copy of your personal data
  • Correction: Update inaccurate information
  • Deletion: Request deletion of your account and associated data
  • Export: Download your published packs and profile data
  • Opt-out: Unsubscribe from non-essential communications

To exercise these rights, contact us at privacy@dqhub.io.

8. GDPR Compliance

For users in the European Economic Area (EEA):

  • Legal basis for processing: Legitimate interest (service operation) and consent (account creation)
  • Data controller: DataQ, Inc.
  • You have the right to lodge a complaint with your local data protection authority
  • Data transfers outside the EEA are protected by Standard Contractual Clauses

9. CCPA Compliance

For California residents:

  • We do not sell personal information
  • You have the right to know what data we collect and request deletion
  • We will not discriminate against you for exercising your privacy rights

10. Children's Privacy

DQHub is not intended for children under 16. We do not knowingly collect information from children under 16. If we learn we have collected such information, we will delete it promptly.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify users of material changes via the service or email. The "Last updated" date at the top reflects the most recent revision.

12. Contact

For privacy questions or requests: