Legal
Privacy Policy
Last updated: November 6, 2026
This Privacy Policy explains how ValuePair ("ValuePair," "we," "us") collects, uses, discloses, and protects your personal information when you use ValuePair, and the choices and rights you have. ValuePair is a values-based friendship and connection service intended for adults (18+).
This is a pre-launch beta.
ValuePair is currently a free, privately operated, non-commercial test. It accepts no payments and carries no advertising. Features may change and data created during the beta may be reset before public launch. You can export or permanently delete your data at any time from Settings.
Who is responsible (controller)
The controller responsible for your data under the EU General Data Protection Regulation (GDPR) is:
Marcel Hanfc/o flexdienst – #21549Kurt-Schumacher-Straße 7467663 KaiserslauternDeutschland
You can also reach us through the contact form.
Information we collect
We collect the following categories of personal information:
- Account details. Your name or chosen display name, unique @handle, email address, and password (stored only as a salted hash). We record whether your email has been verified and when it was first verified.
- Profile & identity. Your date of birth (used to confirm you are 18+ and is not shown to other users as a raw date), gender identity (including any self-description), the genders you are looking to connect with, and your approximate location: a city you select, resolved to a coarse city-center coordinate and country. We never collect or store your precise street address or live GPS location.
- Values answers. Your responses to the onboarding values questionnaire (including how important each topic is to you), your answers and optional free-text notes in the 14-question conversation deck, and answers to any shared question sets you play with a match. When a member who is new to ValuePair is matched with you for their first conversation, we can reuse your earlier deck choices (never your notes, and never the question about faith) so they see your answers right after giving their own. You can review and change these saved answers, or turn this off, in Settings under Matching.
- Public question answers. We store your selected choice, the question source, and the state of a private two-person comparison. For signed-in members, the answer is linked to the ValuePair account so an answer and its active comparisons work across devices. Without an account, a randomized browser identifier provides that continuity in one browser. We store only cryptographic hashes of guest identifiers and shared-link tokens. For a member who created a comparison, we also keep an encrypted copy of its token so the pending link can be recovered on another device. These answers are separate from matching data.
- Messages & connections. Chat messages you send, connection and photo-reveal consents, and interaction signals such as meet intents, check-in nudges, and private next-step choices.
- Match ratings. After a match ends, or once you both finish the questions, we may ask whether the match was fun. Your rating is private: the other person never sees it, and it is never used for matching. We keep it until the match or either account is deleted, include it in your data export, and use it only in anonymous weekly totals. We do not break down a week's ratings when there are fewer than 10.
- Photos. Photos you upload. We re-encode them and strip embedded metadata (including any EXIF/GPS data) on upload, and we keep them private: they are only revealed to a match after a full conversation and only with mutual consent.
- Preferences. Your match filters (including blocked countries), preferred check-in pace, and notification/email preferences, including your product-email consent choice and its change history.
- Safety data. Blocks you create and reports you submit (including the category and any details you provide).
- Technical & usage data. IP address, browser/user agent, session information, a native-app push registration token if you enable push notifications, and in-product analytics events about how the service is used.
Sensitive personal information
Some information you provide is special-category data under Article 9 of the GDPR: information reflecting your worldview or beliefs and information revealing your sexual orientation (such as your gender and the genders you seek), including what can be inferred from your answers. We process it only with your explicit consent (Art. 9(2)(a) GDPR).
You give this consent during onboarding, and we use the data only to operate the core matching and connection service: to find compatible people and show you where your values align. We do not use it for advertising, and we do not sell it. You can withdraw this consent at any time in Settings, which removes you from matching; we keep an internal record of when consent was given or withdrawn.
US state privacy laws likewise treat this information as sensitive and restrict its use.
How we use your information
- To create and secure your account and authenticate you.
- To build your values portrait and automatically match you with compatible people.
- To run the answer-then-reveal conversation, connected chats, and shared question sets.
- To deliver notifications and transactional or service emails you have not opted out of.
- To send occasional product news, beta invitations, and feedback requests only when you have actively opted in to those emails.
- To keep the community safe: handling blocks and abuse reports, and preventing re-matching people who have parted.
- To understand and improve how the product is used, using aggregate and event-level analytics.
- To comply with legal obligations and enforce our Terms.
Legal bases (GDPR)
We process your personal data on these legal bases:
- Art. 6(1)(b): to provide the service you signed up for or requested (your account, matching, conversations, the public One Question feature, and service emails such as password reset).
- Art. 6(1)(a) together with Art. 9(2)(a): your explicit consent for the values, worldview, and orientation data described above, including what can be inferred from your answers. You can withdraw it anytime in Settings.
- Art. 6(1)(f): our legitimate interest in keeping the service secure and abuse-free, and in understanding whether product flows work well enough to improve them. This covers your session IP address and browser data, transient rate limiting, blocks and reports, optional notification emails you can turn off, minimized product events, and anonymous traffic totals. You may object to processing based on this interest.
- Art. 6(1)(a): your consent to native push notifications, given only when you enable them. You can withdraw it in the app or your device settings.
- Art. 6(1)(a): your optional consent to product news, beta invitations, and feedback requests by email. It is separate from service emails and you can withdraw it at any time in Settings or through the signed unsubscribe link.
How we share information
We do not sell your personal information. We share it only:
- With people you are matched or connected with: the parts of your profile, values answers, and (once mutually unlocked) photos that the product is designed to reveal.
- With service providers who host and operate the service on our behalf (for example, our hosting/database provider and our email and push-notification delivery providers). They may process your information only to provide services to us.
- For legal and safety reasons: to comply with law, respond to lawful requests, or protect the rights, safety, and security of our users, the public, or ValuePair.
- In a business transfer: if we are involved in a merger, acquisition, or sale of assets, subject to this Policy.
Hosting
ValuePair runs on servers of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Deutschland (a processor under an Art. 28 data processing agreement). All servers are located in Germany. Our web server keeps no persistent access logs; IP addresses are processed transiently to protect against attacks and abuse (rate limiting) and are stored together with your sign-in session. The legal basis is Art. 6(1)(f).
Email delivery
Transactional and service email (password reset, notifications) is sent through Amazon SES (Amazon Simple Email Service), provided by Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg, an EU processor under an Art. 28 data processing agreement. Email is processed in Amazon’s Europe (Stockholm) region. As AWS belongs to a group with a US parent, some data may be transferred to Amazon Web Services, Inc. in the USA under the EU-US Data Privacy Framework, under which AWS is certified (an adequacy decision, Art. 45 GDPR). We send occasional product news, beta invitations, and feedback requests only if you actively opt in. This choice is separate from activity and service emails. We record when, where, and under which notice version you granted, declined, or withdrew consent. You can withdraw in Settings or through the signed marketing unsubscribe link. Activity emails have their own setting and unsubscribe link.
Links in our notification emails contain a short label naming the type of notification (for example, a new match). If you open such a link while signed in, we record that you returned through that type of email, kept like other product actions for up to 12 months. The label is the same for everyone who gets that type of email. We do not use tracking pixels or identifiers for individual messages.
Native push notifications
If you enable native push notifications, we use Firebase Cloud Messaging (FCM), provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google acts as our processor under the Firebase Data Processing and Security Terms. We send FCM a pseudonymous device registration token and the notification payload: the ValuePair title, a short status message that may include your match’s display name, an app-relative destination, the event type, and a random delivery identifier. We do not send chat-message bodies, question answers, email addresses, or profile answers in a push.
FCM uses an app-installation identifier to route the notification and operates on Google’s global infrastructure, so processing may occur outside the EEA. Restricted transfers are covered by the safeguards in Google’s Firebase Data Processing and Security Terms, including applicable standard contractual clauses. The legal basis is your consent (Art. 6(1)(a) GDPR). You can turn push off in the app or your device settings. We remove stale registration tokens from our server after 60 days and logical delivery/open records after 90 days; account deletion removes both immediately from ValuePair.
Signing in with Google or Apple
You can choose to create your account or sign in using Google or Apple. If you do, that provider authenticates you and sends us your basic profile information: your name, email address, and whether that email is verified (and, for Google, your profile picture). We use it only to create and secure your account, exactly as we would with an email and password. Using a social sign-in is optional; you can always register with an email address and password instead.
With Apple, you can use “Hide My Email” so that Apple shares only a private relay address instead of your real one; email we send to it is forwarded to you by Apple. Sign in with Apple is provided by Apple Inc. (One Apple Park Way, Cupertino, CA 95014, USA).
When you use one of these options, the provider processes your data as an independent controller for the sign-in itself, under its own privacy policy: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) for Google, and Apple for Apple. Data may be transferred to the USA (Google LLC, and Apple) under the EU-US Data Privacy Framework (an adequacy decision, Art. 45 GDPR). The legal basis for our processing of the profile data we receive is Art. 6(1)(b) GDPR (to provide the login you asked for). You can disconnect either connection at any time from your Google or Apple account settings.
Friendship comparisons
For the optional eight-question friendship comparison, you and one invited person submit your own choices before either can see the comparison. This does not create a connected pair or affect matching. Signed-in participants use their account; guests use a separate necessary, randomized HttpOnly cookie for up to 30 days. We store only its hash. Guest answers are not linked to an account when you sign in. Drafts stay in this tab's session storage until submission or discard.
Invitation tokens are stored as hashes and encrypted recovery copies. Links and comparisons expire after 14 days; answer bundles are removed within 30 days. You can delete your feature data from the comparison overview, which also removes affected comparisons for the other person. Account export includes your own answers and safe comparison context; account deletion removes them. Without the guest cookie, guest recovery and deletion controls are unavailable until automatic expiry.
Content-free pilot counters record UTC cohort day, entry surface, generation, a random seed-group label and counts of invitations and completed comparisons. These counters contain no answers, account or browser identifiers, or link credentials and expire within 60 days. Aggregate counts remain after individual comparison deletion.
The self-test
The self-test asks twelve questions about how you are with other people and shows your result on four scales. It needs no account. When you finish, we store your twelve answers, the four scale values computed from them, the page language, a source label if the link you followed carried one, and your gender if you choose to state it. We ask for gender only to see who the test reaches, and you can skip it. We store no name, email address or IP address with the result.
One strictly necessary, randomized HttpOnly cookie lets this browser show, retake and delete its result for up to 30 days. We store only its hash. Your answers also stay in this browser's local storage for up to 30 days, so onboarding can skip questions you already answered if you create an account on this device. The stored result is never linked to an account, including after signup.
You can delete your result at any time on the result page. Otherwise we delete it after 30 days. Before that, we add it to weekly counts by language, source and stated gender. These counts contain no browser identifier. A link you share carries only a coarse version of your result, in five steps per scale, and nothing is stored behind it. Until you finish, your answers stay only in this tab's session storage. Self-test answers become part of a profile, and are used for matching, only if you create an account on this device. You can change them in your profile.
Cookies & product analytics
We use a small number of strictly necessary cookies to keep you signed in and secure, and to remember a language you explicitly choose. If you select the browser-language option, we remove the language preference cookie. If you use One Question without an account, one strictly necessary randomized cookie remembers your answer for up to 30 days. A second necessary cookie keeps your current comparison token for 14 days, so this browser can return to the waiting screen and the private reveal. Signed-in members use their account for this continuity and do not receive these feature cookies. They are used only to provide the feature you requested under § 25 Abs. 2 No. 2 TDDDG.
ValuePair runs its own product analytics on the same German-hosted infrastructure as the service. We do not use analytics cookies, local storage, an advertising identifier, Google Analytics, or another third-party analytics provider. For public page views we keep only the page group (for an article, the published article), internal referral label, UTM source, UTM medium, UTM campaign, referring host, and whether the request came from the web, Android, or iOS app. We do not store an IP address, user agent, exact URL, country, or city with that traffic fact. To estimate daily visitors, we briefly process the request IP address and browser user-agent with a random key for the current Europe/Berlin day. We retain only the resulting daily pseudonym for up to 30 days. The daily key expires at midnight and is deleted by the next traffic request or retention run. These identifiers are not linked across days or to accounts, and cannot identify first-time or returning visitors. Incoming signup attribution stays in the current link and browser memory for up to two hours; it is not written to browser storage. If you create an account, its signup event keeps that attribution, the host name of the external site you arrived from (never the full referring address), and whether you signed up on the web, in the Android app or in the iOS app. If you tap an app store badge on our homepage, we count that click with only the store and the badge position, without an account ID or visitor identifier, for up to 90 days. Country and city summaries for members use the location they provided in their profile. Signed-in product events contain the account ID and only declared coarse fields, never message text, profile answers, question answers, email addresses, or raw URLs. We also record coarse onboarding steps, validation blocks, and critical-action attempts and outcomes for up to 90 days. A random attempt ID connects only the start and result of one action. Email sign-in and signup attempts are recorded without an account ID, form contents or error text; a rejected signup keeps only a rough reason, such as an email that already has an account. On the signup form we also count, without an account ID or visitor identifier, that the form was shown, first used, which field your browser stopped (only the field name, never what you typed) and whether you chose Google or Apple. Signed-in diagnostics use the account ID. We may mark a founder, operator, or test account as an internal analytics cohort so its activity remains available for quality checks without entering the default external-member results. This cohort label is linked to the account, appears in the account export, and is deleted with the account.
Some member records have their own rules:
- Daily visits. When you use ValuePair while signed in, we record one entry per calendar day (Europe/Berlin) noting that you visited and whether you used the website, the iOS app or the Android app. It contains no IP address, device details, pages or times beyond the first visit of that day. We keep it for 90 days, include it in your data export and delete it when you delete your account. We use it only to count how many members come back, in anonymous totals.
- App build. When you use our Android or iOS app, it tells our server its build number, and we keep the most recent build number with your account's activity record.
- Explore invitations. When an Explore invitation is sent, we note on it how recently the recipient was last active, in a broad band (within 2 days, 2 to 7 days, 7 to 30 days, over 30 days, or unknown), to understand whether invitations reach active members. It is never shown in the app. The recipient's data export includes it; the sender's does not. It is deleted with the invitation when either account is deleted.
- Feedback invitations. We may show you a one-time invitation in the app to give feedback. To decide who sees it, we use your last action in ValuePair and how old your account is, and never your gender or your answers. We note when it was shown and whether you tapped it or closed it. This note is in your data export and is deleted with your account. Tapping the form takes you to Google Forms, where Google processes your visit under its own terms. The form doesn't ask who you are, and we don't link your answers to your account. If you email us instead, the contact section below applies.
We use these facts to measure whether product flows work and where an improvement is needed. The legal basis is our legitimate interest under Art. 6(1)(f) GDPR. We do not store analytics identifiers on your device or use these data for advertising.
When you contact us
When you email us or use the contact form, we process your email address, your name if you give it, and your message, only to answer the enquiry (Art. 6(1)(b) if it concerns your account or contract, otherwise Art. 6(1)(f)). Enquiries are deleted once resolved unless a legal retention duty applies. Our contact inbox is hosted by Proton AG, Genf, Schweiz; the EU has an adequacy decision for Switzerland (Art. 45 GDPR).
Your privacy rights
Under the GDPR you have the right to access your data (Art. 15), rectify it (Art. 16), erase it (Art. 17), restrict its processing (Art. 18), receive a portable copy (Art. 20), and object to processing (Art. 21).
You can exercise the core rights directly in the product:
- Access / portability: download a JSON copy of the account and service data available through our self-service export from Settings → Your data.
- Deletion: permanently delete your account and associated data from the same Settings section.
- Withdraw consent: withdraw sensitive-data consent in Settings.
- Email opt-out: manage activity emails and optional product emails separately in Settings, or use the signed channel-specific unsubscribe link in any email.
For a full Article 15 access request, including personal data in retained safety reports where it can lawfully be disclosed, use the contact form or contact us at . We may redact only the parts necessary to protect the rights and freedoms of other people, including reporters and witnesses.
Right to object (Art. 21 GDPR): where we process data on the basis of legitimate interests, you can object at any time for reasons arising from your particular situation, and we will stop unless we have compelling legitimate grounds that override your interests.
You can also complain to a data protection supervisory authority at any time, in particular in the German state or EU member state where you live (Art. 77 GDPR).
If you live in the US, you may also have rights to access, correct, delete, and port your information, and to limit the use of sensitive data. We do not sell or share your personal information for cross-context behavioral advertising. You may make a request or appeal a decision by contacting us at .
Data retention
We keep your personal information for as long as your account is active and as needed to provide the service. When you delete your account, we delete your account data, including product-email consent records, and remove your uploaded photo files. An abuse report filed by someone else may be retained where necessary for safety review, legal compliance, or the establishment, exercise, or defense of legal claims. Account deletion removes the direct subject account ID, but reporter-written details may still contain identifying context. Removing that ID does not necessarily make free text anonymous.
We review ordinary new abuse reports within 30 days. Child-safety reports are escalated for prompt review. We re-review retained evidence at least every six months. We delete report evidence as soon as it is no longer necessary, and normally no later than 24 months after the report was filed. We keep it longer only while an active investigation, dispute, legal claim, or legal retention duty requires it, and we document that reason during review.
Contact enquiries are deleted once they are resolved, and our web server keeps no persistent access logs.
Raw public-traffic facts, including daily pseudonyms, are kept for 30 days. Anonymous daily traffic summaries are kept for 13 months. Passive signed-in exposure events are kept for 90 days. Since this policy update, two of them are kept for up to 12 months because longer-term product measurements start from them: that a new match was shown on your Home screen, and that you saw a connection's daily question. Records of these two from before the update keep the 90-day period. Deliberate product actions are kept for up to 12 months. A compact last-seen and last-action row and any internal analytics cohort label remain while the account exists. Deleting the account deletes its linked raw events, activity row, and cohort label. To keep account erasure from changing an acquisition denominator, we retain at most the earliest safe signup attribution without your account ID until its ordinary retention period ends. We also keep an anonymous record of each account deletion, without an account ID. It holds how long you had the account and how far you got in ValuePair, in broad bands. When you delete your account, you can optionally tell us why; your answer is added to that record. If the account was in an internal analytics cohort, the signup copy and the deletion record retain only this internal status, not the cohort label, so they do not enter external-member results. Other product counts that no longer identify a person are aggregated before raw deletion and may be retained indefinitely so we can understand long-term product change.
When someone you were matched with, or paired with through an invitation, deletes their account, we keep a short record of how that match went, linked to your account, so our match statistics still count it: how the match was made, its mode and question deck, the week it started, whether each of you answered the first question within 48 hours, whether you connected, whether you sent a chat message, and how it ended. It contains no identifier, answers, messages or exact times from the deleted account. If the deleted account was one of our internal accounts, the record also marks it as internal so we can leave it out of member results. Your data export includes the record without that mark, and the record is deleted with your account.
One Question answers are deleted after 30 days. Guest answers include only a hashed browser identifier; signed-in answers remain linked to the member account during that period and are also erased if the account is deleted earlier. Private comparison links expire after 14 days, and expired comparison records are deleted. These answers are not used for matching.
Security
We use technical and organizational measures to protect your information, including encrypted transport, hashed passwords, private photo storage separated from public assets, and access controls on the paths that touch other users’ data. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
Children
ValuePair is for adults. You must be at least 18 years old to use it, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has used the service, contact us at and we will take appropriate action.
Automated matching
Matching runs fully automatically based on your answers and preferences. It introduces people, and it produces no legal or similarly significant effects for you in the sense of Art. 22 GDPR. You can end any match yourself and leave the pool at any time.
Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, notify you. A policy update does not create consent for optional processing. Where consent is required, we will ask you separately.
Contact us
For any privacy question or request, use the contact form, email , or write to us at:
Marcel Hanfc/o flexdienst – #21549Kurt-Schumacher-Straße 7467663 KaiserslauternDeutschland