Support
FieldRadar support
Support for the public iPhone and Android releases and controlled pilots is founder-led and provided by email.
Contact
Email support@fieldradar.co.uk. Include the app/browser version, device and operating system, approximate time, the affected workflow and safe reproduction steps. Use project identifiers rather than attaching confidential plans or photos unless a secure route is agreed.
Triage definitions
These labels help us prioritise; they are not response-time promises.
- Critical: suspected unauthorised access, cross-account data exposure, unrecoverable data loss, or all core capture/sync unavailable for the test group.
- High: a core workflow is unavailable or produces materially incomplete output and no safe workaround exists.
- Standard: a partial fault with a workaround, how-to question, usability issue or feature request.
During the coverage window, the internal targets are: acknowledge Critical reports within 30 minutes, High reports the same working day, and Standard reports within two working days. Outside that window, contact is reviewed when coverage resumes unless a separately announced launch watch is active.
Escalation routes
- Suspected vulnerability or data exposure: security reporting.
- Availability or incident report: service status route.
- Account/data removal: account deletion.
- Privacy request: privacy policy and rights.
Before a paid Team service
A paid Team order must name a credentialled deputy, privacy/legal escalation contact and any different contractual support schedule. Until that schedule is specialist-reviewed and attached to an order, no Team support commitment should be quoted.