The wallets you look up

  • To look up a wallet, my server retrieves its transaction data from a Bitcoin node I operate myself. The address is not sent to any outside blockchain service.
  • The addresses of the traced wallets are also compared with public sanctions lists, currently the OFAC list of the US Treasury. I keep a copy of the list on my own server, so no address is sent anywhere for this check.
  • The address you enter, the wallets traced from it, their transaction data and the investigation result are kept only while you need them to see the result, export a report or merge investigations. They are deleted automatically about 3 hours after the investigation. Deleted data stays in the backup history of the database for at most 1 day.
  • Reports, whether a PDF report, a Case Report or the PDF of a merged graph, are sent straight to you. I do not keep a copy.
  • The credit ledger, which records who used credits, never records which wallet was investigated or watched.
  • If you choose to watch a wallet, its address, the nickname you give it and the transactions found while watching are kept for as long as the watch runs (30 days, longer if you renew it) and deleted when it ends or you stop it. The alert emails name the watch by its nickname, never the wallet or a transaction.

The legal basis is Art. 6(1)(f) GDPR: your organisation's legitimate interest, and mine, in detecting fraud and financial crime. A Bitcoin address does not in itself identify a person, and because investigation data is deleted within about 3 hours, and a watched wallet's data when the watch ends, any possible link to one is kept to a minimum.

Data about you as a user

  • Access account: your work email address and the organisation whose credits you use, once your organisation has approved you. I use it to let you sign in and run investigations, and keep it while your organisation's access continues.
  • Sign-in: a record of your sign-in link and your session, stored in a form that cannot be used to sign in. Both are deleted automatically shortly after they expire.
  • Credit ledger: when credits were added to your organisation or used (for an investigation, a report, a merge or a watch), by which email address, how many wallets an investigation covered and how many credits it used. I use it for billing and to answer questions about charges, and keep it for as long as tax and commercial law require.
  • Organisation records: your organisation's name, email domain and credit balance, and the email addresses it has approved for access. I keep them while your organisation's access continues.
  • Settings history: changes to your organisation's rule settings, with the date and the email address of the person who made them, so that results can be explained later. I keep it while your organisation uses the service.
  • Billing: the billing details of your organisation and the invoices for its credits. I keep them for as long as tax and commercial law require.

The legal basis is Art. 6(1)(b) GDPR, providing the service your organisation has arranged, and Art. 6(1)(f) GDPR, my legitimate interest in providing it securely and billing it correctly. Billing records are also kept to meet my legal obligations (Art. 6(1)(c) GDPR).

What I don't do

  • I do not sell data, and I do not run advertising or analytics trackers.
  • I do not keep a database of user-submitted reports or flags about wallets.
  • I do not use the wallets you look up for any other purpose, and I do not share them with anyone.
  • I make no decisions about people: a risk level describes the transactions of a wallet, and what happens next is decided by your team.

Questions about your data

Who is responsible, which service providers I use, transfers outside the EU and your rights are described in Data Privacy.

Write to me at contact@skdintel.com.