role/01
Founder — company and infrastructure
Company direction, network and infrastructure planning, provider coordination, service readiness and final decisions.
OPSoperations
Operations and responsibilities.
NEKONODE is operated by a small core team. This page describes who is responsible for what, and where each request goes.
O1responsibilities
Two areas of responsibility.
The functions that exist today and the addresses that reach them.
role/02
Support — requests and service monitoring
Support requests, incoming email and customer enquiries, plus service monitoring and escalation of operational issues.
O2request routing
Where a request goes.
Using the matching address routes a request to the correct queue.
-
General
General questions, partnership requests, business enquiries, or non-urgent messages.
-
Support
Billing questions, technical help, cancellation requests, refund requests, and service issues.
-
Abuse
Malware, phishing, spam, DDoS, fraud, network abuse, or copyright complaints involving NEKONODE services.
-
Legal
Court orders, law enforcement requests, regulator requests, preservation requests, or other formal legal requests.
-
Privacy
Data protection requests, privacy questions, access requests, deletion requests, or correction requests.
No response-time guarantee is published. When service levels are committed to, they will appear in the Terms of Service.