Know what you are sharing.

Public transaction records

We save public Tempo records: wallet addresses, amounts, receipts and supporting evidence. They appear in the terminal, API and archive. A wallet address is not a verified identity.

Requests you submit

The form saves your name, email, optional company, selected interest and message in our private server database. A notification containing your request is emailed through Brevo to nader@intelixsystems.com, with your email as Reply-To. Authorized operators review and respond to requests. Email copies follow mailbox retention separately. You are not added to a paid plan or marketing list. Do not send passwords, private keys, payment credentials or sensitive third-party records.

Requests are kept for up to 180 days; cleanup runs on new submissions or operator access. For correction or deletion, select Privacy request in the form and include your reference. We may verify your email ownership.

Aggregate usage

We count page loads, selected link/button clicks and API requests by day, page or endpoint, and broad referral category. AI referrals distinguish ChatGPT, Perplexity, Claude, Gemini and Copilot when a referrer is available. Campaign labels use an allowlist; arbitrary values are ignored. We use a random in-memory visit identifier and event identifiers to deduplicate and connect actions while this page remains open. Reloading starts a new visit; no visit identifier is stored in cookies or browser storage. We also store a coarse viewport-size category. Counts can include bots and repeat visits. Our metrics store no IPs, emails, wallet searches, query strings, transaction hashes, full referrer URLs, cookies or persistent visitor IDs.

Browser counting respects Do Not Track and Global Privacy Control. API request counts remain operational totals. We keep these aggregate metrics for 90 days; cleanup runs during writes or operator access.

Infrastructure

Hosting and network providers process connection information under their own policies. Public evidence is saved on our server and backed up to private Backblaze storage. Form requests and private participant records are stored separately.

Private evidence

Participant submissions, signing credentials and dispute reports require authorized access. The public transaction API does not expose them.

View preferences

Your browser stores your Simple or Advanced view and motion settings locally. These preferences are not visitor identifiers and are not sent to our analytics.

Provider domain proofs

With your consent, we send your work email and listed domain to SwarmBazaar to issue an HTTPS-file challenge. SwarmBazaar stores an email hash unless you separately opt into their marketing; this form does not opt you in. InferenceView stores the claim reference, domain and verification time, not your work email or proof text. Claim records expire from our storage after 31 days. A successful domain proof is displayed for 30 days and does not verify wallet ownership or service quality.