Skip to content
SkyDibiaSatellite-backed
Security

Security & Network Integrity

Security principles for customer access, network operations, payments and protected SkyDibia workspaces.

Last updated: 2026-09-27

Current operating rules

These sections describe how SkyDibia presently delivers and protects the relevant service or customer relationship.

Selected legal wording pending review

Sections marked Pending legal review identify standard legal or commercial clauses that are still being finalised with qualified Nigerian legal input.

Current operating rule

1. Access control

SkyDibia uses controlled customer, partner and administrative access. Public Wi-Fi sessions require a valid access entitlement, while protected customer, partner and operations workspaces use relationship-specific authentication and access controls.

Current operating rule

2. Network and device isolation

SkyDibia designs customer-access networks to reduce unnecessary device-to-device exposure and to separate user access from protected operational systems. This is a security objective, not a promise that any network can be made absolutely risk-free.

Current operating rule

3. Traffic and technical records

SkyDibia does not inspect or store the content of customer internet traffic as a normal operating practice. Technical records such as session, device, access, payment-verification and network events may be retained where needed for service delivery, troubleshooting, security or accountable operational review.

Current operating rule

4. Human-reviewed operational controls

Technical observations, alerts or scores may inform investigation. Material customer-access warnings, restrictions and restorations should remain attributable to authorised human decisions, with the relevant operational record retained where the system supports it.

Current operating rule

5. Application, payment and administration controls

SkyDibia applies server-side payment verification, role-based administrative permissions, protected tokens and audit or event records across relevant workflows. Customer-facing systems should not treat browser-supplied prices, payment status or privileged permissions as authoritative on their own.

Current operating rule

6. Customer security responsibilities

Customers should protect vouchers, order references, email accounts and other access credentials; keep their own devices updated; and use reputable services and encrypted websites when entering sensitive information.

Suspected misuse, account issues or security concerns can be reported through SkyDibia Support.

Pending legal review

7. Incident, disclosure and evidence-retention wording

The final standard public wording for incident notification, external disclosure, law-enforcement handling, evidence-retention periods and escalation procedures remains pending qualified legal review.

Contact

Questions or support

For customer, operational or policy questions, contact support@skydibia.com or use SkyDibia Support.