Treka English EN
Legal
Privacy Policy
Effective May 5, 2025 · Last updated October 17, 2026
Jump to section
1.Overview
Treka LLC ("Treka," "we," "our," or "us") respects your privacy and is committed to protecting your personal information. This Privacy Policy describes how we collect, use, share, and protect data when you access or use Treka's website, mobile app, or related services (collectively, the "Platform"). By using Treka's Platform, you acknowledge and agree to the terms of this Privacy Policy. If you do not agree, please do not use our services.
2.Information We Collect
We collect several types of information to provide and improve our services. This includes:
A. Information You Provide
- Personal Identifiers: Name, email address, phone number, and home base or location.
- Profile Details: Profile photos, bios, and other information you add to your user or guide profile.
- Verification & Payment: Identity verification details (e.g. IDs) and payment information needed for bookings or payouts.
- Professional Info (Guides): Certifications, training, and experience (for guides), as well as any gear rental listings or trip details you submit.
B. Information Collected Automatically
- Device & Usage Data: Device type, browser type, operating system, and unique device identifiers. We also collect usage data such as pages or screens viewed, features used, links clicked, and the dates/times of your interactions.
- IP Address & Geolocation: Your IP address and approximate location may be collected for security and localization (e.g. showing relevant guides or regulations for your region).
- Cookies & Similar Technologies: We use cookies and session IDs to remember your preferences, keep you logged in, and track aggregate usage of the Platform.
- Visit Source (Operator Websites & Booking Widget): When you visit an operator's Treka website or open their booking widget, we record how you arrived: the referring site's scheme and domain (for example https://l.instagram.com — never the rest of its address; for treka.app pages, the page path without its query), any campaign tags in the link (utm_source, utm_medium, utm_campaign), which kind of ad-click identifier the link carried (for example "fbclid" — for these visit statistics, never its value), the page you landed on, a random per-visit session ID kept in your browser for the visit, and your browser's user agent. The operator sees this only as totals (for example, visits and bookings from Instagram) in their Analytics; we use no third-party tracker for it.
- Treka Ads Attribution: When you arrive from an ad or a promoted listing, the campaign tags and the ad-click identifier itself (for example the gclid or fbclid value) are kept in your browser for up to 30 days and, if you book, stored with your booking, so the operator's ad campaign can be credited for it.
C. Information from Third Parties
- Social Login Data: If you choose to register or log in via third-party platforms (such as Google, Apple, or Facebook), we receive information like your name and email from those providers.
- Payment Processors: For transactions, our payment partners provide us with confirmation of payment and limited information needed to link your payment to your account.
- Verification Services: If we use external services to perform background checks or verify guide certifications, we may receive verification results or status.
- Insurance Partners: If you opt to purchase insurance through Treka's Platform, we may collect or receive necessary information to facilitate obtaining coverage from the third-party insurance provider.
3.How We Use Your Information
We use the collected information for the following purposes:
- Provide and Improve Services: To operate Treka's Platform, create your account, allow you to find and book guides or list guiding services, and improve overall user experience. This includes using data to personalize content and optimize our user interface.
- Facilitate Bookings & Transactions: To enable communications and bookings between adventurers and guides, process payments for trips or gear rentals, and provide related customer support.
- Verification and Safety: To verify user identities and qualifications (for guides), screen for fraud, security, or illegal activity, and enforce our Terms of Service.
- Communication: To communicate with you about your account or transactions (e.g. booking confirmations, updates, and support messages). We may also send marketing or promotional communications about new features, deals, or events if you have opted in. You can unsubscribe from marketing emails at any time.
- Analytics: To analyze usage trends and user preferences in order to improve our Platform.
- Cookies: To remember your settings and preferences (so you don't have to re-enter information) and to authenticate your sessions.
Importantly, Treka does not sell your personal information to third parties for their own marketing or profit. All usage of data is solely to serve you and improve our Platform or as described in this Policy.
4.How We Share Your Information
We value your privacy and share personal information only as necessary to run our services or as required by law. Situations where we share data include:
- With Other Users (Guides and Adventurers): When you make a booking or inquiry, we share relevant information with the involved parties. For example, if an adventurer books a trip, the guide will receive the adventurer's name and contact information to coordinate, and vice versa.
- With Service Providers: We share information with trusted third-party service providers who help us operate the Platform. This includes payment processors, hosting and cloud storage providers, analytics services, customer support tools, and email/SMS providers.
- With Insurance Partner: If you choose to purchase insurance through our Platform for a guided activity, we will share the necessary personal information with the third-party insurance provider to facilitate coverage.
- For Legal Compliance: We may disclose information to courts, law enforcement, regulators, or other authorities if we believe in good faith that it is required by law or necessary to protect Treka or others.
5.Google User Data (Gmail and Google Calendar)
This section explains exactly what Treka does with data from your Google account. It applies only if you choose to connect Gmail or Google Calendar to Treka. Connecting is optional: you start it yourself from the Connections page of the Treka portal, Google shows you the permissions on its own consent screen, and nothing is accessed unless you approve them. We only request the permissions listed below.
A. The Google data we access
- Your Google account email address (Google permissions
openid and userinfo.email): so we can show which Google account is connected, send email from that address, and use it as the reply-to address on booking emails Treka sends for your business, so guests' replies reach you.
- Send email on your behalf (Gmail permission
gmail.send): Treka can send an email from your Gmail address. It cannot read, search, delete or change anything in your mailbox.
- See your calendar events (Google Calendar permission
calendar.readonly): the title, time and status of events on the calendars you connect.
- Create and change events (Google Calendar permission
calendar.events): add, update and remove the events that Treka creates for your bookings and schedule.
B. How we use it
- Gmail: when you write an email in Treka (for example a check-in to a past customer) and press Send, Treka sends that one message from your Gmail address. Treka never sends an email you did not write and send, and never reads your inbox.
- Google Calendar: Treka shows your existing Google events on your Treka calendar, next to your trips, so you can see conflicts before you schedule or accept a booking. When you press Push to Google, or a booking is confirmed, Treka adds the event for that booking or departure to your calendar and keeps it up to date. Treka never edits or deletes events you created yourself. If you use a Treka meeting booking page, Treka checks your free and busy times so it only offers open slots, and adds the booked meeting to your calendar.
We use Google user data only to provide these features to you, the person who connected the account. We do not use it for any other purpose.
C. What we store and for how long
- Access and refresh tokens that Google issues when you connect. They are what lets Treka act for you, and they are kept until you disconnect.
- Your Google account email address, kept until you disconnect.
- A record of emails you send through Gmail from Treka (recipient, subject, the message you wrote, and Gmail's message and thread ID), so the email shows up in your Treka account. Kept until you disconnect Gmail or delete your account.
- The Google event ID of meetings booked through a Treka meeting page, so Treka can update or cancel that event later. Kept with the meeting record.
We do not store the contents of your Google calendar: events from your calendar are fetched when you open the Treka calendar, shown to you, and not saved. We do not read or store emails in your Gmail inbox.
D. Who we share it with
We do not sell Google user data, and we do not share or transfer it to anyone except:
- Our hosting providers, which store and process it on our behalf and only to run Treka: Supabase (our database and servers) and Vercel (our website).
- Google itself, when Treka sends your email or writes your calendar events through Google's APIs.
- When the law requires it, or to protect the safety and security of our users, as described in section 4.
We do not send Google user data to artificial intelligence providers, and it is not available to AI assistants you connect to Treka (section 8). Google user data is not used for advertising, is not sold to data brokers or information resellers, and is not used to decide creditworthiness or for lending.
Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models. We do not use any Google user data to train artificial intelligence or machine learning models.
E. How we protect it
- All data travels between your browser, our servers and Google over encrypted HTTPS.
- Google data is stored in our database, which is encrypted at rest. Google tokens can only be read by Treka's servers: they are never sent to your browser or shown to anyone, including people in your own Treka account.
- Database access rules mean only the people you have given access to your Treka account (for Gmail, your company's owners and admins; for Google Calendar, you) can see the Google features you connected.
- Treka staff do not read your Google data, except with your permission to help with a support request, when needed for security or to investigate abuse, or to comply with the law.
F. Deleting your Google data
- Disconnect in Treka: on the Connections page of the Treka portal, click Disconnect on the Gmail or Google Calendar card. Treka immediately revokes its access at Google and deletes the stored tokens. Disconnecting Gmail also deletes your connected email address and the records of emails sent through Gmail. Choosing Outlook for your email instead (section 6) also deletes the Gmail tokens and records; Treka revokes its access at Google too, unless Google Calendar is still connected in Treka (Google ends both together), in which case you can remove it at myaccount.google.com/permissions once you no longer need it.
- Remove access at Google: you can also remove Treka at any time from myaccount.google.com/permissions. Treka can then no longer use your Google account; disconnect in Treka as well to delete what we stored.
- Ask us: email support@treka.app and we will delete your Google data within 30 days. Deleting your Treka account deletes it too.
G. Google API Services User Data Policy
Treka'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.
6.Microsoft User Data (Outlook Mail and Calendar)
This section explains exactly what Treka does with data from your Microsoft account. It applies only if a company owner or admin chooses to connect Outlook to Treka, with a work or school account or a personal Microsoft account (such as Outlook.com or Hotmail), or if a member of a company's team connects their own Outlook calendar (see "Your own Outlook calendar" below). Connecting is optional: you start it yourself from the Connections or Calendar page of the Treka portal, Microsoft shows you the permissions on its own consent screen, and nothing is accessed unless you approve them. We request only the permissions listed below.
A. The Microsoft data we access
- Sign-in and your account's address and name (Microsoft permissions
openid, email and profile): so you can sign in with Microsoft to connect, and so we can show which account is connected.
- Access while you are away (
offline_access): lets Treka keep acting for you after you close Treka, for example to add a booking to your calendar the moment it is confirmed.
- Your basic profile (Microsoft Graph permission
User.Read): your Microsoft account ID, email address and display name, to identify the connected mailbox and calendar.
- Send email as you (
Mail.Send): Treka can send an email from your Outlook address. On its own this permission cannot read, search, delete or change anything in your mailbox.
- Your mailbox, only if you use Outlook for email (
Mail.ReadWrite): requested when your company chooses Outlook as its email provider, for the Email Center (you can instead connect for sending only, without it). Treka reads the messages in the Inbox and Sent Items of the connected mailbox: the whole Inbox, not only guest emails. It reads each message's sender, recipients, subject, date, read state and text; it does not read attachments. The only changes Treka makes in the mailbox are marking a message as read when you open it in Treka and sending the replies you write (and, only if your company turns on the Email Center AI assistant described in B, the messages it sends as set out there). It never deletes, moves or edits your mail.
- A shared mailbox, only if you choose one (
Mail.ReadWrite.Shared and Mail.Send.Shared): requested only when the person who connected Outlook chooses a shared mailbox (such as info@ or bookings@) for the Email Center, and only works for a shared mailbox their account already has access and Send As rights on in Microsoft 365. Treka then reads that shared mailbox's Inbox and Sent Items as described above and, when you press Send on a reply you wrote (or the optional Email Center AI assistant sends a message as described in B), sends that one message as the shared address. Treka cannot give anyone access to a mailbox or Send As rights; your Microsoft 365 administrator sets those.
- Your calendar (
Calendars.ReadWrite): see the title, time, location and link of the events on your Outlook calendar, and create, update and delete the events Treka itself creates for your bookings and departures. The same permission lets Treka list the calendars your account can edit (your own, and team calendars someone shared with you with edit rights), so you can choose which one Treka uses.
- A shared mailbox's calendar, only if you choose one (
Calendars.ReadWrite.Shared): requested only when the person who connected Outlook chooses the calendar of a shared mailbox (such as bookings@) for your company's departures, and only works for a calendar their account already has access to in Microsoft 365. Treka then lists that mailbox's calendars and creates, updates and deletes the events Treka itself creates there, exactly as on your own calendar. Connections that never choose a shared mailbox's calendar are not asked for it.
- Your own Outlook calendar, as a team member (
openid, email, profile, offline_access, User.Read and Calendars.ReadWrite, and nothing else): a guide or anyone on a company's team can connect their own Outlook calendar from the Calendar page so the departures they are assigned to appear on it. This separate sign-in never includes any mail permission: Treka cannot read or send your email through it.
B. How we use it
- Outlook Mail (send only): when you write an email in Treka (for example a check-in to a past customer) and press Send, Treka sends that one message from your Outlook address. Apart from the optional Email Center AI assistant below, Treka never sends an email you did not write and send. Your connected address may also be used as the reply-to address on booking emails Treka sends for your business, so guests' replies reach you.
- Email Center (Outlook email only): when your company uses Outlook for email, Treka shows the mail in the connected mailbox (or the chosen shared mailbox) in the Email Center, so your team can read and answer it in Treka. Treka groups it into conversations, links a conversation to the matching booking or guest (from a booking number in the email, or the sender's address), and raises one Action Center alert per conversation from a known guest, which clears once someone replies. That alert holds only a neutral title, the guest's name and address and the booking: never the email's subject or text. To learn about new mail quickly, Treka asks Microsoft to notify it when a message arrives in the Inbox (a Microsoft Graph subscription that Treka renews every few days) and also checks for new mail every 30 minutes; read/unread changes and messages you delete in Outlook are reflected on the next check. Replies you write go out from that mailbox, or as the shared mailbox when one is chosen (only when you press Send). Unless your company turns on the Email Center AI assistant (next item), Treka never sends anything you did not write, and nothing is drafted, sorted or answered automatically. Gmail is never read: a company that uses Gmail keeps the send-only access described in section 5, and has no inbox in Treka.
- Email Center AI assistant (optional, off unless your company turns it on): an owner or admin of a company that uses Outlook for email can turn on an AI assistant in the Email Center, after a screen that explains what follows and asks them to agree; Treka records who turned it on and when. While it is on, and only for conversations with a guest (the person writing must be the guest on the booking the conversation is linked to, or the guest it was linked to by hand; mail from the company's own addresses, Treka's notifications and no-reply or other automated senders is excluded), Treka sends the content of the relevant Outlook messages (the text of the recent messages in that conversation, with quoted earlier messages and common sign-offs and signatures removed, email addresses, phone numbers and long numbers masked, and the length capped; names in the text are not removed), the guest's first name, and the company's own trip, policy and booking details to our AI provider, OpenAI, so it can draft a reply, label the conversation (booking question, change request, complaint or other) and write follow-ups to enquiries (never to guests who have booked). Drafts wait in the Email Center for someone to use, edit or discard them. A company can also choose to send replies or follow-ups automatically; it starts in draft-only mode, and an automatic email goes out only if it passes fixed rules (nothing about money, prices, refunds, cancellations, discounts, changes to dates or group size, complaints or safety, and no links or contact details that aren't in the company's own details) and a separate automated check, only for emails received after the assistant was turned on, and not at night in the company's time zone (by default 21:00 to 7:00); anything else waits for a person. Emails it sends go out through the company's Outlook mailbox as described above. It can also email the company's owners and admins a daily or weekly report of counts from Treka (sent by Treka, not from the mailbox; no mail text is sent to the AI provider for it). Other conversations, and the rest of the mailbox, are never sent to the AI provider. An owner or admin can turn it off in the Email Center at any time, which stops it at once and deletes every draft that wasn't sent.
- Outlook Calendar: Treka shows your existing Outlook events on your Treka calendar, next to your trips, so you can see conflicts. When you press Push to Outlook, or a booking is confirmed, Treka adds the event for that departure to your calendar, keeps it up to date and removes it when the departure no longer has confirmed bookings. Every event Treka creates carries a Treka tag, and Treka only ever changes or deletes events with that tag: it never edits or deletes events you created yourself. By default the events go to the connected account's main calendar; an owner or admin can choose another calendar the account can edit instead (only the person who connected Outlook can choose a calendar shared with them or a shared mailbox's calendar). Choosing a different calendar stops Treka updating the old one; the events it already added there stay until you delete them. On a calendar other than the main one, the tag also names your company, so Treka never touches another business's events on a shared team calendar.
- Your own Outlook calendar (team members): once you connect it, Treka adds each departure you are assigned to and that has confirmed bookings: the trip name, company, dates, location, meeting point and the number of bookings and guests (not the guests' names). It updates the event when the departure or your assignment changes, and removes it when you are taken off the departure, decline it, or it is cancelled. Treka checks for changes when an assignment or departure date changes, and at least once an hour. It does not read the other events on your calendar except to find the ones it created (by their Treka tag). If the account you connect is the one your company's Outlook calendar already uses, Treka adds nothing extra, so nothing appears twice. This works whether your company uses Google Calendar or Outlook.
- One email and one calendar provider: a company uses either Gmail or Outlook for email, and either Google Calendar or Outlook Calendar for its calendar, chosen separately when connecting. Treka asks before switching. Choosing Outlook for email disconnects Gmail (as described in section 5). Choosing the other calendar stops Treka updating the old one; events Treka already added there stay until you delete them. An Outlook connection used for neither is deleted.
We use Microsoft user data only to provide these features to your business. We do not use it for any other purpose.
C. What we store and for how long
- A refresh token that Microsoft issues when you connect, stored encrypted (AES-256-GCM) in our database. It is what lets Treka act for you, can only be read by Treka's servers, and is never sent to your browser or shown to anyone. It is kept until you disconnect. Short-lived access tokens are obtained when needed and are not stored.
- Your account email address, name and Microsoft account ID, so Treka can show which account is connected and send from it. Kept until you disconnect.
- The calendar chosen for your company's events, if it isn't the main one: Microsoft's ID for that calendar, its name, the shared mailbox's address when it belongs to one, and who chose it. Deleted when Outlook is disconnected.
- Your own Outlook calendar connection (team members): a separate refresh token, stored encrypted (AES-256-GCM) and readable only by Treka's servers, your Microsoft account's address and ID, when your calendar was last brought up to date and whether that worked. Kept until you disconnect it, leave the company's team, or delete your Treka account.
- Email Center mail (Outlook email only): for each conversation, the subject, the other person's address and name, a short preview, when the last message came and any booking or guest it is linked to; for each message, the sender, recipients, date and text (quoted earlier messages trimmed; attachments are never stored). Also the chosen mailbox's address, Microsoft's notification subscription for it (with only a one-way hash of its secret) and how far Treka has read. Only your company's owners, admins and the roles they allow can see it, including the Action Center alerts raised from it. A message you delete in Outlook is deleted here on the next check. Conversations with no new message for 180 days are deleted automatically, and all of it is deleted as described in F.
- Email Center AI assistant (only if turned on): its drafts, the label on each conversation it worked on, and a history of what it did (drafted, sent and by whom or automatically, discarded, reports), which holds no message text. Drafts and labels are deleted with their conversation; unsent drafts and all labels are deleted when the assistant is turned off. The history is kept with the company's account. Each AI request is also logged with its size and cost, without the message text.
Apart from the Email Center, we do not store the emails you send through Outlook (Microsoft keeps a copy in your Sent Items). We do not store the contents of your calendar: your events are fetched when you open the Treka calendar, shown to you, and not saved. The events Treka creates hold only Treka's booking and departure details and the tag that identifies them.
D. Who we share it with
We do not sell Microsoft user data, and we do not share or transfer it to anyone except:
- Our hosting providers, which store and process it on our behalf and only to run Treka: Supabase (our database and servers) and Vercel (our website).
- Microsoft itself, when Treka sends your email, reads your mailbox for the Email Center, or reads and writes your calendar through Microsoft Graph.
- Our AI provider, OpenAI, only if your company turns on the Email Center AI assistant, and only the content described in B, to draft, label and send emails for your company. Under OpenAI's API data terms, OpenAI processes it for Treka, does not use it to train its models, and may keep it for up to 30 days to monitor for abuse.
- When the law requires it, or to protect the safety and security of our users, as described in section 4.
Unless your company turns on the Email Center AI assistant, we do not send Microsoft user data, including the mail in the Email Center, to artificial intelligence providers. Microsoft user data is never available to AI assistants you connect to Treka (section 8), and Trek, the assistant inside the Treka portal, never sees it. It is not used for advertising, is not sold to data brokers, and is not used to train artificial intelligence or machine learning models, by Treka or by our AI provider.
E. How we protect it and who can see it
- All data travels between your browser, our servers and Microsoft over encrypted HTTPS, and our database is encrypted at rest.
- Only your company's owners and admins can connect or disconnect Outlook, push the schedule to it and choose its calendar. Only the person who connected Outlook can choose the Email Center's mailbox, a calendar shared with them or a shared mailbox's calendar, since Treka uses their Microsoft access. A team member's own Outlook calendar connection is theirs alone: only they can connect, sync or disconnect it, and no one else in the company sees its events in Treka. The Email Center and its alerts, and the AI assistant's drafts, labels and history, are visible to owners, admins and the roles they give it to; only owners and admins can turn the assistant on or off or change its settings. Members of your company's Treka account can send email from the connected mailbox and see its calendar events in Treka.
- Treka staff do not read your Microsoft data, except with your permission to help with a support request, when needed for security or to investigate abuse, or to comply with the law.
F. Disconnecting and deleting your Microsoft data
- Disconnect in Treka: on the Connections page of the Treka portal, click Disconnect on the Outlook card. Treka immediately deletes the stored refresh token and connection details, which ends its access, together with all Email Center mail, and asks Microsoft to delete its notification subscription. Events Treka already added stay on your calendar until you delete them in Outlook.
- Your own Outlook calendar (team members): on the Calendar page of the Treka portal, click Disconnect under "Your own Outlook calendar". Treka immediately deletes that refresh token and connection, which ends its access to your calendar. Events it already added stay on your calendar until you delete them.
- Stop using Outlook for email: switching your email to Gmail (or to no provider), switching the Email Center to another mailbox, connecting a different Microsoft account, or Treka turning the Outlook feature off for your company deletes the Email Center mail Treka stored for that mailbox and asks Microsoft to delete its notification subscription (if Microsoft can't be reached, the subscription expires by itself within three days and Treka ignores it meanwhile). Nothing is deleted from your mailbox itself. Disconnecting Outlook or switching your email away from Outlook also turns the Email Center AI assistant off and deletes its drafts.
- Turn off the Email Center AI assistant: an owner or admin can turn it off in the Email Center (AI assistant, Turn off) at any time. It stops at once, nothing more is sent to the AI provider, and its unsent drafts and labels are deleted. Emails it already sent stay in your mailbox.
- Remove Treka's permission at Microsoft: Microsoft does not let an app revoke its own permission, so to remove it there as well, use account.live.com/consent/Manage for a personal Microsoft account, or myapps.microsoft.com for a work or school account (your IT administrator can also remove it). Treka can then no longer use your account; disconnect in Treka as well to delete what we stored.
- Ask us: email support@treka.app and we will delete your Microsoft data within 30 days. Deleting your Treka account deletes it too.
7.Instagram Data
This section explains what Treka does with data from Instagram. It applies only if a company owner or admin chooses to connect the company's Instagram professional account to Treka. Connecting is optional: you start it yourself from Marketing → Social in the Treka portal, sign in with Instagram, and Instagram shows you the permissions on its own consent screen. Nothing is accessed unless you approve them.
A. The Instagram data we access
- Your account profile (Instagram permission
instagram_business_basic): your Instagram user ID, username, name, account type, profile picture, follower, following and post counts, and the list of your own posts with their captions, media and like and comment counts, so we can show which account is connected and display your posts in Treka.
- Publish content (
instagram_business_content_publish): post a photo or reel to your account, with your caption, when you press Publish in Treka.
- Insights (
instagram_business_manage_insights): reach, accounts engaged, likes, comments, saves, shares and total interactions for your account and for your own posts.
- Comments (
instagram_business_manage_comments): read the comments on your own posts, including the commenter's username, and reply to, post or hide comments on them.
- Direct Messages (
instagram_business_manage_messages): the Direct Messages people send to your account and the replies sent from it, including the sender's Instagram-scoped ID and username, the message text, any attachment's type and link, and when each message was sent, so you can read and answer your inbox in Treka. Instagram sends these to Treka as they arrive (a webhook).
B. How we use it
We use Instagram data only to show it back to you and to carry out the actions you take in Treka: publishing the posts you create, showing your account and post insights, and letting you reply to, post and hide comments on your own posts. Every publish and every comment action happens only when you take it; Treka never posts, comments or replies automatically. We act only on the account you connected, never on anyone else's account or content.
Direct Messages are used to show your inbox, to raise an alert in your Action Center when someone writes, and to send the replies you write. A message is sent only when you type it and press Send, and only to the person in that conversation: Treka sends no automated, bulk or marketing messages, and starts no conversations. Following Instagram's rules, you can reply only within 24 hours of the person's last message; after that the reply box stays closed until they write again.
We do not sell Instagram data, use it for advertising, use it to build profiles of Instagram users, or share it with anyone except the service providers that host Treka. Instagram data is not sent to the AI writing assistant on the Social page, which uses only the business and trip details you have entered in Treka.
C. What we store and for how long
- Access token: your Instagram access token is stored encrypted (AES-256-GCM) in our database, can only be read by Treka's servers, and is never shown to your browser or anyone else. It is kept while the account is connected and deleted when you disconnect.
- Connection details: your Instagram user ID, username and account type, so Treka can show which account is connected. Deleted when you disconnect.
- Posts, insights and comments: fetched from Instagram when you open the Social page and shown to you; we do not keep copies of them in our database.
- Direct Messages: for each conversation we store the other person's Instagram-scoped ID and username, when the last message was sent, a short preview of it (up to 140 characters), when they last wrote (for the 24-hour reply window) and how many messages are unread; for each message we store its Instagram message ID, whether it was received or sent, its text, the type and link of any attachment, and when it was sent. If the person unsends a message, we delete its text and attachments. A new message also creates or updates one Action Center item for that conversation with the sender's username and the preview. We keep these so your company can see its inbox and get Action Center alerts, while the account is connected; all of them, including those Action Center items, are deleted when you disconnect, when you remove Treka in Instagram, or when you ask Instagram or us to delete your data. Messages sent to an Instagram account that is not connected to Treka are discarded, not stored.
- Media you upload: photos and videos you upload to Treka for posting are stored in your company's own folder so Instagram can fetch them. This is your content, not data from Instagram; email us to have it deleted.
D. Who can see it
Your company's owner, admins and the team roles the owner allows to manage social media in Treka. Only owners and admins can send replies to Direct Messages; Action Center alerts are visible to the team members who can see your Action Center. A small number of Treka staff may access it only when needed to provide support, keep the service secure, or comply with the law.
E. How to disconnect and delete your Instagram data
- In Treka: press Disconnect on Marketing → Social. We immediately delete the stored access token, connection details, and stored Direct Messages and conversations with their Action Center alerts.
- In Instagram: remove Treka under Settings → Apps and websites. Instagram notifies us and we delete the stored access token, connection details, and stored Direct Messages and conversations with their Action Center alerts. If you ask Instagram to delete your data, we delete it the same way and give you a confirmation code you can use to check the request with us.
- Ask us: email support@treka.app and we will delete your Instagram data within 30 days. Deleting your Treka account deletes it too.
8.AI Assistants (Muse, ChatGPT, Claude and Other Connected Apps)
A company owner or admin can choose to connect an AI assistant, such as Muse (by Meta), ChatGPT (by OpenAI) or Claude (by Anthropic), to their Treka account through the Treka connector at https://treka.app/api/mcp. Nothing is shared until the owner or admin signs in to Treka from the assistant and approves the connection on Treka's own approval page, which lists what the assistant will be able to see and do.
- What the assistant can read: for the one company chosen when connecting — its trips and departure schedule; bookings, including guests' names, email addresses and phone numbers; revenue figures; guide invoices; reviews; gift cards; and rental items with their prices, stock and availability.
- Changes only with permission: a connection is read-only unless the owner or admin turns on "Allow changes" when connecting. With it on, the assistant can add or change departures, add and update bookings (without taking or refunding payments), email a booking's guest, edit trip details, and approve or reject guide invoices. It can also create a booking and send the guest a Treka payment link, which the assistant returns to the owner or admin and, if they choose, Treka emails to the guest; the guest then pays on Treka's own Stripe-hosted checkout, exactly as on the company's booking page, and no card details pass through the assistant. The assistant acts only when the owner or admin asks it to, and asks them to approve each change before it runs; emailing a guest, sending a payment link, cancelling a booking, deleting a departure and approving or rejecting a guide invoice are marked as needing their explicit approval. It can never take payments itself, issue refunds or pay anyone out. Every change is recorded in the company's Treka activity log.
- Who receives the data: the data an assistant reads is sent to that assistant's provider (for example Meta, OpenAI or Anthropic) so it can answer you, and is then handled under that provider's own terms and privacy policy. Treka does not sell this data or use it for advertising, and does not receive your conversations with the assistant.
- Security: Treka issues the assistant its own access, limited to the chosen company and to the Treka connector, stored by Treka only in hashed form. Access tokens expire after an hour and are renewed only while the connection is active; the person who connected must still be an owner or admin of that company for it to keep working.
- Your controls and retention: an owner or admin can see every connected assistant and its recent changes under Connections in the Treka portal and disconnect it at any time, which stops all access immediately; you can also remove Treka from the assistant's own settings. We keep a record of connections and of changes made through them for as long as the company's account is active, as part of its activity history, and delete it with the account.
Booking a trip through an AI assistant (travellers)
Travellers can also ask an AI assistant, such as Muse, ChatGPT or Claude, to find and book a trip through Treka's public booking connector at https://treka.app/api/book/mcp. No Treka account is needed, and only trips whose operator turned on AI-assistant booking are shown.
- What the assistant sees: only public trip information (descriptions, locations, dates, seats left, prices, cancellation policies, photos and published reviews, with reviewers shown by first name and initial). It never sees other guests' details, operator notes or revenue.
- What you share to book: when you ask the assistant to hold a booking, it sends Treka your name, email address and, if you give them, your phone number and notes for the operator. Treka uses them to hold your spots, send you the payment link and booking confirmation, and passes them to the operator who runs the trip, exactly as when you book on the operator's Treka page. Treka also records which assistant the booking came from.
- Payment: nothing is charged inside the assistant and no card details pass through it. You pay on Treka's own Stripe-hosted checkout; an unpaid hold lapses after about 30 minutes and the spots are released.
- The assistant's provider: what you tell the assistant, and the trip information it reads, is handled by that assistant's provider under its own terms and privacy policy. Treka does not receive your conversation with the assistant.
The Email Center AI assistant
Separately from the connected assistants above, a company that uses Outlook for email can turn on Treka's own AI assistant in the Email Center. It is off by default, only an owner or admin can turn it on, and they see what will be shared and agree first. When it is on, the content of the relevant Outlook messages (only conversations with a guest, trimmed and masked as described in section 6) and the related booking context are sent to our AI provider, OpenAI, to draft, classify and, where the company chose it, send emails for the company. Under OpenAI's API data terms, the data is not used to train AI models, and Treka doesn't use it for that either. An owner or admin can turn it off in the Email Center at any time, which stops it immediately and deletes every draft that wasn't sent; disconnecting Outlook or switching email to Gmail turns it off too. Gmail is never read and never sent to an AI provider.
The weekly finance summary
To word the "What to look at this week" card in Analytics, Treka sends our AI provider, OpenAI, only aggregated figures that our own rules computed for the company: counts of guide invoices to review, how many days the oldest has waited, money totals per currency for the cash-flow forecast, and the date of the week in which that forecast first goes below zero. It never sends names, email addresses or any other guest or guide details; the figures shown on the card are filled in by Treka, not written by the AI, and it only suggests: it cannot change, approve or pay anything. AI wording is on by default, and an owner or admin can turn it off in Settings ("AI wording for the weekly summary"), after which the card uses Treka's own wording and nothing is sent.
9.QuickBooks Online (Intuit)
A company owner or admin can choose to connect the company's QuickBooks Online account (by Intuit) from the Connections page of the Treka portal. Nothing is shared until they approve the connection on Intuit's own consent page, and each feature below stays off until they turn it on. Treka asks Intuit for the accounting permission (com.intuit.quickbooks.accounting) and the sign-in permissions openid, profile, email, phone and address, which Treka uses only to show who connected QuickBooks.
- What Treka reads from QuickBooks: the company's name, country and currency settings (CompanyInfo and Preferences), its accounts, products and services, classes, locations and tax codes (so the owner can choose where amounts go), customers and vendors by email or name (so a guest or guide is never added twice), and whether a guide's bill has been paid.
- Guide pay (optional): Treka sends each approved guide invoice to the company's QuickBooks as a bill: the guide's name and email (as a QuickBooks vendor), the amount, dates and invoice number. If the invoice is then rejected in Treka, Treka deletes that bill when it is still unpaid.
- Sales & payouts sync (optional): from the start date the owner picks, Treka sends the company's bookings money: each guest payment, card refund, gift card sale and gift card change, with the guest's name and email (as a QuickBooks customer), the booking number, trip name and amounts. Store credit and gift card changes are sent as journal entries. If the owner chooses, GetYourGuide bookings are sent too, with the GetYourGuide traveller's name and email as the customer. To record each Stripe payout to the company's bank as a deposit with its fees, Treka reads that company's Stripe payouts and the balance transactions in them from its connected Stripe account.
- What Treka changes in QuickBooks: only what Treka itself created. The sync voids a GetYourGuide sales receipt when GetYourGuide cancels the booking, and updates a receipt's product, class or location when a booking moves to another trip; guide pay updates or deletes an unpaid bill as described above. Disconnecting QuickBooks deletes nothing in QuickBooks: what was sent stays there under the company's control.
- Who receives the data: the data goes to Intuit, into the company's own QuickBooks Online account, and is then handled under Intuit's terms and privacy policy. Treka does not sell it or use it for advertising.
- Security and your controls: Treka stores the QuickBooks connection tokens encrypted and only on its servers. An owner or admin can turn either feature off or disconnect QuickBooks at any time, which stops all sending; connecting a different QuickBooks company also turns the sync off until it is set up again. Treka keeps the QuickBooks ids of what it sent (so it never sends the same thing twice) and the guest-to-customer links, for as long as the company's account is active.
10.Xero
Instead of QuickBooks (a company connects one accounting system at a time), a company owner or admin can connect the company's Xero organisation from the Connections page. Nothing is shared until they approve the connection on Xero's own consent page and pick the organisation, and each feature below stays off until they turn it on. Treka asks Xero for offline access and the accounting permissions for settings, contacts, invoices, payments, bank transactions and manual journals, plus the sign-in permissions openid, profile and email.
- What Treka reads from Xero: the organisation's name, base currency and currencies, its accounts and bank accounts, tax rates and tracking categories (so the owner can choose where amounts go), contacts by email or name (so a guest or guide is never added twice), and whether a guide's bill has been paid.
- Guide pay (optional): Treka sends each approved guide invoice to the organisation as a bill: the guide's name and email (as a Xero contact), the amount, dates and invoice number. If the invoice is then rejected in Treka, Treka deletes or voids that bill when nothing has been paid on it.
- Sales & payouts sync (optional): from the start date the owner picks, Treka sends each guest payment, card refund, gift card sale and gift card change, with the guest's name and email (as a Xero contact), the booking number, trip name and amounts, and, if the owner chooses, GetYourGuide bookings. To record each Stripe payout to the company's bank as a transfer with its fees, Treka reads that company's Stripe payouts and the balance transactions in them.
- What Treka changes in Xero: only what Treka itself created: it deletes a GetYourGuide booking's transaction when GetYourGuide cancels it, re-points a moved booking's lines, and updates, deletes or voids an unpaid guide bill as described above. Disconnecting Xero deletes nothing in Xero.
- Who receives the data: the data goes to Xero, into the company's own organisation, and is then handled under Xero's terms and privacy policy. Treka does not sell it, use it for advertising, or use it to train AI models.
- Security and your controls: Treka stores the Xero connection tokens encrypted and only on its servers. An owner or admin can turn either feature off or disconnect Xero at any time, which removes Treka's connection at Xero and stops all sending; connecting a different organisation also turns the sync off until it is set up again. Treka keeps the Xero ids of what it sent and the guest-to-contact links for as long as the company's account is active.
11.Data Retention
We retain your personal data only for as long as it is necessary to fulfill the purposes described in this Policy or as required by law. Specifically:
- Active Accounts: For as long as you maintain an account with Treka, we will keep your profile and transactional information on record so that the Platform functions properly.
- Transactional Records: Even if you delete your account, we may retain certain information about transactions, bookings, communications, or payments as needed for legal, accounting, or fraud prevention purposes.
- Legal Obligations & Disputes: We retain data as necessary to comply with legal obligations or to resolve disputes/enforce our agreements.
When we no longer have a legitimate need or obligation to retain your personal information, we will securely delete or anonymize it. If you wish to delete your account, you may do so through the app or by contacting us.
12.Your Rights
Depending on your jurisdiction, you may have certain rights regarding your personal information. These rights may include:
- Access and Portability: You can request a copy of the personal data we hold about you, and in some cases, ask for it in a portable format.
- Correction: You have the right to request that we correct or update any inaccurate or incomplete information we have about you.
- Deletion: You may request that we delete your personal information.
- Objection to Processing: You can object to certain processing of your data, such as for marketing purposes.
- Restriction: You can ask us to limit the processing of your data in certain circumstances.
- Withdraw Consent: If we rely on your consent to process any data, you have the right to withdraw that consent at any time.
- Lodge a Complaint: If you believe we have violated your privacy rights, you have the right to file a complaint with a supervisory authority or data protection regulator in your area.
To exercise any of these rights, please contact us at support@treka.app with your request and sufficient information to verify your identity.
13.Security
We take reasonable measures to protect your personal data from unauthorized access, loss, misuse, or alteration. This includes using industry-standard security practices such as encryption, firewalls, secure server infrastructure, and regular security audits. We also limit access to your personal data to those employees and contractors who need it to operate the Platform or assist you.
However, no method of transmission over the Internet or electronic storage is 100% secure. Therefore, while we strive to protect your information, we cannot guarantee absolute security. It is important for you to also play a role in keeping your data safe: please use a strong, unique password for your Treka account and do not share it with others. If you suspect any unauthorized access to your account or any security breaches, please notify us immediately.
14.Children's Privacy
Treka's services are not intended for individuals under the age of 18. We do not knowingly collect personal information from children under 18 years old. If you are under 18, do not use the Treka Platform or send any personal data to us. In the event we learn that we have inadvertently collected personal information from a child under 18, we will take steps to delete that information promptly. Parents or guardians who believe their child may have provided us with personal information can contact us, and we will delete the data.
15.International Users
Treka is based in the United States, and our services are primarily targeted to users in the U.S. However, we may have users or guides from other countries. By creating an account or using the Treka Platform from outside the United States, you acknowledge and agree that your information may be transferred to and processed in the United States (and potentially other countries where we or our service providers operate).
16.Changes to This Policy
We may update or modify this Privacy Policy from time to time as our services evolve or as legal requirements change. If we make significant changes, we will notify you by email or through a prominent notice on the Platform (for example, via an in-app alert) prior to the change becoming effective. The "Last Updated" date at the top will always indicate the latest revision. We encourage you to review this Policy periodically to stay informed about how we are protecting your information.
Continued use of Treka after an update constitutes your acceptance of the revised Privacy Policy. If you do not agree to any updated terms, you should stop using the Platform and, if you wish, delete your account.
17.Contact Information
If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:
- Email: support@treka.app
- Phone: +1 (360) 620-8085 (Monday–Friday, 9am–5pm PT)
- Mail: Treka LLC – Privacy Department
We will do our best to address your inquiry promptly and thoroughly. Your privacy is important to us, and we welcome your feedback.
By using the Treka Platform, you confirm that you have read and understood this Privacy Policy. This Policy is incorporated into and subject to our Terms of Service. Thank you for trusting Treka with your outdoor adventures – we are committed to safeguarding your personal information every step of the way.
Questions?
Email support@treka.app or reach the team through our contact page.
Email support
Contact Also readTerms of ServiceThe agreement that covers using Treka, bookings, payments and disputes.Read the Terms of Service
Privacy Policy · Terms of Service