FEASTY

Terms of Service

Last updated: 26 June 2026

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

Version: terms:0.4.0 | Effective date: 26 June 2026

These Terms of Service cover only Consumer Users of the Feasty consumer app. Restaurateurs using Feasty Business (B2B Claim procedure, owner panel) are governed by separate B2B Terms of Service — they will be available at business.feasty.com.pl once published (planned before the first B2B monetisation). Until then, restaurateurs may contact the Provider at contact@feasty.com.pl regarding the terms applicable to the B2B service.

1. General provisions

These Terms of Service govern the use of the Feasty mobile application, available on the App Store and Google Play, and define the rights and obligations of Users.

The service provider is Radosław Rodak (a natural person operating under the Polish "non-registered business activity" scheme — Art. 5(1) of the Entrepreneurs' Law), correspondence address: ul. Boya-Żeleńskiego 34, 20-435 Lublin, Poland. The Application operates in an early-access phase and does not charge fees.

2. Definitions

Application — the Feasty mobile app (code, design, branding, content) and the related server-side functions.
Provider — the entity identified in section 1.
User — a natural person holding an active Account in the Application.
Consumer — a User who is a natural person performing a legal act with the Provider not directly connected to their business or professional activity (Art. 22¹ of the Polish Civil Code). All consumer rights described in these Terms apply only to Consumers.
Account — the set of data identifying a User in the Application.
Content — any materials published by a User in the Application (reviews, photos, lists, comments, Matchmaker entries, profile data).
Restaurant — a dining establishment or another venue serving food or drink featured in the Application (including cafés, patisseries, ice-cream parlours, food trucks, bars, pubs). The definition covers venues sourced from Google Places API as well as those added manually by the Provider. Some information about a Restaurant — in particular the menu with prices, culinary notes and "Venue Faces" — may originate from the verified owner of that venue. The Provider makes such content available as an intermediary (hosting) and does not verify its accuracy or how up to date it is; if in doubt, confirm prices and availability directly with the venue. Inaccurate content can be reported in the Application or to the moderation address indicated in section 6.
Invite code — a single-use or multi-use string entitling the holder to register under the invite-only model; distribution rules are described in section 4.1.
Privacy Policy — a separate document describing the processing of personal data in the Application, available in the Application and at the address provided in section 1.

3. Scope of service and technical requirements

3.1. Application features

The Application allows Users in particular to:

create and edit restaurant reviews (rating on the S+/S/A/B/C/D/F scale and free-text description — scale defined in section 3.3)
add photos to reviews
create their own restaurant lists (e.g. "Favorites", "Want to go") and — for their own lists — share them with friends they follow, who upon accepting the invitation become co-authors with an equal right to add and remove places; each User is responsible for the content they add to a shared list, and a list can be left at any time
follow other Users and browse their activity
use Matchmaker mode — collaborative restaurant picking with friends (session rules in section 3.4)
search for restaurants on a map and by name
enable additional opt-in / opt-out privacy features: exclusion of the User's reviews from Feasty AI generated summaries and objection to anonymous taps being counted in B2B metrics — detailed rules are set out in the Privacy Policy (section 2, sub-sections "Feasty AI" and "Anonymous metrics for B2B partners").

The Application also features a Prestige system (ranks Standard / Elite / Connoisseur), assigned to Users on a rule-based per-city basis from activity signals — it influences how reviews are weighted in Restaurant ranking and how the rank is displayed on the User's profile. The Prestige system has no impact on the scope of services rendered to you by the Application, on access to features, or on any legal consequences regarding your account. Full qualifying criteria and the logic of this profiling are described in Privacy Policy section 11 ("Automated decisions and profiling").

3.2. Technical requirements

To use the Application, the following are required:

a device running iOS 15.1 or newer, or Android 7.0 (API 24) or newer
an active internet connection
an active email account
the current version of the Application downloaded from the App Store (iOS) or Google Play (Android)

3.3. Restaurant rating scale

The Application uses a seven-level qualitative scale (from S+ to F), fully transparent for every User and mapping to an internal 0–10 score. Full thresholds (internal 0–10 score → description):

S+ — score 9.5 and above: exceptional — cult destination, worth a dedicated trip.
S — score 8.5–9.5: excellent — strong recommendation without reservations.
A — score 7.0–8.5: very good — readily recommended.
B — score 5.5–7.0: good — solid, no real flaws.
C — score 4.0–5.5: acceptable — average, skip without regret.
D — score 2.0–4.0: weak — do not recommend.
F — score below 2.0: unrecommended — culinary or service failure.

When you write a review you pick a tier (S+–F); optionally you may also enter a precise 0–10 score within the scale — that score is then stored and your review's tier follows the band it falls in (thresholds above). The tier shown for a Restaurant (the dominant tier) is computed as a weighted mean of the 0–10 scores of your and other Users' reviews, mapped back to the bands above, according to the ranking parameters (weights) described in section 11 of the Privacy Policy (in line with the P2B Regulation).

3.4. Matchmaker mode — session rules

Matchmaker is a feature for choosing a restaurant together. Rules:

The session creator generates a 6-character code shared with friends (in person or via a link). Anyone who enters the code joins the session.
A session is a single database document holding members, a list of 20–30 nearby venues and each participant's "yes/no" swipes.
A "match" emerges when ≥ 2 members swipe "yes" on the same venue. Matches are visible to all session participants; the full list of "no" swipes remains private.
A participant may leave the session at any time — prior swipes remain in the document, but no new swipes are added.
The session creator may close the session manually at any time; the session is also automatically closed after 24 hours of inactivity.
The full session (members + swipes) is permanently deleted within 30 days of closure — retention details are set out in the Matchmaker section of the Privacy Policy.
A "match" in the Application is not a declaration of intent or a contract — it is merely a group aid for choosing a venue. The decision to visit rests with Users outside the Application.

3.5. Review publishing limits (abuse protection)

To protect against spam and artificial manipulation of rankings, the Provider applies technical limits on the number of reviews a single User may publish within a daily, weekly and monthly window. Once a limit is reached, the Application will refuse to publish a further review and will display a message stating which limit was reached and when the next review may be added. The limits are deliberately set at a level an ordinary User will not notice — they are an anti-spam safeguard, not a restriction on active Users. The current limit values may be changed by the Provider without changing the version of these Terms — the applicable value and the unlock time are shown by the Application each time in the limit-reached message.

3.6. Split the bill — a bill-splitting calculator

The "Split the bill" feature lets the User calculate how to divide the cost of a shared meal: after the receipt is scanned, the Application splits it into items (an AI model), and the User assigns items to people and optionally adds a tip.

A calculator only. The Application merely calculates the amounts owed between Users. Feasty is not a payment service, does not intermediate in transferring money, does not store payment data, and is not responsible for the actual settlements made between Users outside the Application.
Responsibility for data. The AI reading of the receipt is a suggestion that the User should verify and correct if needed; the Provider does not guarantee that the reading is error-free.
Third parties. When adding a person from outside the Application to a split (by first name only), the User provides only the data necessary to calculate the split. Processing details are described in the Privacy Policy.

3.7. Feasty Events — planning group outings

The "Feasty Events" feature lets the User propose a get-together: set a time and place (directly or by choosing together in Matchmaker) and invite friends (only people they mutually follow).

Organizer role. Only the organizer may change the event's time or place and approve proposed changes; every such change requires the other guests to re-confirm their attendance.
Group reservation. Using the reservation option triggers the Application's standard reservation feature; only the organizer's contact details are shared with the venue. The Provider does not guarantee table availability or confirmation by the venue.
Settlement. The "Split the bill" option is a calculator only (§3.6) — Feasty does not intermediate payments between Users.

4. User Account

4.1. Registration

Creating an account requires:

being at least 16 years old
authenticating through one of the identity providers supported by the Application: Apple ID, Google account, or a one-time email code (a single-use sign-in link sent to the provided address)
accepting these Terms of Service and the Privacy Policy
entering an active invite code — the Application operates on an invite-only basis

The Provider does not create or store passwords for the Account. Login security depends on the security measures of the chosen identity provider (Apple ID, Google account, access to your email inbox).

#### Invite-code rules

a) Who issues codes. The first waves of codes are issued by the Provider. Every registered User receives a Provider-defined number of personal codes to distribute (currently 3 codes per Account; the limit may be changed by the Provider without changing the version of the Terms — information available in the Application in the "Invitations" section). The number of remaining codes is visible to the User in their profile.

