Privacy Policy

Overview

Almidy helps users organize trips, itinerary segments, imports, budgets, sharing, and calendar sync. This policy describes the data we collect, why we collect it, and the choices available to users.

Data We Process

• Account data, such as email address and profile information.
• Trip data, such as destinations, dates, itinerary items, budgets, and collaborator roles.
• Imported travel content, such as email, PDF, calendar, or manually entered unfiled items.
• Calendar connection metadata, OAuth scopes, encrypted tokens, sync status, and external event IDs.
• Operational logs and audit events, such as OAuth, import parsing, sync, API, and security events.

How We Use Data

• To create, store, and display trip workspaces.
• To classify imported travel records and help convert them into itinerary items.
• To sync selected trip places to connected Google or Microsoft calendars.
• To send account, invite, or operational notifications.
• To monitor reliability, security, abuse prevention, and product quality.

Calendar Access

If you connect Google Calendar or Outlook Calendar, Almidy uses calendar event permissions to create, update, and delete Almidy trip events that you choose to sync. Provider tokens are stored server-side and encrypted at rest. We do not expose provider tokens to browser clients.

Service Providers

Almidy may use infrastructure and integration providers including Supabase, Resend, Google APIs, Microsoft Graph, Google Maps, and flight-status data providers. These providers process data only as needed to deliver the app features they support.

Retention and Deletion

Trip and account records are retained while your account is active or as needed for security, legal, or operational requirements. You can request account and data deletion from the Account page. We will review and process deletion requests according to applicable legal and operational requirements.

Contact

For privacy questions or deletion requests, use the in-app Account page or contact the Almidy operator for this deployment.