Question 1

We already have logs. Why isn't that enough?

Accepted Answer

Because anyone with admin access can edit them, and that's why adjusters and opposing counsel discount them. Lumra records are sealed the instant they arrive and chained; altering one breaks verification.

Question 2

Why can't our IT team just hash and sign our own logs?

Accepted Answer

They can, and it will read as self-audited paperwork the day it matters: when your company controls the database, the keys, and the script, there is no good answer to "could the hashing have been re-run after an edit?" Lumra provides the separation of duties: records sealed the instant they arrive, signed at the source where the device supports it, chained outside your administrative reach, and verifiable by the other side with open tools that never contact PriviNet.

Question 3

Why isn't a WORM bucket (S3 Object Lock) enough?

Accepted Answer

Object Lock protects retained objects from later change. Lumra adds signed records, explicit receipt ordering, package manifests, and a verifier another party can run without access to your cloud account. When an RFC 3161 token is present, the verifier checks what digest it covers and reports its timing scope. Neither control proves that a source event was true or that every expected event was captured.

Question 4

What does Lumra cost?

Accepted Answer

Lumra offers two continuous sealing tiers: (a) Utility & IoT Sensor Metering Tier (Mioty / LoRaWAN) at $0.10 per active sensor/month ($25/month minimum, dropping to $0.08 at 500+ and $0.06 at 2,000+ sensors), and (b) Lumra Seal Fleet, Pharma & Telematics Tier (MyGeotab / Enterprise Fleets / Cold-Chain) starting at $199/month ($169/mo billed annually) plus $1.00/asset/month for standard monitored assets (trucks, trailers, reefers, doors, gateways) and $4.00/asset/month for cameras or high-liability pharma biologics assets. Self-serve raw JSON verification via verify_proofpack.py is $0. Assembled Court & Adjuster ProofPacks are paid only when an incident happens ($450 Standard ProofPack, $1,200 Priority Same-Day, $2,400 Multi-Source Incident Pack).

Question 5

Do you see our video or audio?

Accepted Answer

No. Lumra works from compact signed metadata. Raw media stays yours; it can only be recalled under an audited, logged process. We can't leak footage we never receive.

Question 6

What if PriviNet disappears?

Accepted Answer

Your records outlive us. The verifier is a standalone open tool that never phones home; anyone can re-check any record for as long as they keep it, with no PriviNet server involved. Proof that requires trusting the vendor isn't proof.

Question 7

Is this blockchain?

Accepted Answer

No tokens, no mining, no consensus fees. Just the boring, court-tested cryptography (ECDSA and Ed25519 signatures, SHA-256 hash chains) that federal evidence rules already recognize.

Question 8

How do MyGeotab, Samsara, Motive, and Lytx Surfsight dashcam videos hold up as evidence?

Accepted Answer

Dashcam footage holds up when you can prove nobody edited it after the fact. Your video or telematics platform (MyGeotab GetFeed SDK, Samsara, Motive, or Lytx Surfsight) hashes each MP4 segment; Lumra seals those SHA-256 hashes and GPS kinematics the moment they arrive into a tamper-evident chain without uploading raw video. Under Federal Rules of Evidence 902(13) and 902(14), hash-verified records like these can self-authenticate through a qualified person's written certification rather than live testimony.

Question 9

How does Lumra support 21 CFR Part 11 and EU GDP pharmaceutical and biologics cold-chain compliance?

Accepted Answer

Lumra seals cold-room, lab freezer, clinical trial batch, and reefer telemetry across Sensitech, ELPRO, Emerson, Controlant, and carrier sensors at receipt, chaining excursion alerts, QA notifications, and operator acknowledgments into a tamper-evident audit trail with Cloud HSM ECDSA P-256 signatures and dual RFC 3161 timestamps.

Question 10

How does Lumra work with Mioty (ETSI TS 103 357), Smart Meter Light (SML), and LoRaWAN / The Things Stack?

Accepted Answer

Lumra connects downstream over HTTPS (/v1/ingest/mioty and /v1/ingest/raw) to Mioty Service Centers (mSC), Base Station Controllers (BSC), Fraunhofer IIS stacks, Diehl Metering (IZAR, Hydrus, Sharky), Smart Meter Light (SML) OBIS tariff registers, LORIOT, Netmore, ChirpStack, and The Things Stack (TTN) at $0.10/sensor/month ($25/mo min) with zero over-the-air radio byte overhead, 10-year battery preservation, and automatic multi-base-station deduplication on (ep_eui, pkt_cnt, data).

