How Hangr looks after your shop's data
What we do to keep each shop's records to itself and respect your customers' choices.
Each shop's data is kept apart
Every record belongs to one shop, and the database itself refuses to show it to any other shop. The rule is enforced in Postgres on every query, not only in Hangr's code, and every deploy checks that the app's database login can't skip it.
Photos stay private
Drop-off photos are never at a public web address. Each one is fetched through Hangr's API, which first checks that whoever asks may see that ticket: someone signed in at your shop, or the customer holding that order's own link.
Sign-in
Everyone at your shop gets their own sign-in, and anyone can turn on two-step sign-in with an authenticator app. Hangr's own team can't open a shop's records in Hangr without two-step sign-in.
Your customers' choices
Every email to your customers has a link to stop them, and a customer who stops all your emails gets no more from your shop. Texts to customers are rolling out and are not live yet, and each customer's yes or stop to them is recorded with the date and how it was given.
A customer's own data
From a customer's page you can download what Hangr holds about them, or erase them. Erasing removes their name and contact details; the orders keep only what your books need.
AI assistants, only if you connect one
Only a shop's owner can connect an AI assistant, with two-step sign-in on. Each connected assistant is listed in Settings, and Disconnect stops it at once.
Payments
Hangr doesn't take or store card numbers. Payments are recorded, not processed.
Getting help
Write to us from the contact page. A person reads every message and replies by email.