When work involves domains, email, hosting, websites or business systems, access and handover matter as much as the technical work itself.
We work with the access required for the agreed task and avoid treating client accounts as if they belong to Tech Done Easy.
Credentials or account access should be provided only where it is necessary to perform the agreed work.
Multi-factor authentication is encouraged on important accounts wherever the service supports it.
Access should be reduced or removed when the work no longer requires it, subject to the relevant provider's controls.
If a project needs a developer, designer, hosting provider or other specialist, the requirement and scope are clarified before involving them.
Client information is treated as confidential and shared with specialists only when it is relevant to the agreed work.
Where practical, access should be limited to the systems, accounts or permissions required for the task.
The client remains informed about what is being changed, who is involved and what needs to be handed back.
Backup and rollback arrangements depend on the systems involved. Where they are relevant, they should be agreed before a change that could affect production data or service availability.
Where the platform supports reliable backups or snapshots, we consider them as part of the change plan. We do not claim responsibility for backups controlled entirely by a third-party provider.
Important configuration decisions, credentials ownership and operational notes can be documented where the project requires them.
At completion, the agreed result and relevant next steps are explained so the client knows what changed and what remains.
Security responsibilities can depend on the client, the technology provider and the systems being used. We agree practical responsibilities as part of the scope rather than making blanket security guarantees.
Tell us what is happening and we will work out the next step.