b) Personal nature of codes. Invite codes are intended for free distribution to people the User personally knows and to whom they wish to recommend the Application. Selling, trading, offering for sale, publishing codes for commercial purposes or on auction platforms (Allegro, OLX, Vinted, eBay, etc.) is prohibited and constitutes a gross violation of these Terms (section 5.4).

c) Code expiry during registration. Codes have a defined validity period (currently 30 days from generation) and a single-use limit. If a code expires between entering it in the Application and completing registration, the Application will display an invalidity notice and the Account will not be created. Code expiry does not create any claims against the Provider or the issuer.

d) Denial of an invite code. The Provider has no obligation to grant an invite code to a person who requests one (through the "Request access" pre-form). The Provider's decision is discretionary and requires no justification. A person who did not receive a code has no claim to its issuance; they may at any time remove their waitlist entry (procedure in the Privacy Policy).

e) Revocation of a code by the Provider. The Provider may revoke (invalidate) a generated code before it has been redeemed only for important reasons: (i) suspected abuse (trading, scraping), (ii) revocation of access to the Application of the issuer of the code, (iii) detection of a technical error in code generation. The Provider notifies the issuer of the revocation by email.

f) Invitee status. A person who registered using an invite code holds identical rights and obligations as any other User — there is no "inviter/invitee" hierarchy in the service itself.

