Privacy Policy

1. Introduction and scope

1.1 This Privacy Policy explains how FanPlan ("FanPlan", "we", "us", "our") collects, uses, stores, shares and protects personal data when you use the FanPlan mobile apps for iOS and Android, the website at www.fanplan.app, the FanPlan Groups portal, the FanPlan-for-Shops enquiry form, and every other product or feature that links to this policy (together, the "Service").

1.2 FanPlan is a football trip and matchday companion. You can browse fixtures and clubs, plan a trip around a match, add flights, hotels and notes to an itinerary, invite friends to a shared trip, check in near a stadium on matchday, collect digital passport stamps, and read matchday guides written by our editors and by other fans. Almost every one of those features needs some personal data to work. This policy tells you which data, why, for how long, and who else sees it.

1.3 We wrote this policy to be read, not skimmed past. Each section stands alone, so you can jump to the part you care about: what we collect (section 5), why and on what legal basis (section 7), who receives it (section 9), how long we keep it (section 11), and what you can do about it (sections 13 and 14).

1.4 This policy applies to personal data we handle as a data controller, meaning that we decide why and how the data is used. It is written to meet the transparency duties in Articles 12, 13 and 14 of the EU General Data Protection Regulation (Regulation (EU) 2016/679, the "GDPR"), the UK GDPR and Data Protection Act 2018 where they apply, and the Italian Personal Data Protection Code (Legislative Decree 196/2003, as amended). If you live elsewhere, we apply the same standard to everyone, and local laws that give you more rights still apply.

1.5 This policy does not cover other companies' websites, apps or services that you reach through FanPlan, such as a hotel booking page or a ticket checkout. Those companies are separate controllers with their own policies. Section 16 explains where our responsibility stops and theirs begins.

1.6 If you are a member of a club, supporters' group, travel organiser or other organisation that invited you to FanPlan through our Groups product, that organisation may also process your data for its own purposes. Section 19 explains how the roles are split.

1.7 Please read this policy together with our Terms of Use and our Cookies and Similar Technologies notice. Where the Cookies notice gives more detail about a specific technology, it forms part of this policy.

2. Plain-language definitions

2.1 "Personal data" means any information that identifies you or can reasonably be linked to you, such as your email address, your display name, your device's push token, or the time and place of a check-in.

2.2 "Processing" means anything we do with personal data: collecting, storing, adapting, sending, showing to another person, restricting or deleting it.

2.3 "Controller" is the organisation that decides why and how personal data is processed. "Processor" is a company that handles personal data only on our instructions and under a contract, for example our hosting provider.

2.4 "Account" means the FanPlan profile you create with an email and password, or with Sign in with Google or Sign in with Apple.

2.5 "Trip" means a plan you create in FanPlan, with a title, dates, a match or matches, and itinerary items such as flights, hotels, notes and places. "Shared trip" means a trip that you or somebody else invited another FanPlan user to join.

2.6 "Check-in" means the action of confirming, from inside the app and near the stadium, that you attended a match. "Passport" means the collection of stamps, badges and statistics you earn in FanPlan.

2.7 "Organisation" and "Group" mean a club, supporters' association, tour operator, school, company or other body that uses our Groups portal to publish a base plan for invited fans.

2.8 "Device identifiers" means technical identifiers created by your phone or by our software, such as a Firebase installation ID or an APNs or FCM push token. They are not the same as your advertising identifier, which we do not use (see section 6).

3. Who is responsible for your data

3.1 The data controller is the legal entity that operates FanPlan: FAN PLAN S.R.L., registered office Via Giuseppe Frua 11, 20146 Milano (MI), VAT number and tax code 14908040968, REA MI-2814813 (Milano Monza Brianza Lodi), PEC [email protected]. You can reach the people responsible for FanPlan at the contact details in section 23.

3.2 Contact for all privacy matters: [email protected]. You can also open the app, go to Contact us, and choose the category "Data request". Both routes reach the same team and are logged so that we can prove we answered within the legal deadline.

