The Platform PM
Primitive 08

Regulatory layering

Jurisdiction × activity × entity type: is it a license or a certification?

Regulation stacks up by country, by activity and by the kind of company you are. The first job is to separate law (licenses, mandatory rules) from optional proof (certifications) and from industry rules that partners enforce through contracts.

What it is

The rules that apply to you come from the combination of where you operate, what you do and what kind of entity you are. Some are licenses: you can't legally do the activity without one. Some are certifications: proof you meet a standard, usually demanded by customers or partners. And some are industry codes, enforced through contracts and fines rather than courts.

Knowing which layer a requirement comes from tells you who enforces it and what happens if you miss it.

Where you'll see it

IndustryLawCertification or industry rule
PaymentsMoney transmitter licensesPCI DSS, enforced by the card networks
HealthcareHIPAAHITRUST certification
TelcoTelecom regulators and consent lawsCarrier codes of conduct and industry messaging guidelines
PayrollTax and labor law, by country and stateSOC 2 reports that customers ask for

Questions to ask in week one

  1. Which jurisdictions, activities and entity types apply to us?
  2. For each requirement: is it law, a certification or a partner's rule?
  3. Who enforces it, and what's the penalty for missing it?
  4. Which requirements sit with us, and which with our customers?
  5. What is actually enforced today, compared with what's written?

The trap

Assuming "regulation" means government. In many industries the rules that block you day to day are written by networks and industry bodies, and enforced through contracts and fines.

In the Field Guides

AI agents: orchestration platforms

Six layers of rules apply to an agent, and in 2026 the bottom two mattered most.

Law

EU
AI Act (risk follows use); GDPR; product liability from 2026-12-09
US
No AI statute; Texas and California since 2026-01-01; Colorado and New York from 2027-01-01
Enforced by
Authorities, attorneys general, courts

Sector rule

EU
High-risk uses (hiring, credit) from 2027-12-02
US
FINRA expectations; bank model-risk guidance excludes agentic AI
Enforced by
Supervisors

Standard

EU
EN 18286 approved, not yet cited
US
NIST AI RMF (under revision); ISO/IEC 42001
Enforced by
Certifiers, buyers

Security guidance

EU
National cyber centres
US
CISA, NSA and partners (2026-05-01); NIST's agent initiative
Enforced by
Questionnaires

Lab policy

EU
Human review in employment, credit, health, legal
US
Same
Enforced by
Account action

Customer contract

EU
AI addenda, data terms, copyright-only indemnities
US
Same, plus OMB checks for federal buyers
Enforced by
Contract

The AI Act has no article for agents. An agent is an AI system, and its risk follows its use. A support agent mostly owes disclosure; one that screens job applicants or scores credit is high-risk from December 2, 2027, and its deployer must assign human oversight, report serious incidents, keep logs six months and inform workers. Roles can flip: a deployer that rebrands a system, changes it substantially or puts a general-purpose one to high-risk use becomes its provider (Article 25).

The labs' data terms differ:

OpenAI

Default retention
Abuse logs up to 30 days; no training by default
Zero-retention catch
By approval; not for stored conversations or files
Where data is processed
US, Europe, UAE regionally

Anthropic

Default retention
None by default; flagged content up to 2 years
Zero-retention catch
Top-tier models require 30-day retention
Where data is processed
us or global only

Google (Gemini API)

Default retention
A limited period; free-tier data improves products
Zero-retention catch
On its cloud, caching must be off
Where data is processed
Only paid services for EEA, UK users

On the clouds, AWS says Bedrock doesn't store or log prompts, and Azure keeps them up to 30 days for abuse monitoring unless a customer gets an exception. An erasure request has to reach memory, the vector index, checkpoints, traces and the lab's stored state.

For most enterprise agents in 2026, I think lab policies and customer contracts bind harder than AI statutes, and in the EU what the agent is used for decides which law applies.

