Privacy Policy

Last updated: 17th July, 2026

Fewer is being built around personal conversation and thoughtful introductions. That requires handling information that may be intimate, sensitive, or difficult to reduce to ordinary profile fields.

This Privacy Policy explains what information Fewer may collect, why we collect it, how it may be used, and the choices and rights available to you.

It applies to:

  • the Fewer website;
  • the Fewer waiting list;
  • research and early-access experiences;
  • future Fewer applications and matchmaking services;
  • communications we send to you;
  • related customer support and safety processes.

Some parts of this policy describe planned functionality that may not yet be available.

1. Who is responsible for your information

The organisation responsible for processing your personal information is:

  • Legal entity: Fewer Love GmbH
  • Registered address: Schönhauser Allee 126, 10437, Berlin
  • Contact: contact@fewer.love

2. The information we may collect

The information collected depends on which parts of Fewer you use.

2.1 Waiting-list information

When you join the waiting list, we may collect:

  • your phone number;
  • your country calling code;
  • your city and country;
  • whether you consent to receive automated text messages;
  • what brought you to Fewer;
  • where you are in your current search for a relationship;
  • what would make an introduction feel worth your time;
  • the date and time you joined;
  • the source through which you discovered Fewer;
  • your responses to optional research questions.

Joining the waiting list should not require consent to promotional text messages.

2.2 Account information

When accounts become available, we may collect:

  • your name;
  • phone number;
  • email address;
  • date of birth;
  • age;
  • city, region, and country;
  • authentication and account-security information;
  • language preferences;
  • account status;
  • identity or age-verification results, where applicable.

We do not currently intend to continuously track your precise device location. If location functionality is later introduced, the product and this policy should explain clearly whether the information is approximate, user-provided, or derived from the device.

2.3 Information you share about yourself

Fewer may invite you to share information through written or spoken conversation, including:

  • your relationship intentions;
  • values and beliefs;
  • lifestyle;
  • communication preferences;
  • relationship experiences;
  • boundaries;
  • expectations;
  • interests;
  • family plans;
  • geographic preferences;
  • reflections about previous relationships;
  • what you find difficult or meaningful when dating;
  • preferences relating to potential introductions.

You decide what to share. However, some information may be necessary for Fewer to provide meaningful introductions.

Please avoid unnecessarily sharing names, contact details, or private information about former partners or other people.

2.4 Voice recordings and transcripts

If Fewer introduces voice conversations, we may collect:

  • audio recordings of conversations with Fewer;
  • transcripts of those recordings;
  • voice messages you deliberately send to another member;
  • feedback conversations;
  • technical information needed to process or play audio.

The final product must explain separately:

  • when recording begins;
  • whether raw audio is retained;
  • how long it is retained;
  • whether transcripts are retained;
  • who can access recordings;
  • which transcription or AI providers process them;
  • whether any recording is reviewed by a person;
  • whether recordings are used to improve models.

Fewer does not currently intend to create biometric voiceprints or use voice to uniquely identify members. This must be reassessed if technical implementation changes.

2.5 Photos and profile content

If profile features become available, we may collect:

  • photos;
  • a short biography;
  • answers shown to other members;
  • introduction content;
  • media you choose to exchange;
  • profile edits and preferences.

The final product must define whether photos are used only for presentation, or whether any automated image analysis occurs. Fewer should not claim that photos are excluded from matching unless that is technically true.

2.6 Relational insights and inferences

Fewer may use information you provide to generate an evolving understanding of matters such as:

  • values;
  • relationship intentions;
  • communication style;
  • lifestyle;
  • preferences;
  • interpersonal patterns;
  • areas of alignment;
  • possible areas of difference;
  • qualities that may make an introduction worth exploring.

These are interpretations and inferences, not objective truths, diagnoses, or professional psychological assessments.

Where possible, you should be able to:

  • review them;
  • correct them;
  • remove them;
  • tell us they do not represent you;
  • provide additional context.

2.7 Introduction and outcome information

To provide and improve introductions, we may collect:

  • introductions offered;
  • whether an introduction was viewed or accepted;
  • whether both people chose to communicate;
  • whether a first or subsequent meeting occurred;
  • private feedback you provide about an introduction;
  • whether both people wanted to continue;
  • broad relationship outcomes over time;
  • reasons an introduction did or did not feel worthwhile;
  • reports or safety concerns.

We should avoid asking members to disclose unnecessary private information about the other person.

Where outcomes are used to improve Fewer, this should happen with an appropriate legal basis and, where needed, explicit consent.

2.8 Communications

We may collect information contained in:

  • messages sent to customer support;
  • safety reports;
  • feedback;
  • research interviews;
  • text-message responses;
  • requests to exercise privacy rights;
  • complaints and appeals.

