BetaHub Privacy Policy

Last updated: October 28, 2024

1. Introduction

Welcome to BetaHub (“we,” “our,” or “us”). Your privacy is important to us, and we are committed to processing your personal data transparently and responsibly. This Privacy Policy outlines how we collect, use, disclose, and protect your information when you use our software-as-a-service platform to collect feedback from game players. We encourage you to read this policy in full to understand your data rights and our practices.

2. Legal Basis for Processing

BetaHub processes personal data based on the following legal grounds:

• Contractual Necessity: To fulfill the essential role of our service by enabling feedback collection, bug reporting, and gameplay insights.
• Legitimate Interests: To maintain account security, manage user accounts, and support platform functionality, as long as these interests do not infringe on your privacy rights.
• Consent: For optional tracking and analytics cookies, and any other data processing that requires explicit permission. Cookie settings can be managed via /privacy/cookies, and users in channels with the BetaHub bot can opt-out of specific tracking (like sentiment analysis) by using /help.

3. Information We Collect

3.1 Developers

We collect information essential for managing developer accounts on BetaHub, including:

• Email address: Necessary for logging in or switching from third-party login.
• Account ID: Provided by third-party services like Discord, Google, or GitHub.
• Discord username and avatar: Used when logging in via Discord. Users may choose to hide their avatar or username for privacy.

3.2 Game Testers

For game testers, we may collect specific data depending on usage and interactions:

• Gameplay data: Includes in-game actions, player feedback, and issue reports, aiding developers in troubleshooting and optimizing performance.
• Hardware specifications: Details like operating systems and GPUs help developers assess performance across setups.
• User login information: Optional, for testers who register with BetaHub to track and manage feedback.
• Bug reports: Descriptions of bugs or suggestions, often including contextual data for troubleshooting.
• Discord account ID: Used when reports are submitted via our Discord bot, linking tester reports to their account for easier management through Discord.

Users explicitly agree to share gameplay and hardware data through submission forms, where they can control the data they choose to share.

4. How We Use Your Information

4.1 Developers

Developer information is used to:

• Provide, maintain, and improve the BetaHub platform.
• Facilitate user identification and account management.
• Communicate regarding technical issues, feature updates, or onboarding support.

4.2 Game Testers

Tester information is used to:

• Process and analyze bug reports: Includes in-game data, hardware configurations, and feedback to address reported issues.
• Enhance game development: Feedback and performance data are shared with developers to improve game functionality and understand gameplay dynamics.

Game testers may be contacted by BetaHub via the Discord bot or email about changes in their bug report or suggestion statuses. They can opt-out of notifications. Developers may also contact testers through BetaHub’s platform, but will not see the tester’s email address; Discord usernames are visible only if testers have not chosen to hide them.

5. Data Visibility and Access

5.1 Developers

• Developer data is visible only to BetaHub administrators for platform maintenance.
• Truncated email addresses may be displayed to prevent exposure unless developers choose a nickname.
• Discord usernames and avatars are visible only if used as nicknames, with control options available on the profile settings page.

5.2 Game Testers and Projects

• Only the Main Administrator of BetaHub, with project owner consent, can access project data.
• Testers control data shared in reports, with all data collected through the game engine plugin subject to their consent.
• Testers can view and control shared data in their BetaHub account or by logging in with Discord.

6. Third-Party Services and Data Sharing

BetaHub integrates with third-party services like Stripe and Google Analytics to support analytics and secure payment processing:

• Analytics: We use Matomo and Google Analytics for anonymous tracking on our website, with no tracking on our Discord bot or other integrations.
• Payment Processing: Stripe handles payments. For trial accounts, only an email is shared; paid accounts require additional billing information, collected directly by Stripe. These third-party providers comply with GDPR protections.

7. Cookies and Tracking Technologies

BetaHub uses cookies to support essential functionality and analytics:

• Session Cookies: Necessary for login and navigation.
• Performance Cookies: With your consent, Matomo and Google Analytics cookies gather anonymous data on website interactions to improve user experience.
• Managing Cookies: Users can manage cookies through browser settings or directly on our /privacy/cookies page.

8. Data Protection and Security

We implement stringent security protocols to protect user data:

• Data Storage: Data is stored in an encrypted PostgreSQL database and encrypted S3 storage managed by AWS.
• Access Control: Direct data access is limited to select administrators who must have project owner consent before viewing data.
• Internal Compliance: Access to data is permitted only when initiated through a support ticket from the project owner. Data access is strictly for solving the tester-reported issue, and administrators cannot access data for other purposes.

9. International Data Transfers

Data is stored exclusively within the EU. Developers using third-party tools (e.g., Jira) may transfer bug report data outside the EU. In such cases, developers are responsible for notifying testers and complying with applicable data protection standards.

10. Data Retention

• Retention Period: Bug reports and feedback are retained for the duration of the project to facilitate ongoing development. When testers submit feedback, they grant BetaHub permission to retain it for the lifetime of the project. Testers retain rights to anonymize, delete, or modify their contributions at any time.
• Data Deletion: When a project is removed, all associated data is permanently erased from our systems. Users may request data deletion through their account settings.

11. User Rights

Under GDPR and other applicable laws, users may:

• Access: View personal data collected by BetaHub.
• Correction: Update inaccurate data.
• Deletion: Request data deletion.
• Restriction: Limit specific data processing.
• Portability: Receive data in a common format.
• Objection: Object to processing based on legitimate interests.
• Withdraw Consent: Withdraw consent for optional processing (e.g., cookies or analytics).

Most requests can be managed through your BetaHub account. For further requests or appeals, please contact us at privacy@betahub.io or use our contact form. We strive to respond within 30 days.

12. Children’s Privacy

BetaHub requires a credit card for paid services, ensuring users meet the legal age for transactions. For non-payment accounts, users confirm age through a checkbox upon registration. Content marked for adults is restricted by default for minors, and access is only enabled after age verification, protecting younger users from restricted areas.

13. Updates to This Privacy Policy

BetaHub may update this policy to reflect changes in legal, technical, or business practices. Users should review updates on this page, as indicated by the “Last updated” date.

14. Contact Us

For questions or concerns about this Privacy Policy or BetaHub’s data practices, please reach out at privacy@betahub.io or via our contact form.