Privacy Notice

Effective: October 7, 2026

Scope: this notice applies to the Pawity mobile application (iOS and Android). Last updated: 7 October 2026.

---

1. The Data Controller

Retroscope Ltd. has not appointed a data protection officer, as it is not required to do so under Article 37 of the GDPR. For data protection matters, you can reach us at the contact details above.

2. Introduction

Pawity is a community application for dog owners that offers walk tracking, map-based features, community elements (feed, packs, chat) and gamified elements (treats, badges, leaderboards). Its operation requires the processing of certain personal data.

This notice has been prepared in accordance with the provisions of Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR) and Act CXII of 2011 on Informational Self-Determination and Freedom of Information (Infotv.).

A separate data processing applies to the pawity.app website / campaign landing page — that is governed by the privacy notice published on the website.

3. What data we process, for what purpose and on what legal basis

Abbreviations for the legal bases: Contract = GDPR Article 6(1)(b) (provision of the service); Legitimate interest = Article 6(1)(f); Consent = Article 6(1)(a); Legal obligation = Article 6(1)(c).

3.1 Account and identification

• Data processed: email address, password (only in encrypted/hashed form), email verification (OTP) code, optional phone number, and, in the case of social sign-in (Apple, Google, Facebook), the identifier token and basic profile (name, email) received from the provider.
• Purpose: registration, sign-in, account security, change of email address.
• Legal basis: Contract.

3.2 Profile and dog data

• Data processed: nickname, profile picture, bio, linked accounts; the coordinates of the configured home zone (the reference point for map browsing); the name and phone number of an emergency contact (if you provide one); the dog's name, breed, date of birth, sex and picture; household/family members.
• Purpose: displaying the user and dog profile, operating the community features, displaying nearby content by default.
• Legal basis: Contract. Providing an emergency contact is voluntary; if you provide the contact details of a third person, you do so on your own responsibility and after informing them.

3.3 Location data

• Data processed: precise GPS positions recorded during a walk (latitude, longitude, accuracy, altitude, timestamp) and the route assembled from them; the current position used to query nearby walks/places when browsing the map; the last known position, rounded to a grid of approximately 1 kilometre, derived from the end point of a completed walk or, if you have not set a home zone and have no completed walk, from your current position measured while you use the app; the coordinates of places and reviews created by the user; the location sent as a message in a chat (by default an approximate point rounded to a cell of approximately 1 kilometre, or, if you explicitly choose so, a precise GPS coordinate).
• Purpose: recording and displaying a walk, displaying nearby walks/places/pals, proximity invitations, safety (hazard) alerts, the territorial ("local") classification derived from the starting location of walks for local leaderboards, making your profile discoverable to nearby users, determining the neighbourhood of accounts without a location for local notifications and neighbourhood content, gating location-based chat access, and sharing your location with the participants of a conversation when you explicitly ask for it (all of these are described in detail in Section 8).
• Details: see Section 8. Location data.
• Legal basis: Contract (for the operation of the walk feature) and Consent (the device's location permission; also for storing the last known position on the server). Sending your location into a chat additionally requires separate, per-occasion consent (see Section 3.4).

3.4 Communication

• Data processed: the content of chat messages, shared images, reactions, "treats", typing and presence indicators, the location sent as a message (an approximate or a precise coordinate), and when you last opened a conversation (read receipts).
• Purpose: messaging between users, walk and pack chat.
• Read receipts: in closed conversations (direct messages, walk chats and pack chats) the sender can see which participants have read their message, and when. This indicator cannot be turned off. Open conversations (place chats and post comments) carry no such indicator. If you take part in a walk chat anonymously, you appear in the read receipts under the same anonymous label, and your identity is not revealed.
• Sending your location as a message: in walk chats, pack chats and place chats you can share your location in a message. This requires separate, per-occasion consent, on top of the device's location permission: you granted that permission for a different purpose (recording walks, nearby content), so on its own it is not consent to your whereabouts appearing in a conversation. Before sending, a separate confirmation sheet tells you who will see the location and how long it stays there, and the same sheet is where you choose between an approximate and a precise location. The default is the approximate location: in that case it is not your real coordinate that is sent, but a point rounded to a cell of approximately 1 kilometre. A precise (real GPS) coordinate can only be sent by an explicit, separate choice. Both kinds are labelled in the conversation, so it is unambiguous for the recipients as well whether the location is precise or approximate. The location you send is visible solely to the participants of that conversation. In walk chats and pack chats, the message stays in the conversation until you delete it — there is no automatic expiry. In place chats, by contrast, a message containing your location is kept for at most 7 days and is then deleted automatically; there too you can delete it sooner yourself if you no longer want to share it.
• Legal basis: Contract; for a location sent into a chat, separate, per-occasion Consent.

3.5 Community (user-generated) content

• Data processed: feed posts (events, classified ads, hazard alerts, general posts), comments, uploaded photos, created places and reviews, alerts during a walk (photo, description, location), experience markers (photo, description, location). For lost/found dog reports: the microchip number, the location and time of the last sighting, and the contact phone number provided (which may also be the contact detail of a third person).
• Purpose: operating the community features, content sharing.
• Legal basis: Contract; for published (public) content, the display is based on Legitimate interest / the user's setting.
• Google Photos (optional): if you explicitly authorize it, we synchronize the photos associated with your walks, dogs or alerts to your own Google Photos storage. This is optional, can be turned off at any time, the access is stored as an encrypted token, and we only carry out the uploads you initiate.
• Profile gallery for your pawity friends: your profile shows an excerpt of up to six of your uploaded photos. Apart from you, only your accepted pawity friends can see it, and every photo follows the visibility of its own source. Your friend sees your dog photos because they can also see the dog's profile; a walk photo is included only if the walk itself is visible to them (public and "friends only" walks yes, private walks no); a post photo only if they can see the post as well, so a photo in a pack-targeted post never leaves the pack; and photos shared in chat never enter the gallery. A blocked user cannot reach your profile, and therefore cannot reach the gallery excerpt either.

3.6 Connections network and groups

• Data processed: pal (acquaintance) connections, invitation codes and their usage, pack (group) memberships and roles, blocking/muting settings.
• Purpose: managing community connections and groups.
• Legal basis: Contract.
• Invitation attribution: to link the opening of an invitation link with the installation, we store a short-lived, salted IP hash and a fingerprint hash derived from the device's characteristics (without the raw IP address and device identifier), solely within our own system, in order to correctly credit the invitation. This is not advertising-related and not cross-site tracking.

3.7 Gamification and view statistics

• Data processed: treat balance and history, earned badges, leaderboard rankings; a log of profile views (who viewed your profile, with a timestamp) for the premium "who viewed my profile" feature; the measurement of post reach is described in Section 3.16.
• Purpose: operating the gamified elements and motivational features, providing view feedback.
• Local leaderboard classification: for the "local" (nearby) leaderboards, the system derives a territorial classification from the starting location of your walks (the centroid of the starting points of your recent walks, or, if it is close to it, your configured home zone), solely so that you are classified to your real neighborhood and so that the ranking cannot be manipulated by arbitrary location-setting. Details are in Section 8.
• Legal basis: Contract (for the operation of the gamified features and the leaderboard); with regard to the manipulation-prevention purpose of the local classification, Legitimate interest.

The Application does not make any solely automated decisions producing legal effects concerning the User. The leaderboards and content recommendations are based on automatic calculation, but these do not constitute automated decision-making within the meaning of Article 22 of the GDPR.

3.8 Device, presence and notification data

• Data processed: push notification (FCM) token, the device's operating system and platform (iOS/Android), the application version, the last active time per device, and the account's last activity (last seen) timestamp for the presence indicator. To prevent abuse, we use Firebase App Check device attestation (Play Integrity on Android, Apple App Attest on iOS), during which a device integrity token is generated.
• Purpose: delivering push notifications (walk, community and system notifications), presence indication, abuse prevention.
• Legal basis: Contract (system notifications, presence) and Legitimate interest (abuse prevention); for marketing-type notifications, Consent (which can be turned off at any time in the application settings).

3.9 Purchase (premium subscription)

• Data processed: if we make a premium subscription available in the future, the management of the purchase will involve the processing of data by RevenueCat and the Apple/Google payment systems (user identifier, transaction and receipt data, entitlement status). The application does not see or store any bank card data — the payment is handled by the App Store / Google Play.
• Purpose: when a premium subscription is introduced, managing the subscription and verifying the premium entitlement.
• Legal basis: Contract.

3.10 Analytics, telemetry and error reporting

• Data processed: usage events (e.g. screen view, button press, API call metadata, walk completion), session identifier; error reports and crash data, and the associated device information, user identifier and approximate (city-level) location. Our error diagnostics provider (Sentry) receives the error reports with PII minimization: we attach the user identifier, we remove the email address before sending to Sentry, and we do not store the IP address. However, Sentry derives an approximate geographic location (country and city) from the IP address and stores it with the error report; this location is not precise and does not pinpoint a street or an address. No screen recording (session replay) is made.
• Purpose: measuring the operation of the application, detecting and fixing errors, improving the service. The approximate location is used specifically for troubleshooting: it helps us identify the user who reported an issue and handle support requests.
• Legal basis: Legitimate interest (the stable operation and improvement of the application, effective detection of errors).

3.11 Local data storage on the device (cookie-like technologies)

• Data processed: the application stores data in the device's local storage for its operation: authentication and session tokens, application settings and preferences (e.g. language, theme, notification settings), and a performance cache (offline availability and faster loading). The application does not use browser cookies and does not place any advertising or cross-site tracking technology on the device.
• Purpose: maintaining the signed-in state, preserving settings, ensuring offline operation and faster loading.
• Legal basis: Contract, or legitimate interest — storage that is strictly necessary for the provision of the service and serves operational purposes only. Since the application does not place any non-essential (e.g. marketing or tracking) storage technology, no separate cookie consent banner appears in the application. The locally stored data can be removed by uninstalling the application or by deleting your account. The cookies used on the website are governed by the Cookie Policy.

3.12 Source of the data and its provision

We receive most of the data directly from you. In the case of social sign-in (Apple, Google, Facebook), we receive the identifier and the basic profile (name, email) from the relevant provider, with your consent. Creating an account requires providing an email address (or social sign-in); without this, the service cannot be used. Providing profile, dog and location data is voluntary, but certain features work only in a limited way without them.

3.13 Abuse and scraper prevention (measuring location requests)

• Data processed: as preparation for future protection against unauthorised, bulk, automated extraction (scraping) of dog-place data, with every dog-place request the server keeps an hourly request counter per identifier. The measurement covers both the location requests of the application and the dog-place pages of the public website (pawity.app) and the endpoints that serve them. For a signed-in user the identifier is the user ID; for a website visitor who is not signed in it is a coarsened (generalised to network level, /24 or /64) and hashed (HMAC) form of the visitor's IP address, without storing the raw IP address. The system stores only an aggregated hourly count; it keeps no individual request log or browsing history.
• Purpose: network and information security, and preparing future protection against the unauthorised, bulk extraction of dog-place data.
• Legal basis: legitimate interests (Article 6(1)(f) GDPR): network and information security, and the future prevention of unauthorised data extraction (see Recital 49 GDPR).
• Important: on its own, this measurement currently has no active consequence: it does not restrict access, does not set up a login wall, does not change the content displayed, and does not flag any account. The measurement alone does not affect what you see in the application or on the website.
• For the measurement we use no cookies, no local storage (localStorage), and no device or browser fingerprinting. We measure search-engine robots in the same way as other visitors, without any difference in content.

3.14 Debugging and support-related access to your account

• What happens: a designated staff member of the controller, Retroscope Kreatív és Fejlesztő Szolgáltató Kft., may view your account in read-only mode, from your point of view, that is, they see what you see in the application (e.g. profile, dogs, walks, messages, settings). The access does not modify any data, and the staff member does not contact others on your behalf (does not send messages, tag, post or start walks).
• When: solely to investigate an error report or a support request, or to verify that the service works properly where the problem cannot be reproduced in any other way. The access is time-limited: it expires automatically after the specified period.
• Data processed: the data you store and see displayed in your account for the duration of the access, together with a log kept of the access: the time of the access, the identifier of the staff member who initiated it, the device used and the identifier of the account viewed.
• Purpose: detecting and fixing errors, user support, and operating the service securely and stably.
• Legal basis: legitimate interests (Article 6(1)(f) GDPR). In brief, the balancing test: investigating errors and providing support also serves your interests, and many errors can only be reproduced from your point of view. The processing is as narrow as possible: read-only, purpose-bound, time-limited and fully logged, so its impact on the rights and freedoms of data subjects is low. If you disagree, you may object (see Section 7).
• Transparency: we provide the access log on request at woof@pawity.app.
• Retention: we retain the access log for at most 1 year (see Section 6).

3.15 Offers near you: targeting based on your profile

• What happens: the Application may show offers from local service providers (e.g. vet, dog groomer, dog-friendly place) ("Offer from nearby"). Whether an offer is shown to you is decided by matching the targeting criteria set by the provider against your data within the Application: your dog's size, breed and age group (puppy, adult, senior), the number of walks you have taken, and whether you are a member of a pack. This happens at the moment of serving, within our own system, and we do not tell the provider whether you are the person the offer was shown to: the provider sees only aggregate figures (the number of impressions and clicks).
• What we do not do: we do not use location data for profile-based targeting (the "nearby" nature is handled separately, based on the radius set by the provider and your location at the time of the request, as described in 3.3 and Section 8), we do not pass personal data to the provider or any other third party, we do not use an advertising identifier, and we do not track you on other companies' sites or applications (see Section 11). This processing does not result in a solely automated decision producing legal effects concerning you.
• Data processed: your dogs' profile data (size, breed, age), the number of walks and pack membership, solely for the duration of the display decision, without storing a separate profile.
• Purpose: to make the offers relevant to you, and so that providers do not pay for impressions to people the offer does not concern.
• Legal basis: Legitimate interest (Article 6(1)(f) GDPR), maintaining the free operation of the Application and reaching local service providers. In brief, the balancing test: the data used are data that you have provided in the Application anyway and that are not special categories of personal data, the data are not passed to the provider, the only effect is that you see an offer or you do not, and the right to object is guaranteed. The core functions needed to use the Application (account, walks, community) are not affected by the targeting.
• Objection: if you do not want offers to be targeted at you based on your profile, you can object at woof@pawity.app (see Section 7). If you object, we exclude you from profile-based targeting, and from then on we may show you offers only in a way that is independent of your profile (e.g. based on proximity), or not at all.

3.16 Measuring post reach (reading activity)

• What we record: which posts you saw in the feed (the post appeared on your screen) and which posts you opened. We store one row per user and post: the post identifier, your user identifier and the time. The two kinds of data are kept separately.
• What we use it for: the reach statistics for the post's author ("how many people your post reached"), which is a premium feature. The author sees a number only; the author never sees who specifically saw or opened their post. If few people saw a post (fewer than 5), only a "seen by few" indicator is shown instead of an exact number. The number is visible only to the post's author with an active premium subscription, and to administrators.
• How long we keep it: the per-user rows are kept for at most 90 days and then deleted automatically. After deletion only a daily total per post remains (how many people saw it, how many opened it), which is not linked to any person and contains no user identifier.
• Opting out: if you switch off sending usage data (telemetry) in the app settings, we do not record a row linked to you. Your view still increases the post's anonymous counter, but that counter does not reveal who you are, and you are not counted as a unique viewer.
• What we do not record: views while not logged in, and your own views of your own posts.
• Deletion and access: when you delete your account, the rows recorded about you are deleted too; these rows are also included in your data export.
• Legal basis: Legitimate interest (Article 6(1)(f) GDPR): giving authors feedback on the reach of their posts and improving the community feature. In brief, the balancing test: the author receives aggregate numbers only, individual rows are short-lived, opting out is possible at any time, and the right to object is guaranteed (see Section 7).

4. Data processors and third-party providers

We use the following providers; they act in accordance with their own privacy policies:

To render the base map, the application uses the OpenFreeMap service (https://tiles.openfreemap.org), which is operated by Hyperknot Software Kft., in Hungary, within the European Union. To display the map, the client (your device) downloads map tiles (vector tiles) directly from the provider's servers; in the course of this, the device's IP address and the coordinates of the downloaded tiles (the area of the map view) reach the provider. By default, OpenFreeMap does not log the IP address; in the event of a security incident, it may log it temporarily, for up to 30 days, after which it is deleted. It may retain anonymized server logs (browser type, referring and exit pages, timestamp, operating system) for an indefinite period. The service does not require registration, an API key or a user account, and does not use cookies.

5. Transfer of data to third countries

Some providers — the services of Google/Firebase (e.g. Realtime Database, Cloud Messaging, App Check), Google sign-in and Google Photos, Apple, Meta, Sentry, RevenueCat and certain infrastructures of Expo — may also process data in the United States. In these cases, the data transfer takes place with appropriate safeguards (e.g. the European Commission's Standard Contractual Clauses – SCC, or certification under the EU–US Data Privacy Framework). The safeguard may differ from provider to provider; for details, the privacy policy of the relevant provider is authoritative.

OpenFreeMap (Hyperknot Software Kft.), which serves the map tiles, is a provider located in Hungary, within the European Union, and therefore this service does not fall within the third-country data transfers described above. To deliver its content, OpenFreeMap may also make use of Cloudflare (Cloudflare, Inc., United States of America) as a content delivery network (CDN); in this case, the device's IP address and the path of the requested map tiles may also pass through this infrastructure, subject to Cloudflare's own privacy policy.

Outgoing emails (e.g. verification codes, password resets, notifications) are delivered by the Amazon SES service of Amazon Web Services EMEA SARL, from its European Union region in Frankfurt (eu-central-1). Where access by the United States parent company may occur, it is safeguarded by the European Commission's Standard Contractual Clauses (SCC).

6. Data retention

• We process the data associated with your account for as long as the account exists.
• Account deletion: can be initiated from the application (Settings → Delete account) and also at https://pawity.app/fiok-torles. The deletion becomes final after a 30-day grace period; during this time the account can be restored by signing in again. After the grace period, we permanently delete the data or irreversibly anonymize it.
• Individual items of content (post, message, dog, walk) can also be deleted separately.
• We process the error and analytics data for a limited time, in accordance with the retention rules of the relevant provider.
• We keep the last known position (rounded to a grid of approximately 1 kilometre), whether it comes from a walk or from your current position measured while you use the app, as a single value per account, and retain it for at most 90 days from its last update; after that we delete it automatically. A new value overwrites the previous one; we keep no history. See Section 8. Location data for the details.
• How long a location sent as a message into a chat is retained depends on the type of conversation. In walk chats and pack chats, it is retained for as long as the message itself: until you delete it, with no automatic expiry. In place chats, by contrast, a message containing your location is kept for at most 7 days and is then deleted automatically; you can also delete it yourself sooner if you no longer wish to share your location (deleting it also removes the coordinate it contains).
• We retain the per-user rows of post-reach measurement (see 3.16) for at most 90 days; afterwards only the daily aggregate, which is not linked to a person, remains.
• We retain the log of debugging and support-related account access (see 3.14) for at most 1 year.
• In the case of a legal obligation (e.g. accounting, consumer protection), we retain the relevant data for the period prescribed by law.

7. Rights of the data subject (user)

Under the GDPR, you have the right to:

• access the data we process about you (a data export can also be requested from the application),
• rectify inaccurate data,
• have your data erased ("right to be forgotten"; account deletion provides this),
• restrict or object to the processing; this applies to processing based on legitimate interests, including debugging and support-related access to your account (3.14) and profile-based offer targeting (3.15): you can notify us of your objection at woof@pawity.app, and in that case we will no longer carry out the processing concerned (including access to your account) unless we have compelling legitimate grounds for it which override your interests,
• request data portability,
• withdraw your consent at any time in the case of processing based on consent.

You can submit your requests at woof@pawity.app. We will respond without undue delay, but no later than within the time limit prescribed by law.

8. Location data – detailed information

• Precise location determination takes place primarily during an active walk. From the start to the end of the walk, the application continues location determination with a foreground service — this records the route of the walk and operates the safety/proximity notifications. This continues even when the phone screen is locked or the application is not in the foreground; in such cases the system indicates the ongoing location determination (a notification, or the location indicator in the status bar).
• For the duration of the walk, the application continues location determination in the background (with the screen locked) as well; on iOS this may also use the system's "Always allowed" location access, which is, however, limited solely to the duration of the active walk. We do not track your location when there is no walk, and continuous location determination ceases when the walk ends.
• Continuous, real-time location tracking takes place only during a walk; the configured home zone, by contrast, is a static reference point provided by you, which we store for the default display of nearby content.
• When browsing the map, we use the current position to query nearby content.
• For the local leaderboards, the system derives a territorial ("local") classification from the recent starting location of your walks: it takes the centroid of the starting points of your most recent walks (at most 10, within 3 months), and if your configured home zone is close to it (roughly within 10 kilometers), it uses that. This serves solely so that you are classified to your real neighborhood and so that the ranking cannot be manipulated by arbitrary location-setting. We do not share your raw GPS coordinates with other users for this, and the classification ceases when your walk history or your account is deleted.
• During discovery (searching for nearby users, dogs, packs), based on your configured home zone, or in its absence your last known position, your profile may appear among other users' "nearby" results, typically within a radius of about 25 km at most. Whether you appear is governed by your profile visibility setting, and in such cases we do not show your exact coordinates to others (we only use the proximity classification).
• Your last known position is written primarily when a walk is completed, from the last point of the walk route that has already been uploaded. If you have not set a home zone and have no completed walk yet, the app may also send your current position measured while you use it, so that we can show you content and notifications relevant to your neighbourhood; this requires no new permission (we use the location permission you have already granted) and involves no background tracking. In every case we store the value rounded to a grid of approximately 1 kilometre, not your exact position. From a live position we update it only if it is more than 5 kilometres from the previously stored place; if you stay in the same area the stored place does not change and only the retention period restarts. We retain the value for 90 days from its last update: if it is not updated within that period, we delete it automatically, and from then on we prompt you to set your location. The stored value is not visible to other users; in "nearby" results only the proximity classification is used. You can obtain it in your data export, and it is removed when your account is deleted. We still do not store your exact current position persistently while you browse; only the rounded value described here.
• The gating of location-based chat access: in the application, certain dog-related places (e.g. dog parks, cafés, parks) have their own chat surface. To read and write in it, the application checks whether your current location (your current GPS position) or the destination of your active walk is connected to the given place. This check uses your location data in real time or from the metadata of the active walk, and serves solely to make the gating decision, not for persistent logging. Its purpose is to keep place chats relevant for users who are actually connected to the location.
• The location sent into a chat: in walk chats, pack chats and place chats you can share your location in a message. This does not follow from the device's location permission: before every single send, a separate confirmation sheet appears telling you who will see the location and how long it stays there. By default an approximate location is sent, rounded to a cell of approximately 1 kilometre — the same coarsening the product uses elsewhere, so your precise home position does not end up in the conversation. A precise GPS coordinate can only be sent by an explicit, separate choice, and the conversation shows which of the two it is. Only the participants of that conversation can see the location. In walk chats and pack chats, the message stays in the conversation until you delete it; there is no automatic expiry. In place chats, by contrast, a message containing your location is kept for at most 7 days and is then deleted automatically. Either way, if you change your mind, deleting the message also removes the shared coordinate.
• The non-identifying aggregation of on-site presence: on the chat surface of a given dog-related place, a non-identifying, aggregated count may appear showing how many people are currently near the location. This is an aggregated number only, does not reveal the identity or exact position of individual users, and does not count users who are on a privately visible walk.
• You control the visibility of a walk: public / pals only / private. This per-walk setting determines who can see your live position on the map and on the proximity surfaces during your active walk; in the case of a private walk, we do not display your live position to anyone. The visibility of your profile (who can find you in discovery) can be set separately from this, independently.
• The recorded walk route can be removed by deleting the walk or the account.
• The location permission can be withdrawn at any time in the device settings; the location-dependent features will then work in a limited way, but the other parts of the application remain usable.

9. Minors

The application is intended for persons who have reached the age of 16. We do not knowingly process the data of users under 16. If we become aware that we are processing the data of a person under 16 without an appropriate legal basis, we delete the data concerned. Our detailed rules on the safety of children are set out in the Child Safety Standards.

10. Data security

We transmit personal data over an encrypted connection (HTTPS); we keep the authentication tokens in secure storage (Secure Store) on the device. Access to the backend is restricted and password-protected; operator access to the backend requires two-factor authentication and an approved device, and is logged. To prevent abuse, we use Firebase App Check device attestation. We protect the data against unauthorized access with appropriate organizational and technical measures.

If you detect a data protection incident, you can report it at woof@pawity.app. In the case of a high-risk incident, we will inform the data subjects without undue delay and — in accordance with the law — the Hungarian National Authority for Data Protection and Freedom of Information (NAIH).

11. Tracking and personalization

The application does not carry out cross-site tracking: it does not combine user data with the data of other companies for advertising purposes, and it does not pass data to data brokers. Therefore the application does not display an App Tracking Transparency (ATT) prompt and does not use an advertising identifier (IDFA, or the Android advertising ID). The attribution hash used to correctly credit invitations, which exists solely within our own system (see 3.6), is not advertising-related and not cross-site tracking.

If we personalize the recommended content (for example, based on location data or the dog's data), we do so solely from the (first-party) data processed within our own system. Section 3.15 gives detailed information on the targeting of local provider offers, including the possibility to object.

12. Amendment of this notice

We update the notice as needed. We will inform you in the application about material changes. The version in force at any given time is available from the application and on pawity.app.

13. Remedies

You can submit a data protection complaint to the supervisory authority:

Hungarian National Authority for Data Protection and Freedom of Information (NAIH) 1055 Budapest, Falk Miksa utca 9–11. · ugyfelszolgalat@naih.hu · +36 1 391 1400 · naih.hu

If your rights are infringed, you can also turn to the courts.