Confidentiality
NDA requirements and limits on sharing project information.
Responsible project delivery
Security, confidentiality and GDPR
Plan access, confidentiality and data-protection responsibilities clearly when working with a development partner.
Security starts with scope
Protect client work from the beginning
Before sharing credentials or personal data, agree responsibilities, access needs and the information that must be protected.
Discuss confidentiality before sharing sensitive details
Grant only necessary access
Use project-specific accounts where practical
Document access revocation at handover
Project safeguards
Topics to agree during onboarding
The exact controls depend on the project and contract.
Access management
Account ownership, permissions and credential handling.
Code and IP
Repository access, handover and ownership terms.
Data processing
Determine whether personal data is involved and whether a DPA is required.
GDPR considerations
Clarify the roles, not just the terminology
Compliance depends on the actual processing activities and agreements.
Controller and processor roles
Identify who determines purposes and means of processing.
Data minimization
Limit personal data used in development and testing.
Contractual responsibilities
Document obligations, subprocessors and transfer considerations where applicable.
Before work begins
A short security checklist
Use these questions to prepare for kickoff.
Will the team access production systems?
Is personal data included in the work?
Which accounts and repositories are needed?
What is the agreed handover and revocation process?
FAQs
Frequently Asked Questions
Practical answers before we start working together.
Do you sign an NDA?
Confidentiality terms can be discussed before sharing sensitive project information; any NDA is subject to agreement.
Can you provide a DPA?
If personal data processing requires a DPA, the parties should review roles, processing details and contractual requirements before work begins.
Is BitcraftX GDPR certified?
This page does not claim a GDPR certification. GDPR responsibilities depend on the project and the contractual roles of the parties.
Who controls access to the project?
Access permissions, account ownership and credential handling should be agreed during onboarding.
Who owns the source code?
Intellectual property and delivery terms are specified in the signed project agreement.
Let’s work together
Tell us what you need delivered
Send your project scope, timeline and technical requirements. We will discuss a suitable collaboration model.