Security at G6 Solver

Last Updated: 12 August 2025

1. Data Protection

Data at Rest

  • All stored data is encrypted using Django’s Fernet-based Base64 encryption with secure key management.
  • The desktop application encrypts all user data locally; this data is never transmitted to our servers unless required for specific user actions (e.g., bug reports).

Data in Transit

  • All communications between clients, servers, and third-party integrations occur over HTTPS/TLS to prevent interception or tampering.

2. Authentication & Access Control

  • User authentication requires a username and password.
  • All passwords are hashed and salted before storage; plaintext passwords are never stored.
  • Single-device licence enforcement is applied to the desktop application via a proprietary hashing function, preventing execution on unregistered devices.
  • MFA and token-based logins are not currently implemented due to the assumption that application access implies device-level authentication.

3. Infrastructure Security

Our server infrastructure is hosted on Amazon Web Services (AWS) with strong physical and network-level security.

Cloudflare is used for DDoS mitigation, firewalling, and traffic filtering.

Network security measures include:

  • Firewalls
  • Intrusion detection and prevention systems
  • Automated rate limiting for abusive traffic patterns

4. Application Security

Secure coding practices include:

  • Input validation and sanitisation
  • Prevention of SQL injection
  • Strict separation of code and data layers

We conduct:

  • Regular code audits
  • Vulnerability scanning
  • Penetration testing

Note: Due to the self-rewriting nature of the G6 Solver system, while we maintain strong safeguards, we cannot absolutely guarantee stability against every malicious attack vector.

5. Incident Response

  • We maintain internal protocols for detecting, logging, and investigating security incidents.
  • We aim to acknowledge and begin addressing reported vulnerabilities within 24 hours.
  • Security updates and patches are deployed as soon as practical after validation.

6. User Responsibilities

Users are responsible for securing their devices, operating systems, and login credentials.

We recommend:

  • Using strong, unique passwords.
  • Keeping your system and software up to date.
  • Avoiding use on unsecured or shared devices.

7. Responsible Disclosure

We welcome responsible disclosure of security vulnerabilities. If you discover a vulnerability, please email [email protected].

  • Do not exploit the vulnerability or access other users’ data.
  • Do not publicly disclose the vulnerability until we have confirmed and patched it.
  • Bug bounty rewards may be payable at our absolute discretion upon confirmation of the vulnerability.

8. Third-Party Services

Some G6 Solver features rely on external large language model (LLM) backend providers, such as OpenRouter.

  • We act as infrastructure on top of these LLMs and do not control their internal security or data handling.
  • You should review the security and privacy policies of these providers before use.
  • Data sent to third-party LLM providers is subject to their processing and storage policies.

9. Contact

For security-related concerns, please contact: [email protected]