Digital Assets, Systems & Access Control Policy
01Purpose
Nino Techy does not operate as a design-only service. When we develop, deploy, maintain, or manage a website, application, or digital system, we are responsible for the technical operation and long-term continuity of that system.
To maintain security, performance, reliability, and proper technical management, Nino Techy requires appropriate administrative access and control over the digital assets associated with every project.
This policy establishes how ownership, access, management, and responsibility for those assets must be handled.
02Scope
This policy applies to all digital assets connected to a Nino Techy project, including but not limited to:
- Domains and domain registrar accounts
- DNS management
- Hosting and server accounts
- Websites and web applications
- Mobile applications
- Databases
- Source-code repositories
- Cloud platforms
- APIs and API keys
- SSL certificates
- Email and transactional email services
- CDN and security services
- Analytics and monitoring systems
- Third-party integrations
- Deployment platforms
- Business-critical software and infrastructure
03Full Access Requirement
For every project under Nino Techy's development or management, the company must have full administrative access to all systems required to operate, maintain, troubleshoot, secure, and develop the project.
Having access only to a specific function, such as DNS management or website editing, is not considered sufficient where broader administrative access is technically required.
The purpose is not to make unnecessary changes to a client's infrastructure. It is to ensure that Nino Techy can act immediately when technical action is required.
04Domain & DNS Policy
Where Nino Techy is responsible for the website or digital system, the domain must be:
- Registered under the appropriate company/client account agreed upon for the project.
- Accessible to Nino Techy through an administrator/developer account.
- Managed through a registrar where appropriate administrative control can be maintained.
- Configured so Nino Techy can manage DNS records when required.
Changing nameservers is not the objective of this policy. Nameservers may remain unchanged for the entire duration of a project. Full domain access is required because domain management involves substantially more than nameservers, including DNS records, verification records, redirects, SSL configuration, email-related records, security settings, renewals, and other technical requirements.
05Ownership & Control
Nino Techy requires clear ownership and responsibility for the digital assets involved in its projects.
Where an asset is purchased or created by Nino Techy on behalf of a client, the ownership arrangement must be documented in the project agreement.
Where the client owns the underlying asset, such as an existing domain, Nino Techy must still receive the administrative access necessary to perform its contracted responsibilities.
No critical project asset should depend exclusively on the personal account of an individual employee, developer, freelancer, or unrelated third party.
06No Single-Person Dependency
Nino Techy projects must not be technically dependent on one individual. For business continuity:
- Credentials must not exist only with one developer.
- Domains must not be controlled exclusively through a personal account.
- Hosting must not depend exclusively on a freelancer's account.
- Source code must not exist only on a developer's personal machine.
- Critical API keys and credentials must be securely documented.
- At least the appropriate company representatives must have access to critical systems.
This protects both Nino Techy and its clients from unnecessary operational risk.
07Security & Credential Management
All access credentials must be handled securely. Nino Techy team members must not:
- Share passwords through unsecured public channels.
- Use personal accounts where a company account is reasonably available.
- Remove company access without authorization.
- Transfer ownership of project assets without approval.
- Change critical infrastructure without proper authorization.
Where possible, access should be provided through individual administrator/developer accounts rather than sharing a single password.
08Infrastructure Changes
Nino Techy may make technical changes to project infrastructure when such changes are reasonably required for:
- Website operation
- Security
- Performance
- Deployment
- DNS configuration
- Email configuration
- API integration
- Server configuration
- Monitoring
- Maintenance
- Troubleshooting
- Scalability
Major changes affecting the client's business operations should be communicated and documented where appropriate.
09Third-Party Access
If a third-party developer, agency, hosting provider, or contractor is involved in a Nino Techy project, their access must not prevent Nino Techy from maintaining the system. Third-party access should be:
- Identifiable
- Limited to the required scope
- Revocable
- Documented
- Secondary to the primary project management structure
No third party should retain exclusive control over a critical project asset without explicit written approval.
10Project Handover
If a project is terminated, transferred, or otherwise handed over, Nino Techy will follow the ownership and handover terms established in the project agreement. A handover may include:
- Domain access
- Hosting access
- Source code
- Database
- Documentation
- Credentials
- API configuration
- Deployment information
- DNS configuration
- Other project assets
Any outstanding financial or contractual obligations must be resolved according to the applicable agreement before final handover.
11Policy Principle
The fundamental principle of Nino Techy's policy is:
If Nino Techy is responsible for building, operating, maintaining, or securing a digital system, Nino Techy must have the appropriate level of administrative control required to actually fulfill that responsibility.
Access is therefore not requested for the purpose of making unnecessary changes. It is required to ensure continuity, accountability, security, performance, and professional management. No Nino Techy project should be delivered in a structure where the company is responsible for the system but does not have the access necessary to control and maintain it.