← Home

Introduction

HappyStop: Playground, Toilet and Water (“the App”) helps you find public toilets, playgrounds, and drinking-water points on a map, optionally contribute community ratings and opening-hour reports, and start turn-by-turn navigation in an external maps application. This Privacy Policy describes how information is processed when you use the App. It applies to the App distributed on Google Play (package name eu.zlidak.happystop).

By using the App, you agree to this policy. If you do not agree, please do not use the App.

Data we process and why

Map and place data (OpenStreetMap). Places shown on the map (e.g. toilets, playgrounds, drinking water) are retrieved from OpenStreetMap (OSM) using public APIs (including the Overpass API). That data is created and maintained by the OSM community and may contain names, coordinates, and tags. We do not control OSM content. Queries are sent to third-party servers you can read about in OSM/Overpass documentation.

Search (geocoding). When you search for a place by name, the App may send your query text and related parameters to a Nominatim-based service (OpenStreetMap’s search) to obtain coordinates. That request leaves your device and is processed by the service operator under their terms.

Approximate location. If you grant location permission, the App uses your device location to center the map on you and to request nearby places around that position. Location is used for these features; we do not describe a separate “real-time location tracking” product beyond what the OS and our APIs require to run the App.

Device and app context. Like most apps, Google Play services, Firebase, and ad networks may process technical data such as app identifiers, IP address, device type, diagnostics, and crash data to provide security, deliver ads, and operate the service. See the sections on Firebase and advertising below.

Community features (Firebase Authentication & Firestore)

Ratings and optional opening-hour reports are stored in Google Firebase (Firestore database). To reduce abuse and enforce simple limits, the App uses Firebase Authentication with anonymous sign-in: a random Firebase user identifier (UID) is created on your device. We do not require your name, email, or phone number for this.

What is written to Firestore. The App may create or update documents such as:

  • Aggregated POI summaries (e.g. average rating counts and fields derived from the latest community report) under a collection such as happyStop_poi_data.
  • Individual reports under each POI’s reports subcollection (e.g. star rating, whether you mark the place as closed/unavailable at reporting time, optional opening-hours choice, timestamps, and your Firebase UID).
  • Daily per-user limits (e.g. which POIs you already rated today and how many distinct POIs you rated in a calendar day) under your user path under users (e.g. ratingDaySlots), keyed by your Firebase UID, not by your real name.

Limits (as implemented in the App). The App may block additional submissions when you exceed the same-day limits (for example: one rating per POI per local calendar day, and a maximum number of distinct POIs rated per day). These checks are enforced in the client and should be backed by server-side rules in your Firebase project.

What we do not claim. Community data is user-generated and may be inaccurate. Icons and “open/closed” hints are derived from the latest reports and rules in the App and are not official opening hours from venue operators.

Advertising (Google Mobile Ads)

The App may show banner advertisements and interstitial (full-screen) ads, for example before opening external navigation, depending on build configuration and ad availability. Ads are served by Google through the Google Mobile Ads SDK (AdMob).

Google may use advertising identifiers, IP address, device information, and app-related signals to personalize or measure ads, subject to your settings and applicable law. Where required, you may see a consent or choices flow (e.g. EEA/UK). You can also limit ad personalization in your device settings.

Test ads. In debug or emulator builds, test ad units may be used.

Subscriptions (Google Play Billing)

The App may offer a subscription (e.g. “Premium”) through Google Play to remove ads or unlock related benefits. Payments and subscription status are handled by Google. We receive purchase state from Google (e.g. whether you have an active entitlement for this product) to adjust the App experience. We do not store your full payment card details in the App; those are processed by Google.

You can manage or cancel subscriptions in the Google Play app under Payments & subscriptions.

Legal bases (EEA/UK users)

Where GDPR applies, we rely on contract (providing the App you asked for), legitimate interests (security, fraud prevention, analytics compatible with the service), and consent where required (for example, certain advertising or non-essential cookies). You may withdraw consent where processing is consent-based, without affecting the lawfulness of processing before withdrawal.

Retention and deletion

Community data in Firestore may be retained until the Firebase project owner deletes it or implements deletion policies. If you want community posts tied to your anonymous Firebase account removed, contact us using the channel on the Play Store listing; we may need your Firebase UID or other diagnostic information to locate data (subject to technical feasibility).

Uninstalling the App does not automatically erase data already stored on Firebase.

Security

We use industry-standard providers (Google, Firebase) and secure transport (HTTPS). No method of transmission over the Internet is 100% secure.

Children

The App is not directed at children under 13 (or the age required by your country). We do not knowingly collect personal information from children for the purpose of community accounts beyond what the OS and Firebase require for anonymous technical operation. If you believe a child has provided information, contact us.

International transfers

Firebase, Google Play, and ad services may process data in the United States and other countries where Google or partners operate. Google provides appropriate safeguards (e.g. standard contractual clauses) as described in Google’s privacy documentation.

Changes

We may update this Privacy Policy. The “last updated” notion is reflected by the version shipped with the App. Continued use after changes means you accept the updated policy.

Contact

For privacy requests or questions, use the contact details published on the Google Play store listing for this App.