TrekMap Privacy Policy

Effective date: October 1, 2026 Version: 2026-09-v2.0

TrekMap is operated by Soluvo LLC, a Florida limited liability company doing business as TrekMap ("TrekMap," "we," "us," or "our"). This Privacy Policy explains what information we collect when you use TrekMap, how we use and share it, how long we keep it, and the choices and rights you have.

It applies to the TrekMap website (trekmap.co), the TrekMap apps for iOS and Android, TrekMap hardware devices and their software, our emails, and our shop and waitlist (together, the "Services"). Your use of the Services is also governed by our Terms of Service.

#Quick summary

• Your map runs on location. Pins, trips and photo imports use precise location. We don't collect your device's location in the background.
• You choose who sees your travels: Public, Friends only, or Private — for your whole account and for each pin or trip.
• We use AI service providers to turn links, videos, screenshots, photos and — only if someone in a chat turns it on — chat messages into places and plans. They process that data for us and aren't allowed to train their AI models on it. We ask for your permission before your data goes to them.
• We don't sell your personal information and don't use it for targeted advertising. We may share statistics that don't identify you.
• Messages are stored on our servers so they sync across your devices. They aren't end-to-end encrypted.
• You're in control: download your data or delete your account anytime in Settings or at trekmap.co/delete-account.
• TrekMap is only for people 18 and older.

#1. Who we are and what this policy covers

Soluvo LLC is responsible for the personal information described in this policy. You can reach us using the details in Section 16.

This policy doesn't cover websites and services run by others that you reach through TrekMap — for example Google Flights, airlines and booking sites, Instagram, TikTok, YouTube, Pinterest, Apple, Google, or Kickstarter. Their own privacy policies apply.

#2. Information we collect

We collect information you give us, information created when you use TrekMap, and information from other sources. Many features are optional; if you don't provide some information, the features that need it won't work.

#2.1 Account and profile

• Your email address, username, display name, profile photo, banner, bio, and any social media handles you add (such as Instagram or TikTok).
• Sign-in information. Sign-in is handled by our authentication provider. If you use an email and password, we never see your password in readable form. If you sign in with Google or Apple, we receive your name, email address (or an Apple private relay address), profile photo if available, and an account identifier from that service.
• Your settings, such as language, theme, map preferences, notification choices and visibility choices.
• A record that you passed our age check and accepted our Terms and policies, with the date and version. We don't keep the birthdate you enter.

#2.2 Your map, trips and journal

• Places you pin (wishlist and visited): titles, notes, ratings, dates, categories, cover images, and whether you've starred or shared them.
• Trips and itineraries: stops, days, routes, departure airport, dates or planned length, trip stories and share links.
• Journals and scrapbook pages: photos, text, stickers and layouts.
• Your passport of visited countries and regions, plus badges, challenges, discovery score, and year-in-review summaries.
• Breadcrumbs: private check-ins you drop while traveling — a short note, the place, coordinates, time, and an optional photo.
• Trip expenses and bookings you add: amounts, currency, category, who paid and how costs are split; booking type, provider, dates, confirmation codes, notes and attachments. Please don't upload passports or other identity documents.
• Dates you add, such as time off, availability, birthdays or anniversaries, which we use for trip and deal suggestions.

#2.3 Location information

TrekMap is a map, so location is at the center of how it works.

• Places you add. Every pin has precise coordinates (latitude and longitude) and the city, region and country.
• Location and time saved in your photos. When you choose photos or an album to build a trip or add to a pin, TrekMap reads the location and date/time stored in each photo's metadata. For album imports, the app reads this on your device and sends us the coordinates and times — not the photos — so we can group them into stops and name the places. A photo is uploaded only if you add it to a trip, pin or journal.
• Google Takeout and location-history files. If you upload a Google Takeout export, we read the location and date information in its photo information files, and in any location-history files you include, to rebuild your trips. We don't keep the uploaded export after processing it.
• Google Photos. Google doesn't give apps the location of photos picked from Google Photos. For those photos we use the date and, if you've allowed AI features, what's in the image to suggest where it was taken (Section 12).
• Your device's location. If you allow it, TrekMap uses your device's location while you're using the app — to center the map, show nearby deals, and drop a breadcrumb where you are. We don't collect your device's location in the background.
• Trip Mode. If you start Trip Mode, the app periodically checks for new photos you take during that trip and reads their location and time, until you end the trip. It doesn't use your device's GPS in the background.
• Approximate location from your IP address. Our servers estimate your city, region and country from your IP address for security, preventing abuse, and understanding where people use TrekMap.
• Places in content you share with us, such as a video filmed at a waterfall (Section 2.5).

