kauppaholvi FIEN

Security · privacy · evidential value

A bill of sale that can't be changed unnoticed or read without the key.

When you buy cards, you end up holding your customers' names, addresses and bank account numbers. On a paper form they go into a folder that anyone can open and read. In Kauppaholvi a purchase starts on the customer's own phone and ends with their signature at the counter. The data is stored only in encrypted form, every event goes into a chain that can't be altered unnoticed, and the data deletes itself when the retention period ends. On this page I explain in more detail how the data is protected.

  • 0 customer names, addresses or bank account numbers in readable form, in the database or in a backup
  • AES-256 encryption, and every purchase has its own key
  • 5 yrs · 6 yrs personal data deletes itself, the voucher is kept for as long as the Finnish Accounting Act requires
  • 1 chain every log row and seal row contains the fingerprint of the row before it
  • Finland the server is in Finland, and your business has its own address and its own keys

1 · Encryption

Even if someone stole the database, they couldn't get a single customer's name out of it.

I use the same model that banks and cloud services use in their own systems. It's called envelope encryption. The data opens only at the moment when someone who has the right to see it is looking at it.

  • Every purchase has its own key. Opening one purchase leaves the others shut. The purchase's key is itself encrypted with a master key, and the master key is never in the database, the code or a backup.
  • A stolen backup doesn't give away your customers' details. The master key is not in the database, the code or a backup, so in a copy that falls into the wrong hands the data is unreadable. There is still a spare copy of the master key in a safe place, so your data isn't lost even if the server is replaced.
  • Encryption starts with the first keystroke. The customer's form is encrypted as soon as it is saved, even half-finished. Kauppaholvi stores no data on the phone or the tablet.
  • You find a purchase by surname, even though no names are stored in readable form. Type the exact surname and you get the purchases made under that name.
  • You see who looked, and when. A member of staff sees the customer's details only while the purchase is in progress, and even then behind a PIN. Opening them afterwards requires a recorded reason and leaves a mark: who, when, which purchase and why.
  • You're told if an unusual amount of data is opened. The notice is sent to you automatically.
  • Vouchers have a long-lived key of their own. The accounting PDF is kept longer than the personal data, so it has its own archive key.
PURCHASE #4711 name ▮▮▮▮▮▮▮▮▮▮▮ address ▮▮▮▮▮▮▮▮▮▮▮ account ▮▮▮▮▮▮▮▮▮▮▮ AES-256 · the purchase's own key PURCHASE KEY encrypted by master key MASTER KEY not in the database nor in any backup DISK · BACKUP encrypted data only · no keys 5 yrs: key destroyed → unreadable
Envelope encryption. When a purchase's key is destroyed after five years, its personal data can no longer be opened, not even in old backups.

2 · Chain of evidence

A signed bill of sale can't be changed without it showing.

Every row locks the one before it. A row contains the previous row's fingerprint, a hash calculated from that row's content. Blockchains use the same idea, but Kauppaholvi keeps the chain in its own database.

ROW 1 CREATED prev. – h=9f3a… ROW 2 OFFER prev. 9f3a… h=c71e… ROW 3 SIGNED prev. c71e… h=02bd… ROW 4 PAID prev. 02bd… h=e4a0… If row 2 is changed afterwards, its hash changes and row 3's “prev.” no longer matches.
Hash chain. Rows can only be added to the audit log and the signature seals. They can't be edited or deleted, and a break shows up when the chain is checked.
  • The signature covers exactly what the customer saw. The content is locked into a fingerprint before the customer signs. If someone later claims that something else was agreed, you can show what was signed. The fingerprint can be recalculated years later, and the result matches.
  • The chain is checked automatically. The result is written to a log of its own. If even one row has been changed, the break shows up in the check.
  • The chain doesn't fork, even if two things happen at once. A database lock makes sure rows are created one at a time.
  • The same check is run when a backup is restored. A restored database is not taken into use until the chain has been found intact.
  • The head of the chain is also kept outside the server. It is written to locked storage that can't be changed or deleted, and the record is kept for the whole retention period. If someone shortened the chain on the server, the comparison would reveal that too.
  • I don't use a public blockchain. The chain is in Kauppaholvi's own database, and no data is sent to any outside network.

3 · Privacy and retention

You don't have to remember when data must be destroyed.

