Legal
Privacy Policy
Last updated: November 17, 2026
Toreador — Privacy Policy
Version 1.6 — Last updated: November 17, 2026 Effective: upon publication
This policy explains how CÔNG TY TNHH LOGITALE (international name: LOGITALE LIMITED LIABILITY COMPANY, "Logitale", "we") processes personal data in connection with the Toreador service (the "Service"). Contact: [email protected] .
Logitale is the data controller for the processing described in this policy, except where this policy states that another party acts as controller (payment confirmations sent on behalf of a Merchant, Section 1; providers acting as independent controllers, Sections 4 and 5). We have not appointed a data protection officer; requests relating to personal data are handled by Logitale at [email protected].
It covers two groups of people:
- Merchants — account holders and their team members, and
- Payers — visitors of hosted payment pages (`/pay`) or users of payment QR codes, who are customers of our Merchants, not of Logitale. A Payer who chooses to keep a payment history on Toreador (see Section 1) becomes, for that history only, an account holder of Logitale.
1. Data we collect
From Merchants (account holders):
- Account data: name, email address, business name, country of establishment, declared business category, team member emails and roles.
- Authentication data: passkey public keys, login codes metadata, session data.
- Billing data: subscription plan, billing history, and identifiers provided by the billing provider that handles your subscription (Paddle, see Section 4). We do not collect or store card numbers — payment instruments are handled entirely by that provider.
- Configuration data: wallet addresses you register (public blockchain identifiers), API keys (stored as cryptographic hashes), webhook endpoints, integration settings, and the address (domain) of each website or application you connect to your account.
- Wallet ownership proof, only if you choose to prove that you control a wallet address: the dated message we asked you to sign and the signature produced by your wallet. The signature authorizes no transaction. We keep it as evidence of the proof and show payers that the address was proven.
- Exchange connection data, only if you choose to connect an exchange account (where this feature is available for your country): the read-only API credentials you provide, stored encrypted (AES-256-GCM) and bound to your account, the deposit address and the networks and tokens it accepts as read from the exchange, and the result of our daily re-verification that the credentials remain read-only. We refuse any credential that could withdraw or transfer funds.
- Usage data: dashboard activity, API request logs (endpoint, timestamps, key identifier, IP address), audit logs of account actions.
- Support communications.
From Payers (visitors of payment pages):
- Wallet address (a public blockchain identifier), when a wallet is connected or when a transaction is detected on-chain.
- Technical data strictly necessary to serve and secure the page: IP address, user agent, timestamps, security and anti-abuse logs.
- Aggregate usage measurement of the payment page itself, recorded as categories only: device class (phone, tablet, computer), operating system family, browser family, whether the page was opened inside a wallet application, the name of the wallet you connect, and the step reached (page viewed, wallet connected, transaction sent). This record contains neither your IP address nor the full browser identifier, and it is not linked to any marketing profile. We use it to understand which devices and wallets payers use, so that the payment page works well for them.
- Payment session data: amount, token, chain, session status, and the transaction hash once broadcast — all of which also exist on the relevant public blockchain.
- Email address, only if you choose to type it on the "paid" page to receive a payment confirmation. This confirmation is sent on behalf of the Merchant you paid, with the Merchant's own customer contact details, and Toreador acts as the Merchant's processor for that single sending. Your address is used once, for that one message, and is erased from the payment record as soon as the message is sent; it is never attached to any account, profile or list, and never used for our own communications. The confirmation carries a link to stop receiving such messages: addresses that use it, and addresses reported by our email provider as unreachable or as having filed a spam complaint, are kept on a suppression list (see Section 8) so that nothing else is ever sent to them.
- Payer account, only if you tick "keep my payment history" and then confirm it from the confirmation email. Nothing is created before that confirmation: the link in the email proves that the address is yours. The account holds your email address and the payments you chose to keep (amount, stablecoin, network, transaction hash, merchant name and date). It has no merchant features unless you later start the merchant onboarding yourself. We never attach a payment to an account on the sole basis of an address typed on a payment page.
Payment pages are kept deliberately minimal: we do not run marketing analytics or session-recording tools on `/pay` pages.
From visitors of the public website and of the QR code generator:
- Analytics data via Google Analytics and Microsoft Clarity, only if you accept them in the cookie banner (see Section 6).
2. What we use it for
- Providing the Service: accounts, payment session creation, on-chain detection and confirmation, webhooks, exports, support. (Legal basis where applicable: performance of a contract.)
- Security and anti-abuse: authentication, rate limiting, abuse prevention, sanctions screening of wallet addresses (Merchant receiving addresses before they are registered or used; Payer addresses when a wallet is connected on a payment page or when a transfer is detected on-chain) against published sanctions lists, incident investigation. (Legitimate interests / legal obligation.)
- Billing and account management: subscription lifecycle, invoicing data, dunning emails. (Contract / legal obligation.)
- Transactional communications: payment notifications, security alerts, subscription and legal-update emails, sent via our email provider. (Contract / legitimate interests.)
- Payer account: keeping, at your request, the payment history you chose to keep, and signing you in to view it. (Contract.)
- Product analytics and improvement on the public website and the QR code generator. (Consent.)
- Sanctions screening of names: we compare the names you give us (organization name, legal name, certified legal name, name of the account holder) with the names published in public sanctions lists (European Union, United Kingdom, Switzerland, United Nations). A match does not block anything automatically: it creates an internal alert, with a risk score that only our administrators see, and a person decides. (Legitimate interests: not providing our software to sanctioned persons.)
- Legal compliance: accounting, tax, and lawful requests from competent authorities.
We do not sell personal data. We do not use Payer data for marketing.
3. Blockchain data — an important notice
Blockchain transactions are public and permanent by design. Wallet addresses, amounts, and transaction hashes are recorded on public networks that no one — including us — can alter or erase. Our Service reads this public data; it does not create it. Rights to rectification or erasure (Section 7) apply to data stored in our systems, not to data recorded on public blockchains.
4. Sharing and processors
We share data only with the providers needed to run the Service:
| Provider | Purpose | Notes |
|---|---|---|
| Paddle (Paddle.com Market Limited, United Kingdom; Paddle.com Inc. for purchases made in the United States) | Subscription billing, when the checkout is operated by Paddle as reseller and merchant of record | Sells you the subscription in its own name and processes your billing identity as an independent controller; we receive the subscription status and billing identifiers, never card numbers |
| Amazon Web Services (S3) | Storage of the images you upload (organisation logo, avatar, images attached to a support request) | Private storage; every image is re-encoded and stripped of its metadata before it is stored |
| Render (Render Services, Inc.) | Application and database hosting | Infrastructure provider; processes the data on our instructions |
| Cloudflare | DNS, CDN, security (WAF, anti-abuse); storage of a daily backup copy of our database and of the public status page | Processes IP addresses and request metadata; keeps the backup copy in a private storage space, on our instructions |
| Resend | Transactional email delivery | Processes recipient email addresses and message content |
| Google Analytics | Analytics of the public website and the QR code generator | Loaded only after you accept analytics cookies; never on the dashboard or on payment pages |
| Microsoft Clarity | Usage analytics of the public website and the QR code generator (heatmaps, session analytics) | Loaded only after you accept analytics cookies; never on the dashboard or on payment pages |
| Alchemy, and the public nodes of the blockchain networks as a fallback | Blockchain node infrastructure | Process wallet addresses and transaction queries (public data) |
| Didit (identity verification provider) | Optional business verification (KYB) chosen by a Merchant on a paid plan, and continuous monitoring of the verified business entity | Processes the company and legal representative data and documents the Merchant submits in Didit's hosted flow; we receive the decision and the certified legal name, not the documents |
| Chainalysis sanctions oracle (public smart contract on Ethereum) | Sanctions screening of EVM addresses | Receives the address only, through our blockchain node provider; a wallet address is public data |
| U.S. Treasury (OFAC), European Union, United Kingdom, Switzerland (SECO), United Nations | Sources of the sanctions lists | We download the lists from their official sites; no data is sent to these authorities |
| Exchange you choose to connect (for example Binance or Coinbase) | Reading the deposit address of your exchange account | Receives our read-only API calls made with the credentials you provided; applies only if you connect an exchange account |
Sanctions screening works as follows. We download the sanctions lists of the United States (OFAC SDN), the European Union, the United Kingdom and Switzerland, and compare addresses against them on our own servers, for every network. For addresses on EVM networks (Ethereum, Polygon, Base, Arbitrum, Avalanche, BNB Chain), we additionally query the Chainalysis sanctions oracle, which aggregates OFAC, EU and UN designations; only the address — public data — is sent. Bitcoin and Solana addresses are screened against the downloaded lists only. No personal data is shared with any screening provider. The screening rules and their limits are described on our page "Security and sanctions screening".
Separately, for stablecoins whose contract exposes it, we read on the blockchain whether the issuer of the stablecoin has frozen a Merchant's receiving address. Only the address — public data — is transmitted, through our blockchain node provider. We keep the result (address, stablecoin, network, frozen or not, date) as a record of the check.
We may also disclose data where required by law, to competent authorities upon valid request, or in connection with a corporate restructuring (with continuity of this policy).
5. International transfers
We operate from Vietnam. The providers listed in Section 4 are established, or process data, in other countries — mainly the United States. If you are in the United Kingdom or in Switzerland, your personal data is therefore processed outside your country.
Where the data protection law applicable to you (for example, UK GDPR or the Swiss FADP) requires safeguards for these transfers, they rest on the contractual safeguards that each provider publishes in its own terms:
| Provider | Established in | Role | Transfer safeguards published by the provider |
|---|---|---|---|
| Cloudflare, Inc. | United States | Processor | EU Standard Contractual Clauses, UK Addendum, Swiss adaptations (Customer Data Processing Addendum) |
| Resend (Plus Five Five, Inc.) | United States | Processor | EU Standard Contractual Clauses, UK Addendum, Swiss adaptations (Data Processing Addendum) |
| Amazon Web Services, Inc. | United States; images are stored in Europe (Paris) | Processor | EU Standard Contractual Clauses, UK Addendum, Swiss Addendum (AWS Data Processing Addendum) |
| Alchemy Insights, Inc. | United States | Processor | EU Standard Contractual Clauses, UK Addendum, Swiss adaptations (Data Processing Addendum) |
| Google LLC (Google Analytics) | United States | Processor | EU Standard Contractual Clauses, UK Addendum, Swiss adaptations (Google Ads Data Processing Terms, which cover Google Analytics) |
| Microsoft (Clarity) | United States | Independent controller: Microsoft states that it does not act as a processor for Clarity | Microsoft's own privacy statement, which refers to Standard Contractual Clauses |
| Didit Identity, Inc. | United States | Processor for the verification; independent controller for its own fraud-prevention and security purposes | EU Standard Contractual Clauses, UK Addendum or International Data Transfer Agreement, Swiss clauses (Data Processing Addendum) |
| Render Services, Inc. | United States | Processor | EU-U.S. Data Privacy Framework with its UK Extension and the Swiss-U.S. framework; failing that, EU Standard Contractual Clauses, UK Addendum, Swiss adaptations (Data Processing Addendum) |
| Paddle.com Market Limited | United Kingdom | Independent controller | EU Standard Contractual Clauses, UK Approved Addendum (Data Sharing Addendum) |
You can ask us which safeguards apply to a given provider, and for a copy of them, at [email protected].
6. Cookies and analytics
We use:
- Strictly necessary cookies (session, authentication, security) — always active, on every page.
- Analytics: Google Analytics and Microsoft Clarity, to understand usage and improve the product, on the public website and the QR code generator only. They are loaded only after you accept them in the cookie banner, whatever your country, and you can change your choice at any time from the cookie link at the bottom of the page. They are never loaded on the dashboard, on invoices or on payment pages.
Payment pages (`/pay`) use only strictly necessary technical processing (security, anti-abuse) and our own aggregate measurement described in Section 1 (device class, system, browser, wallet, step reached — without IP address or full browser identifier, and without cookies) — no third-party analytics, no marketing analytics, no session recording.
If we later introduce advertising or remarketing tools (for example, Google Ads), this policy will be updated with a new version number and prior notice.
7. Your rights
Depending on the law applicable to you (including UK GDPR and the Swiss FADP), you may have the right to: access the personal data we hold about you; rectify inaccurate data; request erasure; receive a copy in portable format; object to or restrict certain processing; and lodge a complaint with your supervisory authority.
To exercise these rights, contact [email protected]. We may need to verify your identity. We respond within the timeframe required by applicable law. Note the blockchain limitation described in Section 3.
Payers: because you are the customer of a Merchant and not of Logitale, requests concerning your relationship with a Merchant (orders, deliveries, receipts) should be addressed to that Merchant; requests concerning data in our systems can be addressed to us directly.
8. Retention
- Account data: for the life of the account, then up to the period required by Vietnamese accounting and tax law (up to 10 years for accounting-relevant records).
- Payment session records and exports: for the life of the account, as they constitute the Merchant's business records within the Service.
- Security, API, and audit logs: typically 12–24 months, unless needed longer for an ongoing investigation or legal obligation.
- Internal alerts from sanctions screening (the fact that triggered the alert, the decision taken, its author and date): for the lifetime of the account, then deleted with it.
- Ephemeral data (expired unpaid sessions, anonymous QR generation logs): purged on short automated cycles.
- Payment page usage measurement (device class, system, browser, wallet, step reached): 12 months, then deleted automatically.
- Payer email address typed for a payment confirmation: erased from the payment record as soon as the confirmation is sent; if sending fails, kept at most 7 days for automatic retry, then erased. Our sending journal keeps only a masked form (first letter and domain). The confirmation link that lets you keep your history expires after 30 days.
- Payer account (email address and kept payments): for the life of the account; deleted on request as described in Section 7.
- Email suppression list (addresses that asked not to receive payment confirmations, or reported as unreachable or as having complained): kept as long as necessary to honour that choice, since the address itself is the only way to recognise it.
9. Security
We apply industry-standard measures: encryption in transit, hashed API keys, exchange credentials encrypted at rest and verified read-only, passkey-based strong authentication with step-up for sensitive actions, least-privilege access, audit logging, infrastructure-level protections (Cloudflare WAF), and sanctions screening. No system is perfectly secure; we notify affected users and authorities of personal data breaches where required by law.
10. Children
The Service is a B2B product and is not directed to anyone under 18.
11. Changes
Each version of this policy carries a version number and effective date. Material changes are notified to account holders by email before taking effect. The version history is available on request.
CÔNG TY TNHH LOGITALE (LOGITALE LLC) — Enterprise code 0318970472 — SH09-15 & SH09-16, Khu 122–124, Đường B2, An Khánh Ward, Ho Chi Minh City, Vietnam — [email protected].