Privacy Policy & Data Protection
Last Updated: August 3, 2026 • BerryDB Desktop Software
Your database credentials, connection strings, query histories, and result rows remain strictly on your Mac. We never send database data to our servers.
Execute AI chat tools locally on Apple Silicon via Apple Foundation Models — guaranteeing zero network requests leave your machine.
License keys are verified offline on your device using cryptographic signatures without requiring continuous online tracking.
1. Local-First Architecture & Credentials
BerryDB Desktop is built from the ground up to respect data sovereignty. All connection profiles, passwords, TLS certificates, OpenSSH private keys, query execution histories, saved scripts, and workspace tab states are saved locally on your Mac. Sensitive passwords and key passphrases are secured using macOS Keychain Services.
2. AI Assistant Panel Data Handling
When using the AI Assistant panel in BerryDB Desktop:
- Schema Context: To generate contextually accurate SQL, table names, column names, and data types are included in prompt context sent to your designated LLM provider.
- Sample Rows Toggle: BerryDB includes an explicit toggle titled "Allow sending sample rows", which is OFF by default. Sample row data is never transmitted unless explicitly enabled by you.
- On-Device Option: You may select Apple Intelligence local models to process AI queries 100% on-device with zero network requests.
3. License Seat Telemetry & Hardware Hashing
During trial initialization and license activation, BerryDB Desktop calculates a one-way cryptographic hash of your Mac's hardware UUID (SHA-256). This non-reversible device hash is transmitted strictly to validate seat limits (up to 3 devices per license key) and manage trial durations. No user names, IP addresses, or file system contents are associated with this hardware signature.
4. Payments & Web Checkout Processing
License key purchases are processed via our payment merchant Paddle. Credit card details, billing addresses, and payment credentials are processed securely on Paddle web servers and are never seen, handled, or stored by BerryDB Desktop.