La Botica de Almar Privacy Notice
This is the privacy notice for the game La Botica de Almar. The website's notice is at /en/privacy. You can also read the Spanish version.
La Botica de Almar Privacy Notice
1. Controller
Lopand Solutions S.A. de C.V., Vicente Guerrero 132, Colonia Santa Anita, 45600 Tlaquepaque, Jalisco, Mexico, is responsible for the game La Botica de Almar. Contact: soporte@lopandsolutions.com.
2. Personal data we process
The game does not ask you for any data to identify you. La Botica de Almar does not ask you to register and does not ask for your name, email, age or an account. What does reach us is: technical and usage information about the game, linked to a random installation identifier, which we use to fix crashes and improve the game (section 5); the record of a sale if you buy something (section 4); and, on Android, the random identifier of our game service with your purchases and, if you turn it on, your backed-up save (section 8). The game does not use your phone's advertising identifier and does not sell data. When there is a connection, it goes online for four things: your phone's store, for purchases (section 4); Firebase, for that technical information (section 5); Google AdMob, for the optional ads (section 6); and, on Android, our game service, to validate your purchases and, if you turn it on, back up your save (section 8). If you accept them, also to receive the game's news (section 7).
3. What is stored on your phone
The game stores your progress (day, coins, essences, hourglasses, reputation, recipes, ingredients, potions, garden, shop upgrades and decorations, customer stories, missions and visit streak), a log of your play day used to balance difficulty, a copy of what you bought and your options (sound, vibration, reduce motion, large text, notifications and whether you have seen the notice on the start screen), on Android the game service's random identifier (section 8) and, if you turn on the backup, its code, on your phone's storage. Your progress only leaves the phone if you turn on the backup (section 8); otherwise we have no access to it (the usage data in section 5 is separate and does not include your saved game). What is on your phone is deleted when you uninstall the game or clear its data in your phone's settings (the backup is not: see section 8).
4. In-game purchases
The whole story is free to play. If you buy something in the game's shop (the starter pack or essences), the payment is made by Google Play with your account, under its own terms and privacy policy: we do not receive your card or payment details. The store tells the game what you bought so it can be delivered, and the game notes it on your phone; on Android, it also confirms it with our game service (section 8). For accounting and refunds, the store gives us a record of each sale (order number, product, price, date and country or region), which we keep for as long as tax law requires. Essences live in your save: if you uninstall the game without having turned on the backup (section 8), any you have not spent are lost.
5. Crashes and game usage
On Android, the game uses Firebase Crashlytics and Google Analytics for Firebase, Google services, to send us —without your name, email or account—:
- Crashes: what error happened and where in the game, the game state at that moment (the day, the time of day and the graphics quality) and the last things that happened before it.
- Device data: model, Android version, language, game version and a random installation identifier, created when you install the game and changed if you reinstall it. It is not the phone's advertising identifier or Android ID.
- Game usage: when you start or continue a game, how the counter went each day (how many customers came, how many you served, how many left, how much you earned and your reputation), which potions you brew and their quality, which missions you claim, which customer stories you finish, when each chapter starts and when you reach the ending, what you harvest, what you gather in the forest, what you buy from the cart and in the shop, the gifts you get for watching an ad, which store products you tap and buy (with their price), and how smoothly the game runs on your phone.
- Approximate location (country or region), which Google infers from your IP address without storing it in full. Never your phone's precise (GPS) location.
Primary purposes: detecting, diagnosing and fixing crashes, and measuring the game's stability and performance. Secondary purpose: improving the game's design and difficulty with aggregate statistics. We do not use this data to identify you, for advertising, to build a profile of you or to make decisions about you, and it is set up that way for every player: no advertising identifier, no Google advertising signals and no link to ad services. Google keeps usage data for up to 2 months linked to the installation (after that only aggregate statistics remain) and crash data for up to 90 days. You can object to the secondary purpose as explained in section 11.
6. Rewarded ads
Ads are optional: they only appear if you tap “Watch an ad” on the missions screen, in exchange for a gift, and at most five a day. They are served by Google AdMob, a Google service. We set AdMob to show non-personalized ads (not based on your interests or on what you do in other apps), suitable for all ages and treated as child-directed for every player. The game does not use the Android advertising ID. Even so, to show the ad, count views and prevent fraud, AdMob collects your phone's IP address (which may be used to estimate an approximate location), a device identifier that is not used for advertising (the app set ID), how you interact with the ad, and performance diagnostics. That data goes to Google encrypted and is handled under Google's own privacy policy (policies.google.com/technologies/ads); we do not receive it. So that an ad is ready when you ask for it, the game loads one as soon as it opens, which means AdMob receives that data even if you never watch one.
7. Notifications
The game only sends you notifications if you say yes (in the question shown on the night of your first day at the shop or in Options; on Android 13 or later your phone's permission is also needed). There are two kinds, and each can be turned off separately in Options or in Android's notification settings:
- Reminders: that what you planted in the garden is ready to harvest, or that you haven't played in a few days; at most one a day, in the afternoon. Your own phone schedules them with what is already in your save: they send no data.
- News: occasional notices about the game (for example, new recipes, neighbors or events), which we send with Firebase Cloud Messaging, a Google service. To receive them, your phone gets a random notification identifier and registers it to the game's news topic; that identifier does not carry your name or account, we do not store or see it, and it stops being used if you turn news off or uninstall the game. Firebase tells us how many notifications were received and opened, as part of the usage data in section 5. We never send advertising or notices to buy.
8. Game service (purchases and backup)
On Android, the game connects to a service run by Lopand Solutions (apilgs.lopandsolutions.com) for
two things. To use it, the game creates a random identifier on your phone that carries no name,
email, age or account, and that is not the advertising identifier or the phone's Android ID.
- Validating your purchases: when you buy something, the game sends the service that identifier, the product and the purchase receipt Google Play provides. The service asks Google whether the purchase is real and whether it was refunded, so it is delivered only once and removed if refunded (never leaving your essences below zero). Also, every time you open or return to the game, even if you have never bought anything, it asks the service, with that identifier, whether any of your purchases was refunded; if you never buy or back up anything, the service does not store the identifier. We only pass Google an irreversible version (a hash) of the identifier. We keep the identifier and the record of each purchase (receipt, order number, product and dates) for as long as the game exists, because it is the record of what was sold, and Google's refund notices for up to 24 months.
- Backing up your save (optional): it starts off. If you turn it on in Options → “Respaldo de la partida” (save backup), the game uploads your save (the same one stored on your phone, section 3, without your options) and gives you a 12-character code of letters and numbers to recover it on another phone; from then on it backs up by itself while you play. We keep the save and a fingerprint of the code (not the code); it is deleted when you choose “Borrar mi respaldo” (delete my backup) or after 24 months without updates.
The service uses your IP address only at that moment, to limit abuse, and does not store it with this data. Everything travels encrypted (HTTPS). We do not use this data to identify you, for advertising or for profiling, and we do not share it with anyone.
9. Children
The game is for all ages, including children under 13, and follows Google Play's Families policy. It does not ask anyone for personal data or for their age, so every player is treated as a child. The technical information in section 5 is the same for everyone, carries no name or account, is used only to keep the game working and improve it (not for advertising or profiling) and does not include the advertising identifier or precise location. Ads are non-personalized, suitable for all ages and flagged as child-directed (under the US COPPA law), and AdMob is one of the ad services approved by Google Play for Families. Purchases follow the store's rules for minors' accounts (for example, parental approval). The game service (section 8) does not ask for personal data either: its random identifier is used only to make the game work (delivering purchases, preventing fraud and keeping the backup), never for advertising or profiling; the backup starts off and the game suggests that an adult keep the code. If you are a parent or guardian and want us to delete the information from your child's installation, write to us (section 11): for the data in section 5, as explained there; for the data in section 8, with the Google Play order number (it starts with "GPA.") or the backup code. We delete their backup (you can also delete it from Options) and the record of their purchases is kept as explained in section 8. Notifications start off and are only turned on if someone says yes (section 7).
10. Transfers
We do not transfer personal data to third parties. We process the game service data (section 8) ourselves and do not share it. For sections 5 and 7, Google acts as our processor: it provides the Firebase service to us, processes the data only for that purpose and may do so on servers outside Mexico (Firebase privacy). Payments are processed by Google Play and ads are served by Google AdMob; in those two cases Google handles the data under its own privacy policy.
11. Your rights
The data in sections 5 and 8 carries no name or account; if you want to exercise a right over it, we will ask for details that help locate your installation (for section 5, for example, the phone model and the date you played; for section 8, the Google Play order number or your backup code) and, if it cannot be found, we will tell you. With any question, to object to the secondary purpose in section 5, or to exercise your rights of access, correction, deletion or objection over that data or over the sales record (sections 4 and 8), write to soporte@lopandsolutions.com. To delete your progress, if you backed it up, first choose “Borrar mi respaldo” in Options → “Respaldo de la partida” (if you no longer have the phone, write to us with your code) and then uninstall the game or clear its data; for ad data, use your Google account; to stop receiving notifications, turn them off in Options or in Android's settings.
12. Changes
If a future version of the game starts processing other personal data, we will update this notice before releasing it, with a new version number and effective date.