Privacy notice

Who is responsible

The operator of PeerMark is the controller of the personal data described here.

Privacy requests and questions go to legal@peermark.online. We have not appointed a data protection officer. That address is the contact for all data protection matters.

What we collect, why, and our legal basis

• Account. Email address, first and last name, a bcrypt password hash, an email-verification token and its expiry, flags for whether the email is verified and whether the account is a creator, and the version of the terms you accepted and when. We use these to create the account, check the password, and keep you signed in. Legal basis: performing our contract with you.
• Sessions and security. A signed cookie holds an account id and timestamps, not your email address. A hash of your browser's User-Agent string, with first-seen and last-seen times, lets us notice a browser we have not seen on the account and send a security alert. Console staff sign-ins are logged with the time and IP address. Legal basis: our legitimate interest in keeping accounts secure and preventing fraud, and performing our contract with you.
• Wallet and key material. We store your public key reference and one encrypted share of your signing key. The server cannot spend with it. We never hold your password in readable form or your full signing key. Wallet recovery requests record the time, the IP address and the browser string. Legal basis: performing our contract with you, and legitimate interests in security.
• Registrations, transfers, listings and licences. For each asset you register we store its content hash, title and description, the transactions that record it, ownership and licence history, the encrypted access envelope, prices and fee records. When you register an asset we also record the IP address, browser string and device details of the request, so that we can investigate abuse and unlawful content. Licence access records hold a hash of the IP address and of the browser string. Legal basis: performing our contract with you; legitimate interests in preventing abuse; and legal obligation where we must act on unlawful content.
• Payments and withdrawals. Wallet addresses, transaction ids, amounts and the status of escrow, refunds and withdrawals. We keep records of fees and transactions for accounting. Legal basis: performing our contract with you, and legal obligation for accounting and tax records.
• Reports and moderation. If you report an asset, we store your account (if signed in), your reason, your IP address and your browser details. We keep the records of what a moderator decided and why. Legal basis: legitimate interests in running a safe platform, and legal obligation where the report concerns unlawful content.
• Feedback. If you send beta feedback we store your message, any email address you give, the page, your IP address and your browser string. Legal basis: legitimate interests in improving the service.
• Notifications and emails. We email verification links, password-reset links, password-change notices, security alerts and notices of high-value operations. These are service messages that we need to send to perform our contract with you.
• Newsletter. If you tick the consent box and subscribe, we store your email address, the time and the source. We email a confirmation link and add the address to the list only when you open it (double opt-in). Legal basis: your consent. You can withdraw it at any time with the form below.
• Technical logs. Our servers read your IP address to apply rate limits and to detect abuse. Those limits are held in memory. Server error logs may include request details. Legal basis: legitimate interests in security and reliability.
• Child sexual abuse material. If content is reported or identified as suspected CSAM, we preserve the content record and associated account details, including IP address, and may disclose them to the authorities. Legal basis: legal obligation and the substantial public interest in preventing and detecting unlawful acts.
• This browser. The browser stores a cache called peermark-user (account id, email, name, profile image address, wallet address, wallet type, a key reference, and whether email or an authenticator is enabled), a wrapped signing key, device-share envelopes and wallet status. None of it includes your password. The cookies page lists every name. This storage is strictly necessary for the service you asked for.

You do not have to give us any of this data, but we cannot provide an account or the services without the account, wallet and registration data. We do not use special category data on purpose. Do not put it in titles or descriptions.

What goes on a public blockchain

Registering, transferring or licensing an asset writes transactions to the BSV public blockchain. They can include a content hash, key references, timestamps and amounts. Anyone can read them and no one, including us, can alter or delete them. We do not put your name or email address on chain. A key reference or wallet address can still be linked to you by someone who learns that it is yours. Because the record is permanent, rights to erasure and rectification cannot be applied to what is on the chain. They do apply to the data we hold ourselves.

Who receives data (processors and other recipients)

• Supabase hosts the database that stores the account, newsletter, registration and session rows.
• Resend sends the transactional and newsletter emails listed above. It receives the recipient address and message content.
• Signa (api.signa.so) receives what you enter in the trade mark register check, so that it can search public registers: the mark text, the class numbers and territories you choose and, if you use the class suggestion helper, the description of use you type. If you look up a register record by number, it receives the office and the application or registration number. PeerMark's server sends these requests, not your browser, and only when you use that check. The check panel says Signa keeps request logs for 90 days. PeerMark does not store the results.
• Blockchain data services. PeerMark's servers, not your browser, call WhatsOnChain (api.whatsonchain.com) and Bitails (api.bitails.io) to read transactions, address history, unspent outputs, block data and proofs, and JungleBus (junglebus.gorillapool.io, mainnet only) to fetch a transaction by its id. Reading an account's wallet activity sends the wallet address and transaction ids; Bitails is asked first and WhatsOnChain is the fallback. Chain status checks send transaction ids.
• TAAL (ARC, arc.taal.com) receives each signed transaction that PeerMark broadcasts when a TAAL key is configured, and is asked for the status of a transaction by its id. Otherwise, or if TAAL does not take the transaction, it goes to WhatsOnChain. A broadcast transaction is public on the BSV network.
• VirusTotal (www.virustotal.com) receives the SHA-256 hash of a file during registration, when a VirusTotal key is configured, so that it can say whether that hash is known as malware. The file itself is not sent. PeerMark's server sends the request.
• BSV price sources. The asset listing page works out a price in pounds in your own browser, so the request leaves your browser directly and the source sees your IP address. It asks exchangerate-api.com (api.exchangerate-api.com) for the pound-to-dollar rate, then CoinGecko (api.coingecko.com) for the BSV price. If one does not answer it tries CryptoCompare (min-api.cryptocompare.com), Binance (api.binance.com), KuCoin (api.kucoin.com) and CoinCap (api.coincap.io), in that order, and stops at the first that does. The registration page also asks exchangerate-api.com from your browser when a declared value is entered in a currency other than pounds. No account data is sent with these requests. PeerMark's servers also read BSV prices from these sources, and those requests carry no account data.
• Authorities and advisers. We may disclose data to law enforcement, the Internet Watch Foundation, the National Center for Missing & Exploited Children, the BSV Association, regulators, courts, and our professional advisers where the law requires it or where it is needed to deal with unlawful content or to establish or defend legal claims.

