Privacy and anonymous event data

What an affiliate-link event records

When you click an exchange affiliate button, DZPTO stores a limited event in its first-party database: exchange, on-site page, tool, region selected in the interface, page language, button placement, and server-generated time. These dimensions help measure which tools lead to outbound clicks.

The DZPTO event table does not contain an IP address, browser user agent, name, email address, exchange account, wallet address, or device identifier.

To stop automated clients from flooding the endpoints, the server keeps a short-lived in-memory request count per connection source. That counter is never written to the database or the logs, is discarded once idle, and is never associated with any of the event fields above.

Purpose and editorial separation

Anonymous events are used only for aggregate affiliate performance and button diagnostics. Click or conversion data does not enter fee formulas, source selection, venue ranking, or editorial conclusions.

Browser storage and third-party pages

The calculator and language flow themselves do not rely on advertising-tracking cookies or localStorage. If the deployment configures a valid GA4 Measurement ID, the page loads Google Analytics; depending on Google's service and consent settings, the Google tag may use browser storage and process network, browser, and device information.

After you visit an exchange website, that venue processes data under its own privacy policy; DZPTO does not control third-party cookies, accounts, or verification flows.

Optional Google Analytics

Google Analytics is disabled by default. The Go service emits the Google tag and permits the required network origins only when production explicitly configures a valid GA4 Measurement ID belonging to DZPTO. No Google code is loaded when the setting is empty.

When enabled, it mirrors only the same coarse funnel events as the first-party system: page view, scenario-to-tool click, calculator completion, and affiliate-link click. Sent page locations exclude query strings and fragments, no stored full referrer is forwarded, and Google Signals and ad-personalization signals are disabled. Google remains an independent service provider that may process technical data under its own policy, so its data should be understood separately from DZPTO's first-party SQLite events.

Current limits

This page describes the event fields the DZPTO application explicitly writes and its optional GA4 integration. It does not attempt to summarize every technical record processed by network providers or third-party services. If accounts, newsletters, another analytics provider, or new fields are added, this page and any required consent mechanism must be updated first.

Frequently asked questions