DB Lens - SQLite & SQL Viewer

1. Information We Process

Depending on how you use DB Lens - SQLite & SQL Viewer, the app may process the following types of information:

2. How We Use Information

We use processed information for the following purposes:

• To open and inspect supported files in read-only mode where applicable.
• To show tables, schema, row details, foreign-key navigation, JSON content, tabular previews, PDFs, text documents, and SQL results inside the app.
• To remember recent files, query history, and database-scoped user state.
• To understand user flow, feature adoption, and points of friction in the app.
• To diagnose crashes, errors, and performance issues.
• To review feature requests and plan product improvements.

3. Local Data Handling

DB Lens - SQLite & SQL Viewer is designed to work locally on your device. When you open a supported database or data file, the app processes that file locally so it can display tables, schema, rows, exports, JSON content, PDFs, text documents, spreadsheets, and read-only SQL results.

To improve usability, the app may copy or cache selected files into app-private storage, and may keep local references such as recent files, query history, and database-scoped state on the device.

Depending on file type, the app may open content in one of several ways: fully local in-app viewing, local conversion into tabular or text form, or a bundled embedded viewer for selected document formats.

4. Encrypted Databases

If you open a supported encrypted database, the app may prompt you to enter a password or encryption key. That credential is intended to be used locally to attempt read-only access to the encrypted file.

• Encryption credentials are not intended to be uploaded to our servers.
• Encrypted databases are intended to remain read-only inside DB Lens - SQLite & SQL Viewer.
• If an encrypted open attempt fails, limited technical error information may be recorded through analytics or crash tools to help diagnose the issue.

5. Firebase Services

DB Lens - SQLite & SQL Viewer may use Google Firebase services, including:

• Firebase Analytics to understand app usage and user flow.
• Firebase Crashlytics to detect crashes, record non-fatal issues, and improve stability.
• Cloud Firestore to store submitted feature requests.

Depending on the Firebase service used, Google may receive technical information such as app instance identifiers, device information, usage signals, crash data, IP-related network information, app version, and operating-system details.

DB Lens - SQLite & SQL Viewer may also create a random app-scoped identifier to help distinguish unique app installations for analytics and stability analysis. This identifier is intended to be app-scoped and does not rely on hardware identifiers such as IMEI, serial number, or phone number.

Firebase-related functionality depends on the build and app configuration that is shipped. Some app distributions may include analytics and crash reporting, while local-only development or custom builds may have reduced or unavailable Firebase features.

6. Analytics Events We May Record

To understand how the app is used, DB Lens - SQLite & SQL Viewer may record events such as:

• first-time user or first app open
• app opened
• screen views for splash, home, overview, table viewer, SQL console, JSON viewer, PDF viewer, document viewer, tabular viewer, and settings
• CTA clicks such as open file, open settings, get started, export actions, history-management actions, and feature-request actions
• database open requested, database opened, database open failed
• file opened and file details viewed, including open mode such as database viewer, JSON viewer, PDF viewer, document viewer, tabular viewer, or embedded document viewer
• encrypted database prompt shown and encrypted database opened
• table opened, table schema viewed, related table opened through foreign-key navigation
• table filter used, table sort used, filters cleared
• SQL suggestions used, past query used, quick query used, SQL query executed, SQL query failed
• row details viewed
• JSON converted into tables, tabular-open choice selection, and PDF/document viewer opens
• database exported and table exported
• query history cleared and recent database history cleared
• feature request submitted

These events are intended to describe app behavior and feature use. They are not intended to include full database contents, complete query result payloads, or entire JSON documents.

7. Feature Requests

When you choose to submit a feature request, the app may store information such as:

• request title and request details
• app version and app identifier
• device manufacturer and model
• Android SDK version
• current database name, if included by the app context
• server-side submission timestamp

8. Data Sharing

We do not sell personal information. We may share limited information only as needed to operate or improve the app, including with:

• Google Firebase for analytics, crash reporting, and feature-request storage
• Apryse/PDFTron components used in-app to render certain Word-document workflows, where applicable to your build
• legal, regulatory, or governmental authorities when required by applicable law

9. Data Retention

• Local recent files and query history: stored on your device until you clear them or uninstall the app.
• Cached imported or copied files: may remain in app-private storage until cleared by the app, replaced, or removed when the app is uninstalled.
• Analytics and crash data: retained according to Firebase service settings and Google retention practices.
• Feature requests: retained as needed for review, planning, support, and product improvement.

10. Security

We take reasonable steps to reduce unnecessary exposure of user data and to keep database viewing local where possible. However, no method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Your Choices

• You can choose whether to open a file in the app.
• You can clear query history and recent file history from Settings.
• You can choose whether to submit feature requests.
• You can stop further app-side collection by uninstalling the app.
• If advertising is added later, additional privacy or consent choices may become available.

12. Children's Privacy

DB Lens - SQLite & SQL Viewer is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through the app, please contact us so that we can review the situation.

13. Changes to This Policy

We may update this Privacy Policy from time to time to reflect app changes, supported file-format changes, SDK or analytics updates, or service improvements. When we make changes, we will update the effective date at the top of this page.

14. Contact

For privacy questions, support, or requests related to this policy, please contact us at: