Leave Privacy Policy
Effective date: July 16, 2026
Who We Are
Leave Travel Technologies Inc. operates Leave and is responsible for the personal information described in this policy. For privacy requests, contact privacy@leave.app. For general support, contact support@leave.app.
Information Collected
- Authentication information from Apple, Google, or email login.
- User ID, username, profile, friends, blocks, and trip memberships.
- Invitations and invite links.
- Chat, polls, reactions, notes, tasks, and itinerary content.
- Photos, receipts, screenshots, and travel documents.
- Expense amounts, splits, balances, settlement status, and payment handles.
- Precise location when enabled.
- AI prompts, attachments, outputs, and relevant trip context.
- Apple purchase information and RevenueCat customer/transaction identifiers.
- IP address, device type, operating system, app version, logs, and diagnostics.
- Limited product-interaction analytics, such as feature use and limit events.
- Push-notification tokens.
- Support requests and beta feedback.
- Waitlist email and marketing-consent records.
How Information Is Collected
Information may come from you, other members of your trip, your device, Apple or Google authentication, Apple purchase systems and RevenueCat, and service providers operating Leave.
How We Use Information
- Provide Leave accounts, trips, chat, documents, location sharing, expenses, and settlement records.
- Authenticate users, protect accounts, prevent abuse, and enforce our Terms and Community Guidelines.
- Operate AI imports, summaries, research, extraction, and draft workflows you choose to use.
- Process App Store purchases, RevenueCat entitlements, refunds, and revocations.
- Send account, invite, push-notification, support, beta, and marketing messages where allowed.
- Analyze reliability, crashes, diagnostics, and product usage to maintain and improve Leave.
- Comply with legal obligations and respond to privacy, safety, or abuse requests.
Service Providers
| Provider/category | Purpose | Possible data |
|---|---|---|
| Azure cloud hosting and storage | Operate the API, host infrastructure, and store uploads | Account, trip, photo, receipt, document, and log data |
| MongoDB Atlas | Operate Leave's production database | Account, membership, trip, message, expense, invite, moderation, purchase-entitlement, and related metadata |
| Firebase and Firebase Crashlytics | Push notifications and crash diagnostics | Push tokens, device identifiers, app version, error context, and diagnostics |
| Sentry | Monitor backend errors, performance, and operational safety alerts | Redacted error and request context, environment, release, and internal operational identifiers |
| OpenAI and Google Gemini | Process user-requested AI features and moderate uploaded images for safety | Prompts, selected attachments, images, receipts, documents, and relevant trip context |
| Google Places and Google authentication | Search places, resolve trip locations, and support Google sign-in | Search terms, coordinates, place requests, and authentication information |
| OpenStreetMap and CARTO | Provide map tiles in trip setup and journey maps | IP address, app identifier, and the map coordinates and zoom level being viewed |
| Apple Maps, Google Maps, and Uber | Open directions or ride-request options when you choose one of these actions | Destination name, address, coordinates, and place identifier |
| Apple | Apple sign-in, App Store purchases, and TestFlight/App Store distribution | Apple account identifiers, purchase information, transaction status, and app-distribution data |
| RevenueCat | Validate purchases and manage paid entitlements | User ID, product, transaction, purchase, refund, and entitlement status |
| Resend | Send verification, support, invite, waitlist, and marketing emails | Name, email address, message content, delivery metadata, and consent records |
AI Processing
When you choose to use an AI feature, Leave may send the text, files, images, receipts, travel documents, and relevant trip context selected for that request to third-party AI providers. Leave does not send this information to an AI provider merely because it exists in your account.
The app asks for permission before your first AI request. AI outputs may be incomplete or incorrect, so review AI-generated summaries, extracted details, research, and drafts before relying on them or adding them to a trip.
Sharing
Trip content is shared with active trip members according to the feature and trip settings. Location is shared only when enabled for a trip. Reports and moderation information may be reviewed by Leave and, where appropriate, trip administrators. We may also disclose information to service providers, legal authorities, or others when required to operate, secure, enforce, or comply with law.
International Processing
Leave and its service providers may process information in Canada, the United States, and other countries where providers operate. Privacy protections may differ from those in your province, state, or country.
Retention
| Data | Retention practice |
|---|---|
| Live trip location | Approximately 30 minutes after the last update, and cleared when location sharing is disabled. |
| Location-share request state | 30 days after the last request. |
| Realtime delivery events | Approximately 10 minutes for delivery and reconnect support. |
| Uploaded trip content | Until deleted by the user, removed by moderation, deleted with the trip, or removed during account deletion where the content is account-owned. |
| Shared trip records after account deletion | Shared expenses, messages, notes, tasks, documents, and itinerary records may remain for other trip members with the deleted user's profile anonymized. |
| Purchase and entitlement records | Retained as needed to validate purchases, handle refunds or revocations, prevent abuse, and maintain tax/accounting records. |
| Support requests and beta feedback | Retained while needed to respond, maintain support history, and protect the service. |
| Waitlist and marketing-consent records | Retained while the waitlist or marketing subscription is active and to keep proof of consent or unsubscribe. |
| Logs and diagnostics | Application infrastructure logs are configured for a 30-day retention window where managed by Leave infrastructure; provider diagnostics follow the provider settings used for the service. |
| Product-interaction analytics | Up to 90 days, and deleted earlier when the associated account or trip is deleted. |
| Deleted account data in backups | May remain in encrypted backups until those backups expire under the production database backup schedule; backups are not used for normal account access. |
Privacy Choices
You can access your information, correct profile information, delete your account, withdraw optional AI consent, disable location sharing, revoke device permissions, unsubscribe from marketing, and submit a privacy complaint. Visit Privacy Choices or email privacy@leave.app.
Security
We use administrative, technical, and organizational safeguards designed to protect personal information. No online service can guarantee perfect security.