# Security Policy At Push44, security and developer privacy are our highest priorities. Push44 is engineered to operate strictly client-side without storing user credentials, platform session tokens, or private repository data on intermediate servers. ## Supported Versions | Version | Supported | | ------- | ------------------ | | 1.x.x | :white_check_mark: | ## Reporting a Vulnerability If you discover a potential security vulnerability or sensitive data disclosure issue within Push44, please report it responsibly. 1. **Do not create public GitHub issues for security vulnerabilities.** 2. Send an email with the subject line `[SECURITY VULNERABILITY] Push44` to the maintainer or submit a private security advisory through GitHub's Security Advisories tab. 3. Provide detailed steps to reproduce the issue, including: - Platform / browser / environment details - Affected components (Web app, APK, or CLI) - Proof of concept or reproduction steps ## Our Commitment - We will acknowledge receipt of your report within 48 hours. - We will provide an assessment and timeline for a patch. - Once fixed, we will publish an advisory acknowledging your responsible disclosure (if desired).