Logo
  • Home
  • Tools
  • Tactics
  • Teams
  • Login
  • Book a Demo

Book a Demo

Privacy Policy

Last updated: 21 November 2026

Contents

  1. Who we are
  2. Our role for each group of people
  3. The data we collect
  4. How we use data and our legal bases
  5. Google user data
  6. Meta user data
  7. AI features
  8. Cookies and device storage
  9. Who we share data with
  10. International transfers
  11. How long we keep data
  12. Security
  13. Your rights
  14. Data deletion instructions
  15. Children
  16. Changes to this policy
  17. Contact us

1. Who we are

RetainTee provides marketing, analytics and website tools for hotels. We are based in Zayed City, Giza, Egypt. In this policy, "RetainTee", "we" and "us" mean RetainTee. You can reach us at [email protected].

This policy covers:

  • our marketing website, retaintee.com;
  • the RetainTee dashboard at app.retaintee.com, which hotel staff sign in to;
  • the scripts, widgets and trackers that hotels add to their own websites and booking engines; and
  • the third-party accounts a hotel connects to RetainTee, such as Google and Meta.

2. Our role for each group of people

Dashboard users. For hotel staff and other people who use the RetainTee dashboard, RetainTee is the controller of their account data. We decide how that data is used to run the service.

Visitors to retaintee.com. RetainTee is the controller of data collected on our own marketing website.

Hotel website visitors and guests. When a hotel uses RetainTee on its own website or booking engine, the hotel is the controller of its visitors' and guests' data. RetainTee processes that data on the hotel's behalf and on its instructions, as its processor. If you are a guest or a visitor to a hotel's website, the hotel's own privacy policy explains how it uses your data, and you should contact the hotel first to use your rights. We will help the hotel answer your request.

3. The data we collect

Dashboard users

  • Your name, email address and the organisation you belong to.
  • Your password, which we store only as a one-way hash.
  • Two-factor authentication secrets and recovery codes, if you turn two-factor authentication on.
  • An audit log of actions taken in the dashboard, with the user's name, email address, IP address and browser user agent.
  • Session data. Your sign-in session is stored in our database with your IP address and browser user agent, and is linked to a session cookie in your browser.
  • Messages and files you send to the dashboard's assistant and other features.

Visitors to retaintee.com

  • Analytics. Our site loads Google Tag Manager (container GTM-NXZ48LNV) and Rybbit analytics, which record pages visited, referrer, device and browser information, and approximate location.
  • Contact form. When you send us a message, we receive your name, email address, message and the options you tick. The message is emailed to our team through Cloudflare Email Sending. Your IP address is used briefly to limit repeated submissions.

Visitors to hotel websites that use RetainTee

  • Widget interactions and form submissions. When a visitor sees or uses a RetainTee widget, such as a special offer or a lead form, we record that interaction. When a visitor submits a form, we receive what they enter, such as their name, email address or phone number. Email addresses are encrypted at rest.
  • Site tracker. RetainTee's site tracker counts page views and visits to the booking engine. For each event it records the page path, the referring site, campaign (UTM) tags, whether the visit came from a Google or Meta ad click, the visitor's country, device type, browser and user agent, whether Google Analytics and Google Tag Manager loaded, and the visitor's analytics consent state. The Google Analytics client ID is read from its cookie only when the visitor has granted analytics consent. The site tracker does not store anything on the visitor's device.
  • A/B tests. When a hotel runs an experiment, a random visitor ID is stored in the visitor's browser so they keep seeing the same variant. This happens only when analytics consent is granted, and the ID is removed if consent is denied. See Cookies and device storage.
  • Country. We read the visitor's country from a header our CDN, Cloudflare, adds to each request. We use it to show the right widgets and in statistics. We do not store the visitor's IP address with these events.
  • Booking capture. To tell which bookings came from an experiment, we store a hashed form of the booking confirmation number, not the number itself.
  • Umami analytics. Where a hotel enables it, its site tracker also loads Umami, an analytics tool that RetainTee hosts itself at hub.retaintee.com.

Booking data

