Privacy Policy

Last updated: August 15, 2026

Draft notice: VenMeet has not launched yet. This policy describes, accurately, what the app and website collect today, and will be finalized before public launch.

VenMeet is an app that helps close friends find time to meet up. This policy covers two things: the VenMeet iOS app, and this website (venmeet.com), including the waitlist signup form.

Account & authentication data

When you sign up, we collect your email address (via Supabase Auth — either email/password signup, or Sign in with Apple, which may relay a private Apple email address to us instead of your real one). We also store a handle (a public-ish username used so friends can find you) and a display name, both of which you choose, an optional avatar photo URL, and your device’s timezone, which is auto-detected and used to do scheduling math correctly across timezones.

Schedule & availability data

You can mark times you’re free or unavailable — as weekly recurring patterns and as one-off blocks. This is the core of how VenMeet works, and it comes with a deliberate privacy guarantee:

Your raw schedule is never shown to any other user — including your friends. Only VenMeet’s private server-side matching process reads your availability. Friends only ever see matched suggestion times that the matching process proposes — never your underlying schedule. This isn’t just a setting or a UI choice: it’s enforced at the database access-control layer, so your schedule is structurally unreadable by anyone other than you and the matching system.

Friendship data

We store who you’re connected to on VenMeet, the catch-up cadence you set for each friend (how often you’d like to see them), and when you last met up, which is self-reported and confirmed in-app.

Meetup suggestions

When the matching process proposes a time for you and a friend to meet, we store that suggestion and your response to it (accept or decline).

Life topics (optional)

You can optionally add one to five short notes about what’s going on in your life, with an optional category and a short explanation. For “ask me about” topics, you choose whether each note is visible to all friends or selected friends. Topics to avoid are visible to all friends because hiding a boundary from some friends would defeat its purpose. Topics are conversation starters, not a feed: there are no likes, comments, or public profiles. Each topic automatically expires and is removed 60 days after you add it unless you refresh it.

Invites

If you invite someone to VenMeet, we store an invite code tied to your account and whether and when it was redeemed.

Analytics

We use PostHog for a reviewed set of product events that help us understand whether VenMeet’s core loop works. Events include account activation, invitations, schedule saves, topic activity, and meetup responses. When you are signed in, PostHog receives a pseudonymous VenMeet account identifier so we can measure a product journey. Event properties do not include names, email addresses, raw schedules, availability slots, or topic text. VenMeet explicitly disables screen-view and application-lifecycle autocapture, feature-flag requests, surveys, and session replay; the app does not send arbitrary UI interactions. We use PostHog for product analytics only and do not use it for cross-app advertising or tracking, so you won’t see an App Tracking Transparency permission prompt for it.

Push notification data

If you grant notification permission, the app stores your Apple Push Notification service (APNs) device token so it can deliver friend-request, topic, meetup, and reminder notifications. We also store your notification preferences and a delivery record used to respect quiet hours and notification caps. The token is a technical address for a registered device, not a contact list, and is not shown to friends. You can change notification permissions in iOS Settings and notification categories in the app.

Crash reports

If the app crashes, we use Sentry to send us technical diagnostic data: stack traces, device model, OS version, a short history of recent in-app actions leading up to the crash, and, if relevant, the shape of a failed network request. Crash reports include an anonymized, per-install identifier (not tied to your account or identity), but no IP address and no personal content from your account.

What we don’t do

• No ads, no ad SDKs, no ad identifiers (IDFA), no cross-app tracking.
• We never sell or rent your personal data to third parties.
• Your raw schedule and availability are never shown to other users — only matched suggestion times are, and only to the friend involved in that match.

The VenMeet website

This website is separate from the app. The waitlist form on the homepage collects your email address and which platform you’re on (iOS or Android), stored with a timestamp. We use this only to notify you when VenMeet launches — we don’t share it with anyone or use it for advertising. To prevent spam signups, we briefly store a one-way hashed version of your IP address (never the IP itself) alongside submission timing — this is used only to rate-limit repeat submissions, never to identify or track you. We also keep a single running total of visits to the homepage, shown in the page header — it is one number on our own server, incremented once per browsing session. So that number can’t be trivially inflated, a counted visit also writes the same kind of one-way hashed IP address described above, alongside the time of the last visit we counted from it. That record is kept separately from the total, is never linked to it, and tells us nothing about who you are. Nothing else about a visit is stored — no page, no referrer, no device details — so the total counts visits rather than people, and returning to the site later counts again. The website itself doesn’t use cookies or fingerprinting of any kind, so there’s no cookie consent banner — there’s nothing to consent to. Unlike the app, no third-party scripts or analytics run on this website.

Retention questions still being finalized

The exact retention periods for product-analytics events and notification delivery records are still being finalized before public launch. We will publish those periods in a future revision rather than invent a number in this draft. The website waitlist retention rule is separate: waitlist data is kept until the launch announcement plus 90 days, then deleted or migrated only with fresh consent.

Account deletion

You can permanently delete your VenMeet account in the iOS app: open You, choose Delete account, review what will be removed, and complete the re-authentication step. This immediately deletes your authentication record, profile, friendships, schedule, meetup suggestions, life topics, invites, notification data, and registered devices. Account deletion is irreversible and there is no recovery period.

If you signed up with Sign in with Apple, in-app self-service deletion is temporarily unavailable while we finish configuring Apple token revocation — we won’t delete an Apple-linked account without also revoking its Apple tokens. Until that ships, email privacy@venmeet.com and we’ll delete your account and revoke your Apple tokens manually. For all other accounts, if you cannot access the app, contact the same address and we’ll help with your request.

Minimum age

You must be at least 13 years old to use VenMeet. Our final App Store age classification is still being finalized ahead of public launch.

Changes to this policy

We may update this policy as VenMeet develops, especially before public launch. We’ll update the “Last updated” date above whenever we do.

Contact

Questions about this policy? Email privacy@venmeet.com.