What LidPush Collects
LidPush is a desktop application that requires GitHub authentication via OAuth 2.0. The following data is collected and stored:
- GitHub profile: GitHub user ID (numeric), username, and avatar URL — collected during OAuth authentication.
- Push history: Repository name, files pushed, files cleaned, secrets blocked, and timestamp of each push operation.
- Last seen: Timestamp of your most recent activity in the app.
No file contents, source code, or project data are ever transmitted. The cleaning engine copies your project locally and only sends aggregate statistics (file counts, not file contents) to the database.
Data Storage
Data is stored in a Neon PostgreSQL database (cloud-hosted PostgreSQL). Two tables are used:
users— github_id, username, avatar_url, last_seen, created_atpushes— repo_name, files_pushed, files_cleaned, secrets_blocked, created_at
This data feeds the Lidprex platform for operational analytics and product improvement. No third-party analytics SDKs are used.
GitHub Token Storage
Your GitHub OAuth token is stored in Windows Credential Manager via the keyring Rust crate. The React frontend never has access to the token — it only sees success/failure responses from the internal Axum API.
Internal API Security
The embedded Axum HTTP server starts on a random port every launch. Every request requires an x-lidpush-secret header containing a UUID generated fresh each session. Nothing on the machine can call the internal API without knowing both the port and the secret.
What We Do NOT Collect
- No file contents or source code from your projects
- No credentials, API keys, or secrets found during scans
- No keystrokes, mouse movements, or UI interactions
- No third-party analytics (no Google Analytics, Sentry, etc.)
- No cookies or tracking pixels
- No crash reports or error telemetry
Data Deletion
To request deletion of your data from the Lidprex platform, contact us through Lidprex Labs ↗ with your GitHub username. We will process deletion within 30 days.
Contact
For privacy-related inquiries, visit Lidprex Labs ↗ or open a discussion on GitHub ↗.