Privacy policy

Who we are

TELLME AI LIMITED (“Tellme”, “we”, “us”) makes Troopa and runs its websites, troopa.ai and related domains. We are registered in Northern Ireland with company number NI710572, at 92 Castle Street, Office 1601, Belfast BT1 1HE, United Kingdom, and registered with the UK Information Commissioner’s Office as a data controller, reference ZB782246.

Contact us about anything in this policy at support@troopa.ai, or by post at the address above. We have not appointed a data protection officer, because the law does not currently require us to.

Two different roles, and why it matters

We handle personal data in two different capacities, and the difference decides who you should ask about it.

• Your account. Your name, email address and sign-in, billing, support conversations, how you use Troopa, the app’s diagnostics, and this website. We decide how it is used: we are the controller, and this policy is the full account of it.
• Your meetings. What Troopa captures and makes from a meeting: the transcript, notes, decisions and actions, notes of what was shared on screen, your questions and Troopa’s answers, and documents you add. You decide, or your organisation does. Whoever uses Troopa, you or your organisation, is the controller and we are its processor, under the data processing terms in Annex A of our terms.

This policy describes both, so that you know what happens to your meetings. But for the second, the choices are yours: what to capture, whom to tell, what to keep and what to share. GDPR explains the roles in more detail.

What we collect

• Account data: your name, email address, organisation, role and region. If you sign in with Google or Microsoft, your name, email address and account identifier with them; we do not keep their access tokens. A password, only as a secure hash. Your sign-in sessions, with the device, IP address and when they were last used. How you like the desktop app’s Home laid out (a day, a week, a month or a list, where its divider sits, its side menu open or folded, and its weekends shown or folded), so it is the same on each of your computers.
• About your work, if you answer the desktop app’s first questions: the kind of work you do and the meetings that fill your week, each picked from a short list, so Troopa can suit what it suggests. Change or clear them in the app’s Settings.
• Meeting content: while Troopa is listening, the sound from your microphone and your computer, turned into a transcript; the names of the people in the call and of whoever is speaking, as your meeting app shows them; unless you turn it off, a picture of the meeting window each time what is shared on screen changes, from which Troopa writes a short note (the picture is not kept); with a question you ask during the call, a picture of the meeting window or, when there is none, of the whole screen your pointer is on (not kept either); the notes, decisions and actions Troopa writes; the boards and canvases it draws as the meeting talks, which can name people, such as each person’s estimate or update; your questions and its answers; and documents you add.
• Calendar data, if you connect a calendar: see “Your calendar” below.
• Connected apps, if you connect Notion, Google Drive or another app: see “Apps you connect” below.
• Billing data: your plan, your subscription’s status, and the payment provider’s identifiers for them. Your card details and billing address are held by Onelink, not by us.
• Support data: what you write to us and what we answer.
• Feedback: what you tell us you love about Troopa, or what could be better, and whether we may quote you.
• Ratings: the thumbs up or down you give Troopa’s cards in a meeting, and why, where you say. Never what the card said.
• Device and app data: app version, operating system, IP address, and our servers’ logs. The app contains no crash reporting, and checks troopa.ai and related domains for updates. After an update it reports how the update went: the versions, the download’s size and time, how it installed and whether it worked, never linked to your account.
• Usage data: which features you use, how many meetings you record and how long they last, and, where it is switched on for your region, which screens of the desktop app you open and what you click there, as “Usage analytics in the desktop app” below says. Not what was said in them.
• Website data: cookies, as the cookie policy explains, and what you write in the Talk to us form.
• Marketing preferences: whether you want product news from us.

What we do not collect. Troopa creates no voiceprint and never works out who somebody is from their voice: names come from the meeting app. Within one meeting the transcription service may tell voices apart, and a voice nobody named is labelled with a made-up name such as “Anonymous Otter”, or as “Speaker 2”; that label means nothing outside that meeting. Troopa does not read the meeting’s chat, and it does not infer anybody’s mood, emotions or engagement. We do not ask for special categories of personal data, such as health information, or for criminal offence data, although people sometimes say such things in meetings, in which case they are in the transcript like anything else that was said.

How we use your account data, and our legal reasons

Data protection law requires a legal reason, called a lawful basis, for each use. Where we rely on legitimate interests, we have checked that our interest is not outweighed by yours, and you can object.