3.3 Data protection officer and representatives: we have not appointed a data protection officer because our core activities do not require one under Article 37 GDPR. If that changes, we will publish the officer's details here. If we are required to name an EU or UK representative for a particular jurisdiction, we will list it here as well.

3.4 Supervisory authority: you have the right to complain to the data protection authority of the country where you live, work, or where you think the problem happened. In Italy this is the Garante per la protezione dei dati personali (www.garanteprivacy.it). In the European Union you can find your authority at edpb.europa.eu. In the United Kingdom it is the Information Commissioner's Office (ico.org.uk). We would appreciate the chance to fix the problem first, so please write to us, but you are never required to do so.

4. How FanPlan works with data, in one page

4.1 When you create an account, we create a profile record on our servers. The profile holds your sign-in details, display name, language and subscription tier. The app keeps a short-lived sign-in token in your phone's secure storage so you do not have to log in every time.

4.2 When you plan a trip, the title, dates, matches and itinerary items are saved to your account on our servers so that they appear on all your devices. A copy of recent trips is also kept in an on-device cache so the app opens quickly and works when you are offline.

4.3 When you invite someone to a trip, we store the invitation, send them an email or a link, and, after they accept, show them the trip. Everyone on the trip can see the trip details and, for items that people added, who added them. Section 5.5 explains exactly who sees what.

4.4 When you check in at a stadium, the app asks your phone for its approximate position at that moment. We compare it with the stadium's geofence, record whether the check-in was valid, and award a passport stamp. We do not track you in the background and we do not follow you around the city.

4.5 When something goes wrong in the app, a crash report is sent to a diagnostics service so that we can fix it. When you open screens, the app may send usage events so that we can learn which features are used. Section 5.17 says exactly what these contain.

4.6 When you tap a link to a hotel, flight, ticket or transfer provider, FanPlan opens the partner's own site or app. From that moment the partner, not FanPlan, collects the data you type there.

4.7 Our servers run in the cloud with the providers listed in section 9. Our staff use internal tools, the Admin CMS, the Content Studio and the Groups portal, to maintain fixtures, content and support requests. Those tools can show the same records described in this policy, but only to authorised staff and only for those purposes.

5. The personal data we process

5.1 Account and sign-in data. When you register we process your email address, your display name, your password in hashed form (never in plain text) if you choose email sign-in, your preferred language, the authentication provider you used (email, Google or Apple), and the provider's unique subject identifier so that your account stays linked to the right login. If you use Sign in with Apple and choose to hide your email, we receive Apple's private relay address instead and we treat it like any other email address. We also store the date and time you registered, the date you accepted our notices (the gdprConsentAt timestamp), your last sign-in, your profile visibility setting, your experience points (XP) and level, and your subscription tier. We do not currently offer Facebook or Instagram sign-in to fans.

5.2 Profile and avatar. You may add a profile photo or choose a preset avatar. A photo you upload is stored in our object storage and is shown to the people your profile is visible to: for example, other travellers on a shared trip. You can change or remove it at any time in your personal area.

5.3 Preferences. We store the settings you choose: language, theme, notification choices, home club or favourite clubs, and whether your passport is public. These make the app behave the way you expect and are part of your profile.

5.4 Trips and itinerary data. For each trip we process its title, dates, the matches linked to it, the cover image you pick or upload, the destination, the list of companions' names or labels you type in, and itinerary items. An itinerary item can be a flight (airline, flight number, times, airports, booking reference if you type it in), a hotel or stay (name, address, dates), a ticket note, a restaurant or place from our guides, a transport leg, or a free-text note. We do not ask you for passport numbers, payment cards or identity documents, and we ask you not to type them into notes. Please also avoid putting other people's sensitive information into trip notes. For each item we also record who created it and when, because shared trips show that information to the other travellers.

5.5 Shared trips and invitations. When you invite someone, we process the invitee's email address (or the link you share), the role (owner or traveller), the invitation status (pending, accepted or declined), and the time of each event. After an invitation is accepted, the invitee sees the trip title, dates, matches, items, the display names and avatars of the other travellers, and the "added by" name on each item. The owner can see who accepted. An invitee can leave a shared trip; the owner can remove an invitee. Items that a traveller added to a shared trip belong to the trip while it exists. If you delete your account, items you added to a trip owned by someone else stay on that trip so the other travellers' plan remains complete, and the "added by" label may remain with them; on request we will remove or anonymise that label (section 14). If you type a friend's name into a trip as a companion label, that name is stored as free text inside the trip, so please make sure the person is comfortable with it.

