Cupido Privacy Notice

1. Scope and data controller

This notice concerns Cupido for iOS and Android. It is separate from the privacy notice for the kuama.it corporate website. The controller is KUAMA SRL, VAT number IT05193790283, Via Germania 7 int. 5, 35010 Vigonza (Padova), Italy. For privacy requests: info@kuama.it; certified email (PEC): kuama@pec.it.

The Data Protection Officer (DPO) for Cupido is Andrea Chiarenza. You can contact the DPO at info@kuama.it with the subject “Privacy / DPO”, or by certified email (PEC) at kuama@pec.it.

Cupido is intended for adults only. A person may participate as a Single, seeking a relationship, and/or as a Cupido, helping a Single with whom they have an active in-app relationship. Providing a date of birth is not documentary age verification.

2. Personal data and its sources

We collect the data needed for your account and authentication, such as email address, technical identifiers, chosen name, date of birth and roles. Full dates of birth and contact details are not displayed on candidate cards.

A profile may include photos, city or area, gender, compatibility preferences, relationship intentions, tags and a presentation. Some information may be proposed by the associated Cupido after the Single has given the consent needed for the profile and matching. Both approve the same version before activation. Editorial approval and accepting an invitation do not replace the Single’s privacy consent.

We also process invitations and relationships, private choices, proposals, acceptances and Matches, chat messages and attachments, read receipts, temporary online status, settings and technical notification endpoints. For security and support, we process minimal technical data, reports and requests to exercise rights.

If a Cupido invites you, we receive the recipient contact needed for the invitation and retain a protected verifier to associate it with the account whose email has been confirmed. An external invitation is valid for 7 days; using it does not automatically accept it. We do not import address books or use the contact for automated reminder campaigns. You can ignore the invitation or contact us without creating an account; after registration, you can decline it in the app.

Data may come from you, your associated Cupido, people you interact with, or technical services necessary for the app. Do not include unnecessary personal data about third parties in descriptions, photos, messages or reports.

3. Purposes, legal bases and special-category data

We use data needed to create and manage accounts, handle invitations, publish profiles, present compatible candidates and proposals, create Matches and provide chat to perform the requested service and related pre-contractual steps (Article 6(1)(b) GDPR).

Some profile and matching information may reveal sex life, sexual orientation or other special categories of data. We request the Single’s explicit consent to process such data for the service purposes described in this notice (Article 9(2)(a) GDPR). The Cupido cannot give this consent on the Single’s behalf.

For security, abuse prevention and manual moderation, we process strictly necessary data on the basis of legitimate interests in protecting the service and people (Article 6(1)(f) GDPR), subject to the relevant balancing assessment. Legal obligations are addressed under Article 6(1)(c) GDPR. Reports may include messages and attachments relevant to the reported facts. Where that information contains special-category data, processing to establish, exercise or defend legal claims is limited to what is necessary for that purpose (Article 9(2)(f) GDPR). We do not use reports to build advertising profiles.

Advertising consent is separate from consent for the service’s special-category data and from accepting the terms. We do not use profiles, chats or matching choices to create advertising audiences or train artificial intelligence models.

4. Visibility, compatibility and messaging

Drafts and photos are not freely public. Information is displayed according to roles and authorisation: the Single and associated Cupido collaborate on the profile; the approved version is visible to authorised Cupidos during consultation and to Singles involved in proposals and Matches. Individual choices are not disclosed to the other party.

Proposals arise from compatibility rules and Cupidos’ selections; a Match requires both Singles to accept. You can change the preferences offered by the app. Reaching a number of reports does not automatically suspend an account: moderation decisions are reviewed by an operator.

Chat history is stored in the cloud and is not end-to-end encrypted. The two Singles and authorised Kuama personnel may access the relevant data as needed for service delivery, support, security, moderation and applicable obligations. Online status is temporary and visible only to active Matches; read receipts do not prove comprehension. View-once media does not prevent screenshots or external copies.

5. Device permissions and location

Photo, camera, microphone and notification permissions are requested when needed for features you choose to use. You can manage permissions in your device settings; denying one may make that feature unavailable without requiring unrelated permissions.

You can search for and select a city or locality through Google Places. The Single confirms the location to use; the Cupido may suggest it but cannot confirm it on the Single’s behalf. Searches and the place identifier are sent to Google to obtain suggestions and resolve the selected place. We do not send account identifiers, photos, chats or relationship preferences to Google Maps.

We use coordinates for the representative point of the selected locality, obtained through Google Geocoding, to check on the server that the approximate distance falls within the radius selected by both Singles. These are not the device’s exact GPS location. Coordinates and radius are private: other users see the approved locality in the profile, not the coordinates or radius. Coordinates expire 29 days after retrieval and may be refreshed for the same place; we do not build a movement history. Changing city or radius does not cancel existing Matches or chats.

The optional “Use my location” feature requests device permission and uses the platform’s geocoding services to suggest a locality. Device coordinates are used temporarily for the suggestion and are not sent to the Cupido backend or Google Maps APIs by this feature. You must still select and confirm the place. We do not track location in the background or use location for advertising targeting.

6. Google AdMob and advertising preferences

At launch, Cupido will use Google AdMob for native advertising cards in consultation flows and Home screens, and full-screen ads at designated breaks. Ads are distinct from profiles and do not create choices, proposals or Matches. Actual activation depends on app configuration and applicable privacy choices.

