1. Data controller and contact details
The controller of data processed in connection with the Gotta Pee! mobile app is AZ Tomasz Cedro, tax identification number (NIP): PL5361869704, ul. Artura Grottgera 14/1, 05-120 Legionowo, Poland.
For privacy, personal data and requests to exercise your rights, contact chcesiku.cedrotomasz@gmail.com or call +48 536 800 099.
2. What data may be processed
User account
- email address;
- the display name you provide;
- technical account, session and authentication identifiers;
- information needed to verify your email address and keep sign-in secure.
Location
- the device's current approximate or precise location, used to show nearby toilets, calculate distances and provide guidance;
- the coordinates of a submitted place, when you deliberately add a place to the database.
The user's current position is used to operate app features. It is not used for advertising profiling or to track the user across apps.
Nearest-toilet widget
If you add the widget, it may refresh the nearest place without opening the app, within the location permissions and the limitations of your phone's operating system. To find a place, the Supabase backend receives the available location coordinates, selected filters, and the local day of the week and time needed to check the toilet's opening hours. The widget settings and most recent result are stored on the device. The operating system determines how often it refreshes, so the result may be out of date. You can change permissions in your phone settings and remove the widget from the screen.
User content
- places you add and their features;
- photos selected from the gallery or taken with the camera;
- ratings and information about cleanliness, water, baby-changing facilities and whether a place exists;
- comments and reports requiring moderation;
- the time content was added and its author's identifier.
To allow a submission to be sent in the background and retried after a connection interruption or the app closes, an unsent submission and a reference to the selected photo may be stored temporarily on the device. This is not additional analytics or tracking.
Technical data
Infrastructure providers may process typical connection data, such as an IP address, the country determined at network level, timestamps, and information about the request, operating system version, browser or error, to the extent needed for security, operation and diagnosis of the service. This also applies to technical logs held by Supabase and its network providers.
3. Aggregate launch counter and analytics
Aggregate measurement of successful online launches
When you first enter the main part of the app, we retrieve the current configuration from our backend to display forms and filters correctly. The same functional request increases only the daily aggregate total of successful online launches. We do not send a separate analytics request.
The configuration request used for aggregation contains no session token, account, installation or device identifier, advertising identifier, location or event history. It contains an empty data object, a shared public project key and a generic client name. Our database does not create an individual event row: we store only the date and total number of successful online launches on that day.
However, the connection must travel over the Internet, so Supabase and its network providers may see the IP address, country determined by the network, time and general request information in technical logs. These are the same technical connection data that accompany delivery of the app configuration. We do not use them to identify individuals, link launches together or track people across apps or services.
The legal basis for processing the aggregate total is the controller's legitimate interest (Article 6(1)(f) of the GDPR) in measuring the operation and scale of use of the service and planning its development. We minimise the scope by not using identifiers or separate events and by aggregating immediately. Offline launches, launches interrupted before configuration is downloaded and requests not delivered by the network are not counted. You may object to processing based on legitimate interests by contacting the controller.
Website analytics
We use Google Analytics 4 on chcesiku.pl (measurement ID G-FXTJ25VR00) only after obtaining your consent. Without consent, the Google Analytics script is neither downloaded nor run.
After consent, Google Analytics may collect information about pages visited, approximate location derived from the IP address, device and browser type, the source of the visit and interactions with the website. The data is used to produce statistics and improve the website, not to display advertising.
The legal basis for processing is your consent. We store your choice locally in your browser. You can change it at any time using the button in the footer. Analytics data is retained according to the Google Analytics service's retention settings.
Optional statistics in the app
With your explicit consent, the app may use Google Analytics for Firebase to create general app-usage statistics, such as screens viewed and features used. We do not send comment text, photos or precise location for this purpose.
Firebase statistics are disabled by default. You can enable or disable them at any time in the app's “Settings”. This choice does not affect the functional configuration download or its aggregate measurement described above. Google Analytics for Firebase may process technical identifiers needed to operate the statistics, such as an app installation identifier.
With separate consent to “Google demographics and interests”, the app may provide Google with the Android advertising identifier or the IDFA on iOS, and a signal allowing measurement to be linked to Google information about users who are signed into a Google account and have also given the relevant consent. This is used only to create aggregate reports, for example by age range, gender and interests. We do not enable personalised advertising or remarketing on this basis.
On iOS, access to the IDFA also requires system permission through App Tracking Transparency. Refusing this permission does not block standard Google statistics, but prevents use of the IDFA. Enhanced measurement can be disabled at any time in the app's “Settings”; this blocks new data associated with the advertising identifier.
Optional Meta campaign measurement
After you accept the extended scope of measurement, we also transmit the fact that a new toilet was submitted, a rating was saved or guidance was started. These events do not contain the toilet's identifier or name, coordinates, star rating or submission content. They are used to assess campaign effectiveness. An earlier consent to registration measurement does not automatically enable these additional events.
With your separate consent, the app may use Meta App Events to measure whether an installation, the start of registration, a confirmed registration or a successful sign-in results from an advertisement for Gotta Pee! displayed on Facebook or Instagram services. We do not provide Meta with your email address, username, Gotta Pee! account identifier, precise location, photos, comments or names of visited places.
The Meta SDK may process information about the app and device, the IP address, a technical installation or app identifier, and the events listed above. The Android advertising identifier remains disabled. On iOS, the advertising identifier may be shared only after consent is given in the app and system permission is granted through App Tracking Transparency. Without consent, the SDK does not record campaign events. Consent can be withdrawn in the app's “Settings”; this blocks new events from being sent.
The legal basis for processing for this purpose is consent (Article 6(1)(a) of the GDPR). Measurement is used for attribution and assessment of advertising effectiveness, not for displaying adverts inside the app. Meta reports are aggregate reports and may differ from the total number of installations in the app stores and accounts in our database.
Non-personalised advertising in the app
The app may display banners supplied by Google AdMob on the home screen, toilet-details screen, guidance screen and places map. The controller may remotely disable all advertising or disable it on each of these screens separately. Banners are labelled by the advertising provider.
Advertising requests are sent only after the Google User Messaging Platform privacy procedure required in the relevant region has been completed. If Google does not allow an advertising request to be sent, the app does not display a banner and does not leave an empty space for it. Where required, a “Ad privacy” button appears in the app's “Settings”, allowing you to reopen Google's options.
The app requests only non-personalised adverts and restricts advertising content to a category suitable for a general audience. We do not provide AdMob with the device's precise location, Gotta Pee! account data, the name or identifier of a toilet, photos, comments or a history of visited places. However, Google may process typical data needed to deliver, secure and account for an advert, such as an IP address, general device and app information, consent settings, an approximate country derived from the connection, diagnostics, and information about an advert impression or click.
On iOS, we have disabled the key used to link data across apps from the same publisher. Refusing system permission through App Tracking Transparency does not by itself block a non-personalised advert from being displayed. The legal basis for processing data that requires consent is the user's consent; the remaining necessary technical scope is processed to deliver and secure the advert in accordance with the user's choice and Google's policies.
4. Purposes and legal bases for processing
- Providing the service and managing the account - performance of a contract or steps taken at the user's request.
- Displaying places, distances and guidance - device permission to access location and the user's request.
- Publishing submissions, photos, ratings and comments - carrying out a feature selected by the user.
- Moderation, prevention of abuse and security - the controller's legitimate interest in protecting users and data quality.
- Aggregate measurement of successful online launches - the controller's legitimate interest; service usage is measured during the functional configuration download, without a separate analytics request and without user identifiers.
- Usage statistics and advertising campaign measurement - user consent; this includes optional Google statistics and separately controlled measurement of installations and conversions in Meta.
- Displaying non-personalised banners - financing the app's operation; an advertising request depends on the outcome of Google's privacy procedure and does not contain precise location or user content.
- Handling questions, complaints and legal obligations - performance of a contract, a legal obligation or legitimate interests, depending on the matter.
Access to location, the camera and the gallery is optional and controlled in your phone settings. Refusal may limit features that need the relevant permission, but basic use as a guest remains possible.
5. Service providers and other recipients
Data may be processed by providers of services necessary for the app to operate:
- Supabase - authentication, database, photo storage, delivery of app configuration, aggregate measurement of successful online launches, technical logs and backend infrastructure;
- Apple and Google - app distribution, platform security and management of system permissions;
- Google Maps Platform - providing maps and satellite view inside the current app. Displaying maps requires connections to Google relating to the area being viewed. The SDK may process technical device and connection data, an IP address, SDK identifiers, diagnostics and map interactions. This is separate from optional Firebase analytics and Meta measurement; disabling those statistics does not disable map services. See Google's privacy policy for more information;
- Apple Maps or Google Maps - additionally, when you choose to open a route in an external map app;
- Mapbox (older app versions) - versions released before the switch to Google Maps may still download map tiles and styles from Mapbox. Mapbox may then receive technical request data, such as the IP address, parameters of requested tiles and the app's public token, in accordance with the Mapbox privacy policy. This description remains relevant to users of those older versions;
- Google Analytics - website visit statistics, only with consent;
- Google Analytics for Firebase and Google Signals - optional app-usage statistics and, with separate consent, aggregate demographic statistics created using the advertising identifier and Google information;
- Google AdMob and Google User Messaging Platform - displaying non-personalised banners, managing privacy choices, advertising security and accounting;
- Meta Platforms Ireland - optional measurement of installations and conversion events associated with Facebook and Instagram campaigns, only with consent in the app settings and, on iOS, in accordance with the system App Tracking Transparency choice;
- providers of website hosting and contact email services.
Public place information, photos, aggregate ratings and comments may be visible to other users. We do not publish the author's email address.
Some entities may operate outside the European Economic Area. In that case, transfers take place using mechanisms provided for by law, such as an adequacy decision or standard contractual clauses.
6. How long we retain data
- account data - until the account is deleted, except for information that must be retained by law or to protect against abuse;
- user content - until account deletion, content deletion, completion of moderation or loss of usefulness; public place data may be anonymised and retained as community information;
- unsent submissions in the app's local queue - until they are successfully sent or the app's data is deleted from the device;
- correspondence - for the period needed to resolve the matter and defend against claims;
- technical and security data - for the period required to diagnose issues, secure the service and fulfil legal obligations;
- daily aggregate totals of successful online launches - for the lifetime of the product or until they are no longer useful; we assess the continued need to retain them at least once a year; the totals contain no identifiers and do not allow an entry for a specific person to be deleted;
- infrastructure providers' technical logs - according to the retention period of the relevant service and plan, for the period needed for security and diagnosis;
- optional app statistics data - according to the Google Analytics for Firebase retention settings, only with consent;
- optional campaign measurement data - according to Meta services' retention policies and settings, only with consent; withdrawing consent blocks new events from being sent from the app;
- data relating to advertising and privacy choices - according to Google AdMob and User Messaging Platform retention policies; available options can be reopened in the app where required by the relevant region.
7. Your rights
Depending on the legal basis and circumstances, you have the right to access, rectify and erase data, restrict processing, data portability, object to processing and withdraw consent. Withdrawing consent does not affect the lawfulness of earlier processing. You may object to processing based on legitimate interests by contacting us. An aggregate total cannot be attributed to a particular person, nor can a single launch be removed from it.
You may also lodge a complaint with the President of the Polish Personal Data Protection Office (Urząd Ochrony Danych Osobowych). You can delete your account in the app or by following the instructions on the Delete your account and data page.
8. Security
We use encrypted HTTPS connections, data access controls and backend security rules. However, no method of storing data provides an absolute guarantee of security. Do not submit data in comments or photos that you do not want to make public.
9. Children
The app is not specifically directed at children and is not intended to knowingly collect their data. Anyone who cannot independently give valid consent under the law of their country should use the app with the involvement of a parent or guardian.
10. Changes to this policy
This policy may be updated when app features, service providers or laws change. The current version and its effective date will always be available at this address. We may also notify users of significant changes in the app.