Hotels can import reservation exports from the Amadeus iHotelier booking engine, and the booking engine can send us booking events. We keep the booking's confirmation numbers, dates, rooms, revenue, booking channel and the guest's country. We do not keep guests' names, cities or addresses. An uploaded export file, which does name its guests, is deleted as soon as it has been imported.

The hotel's CRM

When a hotel connects its own GoHighLevel account, RetainTee writes booking events, abandoned checkouts, consent choices and lead form submissions into that account. These can include the guest's name, email address, phone number, country and stay dates as the guest entered them. RetainTee can also send review requests to departed guests through the hotel's GoHighLevel account, and records the rating and any message the guest sends back to the hotel.

Data from accounts a hotel connects

A hotel can connect its own accounts so RetainTee can show their figures in the dashboard. RetainTee reads these accounts. It does not change them, except that in Google Tag Manager we add and edit only our own tags, which are named "RetainTee - …".

  • Google Analytics 4, through the Google Analytics Data API and the property's BigQuery export.
  • Google Tag Manager.
  • Google Search Console. See Google user data.
  • Google Ads. See Google user data.
  • Meta ad accounts, through the Meta Marketing API. See Meta user data.
  • Microsoft Clarity, through its data export.
  • The Amadeus web content system. When staff use the RetainTee browser extension, it sends us their Amadeus login session so the dashboard can save page edits there.

Access tokens, API keys and login sessions for these accounts are encrypted at rest and are never sent to the browser.

Mailing lists

Hotels can upload mailing lists to our list cleaner, which checks whether each mailbox exists. The uploaded file and its cleaning run are deleted after 7 days. The results of mailbox checks are cached for up to 30 days so the same address is not checked twice. Contacts a hotel keeps as verified stay until the hotel deletes them or asks us to.

Public reviews

For our reputation tools we collect public review ratings, review counts and reviews from Google, TripAdvisor, Booking.com and HolidayCheck about the hotels we serve.

4. How we use data and our legal bases

  • To provide the service: run the dashboard, show widgets, produce reports, sync bookings and send events to the hotel's CRM. For dashboard users our legal basis is the contract with your organisation. For hotel visitors and guests we act on the hotel's instructions, and the hotel chooses the legal basis, such as consent.
  • To keep accounts secure, prevent abuse and fix errors. Our legal basis is our legitimate interest in a safe, working service.
  • To answer messages sent through our contact form. Our legal basis is our legitimate interest in replying to you.
  • To understand how people use retaintee.com. Our legal basis is our legitimate interest or, where required, your consent.
  • To comply with the law.

We do not sell personal data. We do not use hotels' guest data for our own advertising.

5. Google user data

A hotel connects its Google account from Settings → Integrations in the dashboard, so RetainTee can read its Search Console and Google Ads data. This section explains what we do with the data we receive from Google through that connection.

RetainTee'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.

What we access

  • The email address of the signed-in Google account, so the dashboard can show which account is connected.
  • Google Search Console: the list of properties the account can see, and search performance data for the property the hotel picks. That is clicks, impressions, click-through rate and average position, by date, query, page, country and device.
  • Google Ads: the names and IDs of the ad accounts the Google account can reach, and, for the account the hotel picks, each campaign's name, daily spend, currency, impressions and clicks.

We only read Search Console and Google Ads data. We do not create, change or delete anything in those accounts.

How we use it

We use this data only to show the hotel its own reports: search (SEO) figures, advertising spend, and return on ad spend, which compares a campaign's spend with the bookings credited to it. Reports appear in the dashboard, and a published report's headline figures can be emailed to the recipients the hotel chooses. When a dashboard user asks the dashboard's AI features about a report, the report's figures, which can include this data, are sent to the AI provider to produce the answer. See AI features.

If the hotel has bought our managed service, RetainTee staff view this data at the hotel's request to prepare its reports. To draft a report's findings, its figures, including Search Console and Google Ads data, are sent to our AI provider (Anthropic by default). Our staff review the draft before it is published to the hotel.

