Escobita Privacy Policy
1. Identification
This policy applies to Escobita, a card game for Android based on traditional Escoba, published under the developer name Escobita on Google Play.
Privacy contact: contact@escobita.com
General support: support@escobita.com
2. General principle
Escobita works mainly locally, on your own device. The current Beta 0.1 does not use any Escobita-operated servers to collect your matches, your gameplay activity, or any other data — there is no Escobita backend the app sends information to.
3. Data stored locally
Everything below is stored only in the app's private storage on your device:
- The name you choose to identify yourself in a match (a gameplay preference, not an account).
- Your preferences and settings: language, visual theme, difficulty, card size, active rules, volume, etc.
- Saved games, so you can resume a match in progress.
- A local technical log of plays from the current match, meant as an internal debugging tool, not as an account history or a match-recovery mechanism (saved games handle that, independently).
- Information needed to connect over Wi-Fi/local network or Bluetooth with another nearby device when you play in local multiplayer mode: recent connection addresses/identifiers, so reconnecting is faster.
- A device trust record: when you manually confirm you trust another device you've played with locally, that confirmation is remembered so you don't have to repeat it every time.
None of this data leaves your device except in the direct exchange described in section 4, and it is never sent to Escobita servers.
From the app's settings you can clear the local network connection history, forget remembered Bluetooth devices (including their associated trust), or clear both at once. These controls do not affect your saved games, your settings, or the technical play log.
4. Local multiplayer
When you play a local multiplayer match (Wi-Fi network or Bluetooth), your device exchanges directly with the other participant(s)' device(s) the information needed to set up and keep that match running (chosen name, table state, plays). This exchange is direct between the participating devices — it does not pass through any Escobita server, because none exists for this feature.
5. Bluetooth
Escobita requests Android Bluetooth permissions solely to discover/connect with other
nearby devices during a local multiplayer match. The device-discovery permission
(BLUETOOTH_SCAN) is declared with "neverForLocation", since
Escobita does not use the results of that scan to determine the user's physical location.
Escobita does not request or use approximate or precise location permissions.
6. Internet permission
Escobita declares the INTERNET permission, required on Android to use
network sockets, including the local-network connections used by Wi-Fi multiplayer. In
the current Beta 0.1, Escobita does not use this permission to send your matches
or your gameplay activity to its own servers.
7. Advertising, consent and purchases
The Android edition of Escobita distributed through Google Play may include interstitial ads provided by Google AdMob. Before requesting ads, Google User Messaging Platform (UMP) is used to manage consent and privacy choices where applicable. Google may process technical data such as IP addresses, device identifiers (including the advertising ID when available), ad interactions and diagnostics, subject to the service configuration and user choices.
Where applicable, you can consent, decline or manage the choices in the privacy message and revisit them using the privacy access provided by the app. Declining personalized advertising is not the same as purchasing the ad-free option. If permission to request ads cannot be established, Escobita must not request them.
Google Play may offer a one-time “Premium · No ads” purchase to remove Escobita ads, without a subscription. Google Play Billing processes the purchase and verifies entitlement; Escobita uses the result to enable the feature. Purchasing Premium does not necessarily disable all Google services.
See the Google Privacy Policy and AdMob privacy information.
8. Third-party services
The Google Play edition may integrate Google AdMob, Google User Messaging Platform (UMP) and Google Play Billing. These services may communicate with Google and process data under their respective policies, user privacy choices and the app's configuration. Availability of other Google Play services depends on the installed version. Escobita does not use its own servers to manage local matches.
Some screens may contain external links that open only when you select them. External websites have their own privacy policies.
9. Data retention and deletion
The local data described in section 3 stays on your device while the app uses it. The local network connection history, remembered Bluetooth devices, and the associated trust data can be deleted using the controls described in section 3. These controls do not delete your saved games, your preferences, or the technical play log.
Uninstalling Escobita removes the data stored by the app according to Android's and your device's own behavior. Escobita does not use its own cloud backup service for this data.
10. Security
The data described is stored in the app's private storage on your device. Local multiplayer connections use, where implemented, encrypted transport between the participating devices. No security measure is absolute; we cannot guarantee perfect protection against every scenario.
11. Children
Escobita does not ask for a date of birth or offer unrestricted chat with strangers. Advertising and related data processing must comply with the age rating, the target audience declared on Google Play and applicable child-protection policies. General consent choices do not replace special requirements for children.
12. Website feedback form
The escobita.com website includes a small feedback form about the Beta. The name and email fields are optional; the only required field is the comment. This data is sent by email to support@escobita.com solely to read and respond to your comment, and it is not used for advertising purposes nor shared with third parties. The form includes technical anti-abuse measures (a hidden field, a minimum-time check, and a per-IP-address submission limit) to filter out automated and abusive submissions; these checks do not identify real people, they only filter out bots. The IP address is processed in pseudonymized form (a technical hash, not the plain-text IP) solely for that submission limit, and is not used for any other purpose.
13. Changes to this policy
This is version 1.2, dated October 22, 2026. If Escobita changes its data practices, this page will be updated and the new date/version will be indicated.