5.6 Check-in and location data. When you use Check in, and only then, the app requests the device's location through the operating system's permission prompt. We process the latitude and longitude returned at that moment, the time reported by your device, the match and stadium involved, whether the check-in passed validation, the reason if it failed, and whether the check-in was queued offline and sent later. Queued offline check-ins are stored on your phone until a connection returns. We use location only to verify attendance and award a stamp and XP. We do not use it for advertising, we do not sell it, and we do not build a movement history of where you go before or after a match. If you decline the location permission you can still use every other part of FanPlan; you simply cannot earn a check-in stamp for that match.

5.7 Matchday reminders and notifications. If you allow notifications, we store your device push token (an FCM token on Android and an APNs token delivered through Firebase on iOS), the platform, the app version and the language so that we can deliver reminders such as a match countdown or a check-in reminder before and after kick-off. We keep a small log of which reminder slots we have already sent you for each match so that we do not send duplicates. You can turn notifications off in the device settings at any time.

5.8 Passport, stamps, badges and XP. When a check-in is validated we create a passport stamp that records the match, the date, the city and country, and any badge or level progress it unlocked. If an administrator grants a stamp manually (for example after a support request), we record the grant and the reason. Your passport is private by default. If you switch on a public passport page, the stamps, name and avatar you choose to publish become visible to anyone with the link.

5.9 Friends and social features. If you add friends, we store the connections you create and the status of each request. We use this to show friends on shared trips and in passport comparisons. You can remove a friend at any time.

5.10 Content you submit. This includes golden tips and recommendations you write about a city or stadium, trip notes, cover photos, and other text or images you choose to upload. Your display name can be shown next to a published tip. Before a tip becomes visible to others it may be checked automatically and by our moderators for spam, abuse and policy violations. Content that you share publicly can be seen, copied and shared by other people outside our control; please think before you post.

5.11 Support and contact messages. When you use Contact us, we process your name if you give it, your email, the category you select, the message, any attachment, your app version and your language. We store the message so that we can reply and to demonstrate that we responded to data requests. Our team may be notified of a new message by email or an internal messaging channel. When you delete your account, your past messages are kept without a link to your account (anonymised) until their retention period ends.

5.12 FanPlan for Shops enquiries. Local businesses can send an enquiry about listing in the FanPlan guides. We process the business contact name, email, business name, message and the time of the enquiry.

5.13 Groups and organisation data. If you are a manager of an organisation, we process your identity from the single sign-on you use (typically Google), your role in the organisation and the activity you perform in the Groups portal. If you are an invited fan, we process your email address, the invitation and the base plan items copied into your personal copy. Your own additions to a trip are yours and are not editable by the organisation.

5.14 Subscription and payment data. Paid plans, where offered, are sold in one of two ways: through Apple's App Store or Google Play, in which case Apple or Google processes your payment and tells us only that a subscription of a certain tier is active, or through a web checkout operated by our payment provider Stripe, in which case Stripe collects your payment details and we store a Stripe customer identifier, the plan, and the status and renewal dates. We never receive or store your full card number in FanPlan systems. We do not collect health data or other special-category data by design.

5.15 Technical and security data. Our servers automatically record your IP address, the date and time of each request, the endpoint called, the response status, the app version and platform, and error details. We use this to keep the service running, to detect abuse and to apply rate limits, for example the limit on how many contact messages one address can send per hour. We also store short-lived tokens for password resets and sign-in sessions.

5.16 Data stored only on your device. The app keeps caches on your phone: recent trips, club hub content, fixtures, translated labels, queued check-ins and interface preferences. Sign-in tokens are kept in the device's secure storage (Keychain on iOS, Keystore-backed storage on Android). This data does not leave your device unless the app syncs it. Clearing the app's data or uninstalling the app removes it.

