PRIVACY POLICY & DATA PROTECTION NOTICE
1. Scope & General Information
This Privacy Policy (“Policy”) explains how Human Oversight Laboratories OÜ (“we,” “us,” or “our”) collects, uses, stores, discloses, and protects personal data obtained from individuals (“you” or “Data Subject”) who interact with our services.
1.1 Material Scope
This Policy applies to processing carried out through:
- Our website at art50compliance.eu, including any subdomains;
- The Art50 application at app.art50compliance.eu, comprising the Human Responsibility Ledger, the AI Inventory, and the Art50 API;
- Public verification pages served at verify.art50compliance.eu;
- Our newsletter and marketing communications; and
- Communication channels used for customer support and enquiries (together, the “Services”).
1.2 Statutory Compliance
We process all personal data in accordance with:
- Regulation (EU) 2016/679 (General Data Protection Regulation, “GDPR”);
- Directive 2002/58/EC (ePrivacy Directive); and
- The Estonian Personal Data Protection Act and other applicable national laws of EU Member States.
1.3 Application
By accessing our website, creating an account, or using the Services, you acknowledge that your personal data will be handled in accordance with this Policy. This Policy does not apply to third-party websites, applications, or services linked from our platform.
2. Identity & Contact Details of the Controller
2.1 Data Controller
The controller responsible for the processing described in this Policy is:
Human Oversight Laboratories OÜ
Registered in the Estonian Commercial Register under registry code 17617561
Tartu mnt 67/1-13b
10115 Tallinn, Estonia
2.2 Contact Point for Data Protection Matters
You may exercise your rights or contact us about any data protection matter at:
- Email: contact@art50compliance.eu
- Postal address: as set out in section 2.1 above.
We have not appointed a Data Protection Officer, as we do not meet the criteria in Article 37(1) GDPR. Enquiries sent to the address above reach the people responsible directly.
2.3 Our Two Distinct Roles
It matters which role we are acting in, because your rights differ:
- As controller. For your own account data, billing data, website analytics, support correspondence and newsletter subscription, we decide why and how the data is processed. This Policy governs that processing.
- As processor. For the content and personal data that a customer enters into their ledger or inventory, the customer is the controller and we process it on their documented instructions. See section 11.
3. Categories of Personal Data Processed
We collect and process personal data in accordance with the principle of data minimisation (Art. 5(1)(c) GDPR).
3.1 Personal Data Categories
a) Server access and technical data. When you visit our website, your browser transmits technical metadata to our servers, including your IP address, browser type and version, operating system, date and time of request, referring URL, and HTTP status code.
b) Account and authentication data. To create an account we process your email address and name. We do not store or have access to your password. Authentication, credential storage and password hashing are handled by our identity provider, Zitadel, on infrastructure located within the EEA. We hold the session tokens needed to keep you signed in and an internal account identifier.
c) Billing and transaction data. If you subscribe to a paid plan, we process your billing email, plan, subscription status, billing period, and the identifiers issued by our payment processor. We do not receive, process or store your card number, CVC or full payment credentials. Those are collected directly by Stripe, which acts as an independent controller for payment processing and as our processor for subscription management.
d) Newsletter and marketing data. If you subscribe to our newsletter, we process your email address, subscription status, and engagement metadata such as opens and clicks, through our email service provider.
e) Contact and support data. When you write to us, we process your name, email address, and the content of your message.
f) Customer-submitted ledger and inventory data. When a customer records a review or an inventory item, the application processes the fields they enter. This may include:
- People and organisation: reviewer name, reviewer role or job title, company or individual entity name, and the named person responsible for an inventory item.
- Asset metadata: asset title, content type (text, image, audio, video or mixed), whether the content was AI-generated, human-made or mixed, the AI system used, and any link to the published work.
- Content artefacts: text submitted for the record, uploaded file attachments, and a flag indicating whether the content refers to identifiable living persons.
- Review metadata: how closely the work was checked, the attestation the reviewer signed, and any notes on what was changed.
- Integrity data: the timestamp the reviewer declared, the timestamp recorded on arrival, and the cryptographic hash sealing the record.
For this category we act as a processor on the customer’s behalf. See section 11.
3.2 Changes to the Data We Collect
As the Services develop, future updates may require processing additional categories of data. In accordance with Articles 13 and 14 GDPR, we will not collect new categories of personal data without prior notice. Any expansion will be accompanied by an updated Policy and, where required, direct notification or an explicit opt-in before such processing begins.
3.3 Explicit Exclusions
We confirm that the Services do not collect or process:
- Automated background browser or desktop activity;
- Cursor movement, mouse tracking, or keystroke dynamics;
- Background document reading or automated character-diff scanning;
- Card numbers or full payment credentials; or
- Special categories of personal data under Article 9 GDPR, unless a customer chooses to place such data into their own ledger, in which case they do so as controller and on their own lawful basis.
3.4 Obligation to Provide Data
Providing your personal data is neither a statutory nor a regulatory requirement. However, providing a name and email address is a contractual requirement to create an account, and billing data is required to take out a paid plan. Without them we cannot provide the Services.
4. Purposes & Legal Bases for Processing
Under Article 6 GDPR every processing operation must rest on a defined legal ground. The table below sets out why we process personal data and the basis for each activity.
| Processing activity & purpose | Data used | Legal basis |
|---|---|---|
| 1. Operating and securing the website and application Server functionality, preventing abuse, detecting security incidents, maintaining uptime. |
Server access and technical data | Legitimate interests (Art. 6(1)(f)) Guaranteeing the security, integrity and stability of our systems. |
| 2. Account creation and service delivery Creating and authenticating accounts, delivering the ledger, inventory, API and export functions. |
Account and authentication data | Performance of a contract (Art. 6(1)(b)) Necessary to provide the Services you have signed up for. |
| 3. Billing, subscriptions and accounting Taking payment, managing plan status and renewals, issuing invoices, and meeting bookkeeping duties. |
Billing and transaction data | Performance of a contract (Art. 6(1)(b)) for payment and plan management. Legal obligation (Art. 6(1)(c)) for retaining accounting records under Estonian law. |
| 4. Newsletter and marketing communications Sending our weekly newsletter and occasional product news. |
Newsletter and marketing data | Consent (Art. 6(1)(a)) You may withdraw consent at any time using the unsubscribe link in every message. |
| 5. Responding to enquiries and providing support | Contact and support data | Legitimate interests (Art. 6(1)(f)) or pre-contractual steps (Art. 6(1)(b)) Answering the person who contacted us. |
| 6. Publishing integrity proofs to a public transparency log Publishing the cryptographic fingerprint of sealed records to an independent public log, so their date can be confirmed without relying on us. See section 6. |
Record hashes only. No content, names or identifiers. | Performance of a contract (Art. 6(1)(b)) Independent verifiability is the core function the customer is contracting for. |
| 7. Serving public verification pages Displaying a record to anyone holding the link, where the customer has chosen to share it. See section 7. |
Only the fields the customer selects for publication | Performance of a contract (Art. 6(1)(b)) with the customer, who determines what is shown. |
| 8. File attachment security Validating uploaded files to prevent malicious content. |
Uploaded file attachments and metadata | Legitimate interests (Art. 6(1)(f)) and Art. 32 GDPR Protecting the platform and its users. |
| 9. Compliance with statutory obligations Lawful disclosure orders, court summonses, statutory record-keeping. |
All relevant categories | Legal obligation (Art. 6(1)(c)) |
| 10. Aggregated product analytics and research Analysing anonymised usage to improve the Services and publish aggregated benchmarks. |
Anonymised and aggregated data, stripped of identifiers | Legitimate interests (Art. 6(1)(f)) Improving the product and advancing research on human oversight. |
5. Cookies & Local Storage
5.1 Technical Necessity
We use strictly necessary first-party cookies and local storage tokens solely for essential functions:
- Session authentication: secure tokens that keep you signed in;
- Security and anti-forgery: tokens preventing cross-site request forgery; and
- Interface state: session variables maintaining form state during data entry.
5.2 No Third-Party Tracking
- We do not use marketing, targeting, or profiling cookies.
- We do not integrate cross-site tracking scripts, advertising pixels, or session replay tools.
- We do not share browsing behaviour with advertising networks.
5.3 Exemption from Consent Banners
Under Article 5(3) of the ePrivacy Directive, storage strictly necessary to provide a service the user has requested is exempt from prior consent. Because we use strictly necessary storage only, no consent banner is shown.
5.4 Browser Controls
You can configure your browser to block or delete cookies at any time. Disabling essential session cookies will prevent you from signing in.
6. The Public Transparency Log (Important)
Please read this section. It describes the one part of our processing that cannot be undone, and it is deliberate.
6.1 What Is Published, and Why
The purpose of Art50 is to produce records whose date and integrity can be confirmed without anyone having to trust us. To achieve that, the cryptographic fingerprint (a SHA-256 hash) of sealed records is periodically published to Sigstore’s Rekor, an append-only public transparency log operated by the Linux Foundation.
6.2 What Is Not Published
Only the hash is published. We do not publish to the log any content, reviewer names, email addresses, company names, file attachments, or any other identifier. A hash cannot be reversed to recover the data it was derived from.
6.3 This Step Is Irreversible
Rekor is append-only and is operated independently of us. Neither you nor we can delete, alter, or withdraw an entry once it has been published. That permanence is what fixes a record’s date independently of Art50, and it is the function the Services exist to perform.
If you exercise your right to erasure, we will delete the underlying records, content and identifiers from our systems as described in section 9. The published hash will remain in the public log, because it is beyond our control. We consider that a hash published without any accompanying identifier does not, on its own, identify a data subject, but we disclose it here so that you can take it into account before creating records.
6.4 Location of the Log
Rekor is operated by the Linux Foundation and may be hosted outside the European Economic Area. See section 8.
7. Public Verification Pages
A customer may choose to publish an individual record as a public verification page at verify.art50compliance.eu. Anyone holding the link can open it without an account.
- The customer decides, record by record, whether to publish and which fields appear.
- Some fields are always shown when a record is shared: the asset title, both timestamps, the fingerprint, and the public log entry.
- Other fields are optional and off by default, including the reviewer’s full name and the reviewed content itself.
- The customer acts as controller for that publication and is responsible for having a lawful basis to publish any personal data it contains, including the reviewer’s.
- A share link can be revoked by the customer at any time, which removes the page. Copies already taken by third parties, and any search engine caching that occurred while it was live, are outside our control.
8. Recipients, Sub-processors & International Transfers
We do not sell, lease, rent, or trade personal data. We share it only with service providers acting on our behalf, or where required by law.
8.1 Processing Under Article 28 Agreements
Third-party providers processing personal data on our behalf are bound by written data processing agreements requiring them to process only on our documented instructions, maintain confidentiality and security, and refrain from using the data for their own purposes.
8.2 Our Sub-processors
| Provider | Purpose | Location |
|---|---|---|
| Scaleway | Cloud hosting for application servers, databases and backups | France (EEA) |
| Zitadel | Identity and access management, authentication, credential storage, account-related transactional email | EEA |
| Stripe | Payment processing and subscription management | EU and United States, under Standard Contractual Clauses |
| MailerLite | Newsletter and marketing email delivery | EEA |
| Sigstore / Rekor (Linux Foundation) | Public transparency log receiving record hashes only. See section 6. | Outside the EEA. Hashes only, no identifiers. |
| Website hosting provider | Serving art50compliance.eu and our published content | EEA |
We keep this list current. If we add or replace a sub-processor that handles personal data, we will update this Policy.
8.3 International Transfers
Our core infrastructure, databases and customer records are located within the European Economic Area. Where a provider routes or handles data outside the EEA, we rely on:
- Adequacy decisions (Art. 45 GDPR) where the European Commission has recognised an adequate level of protection; or
- Standard Contractual Clauses (Art. 46(2)(c) GDPR) under Commission Implementing Decision (EU) 2021/914, supported by technical measures including transport encryption.
Publication of hashes to Rekor involves a transfer of hash values only, with no accompanying personal identifiers. You may request documentation of the safeguards applied by writing to contact@art50compliance.eu.
8.4 Disclosures to Authorities
We may disclose personal data to law enforcement, regulators or judicial bodies only where strictly necessary to comply with a binding order or statutory obligation under EU or Member State law, to defend our legal rights, or to investigate unlawful activity on the platform.
9. Data Retention & Erasure
In accordance with Article 5(1)(e) GDPR we store personal data only for as long as necessary, or as required by statute.
9.1 Retention Schedule
| Category | Retention period | Trigger |
|---|---|---|
| Server access and technical logs | Up to 7 days | Purged or anonymised on a rolling cycle, unless needed for an ongoing security investigation. |
| Account and profile data | For the life of the account | Deleted within 30 days of account closure. |
| Customer ledger and inventory records | For the life of the account, or as instructed by the customer | Deleted on account closure or on the customer’s instruction. Subject to section 6.3 regarding published hashes. |
| Billing and accounting records | 7 years | Required by the Estonian Accounting Act. These records are retained after account closure and cannot be deleted on request. |
| Newsletter subscription data | Until you unsubscribe | Removed on unsubscribe, with a suppression record kept so we do not contact you again. |
| Support correspondence | 24 months | Deleted on expiry or on a valid erasure request. |
9.2 Deletion Protocol
On expiry of a retention period, or on a valid erasure request, we permanently delete the relevant personal data, records, uploaded files and identifiers from our production systems and from backups within our normal backup cycle.
Two things survive deletion, and we set them out plainly:
- Hashes already published to the public transparency log. These are outside our control and cannot be withdrawn. No identifiers accompany them. See section 6.3.
- Billing and accounting records retained for the statutory period under Estonian law.
10. Data Subject Rights
Under Articles 12 to 22 GDPR you have the following rights in respect of personal data for which we are the controller.
10.1 Your Rights
- Access (Art. 15): confirmation of whether we process your data and a copy of it.
- Rectification (Art. 16): correction of inaccurate data or completion of incomplete data.
- Erasure (Art. 17): deletion where the data is no longer necessary, consent is withdrawn, or processing is unlawful. Limited by statutory retention and by section 6.3.
- Restriction (Art. 18): temporary restriction of processing, for example while accuracy is contested.
- Portability (Art. 20): your data in a structured, commonly used, machine-readable format. The application also provides a self-service export at any time.
- Objection (Art. 21): objection to processing based on legitimate interests. We will stop unless we demonstrate compelling grounds that override your interests, or the processing is needed for legal claims.
- Withdraw consent (Art. 7(3)): at any time, where processing rests on consent. Withdrawal does not affect processing carried out beforehand.
10.2 Exercising Your Rights
Write to contact@art50compliance.eu.
- No fee: exercising your rights is free of charge.
- Response time: without undue delay and within one month of receipt. In complex cases this may be extended by two further months, and we will tell you within the first month.
- Identity verification: we may ask for reasonable proof of identity before acting.
10.3 Right to Lodge a Complaint (Art. 77 GDPR)
You may lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, place of work, or the place of the alleged infringement.
As we are established in Estonia, our lead supervisory authority is:
Andmekaitse Inspektsioon (Estonian Data Protection Inspectorate)
Tatari 39, 10134 Tallinn, Estonia
This does not affect your right to complain to the authority in your own Member State.
11. When We Act as a Processor
For content and personal data that a customer enters into their ledger or inventory, including reviewer names, roles and any personal data contained in reviewed content:
- The customer is the controller and is responsible for establishing a lawful basis, informing the individuals concerned, and handling their rights requests.
- We act as processor, processing that data only to provide the Services and on the customer’s documented instructions.
- A data processing agreement meeting Article 28(3) GDPR is available to all customers and forms part of our Terms of Service.
- If you are an individual whose personal data appears in a customer’s records and you wish to exercise your rights, contact that customer. If you are unsure who they are, write to us and we will pass the request on.
12. Security
Pursuant to Article 32 GDPR we implement technical and organisational measures appropriate to the risk.
12.1 Technical Safeguards
- Encryption in transit: all traffic enforced over HTTPS using TLS.
- Encryption at rest: production databases and backups encrypted using industry-standard algorithms.
- Authentication: handled by Zitadel. We never see or store passwords.
- Integrity: records are sealed with SHA-256 hashes and chained, so alteration after the fact is detectable.
- Separation of privilege: the application’s database role cannot alter plan, billing or entitlement fields. Those are writable only by a separate administrative role.
12.2 Organisational Safeguards
- EU infrastructure: application servers, databases and backups are hosted in data centres within the EEA.
- Access control: administrative access to production is restricted on a least-privilege basis and protected by multi-factor authentication.
- Vulnerability management: server software and dependencies are routinely updated and patched.
13. Automated Decision-Making & Profiling
Under Article 22 GDPR you have the right not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects.
We confirm that the Services do not make automated decisions about you, do not profile or score individual reviewers, and do not evaluate, grade or pass judgment on the people named in records. The Services record and timestamp declarations made by people; they do not assess them.
Where a customer uses our API to log decisions made by their own AI systems, those decisions are made by the customer, not by us, and the customer is responsible for compliance with Article 22 in respect of them.
14. Changes to This Policy
14.1 Material Changes
If we make material changes to how we collect or process personal data, we will notify registered users by email or by a prominent notice on our website before the changes take effect.
14.2 Minor Changes
Non-material changes such as formatting, clarification of wording, or corrections take effect on publication.
14.3 Versioning
The effective date and version number at the top of this Policy indicate when it was last revised.
