Privacy and data

What is needed to process. Nothing more.

The social workflow is public and does not require an account. Google Ads requires Google sign-in and advertiser account permission. Technical controls reduce abuse and protect each batch.

Data received

When you submit a CSV, an XLSX converted in the browser or a pasted list, the application receives the URLs and the other columns in the file. Avoid including names, email addresses, phone numbers, identification documents or other personal data that is not needed to find the thumbnails.

Purpose

The data is used to validate the file, process URLs, track the batch, generate the result and prevent abusive automated use. The network address may be used temporarily for request limiting and security validation.

Third-party analytics

Optional third-party analytics are disabled on the unified Social and Google Ads collection page, even for previously granted preferences. Google Tag Manager is not loaded there. Privacy preferences explain this restriction; essential operational security controls remain separate.

Legal bases and rights

Optional metrics processing is based on consent. Strictly necessary security, abuse prevention and operational continuity controls may rely on legitimate interests or applicable legal obligations. Data subjects may request confirmation, access, correction, information, objection, deletion and consent withdrawal, as applicable.

Storage and access

Input files, status information and results are stored privately. The browser receives a random batch credential and keeps it in local history. Anyone who receives a shared address containing that credential can open the same batch.

Final thumbnails may be published at a public delivery address for use in spreadsheets, reports and dashboards. Do not submit links to content you are not authorized to process.

Retention

CategoryOperational period
Input fileAt least 365 days
Batch credential and status365 days of authorized access
Published thumbnails and cache assetsNo automatic time-based deletion

Input files and complete report data are retained for at least 365 days. Social batch credentials expire after 365 days, separately from physical cleanup. Historical result CSVs and public media have no automatic time-based deletion; removal requests use the channels below.

Services used

The operation may use Cloudflare for hosting, storage, queues, abuse protection and human verification, and GitHub Actions as a processing contingency. Platforms associated with submitted links receive the requests required to locate the public thumbnail. Google Tag Manager is not used on the unified collection page.

Security

Batch access uses a random identifier and a separate credential. During normal navigation, the credential is not sent to the server as part of the URL because it remains in the address fragment. Do not publish the complete batch address on open pages.

Sharing, transfer and controller

Providers may process data in other countries under their contracts and policies. The application does not sell submitted data. Kamale.ad acts as the controller for this product and receives requests through the official channels listed below.

Requests

Removal, privacy or security requests must be sent through the official channels at kamalead.com.br, including the batch or thumbnail URL and the reason for the request.

Last updated: October 17, 2026.

Google Ads connection

Any Google email domain can authorize access to their Ads accounts. Google requires the broad Ads permission; this application only reads account, campaign, ad and asset data. The identity and temporary access or refresh credentials are stored privately, encrypted. The default connection uses temporary access, without requesting or storing a refresh credential, and lasts up to one hour within Google token validity. When explicitly selected, the renewable authorization remains encrypted on the server until expiry or revocation. Maintained sessions last up to 30 days on this device and end after 7 days without use. Existing sessions keep their previous expiry. Confirming the same Google identity reuses a valid grant without new Ads consent. Legacy grants are not migrated automatically. Revocation blocks all sessions linked to the saved authorization. Sessions use essential cookies; Google determines the authentication methods. Ads exports are private and retained for at least 365 days. Images are private by default. Enabling “Generate image links for BI” before extraction lets anyone with a link view only that image without signing in, until the batch’s 365-day expiry or link revocation. Accounts, campaigns and CSV reports are not shared. Older batches are not published automatically. Revoking image links is separate from disconnecting Google and cannot erase copies already downloaded. After either session expires, signing in again with the same Google identity allows historical access after current account permissions are checked, and never published on the public thumbnail CDN. Disconnect immediately blocks local access and requests revocation at Google. Public YouTube cover images may be requested without accessing private videos. Ads data is not sold or used for training AI models, and the unified Social and Google Ads page does not load optional third-party analytics. The minimum 365-day retention applies across the application. Public thumbnails and historical exports have no automatic time-based deletion. You may also revoke access in your Google Account permissions.

See the user guide to distinguish social batch credentials, Google sessions and private Ads file access. Retention is not a backup and does not authorize new uses of the data.

Privacy contact: [email protected]