Roadscape is designed local-first.
The current analyzer and swept-path tools run in the browser. Optional uploads or cloud processing should be explicit, permissioned, and controlled.
Policy draft
This is a placeholder privacy page until final legal review. Do not treat it as a final policy.
No hidden frontend keys
Roadscape public pages should not expose secret API keys, private tokens, or unattended paid processing. Any cloud processing must be explicit, scoped, and confirmed before use.
No stealth tracking gate
The Swept Path Pro demo timer is browser-local. It does not use hidden pixels, fingerprinting, or IP tracking to lock users out.
Permissioned files only
Private videos, packets, customer files, and engineering materials should be opened only when needed for the requested work.
Temporary access
When a helper, agent, or contractor needs access to important folders, use least-permission access, document why it was granted, and revoke the key or share when the task is complete.
Connector and access promise
Roadscape uses a single Roadscape intake path for service requests. Any connector, helper, contractor, or review access should be scoped, logged, temporary, and revoked when the task is complete.