Know what you are sharing before you start.
The /start intake is deliberately small. It helps Kiteweld understand a workflow problem without asking you to hand over the sensitive material behind it.
Review the intake01 / What we collect
The first brief stays intentionally small.
The public /start intake collects five fields: businessType, vertical, workflowNeed, currentTools, and contact. They help Kiteweld understand a workflow problem and respond without asking for the records behind it.
- Business type and workflow need describe the operating context and the bottleneck you want to examine.
- Current tools show where a future workflow may need to meet the systems you already use.
- Contact gives Kiteweld a way to respond and continue the conversation.
02 / How it is used
Context for a useful response.
Kiteweld uses the intake information to understand the project, assess fit, respond to the brief, and manage the resulting relationship.
- The brief frames discovery and scoping before anyone discusses deeper implementation details.
- It is a conversation starter, not a general-purpose document drop or secret-sharing channel.
- The public confirmation does not expose internal lead-review notes.
03 / Retention approach
Deletion is an operational aim, not a timer.
Kiteweld aims to delete intake information when it is no longer useful for responding to a project or managing the resulting relationship.
- There is no fixed retention period stated here.
- There is no automatic-deletion promise stated here.
- Retention decisions remain part of the practical project and relationship workflow.
04 / Who can access it
Lead review follows an authenticated admin role.
Submissions are not presented as a public list. Lead reads and updates go through the authenticated Better Auth admin-role boundary before the app accesses those records.
- The public intake can create a project brief, but it cannot browse other submissions.
- Admin lead review is a separate, authenticated surface.
- The policy does not present lead data as available to every visitor or as a public directory.
05 / What not to send
The public form is not a secure dropbox.
Please do not submit passwords, API keys, payment details, health information, regulated records, or other sensitive data through the public intake.
- Share the shape of the workflow and the tools around it instead of the records behind it.
- Kiteweld does not need secrets or sensitive material to decide whether a conversation makes sense.
- Deeper details can be worked through with the team later, in the appropriate project context.
06 / Third-party boundaries
External services have their own limits.
The site uses Meta Pixel for page and lead events. An optional Polsia analytics beacon may also be present when enabled by the deployment.
- Kiteweld does not control those providers’ policies, retention practices, or availability.
- Third-party handling is subject to the provider’s own systems and policies.
- The presence or availability of an optional analytics beacon can vary by deployment.
The first brief is a conversation starter. It is not a document drop or a secret-sharing channel.
Business type
businessTypeThe operating context Kiteweld should understand.
Vertical
verticalThe market context that helps Kiteweld bring relevant workflow patterns.
Workflow need
workflowNeedThe bottleneck or follow-through problem to examine.
Current tools
currentToolsThe systems a future workflow may need to meet.
Contact
contactA way for Kiteweld to respond and continue the conversation.
Leave out secrets and sensitive or regulated data. None is needed to decide whether a conversation makes sense.
Before you send a brief
Keep the first conversation useful.
Share the shape of the problem, the tools around it, and a way to reach you. Leave out secrets and sensitive or regulated data; those are not needed to decide whether a conversation makes sense.
Start a workflow project