Privacy policy

Your photos are not on this list and never will be. Everything here is either what signs you in, what keeps the token balance honest, or what tells us why the app broke on a phone we do not own.

• Your Google email address and account identifier, received when you sign in with Google. The identifier is what the rest of this list is filed under.
• Your tokens and referrals. Against your account identifier we store your token balance, your own referral code, the code you were invited with if you used one, and the date the account was created. This is what stops a balance being spent twice or an invite being paid twice.
• Token purchases. If you buy a token pack, we store Google Play’s receipt identifier and which pack it was, so the same receipt cannot be redeemed a second time. The payment itself is handled by Google Play — we never see your card or your billing address.
• Ads you watched for tokens. When you choose to watch a rewarded ad, your account identifier is passed to Google AdMob so that AdMob can tell our server which account to credit. We store the ad’s transaction identifier and a daily count, so one ad cannot be claimed twice. AdMob may also use your device’s advertising ID to decide which ad to show; that part is Google’s, and is covered by Google’s privacy policy rather than this one.
• Crash and error reports, from installed release builds, through Google Firebase Crashlytics. A report carries the error and its stack trace, your phone model, Android version and app version, a random installation identifier generated by Crashlytics, and — when a video sweep is what failed — which lens was in use, which step it stopped at, the video size and the error text. It does not carry your photos, your project names, your location or your email, and the installation identifier is not your Google account.
• One report of what your phone’s cameras can do. The app decides on the device whether video capture is possible, and when it refuses there is no way to find out why without the numbers it refused on. So it sends them once: make, model, device codename, Android version, app version, the camera and lens specifications Android reports, the video sizes and encoder limits each lens offers, and the verdict the app reached. You must be signed in for the app to send it, but your account identifier is not stored in it — the report is filed by phone model and Android version, so every handset of the same model shares one record and two identical phones produce identical reports. It is sent again only if those numbers change, or if a new app version changes how they are judged.
• A one-way code made from your email address, recorded when the welcome bonus is paid. See how long we keep it — this one is deliberately kept.
• Questions you ask Blueezee, the help chat in the app (Settings › Help & support). Your question, and the last few messages of that same conversation, are sent to Google Gemini together with our public help pages, so it can write the answer. Your name, email and account identifier are not sent with them. We do not store the conversation on our servers. The app keeps it on your phone only, for 7 days after your last message, so you can come back to an answer; you can clear it sooner in the chat, and signing out clears it. All we keep is how many questions your account asked today, so the daily limit works. Please do not type personal details into the chat — see who else sees it for what Google may do with what you type.
• An app integrity check. Anything that moves your token balance asks Google Play Integrity to confirm that the app is the real Bluez360 from Google Play on a genuine device. It is a check on the app, not on you.

• Your photos. Captured shots and finished 360° images are written to your phone’s own storage and are never uploaded to us.
• Your projects. Project, area and image names stay on the device.
• Location. Any location recorded by your camera lives in the photo’s EXIF data, on your device only.
• No profile of you, and nothing sold. We do not track you across other apps or websites, we do not build an advertising profile, and we sell or rent nothing to anybody. What we hold is the list above, and each line of it exists to make the app work rather than to learn about you.

If you are in the EU or the UK, the law asks us to say not only what we hold but on what grounds we are entitled to. Every line in the list above is one of these three, and nothing is held on a ground that is not written here.

• Because you asked for the app to work (performance of a contract) — your sign-in, your token balance, your referral code and the receipt for a token pack. There is no account and no balance without them.
• Because you chose it (consent) — rewarded ads, and the advertising ID Google may use to pick one. Nothing is sent unless you start an ad yourself, and not watching one costs you nothing but the tokens you would have earned. Likewise the questions you choose to ask Blueezee: nothing goes to Google Gemini unless you type a question and send it.
• Because the app cannot be kept working otherwise (legitimate interest) — crash reports, the one report of what your phone’s cameras can do, the Play Integrity check, and the one-way code that stops the welcome bonus being collected twice. Each is the smallest thing that answers a question we have no other way of answering, and none of them is used to advertise to you or to build a profile of you.

