GDPR & data processing

This information concerns the current Between Us MVP, where two people complete an anonymous 50-question relationship conversation flow. It covers the answers, computed trait scores, the stored pair compatibility percentage and five-trait comparison snapshot, locale, anonymous capability/session metadata, consent records, and browser-local state described in the Privacy Policy.

The experience is for entertainment and self-development only. It is not a psychological diagnosis, clinical service, scientific prediction, or relationship-success assessment.

The current processing purposes are to:

• Create and authorize an anonymous two-person questionnaire session.
• Receive and save the participant’s 50 answers after the consent step.
• Compute descriptive trait scores, the pair compatibility percentage, and a neutral five-trait comparison.
• Display a participant’s result and connect the two responses when both are complete.
• Remember the minimum browser-local session state needed to resume the flow; after consent, a local answer draft may also be retained for usability.

The current response flow asks for explicit consent before processing and storing questionnaire responses that may contain relationship data. The consent records the version, locale, and timestamp. The API requires consent=true and the current consent version, so a stale client or a false-consent submission is rejected.

The repository does not decide every legal basis for technical or operational processing. The owner must review and approve that basis before launch.

Where applicable, individuals may exercise these rights:

• Access, rectification, erasure, restriction, objection, and data portability.
• Withdrawal of consent for consent-based processing.
• The right to complain to a competent supervisory authority.

No retention period, automatic deletion schedule, or self-service deletion operation is supplied by the repository. The owner must define and approve those controls before launch. Until then, requests should use the current contact route: betweenus@polsia.app.

The final request workflow, identity verification, response timing, and deletion effect on an anonymous session are also owner-review items. This draft does not promise a deletion outcome that the current product has not implemented.

Technical hosting, database, security, monitoring, and related operational providers may process data only as needed to operate the product. The final vendor list, processor agreements, hosting jurisdictions, and safeguards were not supplied and must be verified by the owner.

International transfers may apply. This page does not claim that no transfer occurs and does not invent a country, adequacy decision, standard contractual clause, or other safeguard.

Contact the responsible entity at betweenus@polsia.app for questions or applicable rights requests. The responsible entity details are shown above without an invented address.

This is an owner-review draft — not legal advice. Approval is required before launch, including review of legal bases, retention and deletion, processor/DPA details, transfer safeguards, and the rights-request process.