Why FN CrashGuard+ asks you to complete a Private Profile before relying on incident reports or exports, and what to check before a journey.
FN CrashGuard+ is designed to help keep an incident record structured, but the quality of the record still depends on safe use, accurate information and careful review. The practical steps below are intended to make that process clearer.
Reports need an identified source
A useful incident report should make clear whose record it is. Your Private Profile provides the personal details CrashGuard+ uses when creating reports and exports.
Complete it before you need it
The roadside is the wrong time to discover that basic profile information is missing. Complete the profile during setup and review it whenever important details change.
Check accuracy, not just completeness
A filled field is not useful if the information is out of date. Check names, contact information and other report details carefully.
Keep private information private
Profile information is sensitive. Only include information the app actually needs and protect access to your device.
Review every export
Generated reports should still be checked before sharing. Confirm that profile details, incident dates and vehicle information are correct.
Update after significant changes
If your contact details or other relevant information changes, update the profile before your next report is needed.
Do not confuse profile data with evidence
Your profile identifies the person creating the record. It does not prove how an incident happened or establish liability.
Practical checklist
Quick checklist
- Keep the record factual
- Preserve original evidence
- Separate observation from assumption
- Keep related information together
- Review details before sharing