Rare HelloBack to the Compass

Privacy notice

Small data footprint. Clear purpose.

This notice explains what Rare Hello stores, which specialist providers process data, why it is needed, and how you can exercise your privacy rights.

Last updated: 28 August 2026

Who controls the data

The data controller is Tomáš Martinák, operator of the Rare Hello validation project in Slovakia. Submit an access, correction, deletion, consent, or safety request through the on-site request form.

What we collect

  • Waitlist: email, city, age range, Compass result, adult confirmation, and consent time.
  • Compass delivery: email, final Compass type, and consent time; individual answers are not stored.
  • Amanda inputs: conversation text or a screenshot sent to OpenAI for a requested analysis. We request that responses are not stored through the API; OpenAI may retain data under its own service policies. Rare Hello does not save these inputs in its database.
  • Dating Studio (Profile Rescue, Message Coach, Match Clarity and Date Prep): your brief, generated text supplied for a refinement, and feedback are sent to OpenAI to generate the requested result. We request that responses are not stored through the API; OpenAI may retain data under its own service policies. Rare Hello does not store these briefs or results on its servers. Your latest draft and result are kept temporarily in this browser tab so a refresh does not erase your work; you can clear both in the tool.
  • Product measurement: a random 30-minute browser session code, registered campaign tags, tool and checkout milestones help us understand how the product is used. These are pseudonymous session counts, not verified unique people. Internal test mode is excluded from customer conversion reports. We do not record your brief, email, raw IP address or full referring URL in these events. Confirmed payment totals, refunds and available processing fees are recorded separately; missing costs are not treated as zero.
  • Amanda and Studio usage limits: a salted, daily-changing hash derived from a network address, purchase reference or access cookie, an attempt counter and an expiry. We do not store the raw address, purchase reference or cookie in these counters. Counters expire after at most two days and are deleted during subsequent requests.
  • Paid-access records: email, Stripe checkout, customer or subscription identifiers, plan, status, and access or renewal time—not card details. An optional signed private backup code lets you restore the same active purchase after Stripe verification. You choose whether to copy or download it; Rare Hello does not store the code in its database, measurement events or URLs. Anyone with that code can use your purchased access, so keep it private. Secure email restoration is also available when its email service is connected.
  • Identity status: Stripe verification-session identifier and status—not document images.
  • Anonymous launch metrics: event name and server time only.
  • Rights and safety requests: email, request type, optional details, status, and time.

Amanda sends the conversation text or screenshot you submit to our AI model provider solely to generate the analysis you requested. Rare Hello does not add the submitted conversation or screenshot to its database. Avoid including names, phone numbers, addresses, payment details, or information that is not needed for the analysis. Stripe processes payment details and identity documents under its own controls; Supabase processes passwordless sign-in emails when connected; ElevenLabs processes selected voice text. Rare Hello does not store your card number, identity-document images, five individual Compass answers, advertising identifier, browser fingerprint, or exact location.

Why we use it

Waitlist data is used with your consent to measure location-level demand and invite suitable adults to a future pilot. Anonymous event totals help us understand where the public funnel fails. Limited request and security data is used to protect the service and respond to legal rights. Optional Amanda inputs are processed to provide the analysis requested by the user. Stripe records are used to manage subscriptions and confirm identity status.

Retention and sharing

Waitlist records are scheduled for deletion after 12 months without a renewed launch purpose, anonymous events after 13 months, and rights request records after three years. Technical cleanup runs as the service processes subsequent activity. Hosting, our AI model provider, Stripe, Supabase, and ElevenLabs may process the limited data needed for their role under their applicable safeguards. We do not sell personal data or use it for targeted advertising.

Your choices and rights

You may withdraw waitlist consent and request access, correction, or deletion. You may also object where applicable or complain to your local data-protection authority. Submit the smallest necessary information in the privacy request form; we may need to verify that the request relates to your email address.

Automated decisions and changes

The free Compass and Amanda provide general orientation only. They do not make a legal or similarly significant decision about you. Material changes to this notice will be published here before they apply to new paid or server-processed services.