Privacy Policy

HỘ KINH DOANH HỆ SINH THÁI PHẦN MỀM BERRYHUB (BERRYHUB SOFTWARE ECOSYSTEM), Business Registration No. 042088009617, 903 C2A Ecohome2, Phường Đông Ngạc, Thành phố Hà Nội, Việt Nam (“BerryHub”, “we”, “us”) is responsible for the personal data described in this policy. It applies to berryhub.app and its subdomains (the “Website”), to our desktop apps, including BerryDB, BerryShot and BerryVideo (the “Apps”), and to the BerryHub AI service. Capitalized terms have the meaning given in our Terms of Service.

BerryDB: data that stays on your Mac

• Connection details (such as host, port, user name and database name), queries, query history, editor tabs, saved queries, AI chat history, results of queries the AI assistant ran, and the schema metadata BerryDB indexes are stored in a database file in ~/Library/Application Support/BerryDB on your Mac.
• Database passwords, SSH passwords and key passphrases, and service API keys are stored in the macOS Keychain. SSH private keys stay in their own files; BerryDB only stores their location.
• BerryDB connects directly from your Mac to the databases, cloud database services and SSH hosts you configure. That traffic does not pass through BerryHub servers.
• You can turn off query history for a connection, clear it, delete AI chats, or remove all local data from the App’s settings.

BerryDB: license and credit checks

When you open a BerryDB window or its license screen, BerryDB asks our server whether your Mac has a license or trial. This request sends a device identifier: a one-way hash derived from your Mac's hardware identifier, which cannot be turned back into it. When you connect to a database, BerryDB also asks for your AI credit balance, sending your access token if you have one. If you start a trial, restore a purchase or activate a license key, BerryDB sends the email address or license key you enter. The signed license is then stored on your Mac, and the access token in the Keychain.

BerryDB: the helper for coding agents

BerryDB includes a helper, berrydb-mcp, that coding agents such as Claude Code or Cursor can start on your Mac. It talks to the agent only through a local pipe and opens no network port. It reads BerryDB's local database and shares only the schema metadata of the connections you add to a project in BerryDB's settings: connection name, type and environment label, table, view, column and index names, relationships, and table sizes and row counts. It does not connect to your databases, run queries, or read your passwords. Projects are off until you set them up.

BerryShot

• Screenshots, screen recordings, annotations and capture history are stored locally on your Mac, in the locations you choose.
• OCR and automatic redaction of sensitive information (such as passwords, card numbers and API keys) run on your device.
• BerryShot asks macOS for Screen Recording, Accessibility and Microphone permissions only to provide the features you use. You can revoke them at any time in System Settings.
• Its helper for coding agents communicates with the app over a private local connection on your Mac and does not open a network port. Temporary artifacts it creates expire automatically.

Downloads and updates

The Apps check our download server for new versions and download updates from it. Each check sends the technical information any web request carries, such as your IP address and the app name and version. We use it only to deliver updates and keep the service secure. The Apps do not include analytics, advertising or crash reporting software. If you download a release from GitHub or Homebrew instead, those services handle the request under their own policies.

BerryDB includes an optional AI assistant that runs on the BerryHub AI service. To use it, you start a free trial with your email address or buy prepaid credit. You can also use an on-device mode that runs Apple Intelligence on your Mac. AI is off by default for connections you label as production, and you can turn it off for any connection.

What we collect

• Account and license. Your email address, the device identifiers of up to three Macs, your license or trial status and expiry, any license key issued to you, and your credit balance.
• Payments. Credit is sold through Paddle, which handles checkout, payment, taxes and invoices. Paddle receives your email address and your device identifier to link the purchase to your Mac. We keep transaction records (amount, currency, status and date) but never receive your card details.
• AI requests. The message you write and the recent conversation, together with whatever the assistant retrieves to answer it: table, column and index names and definitions, query text from your editor tabs and query history, query plans, and the results of queries it runs. By default the assistant may run read-only queries without asking and receive up to 100 rows of their results. You can turn this off in the AI settings, after which every query needs your approval. Other statements always need your approval, and sample rows are sent only if you allow them for that connection.
• Search embeddings. To make your chats and your schema searchable, BerryDB sends the text of chat messages and the names of your tables and collections to the service, which converts them into numeric vectors. The vectors are stored on your Mac.
• Usage records. The time, type and size of each request (such as tokens used) and its cost, so we can charge your credit, apply trial and usage limits, and prevent abuse.
• Reports you send. If you send a report from the AI panel, we store your report text and, if you leave the option on, a summary of the recent conversation, together with your email address, so we can investigate it. Before you send, BerryDB shows you the report and summary.

How we handle it