The retention periods are built into Kauppaholvi. The six years of the Finnish Accounting Act and the five years for personal data are two separate clocks, and Kauppaholvi keeps track of both for you.

  1. During the purchase Only what the purchase needs A member of staff sees personal data behind a PIN for as long as the purchase is in progress. The bank account number is asked for only when the payment goes to an account. If the seller is a minor, a guardian must be present, and the guardian's details are recorded too.
  2. 5 years Personal data is gone The purchase's own encryption key is destroyed automatically. After that the name, address and bank account number can no longer be opened, not even in backups. This is called crypto-shredding.
  3. 6 years The voucher is deleted The Finnish Accounting Act (1336/1997) requires vouchers to be kept for six years from the end of the year in which the financial year ended. The voucher holds only what the law requires: no date of birth, phone number, email address or bank account number.
  • Your accountant doesn't use Kauppaholvi at all. They get an encrypted package of vouchers once a month. They have no access to personal data.
  • When a customer asks about their data, you have a ready-made function for it. Access to data (Article 15 of the GDPR), erasure (Article 17) and restriction of processing (Article 18) each have their own function in Kauppaholvi. The identity of the person asking is checked in the shop from an identity document. The search finds the person by name and date of birth without opening anyone else's data, and the reply is printed in the shop.
  • A customer's personal data can be erased, and your books still stay in order. It can be destroyed on request. The voucher is kept for as long as the law requires, and it holds only what accounting needs.
  • The margin scheme is built in. When the seller is not registered for VAT, the bill of sale produces the voucher that the VAT margin scheme requires.
WhoPersonal dataPurchase historyPDFs and decryption
CustomerTheir own, through the link to their own purchaseNoOwn receipt, limited link
Staff memberOnly for a purchase in progress, with a PINWithout personal dataNo
ManagerWith a recorded reasonYesYes, logged
OwnerWith a recorded reasonYes, plus the audit logYes, logged
AccountantNoNoMonthly package, encrypted

4 · Network and devices

The counter views open only on your shop's own devices. All the internet sees is the customer's page.

Kauppaholvi has three parts, according to the device it is used on: the customer's pages, the counter views and the reports. Only the customer's page answers at the public address. Everything else answers “not found”, and not even a login page shows.

  • The counter and the reports work only inside a closed network. The counter tablet and your own computer connect to the service over an encrypted VPN connection. An attacker scanning the internet can't even see that a login page exists.
  • Why a closed network? New vulnerabilities are now found faster than before with the help of AI, and the internet is scanned as soon as a flaw becomes public. Often a flaw is exploited before the fix is ready. The counter views and the reports can't be reached from the internet at all, so that scanning doesn't reach them even if the software still has an unpatched flaw. A closed network is still only one layer of protection and doesn't replace the others: I install security fixes as a matter of urgency, and logging in always needs a registered device.
  • The customer's page is public because the customer uses their own phone. That's why only a few addresses answer there, guessing attempts are rate-limited, and the link opens only that one purchase.
  • Every device is registered separately. That takes a single-use code that is valid only for a moment. If a tablet goes missing, its access can be cut off at once with a single tap.
  • A password alone gets you nowhere. A registered device is always needed as well, and at the counter a PIN on top of that.
  • Nobody knows anyone else's password. A new member of staff gets a single-use link by email and chooses their own password. You don't see or type anyone's password either. A forgotten password is sorted out with a new link, and using the link ends all old sessions.
  • A tablet left open locks itself. If the tablet sits unused at the counter, it locks, and a countdown warns before it does. The session ends after a set time even if the tablet is in constant use. Attempts to guess a password or a customer link are rate-limited automatically.
  • The code has been reviewed many times. The reviews went one risk area at a time: encryption, chain of evidence, the customer's pages, the server and everything that is visible to the internet. The latest review of the whole application was done in November 2026, and it covered the code, security, and usability and design. The code is reviewed every month.
  • The server is in Finland, and the database is closed to the internet. The database can't be reached from the internet at all. Operating system security updates install automatically. The certificate for your shop's internal network is tied to your shop's own account, so no other server can obtain a certificate in your shop's name.
  • Nothing is lost, even if the server breaks. After every change an encrypted copy leaves the server automatically. The encryption keys don't travel with the copy. I practise restoring regularly, and the chain is checked before a restored database is taken into use. If a copy fails to leave, I get an alert and fix it.
  • A failed update undoes itself. Updates install automatically. If the checks don't pass, Kauppaholvi goes back to the previous version.
  • No credentials are left in the logs. They are filtered out of the server logs, and the logs are moved off the server in encrypted form.