If member-to-member messaging becomes available, the policy must explain whether messages are encrypted, moderated, automatically scanned, retained, or reviewed following a report.

2.9 Technical and usage information

When you use the website or service, we may automatically collect:

  • IP address;
  • device and browser type;
  • operating system;
  • preferred language;
  • approximate location derived from IP address;
  • pages viewed;
  • buttons selected;
  • dates and times of activity;
  • referral source;
  • crash and performance information;
  • cookie identifiers;
  • consent choices;
  • security events.

We should collect only what is reasonably necessary to operate, secure, and improve Fewer.

2.10 Information from third parties

We may receive information from:

  • authentication providers;
  • identity or age-verification providers;
  • analytics providers;
  • SMS and communication providers;
  • safety and fraud-prevention services;
  • app stores;
  • payment providers;
  • members who submit a report concerning another person.

We should not purchase commercial dating profiles or sensitive audience datasets about individuals.

3. Sensitive information

A relationship service may process highly sensitive information.

Depending on what you choose to share, this may include:

  • sexual orientation;
  • information about your sex life;
  • religious or philosophical beliefs;
  • health-related information;
  • ethnic background;
  • political views;
  • relationship history;
  • inferred values or lifestyle information.

Under EU data-protection law, information concerning sexual orientation or sex life, health, religious beliefs, political opinions, ethnicity, and certain other categories receives additional legal protection. Processing is generally prohibited unless a valid exception applies, such as explicit consent.

Where Fewer asks for or infers sensitive information, we should:

  • explain why it is needed;
  • avoid making it mandatory unless essential;
  • obtain explicit consent where required;
  • allow consent to be withdrawn;
  • restrict access;
  • apply shorter or carefully justified retention;
  • avoid using it for advertising;
  • avoid exposing it to other members unless the user intentionally chooses to share it.

4. How we may use information

We may use personal information for the following purposes.

4.1 To operate the waiting list

This includes:

  • recording your interest;
  • understanding where Fewer should launch;
  • determining likely demand;
  • contacting you about availability;
  • inviting selected participants to research or early access;
  • preventing duplicate, fraudulent, or abusive registrations.

4.2 To communicate with you

We may send:

  • requested service messages;
  • waiting-list confirmations;
  • invitations to early access;
  • essential privacy, security, or legal notices;
  • responses to support requests;
  • promotional launch updates where you have consented.

Direct-marketing SMS should rely on a clear and separate consent where required. EU electronic-communications rules protect people against unsolicited direct marketing, including SMS, and consent may be withdrawn.

You may opt out of marketing messages at any time, including by following the instructions in a message.

Opting out of promotional messages should not remove you from the waiting list unless you separately ask us to remove your waiting-list entry.

4.3 To understand you

We may use information from conversations and questionnaires to:

  • create summaries;
  • identify values and intentions;
  • understand communication preferences;
  • form hypotheses about relational patterns;
  • allow you to review and refine our understanding;
  • personalise your experience.

4.4 To provide introductions

We may use information about members to:

  • identify possible introductions;
  • assess practical compatibility such as geography and relationship intentions;
  • reason about possible areas of alignment or complementarity;
  • avoid known dealbreakers or conflicts;
  • decide when an introduction may be appropriate;
  • explain why an introduction may be worth considering.

Fewer does not claim to predict chemistry, love, safety, or the success of a future relationship.

4.5 To support reflection and communication

We may use information to offer:

  • preparation before a meeting;
  • questions for reflection;
  • structured feedback after an introduction;
  • prompts that help members clarify what they experienced;
  • communication support.

These features do not constitute psychotherapy, medical treatment, or professional relationship counselling.

4.6 To keep members and the service safe

We may use information to:

  • verify age or identity;
  • detect fraudulent or duplicate accounts;
  • prevent harassment, exploitation, impersonation, and abuse;
  • review reports;
  • moderate content;
  • enforce our Terms;
  • protect the rights and safety of members;
  • comply with legal obligations.

4.7 To improve Fewer

We may use appropriately protected information to:

  • understand whether introductions are useful;
  • test product features;
  • improve conversations and generated summaries;
  • evaluate bias and fairness;
  • understand broad patterns in successful and unsuccessful introductions;
  • improve accessibility and performance;
  • conduct internal research.

Personal voice recordings, transcripts, private messages, sensitive insights, or identifiable relationship information should not be used to train general-purpose AI models without clear disclosure and an appropriate legal basis, including consent where required.

4.8 To comply with law

We may process information to:

  • respond to valid legal requests;
  • establish or defend legal claims;
  • keep records required by law;
  • investigate suspected unlawful conduct;
  • protect someone from serious harm;
  • meet regulatory obligations.

5. Legal bases for processing

Where the GDPR or similar laws apply, Fewer must identify a legal basis for each processing purpose.

