Capabilities
Everything the tag does after you print it.
Docfense is a small piece of printed paper and a large amount of machinery behind it. This is the machinery.
Binding and validation
Document binding
Enter the number once and it is locked to your tag permanently. Every entry is normalised first, so spacing and case can never create a false mismatch.
Duplicate prevention
A number that is already protected cannot be bound a second time. This is enforced in the database, not merely checked on screen.
Masked display
After binding, your own screens show only the last four characters. The full number is never displayed, never logged and never returned to a browser.
Permanent binding statement
Before you confirm, the platform states plainly that this tag will belong to this document and no other, and asks you to agree.
The printed tag
Print ready artwork
A PDF at forty millimetres with crop marks and a PNG at six hundred dots per inch, both in navy and orange on white.
Unique tag serial
Twelve characters from a cryptographic random source, shown in three groups of four for reading and stored without spaces.
Written fallback address
The address prints in plain text beneath the code, so a broken camera never breaks the return path.
Placement guidance
Clear instructions for the inside back cover of a booklet and the back of a card, with the minimum size stated.
The finder experience
No app and no account
Any phone camera opens the page. Nothing is downloaded and nothing is signed up for.
Partial number challenge
The last four characters of the number in hand are requested before any form appears.
Graded outcomes
Verified, unverified, or blocked. A genuine finder is never turned away by a strict rule.
Minimal form
Name, phone number, location and an optional message. Four fields and nothing more.
Live status line
The finder sees whether the owner was notified, has opened it, or is still being reached.
Masked relay fallback
When every channel fails, contact still happens without the owner's details being revealed.
The alert engine
SMS first
The primary channel, because it needs no data connection and no application.
Email and dashboard
Sent alongside, each logged separately with its own delivery state.
WhatsApp, opt in
Available where the owner chose it.
Verified phone before issue
No tag is issued against an unverified number, because an unverified path is not a promise.
Backup contact
One trusted second contact, alerted after a short silence, for the traveller whose phone is inside the lost bag.
Delivery logging and escalation
Every dispatch carries a provider status, and a failure or an unread message escalates automatically.
Quiet hours that cannot silence a finder
Quiet hours apply to routine messages only, never to a finder alert or a security alert.
Trust, security and privacy
Scan telemetry
Count, spread of locations and timing are recorded, so a harvested code looks different from a genuine find.
Rate limiting
Attempt limits per tag and per device, with cooldowns after failures.
Security alerts
A mismatched or repeated failed scan raises an alert to the owner and a queue entry for the operations team.
Data subject requests
Access, correction and erasure under the Kenya Data Protection Act 2019, requested from your own settings.
Honest deletion
Contact details, tags and scan history are deleted. Payment records are retained for seven years as a legal obligation, and the platform says so before you confirm.
Audit trail
Every action with legal or financial weight is written to an append only log.
Payments and records
Paystack checkout
Card and mobile money, in USD or in Ksh.
Currency handling
USD is the price. Ksh is a display at 1 USD to Ksh 134. Amounts are stored in cents so no rounding error can enter a money path.
Receipts and invoices
A numbered receipt for every payment, downloadable, printable and re openable at any time.
One charge per document
A second successful payment for the same document is impossible at the database level.
Partners and administration
Partner sub accounts
A university or a health facility manages its own cohort under its own account.
Bulk issuance
Tags issued in volume at the cohort rate, with the health facility tier charged to the facility and never to the student.
Partner reporting
Issuance, activation, scans and recoveries, per cohort.
Admin console
User management, the binding validation log, the alert delivery log with retry, payment records, the security alert queue, and the data subject request handler.
Ready to see it against your own situation?
Read how a real loss unfolds for a traveller and a student, or go straight to protecting your own document.