We do not:

  • sell Google user data;
  • use it for advertising, including to serve, target or measure ads;
  • use it to train generalised artificial intelligence or machine learning models; or
  • allow people to read it, except with the hotel's agreement (such as our staff preparing reports under the managed service), when needed for security purposes such as investigating abuse, to comply with the law, or for our internal operations when the data has been aggregated and anonymised.

How we store and share it

The Google refresh token is encrypted at rest and never sent to the browser. Daily Google Ads spend figures and the figures in saved reports are kept in our database. Other Search Console results are cached for up to 15 minutes. We share Google user data only with the hotel's own report recipients and with the service providers who help us run the dashboard (for this data: Hetzner, Cloudflare, Sentry and Anthropic, or the hotel's own AI provider), and only to provide the features described here.

How long we keep it, and how to remove access

We keep the connection until the hotel disconnects it. Disconnecting Google in Settings → Integrations deletes the stored token and the property and accounts picked through it. Stored spend figures and saved reports remain until the hotel asks us to delete them, the hotel deletes the report, or the hotel's account is closed. Disconnecting in the dashboard does not revoke RetainTee's access at Google. You can also remove RetainTee's access at any time from your Google account at myaccount.google.com/permissions.

6. Meta user data

A hotel can connect its Meta business with Facebook Login for Business from Settings → Integrations. We use the ads_read permission to read the hotel's advertising data. Our team can also set up this connection for the hotel with an access token the hotel provides; the same rules apply to it.

  • What we access. For the ad accounts the business connects: account names and IDs, and for the ad account the hotel picks, each campaign's name and ID, daily spend, currency, impressions and clicks. We also read the name of the business or person the connection belongs to, to show who is connected.
  • Why. To show the hotel its own advertising spend and return on ad spend in the dashboard and in its reports, including report emails sent to the recipients the hotel chooses. When a dashboard user asks the AI features about a report, its figures can be sent to the AI provider to produce the answer. If the hotel has bought our managed service, RetainTee staff view this data at the hotel's request to prepare its reports, and a report's figures are sent to our AI provider (Anthropic by default) to draft its findings, which our staff review before publishing.
  • What we do not do. We do not sell this data, use it for advertising, or change anything in the ad account.
  • Retention. The access token is encrypted at rest and kept until the hotel disconnects Meta. Daily spend figures and saved reports are kept while the hotel's account is active, and are deleted on request.

To delete this data, follow the data deletion instructions.

7. AI features

Some dashboard features use AI to answer questions, analyse reports, translate content and draft text. To do this, the feature sends the relevant report data, page content and the user's question to an AI provider. By default this is Anthropic. A hotel can instead set up its own AI provider with its own API key, in which case that provider receives the data under the hotel's own terms with it.

RetainTee does not use customer data, guest data or Google or Meta user data to train AI models. AI output is a draft. A person reviews it before it is used: the hotel's user, or, for reports under the managed service, RetainTee staff.

8. Cookies and device storage

Dashboard. We use a session cookie to keep you signed in, a cookie that protects forms against cross-site request forgery, and browser storage for interface preferences such as light or dark mode.

retaintee.com. Google Tag Manager and Rybbit can set cookies or use similar technologies for analytics.

Hotel websites. RetainTee widgets can store the following in the visitor's browser:

  • a random visitor ID for A/B tests, only when analytics consent is granted, replaced after 13 months and removed if consent is denied;
  • which test variant the visitor was shown, and when, so a later booking can be linked to the test for up to 30 days;
  • how often a widget has been shown, so it is not shown too often; and
  • for the current browser tab only, the visitor's country and details typed into the booking engine, so the information is not lost between pages.

The hotel is responsible for telling its visitors about this storage and, where the law requires it, for asking their consent. Our scripts read Google consent mode when the hotel's site uses it.

9. Who we share data with