• Create and run your account, and provide Troopa to you: performing our contract with you.
• Suit Troopa’s practice meeting and suggestions to what you said of your work: legitimate interests.
• Take payment and manage your subscription: performing our contract, and our legal obligation to keep financial records.
• Answer your questions and fix problems: performing our contract, and legitimate interests.
• Read your feedback to improve Troopa: legitimate interests. Quote it on our website, with your first name and organisation, only if you ticked that we may: your consent, which you can take back in the app at any time.
• Count your ratings of Troopa’s cards, to see what helps and improve Troopa: legitimate interests.
• Keep Troopa secure, and prevent fraud and abuse: legitimate interests.
• Understand how Troopa is used, from usage and diagnostic data and from replays of the desktop app with meeting content masked, never from meeting content, so that we can improve it: legitimate interests. You can turn it off in the app’s Settings (Share usage data).
• Tell you about important changes to Troopa, our terms or your account: performing our contract, and legitimate interests.
• Send you product news: your consent, or, if you are a customer, our legitimate interest in telling you about Troopa, with an unsubscribe link in every email.
• Measure and advertise this website with optional cookies: your consent, which you can withdraw in Cookie settings.
• Keep automated spam out of the Talk to us form, with Cloudflare Turnstile: legitimate interests.
• Meet legal obligations, respond to lawful requests and defend legal claims: legal obligation, and legitimate interests.

We do not sell personal data, and we do not train AI models on your meetings.

How your meetings are handled

Only while listening. Troopa captures a meeting only while you have it listening. Its menu in your menu bar or taskbar shows when it is listening, and lets you stop it at once.

Audio and screen. The audio is streamed to a transcription service as it is spoken. If the connection drops, the app holds at most five minutes of audio in memory until it is back. It never writes audio to your computer’s disk, and Troopa never stores audio or video anywhere. Pictures of the meeting window are sent to an AI model to write a short note of what was shared, and are not kept. The model is told to leave out people’s video, names and faces, the chat and the list of people. A question you ask during the call can go with a picture too, so that Troopa can answer about what you see: of the meeting window, or, when Troopa finds no meeting window, of the whole screen your pointer is on. That picture is read to answer you and is not kept.

AI. To write the notes, find the decisions and answer questions, Troopa sends the transcript, or the parts of it a request needs, your questions, the passages from documents and connected apps that bear on them, and the pictures above to AI models from Anthropic and OpenAI. They do not train their models on what we send. They keep it for up to 30 days to check for misuse, and then delete it, unless the law requires them to keep it longer or their systems flag it as misuse. While Troopa is listening, an AI model from TypeSafe also reads the meeting’s newest lines and who said them, with a little of its context, such as its title, its agenda and what Troopa last did, to tell when somebody asks Troopa something.

Where it is stored, and what is processed elsewhere. Meeting content is stored in the region your organisation chose when it signed up: the United Kingdom (London), the European Union (Frankfurt) or the United States (Northern Virginia). The audio is transcribed at our transcription providers’ European endpoints for the UK and EU regions, and in the United States for the US region. And the AI models that answer questions and write the notes, Anthropic’s and, where switched on for your region, OpenAI’s, process the text a request needs in the United States, for every region. So does TypeSafe’s, which tells when Troopa is asked something. The files of documents you add are kept in your region too. Data residency sets this out in full, with the date it was last checked.

No training. We do not use your meetings to train or improve AI models, ours or anybody else’s.

Who at Tellme can see them. We look at meeting content only where running the service or answering a customer’s request needs it. To help with a problem, our support can sign in to your account in our own Troopa app, with a written reason, for an hour at most, and see what you see, your meetings included. A support session cannot record, change your sign-in, billing, people, calendars or connected apps, search your connected apps, or delete your account. Our staff can also read a person’s meetings in our own console, with a written reason. Each support session and each such reading is recorded in a log of our own, in your region. It is not in your organisation’s audit log, and we do not tell you each time. Replaying a meeting’s record of events in our console is written to your organisation’s audit log, as Security describes. If you send us feedback on a note or an answer, we see what you chose to send, which may include the part of the meeting it is about, and may use it to improve Troopa.

Sharing and email. If you share a meeting, the people you share it with can read it. If you share it by link, anybody with the link can read it and pass it on. You can stop a share at any time. If you send the notes by email, they stay in the recipients’ mailboxes.

