Bounded submissions
The public form endpoint takes JSON only, caps the request size, and caps every text field inside it.
Nothing to wire up. You describe the business in plain language, Ifa designs and builds it, and you check the plan before any of it exists.
Security & data handling
This page sticks to what is implemented today. Anything we cannot point at in the repository or the deployment configuration is not claimed here.
Each of these can be inspected in the code that runs this site.
The public form endpoint takes JSON only, caps the request size, and caps every text field inside it.
A hidden field and a browser-side cooldown, with the same neutral response either way so a bot learns nothing.
Form responses are marked no-store, so a submission result is never served again from a cache.
Mail credentials and the notification address come from deployment configuration. Neither is in the source.
The owner's email carries a request reference and a link. It does not carry the contact details or the free text.
This site has no login, no account session and no direct route into the product's services.
Product principles
Each service in the product owns its own schema and connects with its own least-privilege role. Workspace actions run as typed, validated operations that keep their review and audit context instead of executing whatever they are handed.
These are architectural controls. They are not a certification, and they are not a substitute for your own legal and security review.
Write to hello@ifa.solutions with what you need to know. You will get a direct answer that separates what exists today from what is planned.
Whichever one answers your next question.
With your permission we use Google Analytics and a small set of our own events to see which pages and named actions are useful. Form values and contact details are never included. The site works either way. Read our Privacy Policy.