Privacy Policy

1. Introduction

Sportiverse ("we", "our", "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application.

2. Information We Collect

Personal Information You Provide

• Account Information: Email, password, first name, last name
• Profile Information: Date of birth, nationality, profile picture, bio
• Sports Data: Club memberships, match statistics, training schedules
• User Content: Comments, match results, team rosters

Information Collected Automatically

• Device Information: Device type, operating system, unique device identifiers
• Advertising Identifiers: Apple IDFA (iOS) and Google Advertising ID (Android), used by our advertising partner to serve and measure ads. Collection of IDFA on iOS requires your explicit permission via the App Tracking Transparency prompt.
• Usage Data: App features used, time spent, interaction patterns
• Performance Data: Crash reports, performance metrics

Analytics Data (With Consent)

If you consent to analytics, we collect:

• App usage patterns and feature engagement
• User journey and navigation flows
• Performance and stability metrics

3. How We Use Your Information

4. Data Sharing and Disclosure

We Share Data With:

• Other Users: Profile information, match results, and statistics as part of the service
• Club/League Members: Information relevant to your sports activities
• Service Providers: Firebase (Google) for infrastructure and authentication; Sentry for crash and error reports; Shake for in-app bug reports you choose to send; Algolia for search (names of users, clubs and leagues, so they can be found by search)
• Advertising Partners: Google AdMob for displaying ads. See the "Advertising" section below for details.

We Do NOT:

• Sell your personal information
• Use your data for email or push marketing without consent

4a. Advertising

Sportiverse displays ads to support the free service. We use Google AdMob (operated by Google LLC) as our sole advertising partner.

What AdMob Collects

• Apple IDFA (iOS) or Google Advertising ID (Android)
• Approximate (non-precise) location derived from IP address
• Device information (model, OS, language)
• Interactions with ads (views, clicks)

Personalized vs Non-Personalized Ads

If you are located in the European Economic Area, United Kingdom, or Switzerland, we show a consent form on first launch asking whether you allow personalized ads. You can change this choice at any time in Settings → Account Center.

• With consent: AdMob may use your advertising identifier to show ads tailored to your interests.
• Without consent: Only non-personalized ads are shown, based on contextual signals rather than your profile.

iOS App Tracking Transparency

On iOS 14.5 and later, Apple requires an additional permission prompt before any tracking across apps. If you decline the prompt, no IDFA is shared with AdMob and you will only see non-personalized ads.

Learn More

For details on how Google handles data collected from partner sites and apps, see Google's Partner Data Policy. To opt out of personalized ads across Google services, visit Google Ad Settings.

4b. Administrative Audit Logs

When an action that affects who can govern a club is taken — an admin adding, promoting, demoting, or removing a member, a member (including an admin) leaving a club they belong to, an admin editing club settings or rotating the invite code, the club's creator or an admin generating the invite code, an admin deleting the club, or a user claiming a placeholder club or merging one into their own club — we write a short record to an internal audit log. This section explains what is captured, why, and how long it is kept.

What we log

For member-level actions (a member added, promoted, demoted, removed, or leaving):

• The user ID (UID) of the acting user — the admin who took the action, or the member themselves if they left
• The UID of the affected user (which may be the same person as the acting user, e.g. when a member leaves)
• The display names of the acting user and the affected user, as shown at the time of the action
• The action type — one of member-added, admin-promoted, admin-demoted, member-removed, member-left
• The club ID and a timestamp

For club-level actions (settings changes, invite-code generation or rotation, club deletion):

• The UID of the acting admin (or, for invite-code generation, the club's creator)
• The acting admin's display name (captured at the time of the action) — only for club deletion; club-settings edits and invite-code generation or rotation record only the UID
• The action type — one of club-updated, club-invite-code-issued, club-invite-code-rotated, club-deleted
• For club-updated, the names of the fields that changed (e.g. "name", "description", "colors") — never the field values themselves
• The club ID and a timestamp

When a user claims a placeholder club (takes over a club that was created on their behalf to schedule matches before they joined), we record the action type club-claimed, the claiming user's UID and display name, the UID of the user who created the placeholder, the UIDs of any members removed by the claim, the club ID and a timestamp.

When a user merges a placeholder club into their own club, we record the action type club-merged, the merging user's UID, the UID of the user who created the placeholder, the ID of the club it was merged into, the number of leagues and matches moved, the club ID and a timestamp. No display names are recorded.

We do not capture email addresses, profile content, free-form notes, the actual contents of changed club settings, or any other personal data in audit logs. Where display names are captured, they are captured only as they were at the time of the action, so the entry remains readable for dispute resolution if a participant later changes their name, or if the other party deletes their account. Your own display name is anonymized in these entries when you delete your account (see "Account deletion and this log" below). While your account remains active, the audit-log viewer displays your current display name from your live profile — the captured name is shown only as a fallback after the original user record is no longer available.

Why we log this

The audit log exists purely to allow us to investigate disputes — for example, if a user reports they were kicked or demoted unfairly, or if we need to investigate coordinated abuse of admin powers. It is not a user-facing feature and is not used for profiling, analytics, advertising, or product development.

Retention and automatic deletion

Each audit-log entry is automatically deleted 90 days after the action it records, enforced by a Firestore time-to-live policy. We cannot extend this window for individual entries.

Legal basis

The processing relies on GDPR Article 6(1)(f) — legitimate interests pursued by Sportiverse (fraud prevention, dispute resolution, and platform integrity). We have balanced this against your rights and freedoms:

• Necessity: the captured display names are needed so that an entry stays readable for the remaining party in a dispute after the other party has deleted their account; without them, the most relevant rows would render as "unknown user." The deleting user's own name is anonymized at deletion.
• Data minimization: the log is limited to UIDs, action metadata, and (where applicable) the display names of the acting user and the affected user. No emails, profile content, free-form notes, or club-settings values are captured. Club-settings edits record only the names of fields that changed, not their contents.
• Live-name preference: while a user's account exists, the audit-log viewer shows that user's current display name from their live profile. The captured name is read only as a fallback when the original user record is no longer available.
• Short retention: 90 days from the action, enforced by a Firestore time-to-live policy.
• No secondary use: the data is not shared with third parties and is not combined with your profile for any other purpose (no profiling, analytics, advertising, or product development).

Your access to entries about you

Audit-log entries that record you as the acting user or as the member an action was taken on are included in your data export (see section 6). Each exported entry shows the club, the action, whether you were the one acting or the one affected, when it happened, and who performed it — you, a club administrator, or another user. The identities of other members — their names and user IDs — are withheld from exported entries, and where an action displaced several members, only the number of members is shown. If you were the creator of a placeholder club, or a member removed when it was claimed, the club-claimed or club-merged entry for it is not part of your export; you can request it from privacy@sportiverse.no. To contest an action in which the other party's identity is withheld, email privacy@sportiverse.no within the 90-day retention window; we will review the entry and resolve the dispute with you.

Account deletion and this log

If you exercise your right to erasure (delete your account), we remove your personal data from our systems as described in sections 6, 7 and 7a. Your display name is anonymized in existing audit-log entries at deletion; your UID remains in those entries until each is auto-deleted at the end of its 90-day window. In rare cases, a narrow processing window during deletion may leave residual entries that still carry your display name; these are auto-deleted at the end of their own 90-day windows. We cannot remove individual entries on request.

Right to object

You can object to this processing by emailing privacy@sportiverse.no and citing the specific audit-log entries or timeframe. Because this processing serves fraud-prevention and dispute-resolution interests that may override an individual objection, we cannot guarantee immediate deletion within the 90-day window; we will, however, review each request on its merits. Regardless of the outcome, every entry is auto-deleted once its 90 days elapse.

5. Data Storage and Security

Storage Location

Your data is stored on Google Firebase servers, primarily located in:

• Europe (for EU users)
• United States (for non-EU users)

Security Measures

• Encryption in transit (HTTPS/TLS)
• Encryption at rest for sensitive data
• Secure authentication via Firebase Auth
• Regular security audits and updates
• Access controls and monitoring

7. Data Retention

We retain your data for different periods based on the type:

• Account Data: Until account deletion + 30-day recovery period
• Match Statistics: Indefinitely for historical records. At account deletion your account is removed from match lineups and your portrait is deleted; your player name stays in the match history, and match events and feed events may still carry your account identifier, which no longer leads to a profile (see section 7a)
• Analytics Data: 2 years
• Logs and Security Data: 90 days
• Administrative Audit Logs: UID, action metadata, and the display names of the people directly involved (captured at the time of each action) — 90 days from the action, auto-deleted by Firestore TTL. Retained through account deletion until each entry's window elapses; your display name is anonymized in them at deletion (see section 4b).
• Notifications: 30 days from delivery, auto-deleted by Firestore TTL. The expiry date is set by our servers and cannot be extended from the app.
• Personal Feed Items: the copies of activity delivered to your personal feed — 30 days from delivery, auto-deleted by Firestore TTL.
• Live Activity Update Tokens: up to 13 hours from the last update, auto-deleted by Firestore TTL.

Automatic deletion runs on a schedule, so a record may remain for a short time — usually less than a day — after its deletion date. Deleted data may also persist for a limited additional period in backups that are not accessible to users.

7a. What Stays Visible to Others After You Delete Your Account

Deleting your account removes your profile and personal data. Some things you shared with other people are part of their clubs, matches and conversations, and stay visible to them without your profile attached, although your account identifier may remain on that content. This list gives the main examples; it is not exhaustive.

• Club board posts and comments you wrote, including attached photos and files, stay on the board for that club's members, shown as "Deleted user". While you are still a member you can delete them yourself; after your account is deleted, only a club admin can remove them.
• Comments on feed events stay, with your name replaced by "Deleted User".
• Your name in match history — match lineups and feed events about matches you played in keep the player name, so results and match events stay intact. Your account is removed from match lineups and your portrait is deleted; match events and feed events may still carry your account identifier, which no longer leads to a profile.
• Training attendance — your attendance at club training sessions that have already taken place stays in the club's records with your name and answer, without your profile or portrait attached. Invitations to sessions that have not yet taken place are removed.
• Direct messages you sent stay in the recipients' conversations, with the link to your account removed.
• Notifications other members already received about you — for example a fan or membership request, or a new club board post — may still show your name, account identifier, a link to your profile photo (which stops loading once your account is deleted) or a short preview of your post. We do not separately search every other member's notifications at deletion, because each copy is automatically deleted within 30 days of delivery (section 7).
• Administrative audit logs, as described in section 4b.

If you want something specific removed, email privacy@sportiverse.no.

8. Children's Privacy

Sportiverse requires users to be at least 13 years old. Users under 18 require parental consent. We do not knowingly collect data from children under 13.

9. International Data Transfers

If you're in the EU and your data is transferred outside the EU, we ensure appropriate safeguards through:

• Standard Contractual Clauses
• Adequacy decisions
• Privacy Shield frameworks (where applicable)

10. Cookies and Tracking

The Sportiverse mobile app does not use cookies. We may use:

• Local storage for app preferences
• Analytics SDKs (only with your consent)
• Firebase Performance Monitoring (anonymized)
• Mobile advertising identifiers (IDFA / Google Advertising ID) via Google AdMob — see section 4a

11. Changes to This Policy

We will notify you of significant changes via:

• In-app notifications
• Email to your registered address
• Prominent notice in the app