This is a product-aligned V1 policy draft, not legal advice and not represented as having been prepared by a lawyer.
Information we collect
We collect account details and an immutable Google account identifier; profile, preferences and participation information; payment status; messages; check-ins; reports; blocks; feedback and notification settings. For security we process a first-party random device-risk identifier, keyed network-risk summaries, action timing, rate-limit events and limited Stripe references when available. We do not collect hardware fingerprints, full card details, a home address or precise live location.
Why we use it
We use information to operate Google-only authentication, profiles, matching, friend pairs, payments, meetup logistics, private chat, notifications, support, moderation, promotion protection, spam prevention, account security, internal analytics and legal compliance. Device and network signals are supporting risk indicators; a shared IP address is never treated as proof that accounts belong to one person.
Promotion protection
A deterministic risk process may consider account age, action velocity, repeated claims, cancellations, no-shows, friend-invite patterns, moderation history and a pseudonymous first-party device signal. It does not use protected characteristics, invasive fingerprinting or an LLM. Most members are approved automatically; uncertain cases may receive a neutral verification step or standard-price option. Internal scores are not public.
Processors and sharing
Google provides account identity for sign-in, Cloudflare hosts the service and provides optional Turnstile verification, Supabase supports application infrastructure, and Stripe processes paid confirmations. We share only what is needed. Confirmed group members never see your DOB, device/network signals, private risk information or payment data.
Storage, security and retention
We use secure HttpOnly cookies, access controls, row-level security, encryption in transit, rate limits, audited privileged actions and verified payment webhooks. We retain risk and entitlement records only as reasonably needed for security, disputes, legal obligations and abuse prevention, then delete or de-identify them.
Your choices and rights
You may access and correct profile information, configure optional notifications, block users, and request account deletion. Some security, dispute and financial records may be retained where legally required. Contact privacy@keenout.com or the Office of the Australian Information Commissioner.
Cookies and analytics
We use essential session cookies and a first-party random device-risk cookie. It is a limited abuse signal, not marketed or treated as a permanent device identity. Privacy-conscious aggregate analytics may measure visits and conversions. Optional marketing technologies are not required for core use.
Organisers and Community Events
Community Events are independent organiser listings, distinct from matched KeenOut Experiences. We process organiser profile and ownership information, event content, RSVP and save records, event reports, material-change history, and genuine event analytics such as views, saves, shares and external ticket-link clicks. Private organiser contact email is used operationally and is not published unnecessarily. KeenOut does not receive external-provider payment-card or purchase details.