AI coding agents: writing, reviewing and shipping code

Agents leave the change-management rules as they were and change who counts as the author.

LayerUSEU and elsewhere
Change controlPCI DSS 6.2.3 and 6.2.3.1 for card systems (contractual, through the card brands); SOC 2 CC8.1 (an attestation)EU DORA's technical standard on ICT change management, Article 17, for financial firms
Banking supervisionOCC Bulletin 2026-13 (April 2026) on model risk excludes generative and agentic AISingapore's MAS draft AI guidelines cover autonomous agents
Product securityNo general ruleCyber Resilience Act reporting since September 11, 2026; Product Liability Directive from December 9, 2026
AI lawState laws mostly about consequential decisions, not codeAI Act: no high-risk duties for coding tools by default; general-purpose model duties sit with the labs

For a regulated platform the answer is the same in both places: the reviewer and the approver must be people other than the author, the change record has to show who did what, and the manufacturer answers for the product whoever wrote the code.

AI evals and observability: how teams measure AI quality

No law tells a PM how to build a test set. The rules arrive in layers, and which ones apply depends on what the product decides:

LayerWhat it coversApplies to a support chatbot?
General lawMisrepresentation, consumer protection, anti-discriminationYes, after the fact (Air Canada)
AI-specific lawEU AI Act; US state laws on hiring, credit and insuranceDisclosure only, unless it makes decisions about people
Sector rulesMedical devices (FDA), bank model risk, insuranceOnly in those sectors
Contracts and questionnairesVersioning, change notice, test evidenceYes, for any B2B seller

For the help-desk company the binding layers are general law and its customers' contracts. A team whose agent screens job applicants or prices insurance gets the AI-specific and sector layers too, and bias testing becomes part of the eval suite. That side is covered in AI governance and model risk.

AI governance and model risk

US bank

Sector layer
SR 26-2 (generative AI out); third-party risk guidance; fair lending
Horizontal layer
State laws; EU AI Act if it serves people in the EU
Voluntary and contractual layer
Examiners' expectations; ISO and NIST as language

EU bank

Sector layer
Financial-services governance, which the AI Act accepts for most quality and monitoring duties
Horizontal layer
AI Act; GDPR
Voluntary and contractual layer

US insurer

Sector layer
NAIC bulletin or state rules (Colorado, New York)
Horizontal layer
State privacy and anti-discrimination law
Voluntary and contractual layer
Vendor audit rights

US employer

Sector layer
Federal anti-discrimination statutes
Horizontal layer
NYC, Illinois, California, Colorado, Connecticut
Voluntary and contractual layer
Vendor contract

B2B AI vendor

Sector layer
Its customers' sector rules, flowed down by contract
Horizontal layer
EU provider duties if its system is high-risk
Voluntary and contractual layer
Questionnaires, ISO 42001, AI addenda

One hiring decision in New York by a company based in the EU can touch the AI Act, GDPR, three federal statutes, state and city human-rights law, the city's bias-audit law, FCRA and the vendor's contract.

Agent identity and delegated access: how AI agents act for people

No law is written about agent identity. The layers that apply:

LayerExamplesWhat it means for an agent product
Security guidanceNIST IR 8587, NIST's NCCoE project, CISA's joint guidance, OWASPThe yardstick after an incident; voluntary outside US federal systems
Protocol specificationsThe MCP spec's "must" rulesQuoted as what "reasonable" means
AI lawEU AI Act Article 50Tell people when they're dealing with AI; the text never mentions agents
Product liabilityThe EU Product Liability Directive; a 2025 California lawSoftware defects become product claims in the EU; in California, "the AI acted on its own" is no defence
PaymentsReg E and Reg Z, PSD2 and PSD3, the UK's 2017 payment regulationsRefund rights for unauthorized payments, written before agents
Identity walletseIDAS 2.0Nothing on agents acting for a wallet holder
Contracts and insuranceVendor terms, policy exclusions, questionnairesWhere loss actually gets allocated