CUSTOMER public internet own phone QR or link own link own purchase only else: “not found” STAFF through VPN only counter tablet registered device password + PIN personal data only during the purchase PDFs: manager only REPORTING through VPN only owner's computer registered device separate sign-in audit log, export no decryption
Three parts, three doors. The reporting view can't decrypt personal data. An automated test that inspects the structure of the code makes sure of that.

5 · The customer's experience

Your customer doesn't download an app, create an account or stand at the counter holding a form.

The customer does their part on their phone while you go through the cards. At the counter, all they do is sign.

  1. A code at the counter

    You open a purchase, and the customer scans the QR code with their phone. The link belongs to this purchase only and is valid only for the same day.

  2. Own details on the phone

    The customer types in their name and contact details themselves, and they are encrypted at once. While you go through the cards, they can look around the shop.

  3. Time to read the terms

    The contract terms come up on the phone right after the details. Accepting them on the phone is optional. At the counter the terms are always one tap away, and the signature is always given at the counter.

  4. The offer on the phone

    The customer goes through your offer line by line, “sell” or “keep”, and decides at their own pace. Nobody hurries them.

  5. A signature on the tablet

    The customer sees the summary and signs on the tablet screen. The content is locked into a fingerprint before the customer signs.

  6. The receipt from a link

    The customer can download their receipt from a link for a limited time and a limited number of times. After that they get a new one at the counter once their identity has been checked.

6 · Location and jurisdiction

The data is in the EU, and those who store the backups do not have the key.

Here I set out where the data is processed, which country's jurisdiction the service's equipment is under and how the data is protected against access by authorities outside the EU. This is the information referred to in Article 28 of the Data Act (EU) 2023/2854.

Part of the serviceWhereProvider
Application, database and documentsHelsinki, FinlandHetzner Online GmbH, Germany
Backups (encrypted), server access logs and usage statistics summariesCloudflare R2, EU jurisdictionCloudflare, Inc., United States
Second copy of the backups (encrypted)Stockholm, SwedenAmazon Web Services EMEA SARL, Luxembourg
Sending emailStockholm, SwedenAmazon Web Services EMEA SARL, Luxembourg
Domain name serviceWorldwide, no shop dataCloudflare, Inc., United States
  • The server is in Finland. The application runs in Hetzner Online GmbH's data centre in Helsinki. The data centre is ISO/IEC 27001 certified. Under Hetzner's data processing agreement, processing takes place only in the EU and the EEA, and a transfer to a third country requires Kauppaholvi's prior consent. No such consent has been given.
  • The backups are in the EU and encrypted. Copies are encrypted before they leave the server. They are stored in Cloudflare R2's EU jurisdiction, with a second copy in Amazon S3 in Stockholm. Neither storage provider has the key.
  • Email is sent from Stockholm. Receipts and the monthly package are sent with Amazon SES from an EU region (Stockholm).
  • US-owned groups. Cloudflare and Amazon Web Services belong to US groups. The data is stored in the EU, but remote access by the groups' staff cannot be ruled out. Any transfer of personal data is based on the EU–US Data Privacy Framework (Commission Decision 2023/1795). If the certification lapses or the decision ceases to be in force, the transfer is based on the Commission's standard contractual clauses, which are part of the provider's agreement.
  • Protection against access by authorities outside the EU. Kauppaholvi is provided by a Finnish company, and the shop's database and documents are on a European company's server in Helsinki. The backups stored by US companies are encrypted before transfer, and the storage providers do not have the key, so access to the stored files would not reveal their content. Backups and email sending are restricted to the services' EU regions. These measures also cover data that is not personal data.
  • Requests from authorities. If the data on the server is subject to seizure, bankruptcy proceedings or another measure by a third party, Hetzner notifies Kauppaholvi without delay, unless the law forbids it.

7 · Switching providers

You get your data out in an open format, and switching costs you nothing.

