Privacy

ToMatch Privacy Policy

This policy explains what data ToMatch uses, why, for how long, who it is shared with and how to exercise your rights.

Version: 1.0 · Effective and last updated:

1. Data controller

Legal provider: jordiphonedeveloper, trading as Developertech.
Privacy and support email: jordiphonedeveloper@gmail.com

In this policy, “ToMatch”, “we” or “the service” refers to the mobile application, its backend and this website where the provider identified above is responsible for the processing.

2. Who and what this policy covers

It applies to adult ToMatch users, website visitors, people who contact support and anyone who submits a report or exercises their rights. It does not cover independent processing carried out by Google, Apple, the device manufacturer, a social network or a third party the person chooses to contact.

The website included in this package does not incorporate analytics, advertising, tracking pixels or forms connected to a server. Hosting and infrastructure protection may generate strictly necessary technical logs.

3. What data we process

3.1. Account and service identity

  • Internal account identifier, email address or identifier supplied by the sign-in provider, display name and photograph when the person provides or authorises them.
  • Confirmation of adulthood, country or region and verification or fraud-prevention signals. No more documentation than necessary should be retained.
  • Preferences, language, privacy settings and active plan.

3.2. Profile and content

  • Name or alias, photographs, introduction, intention, interests, skills and availability status.
  • Physical details or other optional information the person chooses to add and, separately, publish.
  • A short message or optional contact detail where that feature exists. ToMatch does not offer an in-app chat.
  • Blocks, reports, appeals and evidence submitted for moderation.

3.3. Location and proximity

  • Precise or approximate location provided by the system when the map or a visibility session is activated.
  • Estimated distance, derived area or geographic index, plan radius and session time.
  • Bluetooth proximity signals, ephemeral technical identifiers and a private invitation token.

3.4. Interactions

  • Invitations sent, received, accepted, declined, cancelled or expired; likes; compatible preferences and session status.
  • Records needed to deliver notifications, prevent duplicates, restore state, investigate abuse and resolve incidents.

3.5. Device, security and diagnostics

  • IP address, device/system type and version, app version, time zone, installation identifiers, notification tokens and integrity or App Check signals.
  • Errors, performance, security activity and access logs. Only diagnostic or analytics SDKs disclosed in the final version will be included.

3.6. Subscriptions

Product, plan, status, transaction identifier or purchase token, and the data needed to recognise entitlements. Payment is processed through Google Play Billing or Apple in-app purchases; ToMatch does not receive the full card number.

3.7. Support and website

Email address, the content of the enquiry, files the person chooses to attach and technical email-service metadata. Web hosting may process IP addresses, dates, requested URLs and security signals.

4. Purposes and legal bases

PurposeMain dataLegal basis
Create and maintain the account; display the profile and provide the requested features.Account, profile, settings and plan.Performance of the contract and pre-contractual steps.
Calculate proximity, adapt the map/radius and manage a visibility session.Location, derived area, plan and session.Performance of the requested service and permission/consent where required by the system or applicable law.
Manage invitations, likes, notifications and state restoration.Interactions, tokens and operational logs.Performance of the contract.
Publish optional data or process information that may reveal sexual orientation or sex life.Optional fields chosen by the person.Consent and, where appropriate, explicit consent.
Prevent fraud, impersonation, harassment, access by minors and attacks.Account, device, activity, blocks and reports.Legitimate interest in protecting the service and its users; a legal obligation where applicable.
Moderate, remove content, and resolve reports and appeals.Content, evidence and decisions.Contract, legitimate interest and digital services obligations.
Validate purchases and retain accounting evidence or evidence for claims.Product, token and purchase status.Contract and legal obligations.
Handle support enquiries and rights requests.Contact details, request and proportionate identity information.Contract, legal obligation or consent, as applicable.

We do not sell personal data or use it for third-party behavioural advertising. Any future analytics or campaign must be assessed, documented and reflected in this policy before it is activated.

5. Particularly sensitive data

A dating app may process information that reveals sexual orientation, sex life, identity, intimate preferences or other categories deserving enhanced protection. These fields will be optional, separate from general acceptance, private by default and accompanied by a clear explanation.

  • The person may withdraw consent and hide or delete the data without losing features that do not depend on it.
  • The data will not be used for advertising, nor will sensitive categories be inferred from location or behaviour.
  • The data must not appear in notifications visible on screen or be transmitted over Bluetooth as an openly available profile.
  • The final version must record evidence of explicit consent without turning it into an unnecessary history.