Depending on the activity, we may rely on:

  • Contract: Where processing is necessary to provide an account, requested service, or introduction.
  • Consent: For example: joining specific research; receiving promotional SMS; processing certain optional sensitive information; optional model-training or product-improvement uses; optional cookies; recording conversations where consent is required. You may withdraw consent at any time. Withdrawal does not make earlier lawful processing unlawful.
  • Explicit consent: Where required for special-category information such as sexual orientation, sex-life information, or certain sensitive inferences.
  • Legitimate interests: Where reasonably necessary to: secure the service; prevent fraud; operate basic analytics; understand service performance; improve non-sensitive features; respond to support requests; protect legal rights. We must assess whether these interests are overridden by your rights and expectations.
  • Legal obligation: Where processing is necessary to comply with applicable law.
  • Vital interests: In exceptional circumstances where processing is necessary to protect someone's life or physical safety.

A detailed internal processing register should map each data field and use to a specific legal basis before launch.

6. Automated processing and profiling

Fewer may rely on automated systems, including artificial intelligence, to:

  • transcribe conversations;
  • generate summaries and inferences;
  • analyse stated values and preferences;
  • identify possible introductions;
  • rank or filter possible introductions;
  • generate explanations;
  • recommend timing;
  • detect fraud, abuse, or safety concerns.

Profiling can include automated evaluation of behaviour, preferences, interests, or other personal characteristics. The EDPB provides specific guidance for automated decision-making and profiling under the GDPR.

Automated systems can be incomplete, inaccurate, or biased. Fewer should therefore provide meaningful ways to:

  • review important inferences;
  • correct inaccurate information;
  • provide context;
  • question an introduction decision;
  • request human review where required by law.

Before launch, we must determine whether any Fewer decision produces a legal or similarly significant effect and whether additional safeguards or rights apply.

7. How we may share information

We may share personal information only where reasonably necessary.

7.1 With people we introduce you to

A potential introduction may receive selected information such as:

  • your name or first name;
  • age;
  • general location;
  • photos;
  • relationship intentions;
  • selected profile content;
  • selected values or interests;
  • a carefully written explanation of why meeting may be worthwhile.

We should not disclose:

  • your raw conversation transcript;
  • private internal insights;
  • exact address;
  • private contact details;
  • sensitive information you did not choose to share;
  • private feedback about another introduction.

The actual introduction format must make clear what information is visible before you participate.

7.2 With service providers

We may use carefully selected providers for:

  • European or international cloud hosting;
  • databases;
  • SMS delivery;
  • authentication;
  • analytics;
  • customer support;
  • transcription;
  • artificial intelligence;
  • safety and moderation;
  • identity and age verification;
  • payments;
  • error monitoring;
  • email delivery.

Providers should be contractually limited to using information only for agreed purposes and must apply appropriate security measures.

The final policy should list important provider categories and, where useful, name key providers.

7.3 With professional advisers

We may share limited information with lawyers, accountants, auditors, insurers, and security advisers where necessary.

7.4 For safety and legal reasons

We may disclose information where reasonably necessary to:

  • comply with law;
  • respond to a valid court or government request;
  • investigate fraud or abuse;
  • protect a person's safety;
  • establish or defend legal claims;
  • enforce our Terms.

7.5 During a business transaction

If Fewer is reorganised, financed, acquired, merged, or sold, information may be disclosed to relevant parties subject to appropriate confidentiality and privacy safeguards.

7.6 What we should not do

Fewer should not:

  • sell personal relationship information to data brokers;
  • sell phone numbers to advertisers;
  • use private conversations for third-party advertising;
  • allow advertisers to target people based on sensitive relationship information;
  • publicly disclose member stories without permission;
  • share raw relational insights with another member;
  • allow service providers to train their own models using Fewer member content unless this is explicitly permitted and lawfully disclosed.

8. Data retention

We should keep personal information only as long as reasonably necessary for the purpose for which it was collected.

Proposed internal retention model:

InformationProposed retention
Waiting-list informationUntil launch in the relevant market, withdrawal, or [24 months] after last meaningful interaction
Marketing consent recordsWhile consent is active, plus a limited suppression record after withdrawal
Account informationWhile the account is active
Raw onboarding audioDelete after transcription and insight generation, and no later than [30 days], unless the member chooses otherwise
Conversation transcriptsWhile needed to provide the account, subject to member deletion controls
Relational insightsWhile the account is active or until individually deleted
Introduction historyWhile the account is active, plus a limited period for safety and dispute handling
Member messages[To be decided]
Safety reportsBased on seriousness, legal requirements, and repeat-abuse prevention
Technical logsUsually [6 to 24 months]
Payment recordsAs required by tax and accounting law
Deleted-account backupsRemove or irreversibly isolate within [30 to 90 days]

These periods are proposals only and must be validated against the actual architecture and legal requirements.