No third-party analytics SDK is loaded by the public site. A Stripe helper exists in the code and is not called by any route, so card payments are not described here. We would update this notice before any such processor receives personal data. We do not sell personal data.

Transfers outside the UK

Several of the services above are provided by companies that may process data outside the UK, including in the United States and the European Economic Area. Where personal data is sent outside the UK, we use a safeguard permitted by UK GDPR Chapter V: a UK adequacy decision, the UK Addendum to the EU standard contractual clauses, or the UK International Data Transfer Agreement. Supabase and Resend, which hold account and email data, offer data processing terms that include these safeguards. The blockchain data services, TAAL, Signa and VirusTotal receive only public chain identifiers, trade mark search text or file hashes, and not your name, email address or account details. A wallet address or transaction id is pseudonymous data. You can ask about the safeguard that applies to a transfer using the privacy address above. Reading the public blockchain is global by nature, and public nodes may be anywhere.

How long we keep data

We keep data only as long as it is needed for the purpose it was collected for. In practice:

• Email-verification tokens expire after 24 hours.
• Wallet recovery requests expire after one hour, and replaced recovery-share archives are purged after 30 days.
• Migration journal entries are purged after 18 months, and expired wallet-operation records are deleted by an automatic purge.
• Account and registration data is kept while your account is open. After you close it, or we erase it on request, we remove or anonymise the personal data we hold, except what we must keep as described below.
• Financial and transaction records are kept for as long as UK law requires for accounting and tax purposes, normally six years.
• Records about reports, moderation decisions, disputes and legal holds are kept while a claim or investigation is open and for a reasonable period afterwards, and records relating to suspected CSAM are kept for as long as the authorities or the law require.
• Newsletter addresses are kept until you unsubscribe.
• Data in your browser stays until you clear site data or reset the wallet. Signing out clears peermark-user only.

When we erase an account, we also clear the IP address, browser string and device details on that user's registrations, feedback and non-CSAM reports. Data in processors' own logs follows their retention periods.

Automated decisions

We use automated checks, such as rate limits, ownership checks before an access envelope is released, and detection of an unfamiliar browser. They protect accounts and assets. We do not make decisions about you that produce legal or similarly significant effects by solely automated means without a way to have a person review them. If a check blocks you, write to the privacy address and a person will look at it.

Your rights

You can ask for access to your data, correction of inaccurate data, erasure, restriction of processing, a portable copy of data you gave us, and you can object to processing based on our legitimate interests. Where processing relies on consent, you can withdraw it at any time without affecting what was done before. Use the privacy address above. We will answer within one month and will tell you if we need longer or need to confirm your identity. Some rights are limited where we must keep data by law, where the data is on a public blockchain, or where we hold it to deal with unlawful content.

You can complain to the Information Commissioner's Office at ico.org.uk or by telephone on 0303 123 1113. We would appreciate the chance to put things right first, but you do not have to contact us before the ICO.

Security

Passwords are hashed. Session cookies are signed and HttpOnly. Database tables are protected by row-level security and accessed through the server. Content keys and signing keys are handled in your browser, and the server holds only encrypted envelopes and one share that cannot spend alone. No system is completely secure. If a breach is likely to put you at risk, we will tell you and, where required, the ICO.

Children

PeerMark is for people aged 18 and over. We do not knowingly collect data from children. If you think a child has given us data, tell us at the privacy address and we will delete it.

Cookies and local storage

Cookie names, browser-storage names, and what each one holds are on the cookies page.

Unsubscribe from the newsletter

The homepage form does not store an address unless the consent box is ticked. To stop newsletter emails, enter your address below and we will email you an unsubscribe link, and the address stays on the list until that link is opened. The response is the same whether or not the address was on the list, and if the email cannot be sent the page says so.

Changes to this notice

We will change this notice when what we do changes. The date at the top shows the current version. For a material change we will tell account holders by email or on the Platform.

The Terms of Service explain the contract between you and PeerMark.