Tell me what you are trying to build, fix, govern, prove, or launch, and I will point you to the public Folium page that fits. It uses public routes only, so do not send private data here.
Privacy notice
Public intake should stay light and safe.
This notice explains the privacy boundary for Folium Systems public pages and demonstration tools. Public forms and demos should not receive private customer data, regulated records, secrets, or production credentials.
Privacy boundary
Public intake boundary
Public contact and demonstration surfaces are designed for high-level workflow discovery. Sensitive customer records, regulated data, secrets, credentials, and confidential files belong in a scoped intake process.
Privacy boundary
What not to submit
Do not submit private customer data, regulated records, payment data, credentials, secrets, legal files, financial account details, health data, or confidential business data through public surfaces.
Privacy boundary
Production intake standard
Before customer-specific production intake, Folium defines form protection, routing, retention rules, access control, deletion paths, and clear disclosure of any analytics or third-party processors.
Privacy boundary
Cloudflare hosting path
Folium can use Cloudflare for verified public hosting. Any future Turnstile, logs, analytics, Worker routes, or storage bindings should be documented before launch.
Start here
Keep discovery useful without exposing sensitive data.
A strong first conversation can start with workflow pain, tool names, goals, and constraints. Detailed private data belongs in a scoped, approved intake process.
- 01 Scope
- 02 Build
- 03 Prove
- 04 Operate