Privacy and analytics
Updated November 3, 2026.
Your account and Upland connection
Console stores the verified identity, server-side authorization, membership, invoices, and support records needed to operate your account. Your Upland password and wallet keys are not required for Developer API registration. Payment references are used for payment verification.
Private security and support history
To investigate account problems and abuse, we retain signup, sign-in, connection, session, administrative and rejected-request events for up to 90 days. Where available, these include your verified identity, IP address, browser user agent, request time, operation and outcome, and Cloudflare-provided approximate city/region/country, timezone and network information. Network metadata is not proof of a person’s location. Sensitive event details are encrypted and available only to recently authenticated administrators; they are not sent to Analytics. We exclude passwords, authorization tokens, cookies, sign-in codes, private keys, request bodies, URL queries and payment secrets. Repeated denials may be grouped and counted, and storage is bounded. Backups have separate operator access controls. Tracking starts with this release and does not reconstruct earlier activity.
Optional Google Analytics
Analytics is off until you choose Allow analytics. When enabled, Google Analytics receives browser/device information, approximate regional information, a pseudonymous browser identifier, generic page names, supported campaign labels, and actions such as starting registration or choosing a plan. Research analytics uses fixed tool and action labels to measure opened features, attempted operations, successful or partial results, stops, errors, recognized access denials, export formats, and bounded operation duration. An opened review link does not mean a game action completed. Verified purchase events describe the plan, payment method, amount, and a random Console invoice identifier.
We do not send your email, Upland username, Upland authorization codes, wallet address, blockchain transaction references, holdings, research balances or prices, property or NFT identifiers, locations, date ranges, search inputs, private notes, raw errors, export contents, or support text to Analytics. Query strings and private page contents are excluded. Research analytics is disabled for administrators, private local mode, and sandbox use. Confirmed purchase UPX amounts are recorded separately from USD revenue. Advertising personalization and Google signals are disabled.
You can change your choice using Analytics preferences at the bottom of the page. Declining does not restrict your account or paid features. Blocking analytics can mean your visit is absent from these reports.
Conversion reporting
Invoices count as purchases only after the server confirms payment. For manual payments, the Analytics purchase is sent when you next open billing with analytics enabled. No payment-reference submission alone grants access or counts as a purchase.
Questions
Use your account’s support inbox or contact support@upxconsole.com for privacy and account-data requests.