1. Create a package
No package created yet.
Controlled Handover Centre
Prepare, verify and move authorised packages.
QR code, controlled file export/import, delayed sharing, Bluetooth and NFC are presented according to actual browser capability. Unsupported devices receive immediate fallbacks instead of pretend success.
2. Package metadata
Package ID, roles, timestamps, schema, record count, checksum, transfer state and audit reference will appear here.
3. Functional QR handover
Create a package to generate QR data.
The system uses multiple QR parts when the payload is too large for one practical code.
Manual QR fallback
Paste scanned parts one at a time. This also allows two browser sessions to test the transfer without camera support.
0 QR parts collected.
4. Controlled file import
Choose a SafeSpark JSON package.
5. Device-to-device routes
Capability status will appear above. A compatible SafeSpark GATT service is required for Bluetooth transfer.
6. WhatsApp and Web Share
SafeSpark™ can prepare or queue an authorised handover package while offline. The package can then be shared through WhatsApp when mobile data or internet connectivity becomes available.
7. Delayed synchronisation queue
8. Handover audit log
Production boundary: File and QR transfer are working local MVP functions. Bluetooth and NFC are functional capability-detected prototypes that require compatible supported hardware and further production security/device testing. No universal browser support is claimed.