We share data with the people and services the hotel chooses (its report recipients, its CRM and its own AI provider), and with providers that help us run the service, only for that purpose:

  • Hetzner, which hosts our servers and database in Germany.
  • Cloudflare, for content delivery, DNS, security, sending email, and the visitor's country.
  • Sentry, for error monitoring.
  • Anthropic, our default AI provider, or the AI provider the hotel configures with its own key.
  • Reoon, which checks whether mailboxes exist for the mailing list cleaner.
  • DataForSEO and Apify, which collect public review data.
  • Rybbit, for analytics on retaintee.com.
  • Google, Meta and Microsoft, whose services the hotel connects or uses, such as Google Analytics, Google Tag Manager, Google Ads, Search Console, Meta ads and Microsoft Clarity.
  • GoHighLevel, the hotel's own CRM, when the hotel connects it.

We may also disclose data when the law requires it, to protect our rights or users' safety, or as part of a merger or sale of our business, in which case this policy continues to apply to the data.

10. International transfers

RetainTee is based in Egypt, and our providers process data in the European Union, the United States and other countries. When we transfer personal data out of the European Economic Area or Egypt, we rely on safeguards the law allows, such as the European Commission's standard contractual clauses or our providers' equivalent commitments.

11. How long we keep data

  • Dashboard account data: while the account is active, and for a limited period after it is closed to meet legal, security and accounting needs.
  • Tokens for connected accounts: until the hotel disconnects the account.
  • Uploaded mailing list files and cleaning runs: 7 days. Mailbox check results: up to 30 days.
  • Uploaded booking export files: deleted as soon as they are imported.
  • Hotel visitor and guest data: as the hotel instructs, and deleted when the hotel asks or when we receive a valid erasure request.
  • Contact form messages: as long as needed to answer and follow up on your enquiry.

12. Security

We protect data with measures that include:

  • encryption in transit with TLS;
  • encryption at rest for access tokens, API keys, login sessions and guests' email addresses;
  • hashed passwords and optional two-factor authentication;
  • access controls that limit each user to their own organisation's data; and
  • audit logs of actions taken in the dashboard.

No system is completely secure. If we learn of a breach that affects your personal data, we will notify you and the authorities as the law requires.

13. Your rights

Depending on where you live, you may have the right to access your personal data, correct it, delete it, object to or restrict how we use it, receive it in a portable format, and withdraw consent you have given. These rights come from laws such as the EU General Data Protection Regulation, for people in the European Union, and Egypt's Personal Data Protection Law No. 151 of 2020.

To use your rights, email [email protected]. We answer within 30 days. If you are a hotel's visitor or guest, please contact the hotel first. We will help it respond.

You can also complain to a data protection supervisory authority, such as the one where you live or work. In Egypt, this is the Personal Data Protection Center.

14. Data deletion instructions

You can remove RetainTee's access to your data and ask us to delete it in these ways:

  1. Disconnect in the dashboard. Go to Settings → Integrations and choose Disconnect for Google or Meta. This deletes the stored access token and the accounts picked through it. Stored daily ad spend figures are deleted on request; see option 4. If you do not see Disconnect, the connection was set up by our team: email us and we will remove it.
  2. Remove RetainTee in Meta. Remove the RetainTee integration in Meta Business Settings. This ends our access to your ad accounts.
  3. Remove RetainTee in Google. Go to myaccount.google.com/permissions and remove RetainTee's access.
  4. Ask us to delete everything. Email [email protected] from the address on your account, or name the organisation and the data concerned, and ask us to delete your data. We will confirm and complete the deletion within 30 days.

Guests and visitors of a hotel can ask the hotel, or us, to delete their data. We can find and delete a guest's data by their email address.

15. Children

The RetainTee dashboard and retaintee.com are for businesses and are not directed at children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has given us personal data, contact us and we will delete it.

16. Changes to this policy

We may update this policy. When we do, we will change the "Last updated" date at the top. If a change is significant, we will tell dashboard users by email or in the dashboard before it takes effect.

17. Contact us

RetainTee, Zayed City, Giza, Egypt.
Email: [email protected]

RetainTee
  • Home
  • Tools
  • Tactics
  • Teams
  • Contact Us

Contact us

Email
[email protected]
Phone
+20 12 08883536
Address
Zayed City, Giza, Egypt
© 2026 RetainTee. All rights reserved. Privacy Policy Terms of Service