• BerryDB adds its own instructions and context to your message and sends the request through the BerryHub service to the AI model you select. We route requests through OpenRouter, which passes them to the provider of that model, for example DeepSeek, Google, Anthropic or OpenAI. Those providers process the request only to produce the answer.
• Apart from the reports you choose to send, BerryHub does not store the content of your AI requests, answers or query results on our servers. Your chat history stays on your Mac until you delete it.
• We do not use your prompts, schemas or query results to train AI models, and we do not sell them.
• OpenRouter and the model providers may keep request data for a limited time under their own policies, for example to detect abuse.
• In on-device mode, answers are generated by Apple Intelligence on your Mac. The text of those messages is still sent to the BerryHub service to compute the search embeddings described above.

Some features send data to a service you choose and connect with your own API key or account. They are off until you set them up:

• AI assistants with your own key in BerryShot (OpenAI, Anthropic, Google Gemini, OpenRouter or Xiaomi MiMo): the prompt you write and the screenshot or text you ask the assistant to analyze.
• Live transcription in BerryShot (Deepgram or OpenAI): the audio being transcribed.
• Uploads in BerryShot (Google Drive or an upload endpoint you configure): the files you choose to upload.
• Coding agents connected to BerryDB: the schema metadata described under Data in our Apps. The agent may send it to its own AI provider.

This data goes directly from your device to the provider or agent. BerryHub does not receive or store it. Each provider handles it under its own terms and privacy policy, so please review them before enabling a feature. Before sending captures to AI providers, consider using BerryShot's redaction tools to remove sensitive information.

BerryVideo uses YouTube API Services to publish videos to YouTube on your behalf. By connecting a YouTube account or channel to BerryVideo, you agree to be bound by the YouTube Terms of Service. Google's use of your data is described in the Google Privacy Policy.

What BerryVideo accesses

• Basic information about the channel you choose when you sign in with Google (its ID, name and picture), so BerryVideo can show which channel you are publishing to.
• Uploading the videos you choose to publish, with the details you set in BerryVideo: title, description, tags, category, privacy status, whether the video is made for kids, and the disclosure that it contains altered or synthetic content.
• Creating a playlist for each video series you publish and adding the series’ videos to it. To avoid duplicates, BerryVideo looks up the playlists on your channel and the items in the playlists it created.

Google grants these actions through a single permission, “Manage your YouTube account”, because YouTube offers no narrower permission that allows creating playlists. BerryVideo uses it only for the actions above. It does not read your comments, subscribers or analytics, does not edit or delete videos it did not upload, and does not access any other data in your Google account.

How we store and use it

• The refresh token Google issues when you connect YouTube is encrypted with AES-256 before it is stored, can be decrypted only for the workspace that connected the channel, and is used only to publish the videos you choose. Short-lived access tokens are used only while publishing.
• We do not sell YouTube or Google user data, use it for advertising, share it with third parties, or use it to train AI models.
• BerryVideo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting YouTube

You can disconnect YouTube in BerryVideo at any time. BerryVideo then revokes its access at Google and deletes the stored token. You can also revoke BerryVideo's access from your Google Account at myaccount.google.com/permissions; the tokens then stop working immediately. Videos already published stay on YouTube until you delete them in YouTube Studio.

• Server logs. Like most websites, our servers record technical data for each request, such as IP address, date and time, requested page, referrer and browser user agent.
• Content delivery and security. The Website is served through Cloudflare, which processes request data to deliver pages and protect against attacks, and may set strictly necessary security cookies.
• Fonts. The Website loads the Inter font from Google Fonts, so your browser connects to Google servers, which receive your IP address.
• Theme preference. If you pick light or dark mode, the choice is saved in your browser's local storage. It never leaves your device.

The Website has no forms, no analytics trackers, no advertising cookies and no Meta Pixel, and does not track you across other sites. Links to external sites are governed by those sites' own privacy policies.

If you email us, open an issue on GitHub, write in our community channels (such as our Telegram group), or support us through a donation platform, we receive the information you provide, such as your name, email address or username, your message, and any attachments. Messages on GitHub and in community channels may be visible to others under those platforms' rules. Donation payments are processed by the platform (for example Ko-fi and its payment partners). We do not receive your full card details.

If you interact with BerryHub through Meta products, for example by messaging our Facebook Page, commenting on our posts or responding to our ads, Meta shares with us the information needed for that interaction: your public profile name, an ID that is specific to our Page, the content of your messages or comments, and any details you choose to give us, such as an email address.

