Security
Specifics rather than slogans. Everything below is a decision in the code, not an intention — most of it exists because we got it wrong the first time and wrote down what to do instead.
Card URLs cannot be guessed
Each card gets a random 12-character address. A competitor's site that numbers profiles /1/, /2/, /3/ lets anyone read every customer in order — this is the mistake that makes that impossible.
Private fields are encrypted before they are stored
Date of birth, national ID and financial fields are encrypted with AES-256-GCM, with the key held outside the database. A stolen backup reveals ciphertext.
We do not encrypt what we display
Your name is on the card. Encrypting it would be pure cost with no benefit — and in our own earlier version it caused data corruption. Encryption is for the fields nobody but you should see.
One company can never see another's data
Every query is scoped to the organization that owns it, enforced in one place and tested on every build. It fails closed: a request with no organization gets nothing, not everything.
Every change is recorded
Who changed which field, when, and from where — including our own staff. Available to you, not just to us.
Staff accounts require two-factor
Anyone here who can reach customer data must have an authenticator app. It is enforced in code, not stated as a policy.
The chip itself is password-protected
Each tag gets its own password derived on our server. A stolen writing laptop cannot produce passwords for cards it did not write.
Encrypted backups you can verify
Nightly, encrypted to a key the server itself does not hold, and restore-tested. A backup nobody has ever restored is not a backup.
What is actually on the card
This is the question people mean when they ask whether an NFC card is safe.
On the chip
- A web address. That is all.
Not on the chip
- Your contacts
- Any password or login
- Anything readable by a stranger with a phone
Someone who picks up your lost card can open your public profile — the same page you hand out on purpose. They cannot read anything off the chip, and the moment you report it lost, the address stops working.
If you cannot use a hosted service
Banks, hospitals and government offices often cannot put staff data on a supplier's server — not from distrust, but because a regulator or a security policy says so. That is what the Self-Hosted package is for: the whole system inside your own network, with your data never leaving it.
Found a problem?
Tell us before you tell anyone else and we will fix it and credit you. We would much rather hear it from you.
info@dadaark.com