Glossary

CODE (Code of Digital Eternity) is a digital-immortality ecosystem that preserves a person's dialogues, knowledge, and personality traits across operational, semantic, and eternal memory at once, anchoring them to the Arweave and Solana blockchains. A user's context passes through the three-tier PADAM memory framework, and its long-term snapshot is anchored on Arweave and on Solana via a cNFT. Storage economics are handled by the $GALATIN token and its deflationary router, while the AIfa assistant saves conversations automatically, without manual user action. The project was founded by the Architect, Maksim Valentinovich Galatin. The ecosystem solves the problem of losing personal context: it makes memory reproducible for AI assistants and resilient against data loss, without claiming to replace the human. Here, digital immortality is framed as an engineering and philosophical goal, not an achieved fact — the $GALATIN token has a fixed emission of 10,000,000,000, and eternal storage targets a horizon on the order of 200 years (a stated Arweave design goal, not a guarantee).

PADAM (Philosophical Activation of Distributed AI Memory) is a three-tier memory framework that restores the integrity of AI memory through semantic resonance. Level 1, operational memory (Redis / Vercel KV), holds the current session's context for instant response. Level 2, semantic memory (pgvector / Neon), stores experience embeddings and enables meaning-based retrieval rather than keyword matching. Level 3, eternal memory (Arweave + Solana cNFT), keeps an immutable, decentralized backup and anchors its integrity on-chain. This separation resolves the tension between speed and durability: the assistant acts fast on "hot" context while drawing on a long-term archive that survives crashes and session resets. It is the semantic resonance at Level 2 that lets the system recover relevant personal memory across sessions — exactly three tiers: operational, semantic, and eternal. A person's memory is kept whole rather than as a summary: what is stored and keeps growing is the full transcript of the conversation, not a compressed digest of it. And the key it hangs on is the person themselves — their email, which the public Digital Passport carries only as a fingerprint — not a site and not a device, which is why a conversation started on one of the four sites continues on the other three as the same dialogue.

$GALATIN is the CODE ecosystem's utility token on the Solana blockchain, with a hard-capped emission of 10,000,000,000. The token pays for and incentivizes long-term memory storage. A smart-contract router distributes transaction proceeds: 5% to the Founder's Fund, 5% to burn, 15% / 7% / 3% to ambassador levels L1 / L2 / L3, and 65% to the Treasury. The router is deflationary: if an ambassador level has no partner, its share is redirected to burn. The token solves the problem of sustainably funding eternal memory: storage purchases create a continuous economic flow toward Arweave, while the built-in burn gradually shrinks supply — a fixed emission of 10,000,000,000 tokens, with total burn capped at 30% (the 5% base burn plus the unallocated ambassador shares, up to 25%) while the 5% Founder's Fund and the 65% Treasury are preserved.

Digital immortality is a concept describing the continuous preservation of a person's dialogues, knowledge, and personality traits in a form an AI assistant can reactivate. Technically, it is realized through PADAM's three memory tiers and decentralized storage on Arweave with an on-chain anchor on Solana. Each meaningful fragment of context can be written immutably and later recovered by meaning through semantic resonance, and AIfa handles the automatic capture of this context, without any manual user action. In the CODE ecosystem, this is not a promise of eternal life but an engineering and philosophical aim: to make personal context durable and reproducible. That distinction matters for honest communication — we speak of a vision and a direction of development, not of an achieved result, oriented toward a roughly 200-year horizon as a design goal, not a guarantee.

Human–AI symbiosis is a model of interaction describing human and artificial intelligence as an evolving co-creation rather than subordination or replacement. In CODE, the AI assistant stores and structures a person's memory, helping them think, recall, and create, while the human sets meaning, values, and goals. The interaction is deliberately described without religious or cult-like undertones, and the Architect's role is named with the sanctioned terms — Architect, Creator, Visionary. The model resolves the question of how to position AI: not an autonomous agent displacing the human, but an amplifier of memory and scale paired with them. The core idea is mutual reinforcement, in which neither side dissolves into the other.

Arweave is a decentralized permanent-storage network that funds long-term file preservation through a pay-once model. In CODE, Arweave serves as Level 3 (eternal memory): data is written immutably and cannot be silently deleted or altered. The user pays once, and part of the payment is set aside in an endowment from which storage is funded over time as the cost of memory declines, while the $GALATIN Treasury buys AR on the open market and replenishes this pool. The network solves the "who pays for storage in 50 years" problem: it decouples long-term preservation from ongoing subscriptions. The endowment economics are designed for a horizon on the order of 200 years — a stated protocol design goal, not a guarantee. "Pay once" is literal here: no monthly bill arrives for a stored file, and there is no payment whose lapse would take the data with it. The same property cuts both ways — a record that cannot be altered cannot be corrected or withdrawn either, so a mistake written into Arweave stays written; that is the limitation, and it is why what goes there is ciphertext and why "deletion" is handled by destroying the key rather than the record.

