JordanSoft Ads Operations Privacy Policy

Effective October 10, 2026 · Updated October 14, 2026

JordanSoft LLC operates JordanSoft Ads Operations, a Windows command-line tool used by its owner to inspect the company’s Google Ads account. This policy covers that tool and these informational pages.

General company-site visits and business inquiries are also described in the JordanSoft website privacy policy. Visitor advertising attribution on pellucid-pdf.com is covered by the separate Pellucid privacy policy. This owner-operated tool is not a visitor tracking tag or consent mechanism.

Data we access

The app uses Google OAuth to obtain access and refresh tokens. It also stores the OAuth desktop client’s identifier and client secret. Google handles authentication; the app doesn’t collect Google passwords.

Through the Google Ads API, the current app reads account ID and name, currency, time zone, manager/test-account flags, auto-tagging status, campaign configuration, aggregate impressions/clicks/cost, historical keyword cost estimates, and eligible offline conversion-action IDs, names, types, statuses and owners. Campaign configuration includes budgets, schedules, targeting, keywords, ad copy and review status. It doesn’t request customer lists, ad audiences, or end-customer contact information.

An optional Data Manager validation check sends Google a fictional event containing a synthetic click identifier, generated transaction reference, test time/value/currency, and fictional measurement-consent signals. The check always uses validation-only mode and cannot ingest conversions. It accepts no customer-event file or real purchase payload. Google receives the account and conversion-action destination and ordinary connection information needed to handle the request.

A separate, guarded purchase-reporting workflow accepts a short-lived dispatch from JordanSoft’s licensing service only for an eligible purchase with recorded Google measurement consent. A dispatch contains one Google click identifier, a stable transaction reference, purchase time, USD value, destination account and conversion action, and consent signals with personalization denied. It excludes customer names, email addresses, phone numbers, license keys and document contents. When enabled for an expressly selected delivery, the sender uses Google Data Manager to submit the purchase or a partial-refund value adjustment. Full refunds use a separately reviewed conversion-retraction workflow.

How we use data

We use the data to confirm account access, inspect and evaluate JordanSoft’s advertising, and validate measurement requests. At the owner’s express direction, a separate fixed-purpose operator can create, verify, enable or pause a budget-limited campaign. Tokens authenticate requests and renew access. Results are displayed in the local terminal. Routine purchase sending remains disabled while its delivery and refund workflow is qualified; live qualification can send one expressly selected, genuinely attributed purchase or value adjustment. Visitor measurement consent is separate; the operator’s Google sign-in does not supply it.

We don’t sell Google user data, share it with advertising networks or data brokers, or use it to train general-purpose AI models. We don’t use it for purposes unrelated to the app’s stated operations.

Storage, protection, and sharing

Client credentials and tokens are stored on the operator’s Windows computer, encrypted with Windows CurrentUser DPAPI and protected by file permissions for that user and SYSTEM. The app communicates directly with Google over HTTPS. It doesn’t send Google Ads data or tokens to this website or a JordanSoft-hosted application server.

The app holds query results in memory and prints them to the terminal; it doesn’t maintain an account-data database or automatically save query-response files. If the operator saves terminal output, that copy remains under the operator’s control. The owner can read the account results as part of operating the tool.

Purchase dispatches pass over an authenticated encrypted operator connection and remain in memory during handoff. The Windows tool keeps a DPAPI-encrypted delivery journal containing delivery and destination identifiers, processing state, request receipt, and a retention deadline. The journal contains no click identifier or purchase payload. A local maintenance task prepares eligible work, checks processing receipts, identifies records requiring operator reconciliation, and removes expired journal entries; it does not automatically send purchases. This website receives none of that data.

Retention and deletion

Stored credentials remain until removed or replaced. Signing out with the app’s logout command deletes its local access and refresh tokens. It leaves the encrypted desktop client configuration in place and doesn’t revoke Google-side authorization. The operator can remove the app’s local credential directory to delete that configuration too.

Delivery-journal entries expire at the source attribution’s 120-day retention deadline and are pruned on use and by the maintenance task when the operator’s computer and account are available. A single local maintenance summary is overwritten on each run. Visitor withdrawal removes associated source records and prevents new claims; a dispatch already handed off or sent cannot be recalled automatically. Missing-source receipts are flagged for provider-side reconciliation rather than replayed. Data already received by Google is subject to Google’s applicable controls and retention.

Google-side access can be removed through Google Account connections. Revoking access for a shared Google Cloud project can also affect other apps or scopes associated with that project. Any separately saved terminal output must be deleted separately. For help with access removal or deletion, contact us at the address below.

Google handles its own account, authentication and service information under Google’s Privacy Policy. Its Business Data Responsibility information explains additional uses of information received through business services. The tool’s owner authorization is separate from visitor consent for advertising measurement.

Website visitors and support

These pages don’t use application cookies, advertising pixels, analytics scripts, or sign-in forms. Cloudflare hosts the site and processes ordinary request information to deliver and protect it; request logging is enabled. See Cloudflare’s privacy policy. If you email us, we use the information you provide to respond and handle your request.

Google API Services User Data Policy

JordanSoft Ads Operations’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes and contact

We’ll update this page and its effective date when the app’s data practices change. Contact Michael Jordan at michael.jordan@jordansoft.net about this policy or a data request.

JordanSoft LLC · Murphy, North Carolina, USA.