4.2. Account security

The User is required to:

protect access to the identity provider used for registration (Apple ID, Google account, email inbox) following the best practices of that provider
immediately notify the Provider of any suspected unauthorized access to the Account
use the Account only personally (one account = one person)

4.3. Account deletion

The User may delete their account at any time from within the Application (Profile → Settings → Delete account). Consequences are described in the Privacy Policy (section 7).

4.4. Right of withdrawal

A Consumer entering into an agreement for the provision of digital services within the Application has the right to withdraw from it within 14 days of the date the agreement was concluded (account creation), without giving a reason and without incurring costs (Article 27 of the Polish Consumer Rights Act of 30 May 2014).

To exercise the right of withdrawal it is sufficient to delete the Account from within the Application (Profile → Settings → Delete account). Alternatively, the Consumer may send a withdrawal statement to contact@feasty.com.pl — a clear expression of will to withdraw is sufficient; no form is required.

#### Exception: loss of the right of withdrawal upon commencement of the service (Art. 38(1)(13) of the Consumer Rights Act)

The Application provides a digital service (within the meaning of Art. 43h(1) of the Consumer Rights Act) delivered immediately upon account creation — without a physical medium, on a continuous basis. For such a digital service Art. 38(1)(13) of the Act provides that the right of withdrawal expires when three conditions are jointly met:

a) the Consumer expressly requests commencement of the service before the 14-day withdrawal period elapses,
b) the Consumer acknowledges that they thereby lose the right of withdrawal once the service has commenced,
c) the Provider supplies the Consumer with confirmation of the conclusion of the contract.

By accepting these Terms when creating the Account, the Consumer simultaneously:

requests commencement of the digital service (access to the Application) immediately upon Account creation, before the 14-day withdrawal period elapses (condition a) — immediate access is an inherent feature of the Application and the Consumer knowingly chooses the Application expecting it to operate without delay,
acknowledges that, as a result of the above request, they lose the right of withdrawal during the 14-day period in respect of the digital content supplied with their consent (condition b) — this clause serves as the express declaration of awareness required by Art. 38(1)(13) of the Consumer Rights Act.

Confirmation of the conclusion of the contract (condition c) is provided by the Provider on a durable medium — in the form of an email automatically sent to the address associated with the Account immediately after its creation. The email contains a statement of contract conclusion, acknowledgment of the loss of the right of withdrawal, and the accepted versions of the Terms and Privacy Policy (e.g. terms:0.4.0 + privacy:0.4.0) with a timestamp — the Consumer retains this message as durable evidence of contract conclusion within the meaning of "durable medium" under Art. 2(4) of the Polish Consumer Rights Act. In parallel, an entry in the consent log linked to the Account (retained for 6 years — see Privacy Policy section 6 "Exception: consent logs") serves as internal audit. The Consumer may at any time request the email confirmation to be re-sent or an extract from the consent log by writing to contact@feasty.com.pl.

#### Consequences

A Consumer who has accepted these Terms (and therefore expressed the request and acknowledgement in conditions a–b above) MAY NOT withdraw from the agreement under Art. 27 of the Act. They may terminate the agreement at any time by deleting the Account (section 4.3) — in which case the rules of the Privacy Policy (section 7) apply, including default anonymization of Content unless the Consumer chooses full erasure.