For a B2B product, the contract and the customer's security questionnaire bite before any law.

B2B payments: cross-border payouts

Two countries' law, two sets of licences and at least two partners' policies sit on every payout.

Law

Sender (US, Canada)
BSA; OFAC sanctions; state money transmission; PCMLTFA; RPAA
Destination
FX law (India's FEMA, Brazil's FX law); labour and tax codes
Enforced by
Regulators, courts

Licence

Sender (US, Canada)
State licences or a bank-agent structure; FinCEN and FINTRAC registration
Destination
RBI cross-border aggregator; Brazilian FX or eFX authorization; BSP, FCA, EU licences
Enforced by
Regulators

Standard

Sender (US, Canada)
FATF R.16, once national law adopts it; ISO 20022
Destination
Same
Enforced by
Peer review, Swift

Network rule

Sender (US, Canada)
Swift rulebooks; card push programs
Destination
SPEI and Pix participation; Pay.UK access
Enforced by
Operators

Partner policy

Sender (US, Canada)
Country lists, KYB depth, reserves
Destination
Local partner terms
Enforced by
Contract
  • US money transmission follows the sender. Model laws license "receiving money for transmission from a person located in this state". The model act (in about 33 states) and Texas law include payroll processing. New exemptions (Nevada, Nebraska, Maryland from October 1, 2026) are written around wages. I'm not a lawyer, but as I read it, a contractor platform that holds funds needs licences, a bank-agent structure, or never to touch the money.
  • Holding the money is the trigger. A US startup that collects client funds on Monday and pays contractors abroad on Friday holds other people's money for those four days, and that's what brings in state licences.
  • Consumer rules miss B2B. The CFPB Remittance Rule covers transfers "primarily for personal, family, or household purposes"; the 1% remittance excise tax and FinCEN's border order cover only cash-type funding. An account-funded payout escapes all three.
  • Canada: the RPAA covers providers based in Canada or serving Canadian users from abroad: a fintech holding a company's funds is in, the company's own bank is not.
  • The EU has no passport for third countries. I'm least sure here: paying into recipients' own EU accounts through an EU partner bank seems to need no EU licence; holding balances for EU contractors does.

B2B payments: order to cash

Keep the layers apart: each has its own enforcer and its own penalty.

Payments law

US
UCC 3, 4 and 4A, Reg CC, Reg E (consumers only), Bank Secrecy Act, state money transmission and surcharge laws
Canada
PCMLTFA (anti-money laundering), Retail Payment Activities Act (RPAA)
Enforced by
Courts, FinCEN, states; FINTRAC, Bank of Canada

Credit and collections law

US
Reg B (including trade credit), FCRA (guarantors), FDCPA (consumer debt only), state collection-agency licensing, usury law, UCC 2 and 9, Bankruptcy Code, PACA
Canada
Interest Act, Criminal Code s.347, Bankruptcy and Insolvency Act s.81.1, provincial security, collection and construction acts
Enforced by
Courts, CFPB, states; provinces

Registration or license

US
FinCEN money services business (MSB) registration; state money transmitter licenses unless a bank partnership or exemption applies
Canada
FINTRAC MSB registration; RPAA registration
Enforced by
Same

Rail and network rules

US
Nacha, RTP and FedNow rules; card rules; PCI DSS v4.0.1
Canada
Payments Canada rules; card rules
Enforced by
Operators via banks; networks via acquirers

Accounting

US
ASC 326 (CECL), ASU 2025-05, ASC 606 (revenue at transfer of control)
Canada
Not researched
Enforced by
Auditors

Contract

US
Sponsor bank policy, insurer policies, lender eligibility, retailer compliance manuals (the de facto scheme rules of retail)
Canada
Same
Enforced by
Contract

Customer demand

US
SOC 1 and SOC 2 Type 2 reports, PCI attestation
Canada
Same
Enforced by
Enterprise procurement

