Summary
This policy covers two discontinued byBnD apps: Mergulho Técnico, a pre-dive checklist for rebreather divers, and Let's Dive, a dive calculator. Both were withdrawn from the stores in November 2026 and receive no further updates.
Neither app has an account or a login, neither asks for your name or email address, and neither shows ads. Mergulho Técnico sends nothing to us: what you type stays in the app on your device while you use it. Let's Dive includes Google Firebase, which, where it was active, sent Google crash reports and basic usage events, such as opening the app; those reports describe the device, the app version and what the app did, not who you are.
We hold no profile, no account and no saved content from either app. There is nothing for you to log in to, and no account to close.
Scope and who is responsible
This policy applies specifically to these two apps, identified by their store identifiers: Mergulho Técnico, br.com.bybnd.mergulho.tecnico, and Let's Dive, br.com.bybnd.dive.calculator. It does not apply to other byBnD apps or games, which have their own policies, and it replaces the policy address published for Mergulho Técnico in 2023, which no longer exists.
BYBND INFORMÁTICA LTDA, company registration (CNPJ) 32.574.894/0001-10, at Alameda dos Maracatins, 1435 - Conjunto 307 - Indianópolis, São Paulo - SP, 04089-015, Brazil, published both apps and is the controller of the personal data processed for the purposes described here.
For support and general enquiries, contact contato@bybnd.com.br. Our data protection officer (DPO) is Robson Felippelli Vicente; privacy questions and rights requests can be sent directly to dpo@bybnd.com.br.
This notice complements the corporate policy at https://bybnd.com.br/privacidade (Portuguese; English summary at https://bybnd.com.br/en/privacy), which describes the byBnD website and business relationships and does not describe these apps. The practices of the apps are the ones described here. This policy is published in English, Portuguese and Spanish with the same content; the English version prevails if a translation differs.
Mergulho Técnico: what the app does with your data
Mergulho Técnico shows a pre-dive checklist and a linearity worksheet. You can type a diver name, a date, a dive number and sensor millivolt readings, and tick checklist items. In the source code we read, these entries live in the app while it is open; they are not written to a file, not sent anywhere and not kept by us.
The app has no advertising, measurement or crash reporting library and makes no network request. Its Android release build declares no permissions (the internet permission appears only in the debug and profile builds used during development), and its iOS build requests no privacy permissions. It asks for no health permission and reads no health data.
If you use the share button, the app saves a picture of the screen in the device's temporary folder and hands it to the system share sheet, so you choose where it goes. We do not receive it. What you then send through another app, such as email or a messaging app, is governed by that app's terms.
Let's Dive: crash reports and Firebase usage measurement
Let's Dive is a dive calculator. What you type is used for the calculation, is not saved by the app and never reaches us. The app shows no ads and declares no permissions of its own; the Google libraries it includes add the internet and network state permissions to the installed app.
The app includes Google Firebase in 2019 versions: Crashlytics, for crash reports, and the Firebase core library, which in that version brought Google Analytics for Firebase with it. Where they were active, Google received a crash report when the app failed — device model, operating system and app version, the technical details of the failure and an installation identifier created by Firebase — and the usage events Analytics collects on its own, such as first opening, the start and end of a session and screens viewed, with the device, the app version, an app instance identifier and an approximate region derived from the internet address. On Android of that period, Analytics also collected the device advertising identifier unless the developer turned that off, and we found nothing in the code turning it off. No name, email address or account was involved, and none of the calculations you make were sent.
In the source code we read, the Firebase configuration exists only for the alpha and beta test variants, so this was set up for test builds rather than for a public release build. We cannot tell from the code which build reached each store, so we describe crash reports and usage measurement as something that may have been active in the copy you have, instead of promising that they never ran. Both apps are discontinued, so nothing is being collected now. Google documents Firebase at https://firebase.google.com/support/privacy.
No accounts, no ads, no advertising profile
Neither app has registration, login, profile, chat or in-app purchase. Neither shows ads, neither asks for the Apple tracking permission and we build an advertising profile of nobody. Mergulho Técnico does not touch the device advertising identifier; in Let's Dive, Google Analytics for Firebase could collect it on Android, as described above, which is a Google default of that period and not something we used for advertising. We do not sell personal data and we do not share it for targeted or cross-context behavioural advertising, in the sense used by United States state laws.
Neither app sends push notifications, and neither asks for location, contacts, camera, microphone or health data.
Stores and your device
The download, your store account and any payment were handled by Apple and by Google as independent controllers, under their own policies. We receive only the sales and installation reports the stores provide, which do not identify you by name or email address.
Because neither app keeps a file with what you typed, there is nothing of yours for us to delete and nothing for us to restore. Uninstalling removes the app and its temporary files from the device. A device backup made through your Apple or Google account is under your control, not ours.
Support and information you send
If you write to us, we receive your email address, your message and whatever details you choose to include, such as the app version, the device model or a screenshot. We use that to answer you and to handle privacy requests. Please send only what is needed, and no passwords, payment data or identity documents.
Because both apps are discontinued, we can answer questions and privacy requests, but we no longer fix defects or publish updates.
Purposes and legal grounds
Mergulho Técnico gives us nothing to process: we obtain no personal data through it, so there is no processing by us that needs a legal basis. For Let's Dive, crash reports served to detect and understand failures, and we rely on our legitimate interest in keeping an app working and secure (Brazilian LGPD, Law 13,709/2018, article 7, IX, and, where the European GDPR applies, article 6(1)(f)). The Firebase usage measurement, where it was active, was never preceded by a consent request in the app, and in the European Economic Area and the United Kingdom measurement of that kind normally requires consent; we say so rather than claim a basis we cannot demonstrate. The apps are discontinued and collect nothing further.
Answering your support message serves the request you made to us, or our legitimate interest in replying when no service is involved (LGPD article 7, II and IX; GDPR article 6(1)(b) and (f)). Records we are required to keep, and mandatory privacy requests, are handled to comply with the law (LGPD article 7, II; GDPR article 6(1)(c)).
There is no advertising, profiling or automated decision making in either app, and neither app asks for your consent, because neither does anything that depends on it. Reading this policy or using an app is not consent to anything.
Who data is shared with and processing in other countries
For Let's Dive, the crash reports and usage events went to Google (Firebase Crashlytics and Google Analytics for Firebase), which processes them on our behalf. Our support email runs on Google Workspace. Apple and Google Play answer, as independent controllers, for the download, the store account and payment. We share data from these apps with no one else.
These suppliers process data in several countries, mainly the United States. For data from the European Economic Area, the United Kingdom and Switzerland, Google states that it takes part in the Data Privacy Framework and uses standard contractual clauses where needed; for data from Brazil, Google's data protection terms include the Brazilian standard contractual clauses. Those terms are at https://business.safety.google/. You can ask us about destinations and safeguards.
How long data is kept
Crash reports and usage events are kept by Google under the retention that applies to Firebase crash data and to the Firebase project's Analytics setting, which we have not inspected; they are not combined with anything we hold. Support messages are kept only as long as needed to deal with the request, to document how it was resolved and to comply with applicable legal duties. Store sales and installation reports are kept for the period tax and accounting law requires.
We keep no other data from these apps, so there is no further retention period to state.
Your choices and privacy rights
Under applicable law you can ask for confirmation of processing and access, correction, deletion or anonymisation, restriction, objection, portability and information about recipients, and you can object to processing based on legitimate interest. Write to dpo@bybnd.com.br, or to contato@bybnd.com.br, which forwards privacy requests to the data protection officer. We answer within the applicable legal deadlines and do not ask you for an identity document.
Because the apps have no account, we cannot connect your email address to an installation. For Let's Dive, a crash report or usage event is identified only by an installation or app instance identifier that the app does not show you, so in practice we cannot isolate the records of one person; if you ask, we pass your deletion request to Google and explain how to contact Google and the stores. For Mergulho Técnico there is nothing to look up, because the app sends us nothing.
You can complain to the competent data protection authority, including the ANPD in Brazil or the authority of your country in the European Economic Area or the United Kingdom, and use any other remedy available to you.
Children and young people
Neither app is directed at children. They are tools for divers, with no chat, no profile, no account and no advertising, and neither asks for age or date of birth. Because they request no personal data, there is no parental consent mechanism to apply.
A parent or guardian who needs help, or who wants to raise a privacy question about a child, can contact us. Please do not send information identifying the child beyond what is needed to explain the question.
Security and changes to this policy
The apps keep no data of yours for us to protect; what we hold is support correspondence, in corporate email with controlled access. Report a suspected privacy or security problem to dpo@bybnd.com.br or contato@bybnd.com.br, without sending credentials or unnecessary personal data. No system can promise absolute security.
Both apps are discontinued and receive no updates, so the practices described here are not expected to change. If we correct or complete this page, we will update the date above. The facts here were read in the source code of both apps on 15 November 2026; the published version of Mergulho Técnico is older than the code we read, and the Let's Dive code we read is the Android app, with no iOS source examined. We state only what that code supports, and we will correct this page if we find out more.