Service Providers & Subprocessors
Last updated: August 16, 2026
FindMeTime uses the following service providers to operate the product. They process personal data only as needed for the listed purpose. Processing locations are determined by each provider.
Vercel
Used in the ordinary operation of the service.
Purpose: Application hosting, delivery, and edge request metadata
Data categories: IP address, User-Agent, URL, approximate country/ASN from edge headers, account session cookies
Processing location: see the provider’s documentation.
Neon
Used in the ordinary operation of the service.
Purpose: PostgreSQL database hosting
Data categories: Account, booking, guest, calendar-connection, session, and security records stored by the service
Processing location: see the provider’s documentation.
Amazon SES
Used in the ordinary operation of the service.
Purpose: Transactional email delivery (SMTP)
Data categories: Recipient email address and message content for sign-in, booking, security, and contact-form mail
Processing location: see the provider’s documentation.
Cloudflare Turnstile
Used in the ordinary operation of the service.
Purpose: Bot protection on selected forms
Data categories: IP address, TLS/browser signals, and site origin as described by Cloudflare
Processing location: see the provider’s documentation.
Stripe
Used in the ordinary operation of the service.
Purpose: Paid Pro checkout, Customer Portal, invoices, and tax-related billing records
Data categories: Name/email associated with the Stripe Customer, payment method details held by Stripe, subscription identifiers mirrored locally
Processing location: see the provider’s documentation.
Used when you choose that sign-in or calendar integration.
Purpose: Optional Google sign-in and optional Google Calendar conflict checks and booking write-back
Data categories: Google account identifiers and email; calendar IDs/names; OAuth tokens; free/busy windows; events FindMeTime creates when write-back is enabled (including guest attendee emails when provided)
Processing location: see the provider’s documentation.
GitHub
Used when you choose that sign-in or calendar integration.
Purpose: Optional GitHub sign-in
Data categories: GitHub account identifiers, email, and display name you authorize
Processing location: see the provider’s documentation.
Microsoft
Used when you choose that sign-in or calendar integration.
Purpose: Optional Microsoft sign-in (not Microsoft Calendar)
Data categories: Microsoft account identifiers, email, and display name you authorize
Processing location: see the provider’s documentation.
LINE
Used when you choose that sign-in or calendar integration.
Purpose: Optional LINE sign-in
Data categories: LINE account identifiers and email when LINE shares it
Processing location: see the provider’s documentation.