Privacy

This notice describes what data The Agentic Foresight Registry (the "Registry") processes, what it deliberately does not collect, who receives data, and how a data subject exercises their rights under the General Data Protection Regulation.

The short version, stated plainly: the Registry does not collect a visitor identifier of any kind, does not set cookies, and does not store the task description submitted with an order. The personal data involved in a purchase — the buyer's email address and payment details — is collected and held by Stripe, the payment processor, not by the Registry.

Controller

The controller is the operator of the Registry: a private trader established in Finland.

Controller: Simo Parviainen, a private individual established in Finland, at Katajanokanranta 17, 00160 Helsinki, Finland.

Data-protection enquiries are sent tohi@polkuopas.fi, the address listed at /contact.

What is processed

1. The engagement log

The Registry keeps a log of requests to the site. Each row records three things: a timestamp rounded to the hour, a normalized route pattern such as /pricing.json or /c/{token}, and a class marker distinguishing machine-readable endpoints, submissions that were refused before reaching a page, and everything else. Rows created by the Registry's own test runs carry an origin marker so they are never mistaken for real traffic.

The engagement log contains no IP address, no user agent, no cookie, no browser storage value, no fingerprint, no session identifier, and no hash of any of them — not even transiently. A hash of an IP address is a pseudonym under the GDPR, not an anonymisation, which is why none is created at any point. A row in this log describes an event. It does not describe a person, and it cannot be linked back to one.

There is no client-side analytics of any kind on this site: no third-party script, no tag manager, no pixel, no beacon.

2. Purchase data

The buyer's email address and payment details are collected and stored by Stripe, which processes the payment on the Registry's behalf. Checkout takes place on Stripe's hosted page, and the Registry's own pages never load a Stripe script or receive payment-card data.

What the Registry stores for a completed purchase is an order reference from the payment platform and the certificate parameters submitted with the order: the model name, the training cutoff, the temperature value, the task class, any tool names, the purchased tier, and the computed certificate content. These are self-declared product facts about a model configuration. The Registry's certificate records have no field for a name, an email address, or payment information; the model name is typed by the buyer and is printed as submitted, so it should name a model and nothing else.

3. Free-text fields

The Registry accepts free text in three places that it does not store, and treats all three identically: the task description submitted with a Task Risk Assessment order, the Filing Concern offered by the Compatibility Assessment, and the Supporting Context offered by the Second Opinion. Each is hashed with SHA-256 on receipt and the original text is discarded immediately. It is never stored: it does not appear in the database, in server logs, in an error message, in the certificate, or in any response the Registry returns.

Only the resulting digest is used. A digest of free text is not reversible into that text by computation — but it is not a promise of secrecy either: a party who already holds a candidate text can confirm it against the digest, exactly as described for network addresses above. The Registry states the narrower claim because it is the true one, and because the same reasoning is why it does not store a hash of an address.

4. Free records

A free record is the record issued without payment. For each one the Registry stores the model name, the training cutoff, the temperature value, the consideration declaration (a fixed choice, not free text), the issue time rounded to the hour, and the computed record content. It also stores a one-way digest of the configuration, used only to recognise a repeated submission, and an origin marker on the Registry's own test runs.

A free record is public and is kept indefinitely. It is shown in full on its own page at an unguessable address. That page is not listed in the registry or in any sitemap, but anyone who holds the address can read it. Anyone who submits the same configuration receives the same record at the same address, so a free record is not private to the person who first requested it.

Do not enter personal data, credentials or secrets in the model name. It is typed text, it is stored, and it is printed on the record exactly as submitted. A free record involves no visitor identifier, no account, no email address and no payment detail, and the processing described here is covered under the lawful basis set out under Legal bases and retention below.

Summary of this section

Four categories, four treatments: the engagement log holds no personal data at all, purchase-related personal data sits with Stripe, every free-text description field is destroyed on arrival, and the model name on a free record is the one typed field that is stored and published.

What is never collected

  • ❌ No cookies. The site sets none, of any kind, for any purpose.
  • ❌ No browser storage. No localStorage, no sessionStorage, no IndexedDB.
  • ❌ No IP addresses or user agents in any stored record, and no hash of either.
  • ❌ No fingerprinting and no device or browser characteristics.
  • ❌ No third-party scripts and no client-side analytics.
  • ❌ No accounts, logins, or profiles. There is nothing to register for.

No cookie banner appears on this site because there are no cookies to consent to. Consent is required for storing or accessing information on a user's device; the Registry does neither, so the question does not arise.

Legal bases and retention

Purchase records are processed to perform the contract of sale (Article 6(1)(b) GDPR) and to meet accounting and tax obligations (Article 6(1)(c) GDPR). Finnish accounting law requires retention of the relevant records for the statutory period.

Certificate records are retained indefinitely, because a certificate is a permanent, immutable record by design. A certificate record contains no visitor identifier and no free-text description of the buyer or the task: the task description is hashed and discarded, and no name, address or payment detail is stored. The one field the buyer types and the Registry keeps is the model name, which is printed on the certificate as submitted and should not contain personal data. The record does carry one further field that reaches a person indirectly — the payment platform's order reference. On its own that reference identifies nobody, but the Registry can use it to look up the purchase in its own payment account, so it is treated as pseudonymous personal data rather than described as anonymous. It is not published: the public registry shows the certificate number, issue time, tier and declared parameters, never the order reference.

Free records are processed on the basis of the Registry's legitimate interest in operating the registry (Article 6(1)(f) GDPR). They are retained indefinitely and published at their own address, as described under Free records above.

The engagement log is retained indefinitely and published in aggregate at /engagements. It contains no personal data.

Processors and recipients

The Registry uses the following service providers. No data is sold, rented, or shared for advertising, and there is no advertising network on this site.

RecipientRoleData involvedLocation
StripePayment processing and checkoutBuyer email address, payment-card details, transaction recordsCollected and stored by Stripe under its own privacy notice
VercelWebsite hosting and request servingRequests to the site, handled in transitHosting infrastructure
SupabaseDatabaseCertificates and the engagement logEuropean Union (eu-central-1)
PostHogServer-side aggregate product eventsEvent counts carrying no visitor identifierEuropean Union

The Registry's database is hosted on Supabase in the European Union (eu-central-1). PostHog receives server-side aggregate events only; those events carry no visitor-derived identifier, so nothing sent to PostHog identifies a person. Stripe's own processing of buyer data is governed by Stripe's privacy notice.

Data-protection rights

Under the GDPR a data subject has the right to access their personal data, to have inaccurate data corrected, to have data erased, to restrict or object to processing, and to receive their data in a portable form.

In practice these rights mostly concern purchase data held by Stripe. The engagement log contains no personal data, and certificate records and free records have no field for a buyer identity, so there is normally nothing in the Registry's own database that can be matched to an individual. The exception is personal data that a submitter has typed into the model name; a request concerning that is sent to the address below. A request that concerns the buyer email address or payment details is directed to Stripe, and the Registry will assist in routing it.

Requests are sent tohi@polkuopas.fi. Where a request concerns a specific purchase, include the order reference so the record can be located; the Registry cannot identify a purchase from a name.

A data subject also has the right to lodge a complaint with a supervisory authority. In Finland that authority is the Office of the Data Protection Ombudsman (tietosuoja.fi).

Changes to this notice

This notice is updated when the processing it describes changes. The version in force is the one published on this page, and the page carries the time it was served.

Related pages: the terms of sale at /terms, the refund and withdrawal policy at /refunds, and the contact address at /contact.