DATA BOUNDARIES

Your fleet evidence.
Your private workspace.

The read-only scanner collects structured Java inventory. New dashboard scripts include hostnames and full runtime paths by default; you can turn off either setting before creating a campaign.

What is reported

Reports contain device and campaign identifiers, platform, observation time, runtime versions, distributor and product metadata, version assessment, coverage, and coded errors. Hostnames and runtime paths follow each campaign’s privacy settings. Runtime identifiers are salted hashes of local paths. Reports do not include raw logs, environment variables, application source, or authentication credentials. Reporting requests use a scoped device credential.

Who can access it

Verified email accounts access private organizations through owner, operator, or viewer roles. Owners can grant access by adding an email address without sending an invitation link; the recipient still verifies that address with a sign-in code. Enrollment and device credentials only allow their designated reporting operations; they do not grant dashboard access. Your RMM controls endpoint execution. The service has no remote command channel.

Retention and deletion

Reports · 30 days
Report history and current report projections expire. Missing or expired evidence is not a clean finding.
Inactive inventory · 90 days
Inactive device inventory expires and its reporting access is revoked.
Audit events · 90 days
Minimal administrative events support accountability.
Backups and deletion journal
Production backup retention and deletion reconciliation require separate infrastructure configuration and verification.

Owners can delete an organization; authorized operators can delete campaigns and devices. Access is revoked immediately.

Infrastructure and local state

Railway hosts the application and private data services. SMTP2GO delivers sign-in codes. No analytics or third-party fonts are loaded. Infrastructure providers may retain operational access logs under their own policies.

Downloaded reporting scripts contain a scoped enrollment token until it expires or is revoked. New tokens are encrypted at rest and can be revealed later by authorized operators without a separate confirmation prompt. Enrollment defaults to 30 days and can be shortened. Reporting scripts store device credentials and up to 10 pending reports or 2 MiB locally with restricted permissions. If upload fails, the script prints its JSON result to the local console and queues the report for retry. Dashboard scripts return process exit code 0 by default for RMM compatibility; operators can disable this in the builder. The JSON result and delivery message still identify findings and failures. A device offline beyond its 90-day credential lifetime needs re-enrollment; preserve queued reports as local evidence before clearing state.

Evidence has limits

Reports are self-reported inventory, not remote attestation. A compromised or misconfigured endpoint can send inaccurate information. Treat results alongside vendor evidence and your existing inventory.