Product privacy

Dubsy Video Translator privacy policy

Updated: 8 November 2026

This policy applies to the Dubsy Video Translator add-on for Google Drive™, offered by Innova Apps. It describes this add-on's data use, including its shared translation service. The separate iPhone app has its own account and purchase flow. Contact support@innovaapps.ai with privacy questions.

What we access

• Account identity: a signed Google identity token used to verify the signed-in account. The service derives an account reference from the verified account identifier to track credits and translation ownership.
• Selected files: the identifier, name, format, size, duration and version of a video you select and authorize. When you start a translation, the service reads that video's contents.
• Translation records: language choices, video duration, request and job identifiers, timestamps, progress, errors, credit charges or refunds, and generated-file references.
• Output files: when you choose Save to Drive, the service creates the Dubsy translations folder when needed and saves the translated MP4 there. It accesses the folder and files it creates to complete or recover that save.
• Purchase records: the add-on account reference, selected credit pack, amount and currency, payment identifiers, timestamps, payment status, credit-grant records and refund or dispute information needed to manage your balance.
• Support and operational information: information you send to support and technical service diagnostics needed to investigate errors, maintain reliability and protect the service.

The add-on uses per-file authorization. It does not request unrestricted access to all files in your Google Drive™ account. Google may display account or profile permissions as part of its installation flow. The translation service uses the verified account identifier, rather than a name or email entered into a form, to determine job ownership.

How videos and authorization travel

The add-on sends small authenticated requests to our backend on Google Cloud™. For a file action, it sends a short-lived Google OAuth access token so the backend can act on the authorized file. The backend verifies that the identity and file-access authorization belong to the same user and approved app.

Source video is streamed from Google Drive™ through a backend worker into private Microsoft Azure storage. Microsoft Azure's video translation service processes the video and speech and produces translated media. This can include generated speech based on voices in the source video. Only submit recordings you have the rights and any required consent to process in this way. When you request a save, a backend worker streams the translated result to your account. Video contents are not buffered in the add-on's sidebar code.

Google provides account authorization, the add-on host, backend hosting and database services. Microsoft Azure provides media storage and translation processing. These providers process data needed to supply their respective services. Data may be processed outside your country; this release does not promise a customer-selected storage region or that all processing remains in one country.

Payments

Stripe hosts checkout and processes the payment details you provide there, which may include your card or other payment-method details, email and billing information. Dubsy does not receive or store full card numbers or security codes. We send Stripe the selected pack and payment references linked to your add-on account so a confirmed purchase can fund the correct balance. We do not send Stripe your selected videos or Google authorization tokens. Stripe's handling of payment information is described in its privacy policy.

Why we use the data

We use this information to authenticate you, check file access, carry out requested translations and saves, display progress and recent jobs, fulfill purchases, investigate payment problems, enforce credits and service limits, recover interrupted work, prevent abuse, and respond to support requests. We do not sell Google user data, use it for advertising, or use it to build unrelated user profiles. We do not use Google user data to train generalized AI models.

Dubsy Video Translator's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Human access to user data is limited to permitted purposes, such as investigating a specific issue you authorize, security, or complying with applicable law.

Storage, retention and security

Raw Google identity tokens are used for authentication and are not intentionally saved in application records. Short-lived file-access tokens needed by queued transfers are encrypted in server-only records. These records are deleted when the transfer completes or fails and have an expiry-based cleanup policy. Expiry prevents continued use; background deletion is asynchronous and is not a promise of erasure at that exact instant. The service does not request offline refresh tokens.

Small pending-start records in the add-on's user settings contain a file identifier, request identifier, languages and timestamp, but no authorization tokens or video contents. They help recover a lost response. At most ten unresolved records are retained by this workflow; records older than 24 hours stop being used and are removed during subsequent access. Closing the sidebar is not proof of immediate deletion.

Account, credit and job records are stored in the backend database. Source videos and generated results are stored in Microsoft Azure to process and recover translations. This release does not provide a guaranteed automatic deletion period for these media, account or job records. Failed imports attempt to remove their incomplete source copy; a storage or network failure may delay cleanup. Contact support for a verified deletion request.

Necessary purchase, credit-grant and payment-recovery records may be retained to reconcile payments, prevent duplicate credits, resolve refunds or disputes, and meet applicable financial-record obligations. A deletion request does not automatically erase these records or cancel an unresolved payment. We limit retained information to what those purposes require; Stripe also maintains records under its own policies and applicable obligations.

Saved output files remain in your Google Drive™ account until you remove them, subject to Google's storage and recovery behavior. They are distinct from service-side copies. Transport uses HTTPS, stored delegation is encrypted, and the backend checks account ownership before returning job information. These controls do not make any service risk-free.

Your choices and deletion requests

You choose each source file and whether to start a translation or save a result. You can revoke the app's access in your Google account settings. Revocation prevents future authorized access but does not delete copies already transferred to the service. Uninstalling the add-on, deleting an output file and deleting service records are separate actions.

To request access, correction or deletion, email support@innovaapps.ai. Include your account reference (from Home, open Credits & help and expand Account reference) and the relevant job reference if available; do not send passwords or access tokens. We verify the requester's identity and explain what can be removed and any records that must be retained for security, resolving disputes or applicable legal obligations. There is no automatic account-deletion button in this release. Provider backups and records are subject to their separate deletion processes.

Contact and updates

Innova Apps, Tove Maës vej 1, 1 TH, 2500 Valby, Denmark. CVR 45291154. Email: support@innovaapps.ai.

We may update this policy as the product changes. The date above identifies this version. Material changes will be reflected in the product's public information and, where required, communicated to affected users.