Privacy Policy
This policy reflects the current Senvariq Live Translator and Travel Companion architecture, including optional account linking, Gateway-verified entitlements, online enrichment and PRO+ AI. Before public-store launch, Senvariq will re-check this text, the Google Play Data Safety disclosure and the actual production SDK/provider configuration.
Senvariq Live Translator
Senvariq Live Translator is designed to perform speech recognition and translation using Android/on-device services where available. Senvariq Data Packs are downloaded from Senvariq only when the user chooses to install them.
Permissions
Microphone, Nearby Devices/Bluetooth, camera, location, notifications and related Android capabilities are requested only when required by user-selected features. The app explains relevant permission use before the Android system prompt.
Support
Information voluntarily sent to support@senvariq.com is used to respond to support requests.
Support Preview and Installation IDs
If you use private support testing, Senvariq may associate your member account with a random app Installation ID, app/device version metadata, optional country code, a public cryptographic proof-key fingerprint, assigned Support Preview releases and download/verification records. The Installation ID does not contain an IMEI, serial number, advertising ID or account data, and the private proof key never leaves Android Keystore. This information is used only to deliver, secure and troubleshoot support releases.
Email subscriptions and marketing
If you subscribe to Senvariq email news, we store your email address, optional name, language preference, consent source and timestamps, delivery status and unsubscribe/suppression status. We use this information to send requested news and promotions, enforce consent and suppression rules, and operate the mailing queue. Click tracking is off by default. You may unsubscribe at any time.
Accounts, country, referrals and promotional offers
For member accounts, Senvariq stores account identity and security information, your selected country / region of residence, plan and consent status, referral attribution, promotional-offer claims and account-inbox campaign messages needed to provide these features. Country is supplied by you and is not silently inferred from GPS or IP location. Password-reset links use short-lived random tokens; only a cryptographic token hash is stored. Referral and offer records are used for eligibility, anti-abuse, redemption and reward auditing.
Accounts and plan choices
FREE and ordinary PRO (24-hour, 7-day or Lifetime) do not require a Senvariq website account. A customer may use a store-verified PRO entitlement without linking the app to senvariq.com. PRO+ AI is an ongoing cloud service and requires a Senvariq account for service identity, metering, recovery and support. Creating or linking an account does not itself grant a paid plan.
App linking and plan verification
If you choose to link the Senvariq Android app to your website account, Senvariq stores the app installation identifier, device/public-key metadata and a gateway-verified entitlement snapshot such as FREE, PRO or PRO+ AI and enrichment-credit balance. Linking does not send your trips, itinerary documents, translations, microphone audio or Travel Companion content to the website. You can revoke a linked installation from your account. Linking is optional for FREE and ordinary PRO and does not itself grant paid access.
Purchases, entitlements, refunds and support IDs
When production store billing is enabled, Senvariq may process store purchase/order references, plan/capability status, an app support Installation ID, an opaque service installation ID and entitlement audit records to verify access, troubleshoot purchases, process cancellations/chargebacks and revoke access after a legitimate refund. Production paid access is not granted manually from the website. Some Gateway audit surfaces store installation identifiers as SHA-256 hashes.
Online AI and enrichment
Offline features are designed to stay on the device after required models/data are installed. When a PRO+ AI user deliberately uses an online AI feature, the text needed for that request is sent through the Senvariq Gateway to the configured AI provider; Senvariq Gateway application code does not write translation text to D1. Online place enrichment sends the venue/location fields needed for the lookup to the configured place provider. Provider processing is subject to the provider configuration actually enabled in production.
Retention, deletion and backups
Account data is kept while the account is active and may be removed through supported deletion flows, subject to records that must be retained for security, fraud prevention, transaction/audit integrity, backups or legal obligations. App linking can be revoked without cancelling a valid production purchase. Backup copies may persist until their normal protected retention cycle completes.
Security and incident response
Senvariq uses HTTPS, server-only secrets, hashed reset/pairing tokens, Android Keystore proof keys and separated entitlement-control secrets where implemented. No Internet service can be guaranteed perfectly secure. Senvariq maintains containment, credential-rotation, session-revocation, evidence-preservation, recovery and notification procedures for suspected security incidents.
Website analytics
Senvariq may use optional Google Analytics or Google Tag Manager to measure public-site usage. When the consent gate is enabled, no Google measurement script loads until you accept analytics. Your choice is stored in your browser so the site can remember it.
Retired community place contributions
The former Community Travel Knowledge contribution workflow is retired. Historical submissions may be retained for moderation, audit and recovery according to Senvariq retention practices, but no new submissions are accepted and they are not an active Data Pack publication source.
Production review required
This policy must be reviewed before Play Store publication to reflect analytics, crash reporting, billing and any server-side services actually enabled in the release build.