• We use this data only to reply to you and to provide the support you ask for.
• We do not sell it, use it to build advertising profiles, combine it with data from our Apps, or share it with anyone except service providers that help us respond to you.
• We keep it only as long as needed to handle your request, and delete it when you ask, as described in How to delete your data below.
• Our Website does not use the Meta Pixel or other Meta tracking tools.

We use the data described above only to:

• deliver the Website, App downloads and updates;
• provide the BerryHub AI service, check licenses and credit, and process payments;
• keep our services secure, prevent abuse and diagnose technical problems;
• respond to your questions, reports and requests;
• comply with our legal obligations, including accounting and tax rules.

We process personal data with your consent or where applicable law otherwise allows it, for example to do what you asked us to do, to meet legal obligations, or, where the law where you live recognizes it, for our legitimate interest in running secure and reliable services. Where we rely on consent, you can withdraw it at any time. We do not sell personal data, use it for advertising, or make automated decisions that have legal effects on you.

We share personal data only:

• with service providers that help us operate, bound to protect it: hosting, content delivery and security (Cloudflare), code hosting (GitHub), email delivery and payments (Paddle);
• with OpenRouter and the AI model providers that process BerryHub AI requests;
• with Google, through YouTube API Services, when you publish videos to YouTube with BerryVideo;
• when required by law, a court order or a competent authority;
• to protect the rights, safety or property of our users, the public or BerryHub;
• as part of a reorganization or transfer of our business, subject to this policy.

Some of these providers process data outside Vietnam, including in the United States, the European Union and, if you choose a model hosted there such as DeepSeek, China. When that happens, we take the steps required by applicable law to protect the data.

• Server logs are kept for up to 90 days, unless needed longer to investigate a security incident.
• Account, license and usage records are kept while your account is active. When you ask us to delete your account, we delete them within 30 days.
• Payment and transaction records are kept for as long as accounting and tax laws require.
• Reports you send from the AI panel are kept until we have handled them, and deleted on request.
• BerryHub does not keep the content of AI requests. Your AI history stays on your Mac, and OpenRouter and the model providers keep request data according to their own policies.
• Messages you send us are kept only as long as needed to handle your request.
• Data stored locally by the Apps stays on your device until you delete it or uninstall the App.

We use HTTPS for the Website and the BerryHub AI service, store App credentials in the macOS Keychain, store only a one-way hash of your device identifier, encrypt the API keys our server uses with AI providers, and keep the data we hold to a minimum. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If we become aware of a breach affecting your personal data, we will notify you and the authorities as required by law.

Under the personal data protection laws of Vietnam, and depending on where you live (for example under the EU or UK GDPR or US state privacy laws), you may have the right to:

• be informed about how your data is processed;
• access, correct or obtain a copy of your personal data;
• request deletion of your personal data, or restrict or object to its processing;
• withdraw consent at any time, without affecting earlier processing;
• lodge a complaint with a data protection authority.

To exercise these rights, email [email protected]. We may need to verify your identity, and we will respond within the time required by law, and in any case within 30 days.

Anyone can ask us to delete their personal data at any time, whether you use our Apps, have a BerryHub AI account, or contacted us through Facebook, Messenger, Instagram, email or any other channel.

Ask BerryHub to delete your data

1. Send an email to [email protected] with the subject “Data deletion request”.
2. Tell us how to find your data: the email address you used for a BerryHub AI trial, purchase or license, and, if you contacted us on Facebook, Messenger or Instagram, your profile name or a link to your profile.
3. We may ask you to confirm the request from the same email address or account. We then delete your account, license, device identifiers, usage records, reports and messages, and email you a confirmation, within 30 days of your request.

Deleting your account also ends your license and any trial, and forfeits remaining credit unless the law or our refund terms provide otherwise. We may keep records that the law requires us to keep, such as invoices and payment records, and data that has been anonymized so that it can no longer identify you.

Delete data stored on your Mac

• In BerryDB, delete AI chats from the chat list, clear query history, or use Reset Local Data in the settings. To remove everything, uninstall the App and delete its folder in ~/Library/Application Support.
• Sign out of BerryHub AI in BerryDB’s license screen to remove the license and access token from your Mac.
• Remove saved credentials by deleting the matching entries in the Keychain Access app.
• Revoke API keys you created with third-party providers in those providers’ dashboards, and ask them directly to delete data where needed.
• Disconnect YouTube in BerryVideo, or revoke its access at myaccount.google.com/permissions.

The Services are intended for professionals and are not directed at children under 16. We do not knowingly collect personal data from children. If you believe a child has sent us personal data, please contact us and we will delete it.

We may update this policy as our Apps and the law evolve. We will change the “Last updated” date above and, for material changes, give a more visible notice on the Website or in the release notes of the affected App.

For any privacy question or request, contact: