Feasty

Privacy Policy

The binding version is the Polish one (Terms §14.4). EN/DE are courtesy translations.

Version: privacy:0.10.0 | Effective date: 14 November 2026

This document covers the Feasty consumer app. Personal data of restaurateurs collected through the B2B Claim verification flow and the Feasty Business panel is governed by a separate privacy policy — it will be available at business.feasty.com.pl once published (planned before the first B2B monetisation). Until the dedicated B2B privacy policy is published, restaurateurs may contact the Controller at contact@feasty.com.pl regarding the processing of their data in the B2B Claim procedure — we respond individually with the full scope of information required by Art. 13 GDPR.

Definitions

For the purposes of this Privacy Policy, the following terms have the meanings set out below:

1. Data Controller

The controller of your personal data is Radosław Rodak, a natural person operating under the Polish "non-registered business activity" scheme (Art. 5(1) of the Act of 6 March 2018 — Entrepreneurs' Law), correspondence address: ul. Boya-Żeleńskiego 34, 20-435 Lublin, Poland. The Application currently operates in an early-access, free phase and does not generate revenue. Upon exceeding the non-registered business threshold or commencing registered business activity, this Privacy Policy will be updated with registration numbers (NIP, REGON, KRS) along with a version bump requiring renewed consent.

For matters relating to the protection of personal data, please contact us at: contact@feasty.com.pl.

Data Protection Officer (DPO). The Controller has not appointed a Data Protection Officer because none of the conditions under Art. 37(1) GDPR are met: the Controller is not a public authority; the core processing activities do not consist of operations requiring regular and systematic monitoring of data subjects on a large scale, nor large-scale processing of special categories of data (Art. 9) or data on criminal convictions (Art. 10). This determination will be reassessed when the non-registered business threshold is crossed or when features that change the scale of processing are launched.

2. Data we collect

Depending on how you use the Feasty app, we process the following categories of data. For each item we indicate whether providing the information is mandatory (required to create an account or use the feature) or optional (you can use the Application without providing it — Art. 13(2)(e) GDPR).

Account data

Activity data

Technical data

Location data

Your approximate GPS location — at the moment when you search for nearby restaurants or start a Matchmaker session. If you choose the automatic theme, the Application also reads the device's last known position to match its appearance to the time of day — only if you have already allowed location access in the system, and only on the device: this position does not reach us. We do not store a history of your location.

Contacts from your phone's address book (optional)

If you use the "Find friends" feature we will ask for one-time permission to access your phone's address book. You can revoke this permission at any time in your device's system settings (iOS Settings → Feasty → Contacts / Android Settings → Apps → Feasty → Permissions).

Once permission is granted:

Purpose: to show you which of your address-book contacts are already on Feasty so you can follow them without manually searching. The feature is fully optional — the Application works without this permission; without it there is no "Find friends from contacts" screen and no suggestions from your contacts in the "People you may know" bar. We remember the result of the latest match (Feasty accounts found in your contacts) only on your device, to show in the bar people you do not follow yet; each time we show it, we check that your permission is still in place. Matching does not repeat by itself — you start it.

Legal basis: Article 6(1)(a) GDPR (User consent expressed by granting the system permission). Revoking the permission in system settings is equivalent to withdrawing consent — from that moment the feature stops working and any earlier matches are no longer displayed.

Analytics data (what we do NOT collect)

Feasty intentionally does NOT use behavioral analytics tools such as Google Analytics for Firebase, Mixpanel, Appsflyer or Adjust. We do not profile your habits, do not build marketing behavior models, do not sell data to third-party advertisers.

We collect only:

We do not use behavioral tools, so we do NOT ask you for consent to cookies or tracking modules. The Application stores on your device only what is strictly necessary to provide the service you request (Art. 399(3)(2) of the Polish Electronic Communications Law (PKE)):

We do not store identifiers for analytics, advertising or tracking on your device. Should we enable analytics in the future, we will ask for your explicit consent before activation.

Anonymous metrics for B2B partners

When you tap "Call", "Reserve", "Directions", "Menu", "Share", a delivery link or add a place to your "Saved" list, we increment an anonymous counter of how many such actions happen per restaurant per day. The counter:

Restaurateurs who have claimed their venue in Feasty Business (B2B Claim procedure, manually reviewed by an administrator) see daily aggregated statistics of THEIR restaurant in their dashboard panel:

Under the Premium plan, restaurateurs additionally see anonymised industry comparisons — the median score and tag distribution across a set of at least 5 similar venues in the same cuisine and area. The restaurateur NEVER sees the names of competitors. We do not disclose the composition of the comparison set either — we only show "compared with 5-9 / 10-19 / 20+ similar venues". Your venue may be used in comparisons presented to other B2B partners in your category and location — but only as an anonymised median, never by name.

If a category (tag) would contain fewer than 5 unique review authors, the owner panel shows "Insufficient data" instead of a percentage — this protects authors of individual reviews from identification (k-anonymity threshold, Art. 4(5) GDPR).

Legal basis: counters are anonymous aggregates within the meaning of GDPR Recital 26 — without person-level identifiers they do not allow direct or indirect identification of a User (k-anonymity threshold of 5 applies to tag distribution). To the extent that the moment of the tap might be momentarily linked to your session on the server side before the counter is incremented, the legal basis is Art. 6(1)(f) GDPR (legitimate interest of the controller in metric integrity + interest of restaurateurs in receiving aggregated traffic).

Right to object (Art. 21 GDPR): you may object at any time to your anonymous taps being counted in B2B metrics by writing to contact@feasty.com.pl. Once your objection is recorded, future interactions stop being counted (we flag the account so the server honours the objection on every subsequent counter increment). The objection cannot apply retroactively — the counters are already anonymous and contain no identifier that could be removed.

Matchmaker

Matchmaker is a feature for choosing a restaurant together — you and your friends join a single session via a 6-character code and swipe through 20–30 nearby venues to quickly pick a place for a shared meal.

Session data processed:

Sessions are stored as single documents in the database and automatically closed after 24 hours of inactivity. A complete session (members + swipes) is deleted within 30 days of being closed. You can manually delete any session you have created.

We do not use Matchmaker data for profiling or to train any models — it operates strictly in real time for session participants.

Legal basis: Art. 6(1)(b) GDPR (contract performance — providing the social feature you knowingly joined).

Feasty AI — generated restaurant summaries

The Application uses a generative AI model (Vertex AI Gemini, processed exclusively within European Union member states) to produce two types of summaries visible on the restaurant screen and a monthly report for the venue owner:

Guarantees enforced by our processing:

Audit logs: every generation is recorded in an internal audit collection (aiOutputAudits) with the SHA-256 hash of the model instruction (the raw instruction is never stored), a truncated result (≤ 4096 chars), model metadata and a 90-day retention period. Purpose: internal quality audit and documentation for defending against potential restaurateur claims (AI Act §11.2).

Legal basis for Level A generation (restaurant summary from public community reviews): Art. 6(1)(f) GDPR — legitimate interest of the controller and Users in receiving a synthetic overview of content that Users publish as public Content in the application. Reviews passed to the model come from already-public Content; the Art. 21 objection (described above) excludes a given person's contribution from the aggregate.

Legal basis for Level B generation (personalised intro for you, built from reviews by people you follow): Art. 6(1)(f) GDPR — legitimate interest of the User (you) in receiving a personalised recommendation based on the opinions of people you follow, and the legitimate interest of those people in having their opinions help the people they have shared them with choose restaurants. The model receives the rating and an excerpt of the text of reviews, without names or identifiers, and a review shared with followers only — solely for an intro for a person who can read it; the restaurant summary for everyone (Level A) uses only public reviews. Any such person may at any time exercise the Art. 21 objection against their contribution — their data is then excluded from both Level A and Level B.

Legal basis for the monthly report: Art. 6(1)(f) GDPR — the legitimate interest of the controller and of the venue owner in understanding the opinions that Users have published about the venue as public. The “Exclude my reviews from Feasty AI” option also excludes your reviews from the report.

Legal basis for audit logging: Art. 6(1)(c) GDPR (legal obligation arising from AI Act Art. 50 — origin transparency for AI-generated content) and Art. 6(1)(f) GDPR (legitimate interest of the controller in defending against claims related to AI-generated content).

Photos in reviews

Photos you attach to restaurant reviews are stored in Cloud Storage in the European-region bucket. To clarify:

Tags in reviews

In a review you can tag the people you were at the venue with — only among people with whom you follow each other. With the review we store the tagged person's identifier, their name and profile photo; if they change them, they also change in the review.

The legal basis is the performance of a contract (Art. 6(1)(b) GDPR).

Comments on reviews

A review can be commented on by its author and by people connected with the author by a follow, in either direction. Under a public review, the venue it concerns may also reply: the owner of a claimed venue writes, and the comment is shown under the venue's name.

The legal basis is the performance of a contract (Art. 6(1)(b) GDPR). Comments can be reported, and we moderate them in the same way as reviews.

Split the bill

The "Split the bill with friends" feature helps you divide the cost of a shared meal. Within it we process:

Legal basis: Art. 6(1)(b) GDPR (performance of the contract — providing a feature you knowingly use). We do not use this data for profiling or to train models.

Feasty Events — group outings

The "Feasty Events" feature ("Propose an outing") helps you plan a get-together with friends. Within it we process:

Legal basis: Art. 6(1)(b) GDPR (performance of the contract — providing a social feature you knowingly use).

Venue Faces

A venue owner may invite you to appear on their listing as a "Venue Face" — e.g. head chef, owner or manager. The feature works only with your consent:

Legal basis: Art. 6(1)(a) GDPR (consent) and Art. 81 of the Polish Act on Copyright and Related Rights (dissemination of likeness with authorisation).

Shared lists

Your own lists (other than the default "Favorites" and "Want to go") can be shared with friends:

Legal basis: Art. 6(1)(b) GDPR (performance of the contract). The recipients of data visible on a shared list (e.g. your name as the author of an entry) are the other co-authors of that list. The notice-and-action mechanisms are described in Art. 16 DSA.

Followed guides. When you follow a guide (a creator's list or a Feasty editorial list), this is visible on your profile — to people who can view your profile under its privacy settings — and on the guide's cover, where people who follow you see your photo among the followers; everyone else sees only the number of followers. You can stop following at any time.

Table reservations

Reservations. When you want to book a table through the Application (or the feasty.com.pl website, if the restaurant allows it), Feasty intermediates in passing on your request — the reservation is accepted and confirmed by the restaurant. We pass to the chosen restaurant the data needed to handle the reservation: the first name you enter in the reservation form (when booking from your account the field is prefilled with the first part of the name in your profile — you can change it or add your surname before sending), the number of guests, the date and time and any notes you enter, and when booking through the feasty.com.pl website also your email address and, if you provide it, your phone number. The restaurant becomes a separate controller of this data and may use it only to handle your reservation (confirmation, contact in case of changes) — not for marketing or any other purpose; our agreement with the restaurant obliges it to do so. If the restaurant publishes its own privacy policy, you can read it before booking. Legal basis: taking steps at your request prior to entering into a contract and performance of that contract (Art. 6(1)(b) GDPR) — this applies both to the reservation request and to a confirmed reservation. We keep reservation data for as long as the reservation is being handled and for 90 days afterwards in case of a complaint or dispute (e.g. a no-show report), after which we delete or anonymise the contact data. If you book as a guest, without an account, before sending the form you will see information about the data controller and about the data being passed to the restaurant, and you will confirm that you have taken note of it; no account is created in that case. Reservation status notifications (confirmation, cancellation, reminder) are sent by us (Feasty), not by the restaurant.

Reservation block. A restaurant may refuse to accept reservations from you if you have repeatedly failed to show up for a confirmed reservation without cancelling it. The threshold here means 3 documented no-shows at the same restaurant within 90 days — a no-show counts as documented only if the restaurant marked it after the time of a reservation you did not cancel. The decision is made by the restaurant — it is not taken automatically by the Application. The restaurant must impose the block actively, confirming it itself; the Application does not impose it on its own, even once the threshold is exceeded. The threshold itself works only in your favour: the Application can only prevent a block below the threshold and never imposes one on its own initiative. When making this decision, the restaurant has access only to those elements of your reservation history at its venue that are directly necessary to assess whether it is justified — the dates and statuses of the no-shows and information about earlier cancellations or explanations relating to those events — excluding data from other venues, aggregate indicators and information unrelated to the assessment of this threshold. We (Feasty) will send you the explanation of the reason for the refusal on the restaurant's behalf — by email; in the Application you will see a notice about the block stating that the details have been sent by email. The message will state the facts on which the decision is based, its basis in the Terms, the duration of the block, and how and by when you can appeal. If you believe the refusal was unjustified (e.g. a no-show was marked in error), you can contact the restaurant and also appeal by email to moderation@feasty.com.pl (for reservations made from an account — also in the Application). The appeal will be reviewed by a human, and the controller will respond without undue delay and in any event within one month of receiving the request. The block described above applies only to the given restaurant, expires automatically after 3 months and is not transferred between venues. We keep information about the block for 3 years after it expires or is lifted, and an appeal for 3 years after it is decided, solely in case of claims relating to the block.

Venue data, suggestions and videos about venues

Data about food and drink venues. We obtain information about venues — name, address and location, type of venue, phone number, website and opening hours — from publicly available sources (the open Overture Maps dataset and the venue's own website), from Users (venue data suggestions, section 5.7 of the Terms) and from the venue owner. Where a venue is run by a natural person, e.g. as a sole trader, some of this information may be that person's personal data. We process it to inform Users about venues, on the basis of our legitimate interest (Art. 6(1)(f) GDPR), for as long as the venue is presented in the Application. The restaurant owner may object (Art. 21 GDPR) by email to the address given in "Contacting us"; we consider each objection individually, within one month. The objection covers data identifying the restaurant owner, not Users' reviews — unless a review contains their personal data beyond the venue name.

Suggestions of venues and venue data changes. When you suggest a new venue ("Add a place") or a change to a venue's data, we store the content of the suggestion (e.g. name, address, location on the map, cuisine), the date and your account identifier. The identifier is not visible to other Users; we need it to notify you of the outcome (in your Inbox and, when a new venue is accepted, also by a notification) and — if we restrict the suggestion as prohibited content — to give you a statement of reasons and allow an appeal (Arts. 17 and 20 DSA; legal basis: Art. 6(1)(c) GDPR). We keep the suggestion until it is decided and then for the appeal period (6 months) plus 30 days; after that it is deleted automatically. Your suggestions are part of your data export.

Creators of videos about venues. Next to venues and on Feasty editorial lists we show links to publicly available videos about venues, published by their authors on YouTube, TikTok or Instagram, together with the name of the author's channel. For this purpose we process data of creators who do not have to be Feasty Users: the channel name, the channel addresses on those platforms and the video addresses — obtained from their public channels. We do not download thumbnails, titles or the creator's image; we do not embed or copy videos. Legal basis: Art. 6(1)(f) GDPR — the legitimate interest of Feasty and Users in identifying the source and author of material about a venue. We keep the data for as long as the link is visible in the Application. A creator may object at any time (Art. 21 GDPR) by email to the address given in "Contacting us" — we do not require a reason; we then remove the links and the channel data, keeping only the platform name and the account name so as not to add the channel again. If a creator opens a Feasty account, they can ask us to connect the channel with their account — after confirming that the channel belongs to them, the channel name shown with the videos leads to their profile.

3. Purposes and legal bases of processing

Service delivery (Art. 6(1)(b) GDPR — contract performance)

Security and abuse prevention (Art. 6(1)(f) GDPR — legitimate interest)

Product communication (Art. 6(1)(a) GDPR — consent)

Pre-registration waitlist (Art. 6(1)(a) GDPR — consent)

If, before creating an account, you leave your email on the "Request access" screen, we process this data for a single purpose: sending you one notification with an invitation to the app when we open the next access wave. Data collected: email address, timestamp of the entry, timestamp and version of this Privacy Policy at the moment of consent, source of the request, hashed (SHA-256 with a server-side pepper) IP address for spam-source auditing, truncated user-agent. Legal basis: your explicit consent (Art. 6(1)(a) GDPR). Without ticking this consent in the form, we do not store your email at all — server-side validation rejects the request.

Waitlist data is not combined with registered users' data, is not used for analytics or profiling, and is not transferred to any third parties. The invitation email is sent personally from the Controller's address.

Retention: until (a) we send you an invitation code — we then delete your email address, the IP address hash and the browser information, and keep only proof that consent was given: a hash (SHA-256) of the email address, the date of consent, the Policy version and the date of the invitation — for 3 years, in case of claims; OR (b) a decision not to grant access — the entry is manually deleted; OR (c) at most 12 months from the entry date without an invitation being sent. You may withdraw consent and request deletion at any time by writing to the address in section 1 — the entry will be deleted within 30 days.

Contacting us. Our addresses: contact@feasty.com.pl — general matters, complaints and your rights under section 7, including the right to object; moderation@feasty.com.pl — reports of content (including of your likeness) and appeals against our decisions, including against a reservation block; legal@feasty.com.pl — for public authorities only. When you write to us at any of them, we process your email address, the content of your message and any data you provide in it. We do this to reply and handle your matter: the legal basis is our legitimate interest in conducting correspondence (Art. 6(1)(f) GDPR) and, where the matter concerns a contract with you, its performance (Art. 6(1)(b) GDPR). Email is handled by Google (Google Workspace). We keep correspondence until the matter is resolved and then for 3 years in case of claims.

4. Recipients of data

We transfer your data to the following categories of recipients (processors operate under data processing agreements concluded with us):

Map. From version 1.0.6 of the Application, the map is displayed by the open-source library MapLibre. The base map (streets, water, green areas, labels) comes from OpenStreetMap data, and the venues on the map come from our database. The Application downloads map tiles and label fonts from our domain mapa.feasty.com.pl, which is operated by Cloudflare, Inc. With each download, Cloudflare receives your device's IP address, technical information about the Application and the device (including the name and version of the Application) and information about which map tiles you download — when the map shows your surroundings, this reveals your approximate location. Cloudflare processes this data on our behalf, as our processor, solely to deliver the map tiles; for the data it uses to protect its network against attacks, it acts as a separate controller under its own privacy policy. We do not store this data. Processing also takes place outside the EEA, including in the United States (section 5). The "you are here" dot is drawn by the Application itself, based on the location provided by your device's system — the map provider does not receive it. The map does not store identifiers or cookies on your device; the only thing kept on the device is a cache of downloaded map tiles and pin images, so that they do not have to be downloaded again. The legal basis for transferring data to Cloudflare is our legitimate interest in showing venues on a map (Art. 6(1)(f) GDPR).

Google map in earlier versions of the Application. In versions of the Application earlier than 1.0.6, the map is displayed by the Google Maps SDK. When the map is displayed, Google receives your IP address, technical information about the device and the Application, crash data of the SDK and information about how you use the map (panning, zooming) and which area you are viewing — when the map shows your surroundings, this reveals your approximate location. On the place selection screen in Matchmaker, the map SDK itself shows your location. The SDK stores an identifier and cookies on your device, which Google also uses for its own purposes (statistics, abuse prevention, improving its services) — to that extent Google acts as a separate controller, under the Google Privacy Policy, and decides on the retention period itself. The data is also processed outside the EEA, including in the United States (section 5). The legal basis for transferring data to Google when the map is displayed is our legitimate interest in showing venues on a map (Art. 6(1)(f) GDPR). After updating to version 1.0.6, the files previously stored by the Google SDK remain on your device until the Application is uninstalled — the new version does not use them.

Application updates. Each time it starts, the Application asks the Expo server whether there is a new version of its code and downloads it if there is. In doing so, Expo receives your device's IP address, the platform (iOS or Android), the Application version, the release channel and the identifier of the code version you have — solely in order to deliver the update. From version 1.0.6, the Application does not send Expo an installation identifier or error descriptions; earlier versions also send an identifier stored on the device and a description of the last serious Application error. A downloaded update remains on the device until it is replaced by a newer one. The legal basis is the performance of a contract — delivering Application updates (Art. 6(1)(b) GDPR; Terms, section 8.3).

5. Transfers outside the European Economic Area

Some of our service providers, including Google LLC, Sentry, Resend and Cloudflare, as well as selected infrastructure providers (e.g. Expo), are based or operate infrastructure outside the EEA, in particular in the United States. Personal data is therefore transferred outside the EEA, in particular to the United States. Transfers are made in accordance with Chapter V of the GDPR, in particular on the basis of:

You can obtain a copy of the standard contractual clauses used by a given provider by writing to contact@feasty.com.pl.

6. Retention periods

We retain your data for the following periods:

Where data from the Feasty AI audit, a moderation case or a reservation block is needed in a dispute that is ongoing or has been announced, we suspend its deletion until the dispute ends — for no longer than 6 years from the generation of the content (Feasty AI audit) or 10 years from the decision (moderation cases and blocks). The legal basis is our legitimate interest in establishing, exercising or defending legal claims (Art. 6(1)(f) and Art. 17(3)(e) GDPR).

After account deletion, we delete or fully anonymize your data according to the scenario you select (see section 7). Maximum erasure request fulfillment time: up to 30 days. In practice most operations complete within seconds (a cascading server-side process triggered after Firebase Auth deletion); the 30-day window covers edge cases (backups expire after 14 days, the last technical markers after 30 days).

Exception: consent logs (GDPR Art. 17(3)(e))

We retain pseudonymised consent logs (e.g. exclusion of reviews from Feasty AI summaries, objection to B2B counters, acceptance of Terms and Privacy Policy at a given version) for 6 years after the last change; once that period lapses the entries are deleted automatically. The basis is our legitimate interest in being able to demonstrate the lawfulness of processing and to defend against claims (GDPR Art. 6(1)(f)), together with the requirement of GDPR Art. 7(1) ("the controller shall be able to demonstrate that the data subject has consented") and falls under the right-to-erasure exception of GDPR Art. 17(3)(e) (data necessary for the establishment, exercise, or defense of legal claims). After account deletion the log retains the bare event metadata (consent type, granted/withdrawn status, timestamp, policy version) and a pseudonymous identifier of your former account — without it the log could not prove that it was you who consented; the IP hash is stripped. Such an entry is not anonymous: it remains personal data, although we do not use it to identify or profile you in day-to-day operations. The 6-year period matches the limitation period for consumer claims under Polish law (KC art. 118).

Exception: record of notices sent

After your account is deleted, we keep a record of having sent the messages whose delivery we must be able to prove: statements of reasons for moderation decisions and decisions on appeals, notices addressed to restaurateurs and the welcome message with the contract terms. The record covers the type of message, the date it was sent, the delivery status, a hash (SHA-256) of the email address and — for a statement of reasons or a block — a reference to its record, without the content of the message and without the address in plain form. We keep it for 3 years from sending or from the event the message concerns (moderation decisions, appeals, notices to restaurateurs), and for 6 years from sending the welcome message. The legal basis is our legitimate interest in demonstrating that we have fulfilled our information obligations and in defending against claims (Art. 6(1)(f) and Art. 17(3)(e) GDPR).

7. Your rights

In connection with the processing of your personal data, you have the following rights:

Anonymize reviews (default)

Your account is deleted, while your reviews are anonymized (author changed to "Former user"). The profile photo is removed immediately; photos within the review body remain visible as social content. Social content remains visible to the community but cannot be linked back to you. This does not apply to comments on reviews: we delete them together with the account.

> ⚠️ Important caveat — limits of anonymization. The system automatically removes only the link between the review and your profile (author, identifier). We do NOT automatically redact the review text itself or photo contents — if you placed identifying information inside the body of a review (e.g. "I, Jan Kowalski…", "I was here with my wife Anna", your face on the photo), it remains visible despite the author label change. Within the meaning of GDPR Art. 4(5) the operation will then be pseudonymization (identifiers embedded in Content), not full anonymization. Recommendation: if full unidentifiability matters to you, before closing your account manually delete the specific reviews containing identifying information, or choose the Full erasure scenario below — in both cases Content is permanently deleted.

Full erasure (Art. 17 GDPR)

Your account and all related reviews, comments, photos (profile + review), lists are permanently deleted.

Right to object. You may object at any time to the processing of your data based on our legitimate interest (Art. 21 GDPR), on grounds relating to your particular situation. This applies in particular to: verification of the Application and other security measures (section 9) — we assess the objection individually, weighing whether our interest in protecting the service overrides yours; counting your anonymous taps into B2B metrics (section 2) — we accept the objection without balancing; generating Feasty AI summaries with your reviews (section 2) — opting out is available directly in Settings. You can submit an objection to contact@feasty.com.pl; we will reply within one month.

Response deadlines

Under Art. 12(3) GDPR we respond to every request concerning your rights within 1 month of receipt. In complex cases or when we receive a large volume of requests we may extend this deadline by a further 2 months (up to 3 months in total), informing you of the extension with justification within the initial one-month period.

Exception: for account-deletion requests, the technical execution of data deletion takes up to 30 days (in practice — seconds, see section 6).

To exercise any of these rights, contact us at contact@feasty.com.pl.

8. Right to lodge a complaint

You have the right to lodge a complaint with the President of the Personal Data Protection Office (PUODO) if you believe that the processing of your data violates GDPR:

Urząd Ochrony Danych Osobowych
ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland
www.uodo.gov.pl

9. Data security

We apply adequate technical and organizational measures to protect your data against unauthorized access, loss or modification:

Verification of the Application. Before the Application connects to our server functions, it confirms that it is an unmodified Feasty Application running on a genuine device. It does this using a mechanism of the device's operating system: on iOS — App Attest or DeviceCheck (Apple), on Android — Play Integrity (Google Play; we use only the basic verdict, without information about other apps on the device). In doing so, the device's operating system passes technical information about the Application and the device to Apple or Google (including the identifier and version of the Application and the attestation result); Apple and Google Play process it as separate controllers, under their own privacy policies, and decide on its retention themselves. The result goes to Firebase App Check (Google Cloud), which issues the Application a short-lived token attached to its connections with our functions; Google Cloud acts here as our processor and, as regards technical data about the operation of the service, as a controller. Processing also takes place outside the EEA, including in the United States (section 5). We do not store the verification result. Our server rejects a connection without a valid token — features of the Application that rely on the server then do not work, and the Application shows a message with a contact address. The purpose is to protect the service and its Users against abuse by modified versions of the Application and by scripts; the legal basis is our legitimate interest (Art. 6(1)(f) GDPR). You may object — see section 7 ("Right to object").

Personal data breach notification (Art. 34 GDPR)

In the event of a personal data breach likely to result in a high risk to your rights and freedoms (e.g. leak of identifying data, unauthorised access to your private data), we will inform you without undue delay — via a push notification in the app and/or an email to the address associated with your account. The information will describe the nature of the breach, the likely consequences, the measures we have taken or propose to take, and the contact details of the Controller's point of contact (contact@feasty.com.pl). No Data Protection Officer is appointed — see section 1.

Independently of notifying users, we report every breach to the President of the Personal Data Protection Office (PUODO) within 72 hours of becoming aware of it (Art. 33 GDPR).

10. Minimum age

Feasty is available only to persons aged 18 and over. When you create an account, we ask you to confirm that you are at least 18; we do not collect or otherwise process your date of birth. If we discover that an account belongs to a minor, we will delete it immediately.

11. Automated decisions and profiling

We do not make decisions based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you.

For fair restaurant ranking, every review is weighted. Your review's weight depends on: (a) the age of your account — it is lower during the first 30 days; (b) the number of your reviews and of people who follow you; (c) your prestige rank (Standard / Elite / Connoisseur); (d) whether your ratings are almost always the same; (e) the age of the review itself — its weight halves every 180 days but never drops below 15% of the weight of a fresh review. These weights affect only restaurant ranking — never decisions about your account, access to the service, or any legal consequences. Full ranking parameters are publicly disclosed to restaurant owners as required by P2B Regulation (EU 2019/1150) Art. 5. The legal basis for weighting reviews and for the prestige rank is the performance of the contract (Art. 6(1)(b) GDPR) — both mechanisms are part of the service described in the Terms (section 3.1).

Prestige-rank qualifying criteria (Art. 13(2)(f) GDPR — meaningful information about the logic of profiling)

The prestige rank is computed fully rule-based (NOT using AI or statistical models), separately in each city, in three steps: (1) quality gate — a minimum number of karma points and published reviews; (2) city threshold — the city must have a set number of people meeting the quality gate, otherwise nobody there receives a rank; (3) among those people, by karma points, the top share is Connoisseur, the next — Elite; everyone else has the Standard rank. A rank is lost only after a grace period.

Karma points are a fully rule-based, deterministic sum of points awarded for: a published review (10–38 pts depending on completeness: photo, recommended-dish description, review body and its length, the tier you chose, vibe and tags; verified creators attaching a video: +15 pts), a like on your review from another User (+6 pts — a single like consists of one point for the like itself and five for marking the review helpful), your review collecting at least 10 likes ("Endorsement", +25 pts once), the first-ever review of a given restaurant in the database ("Pioneer", +25 pts), another User saving a restaurant from your review ("Curator", +20 pts, once per User–restaurant pair), and someone creating an account with your invite code (+50 pts; multi-use creator code: +5 pts per redemption). Visit verification earns no karma. Withdrawing a like deducts 6 pts; deleting a review reverses every point awarded for it. Values current as of the effective date of this Policy. Any change that materially modifies how karma is earned (e.g. adding a new rewarded behaviour category, removing an existing one, or changing values by an order of magnitude) requires a Policy update and re-consent. Minor point-value adjustments (e.g. karma-economy balancing) may be made by the Controller without a version bump — the current table is available on request at contact@feasty.com.pl.

Start-up thresholds. Until the target thresholds (below) are introduced, temporary thresholds apply: quality gate — at least 50 karma points and 3 published reviews; city threshold — at least 10 Users meeting that gate; Connoisseur — 10% of them by karma points, Elite — the next ones up to 40%.

Target thresholds. Quality gate — at least 200 karma points and 10 published reviews; city threshold — at least 50 Users meeting that gate; Connoisseur — top 1% by karma points; Elite — the next 2–10%. We will introduce the target thresholds across the whole Application at once when, at the weekly rank calculation, at least 50 Users in any city meet the target quality gate. A User's city is determined the same way as for the rankings — based on the addresses of the venues they review.

Protection of a rank you hold. We will announce the introduction of the target thresholds by a notification. If you do not keep your current rank under the new thresholds, you will keep it for a further 14-day grace period.

Recompute cycle: the rank is re-evaluated once per week (Sunday cron). Promotion to a higher rank is immediate upon first exceeding the threshold. Demotion (loss of rank) only takes effect after a 14-day grace period — protects against weekly fluctuations in city ranking position.

Notification: we notify you of grace-period start via a push message; demotion at grace expiry is silent. Promotions are silent on the push channel (the UI surfaces the new pill anyway).

The thresholds described above are the only ones applied. Any other change to them requires an update of this Policy; we will give at least 14 days' notice of any change that may take away someone's rank.

12. Policy changes

This privacy policy may be updated periodically to reflect changes in how the Application works, in the law, or in how data is processed. The version and last-updated date are shown at the very top of this document. Material changes (changes to the scope of data, legal bases, categories of recipients or mechanisms for exercising your rights) will be communicated with appropriate advance notice via the Application, email or another available channel. Where applicable law requires your consent or confirmation that you have read the changes, we will ask you to take the appropriate action before continuing to use certain features of the Application. The current version accepted by you is stored in the consent log (section 6, "Exception: consent logs") — you can request an extract at any time by writing to contact@feasty.com.pl.