Data policy

Separate observed data from assumptions.

Roadscape reports should keep cited facts, user-provided footage, estimates, and field-measurement needs visually separate.

Local footage

Use permissioned video and retain the source context.

Assumptions

Label estimates clearly and keep them editable.

Review

Official outputs require qualified review and jurisdiction-specific standards.

Access control

Important folders use temporary, revocable access.

Roadscape work can involve videos, draft packets, maps, customer material, and professional review notes. Those folders should be shared only when the job requires it.

Least permission

Give read-only or task-limited access whenever possible. Do not hand out broad folder access just because one file is needed.

Dual-control for high-value files

For important folders, use owner approval plus a second reviewer or logged agent note before access is granted.

Auto-expire and rotate

Use temporary keys or share links with an expiration timer where the platform supports it. Rotate service keys on a schedule, revoke task keys when done, and avoid permanent agent access unless it is documented and necessary.

Revoke when done

When the work is finished, remove the share, revoke the temporary key, and record that access was closed.

Connectors

One intake door, simple handshakes, revocable access.

New integrations, helper access, uploads, and contractor review should start from one Roadscape service request, not scattered private links.

One intake door

Use the pricing contact form or approved service channel to start a job. Do not collect customer material through random DMs or unmanaged links.

Simple handshake

Before access is granted, record who needs it, what folder or file is needed, why it is needed, and when it expires.

Revoke by default

When a report, upload, or review is complete, remove temporary shares and revoke task-specific keys. Permanent access should be rare and documented.