FinCEN exempts a payment processor from money transmitter status only if it facilitates a purchase or bill payment, through clearing systems open only to regulated institutions, under an agreement with at least the seller (ruling FIN-2014-R009). State rules are converging: 31 states had passed the CSBS model money transmission law by April 2026, with more since. And since April 27, 2022, FINTRAC has treated invoice payment services as MSBs, exempting only an entity that receives payments for a payee without passing them on, so in Canada an AR platform that collects and then remits to the seller is usually in scope.

Phone payments catch people out. When an AR clerk keys card numbers from a VoIP call, those systems fall into PCI scope (the card industry's security standard). A pay link where the payer enters the card keeps the seller out.

B2B payments: procure to pay

AP sits under more layers than it looks, because it's a tax function, an internal-control function and a payments function at once.

Law

US
UCC 3 and 4 (checks); UCC 4A (wires; commercial ACH credits by agreement); IRC 6041 and 3406 (1099, backup withholding); Prompt Payment Act; SOX 404; state money transmission and unclaimed property
Canada
Income Tax Act (T4A); Excise Tax Act (GST/HST credits); federal construction prompt payment; PCMLTFA (anti-money laundering); RPAA (payment service providers)
Enforced by
Courts, IRS, states; CRA, FINTRAC, Bank of Canada

Accounting standards

US
ASU 2022-04 (supplier finance disclosure)
Canada
IAS 7 and IFRS 7 amendments
Enforced by
Auditors, securities regulators

Rail rules

US
Nacha Operating Rules
Canada
Payments Canada rules
Enforced by
Rail operators, through banks

Network rules

US
Interchange, straight-through programs, surcharges
Canada
Same, with a 2.4% surcharge cap
Enforced by
Networks, through issuers and acquirers

Contract

US
Treasury agreements (security procedures, Positive Pay, limits); rebate schedules
Canada
Same
Enforced by
Banks and issuers

Customer demand

US
SOC 1 Type 2 for any AP tool feeding the general ledger
Canada
Same
Enforced by
Buyers' auditors

The buyer rarely needs a license; the fintech in the middle often does. Taking a buyer's money and paying suppliers with it is money transmission under US state law unless a bank structure or exemption applies; one AP network's filing cites state rules requiring liquid assets of at least 100% of customer liabilities. FINTRAC, Canada's anti-money-laundering agency, has treated invoice payment services as money services businesses since April 27, 2022, exempting only an entity that receives payments for a payee without passing them on. The Bank of Canada has supervised payment service providers under the Retail Payment Activities Act (RPAA) since September 8, 2025. As I read it (and I'm no lawyer), an AP platform that holds buyer funds and pays Canadian suppliers is in scope for both, and the payee exemption doesn't help a payer's agent.

B2B payments: real-time payments and open banking

Payment law

US
UCC 4A for businesses; Reg E for consumers
UK
Payment Services Regulations 2017
EU
PSD2 (the EU payments directive); Instant Payments Regulation
Brazil
Central bank resolutions

Open banking

US
Section 1033 rule, blocked in court
UK
Competition authority's 2017 order; Data (Use and Access) Act powers
EU
PSD2; the Payment Services Regulation from around 2028
Brazil
Open Finance rules

Scam reimbursement

US
None
UK
Up to £85,000 for consumers and micro-businesses
EU
None; bank-impersonation refunds around 2028
Brazil
None; MED traces what's left

The US is the outlier: the CFPB is retreating, and the action has moved to courts, state attorneys general and state legislatures. New York has a bill, introduced in March 2026, that would ban data fees and cover small businesses; I've seen no sign it has moved.

B2B payments: spend management

Business cards fall outside most consumer card law.

Card law

US
Reg Z §1026.12: $50 cap on unauthorized use of any credit card; contracts differ at 10+ cards. No billing-error rights, CARD Act or Reg E for business accounts
Canada
Bank Act: $50 cap; unclear for business cardholders
Enforced by
CFPB, courts; FCAC