The advertising SDK may process IP addresses, device or advertising identifiers where available and permitted, technical app and device information, ad interactions and diagnostic data for delivery, measurement and fraud prevention. We do not provide it with biographies, photos, chats, sexual orientation, relationship preferences, matching choices or profile coordinates.

Where required, we gather choices through Google User Messaging Platform before initialising advertising services. The initial integration requests non-personalised ads: this does not mean that identifiers are absent or device-access requirements do not apply. Under the initial configuration, if the required device access is refused, we do not request ads. Refusal does not prevent use of Cupido’s features.

You can change or withdraw your choices through the advertising preferences option in the app’s Settings. Any iOS tracking authorisation is separate from advertising choices and service consent. Google independently determines purposes and means for some processing connected with its advertising products; roles depend on the service and applicable terms.

7. Recipients and international transfers

The backend, SMTP server and backups managed by Kuama use Servereasy infrastructure. The provider places its processing locations and data centres in the European Economic Area (EEA) in its service terms. We use self-hosted Supabase for the database, authentication and application services; this does not involve using the Supabase cloud service to host app data. Data may be accessed by Kuama personnel authorised for their duties, suppliers needed to operate integrated services, Google for advertising and enabled location features, advisers and authorities where applicable. Visibility between users follows the rules described above.

Sign-in is managed by Supabase Auth in our self-hosted installation; authentication emails are sent through the Kuama SMTP server configured in Supabase. We use Expo Push Service for push notifications, which forwards notifications to Apple Push Notification service (iOS) and Google Firebase Cloud Messaging (Android). We process the technical tokens needed for delivery; push notifications contain a generic alert rather than chat text. You can disable them in your device settings.

Expo Push Service, Google AdMob, Google Maps and the Apple and Google push delivery services may involve processing the data needed for those services outside the EEA, including in the United States. Hosting the backend in the EEA does not confine external services’ processing to that area. Expo and Google state that they participate in the EU–US Data Privacy Framework for covered transfers and provide for standard contractual clauses in their terms, depending on the service and transfer; Apple specifies standard contractual clauses for transfers of data collected in the EEA. The links at the end of this page lead to the providers’ information. You can request information about applicable safeguards or a copy from info@kuama.it, with any redactions needed to protect other people’s data and confidential information.

8. Retention, withdrawal and deletion

We keep operational data for as long as needed to provide requested features and manage active account, relationship, proposal and Match states. Minimal information needed to avoid repeating proposals and offer decision undo is separate from a general activity archive.

You can request account deletion in the app’s Settings. The request immediately blocks access to the affected features; operational data and media are deleted within 7 days of the request, except for the specific, justified exceptions described in this notice. Ordinary application logs are retained for 14 days. Reports are kept until closure and for 6 months afterwards, unless a specific documented need requires limited further retention.

We retain minimal consent evidence separately for 5 years after the processing phase covered by each consent ends, for example through withdrawal, replacement or account closure. Evidence of acceptance of the terms is retained for 10 years after the relevant contractual relationship ends. This archive serves our legitimate interest in demonstrating the lawfulness of past processing and compliance with choices and terms (Article 6(1)(f) GDPR); where evidence reveals special-category data, its processing for legal claims is limited to what is necessary under Article 9(2)(f) GDPR. Evidence contains a linkable technical identifier, the purpose, the document version reference and the dates of acceptance, consent, any withdrawal and termination; we do not keep photos, biographies or chats in this archive. Access is restricted to personnel authorised for these purposes. These records remain personal data and are not used to reactivate the account or for advertising.

Where a dispute, proceeding or applicable order requires it, we retain beyond the ordinary deadlines only the evidence needed for that case, for a limited and documented period. We review that need at least every 6 months and delete the evidence when it is no longer necessary, taking account of applicable obligations and time limits for the specific matter.

Backups are retained for up to 30 days and, on restoration, deletions and restrictions are reapplied before the service reopens. We cannot recall copies already downloaded by other users or notifications already delivered. You can contact the controller for information on retention criteria applicable to your case.

9. Your rights and the effects of your choices

Where the GDPR provides, you may request access, rectification, erasure, restriction and portability, object to processing based on legitimate interests, and withdraw consent without affecting the lawfulness of earlier processing. Refusing or withdrawing the consent needed for special-category data prevents use of the relevant dating features and the Cupido’s access to the profile; authentication, consent management, account deletion and privacy requests remain available. Withdrawal starts deletion of the affected data under the periods and exceptions above and is distinct from simply pausing a profile. The Cupido’s consent cannot replace the Single’s, and service consent does not imply advertising consent.

Send requests to info@kuama.it or kuama@pec.it. We may request proportionate information to verify your identity. We respond within the statutory time limits. You may complain to the Italian Garante per la protezione dei dati personali or the competent authority in your Member State.

10. This page and updates

This notice can be read without an account and does not load advertising tags, Google Tag Manager or the Kuama website’s analytics. Requests needed to serve the page may still create technical logs on the web infrastructure. The corporate website’s privacy notice remains a separate document.

The last-updated date identifies the text revision. Material changes are communicated through the app’s channels; new purposes requiring consent are not enabled merely by updating this page.