1. Summary
PollyGlott processes speech, text and translations only as needed to provide conversation translation features, operate billing entitlements, secure the service and support the product. The current beta product design uses ephemeral conversation retention: conversation text, translations, suggested replies and session metadata remain in process memory for the active app session and are not intentionally persisted across app restarts.
PollyGlott does not add website tracking, analytics or cookies on these legal pages.
2. Conversation text and audio
When you use translation features, PollyGlott may process spoken audio, transcribed text, typed text, translated text, suggested replies, target language settings and related session metadata. Recorded utterances are temporary inputs for transcription and should not be retained by PollyGlott after transcription completes unless a future save or export feature is explicitly added.
Conversation content is not supposed to be sent to product analytics. This includes source speech, transcript text, translated text, suggested replies, approved replies and raw audio. Operational analytics, if enabled, should be limited to non-content metadata such as app version, platform, language-pack ID, latency bucket, error class, paywall event, purchase product ID and coarse success or failure state.
The current implementation includes a persistence abstraction, but durable encrypted local history is not complete. Until encrypted local history, user-visible retention controls, deletion controls, export and tests are implemented, durable history remains disabled by product policy.
3. Global mode and mainland China mode
In Global mode, conversation audio or text may be sent to PollyGlott backend endpoints and remote service providers for transcription, translation, reply suggestion or text-to-speech support. Provider credentials are not shipped in the mobile app bundle.
The mainland China operating profile is designed to disable remote AI calls during translation and operate on device after required language models, permissions and paid entitlement leases are prepared. In that mode, translation processing is designed to stay on the device during prepared offline use. Device capability, operating-system language model availability and permission status can affect whether offline conversation works.
4. Billing, subscriptions and Travel Passes
Billing providers may process purchase, subscription and checkout information. PollyGlott uses RevenueCat for subscription entitlement synchronization across Apple, Google and RevenueCat Web or Stripe flows. Dynamic Travel Pass checkout uses server-owned pricing and Stripe/web payment verification before a device-bound lease is issued.
Billing and entitlement processing may involve product IDs, plan, platform, payment rail, RevenueCat App User ID or similar billing subject, transaction or checkout identifiers, travel duration, lease expiration, device-binding subject and coarse purchase outcome. Billing analytics must not include transcript text, audio, translated text or suggested replies.
Apple, Google, Stripe and RevenueCat process information under their own terms and privacy policies when you use their purchase rails.
5. Device permissions
Microphone access is used only when you start a live conversation or recording flow. Speech recognition permission may be required to turn conversation audio into text, including on-device speech recognition where supported. Text-to-speech uses the device or configured speech provider to speak translated text or approved replies.
Location collection is off by default. Translation does not require location. PollyGlott may attach location to conversation history only after explicit user permission and an explicit feature that needs it. The current product policy treats location as absent by default.
6. Retention
Current beta conversation retention is ephemeral. Conversation content is not intentionally retained by PollyGlott across app restarts. Temporary processing by operating systems, backend services or remote providers may occur while providing the requested feature, and provider retention must be reviewed before any production AI or speech provider is enabled.
Billing, entitlement, checkout, refund, chargeback, security and operational records may be retained as needed to provide access, resolve disputes, prevent abuse, satisfy accounting obligations and comply with law. Device-bound offline leases remain on the device until replaced, expired, removed or invalidated by the app or operating system.
7. Security
PollyGlott separates provider credentials from the mobile bundle and uses backend endpoints for operations that require server-side secrets. Offline entitlement leases are designed to use server-side signing, local public-key verification and this-device-only secure storage. Expired, malformed, invalid-signature or wrong-device leases should fail closed.
No system can be guaranteed perfectly secure. Do not provide passwords, payment card numbers in conversation text, sensitive legal or medical details, or other unnecessary high-risk information unless you accept the risks of using a translation tool for that content.
8. Choices, children and contact
You can control microphone, speech recognition and location permissions through your device settings. You can cancel subscriptions through the purchase rail where you subscribed. You can stop using PollyGlott at any time.
PollyGlott is intended for general consumer use and is not directed to young children. Minors should use PollyGlott only with appropriate parent or guardian involvement and consistent with applicable law and store account rules.
Depending on where you live, you may have legal rights to request access, correction, deletion, portability or objection for certain personal information. Because the public site does not currently publish a physical mailing address or a specific privacy email address, those details are not invented here. Use the support channel published by Pupfish Soft when available.