Privacy Policy

1. Scope and accounts

Consumer sign-in may use Telegram, Google or ChainZap email/password authentication. The developer portal uses Google OIDC or the ChainZap account bridge. ChainZap does not require a wallet connection or signing credentials.

2. Data processed

We process account identifiers and contact/sign-in information, submitted wallet addresses and transaction hashes, check history, snapshots, chat questions and answers, usage records and payment references. Telegram IDs are stored in their original numeric form where required for account identity and bot delivery; selected logs use hashes. Business data may include confidential instructions, attempts, allocations and obligation-to-blockchain associations.

3. Data minimisation

Do not submit private keys, seed phrases, signing credentials or unnecessary names, contact details or KYC documents. Public blockchain identifiers and pseudonymous references may still relate to an identifiable person. ChainZap does not custody or execute transfers.

4. Purposes

Data is used to provide checks and history, authenticate accounts, administer purchased access, investigate errors, secure the service, answer support requests and measure product use. Customer-specific pilot data is handled under the agreed purpose and instructions.

5. Providers and analytics

Blockchain and security providers receive the address, transaction or other information required for the selected check. Telegram, Google, email delivery, OxaPay, Cloudflare infrastructure and Sentry may support the relevant service functions.

PulseForge is a separate product analytics service receiving activity, check, purchase and source-attribution events, including the original Telegram ID when available. It uses that ID for unique-user counts, returning-user metrics, attribution and purchase analytics. Advertising pixels were not found in the checked site/portal implementation; this does not mean no operational analytics is used.

6. Retention

Consumer check history, snapshots, Ask conversations, payment records and account Telegram identifiers currently have no automatic deletion period triggered by inactivity or blocking the bot. Cache expiry and the number of history rows displayed do not delete these database records.

PulseForge accepted events and user profiles currently have no automatic maximum retention period. Its 14-day cleanup applies only to rejected ingestion records. Administrative erasure is separate and is not automatically triggered by leaving ChainZap.

Pilot active-data deletion follows the signed agreement. The 30-day-after-completion commitment in the pilot templates requires an agreed operational process; it is not the standard ledger retention timer. Backups follow separate rotation and may retain protected copies.

7. Logs and security telemetry

Ingress/access logs may contain client IP, forwarded IP, request path and query, referrer, browser User-Agent, time and response status. Identifiers included in URLs can therefore appear in logs. Application logging uses request/batch identifiers, route normalization and targeted scrubbing; it does not guarantee that every log contains only hashes.

Portal nginx access logging is disabled. Application/error telemetry remains possible. Sentry is configured with default PII collection disabled and additional private-request scrubbing; this is not a guarantee of complete anonymisation.

8. Business Enquiries

Business access requests contain the form fields and language/source attribution. They are deleted 12 months after they are sent. The form record does not store IP; short-lived anti-abuse limits use a hash. Separate ingress logs may still contain IP.

Email notifications contain an internal request ID; submitted request details stay in the restricted database. Requests are not automatically subscribed to marketing lists. Contact support to request access or earlier deletion.

9. Ask ChainZap and OpenAI

Ask sends a question, limited recent conversation and a selected fact sheet to OpenAI. The fact sheet can include status/coverage, activity aggregates such as balance and transaction counts, token names and signals. The complete raw snapshot/provider response is not sent.

Requests use store=false. Recognized wallet/TXID formats, email, UUID, labeled Telegram IDs and known current-account identifiers are replaced before sending. This is best-effort minimisation: names, unknown numeric IDs and unusual identifiers can remain in free text. Do not include personal data or secrets. The setting does not itself establish zero provider retention.

AI text explains results and does not modify core scores, sanctions matches or saved statuses. Standard status explanations are deterministic. The standard payout batch does not require an LLM.

10. Sharing and public integrity status

Sharing a snapshot or CZ-ID can make its contents visible to recipients and anyone able to access the shared link. The public service-log integrity endpoint returns date, integrity status, entry counts and verification time, not raw check payloads, addresses or secret keys.

11. Hosting and international processing

Backend/database hosting provider and physical region have not yet been verified. Cloudflare provides proxy/CDN and R2 backup infrastructure; this does not establish a specific storage region. No UAE or Poland residency claim is made. Relevant pilot subprocessors and locations must be identified before a transfer under the Pilot Data Annex.

12. Eligibility and requests

The consumer service is intended for adults aged at least 18 and is not offered to persons located in the United States or European Union under the Consumer Terms. Subject to applicable law, contact support to request access, correction, deletion, restriction or objection. Required legal/accounting retention and signed business terms may affect what can be deleted.

13. Changes and contact

Updates will be published with the relevant service. Material notices and any renewed acceptance follow the applicable terms and mandatory requirements. Privacy and data requests: support@chainzap.io.