Coinentry

Legal

Privacy Policy

Last updated: August 17, 2026

1. Who we are

Coinentry is read-to-write financial middleware. We translate inbound USDC and USDT transfers on Ethereum, Polygon, and Tron into balanced journal entries in QuickBooks Online and Xero. We operate read-only on blockchain and write-only on accounting software. We never collect, store, or handle private keys or seed phrases.

2. Data we collect

We collect only what is required to authenticate your firm, monitor designated wallets, and post journal entries to the connected ERP:

  • Account and firm profile: email address, name, organization, and role.
  • Wallet public addresses: Ethereum, Polygon, and Tron addresses you register for monitoring. These are public identifiers. We do not receive spending authority.
  • Transaction metadata: transaction hash, network, log index, timestamp, asset, normalized USD amount, and fair-market value used to book the entry. We do not ingest private memos, seed phrases, or unsigned payloads.
  • Chart of Accounts mappings: the ERP asset (debit) and income (credit) account identifiers you select so inbound stablecoin receipts post as balanced journals.
  • ERP connection data: OAuth tokens for QuickBooks Online or Xero (encrypted at rest), company/tenant IDs, connection status, and journal-entry reference IDs returned by the ERP.

3. ERP read / write scope

When you connect QuickBooks Online, Coinentry requests Intuit accounting scopes solely to:

  • Read Chart of Accounts so you can map wallets to Asset and Income accounts.
  • Write Journal Entries for inbound USDC/USDT receipts using the accounts you chose.

We do not create invoices, bills, payments, or payroll objects. We do not read your full general ledger beyond the accounts needed for mapping. You may disconnect QuickBooks at any time from Integrations or by revoking Coinentry in your Intuit account.

4. How we use and share data

We use the data above to provide the service, maintain audit logs, rotate ERP tokens, and troubleshoot sync failures. We do not sell personal or firm data. We share data with processors who host or operate the product on our behalf, including:

  • Supabase (authentication and PostgreSQL hosting)
  • Alchemy and TronGrid (read-only chain data)
  • Intuit QuickBooks Online and Xero (ERP journal writes)
  • CoinGecko (historical USD pricing used for fair-market value)

Subprocessors receive only what they need to perform that function. Blockchain networks are public; registering an address does not make on-chain history private.

5. Data retention

Account, wallet, mapping, credential, and sync-log records are kept for as long as the client entity remains on Coinentry so your firm can reconstruct posted journals. Encrypted ERP tokens are retained only while the connection is active. After you disconnect an ERP, tokens are invalidated and overwritten. After a verified deletion request (below), we delete or irreversibly anonymize personal data in live systems, subject to legal retention (for example, records we must keep to demonstrate a posted journal or to resolve a dispute). Residual copies in encrypted backups are purged on the backup rotation cycle.

6. Data deletion and user rights

You may request access, correction, or deletion of personal data we hold about you or your firm. This section satisfies Intuit App Assessment requirements for a public deletion-request channel.

To request deletion, email privacy@coinentry.io from the address on your Coinentry account. Include:

  • the subject line “Data deletion request”
  • your organization name and account email
  • whether you want a single client entity or the entire firm removed

We will confirm receipt and complete verified deletion within 30 days, unless a shorter period is required by applicable law. You may also disconnect QuickBooks Online from the Integrations page, which stops further writes and marks the ERP connection as disconnected. Revoking Coinentry inside Intuit independently invalidates our access tokens.

7. Security

ERP tokens are encrypted in transit via TLS 1.2+ and encrypted at rest before storage. Tenant isolation is enforced in the application layer and with PostgreSQL row-level security. We never ask for a wallet seed, private key, or recovery phrase. If you receive such a request, it is not from Coinentry.

8. Contact

Privacy and deletion requests: privacy@coinentry.io. Related terms are published at /terms.