6. Location, map and Bluetooth

Location is requested because it is essential to the proximity feature. The person chooses when to activate visibility and may withdraw permission through system settings, although the map and sessions will then stop working.

The configured range depends on the plan—100 m, 250 m or 500 m—but the actual measurement may vary. We do not guarantee exact accuracy or that the distance corresponds to a route that can be travelled.

When Bluetooth Low Energy is used, the planned design exchanges a private technical token and status signals to process the invitation. It must not broadcast the full profile or maintain stable identifiers that allow tracking between sessions.

Location must not be used to stalk, monitor, infer home addresses or reconstruct movements. Such use violates the rules and may be illegal.

7. Providers and other recipients

We may use providers that act on behalf of ToMatch or as independent controllers for specific functions:

  • Google Firebase: authentication, database, content storage, backend functions, notifications and integrity signals, depending on the final configuration.
  • Google Play: distribution, purchasing and subscription management on Android.
  • Apple: distribution, iOS-compatible sign-in and in-app purchases.
  • Cloudflare: DNS, security, CDN and hosting for this website.
  • Professional service providers: advice, legal defence, auditing or security, subject to a duty of confidentiality.
  • Authorities: where there is a legal obligation, a valid request or an urgent need to protect a person.

Profiles will not be shared with other users outside the chosen visibility controls. A person can copy what they see; we therefore recommend not publishing information you do not want to share.

8. International transfers

Some global providers may process data outside the European Economic Area. Where appropriate, adequacy decisions, standard contractual clauses or other valid safeguards will be used, together with supplementary measures. Before publication, the provider must formalise data-processing agreements, confirm Firebase/Cloudflare regions and maintain an up-to-date list of subprocessors.

9. How long we retain data

CategoryCriterion
Account and profileWhile the account remains active; afterwards, during the deletion process and only to the extent strictly necessary for obligations or claims.
Operational locationDuring the visibility session and for the minimum technical grace period needed for synchronisation or expiry. No movement history is created, except for duly justified, limited security evidence.
Invitations and interactionsFor as long as needed to display status, prevent abuse, resolve disputes and maintain the integrity of the service.
Blocks, reports and moderationFor the time needed to protect users, prevent repeat violations, address appeals and comply with statutory periods.
PurchasesWhile the subscription exists and for the periods required for billing, fraud, claims and legal obligations.
SupportUntil the enquiry is closed and, afterwards, for a reasonable period needed for follow-up or defending claims.
BackupsUntil they are overwritten within the verified technical cycle; they will not be restored to reactivate a deleted account unless legally required.

Before launch, the actual maximum retention period for each record, the Firestore/Storage/Functions TTL policies and the backup cycle must be documented. If they do not match this table, the updated policy communicated before processing will prevail.

10. Your rights

You may request access, rectification, erasure, objection, restriction, portability and withdrawal of consent by writing to jordiphonedeveloper@gmail.com. State your email address or account identifier and the right you wish to exercise. Do not send passwords.

We may request additional information only where there is reasonable doubt about identity. We respond without undue delay and, as a general rule, within one month, unless a lawful extension is communicated. You may also lodge a complaint with the Spanish Data Protection Agency or another competent authority.

11. Account deletion

The app must allow deletion to be initiated from its settings. There is also a public account-deletion page. Deletion from ToMatch does not delete your Google or Apple account and does not automatically cancel a subscription.

12. Automated rules and decisions

The service applies rules based on distance, plan, compatible preferences and status to rank or display profiles. These operations do not in themselves produce legal effects or similarly significant consequences. Moderation may use automated signals to prioritise review, but significant actions must allow human review and appeal where appropriate.

13. Minors

ToMatch is exclusively for people aged 18 and over. We do not seek data from minors. If we detect a minor or receive a credible report, we may impose a precautionary block, carry out proportionate verification and delete the account. Report this immediately through the reporting centre and read the public standards against CSAE and CSAM.

14. Security and data breaches

We apply proportionate measures for access control, authentication, data minimisation, protection of communications, separation of environments, logging, backups and incident response. No system is invulnerable. If an incident poses a risk to individuals, we will act and give notifications in accordance with applicable law.

Protect your device, enable the screen lock, keep the app up to date and do not share access codes. Responsibly disclose vulnerabilities to jordiphonedeveloper@gmail.com.

15. Changes and contact

We will update this policy when features, providers or requirements change. Material changes will be communicated appropriately before they take effect. The published version will include a date and number.

Privacy: jordiphonedeveloper@gmail.com