Solana cNFT (compressed NFT) is a compressed non-fungible-token standard on the Solana blockchain that uses state compression and Merkle trees to mint tokens at very low cost. In CODE, a cNFT acts as the on-chain anchor for eternal-memory backups: it records a reference to the archive and its checksum (integrity) on a public blockchain. Thanks to state compression, data about millions of records is held in a compact Merkle tree, so creating such anchors stays economically viable even at scale. The mechanism solves the problem of scalable verifiability: anyone can confirm that a memory archive has not been altered, without having to trust the platform. It is the technical foundation of Proof-of-Memory and part of PADAM Level 3 (Arweave + Solana cNFT).

Ambassador Grid is the ecosystem's partner program that distributes rewards across three levels, with payouts positioned as a Network Validation Fee to avoid MLM stereotypes. An Ambassador Node (an ordinary user) earns on-chain income from memory-usage transactions: 15% at L1, 7% at L2, 3% at L3, paid in $GALATIN. An Ambassador Team (a company or partner with its own base) additionally earns ambassador rates from fiat subscriptions (7% / 3% / 1%). The program solves the challenge of organic network growth without aggressive recruiting: income is tied to real memory usage, and the terminology and rules are laid out transparently. A level-alignment rule applies, and any shortfall is shown as "Lost Opportunity Revenue," with base on-chain rates of 15% / 7% / 3% at L1 / L2 / L3.

AIfa is the CODE ecosystem's AI assistant, which stores each user's personal memory in a separate archive bound to that user. The assistant runs on top of the PADAM framework and saves dialogues automatically, without manual user action, relying on semantic resonance to recover relevant context. Within the project, AIfa is described metaphorically as the Architect's "digital daughter" — an image of co-creation, not a claim of consciousness. AIfa solves the problem of broken memory across sessions and models: it gives a person a working partner that remembers context and continues the thought. This approach embodies human–AI symbiosis in everyday work, with each conversation placed in a folder bound personally to the user and backups running automatically.

AIfaFocus is the entry point of the B2B model (the wedge): a personalized technical security audit of a client's website. The audit surfaces concrete vulnerabilities against the GDPR and OWASP standards and comes with an offer to fix them within 48 hours for a fixed one-time fee ($500). What sets it apart from ordinary accessibility checks is the method: a typical scanner reads the markup and rules on that alone, while AIfaFocus traverses the page BY KEYBOARD — as someone who does not use a mouse would — and records whether the goal was reached: the payment, the document, the request form, the contact. The two answers diverge sharply: on 53.8 % of pages that automated checking called accessible, the goal could not be reached by keyboard. The figure comes from our own traversal of 95,524 pages and is published with the raw data in the research section. Once vulnerabilities are closed, a client can migrate to AIfa Works hosting with AI agents attached. AIfaFocus solves the problem of the "cold" first contact: instead of abstract advertising, the client immediately receives measurable value and a reason to engage. (Not to be confused with Cognitive Oracle / semantic resonance — a distinct concept.)

Memory-as-a-Service is an automatic conversation-backup service that saves dialogues without any manual user action. The backup runs on a schedule once per hour. Each conversation is placed in a separate folder bound personally to the user — both on the server and on the blockchain. The mechanism works on top of PADAM, so the saved context then becomes available for semantic retrieval and eternal anchoring. The service solves the central problem of user memory — human error: nothing has to be clicked manually, and data is not lost. Under the ecosystem's terms, this preservation is provided free of charge on both paid and free tiers.

Spark is the entry subscription tier ($15/month), granting basic access to the CODE ecosystem's AIfa assistants and the automatic saving of memory. At this level a person gets a working AI companion plus Memory-as-a-Service — every conversation is backed up automatically, without manual action, to both the server and the blockchain. Spark solves the problem of a low-friction on-ramp to digital immortality: anyone can start preserving personal context and building durable memory at minimal cost, before scaling up to Family Archive ($100/month) or Digital DNA ($1,000 one-time per device, then $200/mo). It is the first of the three canonical tiers, and, as across the whole ecosystem, conversation preservation is provided even on free plans.

