Privacy Policy

Summary

What we collect

We collect only the information needed to deliver and bill the service. That means:

• Subscription owner details. The name and contact details (email and/or phone number) of the person who owns the subscription. This is used to manage the account, send receipts, and provide support.
• Notification recipient details. The name, email address and/or phone number of each person added to a subscription as a notification recipient. This is used to notify them when a visitor rings.
• Location details. The address and/or map-pin coordinates of the registered location, used to create your QR code and to confirm that a visitor is physically at the door. For private homes the address is stored only as a one-way hash, never in raw form.
• Device details. If you install the app and enable push notifications, a device push token (a device identifier) so we can deliver alerts to your phone.
• Billing records. Subscription status, plan, billing cadence, and payment history. Actual card details are handled by our payment provider (see below) and never touch our servers.
• Operational logs. Minimal technical logs needed to keep the service running (for example, timestamps of notification deliveries and error traces). These are retained for a short period and then discarded.

What we do not collect

We deliberately avoid collecting anything that is not strictly necessary. In particular:

• We do not see your conversations. Text, voice and video between a visitor and the people at the door are encrypted end to end (WebRTC with DTLS/SRTP). Usually they travel directly between the two devices. When a network won’t allow a direct connection, the encrypted stream passes through a relay server, which cannot decrypt it. Either way, we cannot read, listen to, record or replay a conversation, and none is stored.
• We do not store visitor identities. Visitors who scan a QR code are not required to create an account or share personal details with us.
• We don’t know who visitors are. A visitor has no account with us, and we don’t store their IP address. When someone rings, we keep a record of the visit: which door, when, the location their phone reported if they chose to share it (used to check the ring came from the door, and never shown to the resident), and their browser type. What they write in the chat is encrypted end to end and never reaches us. That record is how residents see who called. It isn’t linked to any identity, and we don’t build a location history for anyone.
• We do not sell or rent data. Your information is not a product we offer to anyone.
• We do not run third-party advertising or tracking pixels on authenticated pages. The marketing site may use basic analytics to understand traffic patterns.

How we use your information

We use the data we collect to:

• Notify the recipients you have configured when a visitor rings.
• Operate your account (authentication, plan management, support).
• Process payments and send receipts.
• Send important service notices (for example, billing failures or security events).
• Diagnose and fix bugs, and improve reliability.

We do not use your information for behavioural profiling, advertising, or training third-party models.

Who we share it with

We share a limited amount of information with the service providers that make Dorbel possible:

• PayPro Global, Inc. (Canada) is our Merchant of Record. PayPro Global processes all payments on our behalf, handles tax compliance globally, and is the party named on your payment statement. When you subscribe, your payment details are provided directly to PayPro Global: we do not receive or store them. PayPro Global's privacy policy is available at payproglobal.com/legal.
• Cookies and local storage on these pages. This site, the marketing pages you are reading now, sets no cookies and loads no third-party scripts. If we ever add analytics, nothing will load until you agree: you will be asked first, and you can change your answer any time from the "Cookies" link in the footer. Your answer is kept in your browser's local storage, not in a cookie, so asking the question does not itself create the thing being asked about.
• Cookies and storage in the product. Your dashboard, the recipient app and the page a visitor reaches after scanning a code do set a few things. All of them are needed to make the service work, and none is used to track you.
  • A sign-in cookie when you log in to your dashboard or the recipient app. It lasts 30 days, can be read only by our server and never by JavaScript in your browser, and is sent over an encrypted connection. Signing out deletes it.
  • A short-lived checkout cookie while you are paying, so the payment provider can return you to the right place afterwards.
  • A visitor token, held in the browser’s session storage for the length of a single conversation, so that someone who scanned your code can be reconnected if their connection drops. It covers that one conversation and is gone when the tab closes. A visitor never signs in and is never given a cookie.
  • On a phone, the most recent notification token, kept on the device so the app does not register the same phone twice.
  None of this is advertising, analytics or profiling, which is why you are not asked to accept it: consent rules cover tracking, not the cookie that remembers you are signed in. Anything we add that is not strictly necessary will be opt-in, and will be described here first.
