Privacy Policy

Effective Date: November 3, 2026

This Privacy Policy describes how Tristan Manchester (“the check-in,” “we,” “us”) collects, uses, and shares information when you use the check-in mobile app and website (the “Services”). If you have questions or requests, contact us at tristan@crowlabs.co.

Scope

This policy applies to the Services, including the waitlist.

Information We Collect

Information you provide

  • Account information, such as name, email, and authentication identifiers provided via Clerk.
  • Profile and preferences, such as display name, language, tone style, reminder settings, and timezone.
  • Couple information, such as couple name, anniversary, and invite codes.
  • Content you create, including notes (private or shared) and check-in agenda items.
  • Recordings and transcripts, including audio recordings of check-ins, each participant's audio and video recording of remote video check-ins, transcripts, recaps, and suggested actions.
  • Waitlist information, including name, email address, and platform preference (iOS or Android).

Information collected automatically

  • Device and usage information, such as IP address, device type, browser/OS, app version, log and error data, and timestamps.
  • Diagnostics data, such as JavaScript errors, unhandled errors, native iOS and Android crash reports, stack traces, device model, OS version, and app version, collected via PostHog. Once you sign in, these events are linked to your account ID. They do not include recordings, transcripts, note text, titles, or email addresses, and tokens are removed before sending.
  • App usage data, such as app opens, screens viewed, features used, and in-app survey responses, collected via PostHog and linked to your account ID once you sign in.
  • AI feature metadata, such as the model used, token counts, and response time, sent to PostHog without the prompt or response text.
  • App performance data, such as startup time, screen load time, frame rate, and screen names, with device model, OS and app version, and an app installation ID, collected via Expo Observe. Expo Observe also receives error and crash reports with stack traces. Invite codes, tokens and email addresses are removed from screen names and error messages.
  • App usage data, such as app launches, app version, platform, and OS version, with an app installation ID, collected via Expo Insights.
  • Push notification tokens, used to deliver reminders through Expo’s push notification service.
  • Website metadata, such as country and locale (from request headers) and device type.
  • Call metadata, such as VideoSDK meeting/session IDs, participant IDs, and recording status/identifiers.
  • Attribution and marketing measurement data, such as install/referrer information and device identifiers provided by AppsFlyer.
  • Website analytics data, such as page views, top pages, referrers, and device/browser metadata collected via Vercel Web Analytics and PostHog. PostHog also records relationship health check results and waitlist sign-ups, and links them to your email address when you join the waitlist.
  • Website advertising measurement data collected via the Meta Pixel and Meta Conversions API, such as page views, waitlist sign-ups, Meta cookies and click IDs, IP address, browser user agent, and a hashed copy of the email address and first name you submit.
  • Paywall and subscription activity, such as paywall views, purchase attempts, subscription status, and transaction/receipt metadata received from RevenueCat, Superwall, and the app stores.

How We Use Information

  • Provide and operate the Services, including authentication, partner pairing, notes, and check-ins.
  • Process recordings, generate transcripts, and create recaps and suggested actions.
  • Communicate with you, including waitlist updates and support responses.
  • Maintain security, troubleshoot issues, and improve the Services.
  • Monitor errors, crashes, and app performance, and improve reliability.
  • Deliver paywalls, process purchases, and manage subscriptions and entitlements.
  • Understand how the app and website are used.
  • Measure marketing attribution and campaign performance.
  • Comply with legal obligations.

How We Share Information

  • With your partner for shared notes and check-in outputs.
  • With service providers that help us run the Services (authentication, backend, storage, video calling, transcription, AI analysis, waitlist storage, and hosting).
  • With RevenueCat and Superwall to provide paywalls, process subscriptions, and sync entitlement status.
  • With AppsFlyer to measure installs, attribution, and marketing performance.
  • With Meta to measure website visits and waitlist sign-ups from our ads.
  • With Vercel to host the website and provide web analytics.
  • With PostHog for product analytics on the app and website, and for error and crash reporting in the app.
  • With Expo to measure app usage through Expo Insights, monitor app performance through Expo Observe, deliver app updates through EAS Update, and deliver push notifications.
  • With VideoSDK.live to provide real-time audio/video calling and to support call recording workflows.
  • With Resend to send waitlist and service emails.
  • For legal and safety reasons.

In-app purchases are processed by Apple App Store or Google Play; they handle payment details and provide us with transaction status and receipt information.

We do not sell your personal information. We share identifiers and event data with AppsFlyer and Meta to measure marketing performance.

Service Providers (examples)

  • Clerk (authentication)
  • Convex (backend/database)
  • AWS S3 (recording storage)
  • VideoSDK.live (video calling)
  • AssemblyAI (transcription)
  • AI providers via Vercel AI Gateway, such as Google Gemini and Anthropic Claude (analysis and coaching)
  • PostHog (product analytics, error tracking, and crash reporting; hosted in the EU)
  • Expo (app usage with Expo Insights, app performance monitoring with Expo Observe, app updates with EAS Update, and push notification delivery)
  • RevenueCat (subscription and entitlement management)
  • Superwall (paywalls)
  • AppsFlyer (mobile attribution and analytics)
  • Meta (website ad measurement via the Meta Pixel)
  • Vercel (website hosting and web analytics)
  • Apple App Store / Google Play (in-app purchase processing)
  • Resend (email delivery)
  • Google Sheets / Google APIs (waitlist storage)
  • Hosting/infrastructure providers

Data Retention

  • Audio and video recordings are stored in S3 and scheduled for deletion after transcription, typically within about 72 hours (configurable).
  • Transcripts, notes, recaps, and account data are retained until you delete them or request deletion.
  • Waitlist data is retained until you request removal or we close the waitlist.
  • If you request account deletion, we delete remaining account data within 30 days of your request.
  • Aggregated analytics and diagnostic data that is not linked to you is kept.

Your Choices and Rights

  • Request access, correction, or deletion of your data by contacting us.
  • Control what you share with your partner by marking notes as private or shared.
  • Opt out of waitlist emails at any time.
  • You can control device-level ad tracking and reset advertising identifiers in your iOS/Android settings.

International Transfers

We process data in the United States and in other countries where our providers operate. PostHog stores our analytics, error, and crash data in its EU region.

Security

Data is encrypted in transit with TLS, and our providers encrypt it at rest. Access to production data is limited to the people who run The Check-In.

Children

The Services are not intended for children under 13.

Changes to This Policy

We may update this policy; we will update the effective date.

Contact

tristan@crowlabs.co