Orvaden Collision

Privacy at roadside.

Orvaden Collision is a local-first digital crash field notebook. Core crash records and photos stay on your device unless you choose to share them or use a connected feature such as VIN decoding.

Effective November 15, 2026

Scope of this notice

This notice explains how the current Orvaden Collision application handles information. It covers local crash records, photos, device permissions, on-device scanning, VIN decoding, optional Face ID app lock, exports, support communications, retention, and deletion.

Information stored in Collision

Collision stores the information you choose to enter or capture for a crash record. Depending on how you use the app, this may include case information, date and time, location text, coordinates, notes, vehicle details, VINs, license plates, insurance information, owner information, driver and passenger details, driver-license information, injury or transport notes, commercial-vehicle information, and reference photos.

No ORVADEN account is required. The current version does not upload your Collision database or crash photos to an ORVADEN backend or cloud database.

Local storage and security

Collision working data is stored locally using encrypted and protected app storage inside the device's private application sandbox. Sensitive storage uses platform security features, including protected local files and secure key storage where appropriate. Optional Face ID app lock uses the device's native biometric system. ORVADEN does not receive or store your Face ID data.

Device security still matters. Keep the operating system, device passcode, and platform account protected. Device-level backup behavior is controlled by the operating system and your device settings, not by an ORVADEN cloud service.

Device permissions

Orvaden Collision requests protected device access only when a related feature needs it:

  • Camera: to scan VINs, license plates, and supported driver's-license barcodes, and to take reference photos.
  • Photos: when you choose to add an existing image from the device photo library.
  • Location: only after you deliberately choose Get Coordinates. Collision does not continuously track your location.
  • Face ID or device authentication: when you enable App Lock.

You can review or change permissions in iOS Settings. Manual entry remains available when a scan or location feature is unavailable.

On-device scanning and Google ML Kit

Collision uses on-device recognition for VIN and license-plate text and for supported driver's-license barcode scanning. Captured image content, recognized text, and driver's-license barcode contents used by these scanning features are processed on the device and are not sent to ORVADEN.

Collision uses Google ML Kit for on-device recognition. Google states that ML Kit input data and results are processed on-device, but the SDK may send limited technical metrics to Google, including device and app information, per-installation identifiers, performance measurements, API configuration, event types, and error codes for diagnostics and usage measurement. See ML Kit Terms & Privacy and Google's Apple data-disclosure guidance.

Scan results must be reviewed before use. Recognition and barcode parsing can be incomplete or incorrect.

VIN decoding through NHTSA

After you confirm a VIN, Collision may send that VIN over an encrypted network connection to the National Highway Traffic Safety Administration's vPIC service to obtain decoded vehicle information such as year, make, and model. A network failure never prevents you from saving the VIN or entering vehicle information manually.

Collision does not send driver's-license barcode contents, crash photos, notes, or the rest of the crash record to NHTSA as part of VIN decoding. NHTSA operates the vPIC service and applies its own online privacy practices, which may include collection of technical request information such as IP address and access time. See the NHTSA vPIC API and NHTSA Privacy Policy.

Photos, exports, and sharing

Photos captured inside Collision remain in app-managed local storage by default and are not automatically uploaded to ORVADEN or written to the Camera Roll. When you choose Share or Export, Collision uses the operating system's sharing tools. The destination app, storage provider, evidence system, email service, or recipient you select controls what happens to the exported copy.

Exporting or sharing a photo or other information does not automatically delete the local Collision copy. Once information is exported or shared, that copy is outside Collision's local protection.

Analytics, advertising, tracking, and sale

Orvaden Collision does not contain advertising or cross-app tracking. ORVADEN does not operate a user-behavior analytics service for Collision and does not sell the crash records, photos, or other working data you store in the app. Limited technical metrics associated with Google ML Kit are described above.

Data retention and deletion

Your Collision records remain on your device until you edit or permanently delete them, reset or remove the app, or the operating system removes app data. Permanent collision deletion removes the local record and associated managed photo files. Copies you previously shared or exported are not deleted automatically.

Because Collision has no ORVADEN account or hosted crash-record database, ORVADEN cannot remotely retrieve or delete records stored only on your device. Before uninstalling or resetting the app, independently preserve any information you are required to retain.

Support communications

If you contact ORVADEN, we receive the information you choose to provide in your message. Do not email driver's-license images, crash records, reference photos containing sensitive information, account numbers, or other personally identifiable information unless it is necessary, you are authorized to share it, and ORVADEN support specifically requests it.

Responsible use

Collision is a field-note tool, not an official crash-report, records-management, evidence-management, or state-submission system. Review the Orvaden Collision Responsible Use notice for additional limitations and user responsibilities.

Changes to this notice

This notice may be updated as Orvaden Collision changes. The effective date at the top identifies the current version. Material changes will be reflected here before or when the related feature becomes available.

Contact

For privacy questions, email privacy@orvaden.com. For product help, visit Orvaden Collision Support or email support@orvaden.com.