5.17 Diagnostics and usage data. FanPlan includes Google Firebase components for stability and performance. Firebase Crashlytics collects crash reports containing the device model, operating system version, app version, the stack trace of the crash and a pseudonymous installation identifier. Firebase Performance Monitoring measures start-up time, screen rendering and the speed and success rate of network requests. The app also records which screens and features are used (for example a screen view or a push-permission choice) through Firebase Analytics hooks and through our own first-party usage endpoint, which can forward events to an internal analytics tool. We use this information in aggregated form to find bugs and to improve the product. We do not use it to build advertising profiles and we do not share it with advertisers. Where the law requires your consent for analytics, we ask for it before turning it on; see section 7 and the Cookies notice.

5.18 Data we receive from other sources. We combine your data with public or licensed data that is not about you personally: fixtures, results and club information from SportMonks, weather forecasts from OpenWeather, flight status information from Flightradar24 when you add a flight number, map and place information from Google Maps Platform and Google Places, and editorial content from our own CMS. We send these providers only what is needed to answer the query, for example a flight number and date, a place name, or a coordinate for a forecast. We do not send them your name, email or account identifier.

5.19 Information you give us voluntarily. Anything else you send us, for example survey answers, feedback or bug reports, is processed for the purpose for which you sent it.

6. Data we do not collect or do

6.1 We do not sell your personal data, and we do not share it with data brokers.

6.2 We do not show third-party advertising in the app, and we do not integrate advertising networks or advertising software development kits today. We do not read or use your device's advertising identifier (IDFA or Android Advertising ID), and the iOS app does not ask for App Tracking Transparency permission because it does not track you across other companies' apps and websites.

6.3 We do not run continuous or background location tracking. Location is read only when you press Check in, and the permission can be set to "while using the app".

6.4 We do not collect special categories of personal data (such as health, biometric identification, political opinions, religious beliefs, sexual orientation or trade-union membership) on purpose. A football supporter's club preference, standing alone, is not special-category data in our view, but if you write sensitive information into a free-text note, you are choosing to put it there.

6.5 We do not take payment card numbers into FanPlan systems.

6.6 We do not make decisions about you that have legal or similarly significant effects by purely automated means.

6.7 We do not read your contacts, photo library or calendar unless you tap a feature that needs it (for example choosing a cover photo) and grant the permission.

7. Why we use your data and our legal bases

7.1 Under the GDPR we may only use personal data if we have a legal basis. We rely on the bases below. Where we say "contract", we mean what is needed to provide the Service you asked for under our Terms of Use.

7.2 Providing your account and the core Service (Article 6(1)(b), contract). We create and secure your account; sync your trips and itineraries; show fixtures, club hubs and guides; run invitations and shared trips; verify check-ins and award stamps; deliver push reminders you enabled; send transactional emails such as sign-up confirmation, password reset and invitations; and run your Groups invitations.

7.3 Security, fraud and abuse prevention (Article 6(1)(f), legitimate interests). We process IP addresses and technical logs to detect and block attacks, credential stuffing, spam, scraping and fake check-ins, to apply rate limits, and to investigate incidents. Our interest is keeping the Service and its users safe. We have weighed it against your rights and keep logs only for the periods in section 11.

7.4 Stability, performance and product improvement (Article 6(1)(f), legitimate interests, and Article 6(1)(a), consent where required). Crash reports and performance measurements help us repair the app. We think this is within your reasonable expectations and has a small privacy impact, because it is pseudonymous and used in aggregate. Usage analytics that involve reading or storing information on your device are, where the ePrivacy rules require it, based on your consent, which you can withdraw as described in the Cookies notice. You can object to processing based on legitimate interests at any time (section 13).

7.5 Support and communication (Article 6(1)(b) and 6(1)(f)). We answer your messages and data requests, and we keep a record of them to show that we responded and to defend legal claims.

7.6 Moderation of public content (Article 6(1)(f)). We review golden tips and other public contributions to keep the community safe and relevant, to comply with notices of illegal content and to protect other users. Where we use automated checks, a human reviews anything that would otherwise lead to your account being restricted.

