Confidentiality
A mutual NDA is standard before detailed discussions. We can work under your agreement or provide one for review. Sensitive context is shared only with the people who need it.
Trust & working model
Clear working controls from the first conversation.
Confidentiality, ownership, access and data handling should be explicit before work starts. Here is how we handle them, and what we need from your team.
You own the work
Code, designs, documentation and infrastructure created for the engagement transfer to you on payment, unless a third-party license says otherwise. Ownership is written into the contract.
Data handled with restraint
We ask for the minimum access needed, avoid copying production data into local environments, and agree retention and deletion before work begins. Client data is not used to train public AI models.
Access and offboarding
Access is role-based, time-bound and revoked at the end of an engagement. We document environments, credential ownership and handover so your team retains control.
US-overlap working hours
Remote-first delivery with planned overlap for US Eastern and Pacific time zones. Decisions are written down, reviews are recorded, and updates do not depend on someone being online late.
Commercial clarity
USD proposals, written scope and acceptance criteria before work starts. New scope gets a written estimate before anyone builds it.
Procurement
Security questionnaires and reviews
We complete your vendor questionnaire and join architecture or security reviews. We describe our controls precisely, provide evidence where we have it, and agree compensating measures where your requirements call for them.
02
Questions we answer before kickoff
Can you sign our NDA and MSA?
Yes. We can review and work under client paper, or provide a mutual NDA before detailed discussions.
How do you handle production access and integrations?
Least-privilege access, named accounts, time limits and documented revocation. Integrations use scoped credentials and explicit data-ownership boundaries.
Can you work with our security team?
Yes. We complete vendor questionnaires and join architecture or security reviews.
Where does our data live during delivery or migration?
In the systems and cloud accounts you approve. We avoid unnecessary copies, validate migrations against agreed checks, and confirm retention and deletion before kickoff.
Who owns the code, infrastructure, and handover if we stop?
You do, subject to the contract and third-party licenses. Runbooks, architecture notes, and credential handovers are included so your team can maintain the system without lock-in.
Do you use AI on client data, and how are AI operating costs controlled?
We do not use client data to train public models. AI-assisted tooling follows your policy, and any production AI features include scoped permissions, fallbacks, and usage monitoring.
Need a vendor questionnaire completed? Send it over. We will answer each question in writing.
Contact ProwebXRead how we workExplore capabilities