Credit law

US
Reg B (a limit cut can be adverse action); Section 1071 from 2028
Canada
No equivalent found
Enforced by
CFPB

Tax and employment law

US
IRC 62 and 274; FLSA; state reimbursement laws
Canada
Income Tax Act; Excise Tax Act; Canada Labour Code; Quebec labour law
Enforced by
IRS, DOL, states; CRA, ESDC, Quebec

Anti-money laundering, money movement

US
Bank Secrecy Act, through the bank; state money transmission if the platform holds funds
Canada
FINTRAC registration; RPAA registration
Enforced by
FinCEN, states; FINTRAC, Bank of Canada

License

US
The bank's charter; money transmitter licenses or an exemption; Visa agent registration
Canada
A bank or trust company issuer, or a fintech under its own Visa licence
Enforced by
Regulators; the network

Network rules

US
No zero liability on Corporate and Purchasing cards; misuse insurance; dispute windows
Canada
Same; misuse insurance of at least CAD 100,000 per cardholder
Enforced by
Networks, through issuers

Attestation

US
PCI DSS v4.0.1 for issuers and their agents; SOC 1 and 2
Canada
Same
Enforced by
Networks; customers

Bank policy

US
Credit box, KYB depth, reserves, prohibited industries
Canada
Same
Enforced by
The sponsor bank

Reg Z's $50 cap reaches business credit cards, but at 10 or more cards the company and issuer can agree other terms, and employees keep the cap only against use by someone else. Business debit, prepaid and just-in-time cards have no legal cap, because Reg E covers only consumer accounts. And where a bank has primary oversight and control of a prepaid program, FinCEN says no participant has to register as the provider of prepaid access.

In Canada, a platform that holds end users' funds or moves reimbursements likely needs FINTRAC registration (since April 2022) and registration under the Retail Payment Activities Act, or RPAA (since September 8, 2025). The RPAA excludes banks and agents of registered payment service providers, but doesn't name agents of banks. As I read it, "we act for the issuing bank" doesn't obviously fit any exclusion for a Canadian card program manager. I'm not a lawyer, and I'd take this one to counsel.

B2B payments: stablecoins and blockchain payments

LayerExamplesWhat it means for a B2B product
LawThe GENIUS Act, MiCA, Canada's Act, sanctions and anti-money-laundering lawWho may issue, what holders can claim, what to screen
LicenceState money transmitter licences, New York's BitLicense, OCC trust charters, EU and Brazilian crypto-firm licencesUsually held by the orchestrator, custodian and off-ramp
AttestationMonthly reserve reports, SOC reports on custodiansWhat a treasurer or auditor can rely on
Network ruleCircle Payments Network rules, card network settlement rulesWho carries the risk inside the scheme
Partner policyA bank's appetite for crypto-linked moneyCan close a corridor overnight

A single US-to-Brazil payment can touch the GENIUS Act (the issuer), US anti-money-laundering and sanctions law (the US ramp), MiCA (if it routes through an EU firm), Brazil's FX rules (the Brazilian ramp) and the Travel Rule on both legs.

A company paying or receiving for its own invoices usually needs no licence, because its provider holds them. Holding, converting or paying out for others can make it a money transmitter, and I'd get counsel on each flow. Charters have become a business asset: the OCC conditionally approved five crypto trust charters, Circle's and Paxos's among them, in December 2025, and reportedly one for Bridge in February 2026.

Card issuing: launching a card program

Separate the layers, because each binds a different party and has a different enforcer.

Law

What it covers
Reg E and the Prepaid Rule, Reg II, Reg Z for credit, the Bank Secrecy Act, FDIC insurance rules, state money transmission
Binds
The bank, and the program through it
Enforced by
Bank regulators, the CFPB, states, private suits