7.7 Consent (Article 6(1)(a)). We ask for your consent for optional push notifications, for optional analytics or marketing technologies where the law requires it, and for any marketing email we may send in future. You can withdraw consent at any time in your device settings or in the app; withdrawing does not affect processing that happened before. We store when you accepted our notices (gdprConsentAt); our counsel will confirm whether we must additionally store the purpose and policy version, and we will update this text if so.

7.8 Legal obligations (Article 6(1)(c)). We keep billing and tax evidence where the law requires, answer lawful requests from authorities, and handle consumer and data-protection complaints.

7.9 Legal claims (Article 6(1)(f)). We may keep and use data when it is necessary to establish, exercise or defend a legal claim.

7.10 Business changes (Article 6(1)(f)). If FanPlan is involved in a merger, acquisition, financing or sale of assets, data may be transferred to the successor under the same protections, and we will tell you if the controller changes.

7.11 Where we need your data to provide the Service and you do not give it to us (for example you refuse to give an email address), we may not be able to create your account. Where we ask for optional data, for example a profile photo or location, saying no never reduces your other rights.

8. Automated processing and recommendations

8.1 FanPlan shows content that depends on the club, city or match you pick. This is a simple lookup, not profiling that produces legal effects.

8.2 Check-in validation compares the coordinates you send with a geofence and the match time window. A failed check-in does not suspend your account. If you believe a validation failed unfairly, contact us and a person will review it.

8.3 Spam and abuse filters may automatically hold a golden tip, an invitation or a contact message for review, or block a burst of requests from one address. You can ask for human review of any such outcome.

8.4 Where we translate editorial content (for example matchday tips) into another language, we use a machine translation service on the content text only, not on your account data.

9. Who receives your data

9.1 We share personal data only where it is needed, with the categories of recipients below. For each processor we have, or are putting in place, a data processing agreement under Article 28 GDPR. Our counsel keeps the current list of processors; you can ask for it at [email protected].

9.2 Infrastructure providers (processors). Railway hosts our application servers, Postgres database and cache. Cloudflare provides content delivery and R2 object storage for avatars, cover photos and editorial media. They process your data only to run our infrastructure.

9.3 Google (processor for Firebase, independent controller for sign-in and maps). Firebase Cloud Messaging delivers push notifications; Firebase Crashlytics, Performance Monitoring and Analytics provide diagnostics; Google Sign-In authenticates you if you choose it; Google Maps Platform draws maps and place information. Google acts as our processor for the Firebase services and as an independent controller for the sign-in account you hold with Google and for certain map data. See policies.google.com/privacy.

9.4 Apple (independent controller and delivery partner). Sign in with Apple authenticates you if you choose it, the Apple Push Notification service delivers iOS notifications, and Apple processes App Store purchases. Apple's privacy policy is at apple.com/legal/privacy.

9.5 Payment provider. Stripe processes web payments where we offer them, as a processor for the payment service and an independent controller for some compliance and fraud processing. Apple and Google process in-store subscriptions as independent controllers.

9.6 Email delivery. A transactional email provider (currently Resend) sends sign-up, password reset, invitation and notice emails on our behalf. It sees the recipient address and the message.

9.7 Data providers we query. SportMonks (fixtures and club data), OpenWeather (weather forecasts), Flightradar24 (flight status) and search or maps services receive only the technical query needed, for example a flight number and date or a coordinate, and not your identity.

9.8 Other travellers and organisations you choose. When you invite people or join a shared trip, they receive the data described in section 5.5. If you accept a Groups invitation, the organisation sees that you accepted and the base-plan items it published. If you make your passport public, anyone with the link sees what you publish.

9.9 Embedded video. Some guides embed YouTube videos through the YouTube player. When you play a video, Google may set cookies or read device identifiers and receive your IP address. We ask you to start a video deliberately; see the Cookies notice.

9.10 Professional advisers, auditors and authorities. We may disclose data to lawyers, insurers, auditors and accountants under confidentiality duties, and to courts, regulators or law enforcement when we are legally required to, or when we believe in good faith it is necessary to protect rights, safety or the integrity of the Service.