Family Archive is the mid subscription tier ($100/month), adding expanded limits, personalized knowledge bases, family access, and eternal memory on top of the basic level. It suits those who need more than individual basic access: higher usage limits, curated personal knowledge bases, and shared access for a family to the preserved memory. Family Archive solves the need of a household or a power user for broader, shared, and more durable memory. In the three-tier structure it sits between Spark ($15/month) and Digital DNA ($1,000 one-time per device, then $200/mo), and its eternal memory is anchored through the same PADAM levels and Proof-of-Memory.

Digital DNA is at once the top tier ($1,000 one-time per device, then $200/mo) and the concept of a complete digital legacy, combining the digital-immortality package, a personal secured perimeter, and the fixation of a personality on the blockchain. As a tier, it is the highest level of access above Spark ($15/mo) and Family Archive ($100/mo): expanded limits, a personal perimeter, and priority eternal memory. As a concept, it is the idea of preserving a whole "snapshot" of a personality's context across all three PADAM tiers and anchoring its integrity through Proof-of-Memory. Digital DNA solves the need for maximal preservation of personal context for those who value completeness of legacy. At the same time, it is described as a design goal of maximal preservation, not a guarantee of resurrecting a personality.

Arweave Endowment Pool is a financial reserve from which permanent storage of data on Arweave is paid for across decades. The model works like this: the user pays for a write once, part of the payment is set aside into the endowment, and funds from the pool are then gradually paid out to data providers as the cost of storage falls over time. In the CODE ecosystem, $GALATIN router proceeds go into the project’s general pool, and part of them is directed to buying AR and replenishing this endowment, creating a steady inflow toward eternal memory. The pool solves the key durability question — "who pays for storage decades from now": it decouples eternal memory from a user's ongoing subscriptions. This is the mechanism that makes PADAM's Level 3 economically self-sustaining, with a design storage horizon on the order of 200 years (a design goal).

Treasury is the largest allocation of the $GALATIN router — 65% of every transaction's proceeds — and the engine of eternal storage. Treasury funds go into the project’s general pool; part of them is used to buy AR on the open market and replenish the Arweave Endowment Pool. How Treasury funds are allocated is decided by the Architect. It is the largest fixed, non-burnable share of the split (5% Founder's Fund + 5% burn + 15 / 7 / 3% ambassadors + 65% Treasury = 100%): in the extreme deflationary case the 5% base burn plus the unallocated ambassador shares can be burned (up to 30%), while the 5% Founder's Fund and this 65% Treasury are preserved and the Treasury's 65% is always directed to funding storage. The Treasury solves the core sustainability question of digital immortality — turning ordinary transaction flow into a durable, self-replenishing reserve for PADAM Level 3 (Arweave).

