Privacy policy for DockLog apps

1. Overview

DockLog apps are remote clients for a DockLog server you or your team hosts. They are not a hosted logging or monitoring service operated by DockLog.

We do not collect, store, or process your infrastructure data on DockLog-operated servers. Server URLs, login credentials, session tokens, and app preferences are kept on your device unless you remove them or uninstall the app.

One policy covers every distribution channel: App Store, Play Store, Linux packages, direct downloads, and anything else we add later. We do not sell your information or show ads inside the apps.

2. Data the apps store on your device

To work as a client, the apps may store the following locally on your device (for example iOS Keychain, Android Keystore / encrypted preferences, or platform credential storage):

• Server connection details: URLs, ports, hostnames, and optional advanced settings (timeouts, custom HTTP headers, TLS options) that you enter.
• Authentication credentials: Usernames, passwords, access tokens, and refresh tokens for servers you configure. These are used only to authenticate with your DockLog instance.
• App preferences: Theme, refresh intervals, notification filters, and similar settings saved with standard on-device storage.
• Optional app lock: If you enable PIN or biometric unlock, a salted hash of your PIN is stored locally. Biometric verification is handled by your operating system; DockLog does not receive or store biometric data.

The apps do not create a DockLog cloud account. You sign in with credentials for a server you already manage.

3. Data sent over the network

When you use the apps, they connect directly to the DockLog server address you configure. Container logs, metrics, alerts, and API responses travel between your device and that server. There is no DockLog cloud proxy in the middle.

You may connect over HTTPS (recommended) or HTTP (for example on a private LAN). When HTTP is used, data is not encrypted in transit between your device and your server.

On first launch, the apps may download UI fonts from Google Fontswhen network access is available. That request goes to Google's font service, not to DockLog-operated infrastructure.

4. What we do not collect

DockLog apps do not embed analytics, advertising, crash-reporting, or attribution SDKs. We do not receive the following on DockLog-operated servers:

• Container logs, stdout/stderr streams, or workload telemetry
• Host system metrics beyond what your server returns during an active session
• Docker socket data, container names, or infrastructure metadata for profiling or marketing
• Contacts, photos, location, microphone audio, calendar data, or SMS

Platform stores and operating systems (Apple, Google, etc.) may collect diagnostics or crash data according to their policies if you opt in at the OS level. That is separate from DockLog and is not controlled by the apps.

5. Notifications

On mobile platforms, the apps can show local on-device notifications when container events arrive while the app is in the background. Alerts are generated from your live connection to your server; DockLog does not use Firebase Cloud Messaging or other third-party push relays operated by us.

Notification permission is requested when you enable alerts. You can turn notifications off in system settings at any time.

6. Permissions

The apps may request platform permissions only as needed:

• Network access: To reach your DockLog server.
• Notifications (mobile): To display local alerts when enabled.
• Biometrics (optional): To unlock the app when you enable biometric app lock.

7. Data sharing

We do not share, rent, or sell app user data to third parties. Data leaves your device only when the apps communicate with servers you configure or when optional third-party services you indirectly use (such as Google Fonts) are contacted as described above.

We may disclose information only if required by law, such as in response to a valid legal request, or to protect rights and safety where permitted by applicable law.

8. Retention and deletion

Connection settings and saved credentials remain on your device until you delete the corresponding server entry in the app, clear app data, or uninstall the application. You can disable optional app lock and remove stored servers at any time from within the app.

To request help deleting locally stored data or for privacy questions, contact us via the DockLog GitHub repository. How long logs and metrics are retained on your infrastructure is determined by your self-hosted DockLog server, not the apps.

9. Security

We strongly recommend connecting over HTTPS and restricting public exposure where possible. Because the apps can access sensitive operational data, you are responsible for securing your server, rotating credentials, and enforcing access controls on your DockLog deployment.

Credentials are stored using platform secure storage when available. On some desktop debug builds, the OS may not provide keychain access; the app may fall back to encrypted local preferences so development remains possible.

10. Children's privacy

DockLog apps are built for developers, operators, and IT professionals managing self-hosted infrastructure. They are intended for users 18 and over, are not designed for children, and we do not knowingly collect personal information from children.

11. Your rights

Depending on your location, you may have rights to access, correct, or delete personal data associated with your use of the apps. Because operational data lives on your self-hosted server, requests about container logs or audit records should be directed to your organization's administrator.

12. Changes to this policy

We may update this privacy policy as the apps evolve or as legal requirements change. Material updates will be reflected on this page with a revised "Last updated" date. Continued use of any DockLog app after changes constitutes acceptance of the updated policy.

13. Contact

Questions about this app privacy policy can be submitted via the DockLog GitHub repository. For the self-hosted DockLog server itself, see our website privacy policy. For app documentation, visit /app/docs.