Privacy Policy

The short version, because it is unusual

Keysa is built to record the condition of a rented home so a deposit dispute is a matter of record. It is designed around a server that stores that record.

That server is not running. There is no Keysa server deployed anywhere, and the build points at an address on the phone itself. So in the app as it stands, the photographs of your home, your address, your deposit amount, your landlord's name and your condition notes are collected, held on your phone, and sent nowhere.

Two things do leave your phone, and both go to Google: signing in, and advertising. Those are described below.

What we collect, and where it actually sits

Your email address, and a display name if your sign-in provides one. This is handled by Firebase Authentication, a Google service, and an account is required to get past the first screen.

The tenancy you set up: property address and postcode, tenancy dates, deposit amount, deposit scheme and the landlord or agent's name.

Your room-by-room photographs of the property, your condition notes, your issue log and your move-out comparisons.

Everything in the second and third points is written to your phone's own storage: the notes and tenancy details in the app's ordinary preferences file, and the photographs as image files in the app's private directory. None of it is encrypted by Keysa beyond the protection your phone gives every app, and none of it is transmitted, because there is nowhere for it to go.

Photographs may still carry their location

A settings screen in the current build tells you that location has been removed from your photographs. That is wrong, and we would rather correct it here than leave it standing.

The code that removes location data lives on the server, and no photograph ever reaches the server. On the phone, the picture is saved with whatever metadata your camera wrote, which can include the coordinates of your home if your camera has location switched on.

If that matters to you, turn location off in your camera app before you photograph the property. We are fixing the misleading screen.

What leaves your phone

Sign-in. Your email address, your password or Google credential, and the ordinary connection details go to Google, because Firebase Authentication is a Google service. This works even though the Keysa server does not, because it is a separate path to Google.

Advertising. Keysa shows ads from Google AdMob, and the ad code runs on the sign-in screen, so an ad request is made before you have an account. Requests are marked as non-personalised, but AdMob still receives your device's advertising identifier, IP address and app information. The shipped Android build asks for the advertising ID permission.

Google's consent form runs before the first ad request. If it fails or times out, the app proceeds and serves a non-personalised ad rather than holding it back.

Nothing else. Not the photographs, not the address, not the deposit, not the landlord's name, not the notes.

Reminders

Deposit and tenancy reminders are scheduled by your phone's own alarm clock and shown by your phone. Keysa sends no push notifications and there is no messaging service involved, so nothing about your reminders reaches us or anyone else.

Deleting your account and your data

There is no delete-account button in Keysa, and no such route exists in its code. We will not describe one.

Because the tenancy record, the photographs and the notes are only on your phone, uninstalling the app removes them. There is no server copy to chase.

The account itself is a Firebase account holding your email address. To have that removed, email [email protected] from the address on the account and a person will action it.

Children

Keysa is intended for adults renting a home. It is not directed at children and it has no age check.