Independently of the above, in the event of non-conformity of the Application with the agreement (Art. 43h–43q of the Act — defective operation, unavailability of critical functions) the Consumer holds the rights set out in section 8 — withdrawal in the non-conformity track is not the same as the 14-day right of withdrawal and is NOT covered by the above exception.

5. User Content

5.1. Ownership and license

All Content you publish in the Application remains your property. By publishing Content, you grant the Provider a non-exclusive, worldwide, royalty-free license within the scope set out below.

#### License scope

a) Exploitation within the Application: displaying the Content in the Application and showing it to other Users in accordance with visibility settings chosen by the author.

b) Organic promotion: creating promotional materials for Feasty across the Provider's owned channels (official social-media profiles, product blog, press materials) using fragments of your Content (quote, micro-quote, photo). "Organic promotion" covers publications that are not funded by an advertising budget.

c) Paid advertising — requires separate consent: use of your specific Content in paid advertising campaigns (promoted posts, Google Ads, Meta Ads, billboards, video ads, etc.) requires your express separate consent, which we will obtain by email describing the specific campaign. You may decline without consequence. This organic license does not cover such uses.

d) Derivative works and adaptations: to the extent necessary to adapt Content to the Application's distribution formats and to organic materials under (b) (excerpts, fragments, fitting to the safe area of Instagram Stories / Reels, photo retouching for specific formats, addition of Feasty branding). Adaptations may not alter the meaning of the Content or suggest an opinion the author did not express.

#### Author's moral rights (inalienable)

This license does not cover the author's moral rights, which under Art. 16 of the Polish Copyright and Related Rights Act of 4 February 1994 are inalienable and cannot be waived. The Provider in particular:

respects the right of authorship of the Content,
respects the right to the integrity of the Content (preservation of meaning) — adaptations under (d) may not violate this right,
respects the right to supervise the manner of use of the Content — the author may at any time request the cessation of a specific promotional use (by writing to contact@feasty.com.pl).

#### Attribution

Content shown in the Application is by default credited with your display name and your profile photo. In promotional materials under (b)–(c) we apply the following attribution rules:

Text quote from a review in organic posts — credited by default with the author's display name (e.g. "Anna K. on Restaurant X"); on the author's request (by email) we may publish anonymously ("Feasty User").
Photo from a review — always with a visible credit naming the author; we do not publish without a credit.
Materials after Account anonymization (the default scenario when deleting the Account) — Content credited as "Former user"; we never use it in new promotional materials after anonymization.

#### Term

The license remains in effect for the duration of your account. Upon account deletion — depending on the chosen deletion scenario — the license expires or content is anonymized (see Privacy Policy section 7).

5.2. Content standards

By publishing Content you confirm that:

you have full rights to publish it (e.g. you are the author of the photo)
the Content reflects your actual experience with the Restaurant
the Content does not infringe the rights of third parties

5.3. Prohibited content

It is forbidden to publish Content that:

infringes copyright or other intellectual property rights
contains hate speech, discriminatory content, threats or insults
is spam or commercial advertising without our consent
consists of fake reviews or manipulates a Restaurant's reputation
contains personal data of others without their consent
violates law or common decency

5.4. Prohibited behaviour

Independently of the prohibition on publishing specific Content, the following User behaviours are also prohibited:

a) Multiple accounts — creating and maintaining more than one Account by the same natural person, in particular in order to evade limits (request rate limits, account suspension), manipulate rankings, artificially inflate Prestige rank, fake mutual follows or likes.

b) Automated data collection (scraping) — using bots, crawlers, scripts, browsers without a graphical interface or other automated tools to bulk-extract data from the Application (reviews, restaurant lists, User profiles, map data). Only ordinary interactive use through the mobile app is permitted.

c) Reverse engineering — decompiling, disassembling, deciphering or otherwise recovering the source code of the Application, as well as attempts to circumvent security mechanisms (App Check, version enforcement, rate-limit, signature verification). Exceptions provided by law (interoperability under Art. 75(2)–(3) of the Polish Copyright Act) remain in force.

d) Commercial use of data from the Application — using other Users' Content or aggregates (rankings, statistics, restaurant lists) to build a competing database, an AI training dataset, a derivative product, or for any other commercial use without the Provider's express consent given in documentary form (Art. 77² of the Polish Civil Code) — i.e. by email, in-app message or any other electronically recorded statement permitting access to its content.

