PGZen Privacy Policy
Last updated 2 November 2026
Draft — pending final review against the shipped release build before this page goes live.
The short version
PGZen sends connection and authentication traffic, and your SQL, only to the database or SSH server you choose, and saves exports only where you choose. Connection passwords are stored in the macOS Keychain. PGZen collects no usage analytics and has no backend that collects database content. Crash reporting is opt-in and disabled by default.
Credentials
Connection passwords, SSH passwords and key passphrases are stored in the macOS Keychain, protected by the operating system’s own access controls, and used when you connect to your database or SSH server. PGZen’s saved connection profiles never contain a password field, encoded or otherwise.
Database content
SQL text and bind parameter values go to the database or SSH server you connect to, and query results come back over that connection. Exports are written to locations you choose. PGZen has no backend service that collects database content.
Data stored on your Mac
Connection profiles, query history, snippets, settings and the list of .sql files and folders you open are stored on your Mac, inside PGZen’s app container. Connection and snippet names are added to Spotlight on your Mac so you can search for them. Nothing is synced to us: PGZen has no account and no server. Deleting PGZen and its container (~/Library/Containers/com.lucianboboc.PGZen) removes this data; saved passwords can be removed in Keychain Access.
Analytics
PGZen collects no usage analytics. If that changes, this section will say so explicitly before it ships — not after.
Crash reporting
Crash reporting is opt-in and disabled by default (Settings ▸ Privacy). If you turn it on, PGZen sends crash reports through Google’s Firebase Crashlytics: the crash stack trace, the app version, your Mac’s model, hardware and macOS version, and random installation identifiers used to count affected installations. While crash reporting is on, PGZen also sends a small session event, carrying the same installation identifier and a random session identifier, each time it launches. Crashlytics keeps crash reports for 90 days. Reports never include your SQL, bound values, query results, or credentials.
Crash reports and your consent
Crash reports are sent only because you chose to turn them on, and turning the setting off stops new reports and session events. Google processes them on our behalf and may do so outside your country; Firebase’s privacy and security page describes how.
Purchases
PGZen is sold on the Mac App Store. Apple processes the payment: we never receive your payment details or your Apple ID, only aggregated sales reports. Apple’s privacy policy covers the purchase itself.
This website
pgzen.dev uses no cookies, no analytics, and no third-party scripts or fonts. It is hosted on Cloudflare, which processes your IP address and request details to deliver and protect the site. If you email support, your message is kept only as long as needed to help you.
Your rights
Depending on where you live, for example under the GDPR or the CCPA, you can ask what personal data we hold about you, have it corrected or deleted, or object to how it is used. The only personal data that can reach us is crash reports and session events, if you turned crash reporting on, and emails you send. Write to info@pgzen.dev, or complain to your local data protection authority.
Children
PGZen is a tool for developers and database administrators. It is not directed at children under 13, or under 16 in the European Economic Area.
Contact
Questions about this policy or your data: info@pgzen.dev.
Changes to this policy
Material changes to this policy will be noted on this page.