Privacy Policy
This document explains the information DevHub uses for accounts, developer discovery, projects, contact, email delivery, analytics, and partnerships without inventing legal facts that the product owner has not confirmed.
1. Scope and operator information
This policy covers visitors, account holders, DeveloperProfile owners, Project Showcase publishers, commenters and voters, contact-form submitters, and partner-inquiry submitters using DevHub.in.th.
Owner and legal-review blocker: the operator's legal entity name, registered address, registration details, formal privacy-request channel, and responsible privacy role have not been confirmed. This policy deliberately does not invent them.
2. Information categories and purposes
- Account and security: internal username, email, password hash, session data, email-verification state, login method, and security records for authentication, recovery, and abuse prevention.
- Developer profile: public name, slug, image, bio, role, experience, technologies, availability, self-selected services, and permitted contact channels for directory discovery and contact.
- Project Showcase: title, description, images, technologies, GitHub or demo links, comments, and votes for project evidence and participation.
- Inquiries: contact and partner-form data such as company, contact name, work email, website, objective, timing, budget status, and message so DevHub can assess and respond.
- Technical data: cookies, sessions, IP or hashed request fingerprint, user agent, URLs, and events designed to exclude PII for security, rate limiting, service operation, and consent-dependent analytics.
3. Public profiles and contact choices
An approved, public DeveloperProfile and an active Project Showcase may be discoverable by people and search engines. Contact methods and Consulting, Mentoring, Workshop, or Corporate Training services appear only when the profile owner selects and permits them. Pending, hidden, or suspended profiles and archived projects should not appear publicly.
Users must not publish confidential client, employer, or third-party information without authority.
4. GitHub, Google, and email
Users may sign in through GitHub, Google, or email. DevHub requests only the identity information configured for the workflow, such as basic profile and email data, and does not need repository, organization, contacts, or public-display access to OAuth tokens. When a provider cannot supply a trustworthy verified email, the user must add and verify one before sensitive writes.
Email-delivery records keep necessary metadata such as event/template key, recipient, locale, timestamps, retry state, and sanitized error details. They should not contain passwords, verification tokens, OAuth tokens, or full sensitive message bodies. Security and verification email is transactional; optional email must have preference and unsubscribe controls.
5. Cookies, analytics, and partner measurement
Necessary cookies support sessions, security, and requested preferences. Analytics or GTM should load according to the consent state the product supports. Analytics events must not include names, emails, OAuth identifiers or tokens, message contents, or private contact details.
Sponsored placements must be labeled, use sponsored-link attributes, and be measured separately from organic ranking. Partner reporting uses aggregate data, suppresses personal and low-sample-size breakdowns, and shares lead details only when the submitter explicitly consents for that purpose.
7. Retention, correction, and account deletion
Each category should be kept only as long as needed for the account, requested service, security, dispute handling, and applicable obligations, then deleted, anonymized, or restricted as appropriate. Users can correct profile information and request account deletion through available DevHub channels. Deletion may not immediately remove records that must remain for security, legal obligations, or rotating backups.
No numerical retention schedule has been approved. The owner and legal reviewer must set periods for accounts, public content, comments and votes, inquiries, email logs, analytics, security logs, and backups using real operational and legal requirements. An invented period must not be substituted.
8. Rights, security, and contact
Subject to applicable law, people may request access, correction, deletion, restriction, objection, consent withdrawal, or a portable copy where those rights apply. DevHub uses authorization controls, email verification, CSRF protection, rate limiting, minimized logs, and security settings, but no service can guarantee absolute security.
Until a dedicated privacy channel is confirmed, submit a request through DevHub's contact form and avoid including unnecessary sensitive information.