e) Trading in invite codes — selling, trading, offering for sale, publishing invite codes for profit, or purchasing them. The prohibition covers auction platforms (Allegro, OLX, Vinted, eBay), social-media groups, online forums and any other form of commercial distribution.

f) Circumventing moderation — deliberate obfuscation of prohibited content (e.g. typos in offensive words, Aesopian language) to evade automated filters; creating a new Account to circumvent a suspension ("ban evasion").

g) System abuse — issuing API requests at a frequency clearly deviating from normal usage (denial-of-service, attempts to overload the service); deliberately submitting malformed data to trigger errors.

5.5. Consequences of violations

The Provider has the right to:

remove Content violating section 5.3,
temporarily or permanently block the Account of a person violating section 5.4 (severe or repeated violations),
pursue civil claims or notify law-enforcement authorities in case of violations meeting the elements of a criminal offence or civil tort (in particular points (b), (c), (d), (e)).

The detailed moderation process and the User's rights (notice, statement of reasons, appeal) are described in section 6.

6. Content moderation (under the Digital Services Act — DSA)

Feasty is a hosting service within the meaning of Regulation (EU) 2022/2065 (Digital Services Act — DSA), which entered into force on 17 February 2024. This section fulfills the transparency obligations of DSA Article 14.

6.1. Reporting content — Notice & Action mechanism (Art. 16 DSA)

Any User or third party may report Content they consider illegal or in violation of these Terms. Available reporting channels:

in-app: tap the "..." icon next to a review → "Report" → select category (Spam / Fake review / Inappropriate content / Copyright infringement)
by email at: moderation@feasty.com.pl — for reports requiring detailed justification, including reports from non-registered users

Email reports should include:

identification of the Content (deep-link URL to the review or its id if known; otherwise the restaurant name + author + approximate publication date)
category of violation (illegal content, Terms violation, fake review, infringement of third-party rights, other)
justification — description of the violation
statement that the reporter is acting in good faith and the information provided is accurate
reporter's contact details (optional for anonymous reports, but required if a response is expected)

6.2. Moderation method

The Provider applies a hybrid moderation model:

a) Automated layer — algorithmic filters may temporarily hide Content after exceeding a threshold of User reports (e.g. multiple reports of the same review as spam or fake) or after detection of obvious patterns (recurring offensive keywords). The automated layer's effect is hiding, not permanent removal — Content can be reinstated on appeal.

b) Manual layer (human decisions) — decisions on permanent removal of Content, account suspension or permanent account closure are taken by a human administrator based on individual review. Every appeal (section 6.5) is reviewed by a person other than the author of the original decision.

In practice — at the current early-access stage — most decisions are direct administrator interventions reflecting the low volume of reports. As scale grows, the role of the automated layer will grow; any change in the auto/manual ratio that materially affects User rights will be recorded in an update to these Terms.

6.3. Response time

