Privacy Policy
Last updated 3 November 2026
The short version.
- Your trips live on your phone, encrypted. You can use Triplogue without an account.
- Signing in with Google and connecting Gmail are separate choices. Signing in doesn’t read your email.
- If you connect Gmail, your phone reads only your travel confirmations and turns them into a timeline. Your email and its attachments never reach our servers.
- If you forward an email to your Triplogue address, it waits on our server until your phone reads it. Then it’s deleted, after 7 days at most.
- If you sign in, we keep one private backup of what you add and change yourself, including what you spend on trips only you are on. Nothing found in Gmail or your calendar goes into it, except changes you make to a booking on a shared trip. The barcodes on your passes and your photos stay off it too.
- When you share a trip, or join one and turn on Add my bookings, the bookings for that trip go to our server so the people on it can see them, including ones Triplogue finds later. Any booking can be set to Only you.
- When you’re signed in and share or paste a link or an AI trip plan, our server asks Anthropic’s Claude model to find the places in its words and any you add. Text from your email, calendar or bookings never goes to that model.
- Share how you use Triplogue starts on. While it’s on, we receive anonymous usage events, never your email. Turn it off in Me → Privacy. No ads, and no selling.
- Delete your account in the app: Me → Account → Delete account.
That summary is there to be useful. It isn’t the agreement. The sections below describe the app as it works today.
1. Who we are
Triplogue is an iPhone app made by Blacktop Social LLC (“Blacktop Social,” “we,” “us”). We are responsible for the personal information described here.
Blacktop Social LLC
606 Metropolitan Avenue, 6B, Brooklyn, NY 11211
legal@blacktop.social
Triplogue is in testing and not yet released. This policy covers the app as it works now. If a new feature would collect more, we’ll update this page before it does.
2. What Triplogue collects
- Your bookings and trips. These come from Gmail (if you connect it), your calendar (if you ask it to look), emails you forward to your Triplogue address, files and screenshots you share into the app, text you paste, or details you type. A booking can include:
- place names, dates and times, and addresses;
- confirmation numbers and PINs, ticket numbers, seats and rooms;
- the names of the travelers on it and who booked it;
- prices, and a host’s check-in instructions.
- Tickets and passes. Triplogue reads the barcode or QR code on a boarding pass, ticket or e-ticket, so you can show it offline.
- Places you save. When you share a TikTok, YouTube or Instagram post, or a Google Maps or Apple Maps link, Triplogue finds the places it names. You choose which to keep, and which trip and day they go on.
- AI trip plans. When you paste or share a trip plan from an AI app such as ChatGPT, Gemini or Claude, or share a ChatGPT link with Triplogue+, Triplogue finds the places it names on each day. If you save the plan, Triplogue keeps its title, the names of its days and which places are on each, never its text.
- Things you make. Trips, ideas you pin to a trip, notes and times you add, and your travel preferences. Also your name, bio and home city, a profile photo, and cover photos you choose.
- Costs. Costs you add to a trip (what for, how much, when, where, who paid and who’s in), with a note, a category, and a photo you attach, such as a receipt or a meal. On a trip only you are on, these are your spending.
- Shared trips. If you share a trip or join one: its costs, packing lists and what’s checked off, and your Venmo username if you add it.
- Invites you prepare. The name of the person you’re inviting and your message. Triplogue can suggest names from the travelers on your bookings.
- Travel friends. The friend links you make, your @handle if you choose one, the people you ask to be your friend or who ask you, and your answers.
- Your photos’ dates, if you allow it. To show each trip’s photos day by day, Triplogue reads when the photos in your library were taken. It keeps a photo only when you choose one.
- Your account, if you make one.
- With Apple, we receive your email address (or Apple’s private relay address) and an Apple account identifier.
- With Google, we receive your Google email address, name, and a Google account identifier.
- Apple shares your name only the first time you sign in. Triplogue puts it in your profile.
- Your Gmail and Google Calendar connection, if you make one. This is a Google access key and your Google address. They stay on your phone (see Section 5).
- Purchases, if you buy Triplogue+. Apple handles the payment. We receive what you bought and until when it lasts (see Section 4).
Triplogue does not ask for your location, contacts, camera or microphone. It doesn’t read passport numbers or dates of birth from your documents.
3. What stays on your phone
Everything in Section 2 stays on your phone, except what Section 4 lists.
- Encrypted store. Your trips, bookings, codes and tickets are kept in an encrypted store (AES-256). Its key is created on your phone and kept in your iPhone’s Keychain for this device only.
- Reading happens on your phone. Gmail, your calendar, forwarded emails, PDFs and screenshots are read on the phone, using Apple’s built-in tools:
- PDFKit for documents;
- Vision for text and barcodes;
- Apple’s on-device language model, when your iPhone has Apple Intelligence. None of that reading is sent to us or to an AI service.
- Places in posts you share. Your phone reads the words the post shares publicly, or the Maps link, and asks Apple Maps where each place is. From a TikTok, it reads the caption, TikTok’s subtitles of what’s said, the on-screen text and the tagged place. From a YouTube video, its title, description and the creator’s own comments (Section 7). From Instagram, the caption. It never downloads the video or its sound. If you’re signed in, it also asks our server to read the link (Section 4). To put a stay or a restaurant from your bookings on a map, your phone looks up its name and address in Apple Maps.
- Photos stay on your phone, except a photo you add to a cost on a shared trip (Section 4, Cost photos). A trip’s story and trip card are made on the phone from your library, and you choose where to share them.
- Files you add. The original PDF, screenshot or forwarded email, and photos you pick, are kept in Triplogue’s own storage on the phone until you delete them.
- Offline copies. To open quickly offline, Triplogue keeps a short-lived copy of trip pages you’ve viewed for up to 7 days. Your bookings, codes and tickets are left out of that copy.
- Reminders. Check-in reminders are scheduled by your phone, with no server involved. Notifications about forwarded emails are the one exception (Section 4).
4. What reaches our servers
Nothing, unless you sign in. Signed out, Triplogue talks only to Apple (maps, place search, sign-in and purchases), to Google (if you connect Gmail or Google Calendar, or share a YouTube link), to TikTok or Instagram (if you share one of their links), to RevenueCat (if you buy Triplogue+), and to PostHog (while Share how you use Triplogue is on, Section 6).
If you sign in, our database provider (Supabase) holds these for us.
-
Your login. Your email address, how you signed in (Apple, Google or email), your account identifier with that provider, and when you signed in. Blacktop Social apps share one login system, so the same login can work in our other apps.
-
Your Blacktop record. Your verified email address is linked to Blacktop Social’s shared record of the people who use our products. It notes that you use Triplogue and when you last did.
-
One backup of what you made in Triplogue. This gets it back on a new phone. It includes:
- trips you created;
- bookings you added by hand, from a file, a screenshot, pasted text or a forwarded email, with their details, such as confirmation numbers, seats, rooms, addresses, the names on them, and check-in steps you typed;
- changes you made to those bookings, such as a time you added or a note;
- what you spend on trips only you are on: each cost’s amount, what it was for, when, and its note, place and category;
- places you saved, with the link, title or caption and creator of the post they came from; ideas you pinned, invites you prepared (the name you gave, without the message or an email address), prompts you dismissed;
- AI trip plans you saved: each one’s title, the names of its days and which places are on each, but not the plan’s text or the link it came from;
- your name, bio, home city and travel preferences.
What Triplogue finds in Gmail or your calendar stays out of the backup:
- the bookings and trips it finds stay on your phone, and so do places you save from one of those emails or calendar events;
- a place you pick from one of those bookings for a cost stays on your phone, unless that booking is on the same shared trip for its travelers to see.
One thing you choose is the exception: a booking you put on a shared trip. The backup keeps your changes to it and who can see it, so they hold on a new phone. A name Triplogue suggested from your bookings stays on your phone in an invite you haven’t sent, and goes only with the invite when you send it.
The backup never includes:
- any email content;
- the barcodes or QR codes on your tickets and passes;
- your photos, including cost photos, or the files you imported.
It is one copy per account, and each change replaces it. Only your signed-in account can read it.
-
Places in links you share. When you’re signed in and share or paste a link, such as a TikTok, Instagram or YouTube post or a blog post, your phone sends our server the link and up to 8,000 characters of text it read for it (Section 3), such as the post’s caption, a TikTok’s subtitles, on-screen text and tagged place, or a YouTube video’s title, description and the creator’s own comments, and any words you shared or pasted with it. For a YouTube link, our server can ask YouTube for the video’s title, description and the creator’s own comments itself. Our server sends that text to Anthropic’s Claude model, which names the places in it, what kind each one is (a stay, food, a sight and so on) and its city. Nothing from your emails, calendar events or bookings is sent, not even a link found in one, and neither are your account details. Google Maps and Apple Maps links are read on your phone. Signed out, past the limit (25 reads a day, 200 a month), or when our server can’t answer, your phone reads the link itself.
- When our server asked YouTube for a video’s words itself, we keep the places found in them for up to 30 days, by the video’s link, so the next person who shares that video gets the same answer. We don’t keep the words. Text that came from your phone isn’t kept.
- Each account can make up to 25 of these reads a day and 200 a month, links and AI trip plans together. To apply the limit, we count your reads for the current day and month. Past the limit, or when you’re signed out, your phone finds the places by itself.
-
AI trip plans. When you’re signed in and paste or share a trip plan you copied from an AI app, your phone sends our server the plan’s text. Our server sends it to Anthropic’s Claude model, which names the places on each day, as it does for links. The plan’s text isn’t kept, on our server or in your backup. Text from your emails and calendar events never becomes a plan. Signed out, past the limit, or when our server can’t answer, your phone reads the plan itself.
- ChatGPT links, with Triplogue+. When you share a link to a ChatGPT chat, your phone opens the shared page itself. Our server never does. Your phone takes ChatGPT’s answers from it, and the plan in them is read as above. Your own messages in that chat stay on your phone, where Triplogue uses them only to tell which city the plan is for.
- Saved plans. A plan you save goes in your backup like your other saved places (above). Only you see it. A place from it that you add to a shared trip stays on your phone unless you choose to share it, and the chat’s link never goes with it.
-
Trips you share or join. So everyone on a trip sees the same plan, our server keeps:
- your name as the others see it;
- the trip’s name, dates and places, kept to the places you chose to show;
- the bookings you put on the trip: what kind each one is, its place (name, city and country, or the airports for a flight) and times. This includes bookings Triplogue found in Gmail or your calendar, once you put them on a shared trip. If you shared the trip, or joined it and turned on Add my bookings, later checks add bookings whose dates fit that trip without asking each time. Any booking can be set to Only you, which keeps it off the trip;
- for the travelers you choose, those bookings’ details: confirmation code, the name on the reservation, address, check-in steps and contact;
- ideas pinned and votes;
- invites: a scrambled form of each link, and the first name of the person you invited, if you gave one;
- costs, each with its note, place and category, kept with the cost for the people on the trip;
- settle-ups, packing lists and what’s checked off, and your Venmo username if you add it.
Boarding passes and other passes are never shared. Anyone with an invite link can see a preview: your first name, the trip’s name, dates and cities, its cover, and how many plans and travelers it has.
-
Cost photos. If you add a photo to a cost on a shared trip, Triplogue stores a compressed copy (about 300 KB) on Blacktop’s servers so the other travelers on that trip can see it. Followers can’t. It’s deleted when the cost, the trip or your account is deleted. Photos on trips only you are on stay on your phone.
-
Emails you forward. Your Triplogue address is your first name and 8 random characters, at triplogue.app. An email sent to it waits on our server (sender, subject, text, and up to 3 PDF attachments) until your phone picks it up. Your phone reads it, and our server deletes it. If your phone never opens Triplogue, it’s deleted after 7 days. Our server doesn’t look for bookings in it. We note whether it came from one of your own addresses: if it didn’t, it waits on your phone for you to check it.
-
Notifications for forwarded emails, if you turn them on. Your phone’s push token, so we can tell you when a forwarded email arrives. The notification names only the company that sent it (for example, Booking.com), never its subject or contents. The token is removed when you sign out or delete your account.
-
Travel friends, if you use them.
- Friend links. When you make a friend link, we keep a scrambled form of it, never the link itself, with who made it and when it stops working.
- What a link shows. Anyone signed in to Triplogue who has your link can see your first name, and whether the two of you are already friends or which of you has asked. A link never shows your full name, your account, your trips or when you made it.
- Your @handle, if you choose one. We keep it, with when you set it, so others can find you. Your friends, and anyone you ask to be friends, see your handle. Anyone signed in to Triplogue who types your handle exactly can see your first name, and whether the two of you are already friends or which of you has asked, the same as with your link. Then they can ask to be your friend. A search never suggests handles or finishes one for you, it never shows your full name or your account, and you can’t search by name, email or phone number. Some words can’t be handles, such as “admin” or “triplogue”.
- Finding people. Each time you look up a handle, we count it for 24 hours: up to 60 lookups a day. You can set or change your handle up to 3 times a day. Asking someone by handle counts toward the same 30 friend requests a day as a link. When you change your handle, your old one is free for someone else to take.
- Requests. When someone opens your link, or types your handle, and asks to be your friend, we keep who asked, who they asked, and when. The person you ask sees your name with your request.
- Saying no. If you say “not now” to a request, or remove a friend, we keep that you said no for 90 days, so that person’s new requests don’t reach you. They aren’t told. If you cancel a request you sent, we keep that it was cancelled for at least 7 days.
- Friends. If they say yes, we keep that you are friends and since when. Friends can see each other’s name, and when it was last changed. Being friends doesn’t let either of you see the other’s trips, bookings or anything else in Triplogue.
- Notifications. When someone asks to be your friend, or you become friends through their link, we send a notification to your phones with their first name, for example “Ana wants to travel with you”. It names no one else and says nothing more. You get at most one such notification about the same person in a week.
- Limits. To stop misuse, we limit how many friend links you make (10 a day), how many friend requests you send (30 a day, by link or by handle), how many handles you look up (60 a day) and how often you set or change your handle (3 times a day). For this we keep the times of these from the last 24 hours. Older times are removed the next time you do the same thing, or when you delete your account.
-
Trip cover photos. When a trip has no photo of yours, the app sends our server the trip’s city or country name, and our server asks Unsplash for a photo of it. We keep the place name and Unsplash’s answer for up to 30 days, so the next person going there gets the same photo without asking again. The photo itself loads from Unsplash.
-
Sign-in codes by email. If you sign in with your email address, it goes to our server, and our email provider sends you the code. To stop the code service being misused, we count requests per network for 2 days, keeping only a scrambled form of the network address.
-
Triplogue+, if you have it. What you bought (yearly, monthly or one trip), when it started and ends, whether it renews, a trial, a founding member’s place and golden tickets, which trip a trip pass is on, and invite rewards (including who joined through your link).
We don’t browse your data. We would open it only to fix a problem you report, or where the law requires it.
5. Gmail, Google Calendar and Google data
Gmail
- Separate choices. Continue with Google asks only for your Google account identifier, email address and name, so Triplogue can create or restore your account. It doesn’t give Triplogue your Gmail.
- What we ask for. After you sign in, Triplogue separately offers Connect Gmail. If you choose it, Google asks whether Triplogue may “read your email” (the
gmail.readonlypermission). Gmail is optional: you can forward a booking, add a file or screenshot, paste text, or type a booking instead. - What your phone does with it.
- It searches your Gmail for travel confirmations from the last 18 months. It looks at booking and airline senders and phrases such as “booking confirmation”, skips the Promotions and Social tabs and chats, and stops at 250 emails. When you start a trip with dates, it also searches the emails sent in the year before that trip, for bookings inside its dates.
- It reads each matching email’s subject and sender to tell a booking from a receipt, a host’s message, a review request or a newsletter. Only bookings become bookings; a cancellation removes the booking it cancels.
- Bookings from trips that are already over stay on your phone, unsaved, until you choose to bring that trip back in History.
- It opens only the emails that match. When an email’s text has no booking in it, it reads up to two PDF attachments.
- It picks out booking details with Triplogue’s own rules first. On iPhones with Apple Intelligence, Apple’s on-device model can help fill in a fixed booking form. The model has no tools and sees one email at a time. Triplogue keeps only values that appear in that email, and skips the model when an email contains text that tries to instruct it.
- What it keeps. The booking details it finds, such as flight, times, place, confirmation number and the names on the booking, and the barcode from a PDF ticket. It does not keep the email itself. PDFs are deleted from the phone as soon as they’ve been read.
- Maps. To show where a stay or restaurant found in Gmail is, your phone looks up its name and address in Apple Maps. Nothing else from the email is sent.
- Cover photos. When a trip found in Gmail has no photo of yours, your phone sends our server only the trip’s city or country name, to find its cover photo (Section 4, Trip cover photos). Nothing else from the email is sent.
- When it runs. When you connect Gmail, when you tap Check for new bookings in Me → Account, or once after you sign in on a new phone. It also checks up to 50 emails from the last 7 days when you open Triplogue or come back to it, at most once every 6 hours. These checks are free. It never runs while the app is closed.
- What never happens:
- Your email is never sent to our servers.
- We don’t use Gmail data for ads, we don’t sell it, and no person at Blacktop Social reads it.
- We don’t use it to train AI models, ours or anyone’s.
- The AI model on our server that reads shared links and AI trip plans never receives anything from your Gmail.
- What can reach our servers. Bookings found in Gmail stay on your phone unless they go on a shared trip: one you put there, or one a later check adds to a trip you shared or turned on Add my bookings for. Then its details go to our server so the people on that trip can see them (Section 4). On a shared trip, a place you pick from a Gmail booking for a cost goes with that cost. If you invite someone whose name Triplogue suggested from your bookings, their first name goes with the invite when you send it; an invite you haven’t sent keeps it on your phone. Otherwise, your backup keeps nothing found in Gmail, except your changes to a booking on a shared trip and who can see it (Section 4). If usage sharing is on, anonymous counts and timings from a Gmail check go to our analytics provider (Section 6), never the email or the booking.
Your calendar
- Add my trips to my calendar. Triplogue makes its own calendar named “Triplogue”, on your iPhone or in Google Calendar. It keeps one event per booking: the name, times, place, address, confirmation code and a link back to Triplogue. It writes nowhere else.
- On your iPhone, iOS syncs that calendar with the account it’s in, usually iCloud.
- With Google Calendar, Google asks once for two permissions together: to manage only the calendars Triplogue made (
calendar.app.created), and to see the events you own (calendar.events.owned.readonly). Triplogue reads your own events so it doesn’t add a booking that’s already in your calendar.
- Find bookings in my calendar. Your phone reads events in your own calendars, 18 months back and ahead, and adds the flights, trains and stays it finds. It reads your iPhone’s calendars if you allow it. It also reads your main Google calendar if you already allowed Google Calendar for Add my trips to my calendar. It never asks Google for anything new.
- Bookings found in your calendar follow the same rules as bookings found in Gmail: they stay on your phone and out of your backup, unless you put them on a shared trip.
- Your calendar settings stay on your phone.
Your Google access key stays in your iPhone’s Keychain on this phone. It is never sent to us.
To disconnect, go to Me → Account → Gmail → Disconnect. That stops any Gmail check, revokes Triplogue’s access at Google, deletes the key from your phone and clears Triplogue’s list of emails it has read. Gmail and Google Calendar access end together. Triplogue asks whether bookings found in Gmail that you never shared should stay or be removed; anything already on a shared trip stays there for the people on it. You can also remove Triplogue from your Google Account under Security → Your connections to third-party apps & services.
Triplogue’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Analytics
Share how you use Triplogue starts on. You can turn it off at any time in Me → Privacy, and Triplogue stops sending these events from then on.
While it’s on, Triplogue sends our analytics provider, PostHog, in the United States, short records of what happens in the app.
- Each one carries the event’s name and time, the app’s version and build, and a random identifier made for this installation of Triplogue.
- It doesn’t carry your Triplogue account, your Google account, your name or your email address. PostHog doesn’t build a profile of you from it, and Triplogue tells PostHog not to work out your location.
- PostHog receives your phone’s IP address with each event, as any server does. PostHog discards it and doesn’t keep it with the event.
- There is no session recording, and no automatic capture of your taps or screens.
The events cover:
- First run and sign-in: which steps you reached, how you signed in, whether you’re new or returning, and whether you connected Gmail and from which screen. That is the connection, not anything in your email.
- Gmail checks: two events, described below. They are the only events made from your Gmail.
- Adding bookings without Gmail: which way you added one (a file, a photo, a share, pasted text, a forwarded email or your iPhone calendar). For a file or text, also its kind, its page count, how many bookings and codes were found, and which reader found them. Also whether you saved it, your first booking and where it came from, and, for an upcoming trip, how many days until it starts and how long it is.
- Booking and trip actions: adding a time, answering a “check this booking” or “one trip or two” question, and removing a booking, with its kind.
- Daily use: one event on each day you open the app, saying whether you’re on a trip. Only a trip you made with its own dates, or a booking you added yourself, counts. Trips built from Gmail or your calendar don’t.
- Sharing and friends:
- invite and friend prompts shown or dismissed;
- invites made, opened and accepted, with your role;
- shared trips opened, and how many trips and bookings you added to one;
- friend links, requests and answers, setting a handle, and which People screen you opened.
- Places from links: the kind of link (TikTok, Instagram, YouTube, Maps or text), how many places were found, saved or new, how many came from each part of a post (such as its caption or the creator’s comment), how they were read, the kind of place, and whether the trip is shared.
- AI trip plans: how many days and places a plan had, how it was read, and whether it came from a ChatGPT link or copied text. Never the plan’s words.
- Calendar: which calendar you connected and, for your iPhone calendar, how many events Triplogue added, changed or removed in its own calendar.
- Triplogue+:
- which paywall you saw and the plan you picked;
- whether it had a trial or a founding price;
- whether a purchase or a restore went through;
- trial reminders and trip passes.
- Other features:
- saving a cost: whether it was an edit, how many people share it, whether guests are in it, and whether it was converted;
- opening a day’s map or the stats preview;
- Wrapped, with its year;
- sharing a trip card or a story.
Events about bookings, trips, places and calendar events are sent only for ones that didn’t come from Gmail or Google Calendar. When an event would count something that did, such as bookings you add to a shared trip, it’s sent without the count.
Gmail check analytics. Triplogue sends PostHog two events from a Gmail check:
- When a full check starts: only whether it continues one that was interrupted.
- When a check ends: anonymous counts and elapsed times:
- whether it was a full, recent or trip-specific check, and whether it used the quick pass;
- the time spent listing, fetching, reading text and PDFs, using Apple’s on-device model and saving, the time to the first result, and the time to finish;
- counts of messages, cached messages, PDFs and model reads;
- if the check stops, only
no-accessorfailed.
We use this only to make the Gmail reader faster, more reliable and better at reconnecting. It never includes your Google address, email text, sender, subject, message or thread ID, attachment, booking, trip, confirmation code, traveler, place, date, access key, account ID or an error message.
We use analytics only to understand and improve Triplogue. We don’t use it for ads, we don’t sell it, and we don’t combine it with information about you from anywhere else. PostHog keeps these events for up to 1 year.
7. Who we share it with
We do not sell personal information. We do not share it for advertising. We disclose it only to the providers and people below, when valid legal process requires it, to protect rights or safety, or as part of a merger, acquisition or sale of the business. Each provider acts on our instructions.
- The people on your shared trips see what Section 4 says they see, and nothing else.
- Supabase hosts your login, your Blacktop record, your backup, shared trips and their cost photos, forwarded emails waiting for your phone, the places found in shared links, and Triplogue+ records.
- PostHog receives the analytics events in Section 6, under a random identifier for this installation, never your account.
- Anthropic runs the Claude model our server uses to find places in links and AI trip plans you share. It receives only the text read for them (Section 4), not your account, email or bookings. Under Anthropic’s commercial terms, it doesn’t use this text to train its models, and it deletes it within 30 days unless its safety systems flag it or the law requires it to keep it longer.
- Cloudflare receives email sent to your Triplogue address and passes it straight to our server. Cloudflare’s own privacy policy covers its handling.
- Vercel hosts our website and the invite link pages.
- RevenueCat handles Triplogue+ purchases for us. It receives your App Store purchase records and your Triplogue account identifier.
- Apple:
- handles Sign in with Apple, and takes payment for Triplogue+;
- draws the maps in trip pages, finds places for you in Apple Maps, and opens Apple Maps when you tap an address;
- if you add your trips to your iPhone calendar, iOS syncs the Triplogue calendar with the account it’s in, usually iCloud;
- when you delete an account that uses Sign in with Apple, we send Apple a one-time code so it can revoke Triplogue’s access.
- Google handles Google sign-in and, if you connect them, Gmail and Google Calendar. Your phone talks to Google directly. Google’s own privacy policy covers that.
- YouTube. Triplogue uses YouTube API Services to find the places a YouTube video names. When you share one, your phone asks YouTube for its public title, description and channel, and for the comments under it, and keeps only the comments the video’s own channel wrote. Triplogue uses these words only to find places. If you’re signed in, they go to our server and to Anthropic for that (Section 4), and our server can ask YouTube for them itself. Triplogue doesn’t keep the description or the comments. A place you save keeps the video’s link, title and channel name. Triplogue never asks for access to your YouTube account. See the YouTube Terms of Service and the Google Privacy Policy.
- TikTok. When you share a TikTok link, your phone asks TikTok for that post’s public page, by its link, and for TikTok’s subtitles of the video. It never asks for the video or its sound.
- Venmo. Settle up opens Venmo with the payment filled in. Venmo’s terms and policies apply there.
- Resend sends the sign-in codes you ask for by email. It receives your email address and the code.
- Unsplash receives the name of a city or country from our server when a trip needs a cover photo, and a notice when that photo is shown. Your phone loads the photo from Unsplash.
- Expo delivers notifications about forwarded emails and friend requests. It receives your phone’s push token and the notification’s words, which can include the first name of the person who asked to be your friend.
- Instagram. When you share an Instagram link, your phone asks Instagram for that post’s public caption, by its link.
- ChatGPT. When you share a ChatGPT link with Triplogue+, your phone asks ChatGPT for that shared chat, by its link. Our server never opens it.
When you tap Share or Ask on a booking, iOS opens its share sheet. You choose the app and the words, and that app’s policies apply.
We are based in New York. If you use Triplogue from outside the United States, information you back up or share may be transferred to wherever our providers process it.
8. How long we keep it
- On your phone: until you delete it in the app or delete the app. Gmail PDFs are deleted right after they’re read. The list of emails from a Gmail check is deleted when the check finishes. Offline copies of trip pages expire after 7 days.
- Emails you forward: on our server until your phone reads them, 7 days at most.
- Push token: until you sign out or delete your account.
- Friend links: each works for 30 days. Making a sixth working link deletes your oldest one. After a link stops working, we delete it the next time anyone makes a friend link, or when you delete your account.
- Friend requests and friendships: until one of you says no, cancels the request or removes the other, or until either of you deletes their account.
- A “no” (declining or removing someone): 90 days. After that, we delete it the next time anyone makes a friend link.
- A cancelled request: 7 days. After that, we delete it the next time anyone makes a friend link.
- The times of your friend links and requests: those from the last 24 hours. Older ones are removed the next time you make a link or send a request.
- Your @handle: until you change it or delete your account. Your old handle is then free for anyone to choose.
- The times of your handle lookups and changes: those from the last 24 hours. Older ones are removed the next time you look up or change a handle.
- Analytics events: up to 1 year at PostHog (Section 6). Turning off Share how you use Triplogue stops new ones.
- Cover photo answers: 30 days.
- Places found in a shared link: up to 30 days, and only for public text our server fetched itself. Your counts of link and plan reads: for the current day and month.
- AI trip plans: the plan’s text isn’t kept. A plan you save stays in your backup until you remove it or delete your account.
- Cost photos on shared trips: until the cost, the trip or your account is deleted.
- Sign-in code request counts: 2 days, as a scrambled network address.
- Your backup, including your spending on trips only you are on: until you delete your account. Each change replaces the previous copy.
- Shared trips: until the trip is deleted, or you leave it or delete your account. What you added to a trip you leave stays on it for the others.
- Triplogue+ records: until you delete your account. Apple and RevenueCat keep their own purchase records.
- Your login: until you delete your account. If you also use another Blacktop Social app with the same login, the login stays for that app.
- After you delete your account: we keep a short record that a login was deleted: its identifier, that Triplogue asked, and when. It has no email address.
- Your email address may stay in Blacktop Social’s shared record if you use another Blacktop product, or if you agreed to receive our emails. That record is covered by the Blacktop Social Privacy Policy.
- Emails you send us are kept as long as needed to answer them and keep business records.
9. Delete your data
Delete your account: in the app, go to Me → Account → Delete account. This deletes:
- your backup, your Triplogue membership and your profile;
- what you added to shared trips: your bookings, ideas, votes, invites, costs with their notes, places, categories and photos, settle-ups and packing checks;
- forwarded emails waiting for you, your Triplogue address, your Venmo username, and your Triplogue+ records.
A trip you own passes to the traveler who joined it first. With no other traveler, it’s deleted. Triplogue also revokes Sign in with Apple, disconnects Gmail, and deletes your login unless another Blacktop Social app uses it. Trips on your phone stay until you delete them there too.
Deleting your account also deletes your friend links, your @handle, every friend request you sent or received, your friendships, every “no” you gave or got, and the times of your links, requests, lookups and handle changes. Your former friends stop seeing your name, and your handle is free for someone else to choose. To end one friendship or cancel a request without deleting your account, remove that person in the app.
Deleting your account doesn’t cancel a Triplogue+ subscription. Cancel it in your iPhone’s Settings → your name → Subscriptions.
If you can’t use the app, email legal@blacktop.social from the address on your account, with the subject “Delete my Triplogue account”. We’ll confirm the request came from you, then delete the same things.
Delete what’s on your phone:
- If you’re signed in, sign out first, or delete your account (above). Otherwise your backup can bring your trips back.
- Go to Me → Privacy → Delete what I added on this phone, then Delete. This removes the trips, bookings and tickets you added or imported, including those found in Gmail, plus your invites and your photos. It also removes your spending on trips only you are on, and the notes, places and photos kept on this phone for any cost.
- To remove everything, delete the app.
Disconnect Gmail: go to Me → Account → Gmail → Disconnect. Do this before you delete the app, because iOS can keep the access key after an app is removed. You can also remove Triplogue at myaccount.google.com → Security → Your connections to third-party apps & services.
Stop using Sign in with Apple: on your iPhone, go to Settings → your name → Sign in with Apple → Triplogue → Stop Using Apple ID.
You can also ask what we hold about you, ask for a copy, or ask us to correct it, at legal@blacktop.social. We won’t treat you differently for asking.
10. Children
Triplogue is not for children under 13. We don’t knowingly collect information from them. If you think a child has given us information, email legal@blacktop.social and we’ll delete it.
11. Security
- Your trips, codes and tickets are encrypted on your phone. The key is kept in your iPhone’s Keychain for this device only. Your sign-in and your Google access key are protected the same way.
- Connections to our servers and to Google use HTTPS.
- On our servers, database rules let only your signed-in account read or change your backup, and only the people on a trip read it. Only the travelers on a trip can open its cost photos. Forwarded emails can be read only by your signed-in phone.
- Your Triplogue address has 8 random characters, so it can’t practically be guessed.
- Anyone who can unlock your phone can open Triplogue and see your trips, so keep a passcode on it.
- No method of storage or transmission is perfectly secure, and we can’t promise absolute security.
- If you find a security problem, tell us at legal@blacktop.social.
12. Changes
We’ll update this page and its date when our practices change. If a change affects what Triplogue collects or where it goes, we’ll update this page before the change applies.
13. Contact
Questions, requests or complaints:
Blacktop Social LLC
606 Metropolitan Avenue, 6B, Brooklyn, NY 11211
legal@blacktop.social
Help with the app: support@blacktop.social
See also the Triplogue Terms and the Blacktop Social Privacy Policy.