My Database ProPrivacy Policy

Effective 16 October 2026

My Database Pro is made by Boco Apps (“we”), in Sweden. This policy says what happens to information when you use the app. It is written to be read rather than agreed to, and it is part of the app itself so that it is there with no connection at all.

The short version. We collect nothing. There is no account, no advertising and no tracking, and the app sends nothing to us — we have no server for it to send anything to. Your databases, your photographs and your passwords stay on your phone unless you send them somewhere, and then they go to the server or the service you chose. The one exception is Google's code scanner and text reader built into the app, which report technical diagnostics to Google — never your pictures or what they read (section 3).

1. What stays on the phone

Everything the app is for is stored on the device, in the app's own private storage, which no other app can read:

Local SQLite databases and the photographs attached to their records.
Every setting — the language, the theme, the order of your lists, which columns a record shows, which column a table is sorted by.
The log of messages the app has shown you (the last 100).
Notes and files you write in the editor.

None of it is uploaded anywhere by the app on its own. Deleting the app deletes all of it, which is why the app carries a backup of its own — see section 5.

2. Passwords and logins

A database password encrypts the database file itself (SQLCipher). It is not stored anywhere: without it the file cannot be opened, by us or by anybody, and there is no way to recover it.
MySQL, SFTP/FTP, SSH and AI keys are kept encrypted under a key held in the Android Keystore. That key cannot leave the device, so a copy of the stored data is worth nothing anywhere else — which is also why the app is excluded from Android's own cloud backup.
The connection lock is a password you may put over the screens that show those logins. It is kept only as a salted SHA-256 hash, because nothing about it has to be decrypted.

3. What leaves the phone, and only because you asked

The app talks to the network only where you point it, with the addresses and the accounts you typed in yourself:

Where	What goes there
Your MySQL server	The queries you run and the rows you write, over your own connection. Images for those records go to the image API on the web host you configured. If you share a database under Users, the app creates the logins and picture keys for those people on that server and web host, and nowhere else.
Your SFTP / FTP server	Exactly the files you chose to upload — an export, a backup, a picture, a folder.
Your SSH server	What you type in the terminal.
The Web View	Whatever page you open, which behaves like any browser tab. It blocks the larger advertising and tracking networks inside that view by default, and that switch can be turned off.
An AI provider	Only when you ask an AI something, and only to the provider you picked with the key you entered: Claude (Anthropic), OpenAI, Gemini (Google), Grok (xAI), Mistral, DeepSeek, Puter, or a model running on your own machine. What goes with your question depends on where you ask it: AI chat (the ✦ on the tool row) — your messages in that conversation, and parts of this app's own How to page so it can answer questions about the app. None of your data. SQL Query — the structure of the database you are on (table and column names and types) and the query in the box. No rows of your data. Editor — the file in the tab you ask about. Terminal — the last lines on the terminal screen and your user name; never the password. Choose a local model and none of it leaves your network. What the provider then does with it is governed by that provider's own privacy policy.
Google Play	The app is unlocked with a purchase made through Google Play. To know whether it is unlocked, the app asks the Play Store app on the phone what this Google account has bought. Payment is handled entirely by Google Play: the app never sees your card, your name or your address, and nothing about the purchase is sent to us. What Google does with a purchase is governed by Google's own privacy policy.
Google (ML Kit)	The code scanner and the text reader are Google's ML Kit, built into the app. When you use them, ML Kit sends Google technical diagnostics: the phone's make, model and Android version, the app's name and version, an identifier for this installation (not meant to identify you or the phone), and how long the recognition took and whether it failed. The picture and the code or text read from it are never sent — reading is done on the phone. Google uses this to measure and improve ML Kit and does not pass it on; see Google's ML Kit data disclosure.

There is no other network traffic. The app has no server of ours behind it and never contacts one, and none of the above reaches us.

4. Camera, photographs and the microphone

The camera and your photo library are used when you add a picture to a record, scan a code, or read text off a label. Pictures you attach are copied into the app's own storage.
Scanning a code and reading text are done on the device. The recognisers are bundled with the app; no picture is uploaded to anyone to be read. They do report technical diagnostics to Google (section 3).
The microphone is used only while you hold the dictate button in the AI chat. Speech is turned into text by the phone's own speech service, which, depending on your phone's settings, may do that over the network — that part is Android's, not ours.

5. Backups

Back up everything writes one ZIP file: your databases, their images, your saved pages, the order of your lists, and your saved logins. The logins have to be readable on another phone, so they cannot stay under the phone's own key. With a Backup password set, they go into the file encrypted with it (AES-256-GCM, the key drawn from the password with PBKDF2), and only that password opens them; without one, they are in the file as plain text.

A backup file is a secret, like a sheet of paper with your passwords on it. It goes wherever you send it and nowhere else — we never see it. Keep it somewhere you would keep that sheet of paper. Database passwords are deliberately not in it: a backup that could open your encrypted databases would not be worth much.

A connection file, made under Users to share one database with someone, holds a single MySQL connection and is always encrypted the same way, with a password you choose and tell them separately. You send it yourself, to whoever you choose; we never see it. Treat it like a backup: whoever has the file and its password has that login.

6. Children

The app is a tool for managing your own data. It is not designed for or directed at children, and since it collects nothing, nothing about a child is collected either.

7. Your rights

Under the GDPR you have the right to see, correct, export and erase personal data a company holds about you. We hold none: there is no account and no server, so there is nothing for us to show, export or delete. The data in the app is in your hands the whole time —

Export it with any of the export or backup options.
Erase it by deleting a database in the app, or by uninstalling the app, which removes everything it stored.

Data you put on your own MySQL or SFTP server is yours to manage on that server. If you believe your rights have not been respected you may complain to your data protection authority — in Sweden, IMY.

8. Changes to this policy

If the app changes in a way that affects this page, the page changes with it: it ships inside the app, so an updated policy arrives with an updated app, and the date under the title says which version you are reading.

9. Contact

Questions about this policy: bocoapps@outlook.com.