Your questions to Troopa. What you ask Troopa about a meeting, or from Home, is kept with its answers so that you can read them again. They are yours alone: nobody else in your organisation, and nobody a meeting is shared with, sees them. They are deleted with the meeting, or with your account, and the words an answer quotes from a transcript are deleted with that transcript. What was asked of Troopa during a call you recorded is kept with that meeting’s transcript, for you alone too, and deleted with it. Where an answer cites one of your connected apps, it keeps that passage’s title, link and a short excerpt, and they are deleted with the answer.

Web lookups. Unless your organisation turns them off, a question Troopa cannot answer from your meetings, or one you ask it to look up on the web, is sent on its own, without the rest of the meeting, to Anthropic’s or OpenAI’s web search in the United States. For a question asked after a call, Troopa sends instead a short search about its subject, written without the names, figures or anything else from your meetings, unless you ask it to search the web, when what you asked it to look up is sent as you wrote it.

Your calendar

If you connect a Google or Microsoft calendar, Troopa reads it every few minutes, looking 90 days ahead, so it can show you what is coming up and give your meetings the right title and people. Its access is read-only: it cannot change, create or delete events, unless you ask it to add your meetings there, as below. You can connect more than one account, Google and Microsoft alike, and choose which of each account’s calendars Troopa shows; it keeps their names to offer you the choice, and reads only the ones you show.

It keeps only events with a Zoom, Teams or Google Meet link, and for those it stores the title, time, time zone, how the event repeats, the joining link, the organiser, each attendee’s name, email address and reply, and which of your calendars it is on. An event on more than one of your calendars is kept once. The access is kept sealed with encryption.

You can turn a calendar off, or disconnect an account, at any time in Troopa’s settings. Troopa then stops reading it, and a disconnected account’s access is deleted. Its meetings coming up leave your list; meetings Troopa recorded stay, with their titles and attendees, until you delete them or your account.

Meetings you add in Troopa. If you add a meeting in Troopa yourself, Troopa keeps its title, time, how it repeats, where it is (a place or a joining link), the people you name and your notes, for you alone, until you delete it or your account. Unless you add it to your calendar, as below, Troopa sends nobody an invitation and writes nothing to your calendars.

Adding a meeting to your calendar. When you make a meeting in Troopa, you can choose to add it to one of your own Google or Microsoft calendars as well. The first time you choose an account, Troopa asks it for permission to create, change and delete events on the calendars you own. Troopa then creates, changes and deletes only the events you ask it to, in the calendar you choose, and nothing else in your calendars: the meeting’s title, time and time zone, its place or joining link, your notes and, if it repeats, its weekly repeat. The people you name are put on the event, and sent an invitation by your calendar from your account, only if you tick “Send invitations”; changes and a cancellation then reach them the same way. Troopa keeps the event’s identifier so it can keep the event in step with the meeting, and if you change the event’s time, title or place in your calendar, Troopa takes your change. Deleting the meeting in Troopa deletes the event. Deleting your Troopa account, or disconnecting the calendar, does not: the events are your calendar’s own entries, and you delete them there. Your organisation can turn adding meetings to calendars off.

If an administrator of your organisation connects its directory, Troopa also reads the names, email addresses and, where the directory holds them, job titles and departments of the people in it, so it can recognise colleagues.

Google user data. Troopa’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements. We do not use data from Google APIs to train AI or machine-learning models, we do not sell it, and we do not use it for advertising.

Microsoft user data. You can also withdraw Troopa’s access at account.live.com/consent/Manage (personal accounts) or myapps.microsoft.com (work or school accounts). Disconnecting deletes the access Troopa holds; meetings Troopa recorded stay until you delete them or your account.

Apps you connect

In the desktop app’s Connectors, you can connect your own Notion, Confluence, Jira, Glean, Google Drive, SharePoint, OneDrive, GitHub or Slack for Troopa to search, and your Obsidian notes, where your region offers them. Each app is your organisation’s own choice, used under your organisation’s own agreement with it. Connectors are on unless your organisation turns them off, which it can do for everybody.

Only your question is sent. When you ask Troopa something in the app, or on your own screen during a call you are recording, Troopa sends your question, and for a follow-up the one or two you asked before it, to the apps you connected and switched on. It searches them with your own access, so each app shows Troopa only what you may see. Nothing else from your meetings is sent. What comes back is shown to you alone, never to a meeting you present or share, and the passages that bear on your question go to the AI model that writes the answer. Troopa does not search your apps during a support session.

