Colota - Android GPS Location tracker
docs: update privacy policy for 1.9.0 (mTLS, import, CA trust change)
Max Dietrich1001c987cfc3
diff --git a/apps/docs/src/pages/privacy-policy.md b/apps/docs/src/pages/privacy-policy.mdindex b424a57d..a9922c3a 100644--- a/apps/docs/src/pages/privacy-policy.md+++ b/apps/docs/src/pages/privacy-policy.md@@ -4,7 +4,7 @@ title: Privacy Policy# Privacy Policy-**Last updated: May 20, 2026**+**Last updated: May 25, 2026**Colota ("the App") is a self-hosted GPS tracking application for Android, developed by Max Dietrich. This privacy policy explains what data the App collects, how it is used, and your rights regarding that data.@@ -54,6 +54,16 @@ If you configure auto-export, the App will write export files (CSV, GeoJSON, GPXAuthentication credentials (if configured) are encrypted.+### Importing Data++You can import location history from external files (GeoJSON, Google Timeline, GPX, KML, CSV) into the local database. The file is read from a location you select via the Android document picker. Imported rows are written to the local SQLite database; nothing leaves your device during import. If you opt in to "Import + Queue for Sync", the imported rows are also enqueued for replication to your configured sync backend and follow the same transmission rules as any other location data.++### Client Certificates and Trusted CAs++If you configure mTLS, the client certificate's private key is stored in the Android OS KeyStore (hardware-backed where supported), separate from app-managed storage. PKCS12 passwords are used only during import and are not saved. If you pick a certificate from Android's device certificate list instead, only a reference is stored - the key stays in the OS keystore and never enters the app process.++The Trusted Server CA (used for self-signed or private-CA servers) is the server's public certificate only and contains no private key.+### Encrypted BackupsYou can create a password-encrypted backup containing your location history, geofences, settings and authentication credentials. The password is never stored; if you lose it, the backup cannot be recovered, and a weak password weakens the protection.@@ -68,7 +78,7 @@ The App supports configuration via `colota://setup` deep links. These links canThe App **only transmits data to a server endpoint that you configure**. No data is sent anywhere by default.-- Data is sent via HTTPS (HTTP is only allowed for local/private network addresses). Self-signed TLS certificates are supported by installing your CA certificate on the device via Android system settings+- Data is sent via HTTPS (HTTP is only allowed for local/private network addresses). Self-signed or private-CA TLS certificates are supported by importing the CA in the in-app mTLS Settings (Trusted Server CA). Trust is scoped to Colota; other apps on the device are unaffected- When a server is configured, the App may send health check requests to backend-specific endpoints to verify connectivity. These requests go only to your own server- No analytics, tracking pixels, or advertising networks are used- No data is shared with the developer, advertisers or analytics providers@@ -108,6 +118,7 @@ Since all data is stored locally on your device, you have full control:- **Export**: Export your data at any time in multiple formats- **Delete**: Delete any or all data at any time- **Portability**: Export your data freely, including as a full encrypted backup for device-to-device transfer+- **Import**: Bring location history from other apps or backups via file import (GeoJSON, Google Timeline, GPX, KML, CSV)## Permissions