← Grovely home

Privacy and connections

Grovely does not collect household data, usage telemetry, account identifiers, or installed-version information. Your household data stays on your own server.

Your self-hosted server

Grovely works locally without a cloud account. License verification is offline and makes no external request. By default, Grovely System checks https://grovely.org/releases/stable.json once every 24 hours so Home can show available security and bug-fix releases. That request is public release metadata only: it sends no household, account, license, installed-version, usage, or identifying data. Set UPDATE_CHECK_ENABLED=false in .env to disable automatic checks. Manual Docker updates remain available.

Docker image pulls use GitHub Container Registry. Guided installers and manual installation files are downloaded from GitHub. Optional SMTP notifications and remote S3 or WebDAV backups connect only to services you configure.

The grovely.org website

The landing site records a small set of page and button counters. It does not use advertising, profiles, fingerprinting, or household-app data. Visit /notrack to disable those counters in this browser; /trackon re-enables them. The site loads the Material Design Icons stylesheet from jsDelivr, which may receive normal network request metadata.

The release manifest is served by the site Worker as an untracked cached response. It is not registered as a landing-site page view or analytics event.

Control and transparency

Grovely is open source. You can inspect its application, installer, updater, and release workflow code, run it offline, or update it yourself with Docker Compose. See the source repository and installation guide for details.