Sigelith Courier

Proof of handover confirmed by the recipient’s key and completed by a public stamp. At the door the recipient confirms on their own phone — not with a squiggle on a stranger’s screen — and the moment is recorded in the public Sigelith log.

1. The shop prints a code — Its plugin puts a signed code on the packing slip and a link in the shipping e-mail. The code carries no name and no address.
2. The courier scans it at the door — Sigelith Courier checks the shop’s signature and opens a short session, passed to the recipient by NFC (phones held together), Bluetooth or a QR code.
3. The recipient confirms — On their own phone, with the link from the shop and a fingerprint, face or screen lock. The courier’s code is valid for two minutes; when it runs out, the courier simply shows a new one.
4. Both are stamped — The courier’s app countersigns, stamps the confirmation and its own record in the public log — only hashes, queued while offline — and sends the evidence to the shop.

With a pickup code
Shops can choose a pickup code instead of the recipient’s signature. The shop e-mails the buyer a code; at the door the courier scans it from the recipient’s screen or a printout, types it or takes a photo of it — or receives it from the recipient’s app over NFC or Bluetooth. Sigelith Courier checks the code against the label, signs the record and stamps it. The recipient needs no app and no passkey — only the e-mail.

For couriers — Sigelith Courier
• Pickup code: reads the recipient’s QR code or the characters on a screen or paper, takes the code typed, or receives it from the recipient’s app over NFC and Bluetooth.
• The courier’s key stays in the phone’s secure key store; a fingerprint unlocks it for every parcel or for 5 to 60 minutes.
• Works without internet: stamps wait in a queue and go out when the phone is back online.
• Keeps every record and exports a period as one file for the employer or a shop.

When the recipient does not confirm
• Handed over without confirmation — Left with a neighbour or another person, or handed to a recipient who has no phone, no link or no internet at hand, or who does not want to confirm on a phone.
• Not handed over — A delivery attempt: nobody home, the parcel refused, or a wrong address.

What the proof shows — and what it does not
It shows:
• that the shop issued the code for this parcel;
• that whoever held the link from the shop confirmed it — after the courier’s session started, over the channel the evidence names (NFC, Bluetooth or QR);
• that the confirmation and the courier’s record existed no later than their public stamps;
• with a pickup code: that the courier’s phone held the code the shop sent only to the buyer, no later than the stamp;
• that the courier’s key countersigned the confirmation.
It does not show:
• who the person was — only control of the link and of a phone;
• what was in the parcel or what state it was in;
• where it happened — a location in a record is the courier’s claim;
• with a pickup code: that the recipient was at the door — a code can be photographed or passed on;
• legal delivery under any law.

For shops and carriers
Shop plugins are being prepared, WooCommerce first. A plugin prints the codes, puts the link in the shipping e-mail, receives and checks the evidence, and marks the order “handed over — confirmed by the recipient”. It works with any carrier, because the code travels on the parcel. Carriers can build the protocol into their own apps.

Privacy
Only proofs pass through Sigelith: its servers receive 32-byte hashes to stamp — never names, addresses, codes, confirmations, records or photos. The link from the shop travels in the part of the address that browsers never send to a server. The courier’s location is optional and off by default; photos and the location go only to the shop. Codes are recognised on the phone by Google ML Kit, which sends Google technical data about its operation.