Last updated: 25 October 2026.
ThirdEye looks at your screen when you ask it to, and in Live mode it listens to a conversation while you have Live switched on. Screens and conversations can contain messages, credentials, personal data and information about other people. This policy explains, in full, what ThirdEye processes, what leaves your Mac, where it goes, how long anything is kept, and the rights you have. It applies to the ThirdEye app for Mac (including Live mode), ThirdEye Companion for iPhone, the ThirdEye analysis service and the ThirdEye website.
ThirdEye is a tool for preparation and practice only. It must not be used during a real interview, examination, test, assessment or any other situation in which outside assistance or tools of this kind are not permitted. How you use ThirdEye, and whether a given use is allowed, is your sole responsibility. The rules that govern this are set out in our Terms of use, which you accept by creating an account or using ThirdEye.
Who is responsible
The controller responsible for processing personal data in connection with ThirdEye within the meaning of the EU General Data Protection Regulation (GDPR) is:
Kanishk Kashayap, Stuntzstraße 18, 81677 München, Germany (Impressum).
Email: support@thirdeye-app.com
In this policy, “ThirdEye”, “we” and “us” refer to the controller named above.
Screen analysis (triggers)
When it happens. ThirdEye captures the display under your pointer only when you trigger it with your keyboard shortcut or hot corner. It does not capture continuously or in the background.
What happens on your Mac.
- The still frame is captured into memory, reduced in size and encoded. It is never written to disk. ThirdEye’s own windows are excluded from every capture.
- The text visible on that frame is read on your Mac, using macOS’s built-in text recognition. Nothing is uploaded to do this.
What leaves your Mac. Each trigger sends the still frame and the text read from it to ThirdEye’s analysis service. The service uses the text to decide what kind of question is on screen (a coding problem or a multiple-choice question) and to find coding problems in ThirdEye’s stored library:
- If the problem is in ThirdEye’s library, the stored answer is returned and nothing is sent to an AI provider.
- If it is a coding problem that is not in the library, the frame and the text are sent to the AI provider, and the answer is streamed back to your Mac as it is written.
- Otherwise the service treats it as a multiple-choice question and sends only the frame to the AI provider. The text read on your Mac is used for routing and is not forwarded on this path.
Requests to the AI provider are made with the provider’s storage feature turned off. The service does not keep the frame, the text read from it, the prompt or the answer once the request is complete.
Live mode
Live mode follows a conversation you are having, for example a mock interview or a practice session, and suggests answers to questions it hears. Live only runs while you have switched it on, and you can switch it off at any time.
Audio.
- Live always listens to your microphone. In meeting mode it also listens to the audio of the meeting apps and browsers you select, using macOS’s screen and audio recording permission (audio only; no video or screen images are processed for this). A selected browser’s audio includes all of its tabs.
- Speech is turned into text on your Mac. The speech-recognition model runs locally. Audio never leaves your Mac and is never recorded or saved.
- The speech model (about 670 MB) is downloaded once, on request, from Hugging Face and stored inside ThirdEye’s app container on your Mac. Hugging Face receives the technical data that any download involves (such as your IP address); it receives nothing about you or your conversations.
What is sent to answer a question. When Live detects a question, it sends a request through ThirdEye’s service to an AI model. Each request can contain:
- the question, roughly the last 45 seconds of the conversation as text (labelled as you or the other speaker), recent topics and up to the last three questions, and the beginnings of answers already shown;
- your profile (see “Personal context” below), if you have set one up;
- the result of your most recent screen capture taken while Live was on (for a coding problem, its title, code and complexities; for a multiple-choice question, the question, the chosen option and the reasoning).
The AI model used by Live is an Anthropic Claude model provided through Microsoft Azure AI Foundry. To answer faster, the provider may briefly cache the repeated parts of a request (your profile and your latest capture) for up to one hour. ThirdEye’s service relays each request and its answer in memory only; it does not log, trace or store the conversation, the question, the profile or the answer.
Your latest capture. While Live is on, the result of your most recent trigger is kept in memory so Live can talk about it. For a coding answer, it is passed to Live piece by piece as it is written (the code and its complexity only), and one additional request asks the AI model for a short explanation of the solution, which is used only as context and is never shown or stored.
When Live stops. Everything Live produced or received during the session (transcripts, questions, suggested answers, the latest capture and the explanation) is held in memory only and is erased when Live stops, including when your Mac sleeps or locks, when you sign out and when you quit ThirdEye.
Personal context (résumé and notes).
- You may add a résumé (PDF, Word, RTF, text or Markdown) and type notes about your experience. ThirdEye keeps only a read-only reference to the résumé file; the file itself is not copied. The text is read on your Mac.
- If “Use AI notes from my resume” is on (it is on by default), the work-experience part of your résumé is sent once per résumé to the AI model to write short notes. Those notes are saved in a private file in ThirdEye’s container on your Mac.
- Your profile (your typed notes and the AI notes, or a short keyword profile if AI notes are off) is sent with every Live answer request and may be cached by the provider for up to one hour, as described above.
- Removing the résumé in Live settings deletes the reference and the saved AI notes. Your typed notes are removed by clearing the field.
Eye contact (camera). If you turn on the eye-contact feature, ThirdEye uses your camera only while Live is listening, the feature is on and its preview is open. Camera frames, face crops and facial landmarks are processed on your Mac with Apple’s Vision framework, held in memory only, and never recorded, saved or sent. This feature is off by default.
Usage records for Live. For each Live request, ThirdEye records content-free information only: identifiers, timings, status codes, token counts and the estimated cost, added to your usage totals. Each Live session is also recorded with its start and end time, the number of answers and its estimated cost, so it appears on your dashboard and counts towards your usage limit. No audio and no text from the conversation is recorded.
Other people in your conversations
Live processes the speech of everyone it can hear, not just yours. Laws in many countries, including Germany (section 201 of the German Criminal Code), protect the confidentiality of the spoken word and may require the consent of other participants before their words are recorded, transcribed or processed. You are solely responsible for informing the other participants and obtaining any consent that the law, your employer, the organiser or the platform requires before you use Live. Do not use Live in any conversation where you are not permitted to do so.
ThirdEye Companion for iPhone
ThirdEye Companion shows ThirdEye’s answers from your Mac, and Live’s transcript lines and suggestions, on your iPhone.
What the iPhone app sends to us.
- When you pair: a pairing code, a public key the iPhone creates for itself, the iPhone’s name, and whether it uses Apple’s test or production notification service.
- After pairing: the iPhone’s Apple push notification token, so we can tell it something is ready, and short receipts saying which items arrived (an identifier only, never the content).
What passes through us.
- When your iPhone is near your Mac, answers and Live lines go directly from the Mac to the iPhone over your local network, encrypted end to end, without passing through us.
- When it is not, an answer travels through our servers and is held in memory only for at most 15 minutes until your iPhone collects it. Live’s final transcript lines and suggestions, and the start and state of a Live session, are held in memory only for at most 10 minutes for an iPhone that is locked or suspended. Partial lines are never held. Nothing of this is written to a database or to logs.
- Push notifications never contain an answer or any conversation text. They say only “You have a new update”.
What stays on your iPhone. Your answers are stored only on your iPhone, for up to 30 days, and you can delete them at any time. Your companion sign-in is kept in the iPhone’s Keychain.
Disconnecting. Disconnect from the iPhone or the Mac at any time. This removes the iPhone’s registration, its push token and its sign-in from our servers, and deletes the answers saved on the iPhone.
What we don’t do. No advertising, no tracking, and no analytics or third-party SDKs in the iPhone app. We never sell your data.
What we keep
- Account data. A minimal account profile so you can sign in (identifiers from your sign-in provider, your verified email address and your display name, stored encrypted where they identify you), and which Mac and which iPhone are linked to your account. We do not keep your sign-in provider’s access tokens, your avatar or your provider username.
- Usage. Per-day totals (number of requests, token counts and estimated costs) to apply limits and quotas. These are kept while your account exists and afterwards only as long as accounting and legal obligations require.
- Request metadata. For screen analysis, a short-lived record per request linked to your account, containing banded sizes and timings, the kind of request, its status and the time to the minute. These records are shown in your dashboard’s activity list and are deleted automatically after 30 to 60 days.
- Usage and cost records. For each screen-analysis request, a record linked to your account with the time (to the second), the request identifier, the kind of request and its status, the exact number of tokens sent and received, and the estimated cost; and for each Live session, its start and end time, number of answers and estimated cost. Token counts and costs describe only the size of a request, not what it contained. We use these records to apply your usage limit (for example, a monthly allowance per billing period), to show your usage, and to answer billing questions, refund requests and payment disputes. They are deleted automatically after 180 days, or earlier if you delete your account.
- None of these records ever contain the screenshot, the text read from it, the conversation, the prompt or the answer. Operational logs and our observability service (Langfuse) receive metadata only.
- Support requests you send us, encrypted, for as long as needed to handle them.
Payments
Payments are processed by Paddle, our merchant of record. Your card or other payment details go to Paddle and are handled under Paddle’s privacy policy; ThirdEye never sees or stores your full card number. From Paddle we keep only what we need to run your subscription: the Paddle customer, subscription and transaction identifiers, your plan and billing period, the amount and currency, the payment and subscription status, and the card brand and last four digits.
Discount codes. If we send you a discount code, we store a fingerprint of the code (not the code itself), your email address in encrypted form and as a fingerprint, the discount and its expiry date, and whether and when it was used and by which account. A code works only for the account with that email address. When you use it, we create a matching one-time discount at Paddle and attach it to your checkout; Paddle receives the discount, not your email address. Records we are legally required to keep for tax and accounting purposes are kept for the statutory periods.
What the app keeps on your Mac
- Your settings (trigger, overlay style, Live preferences and the other choices in Settings). Never any answer, screen text or conversation.
- One sign-in credential in the macOS Keychain, not synced to other devices.
- For Live: the speech model, the reference to your résumé, your typed notes and the AI notes file described above.
- No answers. Copy an answer to the clipboard when you need it.
Website analytics
We use Cloudflare Web Analytics, which is cookieless and does not track individuals. It counts page views and records the page, the referring site, the browser and device type, the country and page-load timings, without cookies, local storage or fingerprinting, so we can see how the website is used and how fast it loads.
Who receives data (recipients and processors)
We use the following service providers, each only for the purpose stated and, where they act on our behalf, under a data processing agreement:
- Microsoft (Azure): hosting of ThirdEye’s servers and database; the AI model for screen analysis (Azure OpenAI); and the Anthropic Claude model for Live (Azure AI Foundry).
- Paddle: payments, as merchant of record.
- Apple: delivery of push notifications to ThirdEye Companion (content-free).
- Google and GitHub: signing in, if you choose them.
- Cloudflare: hosting and security of the website, and cookieless website analytics.
- Resend: sending emails such as invitations and support confirmations.
- Hugging Face: the one-time download of Live’s speech model.
- Langfuse: operational metadata only.
Some of these providers process data outside the European Economic Area. Where they do, the transfer is protected by an adequacy decision (such as the EU–US Data Privacy Framework) or by the European Commission’s standard contractual clauses. The AI providers’ own terms may allow them to keep limited data for a short time to detect abuse; requests are made with storage features turned off wherever the provider offers it.
Legal bases
- Providing ThirdEye (account, screen analysis, Live, the companion, support): Art. 6(1)(b) GDPR, performance of our contract with you.
- Security, abuse prevention, limits, and content-free operational metadata: Art. 6(1)(f) GDPR, our legitimate interest in running a secure and reliable service.
- Cookieless website analytics: Art. 6(1)(f) GDPR, our legitimate interest in understanding how the website is used and keeping it fast.
- Usage and cost records (applying your usage limit and showing your usage): Art. 6(1)(b) GDPR; handling billing questions, refund requests and payment disputes with them: Art. 6(1)(f) GDPR, our legitimate interest in establishing and defending payment claims.
- Discount codes: Art. 6(1)(b) GDPR, applying the discount we offered you.
- Keeping payment and tax records: Art. 6(1)(c) GDPR, legal obligations.
- Camera, microphone and screen recording are used only after you grant the corresponding macOS permission and switch on the feature, and you can withdraw that permission in System Settings at any time.
Your rights
You have the right to access your personal data, to have it corrected or erased, to restrict its processing, to data portability, and to object to processing based on legitimate interests. You may delete your account at any time; this deletes your account data, subject to records we must keep by law. To exercise your rights, email support@thirdeye-app.com.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work, or with the authority responsible for us: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany.
Children
ThirdEye is not intended for anyone under 16, and we do not knowingly process their data.
Your responsibility
- Capture only content you are authorised to send, and use Live only in conversations where you are permitted to, with any consent the law or the other participants require.
- ThirdEye, ThirdEye Companion and Live are for preparation and practice only: practice questions, coding problems, mock interviews and study. They must not be used during real interviews, examinations, tests, certifications or any other assessment in which outside assistance or tools of this kind are not permitted.
- Whether a particular use is allowed is for you to determine, and you alone bear responsibility for how you use ThirdEye. See our Terms of use, in particular “Acceptable use” and “Your responsibility for fair use”.
Changes to this policy
We will update this policy when ThirdEye changes how it processes data, and change the date at the top. Material changes will be announced in the app or by email before they take effect.
Questions about privacy? Email support@thirdeye-app.com or use the contact form.
