Privacy notice

Who we are

Bitting is operated by SYSERR, LLC (United States). Contact us at hello@bitting.app.

This notice covers the Bitting resident app and my.bitting.app. It is written for residents. If you are an operator using the console, the same practices apply to your account.

Two things we never store

Your Wi-Fi password. When you view it, we fetch it, send it to your device and discard it. It is never written to our database, never cached and never logged. When you change it we pass the new value straight through.

The devices on your network. The list of what is connected is read live from your building’s Wi-Fi system each time you open the screen. We do not keep those MAC addresses or device names.

What is on your phone

Almost nothing, and none of it is your biometrics. Your phone never gives your face or fingerprint to an app, including this one. We have never seen it and could not store it if we wanted to.

What the app keeps is a private key, created inside your phone’s secure hardware. Its secret half never leaves that hardware, and the app cannot read it either. It can only be used after your phone checks your face or fingerprint and tells us only whether the check passed. If you change the faces or fingerprints enrolled on your phone, the key stops working, by design.

Alongside it: your signed-in session, held behind the same check and marked so it never leaves this device or reaches a backup, and a non-secret identifier naming which key to use.

Everything else is fetched when you look at it and kept only while it is on screen. Your password, the devices on your network and your traffic totals are never written to your phone. That is why closing the app leaves nothing behind to find.

What we do store

A recovery contact. The email address or phone number you gave us, so you can get back in on a new device. This is ours, not your building’s. We ask for it precisely so your contact details do not have to live in their Wi-Fi system.

Your devices. For each phone or browser you enroll: its platform, app version, a public key, an identifier for that key, any name you gave it, when it was added and when it was last used. The private key never leaves your device and we could not read it if we wanted to.

Which home you are linked to. An identifier for your unit’s Wi-Fi credential in your building’s system, and the unit label your building put on it.

Traffic totals. If your building has the feature, we cache how many bytes your home sent and received over the last seven days and the names of the busiest applications. Totals only. Never addresses visited, never content.

Security records. Hashed session tokens, one-time codes while they are valid, and counters that limit repeated attempts. Those counters include your IP address, which is how we stop someone guessing at codes.

What we do not collect at all

No location. No contacts, photos or files. No advertising identifier. No analytics or tracking software of any kind. Apart from the speed test, which measures against Cloudflare and shares the result with them when you run it, the app talks to our own servers and nowhere else. We do not sell or share anything for advertising, and there is nothing here to sell.

Who else sees it

Your building’s Wi-Fi system: RUCKUS One, from RUCKUS Networks, a Belden company. We read and change your Wi-Fi credential there using access your building gave us. Your recovery contact is never sent to it.

Resend, to deliver the one-time codes we email you. They receive the address and the message.

Railway, who host our servers and database in the United States.

That is the complete list. We would also disclose data if legally compelled, and would tell you unless prohibited.

Your building, and what they control

Your building decides who gets a claim code and which unit it is for. For your Wi-Fi credential itself we act on their instructions. They are responsible for that data and you should contact them about it. For your recovery contact and your enrolled devices, we are responsible, and this notice governs.

When you move out, your building releases your unit. That signs your devices out and unlinks you from the home; it does not by itself delete your recovery contact.

How long we keep it

Your recovery contact and devices last as long as your link to a home, plus thirty days. Rate-limit records, including IP addresses, expire after thirty days. Traffic totals are refreshed at most every six hours and replaced each time.

When you delete your account, everything above goes with it. There is no separate archive we keep you in. Backups roll off within thirty-five days.

Deleting your account

In the app, open Settings and choose Delete my account. Or email hello@bitting.app. You do not need the app installed to ask, and we will verify it is you before acting.

We delete your recovery contact and your enrolled devices, and we unlink you from your home. We keep a dated record that an account was deleted, with nothing in it that identifies you. That is how we can show the deletion happened.

Your Wi-Fi keeps working. Deleting your Bitting account does not change your password or disconnect anything. Your building still manages the network. You simply stop having an app for it.

Your rights

You can ask for a copy of what we hold, ask us to correct it, or ask us to delete it. Write to hello@bitting.app and we will respond within thirty days.

If you are in the EEA or UK, our basis for processing is performing the service you asked for, and our legitimate interest in keeping it secure. If you are in California, we do not sell or share personal information as those terms are defined there, and we will not discriminate against you for exercising any right.

Children

Bitting is not directed at children and we do not knowingly collect their data. If you believe a child has given us information, write to us and we will delete it.

Changes

If we change how any of this works we will update this page and its date. For a change that materially affects you, we will contact you at your recovery address before it takes effect.