Privacy Policy
Effective when approved and published by the operator. Contact: hello@ravynta.com.
1. Application and operator
VTlink Ads Analyst is a single-operator desktop application for Google Ads accounts the operator owns or is authorized to administer. It has no public registration or customer OAuth onboarding. VTlink Ads Analyst is the application name, not a representation that an incorporated company or legal entity has been independently verified.
2. Information accessed
The application requests openid, email and https://www.googleapis.com/auth/adwords. Depending on authorized operations, it receives Google identity metadata, including email and stable Google subject; accessible Google Ads customer identifiers; and account structure, search terms, keywords, ads, costs, impressions, clicks, conversion-related metrics and reporting segments. Separate OAuth profiles retain separate account provenance.
The operator may supply affiliate order, commission and status records for reconciliation. These are separate inputs; Google Ads API data does not automatically contain actual affiliate orders or commissions.
3. Purposes and account control
Information is used to verify authorized account access, analyze advertising performance, reconcile records, prepare reports and learn from the operator's past campaign decisions. Learning means analysis and reconciliation, not permission to train general-purpose AI models. Supported account mutations require separate explicit confirmation; the website itself does not change advertising accounts.
4. Credentials and local storage
The Windows Reader normally loads profile credentials from Windows Credential Manager; a complete environment-variable configuration can override that source. It exchanges credentials with Google to obtain short-lived access tokens. Credentials and secrets must never be placed in reports, source control, AI prompts or this website.
The Native Reader emits JSON to the invoking process's standard output. The invoking tool may retain output and analysis. Local inputs, reports and Codex session records may exist separately. Optional --record-history writes reconciliation history at an operator-selected path; an analysis-state exporter can publish per-run artifacts at another selected path. These copies require separate inventory and handling.
The reports and raw-input directories have scoped Windows access controls; additional authorized system and sandbox principals retain access. This is not a claim that every local or provider-held copy is accessible only to the operator.
5. AI services and other disclosures
The Reader itself calls Google OAuth and Google Ads endpoints and does not directly submit rows to an AI model. The operator uses OpenAI ChatGPT/Codex as an AI model provider for controlled assistance. Selected metrics or excerpts may be submitted only when needed for authorized analysis and when appropriate account controls and data permissions have been confirmed. Unnecessary personal and order identifiers should be removed. Unverified provider paths must not receive private source records.
Antigravity primarily performs independent technical review of code and documentation; that role does not authorize routine transfer of private Ads or affiliate records. OAuth credentials and secrets must never be sent to AI services, including tokens, client secrets and authorization headers.
Provider accounts, settings and retention must be evaluated for the specific service being used. This policy does not promise zero retention, disabled training across every service, or erasure of historical provider copies. Native local execution does not establish those provider settings.
6. Retention, backups and requests
The operator preserves Google Ads and affiliate order/commission history for legitimate long-term analysis and reconciliation while that purpose remains necessary and lawful. No arbitrary 30-day or 90-day deletion rule is adopted. This does not authorize indefinite retention without a legitimate purpose or override lawful deletion requirements.
A manual procedure is adopted for purpose review, verifying requester authority, locating source and derived copies, considering retention obligations, separately approving exact deletion actions and recording the outcome. No universal automatic purge covers reports, captured output, exports, local sessions and provider-held conversations. Temporary-file cleanup is not deletion of retained history.
Local reports and raw inputs have a local snapshot with a verified isolated restore test. The snapshot is on the same physical disk and does not protect against failure or loss of that disk. It does not cover all local sessions, optional exports or provider copies. Before releasing restored records into analysis, the operator must check current deletion or restriction decisions. Provider deletion must be handled through the relevant provider's supported controls; a local deletion is not proof of provider erasure.
7. Revocation
A Google account owner can revoke access through Google Account connections at https://myaccount.google.com/connections. Revocation prevents future authorized use but does not automatically erase saved credentials, prior reports or provider-held copies. Credentials remain in local storage until removed by the operator; invalidation is not deletion of retained reports.
8. Website and contact
The site is intended to use Cloudflare hosting, which may process request metadata for delivery. Its static pages have no analytics scripts, advertising tags, login fields or cookie-dependent functionality and do not collect Ads or affiliate datasets.
The operator is responsible for privacy requests at hello@ravynta.com. Request assessment must verify authority without asking for passwords or tokens, identify relevant copies, consider applicable obligations and record the result. No fixed response deadline or guaranteed erasure of every third-party copy is promised. Applicable legal obligations still apply.
9. Updates
The operator must update this policy when the application's use, storage, sharing or retention practices change. Publication must reflect implemented practices and applicable Google API Services User Data Policy requirements.