Privacy notice

Version 2026-10-13. Plain-language summary of what this site collects, why, and the controls you hold over it.

Who runs this

This site is maintained by organizers of the Artizen claimant effort — an independent, community-run resource not affiliated with Artizen Works Inc. For privacy law purposes (GDPR and equivalents), the organizers act as the data controller for submission records. To reach the organizers about your data, reply in the community channel where you found this site, or act directly on your record — most rights below are self-service and do not require contacting anyone.

What we collect

Only what you choose to type or upload in the intake form:

Claim fields: a contact handle (pseudonymous handles are fine — a real name is not required), country, role(s), season(s), project name, amounts (sales / match / prizes / believed owed / offered / received), payment status, and optional notes.
Attachments: only the files you select. These are sealed in your browser before upload; the server stores ciphertext.
Optional wallet signature: if you sign your submission, we store a hash of your wallet address — never the signature's plaintext purpose beyond binding your consent changes.
Optional public-status opt-in: if you check it, a whitelisted subset (project, seasons, payment status, dollar amounts) is shown on the public status page. Nothing else is published.

What we do not collect: no IP address stored, no user-agent logged to your record, no cookies, no analytics, no trackers, no third-party beacons. The abuse gate is either a Cloudflare Turnstile token or a local proof-of-work (ALTCHA) — the latter identifies nothing about you.

Why we collect it

To tally what claimants are owed and show the aggregate picture.
To coordinate recovery — including producing your submission to counsel or regulators only under the consent state you choose.
To let you verify, correct, or remove your own record at any time.

We do not use submissions for advertising, profiling, or any automated decision-making. There is none.

Legal basis

For GDPR-covered claimants (and equivalents elsewhere): processing rests on your consent (Art. 6(1)(a)) and on the legitimate interest (Art. 6(1)(f)) of organizing affected claimants' claims and preserving evidence of the platform's conduct. Withdrawing consent does not undo processing already done — but because your record is sealed to you, almost nothing is processed in readable form until you say so.

Please do not submit data we didn't ask for — health information, ID documents beyond what's needed, or other people's details. If an attachment incidentally contains such material, note it in your submission or revoke and resubmit.

Who can see your record

Licensed (default): your submission stays ciphertext in storage; organizers can decrypt it for the claimant effort (ledgering, counsel review).
Sealed private: ciphertext only; no one reads it. Aggregate counts may still include it.
Released: elected representatives and counsel may decrypt for legal action.
Revoked: deleted everywhere we host it.

You move between these states yourself — see below.

Your rights and how to use them

Claimants are worldwide; rights differ by jurisdiction, but we aim to honor the strictest common set for everyone:

Right	How
Access	Manage your submission → enter your receipt → your ciphertext is returned. Decrypt it locally on Verify a proof.
Rectification	Submit a corrected record with the same details — deduplication keys on your field content — or ask organizers to annotate.
Erasure	Manage your submission → Delete my submission. This removes the sealed record, escrow key, public listing, and every uploaded file, and writes a content-free tombstone so the ledger can mark consent revoked without keeping your data.
Restriction	Manage → Keep sealed private — processing stops; the record stays unreadable.
Portability	Your receipt retrieves your full encrypted record — it is your copy, decryptable only by your key.
Objection / complaint	You may object to or complain about processing. EU/EEA residents may complain to their national supervisory authority (e.g., in Germany, your state's data-protection commissioner or the BfDI); UK residents to the ICO; others to your local authority. You can also act on your record directly — deletion does not require anyone's approval.

Your receipt is the credential. Treat it like a password. If you signed your submission with a wallet, consent changes require a fresh signature from that wallet.

Where data lives and for how long

Records are stored on Cloudflare's network (Pages Functions + KV + R2), which processes data on globally distributed infrastructure. All claimant content is stored as ciphertext — sealed in your browser before transit — so storage location does not expose contents. Records persist until you revoke them or the claimant effort concludes, after which remaining sealed records will be deleted or destroyed. Tombstones (timestamp + action only) may be retained to keep the ledger's consent audit honest.

Security

Field payloads, PII, and file bodies are sealed in-browser (libsodium sealed boxes); the server never receives plaintext or a decryption key.
TLS in transit; ciphertext at rest; no IP/UA written to your record.
Organizer decryption keys live outside this infrastructure.

Caveat we won't hide: copies already decrypted into the organizers' private archive before a revocation are excluded from future exports and deleted on request — flag it via the community channel and it will be confirmed in writing.