Where the ground is legitimate interest you are entitled to object, and we will stop unless there is a reason we can show that outweighs it. See your rights.

Signing in identifies which library on the phone belongs to you, so two people using the same device do not see each other’s work. It is also what your token balance is attached to.

• Camera — to take the shots that make up a 360° image.
• Storage — to save those images on your device.
• Internet — for Google sign-in, for buying and spending tokens, for rewarded ads, for crash reports, for the one-time report of what your cameras can do, and for answering questions in the help chat.

Nobody outside Google, and Google only as our processor. The parts we use are Firebase Authentication for sign-in, Cloud Firestore for tokens, referrals, purchases and the camera report, Firebase Crashlytics for crash reports, Firebase App Check with Play Integrity for the integrity check, Google AdMob for rewarded ads, Google Play Billing for token purchases, and the Google Gemini API to answer questions in the help chat. Their handling is covered by Google’s privacy policy. We share it with no one else, and we sell nothing.

One difference for the help chat. We use Gemini on Google’s free tier, and under the Gemini API terms Google may use what is sent to it on that tier — your questions included — to improve its products, and people at Google may read it to do so. That is why the chat asks you not to type personal details, and why we never send your name, email or account with a question.

• Your sign-in record — until you delete your account.
• Crash reports — 90 days, after which Crashlytics deletes them.
• Help chat — the conversation is not stored on our servers; your phone keeps it for 7 days after your last message, then removes it. Today’s count of questions sits on your account until the next question on a new day replaces it, and goes when you delete your account. What Google keeps of a question is set by the Gemini API terms.
• Your tokens, referral code and purchase receipts — for as long as the account document exists. See below: deleting your account does not currently remove it.
• The one-way code made from your email — kept indefinitely, and kept on purpose after you delete your account. It is the only thing stopping the welcome bonus being collected again and again by deleting and re-registering. It is a one-way code, not your address: it cannot be turned back into your email, and it is stored away from your account.
• The camera report — kept while it is useful. It describes a phone model rather than a person, and carries nothing that points back to you.
• Photos on your phone — yours to keep or remove. Deleting your account does not touch them.

In the app: profile icon → Settings → Delete Account. Or on the web: bluez360.web.app/delete-account.

What that deletes today, plainly. It removes your Google sign-in record, so the account is gone and nothing can be signed into. It does not automatically remove the document holding your tokens, referral code and purchase receipts, nor the entry that maps your referral code to it, nor the one-way code described above. If you want the first two gone as well, email us and we will delete them by hand — there is no form and no reason we would refuse.

• Your name and phone number — required, because we call you back.
• Your email — optional, and only used if you want the quote in writing.
• The business name and address — this is the place we would come and photograph.
• The package you chose, and anything else you decide to tell us.

We read it and we answer you. It is stored in our own Google Firebase project and emailed to us so we notice it. It is not added to a mailing list, not passed to anyone, and not used to advertise to you.

Six months, then it is deleted automatically — both the stored copy and the email copy. If you would like it gone sooner, email us and we will delete it.

The form allows three enquiries a day from one internet connection. To count them without keeping track of people, your connection’s address is converted into an unreadable code using a secret only we hold, and it is that code we count. We do not store the address itself, the code cannot be turned back into it, and the whole count is deleted within about two days.

The form is also protected by Google reCAPTCHA Enterprise, which checks that a person rather than a script is sending it. That check is subject to Google’s privacy policy.

No tracking cookies and no advertising cookies. The booking form saves what you have typed in your own browser so that a half-finished enquiry is still there if you come back to it. It never leaves your device, we cannot read it, and it is cleared the moment the form is sent.

This site shows maps and virtual tours from Google and videos from YouTube. Those are loaded from Google’s servers and are covered by Google’s privacy policy, not this one.

Whatever we hold about you, you may ask to see it, correct it, or have it deleted. Email us and we will do it — there is no form to fill in and no reason we would refuse.

Bluez360 is a tool for site surveys and a service for businesses. Neither is directed at children under 13.

If this policy changes, the date at the top of this page changes with it.

Questions about this policy, or a request about your data: bluez360.studio@gmail.com