Great infrastructure starts with clear responsibilities. Explore the privacy, security and operational considerations behind your next MNDSET.DEV project.
Requirements depend on the service, the data involved and the way a system is operated. These are the areas to define before deployment.
01 / PRIVACY
Start with the data.
Where personal data is involved, GDPR responsibilities follow the actual processing activities. A project should establish what data is needed, why it is used and who is responsible for it.
Identify controller and processor roles.
Define collection, access, retention and deletion requirements.
Put the required processing terms in place where a processor acts on a controller’s behalf.
02 / SECURITY
Match controls to the risk.
Security is a combination of architecture, configuration and ongoing maintenance. The appropriate controls depend on the system and the impact of potential failures.
Define authentication and access permissions.
Agree on encryption, logging and update requirements.
Document backup, recovery and incident responsibilities.
03 / OPERATIONS
Know who runs what.
Hosting a system and managing an application are different responsibilities. A service agreement should make the boundary between infrastructure, software and customer operations explicit.
Distinguish managed and unmanaged service scope.
Confirm hosting location and relevant suppliers.
Specify support coverage and any agreed service levels.
04 / WEB3 & AI
Make dependencies visible.
Blockchain networks, AI providers and external APIs introduce their own data flows, operating conditions and limitations. These need to be considered as part of the complete solution.
Consider public and potentially irreversible blockchain records before submitting data.
Review external processing, provider terms and transfer requirements.
Define human review for consequential AI-assisted workflows.
Shared understanding
Clear boundaries. Better decisions.
Use these topics to agree a practical division of responsibilities for your project. The signed service scope determines the actual allocation.
Responsibilities to confirm before starting a project
Area
Define in the service scope
Customer input
Personal data
Processing roles, instructions, access and any required data processing agreement.
The intended purpose, data categories, lawful basis and relevant sector requirements.
Infrastructure
Hosting location, supplier dependencies and responsibility for platform maintenance.
Location restrictions, capacity needs and internal procurement requirements.
Application security
Software maintenance, authentication, permissions and security review scope.
Authorised users, business workflows and ownership of customer-managed components.
Continuity
Backup coverage, restoration procedures and any agreed availability targets.
Acceptable downtime, recovery priorities and retention needs.
Third-party services
Integrations, external processing and responsibilities for provider changes.
Approved vendors, licences and restrictions on external services.
Before you deploy
The important questions.
Does this page mean every service is GDPR compliant?
No. GDPR compliance depends on the actual processing, the parties’ roles and how the service is used. Infrastructure is only one part of that assessment. Requirements and responsibilities need to be established for the specific project.
Can I request a data processing agreement?
Yes. Contact us with the service and processing activities you have in mind. Where MNDSET.DEV acts as a processor on your behalf, the relationship must be governed by the required processing terms before that processing begins.
Where will my project’s data be hosted?
Confirm this for your selected service before ordering. Hosting location, backup locations and the involvement of third-party providers can vary by solution. This page does not make a blanket commitment to EU-only hosting.
Are backups, monitoring and updates included?
Check the scope of the selected hosting or development service. Managed and unmanaged offerings have different boundaries. Backup frequency, restoration support, update responsibilities and monitoring should be explicitly agreed.
How should I report a security concern?
Email [email protected] with the affected service, a description and the approximate time of the issue. Do not include passwords, private keys or unnecessary personal data. Do not access other users’ information or disrupt a service while investigating; request authorisation before further testing.
Can you help with a regulated or sensitive project?
Share the relevant sector, intended processing and technical requirements before commissioning work. Suitability, specialist reviews and additional controls need to be assessed for that project. Technical delivery does not replace independent legal or regulatory advice.
Let’s define it properly
Your requirements. Part of the architecture.
Planning a project with privacy, security or procurement requirements? Bring them into the conversation from the start, so the service scope reflects what your organisation actually needs.
Compliance enquiries[email protected]Include your service or project reference and the topic of your request. Please leave out secrets and sensitive attachments in your initial message.