Licence

What it covers
A bank charter; a money services business registration if you're the provider of prepaid access; an e-money licence abroad
Binds
Whoever holds it
Enforced by
The licensing regulator

Certification

What it covers
PCI DSS, PCI card production, processor certification
Binds
Anyone touching card data or cards
Enforced by
Networks, through the bank

Network rules

What it covers
Agent registration, BIN licensing, prepaid approval and reserves, design approval, token rules
Binds
The bank, which passes them on
Enforced by
Assessments and fines on the bank

Bank policy

What it covers
Due diligence, reserves, minimums, approval of every change, prohibited programs
Binds
The program
Enforced by
Contract, freezes, termination

Supervisory guidance and orders

What it covers
The 2023 third-party risk guidance; consent orders
Binds
The bank, then its partners
Enforced by
Examiners

For most US programs, the bank's policy is what binds day to day, and it carries the other layers down to you. A program manager acting as the bank's agent usually stays out of state money transmitter licensing, but holding customer money outside the bank pulls it back in; I'd check each state with counsel.

Abroad the layers sit differently. In the UK and EU a fintech can be an e-money institution and a principal network member, so the safeguarding duty lands on it directly. In Canada, payment service providers register with the Bank of Canada under the RPAA; about 300 made its opening batch, KOHO among them.

The test I'd apply to any obligation: would it survive if we changed banks? Law and network rules would; most of the bank's policy wouldn't, and the next bank brings its own.

Cloud security (CNAPP): posture, workloads and permissions

Nobody licenses cloud security vendors; the rules arrive in layers.

Contract

What it covers
Shared responsibility, the customer agreement
Binds
Customer and provider
Enforced by
Courts, under the contract's caps

Standards with contractual teeth

What it covers
PCI DSS, SOC 2, ISO 27001
Binds
Whoever signed up for them
Enforced by
Card networks, customers, certification bodies

Government buyers

What it covers
FedRAMP, CISA directives
Binds
Vendors selling to US agencies; agencies themselves
Enforced by
FedRAMP, CISA

Sector and disclosure law

What it covers
SEC, NYDFS, bank regulators, the FTC, HIPAA, GDPR, NIS2, DORA
Binds
The breached company
Enforced by
Each regulator

Supervision of the clouds

What it covers
DORA critical providers, UK critical third parties, NIS2 (cloud is an "essential" sector)
Binds
AWS, Microsoft, Google, Oracle and others
Enforced by
EU supervisors, UK regulators

A New York-licensed, SEC-listed lender on AWS answers to its bank regulators, NYDFS, the SEC, PCI DSS through its card processors, state breach laws, and GDPR and DORA if it operates in the EU. Compliance dashboards map one technical check to all of these; the auditors and the evidence they accept differ.

Identity and trust: KYB, KYC and ongoing monitoring

Separate the layers, because each binds a different party and has a different enforcer.

Law

What it says
US bank rules on identifying customers and owners; Canada's PCMLTFR; UK money laundering regulations and company law; EU AMLR
Binds
Banks, licensed money transmitters, other regulated firms
Enforced by
Regulators, through penalties and orders

Law aimed at platforms

What it says
The INFORM Consumers Act
Binds
Online marketplaces
Enforced by
The FTC, up to $53,088 a violation

Network rules

What it says
Visa and Mastercard payfac and merchant rules
Binds
Acquirers, which pass them to payfacs
Enforced by
Fines and assessments

Partner policy

What it says
The sponsor bank's program agreement and risk appetite
Binds
The fintech
Enforced by
Contract, onboarding freezes, termination

Registry practice

What it says
What each registry checks before accepting a filing
Binds
Filers
Enforced by
Registries, now more strictly in the UK