9.11 Staff. Our employees and contractors can access personal data on a need-to-know basis through authenticated staff tools, under confidentiality obligations. Staff access is limited to support, moderation, content and operations.

9.12 Partners you follow. When you tap a link to Booking.com, Skyscanner, Ticketmaster, Viagogo, Sports Events 365, a club shop or a transfer provider, FanPlan opens the partner's website or app and may add an affiliate parameter to the link so that the partner can attribute the visit. We do not send the partner your name, email or account identifier unless a feature explicitly says so before you proceed. Everything you enter on the partner's site goes to the partner.

10. International transfers

10.1 Some of our providers are located outside the European Economic Area (EEA) or the United Kingdom, in particular in the United States. When we transfer personal data to such a recipient we rely on one of the safeguards in Chapter V GDPR: an adequacy decision (including the EU-US Data Privacy Framework where the recipient is certified), or the European Commission's Standard Contractual Clauses together with a transfer impact assessment and supplementary measures where needed. The UK International Data Transfer Addendum applies to UK transfers.

10.2 Our primary database is hosted in the region selected in our Railway project settings, and our object storage is replicated by Cloudflare globally to serve files quickly. Counsel will confirm the exact regions and update this section before we make any residency claim.

10.3 You can request a copy of the safeguards we use by writing to [email protected].

11. How long we keep data

11.1 We keep personal data only as long as needed for the purposes in section 7, then delete or anonymise it. The periods below are our standard periods; a shorter or longer period may apply if the law requires it or if a legal claim is pending.

11.2 Account and profile: for as long as your account exists, and then up to 30 days after you delete it (the time needed to complete deletion across systems and to let you change your mind in case of an accidental request), except for limited billing or legal evidence we must keep.

11.3 Trips, itinerary items, stamps and passport: until you delete them or your account. When an owner deletes a trip, the trip is removed for all travellers.

11.4 Check-in and location logs: up to 90 days. Passport stamps, which record the match and place but not a track of your movement, remain as part of your passport until you delete them or your account.

11.5 Support and contact messages, and shop enquiries: up to 24 months after the conversation ends, or longer where needed for a legal claim.

11.6 Server and security logs, including IP addresses: typically 90 days.

11.7 Crash reports and performance data: per Google's Firebase retention settings, generally 90 days for crash reports.

11.8 Password reset and sign-in tokens: until they expire or are used, normally minutes to days.

11.9 Invitations: until accepted, declined, revoked or expired, and then for a short period for audit.

11.10 Billing records: for the period required by tax and accounting law, usually up to ten years in Italy.

11.11 Backups: deleted data may remain in encrypted backups until those backups are overwritten on the provider's normal rotation. We do not use backups to restore a deleted account's data for any other purpose.

11.12 On-device cache: until you clear the app's data or uninstall the app.

11.13 Public passport pages and shared copies: removed or anonymised when the owner deletes the source, subject to technical delay in caches and search engines that we do not control.

12. Security

12.1 We protect personal data with technical and organisational measures that fit the risk, including encryption in transit using TLS, hashed and salted passwords, short-lived access tokens with refresh tokens, secure storage of tokens on your phone, role-based access to staff tools, rate limiting, monitoring of unusual activity and software dependency updates.

12.2 Access to production data is restricted to authorised staff, and administrative areas can be limited to approved addresses.

12.3 No online service is completely secure. You can help us by choosing a strong, unique password, signing out on shared devices, and telling us at once if you think someone else has accessed your account.

12.4 If a personal data breach is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within 72 hours where the law requires, and we will notify you without undue delay if the risk is high.

13. Your rights

13.1 You have the following rights over your personal data, subject to the conditions and exceptions in the law:

13.2 Right of access (Article 15). You can ask whether we process your data, receive a copy, and receive information about the purposes, categories, recipients, retention and sources.

13.3 Right to rectification (Article 16). You can ask us to correct inaccurate data and complete incomplete data. Most details, including your display name, can be edited directly in your personal area.