When information is no longer needed, we should delete or anonymise it.

A user's request for deletion may be subject to limited exceptions, such as legal obligations, legal claims, fraud prevention, or safety records. The GDPR provides a right to request erasure, subject to specific exceptions.

9. International data transfers

Fewer intends to be built and hosted primarily in Europe.

Some providers may process information outside the European Economic Area, the United Kingdom, or Switzerland.

Where personal information is transferred internationally, we should use an appropriate legal mechanism, such as:

  • an adequacy decision;
  • approved Standard Contractual Clauses;
  • the UK International Data Transfer Agreement or UK Addendum;
  • another legally recognised safeguard.

European Commission Standard Contractual Clauses are one mechanism used for international transfers where required.

The final policy must reflect the real locations of:

  • production hosting;
  • databases;
  • backups;
  • AI providers;
  • analytics;
  • SMS systems;
  • support tools;
  • employees and contractors with access.

10. Security

We should use technical and organisational measures appropriate to the sensitivity of the information, including where appropriate:

  • encryption in transit and at rest;
  • strict role-based access;
  • multi-factor authentication for staff;
  • separation of production and development environments;
  • vendor security reviews;
  • access logging;
  • incident monitoring;
  • secure deletion;
  • data minimisation;
  • regular security testing;
  • restrictions on exporting sensitive data;
  • staff confidentiality and training;
  • incident-response procedures.

No service can guarantee absolute security.

If a personal-data breach occurs, we will investigate it and notify affected individuals and authorities where required by law.

11. Your privacy rights

Depending on your location, you may have rights to:

  • receive information about how your data is used;
  • access your personal information;
  • correct inaccurate information;
  • delete information;
  • restrict certain processing;
  • object to processing based on legitimate interests;
  • object to direct marketing;
  • withdraw consent;
  • receive certain information in a portable format;
  • complain to a data-protection authority;
  • request safeguards relating to certain automated decisions.

Requests should be possible electronically, and under the GDPR organisations generally must respond without undue delay and normally within one month.

To exercise a right, contact: contact@fewer.love

We may need to verify your identity before fulfilling a request.

You also have the right to lodge a complaint with the relevant supervisory authority. The final policy should identify the lead authority once the legal entity and establishment are confirmed.

12. Your controls

Where supported by the product, you should be able to:

  • update your account information;
  • edit or delete relational insights;
  • withdraw marketing consent;
  • manage optional sensitive information;
  • delete recordings or transcripts where applicable;
  • request an export;
  • close your account;
  • request deletion;
  • object to specific product-improvement uses;
  • change visibility choices.

Privacy controls should be understandable and accessible within the service, not hidden exclusively in legal documents.

13. Text messages

If you separately choose to receive automated text messages, we may use your phone number to send:

  • waiting-list confirmations;
  • early-access invitations;
  • launch announcements;
  • limited product updates;
  • other communications described when consent is collected.

Consent should be optional and recorded separately.

Message frequency may vary. Message and data rates may apply. You may opt out at any time by replying STOP or using another method we provide.

We may still send essential non-promotional messages where legally permitted and necessary to provide a service you requested.

14. Cookies and analytics

The Fewer website may use:

Essential technologies

Required for:

  • security;
  • navigation;
  • remembering privacy choices;
  • maintaining a waiting-list session;
  • preventing abuse.

Optional analytics

Used to understand:

  • page visits;
  • conversion into the waiting list;
  • device categories;
  • broad traffic sources;
  • errors and performance.

Where consent is legally required, optional analytics should not operate until consent is provided.

The final website should include a cookie notice or consent mechanism reflecting the actual technologies installed.

15. Children

Fewer is intended only for people aged 18 or older.

We do not knowingly collect personal information from children. If we learn that someone under 18 has provided personal information, we will take reasonable steps to remove it and restrict access.

The final product should establish an appropriate age-assurance approach before launch.

16. Research and early testing

Before launch, Fewer may invite people to:

  • test prototypes;
  • participate in interviews;
  • answer research questions;
  • evaluate conversations;
  • provide feedback about introductions or concepts.

Research participation should be voluntary.

Before each study, participants should be told:

  • what information will be collected;
  • whether the session is recorded;
  • how the information will be used;
  • who will have access;
  • how long it will be kept;
  • whether quotes may be used;
  • how to withdraw.

Research consent should be separate from marketing consent and general service acceptance.

17. Changes to this policy

We may update this Privacy Policy as Fewer develops.

Where changes are material, we should provide reasonable notice through the website, service, text message, or another suitable channel.

If a new use requires consent, continued use alone should not substitute for obtaining that consent.

18. Contact

For privacy questions or requests:

  • Email: contact@fewer.love
  • Legal entity: Fewer Love GmbH
  • Registered address: Schönhauser Allee 126, 10437, Berlin