DBPort
FeaturesSecurityAIPricingFAQ
Download
FeaturesSecurityAIPricingFAQ

Legal

Privacy Policy

Last updated - June 9, 2026
Local-first by design

DBPort opens database connections from your device. The backend does not run your database sessions and does not store database credentials in readable form.

1. Scope

This Privacy Policy explains how DBPort handles personal data for the DBPort mobile app, dbport.app, and DBPort backend services. It does not cover the database servers, cloud providers, VPNs, SSH bastions, or other systems you connect to with DBPort.

2. Information we collect

Account and subscription data

We may store your email address, account identifier, sign-in provider identifiers, session records, subscription status, product identifiers, trial state, renewal state, and purchase history needed to unlock DBPort features. Store providers process payments; DBPort does not store payment card numbers.

App and security data

We may store device public keys, device names and platforms, push tokens, AI quota counters, support messages, feedback, cookie choices, and limited request metadata used for security, rate limits, abuse prevention, and service reliability.

Vault and encrypted sync data

Database credentials are stored locally in the app vault and are also a supported sync category. When you enable sync with the credentials category on (the default), they are encrypted on the device before upload, and DBPort backend stores only the encrypted records, record identifiers, timestamps, and sync metadata. Master Passwords, recovery codes, and readable database secrets are never sent to DBPort backend.

AI assistant data

When you use AI features, DBPort sends the prompt, selected dialect, selected model, and the optional editor context you choose to include, such as schema snippets and SQL editor text. Error text or sample rows are sent only if you place them in your prompt. Masking controls are available for literals, emails, tokens, and similar values.

3. What remains local

  • Database sessions are opened by the app, not by DBPort backend.
  • Database passwords, SSH keys, and vault secrets stay on your device in readable form; with sync enabled and the credentials category on, they upload only as end-to-end encrypted records that DBPort backend cannot decrypt.
  • PIN and biometric unlock material remain in platform secure storage.
  • Query results and database rows stay local unless you export, share, send to AI, or send them to support.
  • Query history stays on your device. Connections, snippets, and credentials stay local until you enable sync, after which the categories you keep on leave the device only as end-to-end encrypted records.

4. How we use information

  • Authenticate accounts and protect sessions.
  • Deliver trials, subscription entitlements, restore purchases, and billing state.
  • Sync encrypted records between your devices when you enable sync.
  • Generate AI responses and enforce AI quota when you use AI features.
  • Send service notices such as security, sync, quota, and support messages.
  • Debug crashes, prevent abuse, and keep DBPort reliable.

5. What we do not do

  • We do not sell personal data.
  • We do not use cross-app tracking or advertising cookies.
  • We do not use your prompts, SQL, or database data to train models.
  • We do not store payment card numbers.
  • We do not store database credentials in readable form on DBPort backend.

6. Service providers

We use service providers where needed to operate DBPort, including app stores and payment processors (such as the Apple App Store and Google Play), entitlement providers, sign-in providers, hosted AI providers, diagnostics tools, push notification services, transactional email services, and cloud hosting providers. Subscriptions purchased on Android are billed and processed by Google Play, and on iOS by the Apple App Store; we do not receive or store your full payment card details. They receive only the data needed for their function.

7. Retention and deletion

We keep account and subscription records while your account is active or as needed for legal, billing, security, and abuse-prevention purposes. Account deletion revokes active sessions and schedules backend deletion after a 7-day cool-down. Backups, security logs, and anonymized diagnostics may expire later on their normal schedules.

8. Your choices and rights

  • Access or export supported account and local data from the app where available.
  • Delete your account from Settings or by contacting [email protected].
  • Disable optional analytics, marketing, notifications, and AI context sharing.
  • Revoke sessions and sync devices from account settings where available.
  • Contact us about access, correction, deletion, portability, or objection requests.

9. Cookies, children, changes, and contact

The website uses necessary storage for language, consent, and security preferences. DBPort is not intended for children under 13 or the minimum age in your jurisdiction. We may update this policy as DBPort changes. Privacy questions go to [email protected].

Ready to keep database work close?

Download on theApp StoreGet it onGoogle Play
DBPort

Your databases. In your pocket.
Local-first and AI-assisted, with end-to-end encryption when sync is on.

Product

FeaturesPricingSuggest an idea

Resources

ResourcesMobile Database ClientSecure VaultPostgreSQL on iPadAI SQL Assistant

Legal

PrivacyTermsContactsDelete account
DBPort - made with for developersdbport.app - [email protected]