1. Scope and data controller
This policy applies to the MatchDay mobile applications for Android and iOS and to this website. MatchDay is operated by Cryoss, an independent software developer. For privacy questions or requests, contact cryossdev@gmail.com.
2. Data we process
| Category | Examples | How it is obtained |
|---|---|---|
| Account and profile | Email address, display name, optional phone number and profile image, skill level, preferred position, account identifiers, creation date, minimum-age confirmation, and the versions and time of legal documents accepted at registration. | From you, Google Sign-In, or Firebase Authentication. |
| Match and participation | Matches created or joined, pitch and coordinates selected for a match, date, time, capacity, format, cost entered by the organizer, attendance, waitlists, teams, scores and payment-status markers. | From you, match organizers and other authorized match managers. |
| Social and communications | Friend requests, invitations, direct and match-chat messages, read status, reports, blocks and moderation records. | From you and other users you interact with. |
| Device and notification | Firebase installation and push-notification tokens, notification preferences, locale, app/platform version and App Check attestation signals. | From your device and Firebase services. |
| Location and map queries | Precise or approximate device location when you actively use nearby-match or map-location controls; selected match coordinates; map tile and weather requests associated with a location. | From your device with permission, or from a location you select manually. |
| Analytics and diagnostics | Feature events, app instance information, crash reports, diagnostics and a Firebase user identifier. | Only when you enable analytics; Crashlytics is disabled with that choice and is not collected in debug builds. |
| Advertising and consent | Consent choices, advertising identifiers and ad interaction/device signals as determined by Google Mobile Ads. | Through Google’s User Messaging Platform and Mobile Ads SDK, subject to consent and platform settings. |
| Support | Email address, message contents, diagnostic details you choose to send and request history. | When you contact support. |
Please do not place sensitive personal information in match titles, locations, notes or chats. Public-match information and public-profile fields can be visible to other MatchDay users.
Optional match features and visibility
- Player availability and SOS: choosing to be available records a selected area, coarse search region, positions, travel radius and availability period. Authorized match organizers can receive a limited discovery summary while the availability is active. Discovery does not reveal the player's precise coordinates. Receiving SOS notifications requires a separate opt-in; being available alone does not subscribe an existing account to SOS pushes.
- Match voting: participation determines voting eligibility. A player's ballot is private and can be changed while the voting window is open. Other players and the general administrator dashboard do not receive individual ballots. Final award summaries and award counts can appear with the match or player profile. Finalization records help prevent duplicate awards.
- Notifications: in-app inbox entries and delivery jobs use event type, match reference, recipient and delivery-state metadata to support retries. Delivery records may include token hashes. These workflow records do not include message text or precise locations. Notification categories have separate preferences; a provider accepting a push does not mean it reached a device.
- Shared-match preview: an organizer's separate preview choice can make a match's title, time, duration, format, city/country, capacity summary and fee visible before sign-in when the player web release is enabled. It does not expose the precise address, coordinates, roster, organizer identity, notes or chat. A match being public to signed-in players does not automatically enable its anonymous preview. Preview abuse controls use a rotating pseudonymous network key; hosting and security providers may still process ordinary network metadata.
- Scoped moderation: separately authorized moderators can access limited information for a selected safety case and record a decision. This is separate from aggregate administrative analytics. Case access and decisions are audited; report content is not made available through general user or match lists.
3. Purposes and legal bases
- Provide the service and perform our agreement: authenticate accounts, show matches, manage participants, deliver invitations and messages, and support account deletion.
- Your consent: access device location, write a match to your calendar, send notifications where platform permission is required, enable optional analytics/crash reporting, and serve consent-dependent advertising.
- Legitimate interests: secure the service, prevent abuse, apply rate limits, investigate reports, maintain reliability, defend legal claims and understand failures where permitted.
- Legal obligations: respond to lawful requests and keep records required by applicable law.
You may withdraw optional permissions and analytics consent at any time. Withdrawal does not affect processing already lawfully completed.
5. Location, notifications and calendar
- Location: requested contextually for nearby results and map controls. You can select a pitch manually instead. Match coordinates chosen by organizers are stored as part of the match.
- Notifications: used for invitations, match updates, chat and relevant reminders. They can be disabled in system settings.
- Calendar: accessed only when you choose to add a match. MatchDay does not upload your calendar contents to its backend.
- Local storage: the app stores essential preferences such as language, theme, analytics choice and limited setup state on the device. If a submitted match has no confirmed result yet, its form and selected venue stay on that device under the submitting account, including after sign-out. The app clears this copy when the result is acknowledged, the submission is rejected, or you delete the account on that installation.
6. Retention and deletion
We retain account and service data while your account is active and as needed to provide MatchDay. When you delete your account, the backend removes the authentication account, private profile, public profile, participation, waitlist and invitation records, friendships, access grants, direct chats and reports you submitted. Created upcoming matches are cancelled and detached from your identity. Match-chat messages are replaced with a deleted-user marker and their text is removed.
Some limited records may be retained for fraud prevention, security, legal compliance, dispute resolution or backup-recovery cycles where permitted. Provider logs and advertising/consent records follow the applicable provider’s retention rules. Support correspondence is normally retained for up to 24 months after the request is resolved unless a longer period is needed for a legal or security reason.
See the dedicated account deletion instructions.
Optional workflow expiry and deletion
Availability stops being eligible for discovery at its configured expiry, independently of later database cleanup. Private ballots, inbox entries, notification jobs and delivery records have bounded cleanup workflows; physical deletion may occur after logical expiry. Final award and replay-protection records are retained with their related workflow to avoid duplicate results. Account and match deletion workflows also remove or anonymize related availability, voting, inbox and delivery records as applicable. Moderation audit records are kept separately for restricted operational review. These descriptions do not promise immediate deletion or announce that production cleanup has been verified.
7. Your privacy rights
Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy of data, withdraw consent, and complain to a supervisory authority. You can edit core profile details in the app and delete the account from Profile → Privacy & Safety → Delete account.
For another request, email cryossdev@gmail.com from the address associated with your account. We may request limited verification and will never ask for your password.
Advertising and analytics choices
Analytics can be enabled or disabled in the app’s Privacy & Safety screen. Where required, “Privacy choices” reopens Google’s consent controls. Platform-level advertising privacy controls may also be available in Android or iOS settings.
8. Security
MatchDay uses encrypted network connections, Firebase Authentication, App Check providers, server-authoritative sensitive actions, access-controlled database rules, rate limiting, audit records and restricted production configurations. No service is completely secure; please use a protected device, keep your account credentials private and report suspected misuse promptly.
9. Children and young users
MatchDay is not directed to children under 16. A person under the age of legal majority must have permission and appropriate supervision from a parent or guardian. Users should not share a minor’s precise home, school or routine in public match content. If you believe a child’s data was provided inappropriately, contact us so it can be reviewed and removed.
10. Changes to this policy
We may update this policy when the product, providers or legal requirements change. Material changes will be highlighted in the app or on this page where appropriate. The effective date at the top identifies the latest version.
11. Contact and complaints
Data controller: Cryoss
Email: cryossdev@gmail.com
Website: matchday.cryoss.com
If you are in the EEA, you may also lodge a complaint with the data-protection authority in your country. In Poland, the supervisory authority is the President of the Personal Data Protection Office (UODO).