Redis Explorer - Privacy Policy

Overview

Redis Explorer is designed with privacy as the foundation. This Privacy Policy explains how we handle your information when you use our Redis database management application available on Android. Our core principle is simple: your data stays on your device.

Platform: Android (Google Play Store) Minimum Android Version: 11.0 (API level 30) or higher

1. Information We Collect

1.1 Local Data Only

Redis Explorer is designed with privacy as the foundation. All your Redis connections, commands, templates, and history are stored locally on your device using encrypted database storage.

1.2 No Personal Information Collected

We do not collect, store, or transmit any of your personal information, connection details, Redis commands, or Redis data to our servers. Anonymous, non-personal usage metadata is collected via Firebase Analytics as described in §1.4 below.

1.3 Analytics and Crash Reporting

Redis Explorer uses Firebase Analytics (by Google) to collect anonymous, aggregated usage data. This helps us understand which features are most useful and improve the overall app experience. Firebase Crashlytics collects crash reports in production builds to help diagnose and fix stability issues.

No Redis data, credentials, or personal information is ever included in these reports.

1.3.1 Crash Reporting — Firebase Crashlytics

Firebase Crashlytics is integrated into Redis Explorer to collect crash diagnostics in production builds only. Crashlytics is disabled in development and debug builds.

Crashlytics collects:

• ✅ Stack traces from app crashes and non-fatal errors
• ✅ OS version and device model at time of crash
• ✅ Available memory at time of crash
• ✅ App version

Crashlytics does NOT collect:

• ❌ Redis connection credentials or passwords
• ❌ Redis commands you execute
• ❌ Pub/Sub messages or channel subscriptions
• ❌ Your Redis data, keys, or values
• ❌ Personal information

1.4 What We Collect and Don't Collect

Anonymous usage metadata collected via Firebase Analytics:

• Screen names visited (e.g., "key_browser", "connection_manager")
• Feature interaction counts (e.g., key type: STRING/HASH, operation success/failure)
• App version, OS version, and device model (anonymous, non-personal)
• Pseudonymous app installation identifier (resets on reinstall; not linked to advertising profiles)

Crash diagnostics collected via Firebase Crashlytics (production builds only):

• Stack traces from app crashes
• Device model, OS version, available memory at time of crash

What we NEVER collect:

• ❌ Advertising identifiers (GAID) — explicitly disabled in the app
• ❌ Redis connection credentials, hostnames, IPs, or ports
• ❌ Commands executed in the CLI terminal
• ❌ Pub/Sub messages, content, or channel names
• ❌ Redis key names or values
• ❌ Location data
• ❌ Contact information
• ❌ Personal information of any kind

1.5 What We DO Collect

• ✅ Anonymous usage metadata (via Firebase Analytics — screen visits, feature interactions, app/device version)
• ✅ Crash diagnostics (via Firebase Crashlytics — stack traces, device model, OS version; production only)
• ✅ Your own Redis credentials (stored locally and encrypted on your device only — never transmitted to our servers)

2. How We Use Information

2.1 Local Processing

All connection management, command execution, and data organization occur entirely on your device.

2.2 No Server Communication for Redis Data

Redis Explorer does not transmit your Redis data, credentials, commands, or any personal information to our servers or any third party. All Redis management functionality communicates exclusively between your device and your own Redis servers.

The only analytics/crash third-party communication is anonymous, non-personal data sent to Firebase (Google LLC), as described in §1.3. Google Play Services are also used for in-app purchases and app updates (see §4.2). No Redis data is ever included in any third-party communication.

2.3 Direct Connection Flow

The only external communication occurs when you establish a connection to your own Redis server:

1. Input: You provide connection details (host, port, password)
2. Storage: Credentials are encrypted and stored locally
3. Connection: App connects directly to your Redis server
4. Commands: All commands are executed on your Redis server only
5. Results: Results are returned directly to your device
6. No Intermediary: Data does NOT pass through our servers

3. Data Storage and Security

3.1 Local Encryption

• Android Keystore: All sensitive credentials are encrypted using Android Keystore with AES-256 encryption
• Device Storage: Encrypted data is stored in the device's internal storage
• Database Encryption: Room database supports encrypted storage for additional protection

3.2 SSH Tunnel Security

SSH tunnel credentials are encrypted and stored locally using the same Android Keystore encryption.

3.3 Network Security

The app enforces secure network communications:

• TLS/SSL support for Redis connections
• Certificate verification enabled by default
• SSH tunnels for additional security layers
• No cleartext traffic for sensitive data

3.4 No Cloud Backup

Your connection details and command history are not backed up to cloud services. They remain only on your device.

4. Third-Party Services

4.1 Firebase (Google LLC)

Redis Explorer uses Firebase Analytics and Firebase Crashlytics, services provided by Google LLC, for anonymous usage analytics and crash reporting. Firebase processes data in accordance with Google's Privacy Policy.

Advertising identifier (GAID) collection and ad personalisation signals are explicitly disabled in the app. No data is used for advertising purposes.

No other third-party data collection or analytics services are used.

4.2 Google Play Services

The App uses Google Play Services for:

• In-app purchases (if available)
• App updates

These services do not collect your connection data or usage information.

5. Your Rights and Choices

5.1 Data Access

You have full access to all data stored in Redis Explorer:

• All connection configurations
• All command history
• All message templates
• All database and key information

5.2 Data Deletion

You can delete your data at any time:

• Delete individual connections
• Clear command history
• Delete message templates
• Uninstall the app to remove all local data

5.3 GDPR Compliance

Redis Explorer is designed to minimize data collection. We comply with GDPR principles:

• Data Minimization: We collect only the minimum data needed — anonymous usage metadata and crash diagnostics. This includes pseudonymous identifiers (device model, OS version, app instance ID) that may be considered personal data under GDPR but contain no directly identifying information (e.g., no name, email, or location)
• Purpose Limitation: Analytics data is used solely to improve app stability and features
• Storage Limitation: Anonymous analytics data is retained by Firebase per Google's data retention policy; your Redis data stays on your device
• Right to Erasure: Delete any local app data within the app anytime; uninstalling removes all on-device data

5.4 Data Portability

You can export your connections and templates to compatible formats through manual documentation.

6. Children's Privacy

Redis Explorer is designed for professional database administrators and developers, not children. However, if you are under 13 years old, please do not use this application. We do not knowingly collect information from children under 13.

7. Security Considerations

7.1 Device Security

Your device security is crucial. To protect your Redis credentials:

• Use a device lock (PIN, password, or biometric)
• Keep your Android device updated
• Install apps only from trusted sources

7.2 Redis Server Security

You remain responsible for:

• Your Redis server security configuration
• Network security for your Redis instances
• Access control and authentication
• Password strength for Redis instances

7.3 SSH Tunnel Security

If using SSH tunnels, ensure your SSH server is:

• Properly configured and maintained
• Updated with security patches
• Protected with strong authentication

8. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be effective when posted to the App. Your continued use of Redis Explorer constitutes acceptance of our updated Privacy Policy.

9. Contact Us

If you have questions or concerns about this Privacy Policy, please contact us at:

Developer: Binod Kumar Swain
Email: me@binodswain.dev

This Privacy Policy is designed to be transparent, comprehensive, and compliant with global privacy regulations while reflecting Redis Explorer's privacy-first design philosophy. Your privacy is not just a policy for us—it's built into the very architecture of our application.

Last Updated: April 22, 2026