The Provider undertakes to review reports in a timely, diligent, objective and non-discriminatory manner (Art. 16(6) DSA). A response is issued without undue delay and in any event no later than within 30 days of receiving the report. In urgent cases (content threatening life or health, child sexual abuse material, explicit incitement to violence or crime) the response is immediate, typically within a few hours. The Provider periodically publishes statistics on average response times as part of its DSA transparency report (Art. 15 DSA) — the full URL of the report will be indicated in this section together with the first publication, at the latest by 17 February 2027 (anniversary of DSA's entry into force). Until then, full statistics are available on request at legal@feasty.com.pl.

6.4. Statement of reasons (Art. 17 DSA)

Removal of User Content and account restrictions are documented. The User receives an email at the address associated with the account containing:

scope of the restriction (removal of specific Content, temporary account block, permanent account closure)
facts and circumstances justifying the decision
legal or regulatory basis (specific provision of law or Terms section)
information about the right to appeal and how to submit one

6.5. Appeals (Art. 20 DSA — internal complaint-handling)

A User dissatisfied with a moderation decision has 6 months from receiving the notice to submit an appeal. Appeals are sent to moderation@feasty.com.pl with "Appeal" in the subject line.

Appeals are reviewed without undue delay, usually within 14 days. Review is conducted by a person other than the author of the original decision.

6.6. DSA points of contact

In accordance with DSA requirements, the Provider designates:

Point of contact for public authorities (Art. 11 DSA): legal@feasty.com.pl
Point of contact for users regarding moderation (Art. 12 DSA): moderation@feasty.com.pl

Languages of correspondence: Polish or English.

6.7. Reports from restaurant owners

A Restaurant owner who believes a specific review is fake or violates these Terms uses the same reporting channel described in section 6.1. The Provider does not disclose the identity of review authors to restaurant owners — except pursuant to a court order or final decision of a public authority.

7. Platform intellectual property

All rights to the Application (source code, design, branding, the Feasty brand) belong to the Provider and are reserved. The Provider grants the User only a limited, non-exclusive, non-transferable and revocable licence to use the Application for its ordinary personal, non-commercial purpose, for the term of the agreement. Use of the Application does not transfer to the User any intellectual property rights in the Application itself; in particular, the User acquires no rights to the source code, the recovery of which (decompilation, disassembly) is prohibited on the terms set out in point 5.4(c).

Open-source libraries. The Application bundles software libraries provided by the open-source community under their respective licenses (including MIT, Apache 2.0, ISC, SIL Open Font License). A full list of bundled libraries together with their license texts is available in the Application under Settings → App → Open source licenses. Use of the Application does not modify or restrict the rights granted to the User by those licenses in respect of the libraries listed in that section.

8. Application's conformity with the agreement

The Provider is liable to Consumers for the lack of conformity of the Application (a digital service) with the agreement on the terms set out in Chapter 5b of the Polish Consumer Rights Act of 30 May 2014 (Articles 43h–43q), implementing Directive (EU) 2019/770 of the European Parliament and of the Council of 20 May 2019.

8.1. What we mean by "conformity with the agreement"

The Application conforms with the agreement when, in particular:

its functions described in section 3.1 work as described
it is available on a continuous basis, subject to the disclaimers in section 9 (maintenance, third-party outages)
it contains no material defects that prevent the use of basic functions (browsing restaurants, adding reviews, receiving notifications)

"Conformity with the agreement" under this section does not cover the following elements of the Provider's editorial judgement, nor the choices of other Users:

the recommendation algorithm (Scoring), the tier assigned to a specific Restaurant, or the order of search results
the quality or truthfulness of Content published by other Users (reviews, photos, lists)
the quality, safety or legality of products or services offered by Restaurants presented in the Application

8.2. Consumer's remedies in case of non-conformity

In the event of non-conformity of the Application with the agreement the Consumer may demand:

bringing the Application into conformity with the agreement
a statement of price reduction — not applicable, since the Application is currently provided free of charge
a statement of withdrawal from the agreement — under section 4.3 or 4.4

The Provider may refuse to bring the Application into conformity with the agreement if it is impossible or would impose excessive costs on the Provider (Article 43m(2) of the Consumer Rights Act).

8.3. Application updates

The Provider undertakes to provide updates (including security patches) necessary to maintain the Application's conformity with the agreement for the period of its reasonable use, no shorter than 24 months from the date of account registration. Updates are delivered through the App Store or Google Play according to those stores' mechanisms; the User is required to install them within a reasonable time.

8.4. Reporting period

The Consumer may report a lack of conformity of the Application with the agreement within 6 years from the date of its discovery (Article 43h(5) of the Act). Reports are sent to contact@feasty.com.pl following the complaints procedure described in section 11.

8.5. Discontinuation of the Application (service shutdown)

The Provider may discontinue the Application as a whole (permanent service shutdown) only for important organisational, economic or technical reasons, in particular where continued operation becomes impossible or disproportionately difficult for the Provider:

a) loss of access to key infrastructure providers without an equivalent alternative,
b) lack of viability of the Application in the post-monetisation phase after reasonable revenue paths have been exhausted,
c) inability to maintain compliance with applicable law or platform partner policies (Apple, Google) at reasonable cost,
d) the Provider's decision to change the product's direction, as a result of which the Application in its current form is no longer developed.

The Provider will inform Users of the planned discontinuation at least 6 months in advance through the Application and via the email associated with the Account. During the notice period:

the Application operates with full functionality — the Provider will not introduce feature or quality limitations beyond what becomes objectively necessary (e.g. infrastructure-provider resource exhaustion);
the Consumer may at any time export their data under Art. 20 GDPR (right to data portability — Privacy Policy section 7) — the Provider will prepare a complete export package within 14 days of the request;
the Provider will deliver security-relevant updates (security patches) — functional updates remain discretionary and may be paused;
the Consumer may terminate the agreement earlier at any time by deleting the Account (section 4.3) — without any consequences.

