Legal & compliance
Plain-language answers to the questions enterprise procurement asks before a contract can be signed. Anything not yet confirmed is marked as a placeholder rather than guessed at.
NDA
Willing to sign a client's own NDA, or to offer a standard mutual NDA where none is supplied. Raise it on the scoping call before any project detail is shared.
IP assignment
Work is performed as work-for-hire. All intellectual property in the delivered code and assets is assigned to the client on final payment, at which point the repository and any related credentials are transferred.
Data handling Unconfirmed
Project data is handled with least-privilege access and is not retained beyond what is needed to deliver the engagement. Exact retention periods, storage locations, and his stance on submitting client data to third-party AI tooling for training purposes have not yet been formally confirmed in writing — treat this section as directional until confirmed on the scoping call, not as a signed policy.
Sub-processors Unconfirmed
Depending on the project, a build may route data through model providers such as an LLM API (e.g. OpenAI, Anthropic, or a self-hosted model) and a voice pipeline provider (e.g. Pipecat Cloud). The exact list of sub-processors touching a given project's data is project-specific and will be confirmed in writing before work starts — no fixed list is published here because it would vary per engagement.
Accessibility statement
This site targets WCAG 2.1 AA as a conformance goal: keyboard operability throughout, visible focus states, reduced-motion and reduced-data support, and no audio or video that autoplays with sound. Known gaps: some third-party embeds (where used) may not be independently auditable, and a full manual screen-reader pass has not been logged for every page. Reported issues are welcome via the contact page.
Privacy
This site does not use tracking cookies or third-party advertising scripts. If a privacy-preserving analytics provider is added, it will be disclosed here with exactly what it collects. The contact form sends data directly to an email address or a form-processing endpoint chosen by the client-facing configuration — no data is sold or shared with third parties.
Terms of engagement
Work is billed per fixed-scope milestone, priced and settled in USD: 50% on milestone start, 50% on delivery. Any milestone not yet started is fully refundable. Full IP in the delivered work assigns to the client on final payment. Rates, tiers and the full payment FAQ are on the pricing page.
Unconfirmed Governing law, jurisdiction and formal liability terms have not yet been fixed to a specific contract template — a written agreement covering these is put in place before a paid engagement starts, not assumed from this page.
Security posture
Credentials are never requested or sent over chat or email. Access to client infrastructure is requested at the minimum scope needed for the task, through the client's own secret manager or invite system wherever one exists, and revoked at the end of the engagement. If a project requires temporary access to production systems, that access is scoped, logged, and time-boxed on request.