Effective: . Last updated: .
Scope and Definitions
1.1 This Privacy Policy describes how we collect, use, disclose and hold Personal Information in connection with the Service.
1.2 This Privacy Policy applies to Personal Information about any person, whether or not that person has an Account.
1.3 "Personal Information" means information that identifies or relates to an identified or identifiable person.
1.4 We "hold" Personal Information when we store it.
1.5 Each capitalized term that this Privacy Policy does not define has the meaning given to it in the Terms of Service. The same applies to the words "we", "us", "our", "you" and "your".
1.6 Each name of a document of the Service in this Privacy Policy refers to the document of that name published through the Service.
1.7 "Report" has the meaning given in Safety and Reporting.
1.8 "Moderation Action", "Child Sexual Abuse Material", "Scam" and "Game Chat" have the meanings given in the Community Guidelines. "Intimate Image" and "Removal Request" have the meanings given in Take It Down. "Request for Review" has the meaning given in Appeals.
1.9 "Website" and "Apps" have the meanings given in the Terms of Service.
1.10 "Parent" means the parent of a person under 13 who gives, or is asked to give, the consent described in clause 8.3.
1.11 The company that operates the Service, to which "we" refers, is identified below.
Fanalytics LLC
Information We Hold
2.1 Table 1 states the Personal Information that we hold, where we hold it, who has access to it and the reason for holding it.
| Record | Location | Access | Retention | Deletion | Purpose |
|---|---|---|---|---|---|
| Sign-in Email address; a password stored in hashed form, or the details shared by your Google account if you sign in with Google | Our sign-in service (Supabase) | You; Supabase, as our service provider; our server code | Until the Account is deleted | Deletion of the Account removes the sign-in record | To enable you to sign in and to send you sign-in emails |
| Public profile Display name, username, picture, biography, country, favorite sports and team, verified mark and date of joining | Our database (Supabase) | Any person, whether or not signed in; a signed-in person also sees score and tier | Until the Account is deleted | Deleted with the Account | To enable other persons to see who you are on the Service |
| Private profile settings Choice about read receipts, choice about who may add you to Circles and date of the last change of username | Our database (Supabase) | You and our server code only | Until the Account is deleted | Deleted with the Account | To apply your choices about read receipts and about who may add you to Circles |
| Moderation status Whether the Account is suspended or banned, until when, and the rule that was applied | Our database (Supabase) | Our server code, our administrators and you | Until the Account is deleted | Deleted with the Account | To apply a suspension or ban and to inform you of the reason |
| Posts and replies Text, pictures and video that you post | Our database and file storage (Supabase) | Any person, unless hidden by a Moderation Action | Until you delete them or the Account is deleted | You may delete a post; deletion of the Account removes all posts; replies to a deleted post are deleted with it | To enable you to share Content and other persons to read it |
| Group messages and direct chats Messages, reactions, read receipts and media | Our database and private file storage (Supabase) | Members of that Circle or direct chat | Until you delete them or the Account is deleted | Deletion of the Account; an owned Circle passes to its longest-standing member; in a direct chat the other person keeps their half | To enable you to communicate with the persons whom you choose |
| Follows, blocks, favorites Accounts that you follow, Accounts that you have blocked, and favorite teams and players | Our database (Supabase) | You, as to blocks; follows are visible to the persons involved | Until the Account is deleted | Deleted with the Account | To operate your feed, your blocks and your favorite teams |
| Saved posts The posts that you saved and the time of each save | Our database (Supabase) | You and our server code only | Until you remove the save, or the post or the Account is deleted | You remove a save, the post is deleted or the Account is deleted | To provide you with a private list of posts to read again |
| Activity and picks Badges, levels, challenges and predictions | Our database (Supabase) | You; displayed where the Service displays scores | Until the Account is deleted | Deleted with the Account | To keep and display your badges, levels and picks |
| Notifications Notices addressed to you and a push registration consisting of the platform and a device token | Our database (Supabase) | You | Until the Account is deleted | Deleted with the Account | To inform you of events in the Apps and to deliver push notifications to your phone |
| Photos Profile pictures, Circle pictures and post media | Our file storage (Supabase). Profile, Circle and post pictures are public; chat media is private | Public storage: any person with the link; private storage: members of the Circle | Until deleted | Deletion of the Account removes your files | To display the pictures that you add where you place them |
| Reports and moderator actions Reports that you make or that are made about you, actions taken, and a copy of the text and picture file names that were reported | Our database (Supabase) | Our administrators only | 1 year after the Report is closed, then deleted | As stated under What Stays When You Delete Your Account: kept for 1 year with identifiers blanked | To examine what was reported, to take action and to show what we did if a review is requested |
| Moderation notices A notice in the Apps that a Report that you made was reviewed, or that we took action on your Content or Account | Our database (Supabase) | You | Until you delete them or the Account is deleted | Deleted with the Account | To inform you that a Report was reviewed or that we acted on your Content |
| Moderation email queue The type of email, the Report or action to which it relates and the Account to which it is addressed, without reported Content | Our database (Supabase) | Our server code | 30 days after the email is sent | Deleted by a daily process | To ensure that each safety email is sent once and can be checked |
| Search and usage Search terms, features used, page views and sessions; a page view also records the page that referred you, when there is one | Our database (Supabase) | Our administrators only | 12 months | Your user identifier is blanked when you delete your Account; the rows then count only in totals | To determine which features are used and to keep them working |
| Error and speed logs Error text, stack traces and the duration of requests | Our database (Supabase) | Our administrators only | 30 days | Your user identifier is blanked when the Account is deleted | To find and correct errors and slow requests |
| Admin action log The action taken by an administrator and the Account affected | Our database (Supabase) | Our administrators only | 12 months | Identifiers blanked, as stated under What Stays When You Delete Your Account | To determine who changed what when a fault occurs |
| Our own data-feed log Our requests to the sports data provider | Our database (Supabase) | Our administrators only | 30 days | Contains no Personal Information about holders of Accounts | To keep our requests within the limits of the sports data provider |
| Rate-limit counters A count for each hashed address and route | Our database (Supabase) | Our server only | 7 days | Expires after 7 days; may contain your user identifier during that period | To prevent one address from flooding the Service |
| Feedback Sentiment, message and, optionally, name and email address | Our database (Supabase); a copy is emailed to us | Our administrators only | 12 months | Feedback sent while signed in is deleted with the Account | To read what you send to us and to reply |
| Sign-in records The time, the device and the address of each sign-in | Our sign-in service (Supabase) | Supabase and our server code | Held by Supabase while the session lasts; removed with the Account | We cannot change what Supabase stores here | To keep you signed in and to protect your Account |
| Age An indicator of under 13 or over 13; for an Account of a person under 13 only, the birth month and year until the person is 13 | Our database (Supabase) | Our server code and you | Indicator: until the Account is deleted; birth month and year: until the Account turns 13, then deleted | Indicator with the Account; birth month and year dropped at 13 | To apply the additional protections for persons under 13 and to end them at 13 |
| Parent consent record The email address of the Parent, the time of confirmation and the method | Our database (Supabase) | Our server code and our administrators | Until the child is 13, or until the Account of the child is deleted or the Parent deletes the record, whichever is first | By the daily process when the child is 13, with the Account of the child, or on request of the Parent | To show that a Parent gave consent and to enable the Parent to act for the child |
| Approved people The Accounts that a Parent approved to share a Circle with the child | Our database (Supabase) | The Parent and our server code | Until the child is 13, or until the Account of the child is deleted or the Parent removes the person, whichever is first | By the daily process when the child is 13, with the Account, or on removal | To ensure that only persons whom a Parent approved can share a private Circle with the child |
2.2 We receive Personal Information from you, from your use of the Service and, if you sign in with Google, from your Google account.
2.3 We also receive Personal Information about you from a person who sends you a Message or makes a Report about you, and from a Parent.
2.4 Each record named in this Privacy Policy is the record so named in Table 1 or Table 2.
2.5 The Service does not request your location, the contact list of your device, an advertising identifier or payment information.
2.6 We do not combine information about your use of the Service with information about your use of the applications or websites of other companies.
Use of Personal Information
3.1 We use Personal Information to provide and operate the Service, including sign-in, the display of User Content and the delivery of notifications and emails, and to answer the questions and requests that you send to us.
3.2 We use Personal Information to maintain the security of the Service, to prevent abuse, to review Reports, to take Moderation Actions and to make the disclosures described in clauses 6.3 and 6.8.
3.3 We use search and usage records and error and speed logs to measure the use of features and to find and correct errors and slow requests.
3.4 We use a birth month and year to determine whether an Account belongs to a person under 13. We use the consent record of a Parent to confirm that the Parent has given consent.
Retention
4.1 Table 2 states, for each record that has a period, the period and the event from which it is counted.
| Record | Period | Counted From |
|---|---|---|
| Error logs (error text, stack trace, address code) | 30 days | The time of logging |
| Speed logs | 30 days | The time of logging |
| Our own calls to the sports data provider | 30 days | The time of logging |
| Data-sync job log | 30 days | The time at which the job started |
| Rate-limit counters | 7 days | The start of the counting period |
| Page views | 12 months | The time of viewing |
| Visit sessions | 12 months | The time of the last activity |
| Searches | 12 months | The time of the search |
| Feature-use events | 12 months | The time of use |
| Admin action log | 12 months | The time of the action |
| Feedback you send us | 12 months | The time of sending |
| Reports and moderator actions | 1 year | The time at which the Report is closed, or the date of the Report if it is never closed |
| The daily process's own run record, counts only | 12 months | The time of the run |
| Birth month and year of an Account of a person under 13 | Until the Account turns 13 | The birth month and year |
| Age indicator, parent consent record and approved people | Age indicator: until the Account is deleted. Parent consent record and approved people: until the child is 13 (deleted by the daily process), or until the Account is deleted or the Parent deletes them, whichever is first | The time of creation |
| Unconfirmed parent code | 24 hours; the code ceases to work then, and the stored record is deleted by the daily process 7 to 8 days later | The time of sending |
| Copy of the reported Content, being the text and picture file names | 1 year | The time at which the Report is closed, or the date of the Report if it is never closed |
| Moderation email queue | 30 days | The time at which the email is sent |
| Posts, replies, Messages and photos | Until you delete them or the Account is deleted | Not timed |
| Saved posts | Until you remove the save, or the post or the Account is deleted | Not timed |
| Sign-in records held by our provider (Supabase) | While the session lasts; removed with the Account | Not set by us |
4.2 We delete each record listed in Table 2 by a daily process once its period has ended.
4.3 User Content remains until you delete it or delete your Account, except as stated in clauses 8.7, 11.2, 11.9 and 11.11. Hiding User Content under the Community Guidelines or Take It Down does not delete it.
4.4 We may place a retention hold, which is a mark in our records, on a Report. Clause 4.2 does not delete a Report that is open or on retention hold, and no end date is set for a Report on retention hold.
4.5 We may hold a Report or other record that we disclose under clause 6.3 for longer than 1 year after the Report closes.
IP Addresses
5.1 "IP address" means the numerical internet address from which your device connects to the Service.
5.2 "Page view" means a request for a page of the Website, and "visit session" means the page views that share one IP address, one browser and one date.
5.3 In our records of errors, slow requests, actions by a person acting for us, page views and rate-limit counts, we hold an address code in place of your IP address.
5.4 The address code is derived from your IP address, the date, a secret key that we hold and, for a visit session, the user agent string of your browser.
5.5 The same IP address produces a different address code on each date. An address code cannot be converted into an IP address.
5.6 We hold the secret key. We use the secret key only to determine whether a given IP address corresponds to an address code, in order to investigate abuse of the Service or a security incident, and we do not use it in the ordinary operation of the Service.
Disclosure of Personal Information
6.1 We will not sell Personal Information and we will not display advertising through the Service.
6.2 Your profile, posts and replies are visible to any person who uses the Service, whether or not that person is signed in, unless the post or reply is hidden under the Community Guidelines or Take It Down, or is hidden from a person by a block under Safety and Reporting.
6.3 We will report apparent Child Sexual Abuse Material of which we become aware to the child-safety tip line of the National Center for Missing and Exploited Children, together with any Report about it and the information that we hold about the Account that submitted it.
6.4 Table 3 identifies each company that processes Personal Information on our behalf, the information that it receives, its location and the terms under which it works. We and the companies in Table 3 hold and process Personal Information in the United States and in the other locations stated in Table 3.
| Company | Function | Information Received | Location | Retention | Terms on File |
|---|---|---|---|---|---|
| Supabase | Operates our database, sign-in and file storage | All information in your Account: email address, profile, posts, Messages, files and sign-in records | United States (US East, Ohio) | While the Account exists, and deleted with it; daily backups for 7 days; its own request logs for 7 days | Its Data Processing Addendum forms part of its Terms of Service and incorporates standard contractual clauses. |
| Vercel | Hosts the Website and our server code | Each request to the Website, including the address from which it came | United States and a global network | Short-lived request logs, as set by our Vercel plan | We have not checked which terms apply to our plan. |
| Expo, Apple and Google | Deliver push notifications to your phone | The push address of your device, the text of the notice and the name of the sender; the Apps also request app updates from Expo, which shows Expo the address of the device | United States | Expo: notice content is held in memory and queues and is not stored in databases; Apple: an undeliverable notice for up to 30 days; Google: up to 4 weeks | Expo states that it acts for us as a processor. Apple and Google deliver notices under their own terms. |
| Google (sign-in) | Enables you to sign in to the Website with your Google account when you select Continue with Google | The sign-in details that your Google account shares with us, such as your name and email address | Not stated by us | Not stated by us | We have not checked its terms. |
| API-Sports | Supplies scores and fixtures to us; its servers also supply team pictures on the club-soccer pages of the Website | Our requests for match data, and your address when your browser loads a team picture | Not stated by the vendor | Not stated by the vendor; its policy states that it logs addresses for abuse and statistics | We know of no agreement between us and API-Sports. |
| Google Fonts | Supplies the two typefaces that the Website uses | Your address when your browser loads the typefaces | Not stated by us | Not stated by us | We have not checked its terms. |
6.5 In clause 6.6, "address" means IP address and "our website" means the Website. Each company named in clause 6.6 is identified in Table 3.
6.6 Besides Vercel and Supabase, who run our website, Google Fonts and API-Sports also see the address of a visitor.
6.7 We may disclose Personal Information to the extent that we are compelled to do so by law or legal process.
6.8 We may report a Scam, a credible threat of violence or an Intimate Image that is submitted through the Service to law enforcement, together with any Report about it and the information that we hold about the Account that submitted it.
Information on Your Device
7.1 The Website does not set cookies.
7.2 The Website stores in the local storage of your browser your sign-in session, your theme and settings and, if you are signed out, your favorites.
7.3 The Website stores in the session storage of your browser short-lived copies of pages and content, unsent post drafts and whether you dismissed the install prompt.
7.4 The session storage of your browser also holds an identifier that we generate for each browser tab and date. We use it to count the use of each feature.
7.5 A service worker of the Website stores copies of the pages and files of the Website in the cache of your browser.
7.6 The Apps store on your device your sign-in session, your reminders, your muted accounts and whether the Apps have asked about notifications.
7.7 The Apps also request updates of the Apps from Expo, which is identified in Table 3.
7.8 The Website and the Apps do not contain advertising software, analytics software or crash-reporting software supplied by another company.
7.9 An App may send a report of an error to us. The report contains the text of the error and the first lines of its stack trace. The report also states the version of the App, the platform, the operating system version and the screen on which the error occurred.
7.10 We remove known patterns of Personal Information from the text of the error. The text may contain Personal Information that we do not remove.
Children
8.1 When you create an Account, we ask for your birth month and year.
8.2 If you are 13 or older, we hold only a record of that fact and not your birth month or year.
8.3 If you are under 13, you may not post or reply in Fandom. If you are under 13, a Parent must give consent to your use of a Circle before you may use it.
8.4 If you are under 13, we hold your birth month and year until the end of the month in which you reach 13 years of age, and then we delete them.
8.5 If you are under 13, we hold the record of the consent of your Parent until the same date, and then we delete it.
8.6 We also hold the list of persons whom your Parent has approved to share a Circle with you until that date, and then we delete it.
8.7 If you are under 13, your Parent may enable Circles for you, approve persons for them and delete your Account, and the information in it, on the parent page of the Website.
8.8 Your Parent may do so at any time until the records in clauses 8.5 and 8.6 are deleted, and those parental controls then end.
8.9 Except where a clause states otherwise, this Privacy Policy applies to the Personal Information of a person under 13.
8.10 Clauses 11.2 to 11.11 apply to a deletion made by a Parent under clause 8.7 as they apply to a deletion made by you.
Reports and Messages
9.1 "Message" has the meaning given in the Terms of Service.
9.2 Except as stated in clauses 9.3 and 9.4, a Message other than a message in a Game Chat is visible in the Service only to the persons in the conversation or the Circle in which it was sent. A message in a Game Chat is visible to any person who opens the game, whether or not that person is signed in, unless the message is hidden on a ground stated in clause 6.2.
9.3 We read the content of a Message only to review a Report, a Request for Review, an Infringement Notice or a Removal Request that concerns it.
9.4 When a Report is made, we save a copy of the whole reported User Content, including a Message in full, for the review of the Report.
9.5 The process for reviewing Reports is stated in Safety and Reporting and in the Community Guidelines.
Deletion and Download
10.1 You may delete your Account and download a copy of your Personal Information in the Settings of the Apps.
10.2 The Apps offer deletion and download only for an Account that uses an email address and password.
10.3 If your Account uses Google sign-in, if you cannot sign in or if you do not use the Apps, you may request deletion or download by writing to privacy@fanalyticshq.com.
10.4 A deletion made in the Apps takes effect immediately and is permanent, except as stated in clauses 11.2 to 11.11. A deletion that you request under clause 10.3 takes effect when we complete it.
10.5 Deletion of an Account removes your profile, posts, replies, messages, including messages in a Game Chat, files, follows, blocks, favorites, saved posts, notifications, push registrations, activity, FanPicks predictions, feedback sent while signed in, age information, Parent consent record, approved people and sign-in records.
What Stays When You Delete Your Account
11.1 Clauses 11.2 to 11.11 describe the Personal Information that remains after you delete your Account and the period for which it remains. Where a clause states no period, no end date is set.
11.2 Except as stated in clauses 4.4 and 4.5, a Report and the saved copy of the reported User Content remain for 1 year after the Report closes. They remain if the Account of the person who made the Report, or of the author of the User Content, is deleted. The saved copy may include Personal Information of the author of the User Content.
11.3 The user identifier on a Report and on a Moderation Action is removed when the Account concerned is deleted, except in the records described in clauses 11.6 and 11.8.
11.4 Search and usage records and error and speed logs remain until the end of the period stated for each in Table 2, and they no longer carry your user identifier.
11.5 Rate-limit counters remain until the end of the period stated in Table 2 and may contain your user identifier during that period.
11.6 Entries in the admin action log remain until the end of the period stated in Table 2. An entry may show the identifier of an Account that no longer exists.
11.7 Feedback that you send is also emailed to us, and we hold the email copy. No period is set for the email copy.
11.8 The account action record lists the actions of a person acting for us and the Moderation Actions taken on an Account. It may hold the identifier of the Account and, for an Account that a person acting for us deleted, its email address. No period is set for that record.
11.9 Backups held by Supabase may contain a copy of your Personal Information for up to 7 days.
11.10 Aggregate totals that cannot identify any person are not Personal Information and are not deleted.
11.11 Copies that other persons have made of your posts and replies by sharing or quoting them are outside our control and remain.
Changes to This Privacy Policy
12.1 We may revise this Privacy Policy at any time. A revised version takes effect on the effective date that it states.
12.2 We will announce a material change on the Service for 30 days from the date on which it takes effect.
Questions About This Privacy Policy
13.1 You may send a question about this Privacy Policy to privacy@fanalyticshq.com.
13.2 Other ways to contact the operator are described in Contact.