Discontinuation of the Application results in termination of the agreement with every User on the date of permanent shutdown. The update obligation described in section 8.3 ("at least 24 months") continues until the date of termination — after that date the agreement to which the update obligation could apply no longer exists. This mechanism does not constitute a contractual shortening of the statutory obligation under Art. 43k of the Consumer Rights Act; it defines the conditions for terminating the agreement, within which that obligation naturally lapses together with the agreement itself. The Consumer retains the remedies under section 8.2 in case of non-conformity of the Application during the notice period.

9. Disclaimers

The Provider makes every effort for the Application to operate properly and be available 24/7, but does not guarantee:

uninterrupted availability (e.g. maintenance, third-party outages)
completeness and accuracy of information about Restaurants (data may be outdated)
accuracy of reviews by other Users — these are solely their subjective opinions

The decision to visit a Restaurant and to evaluate the quality of service rests solely with the User.

9.1. Force majeure

The Provider is not liable for non-performance or improper performance of obligations under these Terms to the extent that such non-performance is caused by force majeure — understood as an external event that could not be foreseen or prevented with due diligence. Force majeure includes in particular: natural disasters, pandemics, acts of war, terrorism, acts of state authority (decisions, sanctions, blockades, mobilisations), critical-infrastructure failures (electricity, telecommunications networks, internet) of a scope going beyond a single service provider, as well as outages of key cloud-infrastructure providers (Google Cloud / Firebase, Apple Push Notification Service, AWS — in the case of incidents documented by those providers).

In the event of force majeure the Provider will inform Users of the scope of disruption through the Application or by email as soon as technically possible, and will use reasonable efforts to restore the Application's operation in the shortest possible time. The duration of force majeure does not count towards a breach of the Provider's obligations nor towards the response deadlines set out in these Terms (including the moderation deadlines in section 6.3 and the complaint-handling deadlines in section 11).

9.2. Links to external services

The Application may contain links directing the User to external services (including table-reservation systems, food-delivery platforms, Restaurants' websites, Apple/Google maps, social media). With respect to such links:

the Provider is not a party to agreements concluded by the User with the operators of those services
the Provider is not liable for the quality, availability or correctness of services provided by those entities
the Provider is not liable for the personal-data processing rules applied by those entities — before following the link the User should review their privacy policies
the Provider is not liable for the financial consequences of transactions concluded through those services

10. Limitation of liability

To the extent permitted by law, the Provider is not liable for:

indirect damages (lost profits, lost data)
the quality, safety or legality of products or services offered by Restaurants
the behavior of other Users in the Application

These provisions do not exclude or limit the Provider's liability towards Consumers (natural persons using the Application for purposes unrelated to their business or professional activity) to the extent that such exclusion or limitation would conflict with mandatory provisions of law.

11. Complaints

Complaints regarding the Application can be sent to: contact@feasty.com.pl.

A complaint should include:

the User's name (or email associated with the account)
description of the problem
any specific request

Complaints will be reviewed within 14 days of receipt (Art. 7a of the Consumer Rights Act — failure to respond within this period means the complaint is deemed accepted). We will notify you of the outcome at the email associated with your account.

Complaints regarding content moderation (review removal, account block) follow a separate procedure described in section 6.5 (DSA appeals).

12. Out-of-court dispute resolution

Consumers have the right to use out-of-court methods of handling complaints and pursuing claims, in particular by:

applying to a permanent consumer arbitration court operating at the Provincial Inspectorate of the Trade Inspection (Wojewódzki Inspektorat Inspekcji Handlowej)
contacting the district (municipal) consumer ombudsman (rzecznik konsumentów) or requesting mediation from the Provincial Inspectorate of the Trade Inspection
using free consumer assistance — the UOKiK consumer helpline (801 440 220) and information at www.uokik.gov.pl

The European Commission's Online Dispute Resolution (ODR) platform was discontinued on 20 July 2025 (Regulation (EU) 2024/3228) and is no longer available.

13. Changes to the Terms

The Provider reserves the right to amend these Terms solely for the following important reasons:

a) changes to generally applicable laws that directly affect the provision of services through the Application
b) issuance of a final court judgment or a final decision of a public-administration body requiring the Terms to be amended
c) introduction of new Application functionalities, modification or withdrawal of existing ones — to the extent affecting the User's rights or obligations described in the Terms
d) prevention of abuse and security considerations of the Application and its Users
e) change of the Provider's identification details (business name, correspondence address, legal form of business)
f) technical reasons related to a material change of the Application's infrastructure (e.g. migration of cloud provider, change of authentication method, change of payment-service provider)

