Privacy Policy

1. Zero Backend & No Server Storage

Push44 is a purely client-side application. There are no Push44 backend servers, databases, or user telemetry collectors. Your GitHub personal access tokens, platform session tokens (Base44, Rocket.new, Floot, Zite, Bolt.new, Lovable.dev, Framer), and push history are stored exclusively in your browser's localStorage on your personal device.

2. Direct Browser-to-Service Communication

When you export or push code with Push44, your browser initiates direct encrypted HTTPS connections to GitHub's REST API and to the AI platform endpoints you connect. Your tokens and project code pass directly between your device and the destination APIs — Push44 does not proxy, intercept, or log source code content.

3. Zero Private Data Collection

Push44 does not store or process your private code or tokens on our servers. Standard edge CDN access logs (IP address, requested path, timestamp) may be retained briefly by our static hosting provider (Vercel) solely for DDOS mitigation, performance, and security.

4. Google AdSense & Advertising Cookies

Push44 uses Google AdSense to serve advertisements on public documentation and blog pages to keep the service free and open source. Google, as a third-party vendor, uses cookies (including the DoubleClick cookie) to serve ads based on prior visits to this website and other sites across the Internet. You may opt out of personalized advertising by visiting Google Ads Settings (https://adssettings.google.com) or aboutads.info.

5. Third-Party Platform Policies

GitHub, Base44, StackBlitz (Bolt), Rocket.new, Floot, Zite, Lovable, and Framer maintain their own respective terms of service and privacy policies governing data sent to their APIs. Push44 is an independent open-source client utility designed to interface with public or authenticated platform endpoints using credentials you control.

6. Local Storage Lifecycle

Because all credentials and history records live solely in your browser's localStorage (or AES-256-GCM encrypted local configuration files in the CLI), you have complete autonomy over your data lifecycle. You can wipe all credentials instantly via Settings > Clear Data, or by clearing your browser cache.

7. Changes to this Policy

Any updates or refinements to this privacy policy will be published directly to this page with an updated timestamp. Continued use of Push44 following revisions constitutes agreement with the terms described.

8. Inquiries & Support

If you have questions regarding this privacy document or the cryptographic implementation of our client storage, please open an issue or inquiry on our official GitHub repository.