Privacy Policy
Last updated November 8, 2026
Maya Migrate builds tools to help immigrants understand and navigate the immigration process. We start from a simple promise: your safety shapes every decision we make. We minimize what we collect, keep the most sensitive data off our servers entirely, and build for a real adversarial threat model (subpoenas, device seizure, detention).
This policy explains what we collect, why, who processes it, and your rights.
We do not collect sensitive personal data we don’t need, and we do not sell your data.
1. What We Collect
-
Information you give us
- Account
- when you sign in with Google or an email login code, we receive your email address (and, for Google, your name).
- Waitlist
- if you join the waitlist, the form (Tally) collects your email.
- Preferences
- settings you choose, such as your time zone and how you want dates and times formatted, so we can display information correctly for you. A time zone places you only in a broad slice of the world: a band that spans many countries, not your country or city. We use it only to show times correctly, never to locate or identify you.
- Location (Digital Rapid Response)
- only when you choose to share it. An emergency alert includes your phone's position, exact or approximate, only if you turn location on for that alert. Approximate means your phone rounds its position before sending it, to the centre of an area about half a mile across: the point your contacts see can be up to half a mile from where you were, and anyone in the same area sends the same point. We put it in the email to your contacts and do not store it. That email stays in their inboxes; once sent, we cannot take it back.
- Appointments (Digital Rapid Response)
- when you ask Maya to watch an appointment, we keep its address and time only while we watch it, and delete the appointment when it ends: when you check in, cancel it, or the alert goes out. If you do not check in, the alert to your contacts includes the address. That email stays in their inboxes; once sent, we cannot take it back.
-
Information that stays on your device, not on our servers
- Emergency contacts (Digital Rapid Response)
- the names and relationships of your emergency contacts are stored encrypted on your device only and never sent to us. The only contact detail that reaches our servers is each contact's email address. We need it to send the alert, and we keep just that: everything else about your contacts is erased, so if you ever set up Digital Rapid Response again, you won't have to re-enter everyone. We use email on purpose: getting an email address doesn't require showing ID, so holding one doesn't reveal a person's legal name, date of birth, or home address the way a phone number can.
-
Information we generate
- Web analytics
- via Google Tag Manager / Google Analytics: page views, clicks, and general browser/device info on our marketing site.
- Diagnostic logs
- (Axiom): error and usage events to fix bugs. We do not log IP addresses or email addresses.
- Push token
- (Firebase Cloud Messaging): a device identifier used only to deliver Digital Rapid Response notifications. A check-in notification's title and text pass through Google, and through Apple on iPhones, to reach your phone. Alerts that clear the phone carry no text.
- Notification wording (Digital Rapid Response)
- if you write your own title and text for the check-in notification, we keep them so our server can send them, until you change them, go back to Maya's wording, or delete your account. Don't put personal information in them: they show on your lock screen and pass through Google and Apple.
- Security (rate limiting)
- to protect the service from abuse, we briefly record the IP address of incoming requests. It is stored on its own, never linked to your account or activity, and is automatically deleted within a day. We do not keep IP addresses in our diagnostic logs.
2. Why We Collect It
- Let you sign in and personalize your experience (e.g., greeting you by name).
- Operate the Digital Rapid Response safety feature.
- Fix bugs, understand usage, and decide what to build next.
- Email you sign-in links and Digital Rapid Response alerts: the only emails we currently send.
3. Who Processes Your Data
We rely on a small set of processors:
- Supabase
- authentication, the sign-up / sign-in emails it sends (login codes), and database (PostgreSQL).
- Railway
- application hosting.
- AhaSend
- transactional email (check-ins and alerts).
- sign-in (OAuth), push delivery (Firebase Cloud Messaging), and website analytics (GA4 via Tag Manager).
- Apple
- distribution of the app through the App Store, and delivery of notifications to iPhones (APNs, which Firebase Cloud Messaging hands them to).
- Tally
- waitlist form.
- Axiom
- diagnostic logging.
- Aptabase
- app usage analytics — which screens are opened and which features are used. Never your check-ins, your alerts, or your contacts.
- Stadia Maps
- address suggestions for the state, county, and appointment addresses you type. Queried by our server, not your device, so Stadia receives only the text you type, never your location, your IP address, or your identity.
- Stripe
- donation payments. Only for people who choose to donate; card details go to Stripe and never reach us.
- Google Sheets
- our record of donations received. Donation data only, never case or profile data.
Our Supabase database, the one holding your account, is in the United States (AWS US East, Ohio). Axiom holds diagnostic logs in the United States. Several other processors store data in the EU/EEA: Railway (our hosting region), AhaSend (Hetzner, Germany/Finland), Aptabase, and Tally. Google and Apple operate globally and rely on Standard Contractual Clauses for transfers outside the EEA. We may share anonymized, non-identifying data with researchers or partners, never personal or identifying data. If legally compelled (e.g., a subpoena), we will comply; otherwise we do not share data with governments or other companies, and our data-minimization design means there is little to disclose.
We sign data processing agreements with the services that handle your data, binding each one to protect it, use it only to provide their service to us (never for their own purposes), and notify us of any breach without undue delay.
4. Where and How Your Data Is Stored
- Stored in Supabase (PostgreSQL); encrypted in transit and at rest, with access limited to those who need it.
- We retain account data until you ask us to delete it.
- You can delete your account and associated data from settings.
5. Your Choices
- Delete your account and data at any time.
- Analytics: our public pages use Google Analytics, which sets cookies in your browser to count visits. It is not loaded on the pages you reach after signing in, and never inside the app. To refuse it, block cookies for this site in your browser, or use its Do Not Track or private browsing mode. We do not yet offer a switch on the page itself.
6. Children
As of now, Maya is not available to children, and we do not knowingly collect personal data from them.
7. Changes
We’ll update this policy as the product evolves and note the date above.
8. Questions
If you have questions about this policy or your data, contact us at contact@mayamigrate.com.