What to share in an inquiry
The contact form asks for your name, email, service and a short workflow brief. Budget and referral details are optional. Describe the task, the tools involved and who checks the result. A redacted example is enough to start.
Please leave out passwords, API keys, sensitive personal data and confidential client records. Do not paste credentials into the form or public demos. If the work needs sensitive material, ask me how to share it before sending it.
The three browser demos
The inquiry, support and document workflows run in your browser. They use local parsing, matching and templates. They do not call an AI provider or model, send your input to a server, or connect to a CRM, help desk or accounting account.
Input stays in the current page and clears when you reload. The invoice workflow can download a CSV or JSON file after review. A downloaded file remains wherever you save it. Read what the site shows.
Your website inquiry
After validation, your inquiry is saved in my authenticated operations workspace. The application encrypts its records before saving them in a separate private GitHub repository. Vercel hosts the website and the workspace.
Formspree receives an owner notification with a record reference and a link to the workspace. It does not receive the brief or contact details in that notification. Historical submissions may still exist in Formspree and email inboxes from earlier form handling.
The on-screen receipt confirms that an inquiry was saved. It reports whether the owner notification service accepted an alert, which does not establish inbox delivery. Visitor email receipts are not enabled yet. No automatic sales sequence follows a form submission.
Storage, logs and retention
Inquiry records include the submitted details and operational information such as status, timestamps and review history. The server also keeps a hashed IP rate-limit record to limit repeated submissions. The inquiry route checks a honeypot.
The private storage repository keeps encrypted historical versions until its history is purged. Removing the latest record alone does not remove those versions. No automatic time-based deletion period is configured in the inspected storage code.
Vercel can process technical request information to host the site. Optional Google Analytics runs only after you allow it. Custom events do not include form content, names, emails or phone numbers. Your choice is stored in your browser and can be changed through Analytics settings.
AI providers in client builds
The provider, model and data sent depend on the project. I agree those choices in writing before a build starts. That agreement should name the inputs, permitted uses and retention settings. There is no single model provider or retention promise for every client build.
Accounts, permissions and secrets
You own your business accounts and API keys. Access is granted for the project and removed at handover. The scope identifies which accounts and permissions the workflow needs.
On this website, server credentials and the storage encryption key are read from environment variables. They are not form fields or analytics parameters.
Human review and approval
I agree approval points before implementation. Unattended sending and financial actions stay outside the scope unless they are explicitly agreed. An editable draft should return to review when its content changes.
Limits
I do not offer a security certification through this service or guarantee AI accuracy. A test can check an agreed example. It cannot prove that every future input is safe or correct.
Raise a concern
Email buildznofficial@gmail.com to ask about access, correct an inquiry or request deletion. Include enough context to identify the request and leave out sensitive documents.