Privacy Policy

1. Information we collect

We process the information needed to provide and secure TIAB, including:

• Account information. Your email address, Supabase user ID, authentication records, and session information.
• Content you choose to save. Vocabulary expressions, meanings, pronunciation, examples, notes, language-bank settings, encounter dates, source titles and URLs, and selected source context when you save it.
• Learning activity. Quiz sessions and answers, review outcomes, familiarity scores, widget recall outcomes, and product settings that support learning and recall features.
• Capture and diagnostic data. Capture-pipeline records use presence flags rather than raw expressions, meanings, URLs, or context. These flags are cleared opportunistically after 24 hours. We may also process limited error and request logs to operate and secure the service.
• Product analytics. TIAB uses PostHog for limited, allowlisted product events, such as screen views, app lifecycle events, capture methods, and quiz modes, under your authenticated Supabase user ID. We do not send raw vocabulary, notes, saved context, source text, source URLs, or authentication tokens to PostHog. Mobile session replay is disabled.
• Advertising data. TIAB uses Google Mobile Ads to display advertising. When ads are enabled, Google may automatically process and share IP addresses, app and ad interactions, diagnostic and performance information, and device or account identifiers for ad delivery, measurement, analytics, frequency limiting, and fraud prevention. IP addresses may be used to estimate general location. TIAB does not send your saved vocabulary, notes, source text, source URLs, email address, or Supabase user ID to Google Mobile Ads.

The Save source text setting is on by default. Turning it off prevents future source context from being stored; it does not remove context you saved previously.

2. Camera, images, and voice input

On supported iOS devices, TIAB can use the camera or photo library for Live Text recognition. Text recognition happens on your device. By default, a camera image stays in memory while you capture text and is not uploaded to TIAB.

If you explicitly enable Keep photo for recall and save an entry, TIAB saves a display-sized copy of the camera image to your device's Photos library and keeps only its opaque, device-local Photos asset identifier. The image is never sent to TIAB's server or synced by TIAB. Deleting it from Photos or revoking photo access can make that reference unavailable in TIAB.

Audio input on supported iOS 26 or later devices uses Apple's on-device speech transcription. Microphone input requests microphone access and does not save a recording. Device audio uses Apple's broadcast picker to capture available playback audio while you visit another app. TIAB discards the broadcast's screen video and microphone audio, and temporarily saves up to two minutes of device audio in protected local storage excluded from backups. Returning to TIAB finishes the recording and transcribes it on your device.

Temporary recordings are deleted after transcription, cancellation, or an error. If the app closes unexpectedly before cleanup, recordings older than one hour are deleted the next time you start Device audio. Audio is not uploaded to Apple's speech servers or TIAB's servers; downloading the initial language model may require an internet connection. You can review and edit the transcript before requesting a meaning or saving it. That text follows the same processing and storage rules as typed vocabulary.

3. AI-assisted meanings

If you leave a meaning blank and request a suggestion, TIAB may send the selected expression and its source and target language codes to OpenAI to suggest a meaning, pronunciation, part of speech, or example. TIAB does not send your original context, source URL, source title, notes, user identifier, or Supabase token in that request. OpenAI requests use API storage disabled.

Batch vocabulary analysis is different because the surrounding text is needed to identify words and expressions in context. Before the first batch analysis on a device, TIAB tells you that the complete text you selected, pasted, shared, or recognized on-device from an image, together with its language pair, will be sent to OpenAI. You can cancel instead. TIAB does not send the image, source URL or title, notes, user identifier, or authentication token, and OpenAI API storage is disabled. Turning off Save source text prevents the passage and its source-derived sentences from being saved after this transient analysis.

Validated results may be cached in your private, account-scoped TIAB account to reduce repeated AI requests and support quality review. AI suggestions can be incomplete or inaccurate, so review or edit them before saving. Listen playback uses your operating system's text-to- speech service; TIAB does not send the expression through its backend or retain generated audio.

4. Source previews and third-party content

When you share a public Threads or X post link, TIAB may retrieve its public title and post text to prefill the editable confirmation sheet. TIAB does not cache that post text as source-preview metadata. It is stored as source context only if you save the capture while Save source text is enabled.

When you open an entry with a public source link, TIAB may retrieve a preview title, image URL, and fetch time. TIAB does not store the page text for that preview. Displaying a preview image connects your device to the image host. YouTube sources use a privacy-enhancedyoutube-nocookie.com player that loads only after you choose to play a video.

5. How we use information

We use information to:

• authenticate you and keep your account secure;
• store, search, organize, and recall your vocabulary;
• provide quizzes, widgets, source previews, and AI-assisted meanings;
• synchronize data across supported devices and connected AI clients you authorize;
• detect abuse, troubleshoot failures, and improve TIAB;
• deliver, limit, measure, and protect advertising; and
• comply with applicable legal obligations.

6. Service providers and international processing

TIAB relies on service providers that process information on our behalf:

• Supabase for authentication and database services;
• Vercel for API hosting;
• OpenAI for optional AI-assisted meaning suggestions;
• PostHog for privacy-filtered product analytics;
• Google Mobile Ads for advertising delivery, measurement, analytics, and fraud prevention. Learn more in Google's information for sites and apps that use Google services;
• public source, image, or video hosts when you share or open related content.

These providers may process information in countries other than your own and apply their own security, subprocessors, and retention practices.

7. Retention and account deletion

We keep account content while your account is active or as needed to provide TIAB. Operational logs, backups, and third-party service records may remain for limited periods under provider retention schedules or legal requirements.

Google retains and deletes advertising data according to its own policies and the controls available through Google Mobile Ads. TIAB its own database.

You can delete your account in Settings → Account → Delete account. Deletion revokes refresh sessions, removes the Supabase Auth identity, and permanently deletes account-linked TIAB data, including vocabulary, banks, encounters, quizzes, and recall history. It also clears the local TIAB session and related app state. This action cannot be undone.

8. Security

TIAB uses encrypted network connections, managed encryption at rest, row-level access controls, and platform Keychain protections for shared iOS credentials. No system is perfectly secure, so we cannot guarantee absolute security.

9. Your choices and rights

You can edit or delete individual entries, archive vocabulary, disable future source-context storage, change your password, sign out, and delete your account in the app. Depending on your location, you may also have rights to access, correct, export, restrict, object to, or erase personal information.

Where required, TIAB asks for advertising consent before requesting an ad. If Google requires ongoing privacy choices for your region, you can reopen them from Settings → Privacy → Ad privacy choices. You can also use your device settings to limit or reset its advertising identifier. Your choice may change whether ads are personalized, but you may continue to see contextual or limited ads.

To make a privacy request, email admin@sudamate.com. We may need to verify your identity before completing a request.

10. Children

TIAB is not directed to children under 13, or the higher minimum age required in their country. We do not knowingly collect personal information from children who cannot legally consent to use the service.

11. Changes to this policy

We may update this policy as TIAB changes. We will update the effective date and provide additional notice when required.

12. Related terms

Your use of TIAB is also subject to the Terms of Use.