Privacy policy
Weekend turns travel videos into places on a map and saves them into trips. This page explains what the app collects, why, who else handles it, and how to delete it. Weekend has no ads, and it never sells your data.
What Weekend collects
- An app user ID. Each install gets an anonymous Firebase ID, so the app can talk to our server before you sign in.
- Your Google or Apple account details, if you sign in. With Google: your name, email address and profile photo. With Apple (on iPhone): your name and email address, or the private relay address Apple makes if you choose Hide My Email. They're used to show who's signed in and to keep your trips in sync across your phones.
- Your trips. The trips, places, notes and video sources you save. They're stored on your phone and, once you sign in, in your account so they sync.
- Ideas you send to friends. When you tap Ask friends, Weekend saves the idea on our server: its name, its places, the link to the video it came from, and the first name you give. It gets its own link, and anyone you share that link with can open its page and see these.
- Friends' answers. A friend who opens your link can answer In, Maybe or Not this one, with a first name. The name and answer are saved with your idea, and everyone who has the link can see who answered and how. Friends don't need the app or an account: a random code kept in their browser remembers their answer, and it isn't tied to who they are.
- The videos you share to Weekend. A YouTube link, or a video file from your phone. They're used only to find the places mentioned in them.
- Weekend Pro purchases. If you subscribe, Apple or Google handles the payment; Weekend never sees your card or bank details. We receive what the store tells us: which plan you have, when it started and renews, and your app user ID, so the app and our server know you have Pro.
- How many videos you add each month. Our server keeps a short list of the videos you added this month (their YouTube or Instagram IDs, or a file name), to count them against the free limit. It starts again on the 1st.
- Usage events. When an analysis starts, finishes or fails, and when you save places, the app records the event with counts (how many places were found, verified or saved) and an app instance ID, through Google Analytics for Firebase. The events never include the video, its link, place names or anything you typed. We use them to see whether Weekend finds useful places and to improve it.
- The waitlist. If you join the waitlist on weekendtrips.app, we keep your email address, whether you use Android or iPhone, how you heard about us if you choose to say, and the rough country and city your connection comes from. We use them only to invite you and to write to you about Weekend.
- Website visits. weekendtrips.app counts page views and clicks in PostHog without cookies or anything stored in your browser: each visit gets a new random ID, and no profile is made. Your email is never sent to PostHog.
- Ad measurement. If you reach weekendtrips.app from one of our ads on Facebook or Instagram and join the waitlist from India or the US, our server tells Meta that a sign-up happened. It sends your email address in hashed (scrambled) form so Meta can match it to an account, your connection's IP address and browser type, and the ad's click ID from the link. We use this only to see which ads bring sign-ups. Nothing is stored in your browser.
- Server logs. When the app calls our server, the request is logged with your app user ID, the video link and your IP address. We use them to fix problems and to limit abuse.
Weekend doesn't access your location or contacts. On Android it only sees a video you choose to share or pick. On iPhone, the screen for Instagram and TikTok links asks to see your photo library, so it can spot the reel you just saved. It only looks for videos saved around the time you shared the link, and nothing leaves your phone unless you choose to use it.
Who else handles it
Weekend uses a few services to work. Each gets only what it needs:
- Google Firebase handles sign-in and stores your synced trips, the ideas you send and friends' answers, in Google Cloud's Mumbai region (asia-south1). Google Analytics for Firebase receives the usage events, with advertising ID collection and ad personalisation turned off.
- Google Gemini API watches the video you share and lists the places in it. Video files you upload are deleted from Gemini as soon as they've been analysed.
- Google Places API receives the place names found in a video, to check them against real places and show their photos.
- Google Routes API receives the places in a trip, and the time you plan to leave, to work out the best route and drive times (Weekend Pro).
- RevenueCat (US) manages Weekend Pro subscriptions: it receives your app user ID and your purchases from Apple or Google, and tells the app and our server whether Pro is on.
- Apify (Czech Republic) receives the link of an Instagram reel you share, fetches that public reel and its caption for us, and returns them to our server.
- Apple handles Sign in with Apple on iPhone, and Apple and Google Play take payment for Weekend Pro under their own terms.
- Cloudflare runs our server and website, keeps their logs, and stores the waitlist.
- Meta (US/Ireland) receives the ad sign-up described above, under the Meta Privacy Policy.
- PostHog (US) receives usage events from the app, our server and the website, keyed by a random or app user ID, never by name or email.
We only use services that protect your data at least as well as this policy does. Each one uses it only to provide its service to Weekend, under its own terms, including the Google Privacy Policy, the RevenueCat Privacy Policy and the Cloudflare Privacy Policy. We don't share your data with anyone else.
How it's protected
Everything between the app and these services travels over encrypted connections (HTTPS). Your synced trips can only be read by your own signed-in account. An idea you send can be opened by anyone who has its link, so share it only with the people you're asking; links are long and random, so they can't be guessed.
How long it's kept
- Your trips are kept until you delete them or your account.
- Ideas you send, and friends' answers to them, are kept until you delete your account, which deletes them too. A friend who wants their answer removed can email us.
- Uploaded videos are deleted right after they're analysed.
- Your waitlist entry is kept until you're invited and have had a few weeks to join, or until you ask us to remove it.
- Server logs are kept for up to 30 days.
- This month's list of videos is replaced on the 1st. Purchase records are kept by RevenueCat, Apple and Google as their terms and tax rules require.
- Usage events are kept by Google Analytics for up to 14 months.
Deleting your data
Delete a trip or place in the app at any time. To delete your account and everything synced with it, open Account in the app and tap Delete account, or see how to delete your account. Signing out removes your trips from that phone but keeps them in your account.
Children
Weekend isn't directed at children under 13, and we don't knowingly collect their data. If you believe a child under 13 has given us data, email us and we'll delete it.
Changes
If this policy changes, we'll update this page and the date at the top.
Contact
Questions about your data: weekend.trips.app@gmail.com.