Notice provided under Articles 13 and 14 of Regulation (EU) 2016/679 ("GDPR") and Italian Legislative Decree 196/2003, as amended by Legislative Decree 101/2018.
| Document | Privacy Notice — SwipeOut app for people going out |
| Version | 1.4 — 24 October 2026 |
| Effective from | Date of publication |
| Public URL | https://swipeout.it/legal/consumer/privacy-policy/en |
| Languages | Italian and English. Both versions have the same content |
1.1 Controller.
Vittorio Barile
Via Don Angelo Sanzò 37 — 86017 Sepino (CB), Italy
VAT number 01826370700
Controller's email: info@swipeout.it
1.2 Where to write to us. To exercise your rights, ask a question or make a complaint, write to info@swipeout.it. We check this address every day and reply within the times in §18.
1.3 Data Protection Officer. We have not appointed a Data Protection Officer (DPO).
1.4 If the business moves to a company. If the business is transferred to a company, this notice will be reissued with the company's details. We will let you know as described in §23.
2.1 We use a direct, informal tone, as we do in the app.
2.2 Processing data means anything we do with it: collecting, storing, consulting, sharing or erasing it.
2.3 A venue is the restaurant, bar, club or event organiser shown on SwipeOut. A venue is registered when it uses the SwipeOut console and not registered when its listing exists but is not managed by the venue.
2.4 Letters in brackets, such as b) or d), refer to the purposes in the table in §4. We use them in the app too, so you can see straight away what a toggle refers to.
| Data | Required | What it is for |
|---|---|---|
| First name and surname | Yes | They identify you in bookings |
| Yes | Used to log in and to send you service communications | |
| Password | Yes, unless you log in with Apple or Google | Stored only in encrypted, non-reversible form |
| Date of birth | Yes | Used to check that you are 18 (§21) |
| Where you usually go out | Yes | The municipality you choose from a list. We use it to show you something relevant when location is not in use |
| Gender | No | See §3.2 |
| Username | Generated automatically | Created from the part of your email address before the @. Other members of your groups can see it. You can change it |
| Profile photo | No | Other members of your groups can see it |
If you log in with Apple or Google, they give us your name and email address, and we only ask for your date of birth and where you usually go out.
Giving your gender is optional. You can also choose "I prefer not to say". If you give it, we ask for explicit, separate consent next to the field. We use this data only in the figures about groups of people that we provide to venues (§6). We do not use it to choose what to show you or to select advertising. You can change or remove it at any time, and it then stops counting in those figures.
We ask for it at your first booking, not at registration. We verify it with a code sent by SMS and keep it in your account so you do not have to enter it again.
If you have given consent b) or d) (§5), we show you some cards where you tell us what you like: food, atmosphere, types of event. Without either consent we do not show them, because we would have no use for your answers. You can reset your answers in the settings at any time.
Your preferences do not include allergies, which we handle only within a booking (§8).
On the home screen we ask, if you want to answer, what you feel like doing tonight. You pick from ready-made answers, such as "Up for going out" or "Quiet evening". We do not ask how you feel.
Your answer is kept for 48 hours and is used for two things:
When you use the app we record your interactions: what you open, tap and scroll past, which filters you use, what you search for, what you follow and what you mark "Interested". We call these signals. We also record technical data: internal account identifier, device identifier for notifications, IP address, device model, operating system, app version, access logs and error logs.
What we always record and what only with your consent. That an action happened — for example that a venue page was opened — we always record, because we need it to give venues the figures in §6 (purpose c) and to know whether the app works. If you have not given consent to usage statistics (purpose i), we record it without linking it to you: not to your account, not to your device, not to your session. With consent we link it to your account and to a random device identifier, which is not the advertising identifier, to understand how the app is used over time: how registration goes, which features are used, who comes back. With the same consent Google Firebase collects automatic statistics for us: installs, sessions, time in the app, device model, app version and, on Android, uninstalls. Without consent Firebase collects no statistics.
Signals and usage events never contain your name, phone number, email, booking notes, allergies, the text of your reviews, the text of your searches, or what you type or say to the assistant. For location, they contain at most the municipality, never coordinates.
Before the app is in the stores you can leave your contact on swipeout.it to be told when SwipeOut comes out. We collect your first name, last name, the city you live in and your email, the language of the page and, if you came from a link in one of our campaigns, the link parameters (source, medium, campaign). We do not store your IP address.
| Purpose | What it means | Legal basis | If you say no | |
|---|---|---|---|---|
| a) | Letting you use the app | Account, login, search, map, calendar, bookings, reviews, groups, missions, level, assistant, subscription, support | Performance of a contract (Art. 6(1)(b)) | We cannot provide the service without this data |
| b) | Personalised content | Ordering the feed, map, calendar and assistant based on your preferences and how you use the app | Consent (Art. 6(1)(a)) | You see content ordered by proximity, time and popularity |
| c) | Figures for venues | Statistics about groups of people above the thresholds in §6, including going-out intent and gender where given with consent | Legitimate interests (Art. 6(1)(f)); for gender, explicit consent | You can object at any time (§18.4) |
| d) | Sponsored content based on your preferences | Choosing which sponsored content to show you based on your preferences and going-out intent | Consent (Art. 6(1)(a)) | You still see sponsored content, chosen without using your preferences or behaviour |
| e) | Promotions by notification | Sending you push notifications with venue promotions, at most one a day | Consent (Art. 6(1)(a)) | You receive no commercial notifications. Nothing else in the app changes |
| f) | Location | Showing you what is nearby, working out which campaigns in your area can reach you, verifying attendance in missions (§7) | Consent (Art. 6(1)(a)), given separately for each of the three uses | We use the municipality you gave in "Where you usually go out" |
| g) | Allergies in bookings | Sharing them with the venue for that booking only (§8) | Explicit consent (Art. 9(2)(a)) | You can still book, without allergies |
| h) | Security, moderation, legal obligations | Preventing abuse and fraud, moderating content, responding to authorities, defending our rights, keeping receipts | Legal obligation (Art. 6(1)(c)) and legitimate interests (Art. 6(1)(f)) | — |
| i) | App usage statistics | Understanding how the app is used in order to improve it: how registration goes, which features are used, who comes back, what does not work. We link usage events to your account and to a random device identifier (§3.6) | Consent (Art. 6(1)(a); Art. 122 of the Italian Privacy Code) | We record only that an action happened, without linking it to you, and Firebase collects no statistics. The app does not change |
| j) | Pre-registration on the website | Telling you when SwipeOut comes out (§3.8) | Consent (art. 6.1.a) | You do not pre-register: you can still download the app when it comes out |
4.1 Consents are separate. Each consent is its own toggle. None is switched on in advance, none is required to use SwipeOut, and switching one off does not switch off the others.
4.2 How SwipeOut makes money. We tell you openly. Most revenue comes from venues, which subscribe to the console and pay for visibility campaigns. Part comes from the optional assistant subscription (§14). What we sell to venues is the chance to be found and figures about groups of people, never your individual data. §6 explains exactly where the line is.
5.1 Three different things. When you register:
5.2 The full list.
| Consent | What it enables | When we ask | Where you withdraw it |
|---|---|---|---|
| Consent to preference profiling — b) | Personalised content | At registration | Settings → Notifications and privacy |
| Consent to the selection of sponsored content — d) | Sponsored content chosen on your preferences and going-out intent | At registration | Settings → Notifications and privacy |
| Consent to usage statistics — i) | Your path through the app linked to you, and Firebase's automatic statistics | On first launch, before the introduction screens | Settings → Notifications and privacy |
| Consent to commercial communications from venues — e) | Promotions by notification | At registration | Settings → Notifications and privacy |
| Consent to gender identity data (Art. 9) | Gender in the figures for venues | At registration, next to the field | By editing your profile, or in Notifications and privacy |
| Consent to use of location for the feed — f) | What is nearby | After you grant the phone's location permission | Notifications and privacy, Location section |
| Consent to use of location for advertising eligibility — f) | The municipality you are in, to know which campaigns can reach you | As above | As above |
| Consent to use of location for attendance verification — f) | Attendance verification in missions | As above | As above |
| Consent to share allergens with the venue (Art. 9) — g) | Your allergies to that venue, for that booking | At every booking, if you say someone has allergies | In the booking details |
| Consent to share preferences with the venue | Your preferences to that venue, for that booking, if the venue uses this feature | At every booking, only at those venues | In the booking details |
| Consent to attendance photos | The photo that completes a mission step | At every mission | Cannot be withdrawn for a photo already verified: the photo remains as proof of the mission, without being linked to you (§11.3) |
| Consent to sign the review | Your name on that review | When you write the review | In the booking details |
A phone permission (location, notifications, camera, calendar) is not a privacy consent: it allows the app to use a phone feature. The consent decides what we use it for.
5.3 If you say no, we do not ask again. A consent you refuse is not offered a second time. At most, once, a notice explains what changes without personalisation and takes you to the settings, where you decide.
5.4 Withdrawing. You can withdraw any consent at any time, as easily as you gave it. Withdrawal takes effect immediately, including for campaigns already queued. It does not make what we did before unlawful.
5.5 We keep a record of your choices. For every consent given, refused or withdrawn, we record which consent, the version of the text, the date and time, where in the app it happened and, where relevant, the booking, mission or review it refers to. This lets us show what you chose (§17).
6.1 A venue does not see your profile. It has no screen, export or feature that tells it who you are, what you like or where you have been. It does not see who follows it or who marked it "Interested": it only sees how many.
6.2 It sees figures about groups of people, such as: "this week, in your area, demand is concentrated on Thursday evenings".
6.3 Below certain thresholds we show nothing. A figure calculated on only a few people could make them recognisable, so we apply these thresholds:
| What | Threshold | Below the threshold |
|---|---|---|
| Indications about a single venue | at least 4 people | We show nothing |
| Area data | at least 50 people | Full distribution with percentages |
| 20 to 49 people | Only the top three items in order, without figures | |
| fewer than 20 people | We show nothing | |
| Comparison with similar venues | at least 8 venues | We widen category and area, and say so |
Fast scrolling past cards never becomes a figure for a venue. If you have objected (§18.4), your contribution is left out of these figures.
6.4 Allergies never enter these figures, in any form or on any plan.
6.5 When a venue sees something about you. This happens only in three cases, always because of something you do:
7.1 Three uses, three consents. We ask for consent separately for:
a) showing you what is nearby;
b) working out whether a campaign from a venue in your area can reach you, based on the municipality you are in;
c) verifying your attendance at a venue or event when you complete a mission step (§11.2).
7.2 How we handle it. We collect your precise location only while you are using the app, never in the background. Coordinates are used in the moment and we do not keep a history of your movements: the feed uses your current location, and signals contain at most the municipality. For an attendance verification we keep the outcome, verified or not, for 12 months (§17), not the point where you were.
7.3 If you say no. The app still works, using the municipality you gave in "Where you usually go out". We use that municipality to show you something relevant, and we do not use it to decide which campaigns can reach you.
8.1 They are health data. Food allergies and intolerances belong to the special categories of personal data (Art. 9 GDPR). We apply stricter rules to them than to anything else.
8.2 We ask at every booking, and we do not keep them. During a booking we ask whether anyone has allergies. If you say yes, you choose from a closed list and we ask for your explicit consent to share them with that venue, for that booking. The box is empty. We do not store allergies in your profile: next time we ask again.
8.3 What you can select. Only items from a predefined list: the fourteen allergens in Annex II to Regulation (EU) 1169/2011, namely cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame seeds, sulphur dioxide and sulphites, lupin, molluscs. There is no free-text field, because it would bring us health information we do not need.
8.4 Guests. If you book for several people, you may give a guest's allergies only if that guest asked you to, so that the venue can take them into account. In bookings made from a group, each person gives their own allergies, and the person making the booking does not see them.
8.5 What they are never used for. Allergies are never used to:
8.6 The menu allergen filter works only on your phone. What you select does not reach us.
8.7 If you withdraw consent. You can withdraw consent from the booking details, even after confirmation: the allergies are removed from the booking and the venue no longer sees them. If the request was sent by WhatsApp to a venue that is not registered (§9.3), we cannot delete the message from the venue's phone.
8.8 It is not a guarantee. Sharing an allergy does not guarantee that the venue can manage it. If it is serious, also say so in person or call the venue beforehand.
9.1 SwipeOut is not a party to the booking. The relationship is between you and the venue: we send your request and show you the reply. We do not collect deposits and do not guarantee the table.
9.2 Registered venues. In its console the venue receives your first name and surname, phone number, email, date and time, number of people, notes and, only with your consent, allergies and preferences. Guests appear as "Guest 2", "Guest 3". The venue may use this data only to manage that booking and is contractually accountable to us for this.
9.3 Venues that are not registered. If the venue does not use SwipeOut but has a mobile number, we send the request by WhatsApp from SwipeOut's number, through Meta's WhatsApp Business service. The message contains the same data as §9.2 and, only with your consent, allergies. We tell you clearly before sending.
In this case the venue has no contract with us: it receives the data as an independent recipient, to answer your request, and we cannot delete the message from its phone. If you do not want this, you can call the venue instead of booking through the app.
9.4 No-show. The venue can record that you did not turn up. You see this in the app with a neutral message. In this version it has no effect on your account, except that we will not invite you to review that booking.
9.5 Calendar. If you add a booking to your phone's calendar, we write only the title, times and address, with no notes, allergies or guests. No data comes back to us from there.
10.1 Who can write one. The day after a completed booking at a registered venue, we invite the person who booked to tell us how it went: a rating, up to three aspects and, if you like, a short text. You can write at most one review per venue per month.
10.2 For the venue, reviews are anonymous. Reviews do not reach the venue one by one. We deliver them once a month, in a batch, and only if the batch includes at least 4 different people. We remove date, time, number of people, event and any detail that could reveal who wrote it, and we shuffle the order. If the threshold is not reached within three months, the batch is deleted without being delivered.
10.3 Signing. You can choose to sign a review. The venue then receives your name with that review straight away, outside the batch. This is a consent you can withdraw.
10.4 Moderation. Before sending, the text goes through an automated check that removes only certain parts, such as references to health, names, contact details or details that could identify you. You see the result before confirming. If you disagree, you can ask for a person to review it.
10.5 Supporting photos. For some aspects (food, price, atmosphere) you can attach a photo. A member of our team checks it, and it must not show recognisable people.
10.6 The link to you is erased. For 60 days after delivery we keep the link between you and the review, so you can receive any reply from the venue. After that the link is erased and the review can no longer be traced to you.
Groups can be closed (invitation only), private (invitation or an approved request) or open. From outside, only the name, type, number of members and entry rule are visible.
Inside the group, other members see your username and profile photo. They do not see your level, preferences or area.
There is no chat. Members exchange only proposals of venues and events, which can come with a short message. Group names, messages and images go through automated moderation that removes only the parts that are not allowed; you can ask for a person to review the decision.
Proposals generated by the assistant take into account the preferences of members who have given consent b). The model receives the sentence written by the person proposing, not members' profiles.
The group name and the list of participants never reach a venue.
To complete a mission step, you show that you are at that venue or event with a photo, your location and the time.
Photograph the venue, not the people. Face detection runs on your phone: if there are faces in the photo, it is not sent. When the photo reaches us, we remove the file's hidden data, including the coordinates where it was taken. An image analysis service returns only labels to us, such as "venue interior", and does not analyse people.
A photo that is not valid is erased immediately. A valid photo is not visible to anyone, including other members and the venue. It remains as proof that the mission was completed: if you delete your account, the photo stays without your name and without the location it was taken from, and can no longer be linked to you.
Verified attendance raises your level and can give you access to some groups. Only you can see your level, points and achievements. They stay inside SwipeOut: they are not an assessment of you as a person, we do not share them with anyone and they have no effect outside the app. No mission and no reward is linked to drinking alcohol.
12.1 How we order what you see. If you have given consent b), the order of the feed, map, calendar and assistant answers depends on:
The calendar is always in time order. Without consent b), the order depends only on proximity, time and popularity: this is the non-personalised view. No venue or event is hidden by the ordering: you can find them all with search.
12.2 Sponsored content. All paid content carries the "Sponsored" label, which cannot be removed. Across the whole platform you receive at most one commercial communication a day, card or notification. Whoever pays for a campaign chooses how many people to reach, not who, and does not receive your identity.
A campaign can reach you:
Without these consents you may still see a sponsored card, chosen without using your preferences or what you do in the app.
12.3 Notifications. There are three kinds of notification:
Beyond essential notifications, you receive at most three a day, of which one commercial. Between 22:00 and 09:00 we send no notifications, except about one of your bookings in the next few hours. Notifications stay in your inbox for 90 days. You manage the notification permission in your phone settings, and consent e) in the app settings.
12.4 Email. We email you only about your account, bookings and data export, and to answer what you ask us. We do not send promotional emails.
13.1 Where we use it. We use artificial intelligence for:
13.2 It can make mistakes. Generated content can be inaccurate. The assistant does not invent venues, events, times or prices: it takes them from the catalogue. Important information should still be checked with the venue.
13.3 What we send to providers. We send providers only what is needed for processing: the text of the question or message and, if you have given consent b), the necessary preferences. We never send your name, email, phone number, profile photo or allergies. Where a technical identifier accompanies the data, that data is pseudonymised, not anonymous, and we treat it as personal data in every respect.
13.4 Do not include health information in your questions. The assistant does not need it. The text of your question is not kept: for 30 days we keep only an encoded version of the request, meaning category, area and time slot, to improve the service.
13.5 Providers do not train their models on your data. Our contracts with them provide for this.
13.6 No automated decisions with significant effects on you. Automated moderation may remove part of your content: you can always ask for a person to review the decision.
14.1 The subscription is optional. The assistant comes with a free allowance of questions, and the subscription increases it. The rest of the app is free.
14.2 How you pay. If you subscribe in the app, you pay through the App Store (Apple) or Google Play (Google). If you subscribe on the web, you pay through Stripe. They process the payment under their own privacy notices. We receive only what we need to know whether your subscription is active, when it renews and, for Stripe, receipt details. We never see your full card number.
14.3 Legal basis. Performance of a contract for the subscription; legal obligation for keeping receipts (§17).
15.1 Providers that process data on our behalf (processors, Art. 28 GDPR):
| Provider | What it does |
|---|---|
| Amazon Web Services | Servers, file storage and login system |
| OneSignal | Delivery of push notifications and service emails. For push it receives only an identifier, the notification text and the link; for email it receives your address and the content of the message |
| Twilio | SMS with the phone verification code |
| Meta Platforms (WhatsApp Business) | Sending booking requests to venues that are not registered (§9.3) |
| Mapbox | Maps |
| Anthropic and OpenAI | Large language models for the assistant, group proposals and text moderation |
| Google (Vertex AI) | Label-based analysis of mission photos |
| Google (Firebase) | Error diagnostics; automatic usage statistics (installs, sessions, device) only with your consent to usage statistics, without the advertising identifier |
15.2 Parties that process data as independent controllers:
15.3 Authorities and professional advisers, where the law requires it or to defend a right.
15.4 No sale. We do not sell your data or share it with advertising intermediaries, data brokers or social networks for their own purposes.
16.1 Our servers and files are in data centres located in the European Union. Our team works from Italy and does not access systems from outside the European Economic Area.
16.2 When data leaves the European Union. Some providers in §15 are based in the United States or may process data from there, even if only for technical support: Amazon Web Services, OneSignal, Twilio, Meta, Mapbox, Anthropic, OpenAI and Google. In these cases the transfer is covered by:
16.3 You can ask for a copy of the safeguards in place by writing to info@swipeout.it.
The rule is simple: we keep data as long as it serves the purpose we collected it for, and no longer.
| Data | Retention period |
|---|---|
| Account data (name, email, date of birth, municipality, username, photo, phone) | As long as you have an account |
| Gender | Until you remove it or delete your account |
| Preferences | Until you reset them, withdraw both b) and d), or delete your account |
| Going-out intent, individual answer | 48 hours |
| Usage signals linked to you | 12 months, then kept only in aggregated form |
| Usage events linked to you (with consent to usage statistics) | 12 months, then kept without any link to you |
| Automatic statistics in Google Firebase | 14 months |
| Searches | 30 days |
| Assistant requests | The text is not kept; the encoded version for 30 days |
| Name and contact details in a booking | 90 days from the booking date |
| Notes and allergies in a booking | 30 days from the booking date |
| Your booking history, visible to you | 12 months |
| Link between you and a review | 60 days from delivery to the venue |
| Name on a signed review | 90 days |
| Supporting photo for a review | 12 months |
| Group proposals and messages | As long as the group exists, and never more than 12 months |
| Outcome of an attendance verification | 12 months |
| Valid attendance photo | As long as you have an account; after that, it remains as proof of the mission without being linked to you (§11.3) |
| Notifications in the inbox | 90 days |
| Data export file | Downloadable for 7 days |
| Support requests | As long as needed to handle them and to show how we handled them |
| Access and security logs | 12 months |
| Record of consents and withdrawals | 5 years from withdrawal or account deletion |
| Receipts for web payments | 10 years, as required by law |
| Registration refused on age grounds | 90 days |
| Backups | Expire through rotation within 12 months. In the meantime we do not use them |
| Pre-registration on the website | Until the launch notice, 12 months at most; if you do not confirm it, the link expires after 7 days |
| Aggregated data that does not identify you | No limit: it is no longer personal data |
You can exercise them at any time by writing to info@swipeout.it and, where indicated, directly in the app.
| Right | What you can obtain |
|---|---|
| Access (Art. 15) | Find out what data we hold and receive a copy |
| Rectification (Art. 16) | Correct inaccurate data, also from Settings → Account |
| Erasure (Art. 17) | Have it erased, including by deleting your account (§19) |
| Restriction (Art. 18) | Have us suspend a processing activity |
| Portability (Art. 20) | Receive your data in a format another service can read |
| Objection (Art. 21) | Object to processing based on legitimate interests, including the figures for venues |
| Withdrawal of consent (Art. 7(3)) | Withdraw any consent, as easily as you gave it |
| Human review | Have a person reassess an automated decision on your content |
18.1 Download your data. From Settings → Notifications and privacy → Download your data you can request a copy of your data. Within 48 hours you receive a ZIP file with a readable page and the data in JSON format, downloadable for 7 days after logging in again.
18.2 Timing. We reply within one month. If the request is complex we may take two more months, and we tell you within the first month.
18.3 Cost. None, unless requests are manifestly unfounded or excessive.
18.4 Objecting to the figures for venues. Write to info@swipeout.it. From the moment we record your objection, your contribution is left out of the figures we provide to venues, including those for periods still in progress. Figures for periods already closed stay as they are. Objecting does not change what you see in the app; consents are there for that.
18.5 Identity check. Before acting on a request we may ask you to confirm it is you, for example by replying from your account email address.
18.6 Complaints. You can lodge a complaint with the Italian Data Protection Authority (Garante per la protezione dei dati personali), Piazza Venezia 11, 00187 Rome — www.gpdp.it — protocollo@pec.gpdp.it, or with the supervisory authority of the EU country where you live or work. You can also go to court.
19.1 In the app. Go to Profile → Settings, scroll to the bottom and tap Delete account. We show you what will happen and, to confirm, we ask you to type the email address of your account. You do not have to give a reason.
19.2 On the web, without installing the app. The page https://swipeout.it/legal/consumer/account-deletion/en explains how to request deletion by email.
19.3 It is final. Deletion happens on confirmation and cannot be undone. If you want to come back, you will need to register again.
19.4 What happens straight away:
19.5 What remains, and why:
19.6 Backups expire through rotation within 12 months.
We use:
In the app you can see the devices linked to your account and log out of all of them.
If a personal data breach puts your rights at risk, we notify the Italian Data Protection Authority within 72 hours. If the risk is high, we also tell you.
21.1 SwipeOut is only for people aged 18 or over, because it features venues and events where alcoholic drinks are served.
21.2 We ask for your date of birth. If you are under 18, registration is refused and the refusal is remembered for a limited period (§17). We do not check documents: we rely on your age declaration.
21.3 If we learn that an account belongs to a minor, we close it and erase the data.
Venue and event listings, and menus reached from a QR code, can also be opened in a browser without an account: they are pages of the web version of the app, at https://swipeout.it. In the browser you can also sign in with email and password.
In the browser:
You can delete this data at any time from your browser settings: you will just have to sign in and answer again.
We use no cookies and no third-party profiling or statistics tools, so we do not show you a cookie banner.
23.1 Every version has a number and a date. When we change something significant, we tell you in the app or by email, with a short summary of changes.
23.2 If a change introduces a new purpose based on consent, we ask for new consent: the consent you gave does not cover it.
23.3 Previous versions are available on request at info@swipeout.it.
Vittorio Barile — controller
Via Don Angelo Sanzò 37, 86017 Sepino (CB), Italy — VAT number 01826370700
Controller's email: info@swipeout.it
For your data and to exercise your rights: info@swipeout.it
In the app: Settings → Notifications and privacy
Version 1.4 — 24 October 2026. The controller's contact and the web addresses move to the new domain: info@swipeout.it and swipeout.it. New §3.8 and purpose j): pre-registration from the website, with the data collected, email confirmation and a maximum of 12 months. Nothing else changes.
Version 1.3 — 10 October 2026. The service changes its name: EasyVent becomes SwipeOut. The controller, web addresses and email stay the same. §22 describes the web version of the app: no cookies or third-party statistics, and what the app stores in the browser. §12.4 no longer promises an email when you delete your account.
Version 1.2 — 30 September 2026. New optional consent to usage statistics (purpose i), asked on first launch: with consent we link usage events to you and Firebase collects automatic statistics; without it, we only record that an action happened. §19 describes deletion as it really works: you confirm by typing your account email, verified attendance photos remain as proof without being linked to you, and there is no final email. Web pages no longer refer to a separate cookie policy: what you need to know is in §22.
Version 1.1 — 25 September 2026. The controller's email changes to info@easyvent.it, the same address to use for your rights. Nothing changes about data, purposes or choices.
Version 1 — 17 September 2026. First publication of the EasyVent Privacy Notice.