What Troopa keeps. Troopa copies nothing from the apps it searches. When it keeps an answer for you, it keeps the title, link and a short excerpt of each passage the answer cites, as “Your questions to Troopa” above says. The access each app gives Troopa is sealed with encryption. It is deleted when you disconnect the app, when you leave the organisation, when your account or your organisation is erased, and after a year without use. Disconnecting also hands the access back where the app allows it. Confluence, Jira, SharePoint and OneDrive do not, so remove Troopa in your Atlassian or Microsoft account as well.

Obsidian. Obsidian has nothing to search, so the desktop app reads the vault you choose on your computer and sends Troopa its notes. Troopa keeps them in your region as your own documents, uses them only for your own answers while Obsidian is connected, and keeps them in step with the vault: a note you delete there is deleted here. Disconnecting Obsidian deletes them unless you choose to keep them, and they are deleted when you leave the organisation or your account is deleted.

Google Drive. Troopa asks Google for read-only access to your Drive, and for your email address to check that the Drive is yours. It uses the access only to find, when you ask a question, the files that match it, to read the part of a Google Doc, Sheet or Slides file that bears on it, and to show you that part in its answer. It does not change your files, does not copy them into Troopa beyond the short excerpt a kept answer cites, does not use them to train AI models, does not sell them and does not use them for advertising. Troopa’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.

Usage analytics in the desktop app

Where we switch it on for your region, the desktop app tells PostHog, a product analytics service, how it is used, so that we can see where Troopa is hard to use and make it easier. It sends which screens you open, where you click on them with every word hidden, when a meeting starts and ends and how long it ran, the kind of board you open, whether you rate one of Troopa’s cards up or down, your device’s system, screen size and IP address, and your Troopa user id and your organisation’s id. It never sends what is said in a meeting: no transcript, answer, question, board or canvas, and no names, email addresses, file names or document text.

Replays. The app records sessions of how you use it, with meeting content masked: every word and every field in them is hidden, and Troopa’s meeting views, boards and anything you present are left out. You can turn it off in the app’s Settings (Share usage data). Where we choose to ask first, nothing is recorded until you say yes.

Where, and for how long. PostHog keeps it in its EU cloud, in Frankfurt, for the UK and EU regions, and in its US cloud for the US region. It keeps replays for 30 days and everything else for 12 months, then deletes them.

Turning it off. Switch off Share usage data in the desktop app’s Settings and it sends nothing more from your computer. An organisation can turn it off for everybody in it with its Usage analytics setting. Nothing is sent while our support is signed in to your account.

If you would rather it was not there

This part is for you if somebody on a call with you was using Troopa. You did not choose Troopa, so here is what it means for you. What Troopa is, and what it heard has more.

What Troopa keeps about you. What you said, as text, in the transcript of that meeting and in the notes made from it, with your name as the meeting app showed it, and your email address if you were in the calendar invitation. Troopa keeps no recording of your voice, never works out who you are from your voice, and does not assess your mood or behaviour.

Where it is kept. In one region, chosen by that organisation: the United Kingdom (London), the European Union (Frankfurt) or the United States (Northern Virginia). Everything Troopa keeps from a meeting is stored there. The person who used Troopa may also keep the transcript and notes on their own computer, and sometimes only there: then Troopa writes them but keeps none of them, only a record that the meeting happened.

Who decides. The person who used Troopa, or the organisation they work for. They decide whether to capture the conversation and what to keep, and it is their job to tell you. We handle the transcript on their behalf and use it for nothing else.

If you object. During the meeting, ask the person using Troopa to stop it. Afterwards, ask them to delete the meeting, which deletes its transcript and notes. Troopa cannot yet remove one person’s words from a transcript and leave the rest, so deleting the meeting is how it is done.

If you do not know who used Troopa, or they do not respond, write to support@troopa.ai. You do not need an account. Tell us roughly when the meeting was and who else was in it, and we will tell you which organisation holds it and help them act on your request.

Who we share data with, and international transfers

Our sub-processors. We share personal data with service providers who help us run Troopa, for hosting, storage, transcription, AI models, email, payments and product analytics, under contracts that bind them to confidentiality and to our instructions. They include Anthropic and OpenAI, whose AI models process meeting text. TypeSafe’s model reads a meeting’s newest lines to tell when Troopa is asked something. The apps you connect are listed with them, because Troopa sends them your question. The current list, with what each one sees and where, is at troopa.ai/subprocessors. We update it before a new company begins processing meeting content, and business customers who would like an email when it changes can ask at support@troopa.ai.