Question 11

What is a tamper-evident audit log?

Accepted Answer

A tamper-evident audit log is a record of alerts, notifications, and responses that cannot be edited after the fact without detection. Lumra signs each event the instant it arrives, such as a geofence exit or a staff acknowledgment, and chains it to the previous record. If an entry is altered or inserted later, verification fails. Opposing experts can check the timeline themselves with a free standalone verifier.

Question 12

How do I prove when an alert fired and who responded?

Accepted Answer

Lumra signs the alert and every response event, such as a cold-chain freezer excursion, a QA notification, and an operator acknowledgment, at the instant each arrives, then hash-chains them into an ordered timeline no one can backdate or reorder. When a response time is later disputed, an insurer, quality auditor, or opposing counsel verifies the sequence independently with a free standalone tool. This is the timeline that decides pharmaceutical cold-chain, utility, and guard-response cases.

Question 13

Can GPS, sensor, camera, or access-control data be used as evidence in court?

Accepted Answer

It can, if you can show it was not altered after the fact, which is the objection that gets operational data discounted. Lumra signs those events at intake, and at the source where the device supports it, hash-chains them, and exports a ProofPack built to the U.S. FRE 902(13) and 902(14) standard, where hash-verified records can self-authenticate through a qualified person's written certification. Self-authentication is not automatic admissibility and other objections still apply, but the records answer the tampering question directly and anyone can verify them independently.

Question 14

How do you prove chain of custody for cargo?

Accepted Answer

Chain of custody is proven by signed records at each handoff. Lumra seals gate-in, yard moves, seal checks, and gate-out events the moment they arrive, verifies the device's own signature where source keys are enrolled, then chains the records so any rewrite is detectable. When a container arrives damaged, an adjuster who trusts no party can verify each record independently and narrow the loss to a specific custody window instead of relying on competing paperwork.

Question 15

What is a cryptographically verifiable event record?

Accepted Answer

A cryptographically verifiable event record is an event that is digitally signed where it happens when the device supports signing, or sealed on arrival when it does not, and linked by hash to the record before it. The signature proves which enrolled device or person created it, or that Lumra sealed it on arrival, and the hash chain proves nothing was altered, inserted, or deleted afterward. Verification requires only the exported records and open cryptographic checks, not access to the vendor's systems.

Question 16

How is this different from evidence vaults, photo apps, or free timestamping?

Accepted Answer

Different job. Evidence-management platforms are vaults: you upload media and trust whoever runs the vault. Photo-verification apps authenticate media captured through their own camera flow, and nothing outside it. Free timestamping proves a hash existed by a certain time, with no event, no custody, no paperwork. Lumra signs the operational events themselves, from the systems you already run, never takes your media, and hands you records anyone can verify plus the certification template to use them. And unlike most of the category, the pricing is on this page.

Question 17

What stops PriviNet itself from rewriting history?

Accepted Answer

The exported package is checked outside PriviNet: the standalone verifier recomputes protected content, checks package structure and trust, and fails if protected content changed. Production signing uses a non-extractable cloud HSM key. External timestamp evidence is reported separately and proves only what digest existed by the token time.

Question 18

What is a ProofPack, and is verification free?

Accepted Answer

Verifying a supported ProofPack is free and needs no PriviNet server. A ProofPack is a portable evidence package containing signed records, package metadata, verification instructions, and, where applicable, timestamp and certification material. It can support an evidence workflow, but it is not itself a legal conclusion or guarantee of admissibility.

The Tamper-Proof Black Box for Fleet Dashcams, Pharma Logistics, and Industrial Sensors.

Select the View Built for Your Role

For Executives, Fleet, Pharma & Insurance Leaders

For CTOs, Engineers & Security Auditors

When a six-figure claim lands, ordinary logs get discounted because your own team can edit them.

Your Fleets, Pharma Monitors & Sensors Run Normally

Events Seal on Arrival

Anyone Can Verify Offline

The portal your team logs into.

Predictable for fleets and pharma cold-chain. Metered for utilities. Self-serve JSON exports are included in every plan.