THE PROJECT WEBSITE
Website privacy
How this website handles requests, demo entries and browser storage.
Updated 19 October 2026.
Who to contact
This website is operated by ${escape(facts.operator)}. For questions about information handled through this website, or to ask about access, correction or deletion, contact ${escape(facts.contact)}. Describe the example and approximate time involved; do not send session cookies or admin credentials.
Local preview. The website operator and public privacy contact must be supplied before the public website build. No contact details have been invented.
'}Reading the website
The project homepage and guides add no analytics, advertising tags or optional cookie prompt. Fonts, images, styles and demo scripts are served from this website. The example privacy, cookie and terms documents describe their sample products; they are not this website’s privacy notice.
Cloudflare hosts the website and processes request information, including your IP address, requested URL and browser headers, to deliver and protect it. Demo creation also uses your IP address for rate limiting. The application does not put raw IP addresses or raw request headers into its demo evidence ledgers. Cloudflare’s network processing is separate from the demo database cleanup described below. See Cloudflare’s privacy policy.
A demo workspace for your browser
Opening a recorded example or the demo admin creates an isolated database on Cloudflare. A first-party session cookie named __Host-notabenda_demo allows this browser to return to it without a password. The cookie is sent only over HTTPS, is inaccessible to page scripts and has no persistent expiry. It is used for the demo you opened, not advertising. The two website domains do not share this cookie.
The database contains seeded sample records and the actions or entries you submit in recorded examples, including choices, agreement assertions, form permissions, contract declarations and sample order requests with their exact quotes and product facts. These can include the name, email address or other fields you type. Use sample details; do not enter sensitive information. Demo actions do not create real contracts, change external services, send email, take payment or perform refunds.
The session expires after one day without use. Activity refreshes that deadline. Cleanup is scheduled at expiry and can be delayed by background execution or retries. Closing the browser or clearing the cookie removes your way back but does not immediately delete the database. Some browsers restore session cookies. Exports you download and provider-managed copies have their own lifetime; the demo cleanup does not delete those copies.
Storage in interactive examples
Some examples demonstrate saved cookie preferences, pending retries or recovery through local storage, session storage and browser databases. Their pages explain the behavior they demonstrate. Cookie-consent samples wait for permission. The storage-settings example starts two local features under declared draft exception profiles and gives you direct on/off controls. Its feature settings and objections stay in the browser database notabenda-storage-exceptions-v1 until you clear browser storage. The reading-layout preference uses local storage and is removed when you switch it off; sample interaction counters are temporary. These sample services upload no events. You can clear this website’s browser storage through your browser settings; doing so may remove a saved choice or retry. Browser-local cleanup does not itself erase server records. The order example keeps its exact review and pending request in session storage so this tab can check the same attempt after navigation; clearing it can remove that recovery copy.
Guided setup runs in your tab. Its answers and imported files are not uploaded or saved by the setup interface. Download the private report if you want to keep those notes. Keep that report outside public assets and repositories.
Using the toolkit on another website
Notabenda does not receive records from websites that install its packages. Their operators choose their configuration, providers, hosting, retention and contact routes. This notice covers the project website only. Read the integration guide or return to the examples.