13.4 Right to erasure (Article 17). You can ask us to delete your data, for example when it is no longer needed or you withdraw consent. You can also delete your account from the app (section 14).

13.5 Right to restriction (Article 18). You can ask us to pause the use of your data while we check a dispute about accuracy or about our legitimate interests.

13.6 Right to data portability (Article 20). You can ask for the data you provided to us, based on consent or contract, in a structured, commonly used, machine-readable format, and ask us to send it to another controller where technically feasible.

13.7 Right to object (Article 21). You can object at any time to processing based on our legitimate interests, and we will stop unless we show compelling legitimate grounds or the processing is needed for legal claims. You can object to direct marketing at any time and we will stop at once.

13.8 Right to withdraw consent (Article 7(3)). Where we rely on consent, for example for push notifications or optional analytics, you can withdraw it as easily as you gave it, in the device settings or in the app.

13.9 Rights about automated decisions (Article 22). You have the right not to be subject to a decision based solely on automated processing that has legal or similarly significant effects. We do not make such decisions.

13.10 Right to lodge a complaint. See section 3.4.

13.11 How to exercise your rights. Use Contact us in the app and choose "Data request", write to [email protected], or, for deletion, use Personal area then Delete account. To protect you, we may ask for information that confirms you are the account holder, for instance asking you to reply from the account's email address or to confirm a detail only you would know. We will not ask for more than is needed.

13.12 Deadlines. We answer within one month of receiving your request. If your request is complex or we have received many, we may extend the deadline by up to two further months, and we will tell you within the first month and explain why.

13.13 Cost. Exercising your rights is free. If a request is clearly unfounded or excessive, in particular if it is repeated, we may charge a reasonable fee or refuse to act, and we will explain why.

13.14 Limits. We may be unable to fully meet a request when it would reveal other people's personal data, when the law requires us to retain the data, or when the data is needed for a legal claim. We will always tell you what we did and why.

13.15 California and other US state rights. If you live in a US state that grants privacy rights, you may have the right to know, delete, correct and opt out of the sale or sharing of personal information. We do not sell personal information and we do not share it for cross-context behavioural advertising. You can use the same contact routes above and we will not discriminate against you for exercising your rights.

14. Deleting your account

14.1 You can delete your account at any time in the app: Personal area then Delete account. You can also ask us in writing.

14.2 What deletion removes: your profile, sign-in links, display name, avatar, preferences, trips you own (including their items), stamps, XP, friend connections, golden tips you authored, push tokens and invitations. If you have a Stripe customer record, we delete it as well. Items you added to trips owned by other people stay on those trips so that the other travellers' plan stays complete. The "added by" name shown with them can be removed or replaced with a neutral label if you ask us to when you delete your account or afterwards.

14.3 What we keep: contact messages and data requests are kept without a link to your account until their retention period ends; billing evidence we must keep by law; security logs for their normal period; and encrypted backups until they rotate out. Subscriptions bought through Apple or Google must be cancelled in the store; deleting your FanPlan account does not cancel a store subscription.

14.4 Bookings you made with partners (hotels, airlines, ticket sellers) are not affected, because they are contracts between you and the partner. Groups organisations you do not own are not deleted when you delete your account.

14.5 Deletion normally completes within 30 days. We will tell you if a technical issue delays it.

15. Children

15.1 FanPlan is not directed at children. You must be at least 16 years old to create an account, or have the consent of the holder of parental responsibility if the law of your country sets a higher digital-consent age than the minimum we apply. Italy applies the age of 14 for digital consent, and many EU countries apply 13 to 16; we apply the more protective age of 16 to keep the rules simple.

15.2 We do not knowingly collect personal data from children below that age without valid parental consent. If you are a parent or guardian and you believe your child has created an account, contact [email protected] and we will delete it promptly.

15.3 Store age ratings for the app are kept aligned with this policy.

16. Partner links, affiliates and ticket sellers

16.1 FanPlan is a planning companion. It is not a travel agent, ticket seller, airline, hotel or transfer provider, and it is not the merchant of record for any booking.

