ProofStack Privacy Policy
Version 2026-10-28. Effective 2 November 2026.
ProofStack is built so that the files you seal or check never reach us. They are hashed on your own device and the original stays where you put it. If you save them to Google Drive, they go straight from your browser to Google (paragraph 2.4). That design decides most of what follows.
1. Who we are and what this notice covers
1.1 This notice explains how ProofStack BV processes personal data when you use ProofStack: the web platform at hegna.io, the products Hegna Cam, Hegna Doc, Hegna Screen, Hegna Audio and Hegna Verify, the Proof API, and the verification tools, certificates, proof packages, cases and related services provided through them. Our mobile applications are not yet provided by ProofStack BV (paragraph 1.6). What this notice says about them applies from the date they move to ProofStack BV.
1.2 ProofStack BV is the controller for the processing described here. Our registered office is at Mimosalaan 18, 3191 Boortmeerbeek (Schiplaken), Belgium, enterprise and VAT number BE 1039523066. Write to us at privacy@hegna.io, or call +32 476 86 44 74.
1.3 There is one situation in which we are not the controller. If you are a business customer and you use ProofStack to process personal data of your own users, clients or employees, you are the controller for that data and we act as your processor. Our Data Processing Agreement governs that processing, not this notice. Section 3 of that agreement sets out exactly which data it covers, because the answer is narrower than it usually is for a service of this kind.
1.4 If you use ProofStack under a business account that someone else administers, your employer or client decides who has a seat and can remove it. We tell you here how we process your data. They must tell you why they gave you the account. If someone invites you to a business account, we receive your email address from them.
1.5 Each version of this notice carries a version identifier and a document hash. When you acknowledge it we record which version you were shown. You can ask us for a copy of that version at any time.
1.6 The HashCam mobile applications are still provided by Impact Makers BV, under its own terms, until they move to ProofStack BV. We will tell you by email and in the application before that happens, and this notice applies to them from that date.
1.7 This notice is published in English. Dutch and French versions will follow. Our applications are available in English, Dutch and French. Each language version says the same thing, and you may rely on any version we publish. We publish a further language only once the translation has been checked.
2. What personal data we process
2.1 Account data: your email address, your user identifier, authentication and session identifiers, your plan, your seat within an account, your credit allowance and how much of it you have used in the current cycle. If you sign in with an account you hold elsewhere, such as Google or Apple, we receive from that provider your email address and the identifier it gives us, and your name and profile picture where it sends them. You can also choose to upload a picture for your personal workspace, and one can be uploaded for a team workspace. Unlike the files you seal, that picture is stored by us, in our database. It is shown only inside your account or that workspace, and never on a certificate, a verification result or a shared proof link. Only JPEG and PNG pictures are accepted. Before we store it, we re-encode it, which removes the information kept inside the image file, such as the place where a photograph was taken and the camera that took it. It is the only picture you can upload to ProofStack: the option of our sign-in provider to upload a profile picture of your own is switched off. It is deleted when it is removed or replaced, or when the workspace or the account is deleted (section 10).
2.2 Proof data: SHA-256 hashes, proof identifiers, blockchain transaction hashes, verification links, certificate data, audit events and the time values each proof carries: the capture time, the import time and the date an imported file reports about itself, the hash time, the time of the first submission and of any retries, the blockchain registration time and the certificate time. The registration time is the block time of the blockchain transaction. Every other time value may come from a device or from our servers and has been verified by no one, including us. Where you use cases, we also hold the name you give each case, the note you add to it and which proofs it contains, in our database. A case is not registered on the blockchain and has no timestamp of its own.
2.3 Metadata you choose to attach: media type, capture time, a hash of the file name, workflow identifiers, device and sensor values, and location where it is switched on. Which values are read, on which platform, and whether they are read automatically when a capture screen opens or only when you ask for them, is set out item by item in Annex A. Annex A is part of this notice and is the accurate version of this paragraph. The readings from the weather, compass, altitude and measurement settings, and your location, may be written into your file, its manifest and its receipt, and go wherever those go: to the storage you selected, and to anyone you share them with. They are not sent to our servers: the request that registers a proof carries the hash (paragraph 5.2). Where a value is looked up from an outside provider, paragraph 4.6 says which.
2.4 Storage you select. You choose where your proofs, certificates and gallery records are saved: a folder on your device or, on the plans that include it, Google Drive. Microsoft OneDrive and SharePoint are not offered yet, and we update this notice before they are. We no longer offer to keep them in your browser's own storage. Anything saved there earlier stays in your browser, not with us, until you clear your browsing data. Where you choose a folder on your device, the connection is between your browser and that folder. The permission you grant is held by your browser and is not sent to us. If your device synchronises that folder with a cloud service, such as iCloud Drive, the synchronisation is between you and that service, and ProofStack has no connection to it. Where you connect Google Drive, you sign in with Google and allow ProofStack to use your drive. ProofStack asks Google only for access to the files you use with ProofStack, such as the proofs, certificates and records it saves there, and not to the rest of your drive. It can read, change and delete those files and create new ones. Google then gives us a credential, which we keep encrypted on our servers and use only to give your browser a short-lived access token. Your browser uses that token to save, list, read and delete your proofs, certificates and records directly with Google. The files themselves do not pass through our servers. To show your gallery and to reconnect your drive, we keep the name and identifiers of the folder you select, the identifiers Google gives the files saved there and, for the proofs shown in your gallery, the file name and the title displayed. We never keep their contents. When you reconnect your drive, our servers read from Google the identifiers, names, types, folders and sizes of the files ProofStack can reach there, never their contents, and keep only what is needed to link them to your proofs. When you connect, Google also sends us the display name of the account you connect, where it has one, and an identifier that Google keeps the same for that account. We do not ask Google for the email address of that account. This connection is separate from signing in to ProofStack with Google (paragraph 2.1). You can end the connection at any time in your account settings. We then delete the credential and the connection data from our live database, and the copies in our backups expire within 31 days (paragraph 10.3). Ending the connection does not delete the files already in your drive. When you end it, you can also tick a box to have us ask Google to withdraw the permission you gave, unless another of your workspaces still uses the same drive, because that workspace would then stop working. You can check the result, and withdraw the permission yourself at any time, in your Google account settings. We do not receive the contents of a folder on your device, its file list or its file names, and the gallery records themselves are held in the storage you selected rather than by us. Apart from Google Drive as described in this paragraph, a file name reaches us only where you have chosen to attach it, or a hash of it, as metadata to a proof.
2.5 Payment and billing data: payment references, checkout session identifiers, the plan you subscribed to, subscription and renewal dates, payment status, and the billing details needed to issue an invoice, which for business customers include company name, address and VAT number. We never receive or store your full card details.
VAT evidence. The VAT rules require us to establish, for each payment, the country where you live or where your business is established, and to keep the evidence. We use the country you enter at checkout and the country of your card or bank account, with the payment method it came from, as reported by our payment provider. When the checkout starts we also derive a country from your IP address. Our VAT records hold that country, never the address, and we keep it only where the first two disagree, where one of them is missing or where the VAT rules require a second item of evidence. Otherwise we delete it once the first payment has been taken. Your IP address still appears in our technical logs for the period in section 10. If the evidence does not point to one country, we may ask you to confirm where you live. We ask for a statement, never a document, and we record the decision and the reason. If you give us a VAT number, we check it in the EU VIES system before payment and again before each renewal, and, if VIES was unavailable, for up to seven days afterwards. We keep each result, the time of each check, the request identifier and the name and address VIES returns.
2.6 Technical data: IP address, user agent, request timestamps, API error logs, security events and diagnostic information.
2.7 Support data: the content of the messages you send us and our replies, and the email address you write from. If you report a workspace picture or other content we store (Terms of Use, clause 10.5), we also process your report and our decision on it.
2.8 Consent and acceptance records. For each event we record the event type, the document version and its hash where a document is involved, whether a permission was granted or withdrawn, the time and your user identifier. We do not record your IP address or browser details with these records. Terms acceptance and privacy acknowledgement are recorded separately from each other, and accepting the same version again does not overwrite the first acceptance. If you withdraw from a subscription online, we record the statement you submitted and the time we received it. The application only adds to these records and does not change them. Someone with administrative access to our database could still change or delete them, which is why that access is limited to the people who need it (paragraph 11.1). If you close your account, we keep them for the period in section 10, linked only to an internal identifier, without your email address or sign-in identity.
2.9 Do you have to give us this data? The account, proof, payment and technical data in this section is necessary in order to provide ProofStack. Without it we cannot open an account, register a proof or take payment. The metadata in paragraph 2.3 is optional, and so is connecting a cloud drive under paragraph 2.4. If you do not turn them on, proofs are still created, with less information attached to them.
2.10 Single-file verification through Hegna Verify is free and is used without an account and without signing in. When it is used that way we process the hash being checked, which is calculated in your browser, the technical data in paragraph 2.6, and, where the file carries Content Credentials, what paragraph 2.11 describes.
2.11 Content Credentials. ProofStack does not currently add Content Credentials to your files. It does check them: when you check a file in Hegna Verify or in one of our applications, the credential carried by that file is validated on your own device. Validating it can, however, cause the application to request a manifest, or the identity document of whoever signed the credential, from an address contained in the file itself. That server is chosen by whoever created the file, not by us. It does not receive your file. It receives the request and the connection information that carries it, including your IP address, and it learns that a check was run. A manifest can itself contain personal data, including camera make and model, edit history, location and, where identity assertions are used, the name, handle or wallet address of whoever created the file. That person may not be you and may never have heard of us. We display what the manifest contains, we do not store it, and it is not written to the blockchain.
2.12 Screen and audio recordings. Hegna Screen records the screen, window or tab you select in your browser's sharing prompt, as a screenshot or a video, and includes the sound that screen, window or tab plays only if you tick the box and your browser offers it. It never records your microphone. Hegna Audio records from your microphone and mixes a short spoken seal into the recording on your device. Both recordings are made and sealed on your device and saved to the storage you selected. They are not sent to any AI or speech provider, and not to us. What we receive is the proof data in paragraph 2.2, as for any other file. A recording can contain other people's voices, names, messages or images, and confidential material. Your browser's permission covers your device, not them, so record and share only what you are entitled to.
2.13 Checking and importing proof bundles. Hegna Verify can check a Safe2Share ZIP bundle, including bundles from Hegna Screen and Hegna Audio, and export the result as a CSV audit file. The bundle is opened, its files are counted and checked, and the CSV file is produced, all in your browser. Its files are not sent to us. Checking the blockchain record of each file sends its hash to our servers and to the blockchain, with the technical data in paragraph 2.6. A check of up to 20 files is free and needs no account. Checking more at once needs Hegna Verify Pro, which is included in the Business Premium and Enterprise plans. The count is made in your browser and is not kept by us. Importing a bundle from our mobile applications into your library copies it into the storage you selected. An import is not a blockchain verification and does not create a new timestamp. Where you use Hegna Verify Pro, we also process your account and billing data, and we may keep a record of the checks run under your account, such as when each check was run and what it found.
3. Why we process it, and on what legal basis
3.1 The table below sets out each purpose, the data it uses and the legal basis we rely on. Article references are to the General Data Protection Regulation unless stated otherwise.
| Purpose | Data used | Legal basis |
|---|---|---|
| Open and manage your account, authenticate you, keep you signed in, manage seats on a business account | Account data | Performance of the contract, Article 6(1)(b) |
| Create, register and verify proofs, generate certificates and proof packages, and keep related proofs together in cases | Proof data, metadata you attach, case names and notes | Performance of the contract, Article 6(1)(b) |
| Read information from your device, such as camera, NFC, sensor or location values | Device permissions | Your consent given through the device or browser permission prompt, Article 5(3) of the ePrivacy Directive and Article 10/2 of the Belgian Act of 30 July 2018, except where access is strictly necessary for a function you asked for (paragraph 4.3). The metadata that results is then processed to perform the contract |
| Save your proofs, certificates and records to the storage you select, and show them in a gallery | The permission you give your browser, or the credential and access token for a Google Drive you connect, and the proof records shown | Performance of the contract, Article 6(1)(b). The permission to a folder is granted through your browser and is not transmitted to us. A cloud drive is connected only when you sign in with its provider and allow it. |
| Look up weather, air quality, altitude or similar values for a capture | Your location coordinates, sent to the weather or air-quality provider | Your consent through the device or browser location permission, Article 5(3) of the ePrivacy Directive and Article 10/2 of the Belgian Act of 30 July 2018, and performance of the contract for the feature you asked for. |
| Check the Content Credentials carried by a file, including any request to a server named in the file | The credential, and the connection information sent with any such request | Performance of the contract for the check you asked for, Article 6(1)(b), and our legitimate interest in providing a free verification tool, Article 6(1)(f) |
| Run your subscription, take payment, issue and keep invoices, send the renewal reminder for annual plans, and acknowledge an online withdrawal | Payment and billing data, account data, withdrawal records | Performance of the contract, Article 6(1)(b), including the renewal reminder, and legal obligation, Article 6(1)(c), for invoicing and accounting retention and for the withdrawal acknowledgement consumer law requires (and for the renewal reminder, where consumer law requires it) |
| Establish which VAT applies to your purchase, validate a VAT number, and keep the evidence the VAT rules require | VAT evidence (paragraph 2.5), payment and billing data | Legal obligation, Article 6(1)(c), under the VAT Directive (2006/112/EC), Implementing Regulation (EU) No 282/2011 and the Belgian VAT Code |
| Record which version of the Terms you accepted, and which permissions you granted or withdrew | Consent and acceptance records | Our legitimate interest, Article 6(1)(f), in being able to show what was agreed and which permissions were given, which consumer law expects of us, because it puts on us the burden of proving that the required information was given and the request was made; for any consent, legal obligation, Article 6(1)(c), read with Article 7(1) |
| Protect the service against abuse, fraud and attack, investigate and report security incidents | Technical data | Legitimate interests, Article 6(1)(f), and legal obligation under Article 19a of Regulation (EU) No 910/2014 as amended, Article 6(1)(c) |
| Find and fix errors and performance problems in the service | Technical data in our hosting provider's logs of requests to our servers and of errors on them | Legitimate interests, Article 6(1)(f): keeping the service working for the people who rely on it |
| Answer your support requests | Support data, account data where you have an account | Performance of the contract, Article 6(1)(b), where you are a customer, and our legitimate interest, Article 6(1)(f), in answering visitors who write to us. For a report under clause 10.5 of the Terms of Use, legal obligation, Article 6(1)(c), under Articles 16 and 17 of the Digital Services Act (Regulation (EU) 2022/2065) |
| Comply with legal obligations and answer lawful requests from authorities | As required by the obligation | Legal obligation, Article 6(1)(c) |
| Establish, exercise or defend legal claims | As required by the claim | Legitimate interests, Article 6(1)(f) |
3.2 Where we rely on legitimate interests we weigh our interest against your rights and we record that assessment. You can ask us for a summary of it at privacy@hegna.io. You can object at any time (paragraph 3.4).
3.3 We do not process your personal data for advertising, and we do not profile you.
3.4 Your right to object. Where we rely on our legitimate interests (the rows in paragraph 3.1 that cite Article 6(1)(f)), you can object at any time, on grounds relating to your particular situation. Write to privacy@hegna.io. We then stop, unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend legal claims.
4. Your device, and what we read from it
4.1 Reading information that is stored on your device, or accessing your camera, sensors or location, is governed by Article 5(3) of the ePrivacy Directive and Article 10/2 of the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data. What we then do with the resulting metadata is governed by the GDPR.
4.2 Your device or browser presents the permission prompt, and nothing is read until you allow it. You can withdraw the permission at any time in your device or browser settings, and you can decline any individual capture. If you decline, the feature either works with less information or does not work at all, and we tell you which.
4.3 Where access to your device is strictly necessary in order to deliver a function you have explicitly asked for, such as opening the camera when you press capture, Article 5(3) does not require a separate consent beyond that request and the device permission itself.
4.4 Location is treated as optional throughout and you can refuse or withdraw the permission at any time. On the web, location is switched off by default. It is read only if you switch it on and your browser grants permission. To work out your position, your browser or operating system may use a location service of its own, which it chooses, not us. Your coordinates are drawn into the photograph or video only if you also choose to show them there; otherwise they are kept with the proof as metadata only. Once the mobile applications have moved to us (paragraph 1.6), the following also applies. On Android, turning a value off on the watermark stops it being displayed but does not always stop it being read: the capture screen begins reading compass and pressure when it opens, and where location is available, weather and air-quality lookups are made whether or not those values are shown.
4.5 The same principle applies to any other device or sensor value: we read it only where it is needed for a feature you asked for, and subject to the permission your device or browser controls.
4.6 Once the mobile applications have moved to us (paragraph 1.6), some of those values are not read from your device but fetched for it. Where a weather, air-quality, altitude or similar value is shown, your coordinates are sent to the provider that supplies it, currently Apple WeatherKit on iOS and Open-Meteo on Android and for air quality. Apple Maps and Open-Meteo also receive your coordinates to find the time zone shown on a certificate. Your photograph, video or document is never sent to them. Those providers are not our processors: they receive coordinates and answer a question, and they decide for themselves what they do with the request. Section 8 lists them.
4.7 Screen and microphone. Your browser asks you which screen, window or tab to share, and shows while it is being shared. Hegna Screen stops sharing after a screenshot, and when you stop or cancel a recording. Hegna Audio asks for the microphone only when you press Start.
5. Your files stay with you, and where your proofs are kept
5.1 ProofStack reads and hashes your file locally, in your browser or on your device. The file is not uploaded to us for hashing or for verification, and we do not store it. Local processing is still processing, so we say what the application does rather than that nothing happens: it reads the file in order to hash it, and it reads the values that any metadata you asked for requires.
5.2 What is transmitted to us is the hash, the metadata you attached or the workflow requires, and the technical data needed to create or verify the proof. The readings from the weather, compass, altitude and measurement settings, and your location, are not (paragraph 2.3).
5.3 Where a gallery displays files from a folder you nominate, that folder stays yours. The permission sits in your browser, not with us. The application can create and delete files inside that folder, which is how proofs and certificates are written into it, so choose the folder narrowly. In Google Drive, the application can create, change and delete only the files you use with ProofStack (paragraph 2.4).
5.4 Verification is designed so that a third party can compare the hash of the original file with the recorded proof without sending the original file to us or to anyone else. That is true of the file. It is not the same as saying that verification contacts nobody: checking the blockchain record needs a network request to our systems and to the blockchain, and checking a Content Credential can contact a server named in the file, as paragraph 2.11 explains.
5.5 If we release a feature that requires an original file to be uploaded or stored, that feature will say so clearly before you use it, and we will update this notice before it goes live.
5.6 Where your proofs, certificates and gallery records are kept depends on the storage you select. If you choose a folder on your device, they are written into it and they stay there. What you saved in your browser's own storage before we stopped offering it stays there until you clear your browsing data (paragraph 2.4). The exception is automatic capture: photographs wait in your browser until they are sealed and saved to your storage, and may remain there until you clear your browsing data. If you connect a cloud drive, they are written into it and held by that provider under your own agreement with it. Once the mobile applications have moved to us (paragraph 1.6), what they create is held in the application's own storage on your device.
5.7 Three things follow, and they are the questions worth asking before you rely on any of this. A folder on your device does not come with you when you change device, unless you copy it or it is synchronised. A cloud drive does. Signing out does not delete what is held in your folder or your drive. Closing your account does not reach into your device, your folder or your drive at all: what you hold stays with you, and what we delete is in section 10.
6. Cookies and local storage
6.1 ProofStack uses only what it needs in order to work: a session cookie or token, authentication and refresh tokens held in your browser or app, and storage used for security and to remember your preferences. Under Article 5(3) of the ePrivacy Directive and Article 10/2 of the Belgian Act of 30 July 2018, storage strictly necessary to deliver a service you have requested does not require consent.
6.2 We do not use advertising or tracking cookies and we do not profile you. We do not use Google Analytics, product analytics, visitor analytics, session replay or a separate error-reporting service. When something breaks on our servers, we find it in our hosting provider's logs (paragraph 8.2). If we add an error-reporting service, we update this notice and the list at hegna.io/subprocessors before it receives any data (paragraph 8.4). Our hosting provider protects the service against attacks and automated abuse. Where it decides to check that a visitor is a real browser, it runs a short check in your browser and keeps a record that the check was passed for one hour (Cookie and Local Storage Policy, paragraph 3.5). Our hosting provider also processes technical data to run, monitor and protect the service. Nothing that is not strictly necessary is stored on or read from your device without asking you first, and the Cookie and Local Storage Policy is updated before it is.
6.3 Our Cookie and Local Storage Policy lists every item we set, what it does and how long it lasts.
7. Blockchain records, and what erasure means here
7.1 ProofStack writes a SHA-256 hash, a proof identifier and a timestamp to Base, a public blockchain that settles on Ethereum. No original file, no file content and no directly identifying personal data is written on-chain. We do not intentionally write personal data or personal metadata on-chain at all.
7.2 A hash is designed so that the underlying content cannot be reconstructed from it, and we do not keep the original file.
7.3 Our position on the status of an on-chain hash is as follows. Where we can link the hash to your account using information we hold off-chain, we treat the hash as personal data and apply the rights described in section 12. For another person accessing the blockchain, the position may be different. Where that person has no means reasonably likely to enable them, directly or indirectly, to link the hash to an identified or identifiable individual, the hash may not constitute personal data in that person's hands. This reflects the context-specific approach to identifiability confirmed by the Court of Justice in Case C-413/23 P, EDPS v SRB, judgment of 4 September 2025.
7.4 ProofStack BV acts as controller in respect of writing the record. Because of how distributed ledgers work, a confirmed on-chain record cannot be altered or deleted, by us or by anyone else.
7.5 If you ask us to erase your personal data, we delete the off-chain records that link a hash to your account, your email address and your metadata, subject to the retention exceptions in section 10. After that deletion, neither we nor anyone else can associate the on-chain record with you, and by our reading in paragraph 7.3 what remains on-chain is no longer personal data. We consider this the proportionate way to reconcile the integrity purpose of the service with your rights under Article 17 GDPR, and we would explain it in those terms to a supervisory authority. Proofs made in a team workspace are held for the business that runs it, which decides on their erasure (paragraph 12.5). If you leave that workspace or close your account, we remove your name and email address from our records of it and keep only an internal identifier, the role you had and the time of the change, but the business, and the certificates and metadata it holds, may still connect those proofs to you.
7.6 There is a consequence you should understand before you use the service. Erasure of the link makes the on-chain record anonymous, and it also makes it useless to you. A proof you can no longer connect to yourself is a proof you can no longer rely on. If you may need the proof later, keep your certificates and proof packages, and ask us for a copy of your proof records (paragraph 12.4), before you ask us to erase. Closing your account has the same effect: we then delete the proof records we hold for it (section 10). Proofs made in a team workspace are the exception: they belong to that workspace and stay with it (section 10).
7.7 If you would rather no hash of a file were recorded on a public blockchain, do not register a proof for that file.
8. Who else is involved
8.1 We do not sell your personal data, and we do not share it so that someone else can market to you.
8.2 We use the following service providers, each of them a processor acting on our instructions.
| Provider | What they do |
|---|---|
| Vercel Inc., United States | Hosting of the website, the web application and its backend, with compute set to the Paris, France region. Vercel's platform logs, caches and outage failover are not confined to that region, and Vercel provides for processing in the United States under its data processing addendum. See section 9. Observability Plus is active for our projects, so Vercel keeps runtime logs of requests to our servers for up to 30 days (section 10). Vercel also stores, encrypted and in the Paris region, our record of deletions (paragraph 10.3). |
| Combell NV, Belgium | Domain names, and email hosting for some of our mailboxes |
| Google Cloud EMEA Limited, Ireland (Google Workspace) | Email for our team mailboxes, including the hegna.io mailboxes and the messages you send us. Google may store this data in its data centres outside the EEA, including in the United States. See section 9. |
| Clerk, Inc., United States | Authentication and account management, including the sign-in emails. Clerk's published information describes infrastructure hosted in the United States. See section 9. |
| UpCloud Oy, Finland | Storage of account, billing, VAT evidence and proof records in a managed database in UpCloud's Amsterdam data centre, in the Netherlands. UpCloud runs its data centres in the EU itself, without sub-processors. Backups are taken daily, encrypted, stored separately from the database within the EU, and held for 31 days (section 10). |
| Billit NV, Belgium | Invoice generation and delivery of structured electronic invoices to business customers over the Peppol network. It may also send invoices and corrected invoices to you by email. |
| Xienu BV, Belgium | Our accountant: bookkeeping and VAT returns. It may act as an independent professional under its own rules. |
| Resend (Plus Five Five, Inc.), United States | Email sent from our contact form, invitations to join a business account, and our service emails: the contract confirmation with the accepted Terms attached, the renewal reminder for annual plans, the acknowledgement of an online withdrawal, the notice to the owners of a team workspace when its business subscription ends, and corrected invoices. These emails may be processed in the United States. See section 9. |
8.3 The following third parties receive personal data from ProofStack without being our processors.
| Who | What they receive, and in what capacity |
|---|---|
| Apple Distribution International Ltd, Google | Once the mobile applications have moved to us (paragraph 1.6), where you subscribe through the App Store or Google Play, the store operator is the seller and holds your purchase, billing and refund data. It is an independent controller for that transaction and its own privacy notice governs it. We receive the fact of the subscription and the proceeds |
| Google, as provider of Google Drive, where you connect it | Where you connect Google Drive, Google receives the files your browser saves there at your request, and issues the credential described in paragraph 2.4. It holds your files under your own agreement with it, as your provider, not ours. It sends us the display name of the account you connect, where it has one, and an identifier for that account, but not its email address. |
| Mollie B.V., Netherlands | Processes your payment for subscriptions bought at hegna.io. Mollie acts as an independent controller under its own privacy statement, because payment and anti-money-laundering law give it obligations of its own. We receive the payment status and references, never your full card details |
| Apple WeatherKit, Open-Meteo, Apple Maps | Your coordinates, where a weather, air-quality or related value is requested for a capture. They never receive your file. Each decides for itself what it does with the request, so each is an independent controller. Apple Maps and Open-Meteo also receive your coordinates for the time zone shown on a certificate. This row applies once the mobile applications have moved to us (paragraph 1.6). |
| Servers named inside a file's own Content Credentials | Where checking a credential requires a manifest or an issuer's identity document to be fetched, the request for it and the connection information that carries it, including your IP address. These servers are not our processors and are not chosen by us. They are chosen by whoever created the file. See paragraph 2.11 |
| The Base node and RPC provider | The transaction we submit, which contains a hash, a proof identifier and a timestamp. In that provider's hands, with no access to the off-chain link, that payload does not identify anyone, which is why it is listed here rather than as a sub-processor. See paragraph 7.3, and the note in Annex 1 of our Data Processing Agreement |
| The EU VIES system, run by the European Commission with the national tax authorities | Your VAT number, if you give us one, together with ours, when we check whether yours is valid. Each is responsible for its own processing |
| Anyone, through the public blockchain | Whatever is written on-chain is public and permanent. See section 7 |
8.4 The current list, including any provider added after the date of this notice, is maintained at hegna.io/subprocessors. We tell you before a new provider starts processing your data, so that you can object if you have grounds to.
8.5 We may also disclose personal data where the law requires it, to answer a lawful request from an authority, or to establish, exercise or defend a legal claim. Our VAT returns and One Stop Shop returns contain totals, not your details. Where you are a business customer in another member state, your VAT number appears in the listing of intra-Community services we file with the Belgian tax administration. Our VAT records about individual purchases are made available to a tax administration only when it asks for them, as the VAT rules require.
8.6 Blockchain transactions and smart contract events are public by design. Hashes and transaction identifiers written on-chain are visible to anyone and cannot be removed. See section 7.
9. Transfers outside the European Economic Area
9.1 We keep processing inside the European Economic Area wherever we reasonably can, and we choose providers and settings on that basis. That is a direction we work towards, not a claim that nothing ever leaves the EEA. Where it does, this section says how.
9.2 Hosting. Our website, web application and backend run on Vercel, a United States company, with compute set to a region in France. Selecting that region does not make the arrangement EU-only: Vercel's platform logs, caches and support access, and the automatic rerouting of traffic to another region during an outage, can involve processing outside the EEA, and Vercel's data processing addendum provides for transfers to the United States. We rely on Vercel's certification under the EU-US Data Privacy Framework, and keep the Standard Contractual Clauses it offers as a fallback. If we ever have to rely on those clauses, we assess the transfer first, as paragraph 9.3 describes.
Clerk and Resend are United States companies too, and Google Workspace is provided to us by Google Cloud EMEA Limited in Ireland, with data that Google may store in the United States. Clerk, Resend and Google LLC state that they are certified under the EU-US Data Privacy Framework. UpCloud, which holds our database, is a Finnish company and keeps it in its Amsterdam data centre, inside the EEA, and its backups in the EU.
9.3 Where any other provider or one of its sub-processors processes personal data outside the European Economic Area, we rely on an adequacy decision of the European Commission where one covers the country, or on the Standard Contractual Clauses adopted by Decision (EU) 2021/914 together with a transfer impact assessment made before we rely on them, and any additional measures that assessment calls for.
9.4 Where a United States provider is certified under the EU-US Data Privacy Framework, we may rely on the Commission's adequacy decision of 10 July 2023. We monitor its status. The General Court dismissed the first challenge to it in Latombe v Commission on 3 September 2025, and an appeal is pending before the Court of Justice (Case C-703/25 P), so, where the provider's terms include them, we keep Standard Contractual Clauses in place as a fallback rather than relying on adequacy alone.
9.5 You can ask us at privacy@hegna.io which mechanism applies to a particular provider and, where we are able to share it, for a copy of the relevant safeguards.
10. How long we keep it
10.1 We keep personal data for the periods below.
| Category | Retention period |
|---|---|
| Account data | While your account is open, then 30 days after closure, after which it is deleted, except for an internal identifier that links the records we must keep (paragraph 2.8) |
| Proof records: hashes, proof identifiers, transaction hashes, timestamps, certificate data | While your account is open, then deleted with your account data (paragraph 7.6). A proof can still be verified against the blockchain with the file and its certificate. On-chain records persist indefinitely and are outside our control. Proofs made in a team workspace belong to that workspace. When a member leaves it, is removed from it or closes their own account, those proofs stay with the workspace, and our records of that workspace no longer hold that member's name or email address, only an internal identifier, the role the member had and the time of the change. They are deleted when the workspace is deleted, or 30 days after the business subscription has ended, once its export period has passed (Data Processing Agreement, section 9). We email the owners when the subscription ends, giving that date |
| Gallery records and certificates held in the storage you selected, and folder permissions held in your browser | Not held by us at all. They stay in your folder or your cloud drive until you remove them. See paragraphs 5.6 and 5.7 |
| Credential for a Google Drive you connect, and the access token issued from it | The credential, held encrypted on our servers: until you end the connection or close your account, and in our backups for up to 31 days after that. The access token in your browser: until it expires, after a short time, or until you clear your browsing data |
| Display name of the Google account, where it has one, and the identifier Google gives that account | Until you end the connection or close your account |
| Name and identifiers of the Google Drive folder you selected, identifiers of the files saved there, and the file names and titles of the proofs shown in your gallery | While your account is open, then deleted with it |
| Records of Hegna Verify Pro checks | While your account is open, then deleted with it |
| Case names, notes and the list of proofs in each case | While your account is open, then deleted with it. For a case in a team workspace: as for the proofs of that workspace |
| Picture uploaded for a personal or team workspace | Until it is removed or replaced, or the workspace or the account is deleted, and in our backups for up to 31 days after that |
| Consent and acceptance records | Acceptance of the Terms, privacy acknowledgements and checkout consents of paying customers: 10 years from the event, matching the limitation period for contractual claims, also after your account is closed (paragraph 2.8). Permission records, and acceptance records of accounts that never paid: 5 years from the event, also after your account is closed |
| Withdrawal statements and our acknowledgements | 10 years from the event, matching the limitation period for contractual claims, also after your account is closed |
| Invoices, credit notes, payment and accounting records | Ten years from 1 January of the year after the document was issued, matching the limitation period for contractual claims and covering the period in Article 60 of the VAT Code. For sales under the One Stop Shop, see the next row |
| Invoices and VAT evidence for sales to consumers in other member states under the One Stop Shop | Ten years from the end of the year of the sale (Article 369k(2) of the VAT Directive and Article 58quater, paragraph 7 of the VAT Code) |
| VAT evidence for all other sales, including VAT number checks | Ten years from 1 January of the year after the invoice was issued, matching the limitation period for contractual claims and covering the period in Article 60 of the VAT Code. |
| Technical and security logs | 12 months, or longer where a specific record is needed to investigate an incident, to meet a reporting obligation or to support a claim. Our hosting provider keeps its runtime logs for up to 30 days. |
| Security incident records under Article 19a of Regulation (EU) No 910/2014 and Article 23 of Directive (EU) 2022/2555 | 5 years from closure of the incident |
| Support correspondence | 24 months after your request is closed |
| Backups | Taken daily, encrypted, kept within the EU for 31 days. See paragraph 10.3 |
10.2 Where a longer period is needed to comply with a legal obligation, to establish, exercise or defend a legal claim, or to prevent fraud, we keep only the records that serve that purpose and we delete the rest. Where a sale is corrected, we count from the last invoice, credit note or correction linked to it. Records under audit, in dispute or under review are kept until that matter is closed.
10.3 Deletion is not instantaneous everywhere, and it would be misleading to imply that it is. When a record is deleted from the live system it continues to exist in encrypted backups until the backup rotation has passed, which takes up to 31 days. During that window the record is not used, not restored selectively and not accessible other than through a full restoration of the environment. If we ever restore a backup, we first apply again every deletion made after the point to which it is restored. For that we keep an encrypted record of deletions outside our database, in the Paris region, holding only internal identifiers, the kind of record deleted and the time, for 32 days, one day longer than our backups.
11. How we protect it, and what happens if something goes wrong
11.1 We apply technical and organisational measures appropriate to the risk. Connections to the service are encrypted in transit, our database provider encrypts the backups, and access to personal data is limited to the people who need it. Multi-factor authentication for privileged access, logging of administrative access and full separation between test and production environments are being introduced, and we do not describe them as in place until they are.
11.2 The strongest measure is structural rather than technical. Your original files are not uploaded to us, so a breach of our systems does not expose them directly. Files you save to Google Drive go there straight from your browser. If you connected Google Drive, a breach could expose the encrypted credential we hold for it. It is encrypted with a key kept apart from our database, so a copy of the database alone does not open it. With its key, that credential reaches the files you use with ProofStack in your drive, which can include your photographs, videos and certificates, though not the rest of your drive (paragraph 2.4).
11.3 If a personal data breach occurs, we notify the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit, Autorité de protection des données) within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to your rights and freedoms. Where the breach is likely to result in a high risk to you, we tell you as well, without undue delay, and we describe what happened, what we are doing about it and what you can do.
11.4 Two further regimes sit alongside the GDPR. ProofStack BV provides electronic timestamps, which makes it a non-qualified trust service provider under Regulation (EU) No 910/2014 as amended. Article 19a of that Regulation requires us to notify a security breach or a disruption with a significant impact on the service, and where relevant the individuals affected and the public, within 24 hours of becoming aware of it. Because we are a trust service provider we are also an important entity under Directive (EU) 2022/2555, regardless of our size, which adds, for a significant incident, an early warning within 24 hours, a notification within 72 hours or, where the incident affects our trust service, within 24 hours (Article 23(4)), and a final report within one month, to the Centre for Cybersecurity Belgium. One event can therefore be reportable three times over, to three different recipients, and the shortest deadline governs the first move.
12. Your rights
12.1 Subject to the conditions in the GDPR, you may ask us for access to your personal data, for rectification of data that is wrong, for erasure, for restriction of processing, for a copy in a portable format, and you may object to processing we base on legitimate interests. Paragraph 3.4 explains your right to object.
12.2 Where processing rests on your consent or on a device permission, you may withdraw it at any time. Withdrawal does not affect processing that already happened, or processing that rests on another basis.
12.3 We do not take decisions about you by automated means that produce legal effects or similarly significantly affect you, within the meaning of Article 22 GDPR.
12.4 To exercise a right, write to privacy@hegna.io. We answer within one month, and we tell you if we need longer, which the GDPR allows in limited cases. We may need to verify who you are first, and we ask for no more information than that requires. For a copy of your account data and proof records as we hold them, write to the same address. We provide it within one month, free of charge, in a structured, commonly used and machine-readable format. Your certificates and proof packages are held on your device or in the storage you selected. You can copy them from there yourself, and where a product offers a download, you can download them too. If you cannot reach one, write to us and we will help where we can.
12.5 If you are a user on a business account and your request concerns data your employer or client controls, we will pass the request on to them and tell you that we have.
12.6 If you are not satisfied, you have the right under Article 77 GDPR to lodge a complaint with a supervisory authority, in the member state where you live or work or where the alleged infringement took place. The Belgian authority is the Data Protection Authority (Gegevensbeschermingsautoriteit, Autorité de protection des données), Drukpersstraat 35, 1000 Brussels, +32 2 274 48 00, contact@apd-gba.be, www.gegevensbeschermingsautoriteit.be. Under Article 79 you may also go to court, including the courts of the member state where you live.
13. Age
13.1 ProofStack is not for children. You must be at least 18 to open an account or subscribe. We do not knowingly process the personal data of anyone under 18. If you believe a child has given us personal data, write to privacy@hegna.io and we will delete it.
14. Changes to this notice
14.1 We update this notice when the service, the law, our providers or our security practices change. Each version carries its own identifier and hash, and the current version is always published on the ProofStack website.
14.2 Where a change is material, we bring it to your attention before it takes effect, by in-app message, email or another channel we can show reached you.
14.3 This is a notice, not a contract. We ask you to acknowledge that you have been informed. We do not ask you to accept it, and nothing in it creates obligations on you.
15. Contact
For any question about this notice or about how we handle your personal data, write to ProofStack BV, Mimosalaan 18, 3191 Boortmeerbeek (Schiplaken), Belgium, or email privacy@hegna.io.
Annex A. What each product reads from your device
The iOS and Android columns apply once the mobile applications have moved to ProofStack BV (paragraph 1.6).
This annex is part of this notice. It is the item-by-item version of paragraph 2.3, and where the two differ, this annex governs. Automatic means read when the relevant screen or feature is active and the device permission allows it. It does not mean continuous background collection. Showing a value on a watermark and reading it are two different settings, and on Android they are currently not the same, which is why the rows say so.
| Information | Web app | iOS app | Android app |
|---|---|---|---|
| Camera images | Read when you use a capture feature and camera access is allowed. Processed locally. | Read when you use the camera and access is allowed. Processed locally. | Read when you use the camera and access is allowed. Processed locally. |
| Camera settings | Reads the available cameras and the selected camera's settings, such as image dimensions and facing direction. | Uses camera settings, orientation and zoom. Some of it can appear in the local certificate. | Uses camera settings, orientation and information about supported camera features. |
| Microphone and recorded audio | Video capture requests microphone access. Hegna Audio requests it when you press Start. Hegna Screen never uses it. | Used for video audio and for optional noise measurement, subject to permission. | Used for video audio and for optional noise measurement, subject to permission. |
| Screen content | Read only from the screen, window or tab you select in the browser's sharing prompt, for Hegna Screen. The sound that tab or window plays is included only if you tick the box. | Where the application offers it, it reads only what you select in the system's sharing prompt. | Where the application offers it, it reads only what you select in the system's sharing prompt. |
| Noise level | No separate noise measurement. | Read when the noise feature is enabled and available, with microphone permission. | Read when noise measurement is enabled and microphone permission is available. Video recording can also supply audio level information. |
| Location and accuracy | Off by default. Read only when you switch location on and the browser grants permission. Drawn into the photograph or video only if you also choose to show it there. | Read by location-related features, subject to your settings and the device permission. | Read during capture where location permission is available. Hiding the coordinates from the watermark does not stop the reading. |
| Altitude | Read from the location result where available, even if altitude is not shown. | Read when the altitude feature is enabled and available, using location and altimeter information. | Reads pressure when the capture screen opens, and uses location-based altitude where available. |
| Compass or heading | Read from the browser's location result. Not necessarily a magnetic compass reading. | Read when the compass feature is enabled and available. | Starts reading the rotation sensor when the capture screen opens and calculates heading from it. This does not depend on showing the compass. |
| Speed | Read from the browser's location result where available. | Read when the speedometer feature is enabled and available. | Calculated from available location information during capture. |
| Motion and orientation | Uses camera facing and track settings. No separate accelerometer or gyroscope reading. | Used for camera orientation. The settings screen also reads tilt for a visual effect, separately from proof settings. | Used for camera orientation and heading. |
| Air pressure | No direct pressure reading found. | Used by the altimeter when it is enabled. | Pressure readings start when capture telemetry starts, where the device has the sensor. |
| Weather, temperature and wind | No weather lookup. | Requested from Apple WeatherKit where an enabled weather feature needs it. The request uses your location. | Requested from Open-Meteo where location is available. The request is not controlled by the individual weather display setting. |
| UV index | No separate lookup found. | Obtained with weather information; its display has its own setting. | Requested with weather information, even where UV is not shown. |
| Air quality | No separate lookup found. | An Open-Meteo air-quality lookup is present and sends coordinates. | Requested from Open-Meteo alongside weather, even where air quality is not shown. |
| Depth and measurement | No equivalent feature found. | Used by supported depth and measurement features when they are enabled or opened. Processing is local. | Checks whether depth hardware or software is available. The check alone does not mean depth images are collected. |
| QR and NFC information | Not offered at launch. | QR and NFC modes read payloads when enabled or used, and these can be included in local proof files. | Where the application offers it, read when enabled or used. |
| Content Credentials check | Validated in the browser. Can request a manifest or an issuer's identity document from an address inside the file. No certificate revocation lookup, no trust-list download and no upload of the file. | Validated on the device. Same behaviour as the web app. | Validated on the device. Same behaviour as the web app. |
| Device, operating system and app details | Reads browser information for certificate details, and includes the app version. | Uses device model, operating system and app details in certificates. | Uses manufacturer, device model and Android version in certificates. |
| Device identifier | None. The web application creates no device identifier and prints no device hash on certificates. | Keeps a random installation identifier in the Keychain and derives a device hash used in certificates. | Reads the Android identifier to derive a device identity used in certificates. |
| Date and time | Capture time uses the device clock. Blockchain registration time is the block time of the transaction. Other times may come from the device or from our servers and are not verified. | Uses the device clock for capture, hashing and, where recorded, submission. Recorded in UTC. Blockchain registration time comes from the block. | Uses the device clock for capture, hashing, queueing and, where recorded, submission. Recorded in UTC. Blockchain registration time comes from the block. |
| System preferences | Reads the system theme preference for appearance. | Uses reduced-motion and low-power settings for interface behaviour. | Reads system information needed for compatibility. No battery-level reading. |