Companies that are not our sub-processors. Onelink (Sold through Link, LLC, a company in the Stripe group) sells the subscription as reseller and merchant of record, and takes payment. For payment data it is an independent controller under its own privacy policy. Google and Microsoft are where you sign in and where your calendar is, under your own agreements with them. Microsoft Teams, Zoom and Google Meet are not our service providers. They are where your meeting already happens, under your own agreement with them. On this website only, Google Analytics runs if you accept optional cookies, and Cloudflare Turnstile protects the Talk to us form. Neither sees anything of your meetings.

Other disclosures. We may also disclose personal data when you ask us to, for example by sharing a meeting, emailing notes, or connecting another app to Troopa, such as an AI assistant, which then receives what you allowed it to see, and adds to your meetings only if you allowed that too; or by continuing a request from Ask Troopa in your own Claude or ChatGPT, which receives a short prompt naming the meetings, and a summary of them only if you choose to send one; when the law requires it, or to respond to a valid legal request, which we will tell you about unless the law forbids it; to protect the rights, safety or property of our users, the public or Tellme; and to a buyer or successor if Tellme or its business is sold or reorganised, under the same protections as this policy. We do not sell personal data.

International transfers. Some processing takes place outside the UK and the European Economic Area, mainly the AI models in the United States, payments, and a question sent to an app you connected, wherever that app keeps its data. Where personal data is transferred, we rely on the adequacy findings the UK and the EU have made for each other, for the European Economic Area; on the EU–US Data Privacy Framework and its UK Extension, for a US company certified under it; and otherwise on the EU Standard Contractual Clauses, for data from the European Economic Area, and on the UK Addendum to them or the UK International Data Transfer Agreement, for data from the UK, with an assessment of the risks of the transfer. Ask us for a copy of the relevant safeguard.

How long we keep data

• Audio, video, and pictures of the screen: never stored.
• Transcripts, and what was asked of Troopa during the call: deleted automatically 365 days after the meeting, or sooner if your organisation sets a shorter period, or when the meeting is deleted.
• Notes, decisions, actions, boards and canvases, and notes of what was shared on screen: until the meeting is deleted, or your account is.
• Documents you add: until they are deleted, or the meeting they belong to is. A document you add while preparing a meeting that no meeting uses within 30 days is deleted then.
• Copies of decks and PDFs on your computer: the desktop app keeps the ones it shows, up to about 2 GB for each account, removes the least recently used first, and removes them all when you sign out or delete your account.
• Meetings on your computer: in local mode, where your organisation allows it, the desktop app keeps your transcripts and notes in a folder on your computer. A meeting that Troopa also keeps is removed from your computer when it is deleted in Troopa. Where Troopa offers it, a meeting can be kept only on your computer: Troopa transcribes it and writes its notes, then keeps none of it, only a record that it happened, how long it ran and who recorded it, and deleting it is done on your computer. A copy you move somewhere else is yours to delete.
• When your account is deleted: everything above is deleted within 30 days of your request, apart from the backups and files in the next line.
• Backups: deleted data can remain in our database backups until those backups expire, and the file of a deleted document can remain in our file storage for up to 35 days.
• Account data: for as long as your account exists, then deleted within 30 days.
• About your work: until you clear it in the app’s Settings, or as account data.
• Your organisation’s audit log, which records who did what, with IP address and device: for as long as the organisation exists.
• Sign-in sessions: up to 30 days.
• Request logs: 30 days. Server logs: 14 days.
• In-app notifications, which carry a meeting’s title and action items: 90 days.
• Calendar data: while your calendar is connected and shown; meetings Troopa recorded stay until deleted.
• Meetings you add in Troopa: until you delete them or your account; a deleted one is kept 15 minutes so you can put it back. Events Troopa added to your calendar stay there until you delete them in your calendar or in Troopa.
• Connected apps: an app’s access until you disconnect it, or a year after it was last used; your Obsidian notes until you remove them or disconnect Obsidian. Both go when you leave the organisation or your account is deleted.
• Update reports from the desktop app: 90 days.
• Usage analytics from the desktop app: replays 30 days, everything else 12 months.
• Billing records: six years after the transaction, as UK tax law requires.
• Support conversations: until your account is deleted.
• Feedback: until your account is deleted. A quote already on our website is taken down when you take back your consent.
• Ratings of Troopa’s cards: until the meeting or your account is deleted.
• Marketing preferences: until you unsubscribe; then your address stays on a suppression list so we do not email you again.
• Website cookies: as the cookie policy lists.