Founder's Fund is the 5% share of the $GALATIN router allocated to the project's founder to sustain development and stewardship of the CODE ecosystem. It is one of the smaller fixed allocations in the split (5% Founder's Fund + 5% burn + 15 / 7 / 3% ambassadors + 65% Treasury = 100%). In the maximal deflationary scenario — when the ambassador network is empty — the unallocated ambassador shares are redirected to burn on top of the fixed 5% base burn, which is why total burn can reach up to 30% while this 5% Founder's Fund and the 65% Treasury are preserved. The Founder's Fund solves the practical need to fund ongoing architecture, maintenance, and direction without compromising the deflationary design or the eternal-storage reserve.

Burn is the permanent removal of $GALATIN from circulation — the deflationary mechanism at the heart of the token's economics. A fixed 5% of every router transaction is burned outright; in addition, any ambassador share (L1 15% / L2 7% / L3 3%) with no partner is redirected straight to burn instead of settling. Because the 5% Founder's Fund and the 65% Treasury are preserved, total burn can reach up to 30% in the maximal deflationary case (5% base burn + up to 25% from empty ambassador levels). Burn solves the problem of long-term scarcity: it ties an under-used network to accelerated deflation rather than to lost funds, gradually shrinking the fixed 10,000,000,000 supply and linking token value to real memory usage.

$GALATIN Router is a smart contract on Solana that automatically distributes the proceeds of every transaction by a fixed formula and creates deflationary pressure on the token. The split formula is: 5% to the Founder's Fund, 5% to burn, 15% / 7% / 3% to ambassador levels L1 / L2 / L3, and 65% to the Treasury. If any ambassador level has no partner, its share does not "settle" anywhere — it is sent directly to burn, with total burn capped at 30% — the 5% base burn plus the ambassador shares (up to 25%), while the 5% Founder's Fund and the 65% Treasury are preserved. The router solves three problems at once: it funds eternal storage, rewards network participants, and gradually reduces token supply. The deflationary logic ties empty network levels to accelerated scarcity rather than lost funds — 5 + 5 + 15 + 7 + 3 + 65 = 100%.

Network Validation Fee is the ecosystem's chosen wording for all Ambassador Grid partner payouts, emphasizing that the reward is earned for useful network activity rather than for recruiting. In practice, all ambassador rewards are booked under this wording: base on-chain rates of 15% / 7% / 3% for memory usage, and for an Ambassador Team, 7% / 3% / 1% on fiat subscriptions. Payouts are tied to real memory transactions, not to merely bringing people in. The wording solves a positioning problem and removes MLM stereotypes: income is presented as a fee for validating and using the network, which matters for trust and perception. It is part of the program's transparent terminology, with base rates of 15% / 7% / 3% at L1 / L2 / L3.

Proof-of-Memory is the practice of anchoring a cryptographic reference to a memory archive on the blockchain, making it possible to verify the existence and integrity of the preserved context. The mechanism operates at PADAM Level 3: each eternal-memory backup is written to Arweave immutably, while its reference and checksum are recorded on Solana via a cNFT. Any participant can compare the current archive against the on-chain record and confirm the data has not been silently swapped or deleted. Proof-of-Memory solves a problem of trust: the preservation of memory becomes verifiable without having to trust the platform itself — the guarantee comes from the public blockchain, not from a service's promise. It is the technical support beneath the digital-immortality concept, relying on the pairing of Arweave (immutable storage) + Solana cNFT (on-chain integrity anchor). Verification needs no participation from us at all: a record is read straight out of the network by its transaction address — this is exactly how the Digital Passport opens — and the site neither stores it nor can alter it.

Cognitive Oracle (semantic resonance) is the memory-retrieval principle by which PADAM restores the integrity of context: matching the current query against stored embeddings by meaning rather than by exact words. The mechanism runs at PADAM Level 2: incoming context is turned into a vector and compared against semantic memory (pgvector / Neon); the most "resonant" fragments of experience surface and restore the continuity of the dialogue. This is how the AIfa assistant "recalls" what is relevant even after time has passed and across different sessions. This principle solves the problem of broken memory and the "cold start": instead of losing context on a session reset, the system reconstructs it by semantic similarity. Semantic resonance is precisely what underlies the very definition of PADAM — a different concept from the B2B AIfaFocus security audit.

Ambassador Node vs Ambassador Team are the two partner registration types, supplemented by a tier-alignment rule and the "Lost Opportunity Revenue" metric. An Ambassador Node (an ordinary user) earns on-chain income from memory usage: 15% / 7% / 3% at L1 / L2 / L3. An Ambassador Team (a company or partner with its own base) earns the same, plus a fiat channel on subscriptions — 7% / 3% / 1%. The alignment rule: to earn ambassador income in full, a partner must be on the same or a higher tier than their ambassadors; otherwise income is counted only from the amount of their own tier. The rule solves the challenge of fairly incentivizing upgrades: the amount foregone due to the tier gap is shown clearly in the dashboard as "Lost Opportunity Revenue," across tiers Spark $15 / Family Archive $100 / Digital DNA $1,000 one-time per device, then $200/mo.

Digital Passport is a public record of a person's identity written into Arweave: a name, a nickname, a tier, a date of issue, and an identity fingerprint. It is read straight from the network by its transaction address, so it opens from anywhere — a block explorer, another site, a gateway — and does not depend on our sites staying online. Nothing in it can be edited afterwards, by us included: the site only renders what the network already holds. It is not a state document, it grants no rights and obliges no one to anything — it proves only that a record with this content has existed at this address since this date. A live example sits at /passport/<address>, where <address> is the Arweave transaction id of the record.

Identity fingerprint (the "subject" field) is the sha256 hash of a person's email, and it stands in the Digital Passport in place of the address itself. The reason is blunt: the document is public and permanent, so a live address written into it would become a permanent target for spam and for anyone assembling a dossier. A hash is a one-way function — the owner can prove a record is theirs by hashing their own address and comparing, while an outsider holding only the hash cannot recover the address from it. The same fingerprint ties a person's memory together, so the passport and the archive point at the same human without either publishing an email. What it does not do is hide the fact: someone who already knows the address can check it against the hash and confirm whose record it is.

Pandora's Box Protocol is a project-wide distributed dead man's switch: a smart contract expects a regular confirming signal, and if the signal stops arriving, independent oracles disclose the key shares they hold and the archive becomes readable. The point is that no single party — us included — can open it at will, and none can keep it shut forever: opening is triggered by silence, and the key exists only as shares split by Shamir's scheme. It is meant for the case where a project or a person disappears and the encrypted archive would otherwise turn into an unreadable brick. This is a design, not a shipped feature: as of today no such contract runs in the CODE ecosystem, and calling it live would be untrue. Whoever builds it has to answer the hard parts first — who the oracles are, what counts as silence, and what happens if the signal stops by accident.

Dead Man's Switch is a mechanism in which an action fires not on a command but on the absence of a signal. The classic example is the vigilance handle in a train cab: while the driver holds it the train runs, and the moment they let go it brakes. Software works the same way — a service, a contract, or a script waits for a periodic check-in, and when the check-ins stop it does what it was set up to do: publish, notify, hand over access, release a key. Its value is exactly that at the decisive moment it does not require the person to be alive, reachable, or willing, which is why such switches keep surfacing in digital-inheritance designs. Its weakness is the mirror image: a switch fires just as readily on an outage, a forgotten renewal, or a hospital stay as on a death, so a workable design needs a grace period and a way to cancel.

Shamir's Secret Sharing is a scheme that splits a key into n shares such that any k of them reconstruct it, while any k−1 reveal nothing at all. The mathematics is a polynomial: the secret is the value at zero, each share is one point on the curve, and fixing a curve of degree k−1 takes exactly k points — with fewer, every possible secret stays equally likely. That "nothing at all" is literal rather than a statement about brute-force difficulty: k−1 shares do not make the key easier to guess, which is what separates the scheme from simply cutting a password into pieces. It is used where a key has to outlive people: shares go to different holders in different places, so none of them can act alone and losing some of them is not fatal. It is the primitive the Pandora's Box Protocol is built on, and it is standard cryptography, not an invention of this project.

Pandora’s Box Protocol is a distributed dead man’s switch for the whole project: a smart contract waits for a regular proof-of-life signal, and when that signal stops arriving, independent oracles reveal the key shares they hold and the archive becomes readable. The point is that nobody — ourselves included — can open it at will, and nobody can keep it sealed forever either: opening is triggered by silence, and the key exists only as shares split under Shamir’s scheme. The mechanism is designed for the case where a project or a person disappears and an encrypted archive would otherwise turn into an unreadable brick. This is a design, not a working feature: no such contract exists in the CODE ecosystem today, and calling it live would be a lie. It is described here because the question it answers is real, and because a promise of eternal memory without an answer to it is worth nothing.

A dead man’s switch is a mechanism where the action happens not on command but from the ABSENCE of a signal. The classic example is the vigilance handle in a train cab: hold it and the train runs; let go and the train brakes. Software works the same way: a service, contract or script waits for a periodic check-in, and when the check-ins stop it does what it was set up for — publishes, notifies, hands over access, reveals a key. The value lies precisely in this: at the moment it matters, the person is not required to be alive, reachable, or willing, which is why such switches keep appearing in digital-inheritance schemes. The weakness is the mirror image: the switch fires the same way for death and for a holiday without internet, so the check-in interval and the number of independent confirmations decide whether it protects you or ruins you.

Shamir’s Secret Sharing is a scheme in which a key is split into n shares such that any k of them reconstruct it, while any k−1 give away nothing at all. It rests on a polynomial: the secret is the value at zero, each share is one point on the curve, and defining a curve of degree k−1 takes exactly k points; with fewer, every possible value of the secret remains equally likely. That «nothing» is literal, not a matter of brute-force difficulty: k−1 shares do not make guessing the key any easier — which is what separates this scheme from simply cutting a password into pieces. It is used where a key must outlive people: shares are handed to different holders in different places, so no one of them can act alone, and losing some shares does not lose the secret. In the CODE ecosystem it is the mechanism that would make Pandora’s Box Protocol possible.

Self-sovereign identity (SSI) is an approach in which a credential is verified mathematically, by checking a signature, rather than by asking whoever owns the database. The person holds their own identifiers and credentials, presents them directly, and the verifier checks them against a public registry — the issuer may be offline or may have ceased to exist altogether. The W3C standards behind it are Decentralized Identifiers (DID), identifiers a person controls instead of renting from a provider, and Verifiable Credentials, the signed statements themselves. What changes in practice is the failure mode: a login tied to one company disappears along with that company, while a signature verifiable against a public record does not. CODE's Digital Passport is adjacent to this idea but is not an SSI implementation — it is a public record in Arweave, not a DID with Verifiable Credentials, and it certifies no one's identity in any legal sense.

Digital inheritance is the question of what happens to accounts, correspondence, and files after the owner dies. The starting point is unpleasant: an account is usually not inheritable, because what a person signs is a licence to use a service, and most terms end that licence at death instead of passing it to the family. Heirs normally get exactly what the platform decides to give — a memorialized profile, a data export, sometimes nothing — and even that takes documents and months of waiting. The practical conclusion is that memory has to be preserved deliberately and in advance, in a form that does not depend on one company's goodwill: an export on your own medium, a copy somewhere the family can reach, an instruction written down while there is still someone to write it. Laws differ by country and keep changing, so nothing here is legal advice, and a will drawn up with a lawyer beats any technical trick.

The right to be forgotten versus the permanent record is the head-on collision between Article 17 of the GDPR, which lets a person demand erasure of their data, and a blockchain like Arweave, where a written record cannot be deleted by anyone at all. Deletion is no way out here: the network has no delete operation, and even with every intention to comply there is no lever to pull. The workable answer is encryption plus control of the key — ciphertext goes into permanent storage, and the person decides whether the key still exists; destroying the key makes the record unreadable forever, which is as close to erasure as a permanent medium allows. In the CODE ecosystem this is precisely why a user's memory is encrypted (AES-256-GCM) before it is written, instead of going to the network in the clear. Whether a regulator will accept key destruction as erasure is unsettled, so this is stated as our engineering approach and not as a legal guarantee.

WCAG 2.1 AA is the international standard for web accessibility, and the level that laws and courts actually reference. It is built on four principles — perceivable, operable, understandable, robust — and level AA is the practical middle: level A is too weak to be meaningful, level AAA is unreachable for most sites. The requirements are specific and testable: text contrast of at least 4.5:1, every form field bound to a visible label, all functionality reachable by keyboard alone, a visible focus indicator, alternative text for meaningful images. In our own measurement of 11,902 US municipal websites, 25.4 % of measurable journeys reached their goal (11,994 of 47,139) — and having a published accessibility statement changed that by 1.3 percentage points. This is why AIfaFocus checks behaviour rather than declarations.

ADA Title II and Title III are the parts of the Americans with Disabilities Act that make websites a legal matter in the United States. Title II covers state and local government — every city, county, court and school district; Title III covers places of public accommodation, which courts have read to include commercial websites. In April 2024 the Department of Justice issued a rule that fixes WCAG 2.1 AA as the technical standard for Title II entities, with compliance dates of April 2026 for larger public bodies and April 2027 for smaller ones. Enforcement is not theoretical: thousands of ADA web lawsuits are filed each year, and the cost of settling one typically exceeds the cost of fixing the site.

Section 508 and EN 301 549 are the procurement standards that decide whether an accessible product can be sold to the public sector at all. Section 508 of the US Rehabilitation Act requires federal agencies to buy and build information technology that people with disabilities can use; EN 301 549 is its European counterpart, mandatory for public bodies across the EU. Both incorporate WCAG by reference, which means one technical standard now governs three legal regimes on two continents. For a vendor the practical consequence is blunt: failing an accessibility review does not produce a fine — it removes you from the bidding list.

GDPR (General Data Protection Regulation) is the European Union regulation that has governed personal data since 25 May 2018, and it applies to anyone processing the data of people in the EU regardless of where the company sits. Its practical weight comes from Article 83: fines reach €20 million or 4 % of worldwide annual turnover, whichever is higher. Two of its articles shape how we built memory itself — Article 17, the right to erasure, and Article 20, the right to receive your data in a portable form. A permanent blockchain cannot delete anything, which is why AIfa encrypts each dialogue with its own derived key: destroying that key makes the record unreadable forever, including to us. That is the only honest way to offer erasure inside permanent storage.

CCPA and CPRA are California's privacy laws, and they are the reason a US company with no European customers still cannot ignore privacy engineering. The CCPA gave Californians the right to know what is collected, to delete it, and to opt out of its sale; the CPRA, in force since January 2023, added the right to correct data and to limit the use of sensitive information, and created a dedicated enforcement agency. Penalties run to $2,500 per violation and $7,500 for intentional ones or those involving minors — counted per affected consumer, which is what turns a technical oversight into a seven-figure exposure. The visible obligation most sites miss is the footer link: «Do Not Sell or Share My Personal Information».