Location information can be sensitive. Photos can reveal where you live, work or spend time, and where other people have been. Use Friends only, Private, or Approximate location for places you don't want to share (Section 6).

#2.4 Photos and videos

Photos and videos you upload to pins, trips, journals or your profile, with details such as file type, size, dimensions, capture date and camera make. Before we show your photos to other people, we remove location metadata embedded in the files. We don't use facial recognition.

#2.5 Content you share from other apps and websites

When you share or paste a link to a post (for example from Instagram, TikTok, YouTube, Pinterest, or a website), or upload a screenshot or a photo of something like a newspaper or magazine article, we analyze that item to find the places in it. Depending on the item, this can include:

• the link, caption, title, hashtags, and the creator's name or handle;
• images, video frames, and text that appears on screen;
• the audio track, which we convert to text;
• a limited number of the post's public comments.

The results wait in your share inbox for you to review. For public posts, we may reuse a completed analysis when someone else shares the same post, so it isn't processed twice — your own edits, choices and saved pins are never shared this way.

To analyze a public post we may temporarily download its media, and we delete those copies after processing. Pins created from a post keep a link to the original and credit the creator. When a saved post is viewed in TrekMap, it's shown or played from the original platform, so if the creator deletes it or makes it private, it stops appearing in TrekMap.

We only analyze items you choose to share with us. We don't access your social media accounts or read your feeds. If you report that a place was detected incorrectly, we keep the details of that analysis to fix the problem.

#2.6 Friends, social features and messages