All of your shop's data belongs to your shop. Here I set out how it moves if you switch to another service, move the data to your own systems or stop, and what the export package contains. This is the information referred to in Article 26 of the Data Act. The detailed terms are in the service agreement.

  1. At most 2 months Notice The shop gives notice that it is starting the switch. The notice period is at most two months. After that the shop says whether it is moving to another service or to its own systems, or asking for the data to be erased.
  2. At most 30 days Transfer The data is transferred to the shop or to the new provider it names. Kauppaholvi looks after the continuity and security of the service throughout the transfer. If a 30-day transition period is not technically feasible, the shop is told so, with reasons, within 14 working days, and the transition period is at most seven months. The shop can extend the transition period once.
  3. At least 30 days Retrieval period After the transition period ends, the shop still has at least 30 days to retrieve its data and check that the material is complete and usable.
  4. Finally Erasure When the switch has succeeded and the retrieval period has ended, the transferred data is erased, unless the law requires it to be kept. It disappears from the backups within six weeks at the latest. The erasure is confirmed in writing.
  • The owner can export the data themselves. The shop's owner can download all the data from the application's export page at any time with a PIN. On request, Kauppaholvi also delivers the package by the fifth working day at the latest. When the service ends, the package is delivered on a USB stick or in another agreed way, and the password travels through a different channel from the file.
  • The data opens without Kauppaholvi. The package is an ordinary encrypted zip file, and free programs are enough to open it. The shop also has its own encryption keys in safekeeping.
  • Everything related to the deals is included. The signed bills of sale with their versions of the terms, the accounting vouchers, the details of the deals and the sellers, signature and timestamp data, the event log and the document hashes that can be used to verify integrity.
  • What is not transferred, and why. Under the service agreement, only the server's technical system and monitoring logs and Kauppaholvi's own user accounts, passwords and service access keys are left out of the transfer. They relate to running the service and not to the shop's deals, and handing them over would endanger the security of the service. The exclusion does not cover the shop's own event log, and it does not prevent or delay the switch.
  • No switching charges. No fee is charged for switching, for help with the switch or for transferring the data, and no penalty is charged for ending the agreement early.
  • Known limitations. The transfer covers data and documents. The application and its source code are not handed over. Personal data that has already been destroyed, at the end of the retention period or on request, is not in the package, and neither are the bill of sale and the receipt that contain it. The deal, the sums and the voucher are still included. Times are in UTC, so Finnish time is two or three hours ahead.
FileFormat and standardData by group
PackageZip, encrypted with WinZip AES-256Opens with 7-Zip (Windows) and Keka (Mac), for example. The password is shown to the owner once or delivered through a different channel.
kaupat.csv, kaupat.jsonCSV (UTF-8, semicolon separator, decimal comma), JSON (RFC 8259, amounts with a decimal point)One deal per row: deal number, status and times, reason for voiding · customer type, minor status, VAT and margin scheme treatment, version of the terms, place of the deal · purchase price, payment method and payment date · comment on a declined offer · names of the signatories and the staff who handled the deal · seller's details: name or company, business ID and representative, address, contact details, bank account number, identity document and guardian's details · status of the personal data · the hash that the seller and the shop signed. In the JSON file the deals' product lines and documents are included.
tuoterivit.csvCSVDeal number and line · product, type, quantity, condition, grade and certificate · market price and its source, buy percentage and purchase price · seller's decision (sells or keeps) · used or new.
asiakirjat/PDFBills of sale with signatures, purchase vouchers, voiding vouchers and receipts, one folder per deal. Each is checked against its seal before export.
asiakirjat.csvCSV, SHA-256Deal number, document type and file name · created and deleted · document status · SHA-256 hash for checking the file's integrity without the application.
tapahtumaloki.csvCSVWho did what and when: time, actor, action, deal, recorded reason, IP address, further details and the row's hash in the chain of evidence.
ketjutarkistus.txtTextThe check of the event log chain and the document seal chain at the time of export.
LUEMINUT.txtText (Finnish)Explanations of the files and hashes, the deal statuses, and what is missing from the package and why.

The CSV files open directly in a Finnish-language Excel: the character set is UTF-8, line breaks are CRLF and times are in ISO 8601 format. An apostrophe is added to the start of a cell if the cell begins with =, +, - or @, so that Excel does not read it as a formula. This list is updated when the structure of the export package changes.