DATA BOUNDARIES
Your fleet evidence.
Your private workspace.
The scanner collects structured PHP inventory and action outcomes. Hostnames and full paths are opt-in. Review your organization’s requirements before deployment.
What is reported
Reports contain device and campaign identifiers, platform, observation time, discovered runtime versions, package evidence, coverage, action outcomes, and coded errors. Hostname and runtime path fields are included only when selected. Scripts do not upload raw logs, configuration file contents, environment variables, application source, or credentials.
Who can access it
Verified accounts access private organizations through owner, operator, or viewer roles. Enrollment and device credentials only allow their designated reporting operations; they do not grant dashboard access. Your RMM continues to control endpoint execution. The service does not provide a 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
- The deployment target is 30-day backup retention with a minimal 37-day deletion journal to prevent deleted data returning after restoration. The service operator must configure and verify these controls before launch.
Owners can delete an organization; authorized operators can delete campaigns and devices. Access is revoked immediately. Backup copies age out under the operator’s configured retention policy, and restoration must reconcile deletions before reopening access.
Infrastructure and local state
Railway hosts the application and private data services. SMTP2GO delivers account and invitation email. No analytics or third-party fonts are loaded. Infrastructure providers may retain operational access logs under their own policies; account email addresses are used for authentication and notifications.
Endpoint state stores device credentials locally with restricted permissions. Temporary offline reports are bounded to ten reports, 2 MiB, and seven days. Configuration backups are retained for recovery; their cleanup depends on verified activation and may require manual review.
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, operational checks, and your existing inventory.