Which layer reaches you depends on what you are. For most US platforms on a sponsor bank, the one that binds you day to day is the contract with the bank. A payfac gets its KYB requirements from the network and its bank; the bank rules themselves bind the bank. A marketplace has INFORM directly: once a seller makes 200 sales and $5,000 in a year, you have 10 days to collect and verify its bank account, tax ID and contact details, and sellers above $20,000 must show their identity to buyers. A B2B software company that doesn't move money may have no legal KYB duty at all, and checks for fraud and trust.

Beneficial ownership is where the four jurisdictions split most:

  • US. The Corporate Transparency Act was meant to give FinCEN a register of every company's owners. An interim rule in March 2025 and a final rule effective August 14, 2026 cut it to foreign companies: about 28,000 instead of the 32.6 million FinCEN once expected. FinCEN is deleting the data it had on US people. Banks still collect owners under their own rule, so the change mattered less to platforms than the headlines suggested: their ownership checks always came from the bank.
  • Canada. Federal companies must file their significant owners with Corporations Canada, publicly since January 2024. Most Canadian companies are incorporated in a province instead, and only Quebec has a public register of its own. Since October 1, 2025, firms that report to FINTRAC must flag mismatches on high-risk federal companies within 30 days.
  • UK. The register of people with significant control has been public for years. Since November 18, 2025 Companies House checks the identity of directors and owners itself. Between 6 and 7 million people have to verify by November 17, 2026, and by the end of June just over half of directors had.
  • EU. In 2022 the EU's top court struck down public access to ownership registers on privacy grounds, and several countries closed theirs. The 2024 directive reopens them to people with a "legitimate interest". From July 10, 2027 the AMLR sets one method across the EU: multiply percentages down each chain of ownership, add them across chains, and count control by other means.

Login and access for apps: authentication and authorization

No single law covers login. The layers:

LayerExamplesWhat it means for an app
Platform mandatesAzure, AWS, Google Cloud, GitHub, SnowflakeMFA for your own admins
Sector rulesPCI DSS, PSD2, FFIEC and New York's DFS, HIPAA (proposed)MFA where card, payment, bank or health data sits
Standards in contractsNIST SP 800-63-4, CISA guidanceThe password and MFA bar customers ask about
Privacy and consumer lawGDPR, the FTC Act, US state laws"Appropriate" security, judged after a breach
Audits and questionnairesSOC 2, ISO 27001, security reviews, insurersThe day-to-day bar for a B2B app

For a B2B app the questionnaire usually bites before any law. The strictest layer you face sets your defaults, and enforcers of the vaguer layers use the specific ones as their yardstick: the UK's ICO and the US FTC have both cited missing MFA. Authorization has almost no law behind it.

Models and inference: what AI runs on

Model makers

US
California SB 53 (frontier developers above 10^26 operations); New York RAISE from 2027
EU
AI Act duties for general-purpose models; Code of Practice
China and elsewhere
Chinese labs mostly outside the EU Code

Chips and weights

US
Export controls: case-by-case H200 licences for China, approved entities in the UAE
EU
China and elsewhere
Beijing approves or blocks imports

Data

US
Sector rules; court preservation orders
EU
GDPR; residency demands
China and elsewhere
Data stays in-country in many sovereign deals

Products

US
Deployer liability (case law)
EU
Product Liability Directive from December 9, 2026
China and elsewhere

The same model reached through the lab, Bedrock or Vertex can come with different retention, residency, SLA and indemnity terms, so the route is a legal choice too. For most builders the law arrives through vendor terms and procurement questionnaires.

Observability: metrics, logs and traces

Observability has no licensing regime. Nobody needs permission to collect or store telemetry, and no regulator supervises observability vendors as such. Rules reach this industry through four other doors.

Data inside telemetry

What it covers
GDPR and CCPA for personal data, HIPAA for health data, PCI DSS for card data
Binds
The customer as controller; the vendor as processor by contract
Enforced by
Data protection authorities, the FTC and states, card networks through acquirers

The buyer

