Last updated: 08.06.2026
This is a hobby/self-hostable project.
This application does not use accounts, analytics, ads, tracking, profiling, newsletters, or cookies.
Location data
Location sharing is end-to-end encrypted.
The server only relays encrypted data between clients. The server never receives the encryption key and cannot decrypt or inspect plaintext location data.
Location data is not saved to a database or persistent storage. Connection metadata may exist briefly in memory while the service is running.
Logs
The server, reverse proxy, hosting provider, Apache2, or similar infrastructure may create access logs.
These logs may include IP address, request time, requested URL, HTTP status code, user agent, referrer, and similar technical request data.
Log retention depends on server configuration. Logs may be rotated, deleted, or stored indefinitely. If no deletion or rotation is configured, logs may remain until manually removed.
The application may also print runtime logs to the terminal, stdout, stderr, systemd journal, Docker logs, screen/tmux, or another process manager.
By default, info-level logging is used. Debug logging may be enabled by configuration.
Runtime debug logs may include timestamps, ephemeral connection IDs, ephemeral share IDs or keys, internal status messages, viewer counts, errors, and connection/disconnection events.
Runtime logs do not contain plaintext location data. Logged share IDs, keys, or URLs may allow access to an encrypted live stream, but decrypting that stream requires the client-side encryption key, which is not sent to the server.
Why data is processed
Data is processed only to provide the service, relay encrypted live updates, debug problems, prevent abuse, and keep the service secure.
Sharing
Data collection is minimized as much as technically practical.
Data is not sold, rented, or shared for marketing.
Data may be processed by the server operator, hosting provider, reverse proxy, logging system, or other infrastructure used to run this instance.
Self-hosted instances
This software can be self-hosted. Each instance is controlled by its own operator.
The operator of each instance is responsible for its own logging, retention, security, hosting, and legal compliance.
Contact
For this instance, contact: loading from server...