Offline recording
Vespi is designed to keep working when a registered phone has no network connectivity, without ever inventing or silently merging events.
While offline
Section titled “While offline”After a phone has authorized online at least once, it continues recording offline for a seven-day default window. This is distinct from how long an access token stays valid, how long policy is cached, and how long data is retained on the device — it’s specifically how long the phone will keep accepting new offline actions as verified before treating further activity as unverified pending re-authentication online.
- Actions are persisted in an encrypted, account-scoped queue on the device, protected by a key held in the Android Keystore.
- Each recorded action captures wall-clock time, monotonic device time, a boot identifier, a sequence number, a client-generated event ID, and any evidence that the device’s clock changed — so a review can reconstruct what actually happened on the phone even without trusting its clock alone.
- If local storage fills up, existing queued evidence is preserved, new recording stops, and the app never shows an unsaved action as if it had succeeded.
- A pending (not-yet-synced) shift closing locally does not block starting a new shift.
Signing out or transferring a phone warns about any pending, unsynced evidence first — pending events are never backed up off the device before they sync.
Syncing and review
Section titled “Syncing and review”When the phone reconnects, it uploads queued actions in batches. The server accepts a batch idempotently: resubmitting the same batch returns the original result rather than double-recording it, and batches are retried safely across app or device restarts.
Offline evidence is never silently merged or discarded. Administrators review affected events and sessions individually:
- Overlapping or conflicting evidence is never auto-merged.
- Late-arriving evidence is never discarded automatically.
- The time the server received evidence is never substituted for the time the action actually happened on the phone.
Evidence only becomes part of an employee’s official record once it is explicitly admitted through that review — see official totals for what counts.
Device or key loss
Section titled “Device or key loss”If a phone or its key is lost, synchronized records are preserved and restored from the server once a replacement device is registered (see device replacement). Any time that was never synced before the loss is not reconstructed from guesswork — it’s handled through a correction request with a reason, the same as any other missing time (see Corrections & reporting).