• Friends ("mates"): friend requests and connections, invitations, and referral links you send or use.
• Interactions: likes, votes, comments, companion tags ("you were here"), pins you collaborate on, trips you join or are invited to, trip proposals and votes, challenges, and travel-twin matches (which compare your wishlist, visited places and available dates with your friends').
• Messages: the content of direct messages and group or trip chats — text, emoji reactions, shared pins and trips, and votes on shared places — plus who sent them, when, and whether they've been read.
• Blocks and reports you make, or that involve you.

Messages are stored on our servers so they sync across your devices. They aren't end-to-end encrypted. We don't look at your messages except (a) when a member of the chat reports them, (b) when needed to investigate safety, security or legal issues, (c) when the law requires it, or (d) when the AI trip planner is turned on for that chat, in which case messages are processed by automated systems as described in Section 4.

#2.7 Finding friends from your contacts (optional)

If you choose to find friends from your contacts, the app reads the phone numbers in your device's contacts, converts each one into a coded value (a "hash") on your device, and sends only those hashes to our servers to check which belong to TrekMap users. We use them only for that check and don't store them. Hashes can sometimes be reversed, so we treat them as personal information.

If you add your own phone number, we store it (and its hash) so friends who have your number can find you. You can remove it anytime.

#2.8 AI trip planner and travel profile

When you use the AI trip planner (as it becomes available), we collect:

• Your travel profile: your answers to optional questions about how you like to travel, such as pace, interests, budget range and trip style.
• Planner conversations: what you ask the planner, what it suggests, and your feedback.
• Chat messages, only when the planner is turned on for a chat. Any member of a chat can turn the planner on. While it's on, it can read that chat's messages — including messages sent before it was turned on — to understand the group's plans. Everyone in the chat can see that it's on, and anyone in the chat can turn it off. If you've turned AI features off, or opted out of the planner in that chat, your messages aren't sent to the AI provider.
• Your trips, pins, wishlist, visited places and travel preferences, to personalize suggestions.

#2.9 Flights, deals and travel preferences

• Home airports, preferred airlines, loyalty and points programs, trip-style preference, and — if you add it — your passport country, which we use only to show visa and entry information. Passport country can indicate citizenship, which some laws treat as sensitive. You can remove it anytime.
• Flight searches, deal watches, price alerts and alert thresholds.
• Flight clicks. When you tap to view or book a flight, we record the route, dates, price shown, airline, number of stops, deal rating, where in TrekMap you tapped, the website we sent you to (for example "google.com"), and how many of your wishlist pins are near that destination. We don't record the full link or anything you do on the other website. We may later ask whether you booked the flight; answering is optional and your answer is recorded as self-reported.
• If you connect a seats.aero account: an access key or token for that account, stored encrypted.

To look up prices we send flight data sources the route and dates — not who you are.

#2.10 TrekMap devices

If you set up a TrekMap device (such as TrekMap Mini), we collect a hardware identifier derived from the device, its model, pairing codes and tokens (stored in hashed form), the name and display settings you choose, what content it shows, when it last checked in, and its IP address. Wi-Fi setup happens directly between your phone and the device, and we don't receive your Wi-Fi password. Actions you take on the device, such as "Send to app," are linked to your account.

#2.11 Shop, waitlist and Kickstarter

• Waitlist and newsletter signups: your email address, where you signed up, and your cart subtotal if you signed up at checkout.
• Kickstarter backers: Kickstarter collects pledge and payment information under its own privacy policy. We receive what we need to deliver rewards — such as your name, email address, shipping address, phone number and reward choices — directly or through a backer survey tool.
• Future purchases: if we sell products directly, a payment processor (such as Stripe) will handle your card details and we won't store full card numbers. We'll collect order, shipping and support details.

#2.12 Communications and support

Emails and messages you send us, bug reports and feedback (including the device, app version and screen you were using), survey answers, and records of our replies.

#2.13 Usage, device and diagnostic information

• Log data: IP address, date and time, pages or features requested, browser or app version, device type, operating system, referring page, and approximate location from your IP address.
• Product usage (analytics): app opens, sessions and time spent, screens viewed, features used, taps such as "book flight," and how usage changes over time (for example, whether people come back in their first week). We use this to improve TrekMap and understand how it's growing.
• Crash and performance data: error details, device and app state at the time of an error, and performance measurements, collected through our error-monitoring provider. On the website, if an error happens we may capture a replay of the page with all text masked and images blocked.
• Device identifiers and push notification tokens, used to deliver notifications and diagnose problems.
• Cookies and similar technologies (Section 8).

#2.14 Information from other sources

• Other users, for example when a friend tags you, adds you to a trip, invites you, sends you a message, or has your phone number in their contacts.
• Sign-in and connected services: Google, Apple, Google Photos (only the photos you pick), and seats.aero.
• Public and licensed sources: public posts you share with us; place information (such as Google Places and OpenStreetMap); images from Wikimedia Commons and Openverse; visa, country and transit data.
• App stores: where the law requires it, Apple or Google may tell us whether a user meets an age requirement.

#3. How we use information

We use information to:

• Provide TrekMap: create and secure your account; show your map, pins, trips, journal and passport; sync across your devices and TrekMap devices; send notifications you've asked for.
• Build places and trips for you: read photo locations and dates, group them into stops, look up place names, analyze content you share, and create pins, routes and trip stories.
• Personalize: suggest places, trips and deals based on your wishlist, visited places, preferences, travel profile and activity; show memories and travel-twin matches.
• Run social features: show your content to the audience you choose; deliver messages, comments, likes and invitations; help you find friends and plan trips together.
• Power AI features as described in Section 4.
• Flights and deals: find fares, rate deals, send alerts, and use flight clicks and optional follow-up answers to learn whether our flight suggestions are useful.
• Communicate with you: account, security and legal notices; replies to support requests; and — unless you opt out — product updates and our weekly digest.
• Keep TrekMap safe: check age eligibility; prevent spam, fraud and abuse; enforce our Terms and Community Guidelines; review reports; protect our systems.
• Improve and measure TrekMap: analytics, debugging, testing new features, measuring AI quality and cost, and producing aggregated statistics.
• Meet legal obligations and establish, exercise or defend legal claims.
• Do other things with your consent or at your direction.

We don't use your personal information for targeted advertising, and our apps and website don't include advertising SDKs or use advertising identifiers.

Automated processing. We use automated systems to detect places, build trip stories, rank suggestions, rate deals, and temporarily hide content that several people have reported. None of these systems make decisions that have legal or similarly significant effects on you. You can ask us to review any moderation decision — see Section 12 of our Terms of Service.

#4. AI features

#4.1 Which features use AI

• Finding places in links, videos, photos, screenshots and articles you share (Section 2.5).
• Suggesting where photos were taken when they don't include a location, and naming stops in rebuilt trips.
• Writing suggested notes, descriptions and trip stories.
• The AI travel agent and AI trip planner, including chat messages when the planner is turned on for a chat (Section 2.8).
• Search that understands meaning (for example, matching "waterfalls near Lisbon" to relevant pins).

#4.2 Who processes it

We send the data needed for each request to AI service providers that process it on our behalf (see Appendix 1). They may process data in the United States or other countries. By contract and through the settings we use, they aren't allowed to use your data to train their AI models. Some providers keep inputs for a short time — typically up to 30 days — to monitor for abuse and security issues, unless we've arranged for them not to keep it.

#4.3 Your permission

We ask for your permission before your personal data is sent to a third-party AI provider for the first time. You can turn AI features off anytime in Settings → Privacy & Safety → AI & Personalization; features that depend on AI will then stop working, and you can still add places manually. The AI trip planner never reads a chat unless someone in that chat turns it on, and it never sends your messages if you've turned AI features off or opted out of the planner in that chat.

#4.4 Accuracy

AI can be wrong. It can put a pin in the wrong place, invent details, or rely on outdated information. Pins created with AI are marked until you confirm them. Always check important details — especially anything about safety, entry requirements, prices, opening hours or accessibility — with official sources. Our Terms of Service say more.

#4.5 Our own use of data for AI

We don't use your private content — such as messages, private photos, private pins or your travel profile — to train AI models. We may use de-identified or aggregated information, public content, and reports you send us about wrong results to improve how our features work (for example, testing whether a change finds places more accurately).

#5. How we share information

#5.1 With other people, based on your choices

Your account visibility and the audience you pick for each pin or trip decide who can see them:

• Public: anyone, including people without a TrekMap account — on Explore, on your profile page (trekmap.co/u/yourname), and in search engine results.
• Friends only: people you've accepted as friends.
• Private: only you, plus the people you add to a specific trip or chat.

Some information is visible to others whatever your settings:

• Your username, display name and profile photo, when you message someone, comment, send a friend request or join a trip — and when someone looks up your exact username to send you a friend request.
• Comments you leave on someone else's content, which are visible to that content's audience.
• Messages, which everyone in the chat can see.
• Trip details — including expenses and bookings added to that trip — which the trip's participants can see.
• Companion tags, which appear on the tagged pin.
• If you add your phone number, people who have it in their contacts can find that you're on TrekMap.

If you turn on Approximate location for a pin, other people see a location within about 1–2 km of it. People who can see your content can screenshot or share it, and we can't control that.

#5.2 With service providers

We use companies that help us run TrekMap — for hosting and storage, sign-in, email, error monitoring, AI processing, maps and place information, flight data, and notifications. They may access personal information only to perform services for us, under contracts that require them to protect it and not use it for their own purposes. Appendix 1 lists our current providers.

#5.3 With services you choose to use

• Booking and travel websites. When you tap a flight or other travel link, you leave TrekMap. That site receives the information your browser normally sends (such as your IP address). We don't send it your name or contact details.
• Posts from other platforms. When you view or play a post saved from Instagram, TikTok, YouTube or another platform, it loads from that platform, which may collect information about you under its own policies.
• Connected accounts. When you sign in with Google or Apple, or connect Google Photos or seats.aero, information passes between TrekMap and that service as described in this policy and the service's own policy.
• Maps. Map images load from map providers (Apple Maps on iOS; OpenStreetMap-based tile providers elsewhere), which receive your IP address and the map area you're viewing.
• Affiliate partners. Some links to hotels, car rentals, tours or other travel services are affiliate links. If you book through one, the partner can tell you came from TrekMap and may pay us a commission. We don't give them your name or contact details.

#5.4 For legal, safety and protection reasons

We may disclose information if we believe in good faith it's needed to comply with law or valid legal process; to protect anyone from death or serious harm; to protect the rights, property or safety of TrekMap, our users or the public; to prevent fraud or abuse; or to enforce our Terms. Where federal law requires, we report apparent child sexual exploitation to the National Center for Missing & Exploited Children (NCMEC).

#5.5 In a business transfer

If Soluvo LLC or TrekMap is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that deal. The recipient must keep honoring this policy for information collected under it, or ask for your consent.

#5.6 Aggregated or de-identified information

We may share statistics that don't identify you — for example, with airlines, travel companies or potential partners: how many flight clicks a route receives, or what share of users return after a month. We take reasonable steps so this information can't be linked back to you, we don't try to re-identify it, and we require anyone we give it to not to try either.

#5.7 With your consent

We may share information for other purposes when you ask us to or agree to it.

We don't sell your personal information, and we don't share it for cross-context behavioral (targeted) advertising — and we haven't in the past 12 months. That includes precise location. If we ever wanted to change this, we'd update this policy first, ask for your consent where the law requires, and never apply the change to information collected before it without your consent.

#6. Your choices and controls

Do Not Track and Global Privacy Control. Our websites don't respond differently to browser "Do Not Track" signals, because we don't track you across other companies' websites and don't sell or share personal information for advertising. If your browser sends a Global Privacy Control signal, we treat it as a request to opt out of any sale or sharing and turn off optional analytics cookies in that browser.

#7. Your privacy rights

Wherever you live in the United States, you can ask us to:

• Access the personal information we have about you and get details about how we use it;
• Correct inaccurate information;
• Delete your personal information;
• Get a copy in a portable format;
• Withdraw consent you've given (such as for AI features or contacts matching);
• Opt out of the sale or sharing of personal information, targeted advertising, and profiling that has legal or similarly significant effects — which we don't do;
• Appeal a decision we make about your request.

Several states give their residents these rights by law (for example California, Colorado, Connecticut, Oregon, Texas and Virginia). We offer them to all users. We won't treat you differently for using them.

How to make a request. Use Download my data or Delete account in Settings, or email support@trekmap.co from the address on your account. We'll verify your request, usually by confirming you control that account or email address, and we may ask for more information when needed. You can use an authorized agent; we'll ask for proof of their authority and may confirm your identity with you directly.

Timing. We'll respond within 45 days. If we need more time (up to another 45 days), we'll tell you why.

Appeals. If we decline your request, reply to our decision or email support@trekmap.co with "Appeal" in the subject line. We'll respond within 45 days. If you're unhappy with the outcome, you can contact your state's Attorney General.

Sensitive information. Some of what we collect can be "sensitive" under state laws: precise location, the contents of your messages, your account login, and your passport country (which may indicate citizenship). We use sensitive information only to provide the features you ask for, keep TrekMap secure, and comply with law — with your consent where required — and not to infer characteristics about you. We don't sell it.

California "Shine the Light." We don't disclose personal information to third parties for their own direct marketing.

#8. Cookies and similar technologies

We don't use advertising cookies or cross-site tracking.

#9. How long we keep information

We keep information for as long as we need it for the purposes in this policy, then delete or de-identify it.

When you delete your account, we remove your account and content from our active systems right away and delete your stored files within 30 days. Copies in backups are overwritten within 35 days. Content others already copied or shared outside TrekMap isn't affected. We may keep limited information longer when we need it to comply with law, resolve disputes, prevent fraud or abuse (for example, to stop a suspended user from rejoining), or enforce our agreements, and statistics that no longer identify you.

#10. How we protect information

We use administrative, technical and physical safeguards designed to protect your information, including encryption in transit (HTTPS), encryption at rest provided by our hosting providers, hashed pairing tokens, encrypted tokens for connected accounts, limiting access to people who need it for their work, and monitoring for errors and abuse. We require our service providers to protect information too.

No system is perfectly secure, and messages aren't end-to-end encrypted. If a breach affects your personal information, we'll notify you and the authorities as the law requires. You can help by keeping your sign-in secure. To report a security vulnerability, email support@trekmap.co.

#11. Children and teens

TrekMap is only for people 18 and older. The Services aren't directed to children, and we don't knowingly collect personal information from anyone under 18. We use an age check when you sign up and, where available, age information from app stores. If we learn that someone under 18 has an account, we'll delete the account and its information. If you believe someone under 18 is using TrekMap, contact support@trekmap.co.

#12. Google user data

• Sign in with Google. We receive your name, email address, profile photo and Google account ID, and use them only to create, identify and secure your TrekMap account.
• Google Photos. When you choose to import from Google Photos, we access only the photos and videos you select in Google's picker, with basic details Google provides (such as file name, type, capture time and camera). We use them only to build your trips and pins. We download the selected items to process them and keep only the photos you add to trips or pins. Google Photos access is temporary and expires. If you've allowed AI features, selected photos may be sent to our AI providers to suggest where they were taken.
• We don't use data from Google APIs for advertising, don't sell it, don't use it to train general-purpose AI models, and don't let people read it except with your permission, for security or legal reasons, or in aggregated, anonymized form for internal operations.
• TrekMap's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
• The use of information received from Photos APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
• You can remove TrekMap's access to your Google account anytime at https://myaccount.google.com/permissions.
• Some features use Google Maps Platform services. Your use of them is also subject to the Google Privacy Policy.

#13. TrekMap on iOS, Android and the web

This policy covers all versions of TrekMap. The apps ask your permission before using these device features, and you can change them anytime in your device settings:

We don't use Apple's advertising identifier or ask to track you across other companies' apps, and our Android app doesn't use the Android advertising ID.

#14. International users

TrekMap is based in the United States, and our service providers may process information in the United States and other countries where they operate. Privacy laws there may differ from those where you live.

If you're in the European Economic Area, the United Kingdom or Switzerland, Soluvo LLC is the controller of your personal information, and we rely on these legal bases:

You have the right to access, correct, delete, restrict, or receive a portable copy of your information; to object to processing based on legitimate interests and to direct marketing; to withdraw consent; and to complain to your local data protection authority. When we transfer your information outside your region, we use safeguards such as the European Commission's Standard Contractual Clauses.

#15. Changes to this policy

We'll update this policy as TrekMap changes. The effective date at the top shows when it last changed, and previous versions are available at trekmap.co/legal. If we make a material change, we'll tell you by email or in the app at least 30 days before it takes effect and, where required, ask for your consent. We won't apply a change that reduces your protections to information collected before the change without your consent.

#16. Contact us

Soluvo LLC (TrekMap) [Mailing address pending]

• Privacy questions and requests, safety concerns, security reports, and everything else: support@trekmap.co
• Legal and copyright notices: contact@trekmap.co

#Appendix 1 — Our service providers

Current as of October 1, 2026.

Kickstarter (and, in the future, a payment processor such as Stripe) handles pledges and payments under its own privacy policy.

#Appendix 2 — Categories of personal information

This table summarizes, using the categories US state privacy laws use, the personal information we've collected in the past 12 months. We haven't sold or shared (for targeted advertising) any of it. Section 9 explains how long we keep it.

We don't collect biometric information, professional or employment information, or education information.