Orbit privacy policy
Orbit Website Filter (experimental) ยท Updated November 19, 2026
Purpose and operator
Orbit is a family-control tool operated by Pablo Salanova. Its browser extension blocks parent-configured websites and supplies domain-level website usage estimates to the configured Orbit parent dashboard. It requires configuration by a parent or device administrator.
Information the browser extension handles
- Administrator-provided server address and a browser authentication token used to communicate with that server.
- A randomly generated, persistent identifier for each browser installation.
- Approximately once per minute, the active tab's hostname when Chrome is focused and the device is active. A report with no hostname is sent when no eligible active website is detected. The server records receipt times and estimates time spent on each domain.
- The extension reads the active tab URL locally to extract the hostname. It does not transmit full URLs, paths, query strings, or page titles. It does not collect page content, messages, passwords entered on websites, payment details, keystrokes, mouse movements, or clicks.
- Locally stored policy revision, last successful update time, and blocking rules.
Active/idle and browser-focus checks support usage estimates; they do not provide exact screen time. The browser token is an Orbit service credential, not a website password.
Optional Mac components
If the separate Orbit Mac agent and foreground monitor are installed, they also send the Mac hostname, application identifiers, application names, foreground-session times, and operational status to the Orbit server. These components are separate from the Chrome extension.
Optional iPhone app
The experimental iPhone app uses Apple Screen Time authorization and locally selected app tokens. Selection tokens and application names stay on the phone. It sends a generated installation identifier, locally configured policy revision, authorization status, selected app count, and whether a shield is configured to the administrator-configured Orbit server over HTTPS. It does not upload detailed Screen Time usage. Installation status records are retained until removed by the server administrator. Setup uses a single-use, expiring code generated by the parent dashboard. Each enrolled phone receives a separate credential stored in Keychain and a short-lived parent setup session kept only in memory. The dashboard administrator credential is not downloaded. The server stores hashes of setup codes and device/session credentials. Revoking access stops future server requests but does not remove downloaded restrictions.
Use and sharing
Information is used to enforce parent-selected restrictions, produce usage reports, and operate the service. Reports are accessible to anyone holding the parent dashboard's administrator credential. Extension reports are transmitted over HTTPS to the administrator-configured Orbit server; there is no separate advertising or analytics destination in the extension.
Orbit does not sell personal data, use it for advertising, or use it to determine creditworthiness or lending eligibility. The configured hosting provider, reverse proxy, or CDN may process connection metadata, including IP addresses, and may keep access logs. Logging and infrastructure retention depend on the deployment; Orbit does not derive GPS location.
Orbit's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the described family-control functionality.
Storage and retention
Usage records are stored in the configured server's database. Usage-history retention defaults to 90 days and can be changed by the server administrator. Old usage records and browser-session records older than one day are removed when server cleanup runs. Blocking configuration and credentials persist until changed or deleted.
The extension retains its local installation identifier, update metadata, and blocking rules until its storage is cleared or the extension is removed. Managed configuration remains until its management policy is removed. Server backups, infrastructure logs, and downloaded reports have separate retention controlled by the server administrator; removing the extension or uninstalling Orbit does not delete those copies.
Choices, access, and deletion
Contact the parent or administrator who configured your Orbit installation to request access, correction, or deletion of usage information, to change restrictions, or to stop monitoring. Managed installations may require administrator approval for removal. The server administrator must arrange server-side deletion and backup cleanup; the uninstaller does not erase server history.
Children and family use
Orbit is intended to be configured by a parent or authorized administrator. The person configuring it is responsible for informing monitored users about website blocking and usage reporting and obtaining any required permission before enabling monitoring.
Contact and updates
For privacy questions or deletion requests about a particular installation, contact its parent or server administrator directly. For software questions, contact the maintainer through the Orbit project issue tracker. Do not post credentials, children's information, or browsing history in public issues. This policy will be updated when the software's data practices change.