Maynooth Matches — Privacy Policy

Version 1.0 — 29 October 2026

1. Who is responsible for your information?

Maynooth Matches is operated by Shawn Maloney, an individual based in Ireland (the controller for the purposes of data-protection law).

• Website: https://maynoothmatches.com
• Privacy and support contact: support@maynoothmatches.com
• Correspondence address: Buckley House Accommodation, Maynooth, County Kildare, Ireland

2. Who can use Maynooth Matches?

The service is intended exclusively for adults aged 18 or older, whether or not they attend a university. University affiliation is optional. The service is designed for introductions and dating; interactions and dating preferences may be sensitive.

3. Information we collect

Depending on how you use the service, we process:

• Account and eligibility: email address; private date of birth; confirmation of age eligibility; authentication/session and policy-acceptance records; age-assurance status and reference, if used.
• Profile: first name, publicly shown age (not date of birth), gender, preferences and relationship intentions; photographs; biography, prompts, interests, and optional details such as university, course, home area and lifestyle choices.
• Dating activity: Likes, Passes, Super Likes, private Campus Crush nominations, matches, Rewinds and entitlements, incoming-Like reveal records and referral rewards.
• Communications: text chats, timestamps and relevant read/unread status.
• Safety: reports, blocks, moderation decisions, appeals, potential abuse indicators and restricted incident records.
• Technical information: device/browser details, security logs, IP addresses and essential authentication storage, as necessary for security and service delivery.

The app does not support sending images/videos in chats or voice/video calling at initial launch.

4. Purposes and legal grounds

We use information to operate accounts, display approved profiles, connect members, deliver matches/messages, administer requested features, provide support, maintain security, and comply with legal obligations.

The legal basis for maintaining an account and providing requested matching and messaging functionality is generally performance of the user agreement (GDPR Article 6(1)(b)); processing necessary for security, fraud prevention and safety may rely on legitimate interests (Article 6(1)(f)) following a balancing assessment; statutory compliance may rely on legal obligation (Article 6(1)(c)). Where dating information reveals a special category of personal data, including sexual orientation or sex life, the service will require a separately presented, explicit, informed and withdrawable consent where the applicable legal basis is Article 9(2)(a). Withdrawal may mean that certain dating features or the account cannot continue, and users will be informed before consenting. These bases and the actual separate-consent interface must be validated by counsel and the technical implementer before publication.

5. What other users can see

Other members can see only approved profile information intentionally made public within the app, including your first name, age, chosen photographs, relationship intention and visible profile fields. Private email addresses, full dates of birth, authentication data, confidential Campus Crush nominations, report details and private chats are not publicly available. Messages are made accessible only to authorized participants, subject to necessary safety and legal processes. Optional profile fields can be hidden where the app provides that setting.

A Campus Crush nomination does not appear as an ordinary incoming Like and is not disclosed to the recipient unless the applicable matching rules reveal a connection.

6. Moderation, safety and age assurance

Public-facing photographs and profile text are screened before publication, with uncertain cases held for human review. Reports and appeals may involve authorized manual review. Where an age-assurance provider is used, the app should collect only the necessary outcome and limited verification reference wherever feasible.

7. Service providers and international transfers

Maynooth Matches uses Supabase for backend services and private storage, and Resend for sending transactional emails. The actual hosting regions, subprocessors, retention and international transfers must be verified from the deployed configuration and vendor terms. Further services (such as web hosting, CAPTCHA, age assurance, moderation and error monitoring) must be added to this policy only when configured and verified.

8. Account deletion and retention

Members can request permanent deletion inside the app or seek assistance via support@maynoothmatches.com and the website's account-deletion page. On verified deletion, the account and profile are removed from normal operation, and associated photographs, matches, conversations and other account-linked records are deleted or anonymized as technically appropriate.

A limited subset of records relating to serious abuse, safety incidents, fraud, legal claims or compliance obligations may be retained only where justified and for a defined period. Backups may expire on a separate cycle, with restricted access in the meantime. We cannot retract screenshots or copies already retained by other members.

9. Your data-protection rights

Subject to applicable law, you may request access, correction, erasure, restriction, portability or objection; where processing relies on consent, you may withdraw that consent. We may need reasonable identity verification before acting. Contact support@maynoothmatches.com. You can complain to the Irish Data Protection Commission or another competent supervisory authority.

10. Cookies and app storage

The website and web app may use strictly necessary cookies or local storage for authentication, security and core functionality. Non-essential advertising or analytics should remain disabled until the necessary notices and consent mechanisms are implemented. Non-essential tracking will not be introduced without the required notice and consent.

11. Changes

We may update this policy and will notify users appropriately about material changes. Where law requires it, we will ask for a fresh agreement or consent. Registration must remain restricted until this policy is legally approved, published and correctly versioned in the backend.