Privacy Policy
Last updated on
The short version: we count visits, not people. Opening a link sets no tracking cookie and builds no profile, and we never sell your data to anyone.
This policy covers two kinds of people: account holders who create links and QR codes, and visitors who open them.
1 What we keep about you
1.1 Signing in
There are no passwords. You sign in with a six-digit code sent to your email, or with Google. We keep your email address, the name you give us, your time zone, your settings and any setup answers, a profile photo if you have one, and when you signed in. For each signed-in device, we also keep its browser, IP address and rough location.
1.2 What you create
Your links, destinations, schedules, access codes and QR code designs are stored so the service can work. Every change is saved as a version, and an activity log of changes is kept for your account.
1.3 Cookies on this site
Session cookies keep you signed in, and a few functional ones remember preferences like theme, grid or list view and Test mode. While you sign in, one holds your email address for up to an hour. None of them track you.
1.4 Shared reports
You can publish a read-only report of one link’s numbers at an unlisted address. It shows the link’s title and its numbers, including where visits came from, but never its destinations or anything about your account. Anyone with the address can open it until it expires or you revoke it.
1.5 Support
If you contact support, we keep your message and email address so we can reply.
2 When a link is opened
2.1 One event per visit
Each open or scan records one event: when it happened, which link was opened, which destination was served, whether it came through the short link or the QR code, the site that sent the visitor and any campaign tags in the address, and what happened (redirected, expired, paused, warning shown and so on), and how quickly we answered.
2.2 A visitor key, not a visitor
We turn the visitor’s IP address and browser into a key using a secret that changes every day. The visit is stored with the key, never the address itself, and the same person gets a new key each day. Entering a link’s access code also holds the visitor’s IP address for 10 minutes, to stop guessing.
2.3 Rough location and device
Country, region and city come from our hosting provider’s request headers, and location never goes below city. We also note the device type, operating system and browser, and where the visit came from (direct, search, social apps and so on).
2.4 Bots
Known crawlers, link previews and security scanners are labeled as bots and left out of every count, unless you switch off Hide bots in Settings.
2.5 Cookies for visitors
A plain redirect sets no cookie and runs no script. A visitor only gets a cookie after entering a link’s access code (it lasts 12 hours) or choosing to continue past a safety warning (it lasts an hour). Both are tied to that one link and expire on their own.
3 Images you upload
Profile photos and QR code logos are kept in a public store, so anyone with an image’s address can open it. Treat an image as published the moment you upload it.
We check every upload on the server and delete anything that isn’t a PNG, JPEG, WebP or GIF within our size limits. The dashboard can’t delete an image yet, so a removed logo or replaced photo stays online until you delete your account.
4 How long we keep things
Raw visit events are deleted after 90 days. They’re removed in whole-month batches, so in practice that’s 90 to 120 days.
Totals hold no visitor keys. Hourly ones are deleted after 13 months, and daily ones are kept while your account exists. Your account data is kept until you delete your account, and IP addresses held to stop abuse go after a day or two.
When you delete a link, its address is retired for good and never issued to anyone else, so nothing already printed can quietly point somewhere new. Deleting your account retires every address in it the same way.
5 Who else sees it
We don’t sell data, share it with advertisers or use it to build profiles.
It’s processed only by the services that run Doorbell: Supabase (database, file storage and sign-in), Vercel (hosting and location headers), Upstash (a short-lived cache and event queue), Resend (sign-in codes, notification emails and support messages) and Google (sign-in with Google, and the Gmail inbox where support messages arrive). When it’s enabled, destination addresses, and only the addresses, are sent to Google Safe Browsing to be checked.
6 Reporting a link
Anyone can report a link from its warning page, or from the page shown when it has expired, been paused or been blocked. A report keeps the reason chosen, anything typed in the optional note, whether the reporter came by link or QR code, and a visitor key. To stop spam, we hold the reporter’s IP address for 10 minutes. We never ask for a name or contact details.
7 Your rights
You can delete any link from your dashboard, and your whole account and everything in it from Settings, straight away. You can also read everything back through our API, which runs on the same code as the dashboard. There’s no one-click export yet.
Under the Nigeria Data Protection Act 2023, you also have the right to access, correct and delete your personal data, to object to how it’s used, and to complain to the Nigeria Data Protection Commission.
Visit records hold no names or IP addresses. We can only find a visitor’s visits if they tell us the exact network address and browser they used, and when. That’s by design.
8 Under 16s
Doorbell isn’t meant for anyone under 16, and we don’t knowingly keep data about them.
9 Changes to this policy
If this policy changes in a way that matters, we’ll say so on this page, with the date it takes effect.
10 How to reach us
Doorbell is run by Jide Fabanwo. Questions about your data, or a request to see, correct or delete it? Write to jide.fabanwo@gmail.com.
The rules for using Doorbell are in our Terms of Service.