Trust and security
Access, public visibility and operational decisions stay separate.
This summary describes controls evidenced in the product today. It does not claim certification, guaranteed security or uptime.
Role and scope boundaries
UrbanTrack separates public reporting, invited portal access, tenant administration and contractor delivery. Server checks validate the current identity, organisation and permitted action for protected work.
Public and Restricted portal access is separate from raw report publication. Automatic safe portal updates do not expose raw operational records.
Tenant and record separation
Organisation context is resolved on the server and protected reads are scoped to the current tenant. Public-safe projections are distinct from raw reports, exact coordinates, private evidence and internal notes.
Restricted records and unavailable references use privacy-neutral responses so public routes do not confirm that a private record or membership exists.
Audit and moderation boundaries
Sensitive operational changes use authenticated permissions and audit history. Publication and evidence review are separate from operational completion and authority acceptance.
Operational analytics is minimised and is not used as a replacement for security logs or audit records.
Operational recovery
The product distinguishes validation errors, access failures, service failures and uncertain submissions so a user is not told that work succeeded when it did not.
Customer-specific continuity, retention and service commitments are defined through procurement and signed agreements rather than this public summary.
Responsible disclosure
Include the affected route, observed behaviour and likely impact. Do not send passwords, live credentials or unnecessary personal data. This route does not promise a response time or payment.