Information we collect
We collect account details and sign-in identifiers for Google and/or verified email; private date of birth; required onboarding gender and optional dating preferences; profile, preferences and participation information; payment status; messages; check-ins; reports; blocks; feedback and notification settings. If you enable calendar sync, we store your choices and a one-way hash of a private, revocable subscription link; the feed contains only your own exact-time plan status and practical event details. We derive current age from date of birth for eligibility, but do not show full date of birth publicly or send it to analytics. Members choose Female or Male once during onboarding; we do not infer gender from a name, photo or sign-in provider. 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. Photos you choose to share are compressed before upload, stored with the private group conversation and available to confirmed members to view or download. For a public HTTPS link in a confirmed-group message, Keenout may fetch limited page information and proxy its thumbnail to create a private preview; the destination does not receive the member's identity or browser address through that preview image. After a meetup ends, its conversation and photos are automatically deleted once the chat has been inactive for seven days. Friend-to-friend calls use short-lived call and connection-signalling records so the two browsers can connect; Keenout does not record or store the audio or video stream. If you choose live location sharing in a confirmed group, we keep only your latest point until you stop or its 15, 30 or 60 minute period expires; we do not store a route history. We do not collect hardware fingerprints, full card details or a home address.
Why we use it
We use information to operate provider-backed Google and email authentication, verification and password recovery; one canonical profile; event and plan participation, payments, meetup logistics, private chat and friend-to-friend calls, optional personal calendar sync, notifications, support, moderation, promotion protection, spam prevention, account security, internal analytics and legal compliance. A call starts only after a member chooses audio or video and grants the relevant browser permission. The media travels directly between the members' browsers where their networks allow it, and each member's internet or mobile-data provider may charge for data. Calendar sync is generated from Keenout's server-side plan state and never creates a booking. Age confirms eligibility. Dating preferences are considered only in features where both people have chosen dating as an intent. 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 optional account identity for sign-in and, in owner-only venue administration, transient Google Maps place information used to compare a venue against owner-verified records. Cloudflare hosts the service, stores verified email authentication records, provides optional Turnstile verification, and provides the STUN connection-discovery and optional TURN relay used by friend calls. These call services receive the limited network information needed for two browsers to connect; relay credentials are short-lived and issued only to active call participants while Keenout's conservative free-only monthly reservation guard is open. Resend is the primary provider for account, receipt and essential service email; AWS SES may deliver those messages when the configured fallback is used. Stripe processes payments, temporary authorisations, refunds and eligible Apple Pay, Google Pay and Link wallet transactions. For an organiser who voluntarily starts Verified Host, Stripe Identity also collects a government-issued identity document and a live selfie, creates biometric information to compare them and returns the verification outcome to Keenout. Keenout stores the outcome and limited provider references, not copies of the identity document, selfie, biometric template, full card or wallet credentials. We share only what is needed. Other members never see your date of birth, gender, dating preferences, device/network signals, private risk information or payment data.
Optional organiser identity verification
Verified Host is optional. Before opening Stripe Identity, Keenout asks the organiser owner for express consent to a government-issued photo ID and live selfie check. Stripe uses biometric information to compare the selfie with the identity document. An authorised Keenout owner admin may instead record a manual identity review when an accessible or support-led alternative is appropriate. The public blue tick means an identity review succeeded and remains active; it does not guarantee event quality, personal safety, qualifications, licences or future conduct. Keenout may remove the tick after cancellation, failed reverification, account ownership changes, suspension, fraud or a material identity mismatch. Contact privacy@keenout.com for a privacy question or support@keenout.com if you need an accessible alternative review path.
Automated decisions and safeguards
Keenout uses deterministic computer programs and personal information to support capacity and waitlist order, promotion eligibility, fraud and abuse checks, attendance restrictions, notification timing and payment lifecycle decisions. Depending on the decision, inputs can include event eligibility, attendance and cancellation history, account and promotion history, payment state, reports, blocks, and limited device or network risk signals. These programs can rank an eligible waitlist replacement, require verification or standard pricing, prevent a duplicate benefit, pause new bookings for a stated period, or hold a payment action for review. Safety rules, eligibility and capacity remain firm; uncertain or exceptional outcomes can be reviewed through support, and a shared network alone is never proof of misuse.
Overseas processing
Some service providers operate globally. Depending on the configured service region and provider subprocessors, personal information may be processed in Australia, the United States and other countries used by Cloudflare, Google, Stripe, Resend or Amazon Web Services to provide hosting, authentication, payments, fraud prevention and email delivery. Keenout limits the information sent to each provider and uses provider security and contractual controls. Contact privacy@keenout.com for the current provider and country information relevant to your request.
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. The web app may retain device-local installation choices, other non-sensitive device choices and a limited public asset cache. On a device where you open Plans, a short-lived offline snapshot may include your confirmed plan time and only venue details already revealed to you; it is removed after the plan or when you sign out. Private messages, payment details, auth tokens, admin data and unrevealed venues are not placed in its public offline cache. When an account is deleted, visible profile data, Google and custom avatar links, preferences and push credentials are removed or anonymised. We retain only records reasonably required for payment and refund reconciliation, accounting, promotion and one-time entitlement enforcement, attendance integrity, unresolved safety or fraud matters, disputes and legal obligations. Retained promotion identity is keyed and pseudonymous rather than an email or public profile. Where private disaster-recovery exports are enabled, they expire after 30 days; a minimal pseudonymous deletion manifest prevents a restore from reviving a deleted profile and expires after 90 days. Operational data is deleted or reduced to non-identifying aggregates when its configured purpose ends.
Your choices and rights
You may access and correct profile information, configure optional notifications and calendar sync, reset or revoke a private calendar link, block users, log out, change a password where enabled, and delete your account from Profile → Account. Calendar apps may retain entries they already imported after you disconnect, so remove those entries in the calendar app if needed. Date-of-birth corrections are limited and may require recent sign-in or support to prevent restriction and promotion misuse. Deletion requires an intentional confirmation and recent authentication. Active confirmed plans, payments, refunds, organiser responsibilities or unresolved safety matters must be resolved first. Historical messages that must be retained show the sender as Deleted member.
Privacy questions and complaints
Email privacy@keenout.com to request access or correction, question a privacy practice, or make a complaint. Include enough information for us to identify the issue, but do not send payment-card details or identity documents unless we provide a secure method. Keenout will acknowledge the request, investigate it and ordinarily respond within 30 days. If you are not satisfied after giving Keenout a reasonable opportunity to respond, you may contact the Office of the Australian Information Commissioner.
Service and marketing messages
Verification, security, payment receipts, refunds and activity logistics are essential service messages tied to an account or transaction. Keenout keeps promotional email separate. Marketing email is sent only with an appropriate consent basis, identifies Keenout, includes contact details and provides a working unsubscribe method. Unsubscribing from marketing does not stop essential security, payment or joined-plan messages.
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. Device storage may remember dismissed app prompts, non-sensitive interface choices and a random per-tab analytics session. Privacy-conscious first-party analytics may measure page and activity views, a bounded campaign source, referrer hostname, signup and onboarding progress, plan-join outcomes, install eligibility, installation, standalone sessions, notification choices, notification opens and offline sessions. We do not store the full referring URL or use a cross-site advertising identifier. If an onboarded member has not joined a plan, they may optionally tell us the reason; that answer is private and never inferred. Raw product events are retained for a limited period before count-only aggregation. Optional marketing technologies are not required for core use.
Organisers and organiser-hosted events
Organiser-hosted events are independent organiser listings, distinct from member-created plans. 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. For organiser session subscriptions, we also store the member, linked event and plan, provider references, subscription status and paid-through date needed to control booking access. Private organiser contact email is used operationally and is not published unnecessarily. Stripe collects card and bank details on its secure services; Keenout stores only the references and status information needed to operate subscriptions, bookings and payouts. Keenout does not receive card numbers or CVCs.