Use cases
Start from what you are making
Every setup below picks an access gate for you, and tells you why. The gates differ because the risks do: a menu behind a login is a menu nobody reads, and a patient form behind a public link is an incident.
Secure document share
A contract or report that only named people should open.
Private link
A private link you send to each named person, revocable at any time and expiring on its own. The document is watermarked with whoever opened it, so a leaked copy points back at one reader.
Start with thisHR onboarding pack
Handbook and forms for new starters, staff only.
Sign-in required
New starters sign in with their work account, so a code left on a desk is useless to a visitor and you can see who has read the pack.
Start with thisPatient intake
A form or instructions handed to one patient.
Private link
A private link you send to one person, with no account for them to create. Scans are not recorded at all, so the code cannot become a log of who visited your clinic.
Start with thisEvent pass
A ticket or badge for one attendee.
Private link
One link per attendee, openable once. A screenshot passed to a friend stops working, which is what makes it a pass rather than a poster.
Start with thisRestaurant menu
A menu on every table, for anyone who sits down.
Open to everyone
No gate at all: a menu behind a login is a menu nobody reads. The content is still encrypted at rest and you can change it without reprinting a single table card.
Start with thisProduct page
Packaging or a shelf label pointing at a live page.
Open to everyone
Open to everyone, and the destination is yours to change later. The printed code keeps working when the campaign moves to a new landing page.
Start with thisBusiness card
Your contact details, saved to a phone in one tap.
Open to everyone
Anyone you hand the card to can save your details immediately. Nothing to gate: these are the details you are giving them.
Start with this