Privacy Policy

NomadCal is a travel-aware calendar that helps you schedule across time zones. This policy explains what information we collect, how we use it, and the choices you have.

Key points

• We use your information to provide scheduling features (calendar views, booking links, and notifications).
• If you book a meeting via a NomadCal booking link, we collect your email address to send booking confirmations and links to manage your booking (cancel/reschedule). Booking emails include an unsubscribe link.
• If you connect Google Calendar, we access calendar data to detect conflicts/availability and can create, update, and delete events for bookings.
• We do not sell your personal information.

Information we collect

• Account information: when you sign in with Google we store identifiers and basic profile details (e.g. email and display name), plus your NomadCal settings (handle, time zones, privacy controls).
• Google Calendar data (if connected): calendar list metadata (like calendar name and timezone) and event data needed for conflict detection and scheduling (like event times and, when available, title/location/description/attendees).
• Billing information: if you purchase a paid plan, payments are processed by Stripe. We store subscription status and Stripe identifiers (like customer/subscription IDs), but we do not store full card details on our servers.
• Events created in NomadCal: events you create or accept in the app (including title, time, location, attendees, and notes).
• Booking guest information: when you book via a booking link, we store the email address you provide (and optional name/notes) so we can confirm the booking and provide management links.
• Travel locations: locations you add (date ranges + city/timezone) so each day renders in the correct timezone.
• Telegram linking: if you link Telegram, we store your Telegram user/chat identifiers (and optional username) so we can deliver scheduling messages and notifications.
• Diagnostics (optional): if enabled, we store technical error reports and basic product telemetry to keep NomadCal reliable. These reports may include browser user-agent and the page path where the error occurred.
• Usage analytics: we may use Google Analytics (GA4) to understand aggregate usage (for example, page views and basic device information). Google Analytics may set cookies or similar identifiers in your browser.

How we use information

• Provide the service (calendar rendering, scheduling, booking links, notifications).
• Protect abuse and ensure reliability (rate limiting, fraud/abuse prevention).
• Improve the product (when diagnostics are enabled).

Google user data (Google Calendar)

When you connect Google Calendar, NomadCal requests access through Google OAuth. This access is used only to provide the calendar sync and scheduling features you request.

• Identity: we use your Google account information (like email and name) to sign you in and show your account in the app.
• Read access: we read your calendar list and events to detect conflicts (busy/free), power scheduling suggestions, and display synced events in your NomadCal calendar view.
• Write access: when you create a meeting or accept a booking, we can create or update the corresponding event in your selected Google calendar, and delete it if you cancel.

Storage: Google refresh tokens are stored encrypted at rest. Synced calendar metadata and events may be stored in our database so the app can function efficiently.

Sharing: if you add attendees to an event or accept a booking with attendee emails, those attendees may receive calendar invites or updates via Google Calendar. Within NomadCal, we share calendar information according to your privacy settings (full details, free/busy, or nothing).

Limited Use: NomadCal’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, and we do not sell it.

How to disconnect or revoke Google access

• In NomadCal: open Settings → Google Calendar → Disconnect. This removes stored tokens and deletes synced Google events from your NomadCal view.
• In your Google Account: you can also revoke access from your Google Account security settings (third-party access).

How we share information

• With Google: when you connect Google Calendar, we access your calendar data according to the permissions you grant and may write events back to your selected Google calendar.
• With Stripe: if you purchase a paid plan, Stripe processes payments and manages billing. Stripe receives information needed to process your payment and maintain your subscription.
• With other NomadCal users: we share calendar information according to your privacy settings and allow/block lists (full details, free/busy, or nothing).
• With Telegram: if you link Telegram, we send messages you request (e.g. meeting proposals, confirmations, reminders).

We do not sell your personal information.

Data retention

• Account, settings, and calendar data are retained while your account is active.
• Diagnostics data is retained for a limited time (typically 30 days) and then pruned.

Security

Sensitive credentials (like Google refresh tokens) are encrypted at rest. No system is perfectly secure, but we use reasonable technical measures designed to protect your data.

Your choices

• Change your privacy mode (full details vs free/busy vs none) and manage allow/block lists.
• Disable diagnostics in Settings.
• Disconnect Google or unlink Telegram from Settings.
• Use the unsubscribe link in booking emails to stop receiving booking emails.

Contact

Questions about this policy? Email support@nomadcal.xyz.