Trust preview

Trust has to be visible in product behavior, not just in brand language

KeepItUp is designed for real-world meetings, so this page explains the current trust boundary in plain language. It describes what the preview does now, what remains intentionally unavailable, and what still requires launch-country legal and operational review.

Where can I use KeepItUp?

  • KeepItUp can be used worldwide to organize and join sports events — participation is not geographically restricted.
  • Everyone gets the same GDPR-grade privacy, safety standards, and community care — wherever you play.
  • Events are organized by members, not by us — we do not host, supervise, or provide support in every location. Local availability depends on hosts in each area.
  • Everyone gets EU-grade (GDPR) privacy protection from the start, wherever they are.

What the product protects by default

  • Exact meeting details stay hidden until a host accepts a request.
  • Adults only. The preview is built for members who are 18 or older.
  • Blocking immediately removes shared requests, places, room access, and exact-location access.
  • Reporting exists as a dedicated safety path, separate from feedback or private reflection.

What we do not claim

  • Email verification means inbox control only. It is not identity, age, or background verification.
  • No public trust score, verified-community badge, or host guarantee exists in this preview.
  • The Movement Arc is private reflection, not public proof that another member is safe or reliable.
  • Moderation and reporting reduce harm; they do not remove all real-world risk.

Design choices that stay intentionally constrained

  • No open member-to-member chat launches before blocking, reporting, moderation evidence, and response operations are ready.
  • No public popularity rankings, streaks, or rewards exist for rejection, screen time, or pressure.
  • Hosts can accept or skip requests, and a third skip quietly closes the request for that event.
  • Discovery shows approximate area and fit, not unnecessary precise location exposure.

What still requires real-world readiness before launch

  • Final launch-country legal review, including Europe-specific privacy, consumer, and platform obligations.
  • Operational moderation staffing, escalation coverage, and response-time claims.
  • Any future identity, age, payment, or host-verification programs that would need separate proof and controls.
  • Public safety or trust marketing language beyond what the product can actually demonstrate.

For the current member-facing boundary, also read the Terms preview, Privacy Notice preview, and the safety guidance.

If you are evaluating the product for launch, partnerships, hosts, or member communications, this page is the shortest honest summary of the current trust posture.