What it covers
FedRAMP for US federal agencies, OMB logging memos, SEC disclosure for listed companies
Binds
Vendors selling to those buyers; the buyers themselves
Enforced by
Agencies, auditors, the SEC

The market

What it covers
EU Data Act switching rules, competition review of deals
Binds
Vendors
Enforced by
The EU, competition authorities

Attestation

What it covers
SOC 2, ISO 27001
Binds
Vendors, as a sales requirement
Enforced by
Customers' procurement teams

GDPR and CCPA don't mention logs; they apply because logs carry IP addresses, user IDs, emails and tokens. SOC 2 is a contract artifact with no legal force, and in practice it's the report every vendor is asked for first.

The test I'd use on any requirement: is it about the data, the buyer or the vendor? Data rules follow the data into every tool, buyer rules only matter if you sell to that buyer, and vendor rules mostly live in contracts.

Phone numbers, messaging and voice

I keep these layers apart because each has a different enforcer and a different penalty.

Law

US and Canada
TCPA (the US consent law for calls and texts); state laws (Texas treats texts as telephone solicitation since Sept 2025); CASL (Canada's anti-spam law); Kari's Law and RAY BAUM'S Act for 911
Elsewhere
Spain's Orden TDF/149/2025; Colombia's Ley 2300
Enforced by
Courts, plaintiffs, regulators

Regulator rule

US and Canada
FCC rules: 47 CFR Part 9 (911), Part 52 (numbering), Part 64 (consent, robocalls); CRTC decisions
Elsewhere
India's TCCCPR, ACMA's register, CNMC's alias registry, CRC resolutions
Enforced by
FCC, CRTC, national regulators

Industry guideline

US and Canada
CTIA principles and handbook; Canadian short code guidelines; token policy from STI-GA (the industry board that governs SHAKEN)
Elsewhere
MEF's SenderID registry (UK)
Enforced by
Audits, contracts, token revocation

Carrier policy

US and Canada
Codes of conduct, filtering, fines, throughput tiers
Elsewhere
Allowlists, per-carrier ID approval
Enforced by
Blocking and fines

Platform-owner policy

US and Canada
Meta's Business Messaging Policy; Google's RCS acceptable use policy
Elsewhere
Same
Enforced by
Rejections, pauses, bans

Your policy

US and Canada
Acceptable use, KYC
Elsewhere
Same
Enforced by
You

Carrier policy is routinely stricter than the law. The 11th Circuit threw out the FCC's one-to-one consent rule on January 24, 2025, and the FCC later deleted it. Yet providers say toll-free and campaign reviewers still reject consent that lead generators gathered for unnamed "partners". The FCC allows up to 10 business days to honor an opt-out; carriers expect STOP to work immediately.

Canada is the useful contrast. CASL requires consent, sender identification and a working unsubscribe, with penalties up to CAD 10M for a business, but the part that would let people sue directly has been suspended since 2017. Providers say there's no 10DLC-style registry for texts within Canada, but Canadian numbers texting the US must register with TCR. Toll-free reaches both countries. Canadian short codes must answer STOP, ARRET, HELP, AIDE and INFO in English and French.

Voice AI: real-time voice agents

CallLayers that apply
Outbound, USTCPA and the FCC's rules, state telemarketing laws, state AI-disclosure laws, state recording laws, carrier policy, the platform's terms
Inbound, USState AI-disclosure laws (Maine, Utah), recording and wiretap laws, biometric laws if voiceprints are used
Any call in the EUAI Act Article 50, GDPR, national telemarketing and recording rules
Health or card data, anywhereHIPAA and BAAs; PCI DSS through the card networks
CanadaThe CRTC's rules on automated calls (which already cover synthesized voices), privacy law

One agent usually serves callers in every state, so in practice the strictest layer wins: an all-party recording notice on every call, AI disclosure in every greeting.

Field Guides are learning notes, not legal or compliance advice. Rules and fees change; check the cited primary sources before you act on anything here.