Controls Engineering HubControls Engineering Hub

Privacy Policy

Last updated: 5 June 2026

1. Who we are

Controls Engineering Hub (“we”, “us”, or “our”) operates the website at controlsengineeringhub.com. We provide professional engineering education and community tools.

2. Data we collect

  • Account data: email address, username, and bcrypt-hashed password when you register.
  • Profile data: full name, job title, company, bio, avatar URL, and skills — all optional and provided by you.
  • Learning data: course enrollments, lesson completion records, and progress percentages.
  • Community data: forum threads, replies, votes, and project showcase submissions you create.
  • Payment data: transaction records including amount, currency, and Stripe session ID. We do not store card numbers or bank details — all payment processing is handled by Stripe.
  • Session data: a JWT session cookie to keep you signed in. It contains your user ID, role, and username.

3. How we use your data

  • Authenticate your account and keep you signed in
  • Deliver course content you have purchased or enrolled in
  • Display your profile and community contributions
  • Send in-app notifications about replies, approvals, and purchases
  • Process and record payments via Stripe
  • Detect and prevent fraudulent or abusive activity

We do not sell your data. We do not use your data for advertising.

4. Third-party services

  • Stripe — payment processing. Your payment details are submitted directly to Stripe under their privacy policy.

5. Data retention

Your account data is retained for as long as your account exists. If you request account deletion, we will remove your personal data within 30 days, subject to legal retention obligations for payment records.

6. Your rights

You may request access to, correction of, or deletion of your personal data at any time by contacting us at privacy@controlsengineeringhub.com. You may also update your profile information directly in your account settings.

7. Security

Passwords are hashed with bcrypt (12 rounds) and never stored in plaintext. Sessions use signed JWT tokens. Payment data flows exclusively through Stripe's PCI-compliant infrastructure — no card data touches our servers.

8. Changes to this policy

We may update this policy as the platform evolves. Material changes will be communicated via an in-app notification. Continued use after changes constitutes acceptance.

9. Contact

Privacy questions: privacy@controlsengineeringhub.com