The Provider will notify the User of the changes at least 14 days in advance through the Application or the email associated with the Account. The change takes effect after that period, unless the User earlier:

accepts the new Terms in the Application (accelerating the effective date), or
deletes the Account before the effective date — in which case the previous version of the Terms applies until the date of deletion.

14. Governing law, jurisdiction and miscellaneous clauses

14.1. Governing law

Matters not covered by these Terms are governed by Polish law, including the Civil Code, the Act on Provision of Services by Electronic Means, the Consumer Rights Act and Regulation (EU) 2022/2065 (DSA).

14.2. Jurisdiction

Disputes arising from the agreement concluded on the basis of these Terms are heard by the ordinary courts in Poland. For Consumers, the competent court is the court of the Consumer's place of residence or the court of the Provider's seat — the choice rests with the Consumer (Art. 17(1)(c) and Art. 18 of the Brussels I bis Regulation for Consumers in the EU; Art. 31 et seq. of the Polish Code of Civil Procedure for Consumers in Poland). This provision does not limit the Consumer's right to use out-of-court dispute-resolution mechanisms (section 12).

14.3. Severability

If any provision of these Terms is held by a competent court, public-administration body or another authorised adjudicator to be invalid, ineffective or unenforceable in whole or in part, the remaining provisions of the Terms continue in full force and effect. To the extent of the invalid provision, the parties apply the rule of law that comes closest to the economic purpose of the invalid provision — while preserving Consumer protection.

14.4. Binding language version

These Terms are published in Polish, English and German language versions. The Polish version is the binding version. In the event of discrepancies between language versions (e.g. inaccurate translation, typographical error), the wording of the Polish version prevails. The above does not limit the Consumer's right to use the Application in their own language (DSA Art. 14(1)).

15. Provisions concerning distribution through the App Store and Google Play

The Application is distributed through the Apple App Store (iOS) and Google Play (Android). Notwithstanding any other provision of these Terms, the User acknowledges that:

15.1. Apple App Store (iOS)

Apple Inc. ("Apple") is not a party to these Terms or to the agreement between the User and the Provider. Apple is not responsible for the Application or its Content.
Apple provides no technical support for the Application. All questions, complaints and claims related to the Application must be addressed solely to the Provider (contact@feasty.com.pl).
Apple is not liable for any third-party claims of intellectual-property infringement by the Application.
Apple and Apple's subsidiaries are third-party beneficiaries of these Terms — Apple has the right to enforce the provisions of these Terms against the User as a third-party beneficiary.
Distribution and installation of the Application on iOS devices is additionally subject to the Apple Media Services Terms and Conditions (https://www.apple.com/legal/internet-services/itunes/).

15.2. Google Play (Android)

Google LLC ("Google") is not a party to these Terms or to the agreement between the User and the Provider.
Google provides no technical support for the Application. Complaints and claims must be addressed solely to the Provider.
Google is not liable for the quality, safety or legality of the Application.
Google may enforce the provisions of these Terms to the extent required by the Google Play Developer Distribution Agreement. This provision does NOT grant Google the status of a "third-party beneficiary" in the civil-law sense beyond that scope — Google is not a party to the agreement between the User and the Provider.
Distribution and installation of the Application on Android devices is additionally subject to the Google Play Terms of Service (https://play.google.com/intl/en/about/play-terms/).

15.3. In-app payments

The Application currently contains no paid features or In-App Purchases. Should paid features be introduced in the future, transactions will be processed exclusively through the App Store or Google Play payment mechanisms, subject to amendment of these Terms under section 13.

16. Effective date

These Terms in version terms:0.4.0 enter into force on 26 June 2026 and apply to all Users who use the Application after that date. The currently effective version and effective date are also shown at the very top of this document. The version accepted by the User is recorded in the consent log (Privacy Policy section 6 "Exception: consent logs") — an extract may be requested at any time by writing to contact@feasty.com.pl.