Skip to content
Layag

Data Sharing

Last updated: September 23, 2026

This lists every third party Layag currently shares data with, and exactly what each one receives. It's a companion to the Privacy Policy, not a replacement — see the Privacy Policy for the full picture of what we collect and why. Not legal advice; have it reviewed before relying on it at scale.

Layag does not sell your personal information, and we do not share data with data brokers or advertising networks. We do share specific pieces of data with a small number of service providers, only as needed to run the app and the website — each one is listed below, with what it receives, why, and where it's based. For the complete picture of what we collect and your rights over it, see the Privacy Policy.

1. How to Read This Page

Each entry below names a provider, what data reaches them, and why. "Receives" means that provider processes the data to deliver a specific feature — it doesn't mean they can see everything Layag stores. None of these providers are permitted to use your data for their own advertising, and none of them are data brokers.

2. Google Firebase / Google Cloud

Receives: your account credentials and profile (email, display name, photo), trip and itinerary content, uploaded photos, push-notification tokens, and app usage/crash diagnostics.

Why: Firebase is Layag's primary infrastructure — it runs authentication, the database (Firestore), file storage, serverless backend functions, push delivery (Cloud Messaging), analytics, and crash reporting. Nearly everything the app does passes through it.

Based in: United States (Google Cloud, multi-region).

3. Google Gemini (Vertex AI)

Receives: your trip-planning chat messages and trip details (destination, dates, budget, traveler preferences), plus search parameters used to generate flight/stay estimates and nearby-place suggestions.

Why: to generate itinerary content, flight/stay estimates, and discovery suggestions. Processed server-side; Google does not receive your Layag account credentials, and your content is not used to train third-party foundation models.

Based in: United States (Google Cloud, under Vertex AI's enterprise terms).

4. Google Sign-In and Sign in with Apple

Receives: nothing from us — this flows the other way. These providers share only the name, email, and photo they make available and that you authorize, to let you sign in.

Why: account authentication, as an alternative to email and password.

5. Google Maps, Places & Geocoding

Receives: location queries and coordinates used to render maps, search places, and power nearby-places discovery.

Why: maps, location search, and nearby-place suggestions inside the app.

6. RapidAPI-Hosted Flight & Stay Search Providers

Receives: search parameters you enter — origin/destination, dates, traveler count. These providers do not receive your name, email, or account identity.

Why: to return estimated flight and accommodation options within the app.

7. Unsplash

Receives: nothing — Unsplash supplies destination/cover photography shown in the app. This is a one-way content fetch and does not involve any of your personal data.

8. Klaviyo (Website Only)

Receives: the email address and role (traveler or creator) you submit on the waitlist form, plus any referral code.

Why: to send waitlist confirmation and launch-related emails.

9. Google reCAPTCHA / Firebase App Check (Website Only)

Receives: signals used to distinguish human form submissions from automated ones (e.g. browser/device signals), for the sole purpose of screening the waitlist form for bot signups.

11. What We Don't Do

  • We don't sell personal information to anyone, for any reason.
  • We don't share data with data brokers.
  • We don't use advertising or ad-network SDKs in the app.
  • We don't let any listed provider use your data for their own advertising or resell it to third parties.

12. Questions

Questions about who has your data or why? Email hello@layagapp.com. See the Privacy Policy for retention, deletion, and your rights over this data.