• DigitalOcean (Sydney, Australia) hosts the Dorbel app and its database. Everything this policy says we keep is stored there.
• Cloudflare (global network) sits in front of dorbel.app to protect it from attacks, and relays a call’s encrypted audio and video when two devices can’t connect directly. It sees IP addresses as traffic passes through, and cannot read a call.
• Zoho (ZeptoMail, Australia) sends our emails: sign-in codes, invitations, account and billing notices, and doorbell alerts to recipients who don’t have the app. It receives the email address and the message. Open and click tracking are turned off.
• Mapbox (United States) turns the address you type when registering into map coordinates. It receives the address, not your name or email.
• Push notification services from Apple, Google or Mozilla, depending on your phone and browser, deliver doorbell alerts to the Dorbel app. For the installed web app the alert is encrypted, so the push service can’t read it.
• Grafana Labs (Australia) receives our server logs and checks that the service is up, so we are alerted when something goes wrong. Logs are technical records, but some include an email address or an IP address.
• OpenStreetMap supplies the map you place your pin on when registering. Your browser loads the map images from its servers, which see your IP address and the area shown, but not your name, email or anything else that identifies you.
• Legal obligations. We may disclose information if required to do so by law or a valid legal process.

Where your data is stored

Dorbel’s app and database run on DigitalOcean in Sydney, Australia, and that is where the information this policy describes is stored. Our server logs are kept by Grafana Labs, and our emails are sent by Zoho, both also in Australia. The other providers listed above process some data elsewhere as part of their service: Mapbox in the United States, PayPro Global in Canada, and Cloudflare and the push services on their global networks. We take reasonable steps to ensure that processing is protected by appropriate safeguards.

Security

We protect your data with:

• Encryption in transit (HTTPS/TLS) for all traffic to and from the service.
• End-to-end encrypted channels for call and chat media (WebRTC with DTLS/SRTP), direct between devices wherever the network allows.
• Single-use, expiring session links so that notification URLs cannot be replayed.
• Standard access controls and monitoring on our infrastructure.

No system is perfectly secure. If a breach occurs that affects your data, we will notify you as required by applicable law.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete the personal information we hold about you, and to object to or restrict certain processing. You can exercise these rights by contacting us at the address below. We will respond within a reasonable time and will not charge you for reasonable requests.

You can also remove notification recipients yourself at any time from your subscription dashboard. Removing a recipient stops future alerts from being sent to that address and deletes the associated record.

Deleting your data. You can delete your data yourself at any time at dorbel.app/delete-account (also linked from your dashboard). Account holders can delete their entire account there; people who were added as notification recipients can erase all of their recipient data by verifying their email. Deletion takes effect immediately: access is revoked and notifications stop, and your personal data is permanently purged after a 30-day grace period, during which you can contact us to reverse the request. If you have an active paid subscription, cancel it with our payment provider first so billing stops. Financial records held by our payment provider are retained for the period required by tax and accounting law.

Data retention

We retain subscription and billing records for as long as your account is active, and for a limited period afterwards as required to meet tax and accounting obligations. Notification recipient records are kept for as long as they remain on a subscription; removing a recipient deletes the record. Operational logs are retained for a short rolling window. When you request deletion (see Your rights), access is revoked immediately and your personal data is permanently purged after a 30-day grace period; financial records held by our payment provider are retained as required by law.

Children

Dorbel is not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.

Changes to this policy

If we make material changes to this policy we will update the "last updated" date above and, where appropriate, notify account holders by email. Continued use of the service after an update constitutes acceptance of the revised policy.

Contact us

Questions about this policy, or requests relating to your personal information, can be sent through our contact form.