The Translator That Doesn't Watch You Translate

Most translator apps log every query you make. TapSay can't — because there's no server to log it to.

By · · 6 min read

Why translation privacy actually matters

You probably don't think about translator privacy. Most queries are mundane — "where is the train station," "how much," "thank you." A log of these on someone's server is harmless.

Then you have the other queries. The ones travelers actually need translators for in moments that matter:

Each of these is a query you don't necessarily want sitting in a translation log indefinitely, associated with your IP address, your Google account, your device fingerprint. Most translation services are good actors — but "good actor with my data" is a weaker guarantee than "no data exists."

How translator apps handle your data: the honest comparison

Translator Translation queries sent to server? Account required? Telemetry / analytics? Truly offline-capable?
TapSay Never (no server exists) No GA4 page views (consent-gated) Yes (after one cache load)
Apple Translate No in on-device mode (iOS only) No (Apple ID already on device) Apple analytics (opt-out available) Yes (with downloaded languages)
Google Translate Yes when online; offline pack uses on-device Optional (features expand if signed in) Yes (Google analytics) Partially (text only, with packs)
Microsoft Translator Yes when online; offline pack uses on-device No Yes (Microsoft telemetry) Partially (with downloaded packs)
iTranslate Yes (sent to iTranslate servers) Required for Pro Yes (analytics + ad SDKs in free tier) Pro only, with packs
Bravolol No (static phrasebook) No Yes (analytics + ad SDKs in free tier) Yes

Important nuance: none of these apps are doing anything wrong. They have privacy policies, comply with GDPR, and process data for legitimate purposes (improving translations, ad targeting, telemetry). The question isn't "are they trustworthy?" — it's "do you want your translations on someone else's server at all?"

What TapSay actually does and doesn't do with your data

1

No translation queries leave your device. The phrasebook is static text bundled with the app. When you tap "I have a peanut allergy," nothing is sent anywhere — the phrase is already on your phone in 119 languages.

2

No account, no email, no signup. The free 45-phrase tier requires nothing. Paid trip passes use PayPal — TapSay never sees your card details (PayPal handles payment in their iframe).

3

No GPS or location tracking. TapSay doesn't ask for location permission. Country detection (used to suggest the local language) uses your phone's timezone and a one-time IP geolocation, both client-side.

4

Anonymous analytics with opt-out. TapSay uses Google Analytics 4 to understand which features are used. Loaded with consent denied by default — you can grant or revoke consent at any time via the "Consent Settings" link in the footer. Analytics only sees page views and feature interactions, never your translations or any personally identifying information.

5

Open-source assets where it matters. Logo, OG images, and brand assets are hosted on a public GitHub CDN (jsDelivr) so anyone can verify nothing is being secretly fetched. The PWA service worker code that handles offline caching is inspectable in your browser's DevTools.

The structural argument: why TapSay can't track you even if it wanted to

This is the part that matters: TapSay's privacy isn't a policy promise. It's a structural fact.

Google Translate's privacy policy could change tomorrow. iTranslate could be acquired by an ad-tech company. Microsoft could decide to use translation queries to train new models. None of these scenarios harm you under their current policies — but they're all possible because the architecture allows it. Your data is on their servers, and what happens to it depends on their goodwill.

TapSay's architecture doesn't allow it. There is no translation server. No translation API endpoint. No log of phrases tapped. The phrases are static files bundled into a 5MB Progressive Web App. Even if I wanted to start logging your queries tomorrow, I'd have to rebuild the entire app to add a server — at which point it would no longer be the same product.

This is why "data stays on your device" only counts when there's no architecture to take it off your device. Most "privacy-respecting" apps still ship a server you have to trust. TapSay ships no server.

When other apps are still the right choice

Privacy isn't free — TapSay's no-server architecture is what makes it private, but it's also why TapSay can't do free-form translation. Here's where other apps are genuinely better:

The honest stack: TapSay for the 90% of travel translations that fit a curated phrasebook (especially sensitive ones), plus a backup translator for the unpredictable 10%.

Frequently asked questions

Is TapSay GDPR compliant?

Yes. The simplest path to GDPR compliance is to not collect personal data, and TapSay's architecture takes that path. The only data TapSay processes is opt-in analytics (page views) and PayPal-handled payment for paid tiers. There are no translation logs to request, export, or delete. Full policy here.

Does TapSay work without giving it any permissions?

Yes. TapSay does not request location, camera, microphone, contacts, or any other phone permissions. It only needs network access (for the initial cache load) and storage access (for the cache). Both are implicit for any web app.

If I'm a journalist or activist, is TapSay safer than Google Translate?

Generally yes, for translation purposes specifically. Translation queries can reveal sources, locations, names. If your threat model includes "translation logs subpoenaed or breached," TapSay's no-server architecture eliminates that risk vector. For comprehensive operational security you should also consider VPN, encrypted messaging, and avoiding signed-in browsers when traveling.

What happens to my translations if I close the browser?

Nothing — they were never stored anywhere to begin with. TapSay does not maintain a translation history. If you want to remember a phrase, screenshot it.

Can I use TapSay anonymously through Tor?

Yes. TapSay works in Tor Browser. The initial cache load takes longer over Tor, but once cached the app works fully offline so Tor isn't needed for subsequent use. PayPal does not work over Tor for payment, so the free 45-phrase tier is what most Tor users will use.

Does TapSay use any third-party trackers or ad networks?

No ad networks. The only third-party JavaScript is Google Analytics 4 (loaded with consent denied by default) and PayPal (only on the payment page). No Facebook Pixel, no marketing trackers, no retargeting cookies.

The translator that doesn't watch you translate

45 free phrases across 12 categories. No account, no email, no card. Open in your browser, switch to airplane mode, and every translation stays on your device because there's nowhere else for it to go.

Try TapSay (free, no signup) →

Read next: