Legal pages and consent
Open in
The site renders your legal pages from text you supply and facts the file states, and asks a visitor before any tag you add loads.
Filled: what a visitor and a Customer read. The words are always yours.
What the site tracks, and consent
The generated site sets no cookie before sign-in, and counts visits without one. So by default it shows no consent prompt.
The portal's session cookie arrives with sign-in and does nothing else. Every tag you add in consent.tags waits for the visitor's yes to its category.
| The visitor | The site |
|---|---|
| Opens a page | Shows the prompt once, each category apart, refusing in one click as accepting does |
Refuses, or sends the browser's privacy signal with gpc | Loads no tag in that category, and asks again only after a new notice |
| Accepts | Loads the tags of the categories accepted |
| Changes its mind | Uses the footer link on every page, which withdraws at once |
Each choice is a consent record: the categories, the notice version seen and the time, written as an Event.
Who writes what
APIs.Dev never writes a legal word for your product. You supply the text, and the file supplies the facts it states.
| Page | The words, from | The facts it prints, from the file |
|---|---|---|
| Terms | legal.terms | The seller in legal.entity, the prices, the refund rule and the licence in terms |
| Privacy notice | legal.privacy | Each data class kept, the processors, where the data lives and how long |
| Data processing agreement | legal.dpa, or the one governance generates | Your role per class, the sub-processors and the window for a person's request |
| Imprint | legal.imprint | The seller's name, address and contact |
| The refund rule | The Offer | The rule each receipt cites |
Your text places a fact by name, such as the processor list, so a deploy that adds a processor updates the page that lists it. A Live product that charges and has no terms or privacy text is refused at publish with legal_missing.
Versions and acceptance
Each page has a digest per version, and every old version stays at its own address.
A Customer accepts the terms digest at sign-up; an agent sends it in Accept-Terms, and each receipt names it. A change reaches Customers by the notice rule on agreements and price changes.
Text of your own, one tag
The weekly brief supplies its own terms and privacy notice, and adds one advertising tag behind consent.
import { define, generative } from 'apis.dev'
/** A weekly brief on the software companies that changed headcount,A visitor who refused advertising leaves this record behind.
{
"type": "Consent.recorded",
"at": "2026-10-28T14:Broadcasts
One message to contacts and Customers who consented: approved, sent in each reader's timezone, unsubscribed in one click, and posted to a feed agents read.
Ready actions in automation tools
Your product inside the automation tools a Customer's team wires by hand: each Verb a ready action, each move an instant trigger, generated from the file.