We may keep data longer where the law requires it, or where it is needed for a legal claim.

Your rights

Under UK and EU data protection law you may have the right to be informed, and the rights of access, rectification, erasure, objection, restriction of processing and data portability. In plain words: to know how your data is used, to have a copy, to have it corrected or deleted, to object to how we use it (always for direct marketing), to limit how we use it, and to take it with you in a machine-readable format. You can withdraw consent at any time where we rely on it. Troopa does not make decisions about you by automated means that have legal or similarly significant effects.

To use any of these rights, write to support@troopa.ai. It is free. We may ask you to confirm who you are, and we will answer within one month. If your request is about a meeting somebody else recorded, “If you would rather it was not there” above explains who decides and how we help.

Complaints. If you are unhappy with how we have handled your data, email support@troopa.ai with “Data complaint” in the subject line. We will acknowledge your complaint within 30 days, look into it, and tell you the outcome without undue delay. You can also complain to the UK Information Commissioner’s Office at ico.org.uk, or to the data protection authority where you live or work in the European Union.

If you are in the United States

Some US states give their residents rights over their personal data, such as the right to know what is collected, to access, correct and delete it, and to opt out of its sale, of targeted advertising and of profiling. You can use any of these rights by writing to support@troopa.ai, and we will not treat you differently for doing so. If we refuse a request, you can appeal by replying to our answer.

We do not sell personal data. This website uses Google advertising cookies only if you accept them, and you can refuse them or withdraw your choice in Cookie settings.

Do Not Track. There is no agreed standard for responding to a browser’s “Do Not Track” signal, so this website does not change its behaviour when it receives one. The cookie choice above is how you control tracking on it.

Security

We protect data with measures appropriate to the risk. Security describes them as they run, with the date they were last checked: encrypted connections, credentials sealed under a key held in the region, and passwords stored only as Argon2id hashes. Our staff access data only where their work needs it, and every reading of a meeting in our console, and every support session, is recorded, as “Who at Tellme can see them” above says. No system is perfectly secure. If a breach affects your data in a way that puts you at risk, we will tell you and, where the law requires, the regulator.

Children

Troopa is made for use at work. You must be 16 or older to use it, and we do not knowingly collect data about children. If you think a child has given us their data, tell us and we will delete it.

Changes to this policy

We will update this policy as Troopa changes. When a change matters, we will tell you by email or in the app before it applies, and say what changed. The date at the top shows when it last changed, and earlier versions are available on request.

If you connect your Zoom account

The desktop app does not need Troopa’s Zoom app. If you connected a Zoom account to Troopa, Zoom gave us your name, your email address, your Zoom user id, your Zoom account id, and a token. Nothing else: not your meetings, recordings, contacts, chats or settings, and Troopa cannot ask for them.

The token lets Troopa’s meeting bot, where an organisation has switched it on, join a Zoom meeting you sent it to. We use these for nothing else and share them with nobody. The token is encrypted before it is stored, and kept in the region your organisation chose.

In the meeting, the bot asks the host for permission to record before it captures anything, and Zoom shows its own recording indicator to everybody while it does. If the host says no, or nobody answers, Troopa leaves within two minutes and keeps nothing from that meeting.

To have them deleted, disconnect Zoom in Troopa, or write to us at support@troopa.ai.

This website

For our websites themselves, troopa.ai and related domains, Tellme AI Limited is the controller. We may use Google Analytics, Tag Manager or Ads on these pages, and only after you accept optional cookies. The choice is stored in a cookie we set ourselves. You can refuse, and you can change it later. The cookies, the legal basis, and how to withdraw are on the cookie policy.

Google LLC processes that analytics or ads data in the United States when you have consented. We do not join it to a transcript, a meeting, or an account.

The Talk to us form may use Cloudflare Turnstile to check that a message comes from a person rather than a script. It loads on that page only. Most people see nothing; now and then it shows a box to tick. While the page is open it sends Cloudflare what it needs to tell a person from a script, such as your IP address and details of your browser, and when you press Send it tells us whether the check passed. What you write in the form comes to us, not to Cloudflare. It does not set advertising cookies, and Cloudflare does not use what it sees to profile you or target advertising. Cloudflare, Inc. processes the check under the Turnstile privacy addendum. Our reason is a legitimate interest in keeping automated spam out of a mailbox people read. If it will not let you through, write to the address on that page instead.