Privacy Policy

1. Scope

This Privacy Policy explains how OpenObserve Mobile handles information when you use the read-only mobile client to connect to an OpenObserve instance.

The operator of the OpenObserve instance you connect to remains responsible for the telemetry stored on that instance. Logs, traces, metrics, dashboards and alerts may contain personal information controlled by that operator or your organization.

2. Information Stored on Your Device

The app stores information required to remember your local setup:

• Connection profile details, including profile name, server URL, organization, username and authentication method.
• Your password, service-account token or API key in the platform secure storage, such as iOS Keychain or Android Keystore.
• Local preferences such as theme, language, refresh interval, selected streams, time ranges, watched streams, dashboard favorites and recent log view state.
• Consent information maintained by Google User Messaging Platform when the advertising integration is enabled.

Profile secrets are not included in the profile metadata file. Signing out does not delete saved profiles. You can remove profiles and their local secrets through Manage profiles.

Secure-storage behavior after app removal may vary by platform.

3. Information Received from OpenObserve

When you use a live connection, the app sends read-only requests to the OpenObserve server and organization selected in your profile.

Responses may contain logs, traces, metrics, dashboards, streams, alert rules and alert history. This data is used to display the requested screens and is not uploaded to an app-owned backend.

Search terms, SQL queries, trace IDs and filters are sent to the configured OpenObserve instance to retrieve the requested results.

The demo workspace uses bundled sample data and does not connect to a real OpenObserve instance.

4. Authentication and Security

The app authenticates to OpenObserve using the credentials entered for a connection profile. Requests use HTTP Basic Authentication over the configured server connection.

HTTPS certificate validation remains enabled by default. HTTP connections are allowed only after you acknowledge the warning for that profile.

Keep your device, operating system and OpenObserve instance secured. Revoke credentials at the OpenObserve instance when they are no longer needed.

5. Advertising and Privacy Choices

The app includes Google Mobile Ads and Google User Messaging Platform libraries. No production advertising placement is currently active.

Debug builds may use Google's sample App IDs to test the consent flow. Release builds keep the advertising integration disabled until valid production App IDs and privacy messages are configured.

If the advertising integration is enabled, Google may process information such as:

• Device IP address
• Product and app interactions
• Diagnostic and performance information
• Device or account identifiers

This information may be used for advertising, analytics, measurement and fraud prevention according to Google's policies.

Google User Messaging Platform checks consent information and may display a consent form when required. Available privacy choices can be reopened from the app's Settings page.

For more information, see Google's Privacy Policy .

6. Purchases

The project includes Google Play Billing and Apple StoreKit libraries for a possible future purchase flow.

The current app does not expose products, purchase buttons, transactions, entitlements, receipt validation or restore flows. Purchase data is not currently processed by the app.

If purchases are introduced later, Google Play or Apple may process transactions according to their respective terms and privacy policies. This Privacy Policy will be updated before the feature is released.

7. Sharing and Retention

The app shares connection requests and the credentials required for authentication with the OpenObserve endpoint configured by you.

The app does not sell your information and does not operate its own analytics or telemetry service.

Data stored on your OpenObserve server follows the retention rules of that server and your organization.

Removing a connection profile deletes its local metadata and saved secret. It does not delete data from the OpenObserve instance.

Local preferences remain until removed, cleared through device settings or otherwise deleted. In-memory results and detail views are released when the related view or app is closed.

8. Your Choices and Rights

You can remove saved profiles, change local preferences and clear app data through your device settings.

You can revisit available advertising consent choices from the application's Settings page.

Depending on your location, you may have rights to access, correct, delete, restrict or object to the processing of personal information.

Requests concerning information handled directly by the app should be sent to the publisher using the privacy contact below.

Requests concerning telemetry stored in an OpenObserve instance should be sent to the instance operator or your organization.

9. Children

OpenObserve Mobile is an operational monitoring tool and is not directed to children.

Do not use the app to collect information from children. If advertising is enabled, the publisher must configure the applicable age and consent settings before release.

10. Changes to This Policy

This Privacy Policy may be updated when the app adds a new data source, SDK or privacy-relevant feature.

The date at the top of this page identifies the most recent update.

11. Privacy Contact

A dedicated privacy contact address will be published with the production app listing before release.

Until then, use the support contact provided by the publisher of the OpenObserve Mobile app for privacy questions or requests.