Privacy Policy

Last updated: October 26, 2026

This policy covers Creative Renamer for Yango Play and Yasmina, its file-processing worker, and its delivery integration with Content Hub. For questions or requests about your data, contact the service administrator at artgolubtsov@gmail.com.

Data we process

When you submit a task, we process the source links, files and folders you identify; file names, identifiers, types, sizes, dimensions and video durations; and campaign information you supply. Campaign information can include names, markets, languages, agency, ad copy, landing pages, notes, creator names and Spark codes. We also process the submitting user's identity and role from Content Hub, job status, timestamps and diagnostic records needed to operate and troubleshoot the service.

Google Drive access and use

The connected account owner authorizes Google Drive access through OAuth. Our server uses the authorization to read submitted source files and folder contents, check access, and create delivery folders, renamed copies and sharing links in the configured destination. We use file metadata to validate inputs, name outputs and avoid duplicate transfers. We do not use this authorization to browse unrelated Drive content for other purposes.

The current integration uses the https://www.googleapis.com/auth/drive scope. This scope permits broad Drive access because the workflow accepts existing file and folder links without a Google Picker selection. Submit only materials you have permission to process and share. Renaming creates output copies; it does not rename the source files.

We use Google user data to provide these file-processing and delivery features. We do not sell that data, use it for advertising targeting, or use it to train general-purpose AI models. Creative Renamer's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and sharing

• Google Drive: we store prepared delivery copies in the connected destination account. The delivery workflow creates reader access for anyone with the output link. A recipient can forward that link; do not submit material that must remain restricted to named recipients.
• Backup storage: we also transfer copies of processed materials to a separate backup storage provider for recovery. Changing or deleting a Google copy does not remove this backup.
• Content Hub and its database: we store package metadata, file links, processing state and history. Some processing paths also store source-content chunks so jobs can resume.
• Agency delivery: when you or an authorized team member releases a package, or you enable auto-release, we send the relevant campaign metadata and links to the selected agency's spreadsheet and notification destination, including Google Sheets and Telegram. Access to those destinations follows their own sharing settings.

Hosting and storage providers process data as part of running the service. Authorized administrators may access task data to support a request, investigate failures or maintain security. Agency recipients may download their own copies. We cannot remove copies that recipients keep outside the systems we control.

Credentials and browser storage

We transmit data to our web service over HTTPS and restrict job submission and administrative operations through access controls. OAuth grants let our server access the connected account without receiving its Google password. These controls do not prevent recipients from forwarding public delivery links.

We store OAuth credentials in deployment secrets and use them on the server to obtain access tokens. Do not put credentials in campaign notes or send them in a support message. We use authentication cookies or tokens for access control. Your browser can also store saved form templates, recent-run labels and previous form inputs in local or session storage. You can clear those entries through your browser's site-data settings.

Retention, deletion and revoking access

Retention depends on the record: delivery files and backup copies remain until removed through the applicable storage workflow or an approved deletion request; package metadata and operational records support delivery history and troubleshooting; server-side OAuth credentials remain until replaced or removed. Revoked credentials no longer grant access. Browser-stored inputs remain until cleared or replaced.

We keep delivery files, backups and package history to support campaign delivery, recovery and reporting. The service does not promise a fixed automatic deletion period for these records. To request access, correction or deletion, email the service administrator with the package number or file link and the scope of your request. We may need to verify that you are authorized to make the request.

Deleting a Content Hub card does not by itself delete its Google Drive files, backup copies, agency spreadsheet rows or notification history. A deletion request should identify which copies need removal; we will explain any copies outside our control or records we need to retain.

The connected account owner can revoke Creative Renamer's access in Google Account connections. Revocation stops future use of that authorization but does not delete files already created or information already delivered. Contact us to request removal of retained data and the server-side credential.

Changes and contact

We publish changes to this policy on this page and update the date above. Contact artgolubtsov@gmail.com before submitting files if you have questions about access, sharing or retention.