Cache Refresh
Refresh local portal rendering state.
Rebuild UI State
Re-render operational pages and account widgets.
Maintenance Mode
Backend maintenance mode is not activated by this local build.
Privacy Kept · Connection Secured.
Clean overview of your portal. Open a section when you need its full controls.
Your SafeKeep account information and current session details.
Create a SafeKeep VPN customer account. The customer uses the SafeKeep VPN mobile application.
Create a controlled reseller/dealer account.
Create an Administrator account for assigned operations.
Create an owner-side manager with delegated permissions.
VPN customers only. End Users use the SafeKeep VPN mobile application and do not access this admin website.
| Username | Device | Device ID | Status | Duration | Action |
|---|---|---|---|---|---|
| No End Users created yet. | |||||
Dealer accounts responsible for their assigned customers, credits and slots.
| Username | Account ID | Status | Credits | Slots | Action |
|---|---|---|---|---|---|
| No Resellers created yet. | |||||
Operational administrators with delegated customer/support permissions.
| Username | SafeKeep ID | Status | Duration | Access | Action |
|---|---|---|---|---|---|
| No Administrators created yet. | |||||
Owner-side managers with delegated permissions. They do not outrank the Super Admin.
| Username | SafeKeep ID | Status | Access | Action |
|---|---|---|---|---|
| No Superior Administrators created yet. | ||||
End User VPN accounts created with the Trial 1 Day plan. These credentials are for the SafeKeep VPN application, not the management website.
Control advertising rules for SafeKeep VPN End User subscriptions. These settings apply to VPN-app accounts, not management-portal access.
Show ads while an End User is on the Trial 1 Day plan.
Show ads for End Users on the 1 Month plan.
Manage rewarded advertising for the SafeKeep VPN mobile app, user rewards, ad-network configuration and revenue reporting.
Manage networks that can be published to the SafeKeep VPN app.
Manage SafeKeep VPN servers, connection settings, monitoring and maintenance.
Configure DNS servers used by SafeKeep VPN profiles.
Control SafeKeep VPN application release settings. This does not modify application source code.
Create a notification payload for the SafeKeep application.
Set the notice shown when users open SafeKeep VPN.
Prepare and validate the configuration payload used by SafeKeep VPN. Saving JSON does not directly change the production app.
Manage published SafeKeep service information shown to supported clients.
Manage published information.
Audit and activity logs for SafeKeep administrative activity.
Configure SafeKeep portal API settings for local testing. Production secrets should remain on the backend.
/accounts/servers/vpn/control/protocols/notificationsRuntime protocol selection layer used by SafeKeep VPN Control. The test build stores state locally; production enforcement belongs to the VPN backend.
Manage the protocol profiles available to SafeKeep servers and VPN Control. Changes are stored locally in this test build.
Local deployment checklist and service health view for SafeKeep testing.
Build a local test configuration preview from the selected protocol profile.
No configuration generated yet.
Current browser/device information used for SafeKeep test-session visibility.
SafeKeep VPN privacy notice for the website, administration panel and related service operations. This is a product draft and must be aligned with the production backend, actual data flows and applicable law before publication.
To provide and secure accounts, operate the VPN service, manage subscriptions/renewals and credits, prevent misuse, investigate security events, provide support, maintain service reliability and meet applicable legal obligations.
SafeKeep should not collect information merely because it is technically available. The production implementation should document each data category, purpose, retention period and access role.
Information may be shared with hosting, infrastructure, payment, communications or security providers only where required for the service and subject to appropriate contractual and security controls. Do not claim that data is never shared until the production provider list is finalized.
Use access controls, secure authentication, encryption in transit, protected credential storage, audit logging and least-privilege administration. Passwords must never be stored as plain text.
Retention periods must be defined from actual operational and legal requirements. Do not promise automatic deletion periods until the backend implements them.
Provide a clear process for applicable access, correction, deletion, objection or other privacy requests. The final policy should identify the responsible privacy contact and applicable jurisdiction.
Describe only cookies, analytics and tracking that are actually deployed. If none are used, the production policy should say so rather than copying a generic cookie statement.
The final policy should state the intended minimum age and how the service handles information relating to children, consistent with applicable law.
Material changes should be reflected in the published policy with an updated effective/revision date and an appropriate notice method. Privacy contact details must be added before publication.
You are responsible for protecting your credentials and for activity performed through your account. SafeKeep IDs and usernames must not be shared in a way that compromises account security.
Accounts can have an expiry date. An expired account may be suspended until an authorized renewal is completed. Renewal periods, permissions and credit charges depend on the account role and the production service rules.
Credits are service balances used for supported account operations. Only the Super Admin has unlimited credits. Transfers and credit-consuming actions should be recorded in the service history.
SafeKeep IDs identify accounts. Users must protect credentials and devices. Blocked IDs may require an authorized unblock process and, where applicable, a credit charge.
The VPN must not be used to facilitate unlawful activity, unauthorized access, fraud, malware distribution, abuse of networks, or interference with systems or services. South African law includes provisions addressing unauthorized access and interference with data and systems.
Availability can depend on server health, maintenance, network conditions, upstream providers and other technical factors. No uninterrupted availability should be promised unless the production service contract expressly provides it.
SafeKeep may update features, servers, security controls, account rules and documentation. Material changes should be communicated through the official update channel or other appropriate notice.
Accounts may be suspended for expiry, security restrictions, misuse, fraud or other documented service reasons. Suspension reasons should be recorded internally and users should receive appropriate notice where required.
Personal information is handled according to the final SafeKeep Privacy Policy and applicable data-protection requirements. In South Africa, POPIA provides conditions for lawful processing of personal information.
The final production flow should present the current Terms of Use and require acceptance where legally or operationally appropriate.
This area records important SafeKeep policy, security, server, account and application updates.
Effective Date: September 27, 2026 • Last Updated: September 27, 2026
This Acceptable Use Policy establishes rules for responsible use of SafeKeep VPN and helps protect users, the SafeKeep network, servers and connected services.
This policy applies to SafeKeep VPN accounts, VPN connections, applications, portal users, administrators, resellers, servers, networks and related services.
Users may use SafeKeep VPN for lawful activities, privacy and security, ordinary internet access, work, education, communication and other purposes permitted by the applicable Terms of Use.
Do not use SafeKeep to gain unauthorized access to accounts, devices, servers, applications, networks or data.
Do not use the service for fraud, impersonation, credential theft, deceptive activity or unauthorized financial transactions.
Do not disrupt, overload, scan, attack or interfere with networks, servers or services without authorization.
Do not use SafeKeep to knowingly infringe copyrights, trademarks or other intellectual-property rights.
Do not use SafeKeep to distribute or facilitate content or activity that is unlawful under applicable law.
Users are responsible for protecting usernames, passwords, SafeKeep IDs and connected devices. Do not share credentials in a way that compromises account security. Report suspected unauthorized access promptly.
Users must not attempt to bypass security controls, abuse infrastructure, introduce malicious software, or interfere with SafeKeep services. Administrative access must be used only for authorized duties.
SafeKeep may depend on hosting, payment, communications, network, DNS and other third-party services. Their own terms and policies may also apply.
Suspected abuse, security incidents or unauthorized activity should be reported through the official SafeKeep support channel with enough information for investigation.
SafeKeep may investigate documented violations and, where permitted and appropriate, restrict, suspend or terminate access. Actions should be based on the applicable service rules and documented security or abuse findings.
Information related to security, account administration and abuse reports should be handled according to the SafeKeep Privacy Policy and applicable data-protection requirements.
SafeKeep VPN must not be used as a means to circumvent applicable legal obligations, lawful restrictions or authorized security measures.
SafeKeep may update this policy as the service, security controls, legal requirements or operational practices change. Material changes should be reflected by an updated revision or effective date.
This policy forms part of the SafeKeep service rules and should be read together with the Terms of Use, Privacy Policy and other applicable service documentation.
If a provision of this policy is found unenforceable or invalid, the remaining provisions should continue to the extent permitted by applicable law.
For acceptable-use questions or abuse reports, use the official SafeKeep support channels published in the portal. Contact details should be finalized and maintained by SafeKeep before production publication.
Central SafeKeep ID restriction management. Blocking permissions remain role-controlled. Any signed-in account can request an unblock when it has enough credits; the Super Admin is unlimited.
Online renewal for Reseller, Administrator and Superior Administrator accounts.
This billing system is coded and ready for online account renewal, but payments are not active yet. For now, account renewal remains unavailable from the portal.
Central security information for account access, devices, SafeKeep ID protection and security activity.
Adult-content filtering only. Normal internet access remains unaffected.
Local test session controls; production revocation requires backend enforcement.
| User | Role | Device | Server | Last Seen | Status |
|---|
Device details are shown from the current browser/session where available.
| Device | Identifier | Last Seen | State | Action |
|---|
Credits • 30-day renewal cycle
Credit • one-day trial allocation
Days • calculated against the renewal cycle
No live server telemetry is claimed unless a backend reports it.
| Server | Address | Region | State | Load |
|---|
| Time | Action | User / ID | Role | Details |
|---|
Refresh local portal rendering state.
Re-render operational pages and account widgets.
Backend maintenance mode is not activated by this local build.
LocalStorage data used by this test build, including renewal history, notification queue and portal preferences. Server-side databases are not included.
Stay connected with SafeKeep through our official support and social channels.
Portal preferences, refresh controls, security confirmations and local configuration tools.
Export or restore portal preferences stored in this browser. Account credentials and server passwords are not exported.
Local maintenance tools for this browser. These controls do not delete VPN accounts stored on a production backend.
👤 USERNAME : —
🔑 PASSWORD : —
🆔 SAFEKEEP ID : —
🛡️ TYPE : —
📲 RECOVERY NUMBER : 🇿🇦 +27 —
FINGERPRINT : Verified
📅 JOINED : —
⏳ EXPIRY : —
👑 CREATED BY : —
💳 CREDITS : 0
| Renewal Date | Account | Plan | Credits | Prev Expiry | New Expiry |
|---|
| Endpoint | Scope | Status |
|---|---|---|
| /users | users | READY |
| /servers | servers | READY |
| /notifications | notifications | READY |
| /analytics | analytics | READY |
Unified event layer connecting Authentication, Sessions, Devices, Servers, Bot Notify, Audit and Analytics.
\n\n\n