16.2 Outbound partner links. Home, Club Hub and Trip screens may link to official clubs, Booking.com, Skyscanner, Ticketmaster, Viagogo, Sports Events 365 and similar providers. We may earn an affiliate commission if you buy after following a link. The link may contain an affiliate identifier so the partner knows the visit came from FanPlan. It does not carry your account details.

16.3 What we do not copy. We do not scrape partner prices, reviews or photos onto FanPlan servers, and we do not store your booking form data. If you buy, the partner collects your payment and personal data under its own policy.

16.4 Sports Events 365. Where enabled, we show event labels and a buy link to ticket.sportsevents365.com. Checkout takes place on their site, and they are an independent controller. If an order is created through our API partnership, they may send us a technical notification with the order status; we do not receive the personal data you type into their checkout form. We will not pass your email to them unless the product says so first.

16.5 Google Places and Maps. We use Google's services to show place names, ratings, photos and maps. Google's attribution requirements apply, and Google processes data under its own policy when you interact with a map.

16.6 Always check the partner's own privacy policy before you submit personal information to them.

17. Device permissions and what they are for

17.1 Location (while using the app): only to verify a check-in. You can deny or revoke it in settings.

17.2 Notifications: to send matchday and check-in reminders if you opt in.

17.3 Photos and camera: to choose a profile photo or trip cover if you select that feature. We access only the image you pick.

17.4 Network access: to sync trips, fixtures and content.

17.5 Biometric or device lock features, if used, are handled by the operating system. FanPlan does not receive your fingerprint or face data.

17.6 You can change any permission at any time in your phone's settings. Revoking a permission does not delete data we already collected; use the rights in section 13 for that.

18. Public information and user-generated content

18.1 Golden tips and other contributions you publish can be visible to every FanPlan user, and may be shown with the display name you chose.

18.2 If you enable a public passport, its URL is accessible to anyone who has it, and search engines may index it. You can switch it off at any time.

18.3 Content shared on social networks from the app (for example a story card or match share) is posted under the terms of the network you choose.

18.4 We may remove public content that breaks our Terms of Use. You can report content using Contact us.

19. Groups, organisations and staff tools

19.1 Groups lets an organisation publish a base plan, for example a supporters' coach trip, that invited fans open in the consumer app. The organisation decides which fans to invite and what the plan contains, and is responsible for having a lawful reason to invite you.

19.2 For the invitation and the base plan we act as a processor on behalf of the organisation in some respects, and as a controller of your FanPlan account. Your personal additions to a trip are yours: the organisation cannot read your private notes.

19.3 Organisation managers access the Groups portal with Google single sign-on. We process their name, email and portal activity to run the product and secure it.

19.4 If you leave a Group or decline an invitation, the organisation stops receiving updates about you from FanPlan. Data the organisation already holds under its own relationship with you stays with the organisation, and you must contact it directly about that.

19.5 Our Admin CMS and Content Studio are used by authorised staff to manage fixtures, clubs, copy and support requests, and can display the same account data described in section 5. Those tools are protected by individual logins, and activity is logged.

20. Personal data breaches

20.1 We maintain an incident process that covers detection, containment, assessment, notification to authorities and affected users where required, and post-incident review.

20.2 If you notice anything suspicious, such as an email you did not request or a login you do not recognise, write to [email protected] with the subject "Security".

21. Changes to this policy

21.1 We may update this policy as FanPlan evolves, for example when we add a feature, change a provider or the law changes. The "Last updated" date at the top shows the current version.

21.2 For material changes we will tell you in the app or by email where we have a working address, and where the law requires it we will ask for your consent again.

21.3 Earlier versions are available on request.

22. Language

22.1 This policy is written in English. We may offer translations for convenience. If a translation differs from the English text, the English text prevails unless the law of your country of residence says otherwise.

23. Contact us

23.1 Email: [email protected]

23.2 In the app: Personal area, then Contact us, and choose the category that fits (for personal data choose "Data request").

23.3 Post: FAN PLAN S.R.L., Via Giuseppe Frua 11, 20146 Milano (MI), Italy (registered office named in section 3.1).