This policy explains the clear operational and contractual boundary between unverified Self-Serve Developer Sandbox accounts and DPA-backed Production Fleet Legal-Hold accounts, how Write-Once-Read-Many (WORM) dashcam video and telematics preservation works, and how legal-hold suspension and deletion requests are handled. It is a companion to our Privacy Policy and Terms of Service; where they differ, those govern.

1. Unverified Self-Serve Sandbox (/sandbox)

Synthetic Metadata & Hashes Only

  • Who it is for: Instant email-OTP developer trials at api.privinet.net/sandbox with no executed Data Processing Agreement.
  • Accepted payloads: Synthetic or non-regulated operational metadata, timestamps, device IDs, sensor readings, and SHA-256 digests.
  • Intake safeguard: Direct personal identifiers, health/biometric records, and raw video/image uploads are automatically rejected before storage so uncontracted personal data never enters an immutable bucket.
  • Retention: 30-day rolling working sandbox (non-WORM).
2. Production Fleet Legal-Hold Vault (B2B DPA)

Encrypted 3-to-10-Year WORM MP4 + ELD HOS

  • Who it is for: Commercial trucking fleets, MyGeotab operators, dashcam fleets, and telematics insurers/MGAs under an executed PriviNet B2B Data Processing Agreement (DPA).
  • Preserved evidence: Actual raw road-facing and cab-facing dashcam MP4 clips (Lytx Surfsight, Motive, Samsara), live post-crash driver SMS walkaround photos (getUserMedia), and MyGeotab ExecuteMultiCall 1Hz GPS/speed, G-force braking, fault codes, and driver ELD Hours-of-Service (DutyStatusAvailability).
  • Retention: Encrypted 3-year (Standard) or 7-to-10-year (Pro) WORM Object Lock with automatic legal-hold suspension of expiry.

1. Production Fleet Legal-Hold Accounts: WORM MP4 & HOS Preservation

Dashcam SD cards overwrite footage in 30 to 104 driving hours, and standard cloud telematics portals purge video clips in 30 to 90 days while commercial crash claims regularly surface 12 to 24 months later under state statutes of limitations. Storing only a detached hash of a deleted MP4 leaves a fleet unable to play the video for an adjuster or jury.

Under a B2B Data Processing Agreement (DPA) and explicit WORM retention schedule, Production Fleet Legal-Hold accounts preserve the complete evidentiary artifact set:

Access & Tenant Isolation on Production Accounts: Preserved MP4 clips and ELD driver logs remain tenant-isolated. External adjusters, defense counsel, or opposing counsel can view a specific incident only when an authorized fleet administrator or MGA claims handler explicitly issues a scoped, revocable Evidence Room link or exports the court-ready FRE 902(13)/(14) package.

2. Unverified Self-Serve Sandbox Accounts: Intake Safeguards

When a developer provisions an instant trial key on api.privinet.net/sandbox prior to signing a B2B DPA or Business Associate Agreement (BAA), that sandbox account is restricted to synthetic or non-regulated operational metadata only (timestamps, sensor/gateway identifiers, RF packet counters, coarse telemetry, and pre-computed SHA-256 hashes).

Blocked on unverified self-serve sandbox accounts: driver or patient names, dates of birth, license or government identifiers, medical record numbers, biometric templates, and raw embedded MP4, audio, or image binaries. Until a B2B DPA (or HIPAA BAA for healthcare/clinical custody) is executed and the tenant is upgraded to a Production Account, the intake filter refuses those fields and stores nothing.

Because field-name filters inspect structure rather than context, self-serve sandbox terms also prohibit uploading any data describing an identifiable individual, employee monitoring stream, or regulated clinical dataset prior to account review and agreement execution at [email protected].

3. Regulated Healthcare, Pharma & Biometric Deployments

Pharmaceutical 21 CFR Part 11 / EU GDP cold-storage facilities, clinical custody operators, and healthcare deployments are onboarded through our enterprise review workflow rather than anonymous self-serve signup. Contact [email protected] so we can execute the appropriate DPA or BAA and configure your dedicated retention policy before live production feeds are enabled.

4. Deletion, Erasure & Active Legal-Hold Locks

Account administrators may submit deletion or account-closure requests to [email protected]. Every request is logged through tracked states (received, authority verified, deleted where permissible, retained under active WORM lock or legal hold, scheduled for post-lock purge, and completed).

Unlocked sandbox records and administrative account metadata are deleted promptly upon verified request. Where collision ProofPacks, raw dashcam MP4s, or sealed telemetry sit inside a WORM retention-locked archive or an active litigation legal hold, neither PriviNet nor a tenant administrator can silently overwrite or purge those objects before the retention lock or legal hold lifts. We report the exact lock expiration timestamp and schedule automated purge upon release rather than claiming a deletion that WORM storage blocks.

5. Evidentiary Scope & Boundaries

Lumra produces tamper-evident, court-ready electronic records signed synchronously upon arrival in Google Cloud KMS HSM, anchored to dual independent RFC 3161 Timestamp Authorities, and verifiable standalone without contacting PriviNet servers. Exports and automated certificates are designed to support Federal Rules of Evidence 902(13) and 902(14) authentication through a qualified person's written certification. Lumra does not provide legal advice, prevent physical collisions, prove physical sensor accuracy prior to ingestion, or guarantee court admissibility, which always remains a decision for the presiding judge.