Privacy

Privacy Policy

How Yukab handles account, security, hosting, and iOS application information.

Effective August 12, 2026Last updated August 12, 2026

1. Scope

This Privacy Policy explains how Yukab processes information when authorized users access Yukab Panel, the Yukab iOS application, widgets, hosted-server management features, and related support or security functions. It applies to Yukab-operated services unless a separate written agreement expressly provides otherwise.

2. Information Yukab may process

Depending on the features you use, Yukab may process:

Account information: email address, account identifier, role and access assignments, account status, app-tester designation and expiration, and security settings.
Authentication and security information: password hashes, two-factor authentication configuration, recovery/security state, session records, login-failure information, IP-derived security information, user-agent/device information, and security/audit events.
Hosting and operational information: VPS and server names, domains, deployment metadata, application files and content you choose to host, managed database information, environment configuration, backups, task definitions, logs, monitoring data, resource usage, migration state, and network-management settings.
Support information: information you provide when requesting help, reporting a problem, or communicating about an account or service.

Yukab does not need or request biometric templates. On Apple devices, Face ID, Touch ID, or device-passcode verification is performed by Apple’s LocalAuthentication framework and Yukab receives only the authentication result.

3. How information is used

Yukab may use information to provide and secure the service; authenticate users; enforce account and server permissions; deploy, operate, back up, migrate, monitor, and troubleshoot workloads; prevent abuse; investigate failures or security events; maintain administrative records; respond to support requests; and comply with applicable legal obligations.

Yukab is not designed to sell personal information or use personal information for third-party behavioral advertising.

4. iOS application and cookies

The Yukab iOS application uses Apple’s WKWebView to display the authenticated Yukab Panel. WebKit may store Yukab website cookies and related website data on the device so a user can remain signed in according to Yukab’s server-side session policy. The application also uses a native privacy shield and device-owner authentication to limit local access when the app is reopened.

5. Widgets

The Yukab Status widget checks Yukab’s public health endpoint. It may store a small, non-secret health snapshot in an Apple App Group shared by the app and widget, including online/offline state, status text, release/version text when available, and the time checked. The widget is not given the WKWebView authentication cookie, Yukab password, two-factor secret, or server-management credentials.

6. Sharing and service providers

Yukab may disclose information to infrastructure, hosting, DNS, certificate, platform-distribution, or other service providers only as reasonably necessary to operate, secure, or support the service; when you direct or authorize the disclosure; in connection with a transfer or reorganization of the service; or when disclosure is reasonably necessary to comply with law, protect rights or safety, investigate abuse, or secure Yukab systems.

Service providers may process information under their own legally applicable terms and privacy obligations. Yukab does not authorize service providers to use Yukab data for unrelated third-party advertising.

7. Retention

Retention depends on the type of information and operational need. Account and hosting data may be retained while the applicable account, server, backup, or service remains active and for a reasonable period needed for security, recovery, dispute resolution, or legal obligations. Short-lived operational artifacts are removed as workflows complete or expire. Yukab’s current administrative audit-log design uses rolling retention rather than permanent storage.

Backups and hosted content can persist until they are deleted, expire under configured retention, or the associated service is removed. Users and administrators should not rely on Yukab as the sole copy of important data.

8. Account deletion and privacy choices

Users can initiate permanent account deletion from My Account → Account deletion. The request is recorded for review by an authorized Panel Administrator; the account remains usable until the request is completed. A pending request can be withdrawn from My Account before deletion is completed.

When an administrator completes deletion, Yukab is designed to revoke login access and remove or invalidate the account’s identifiable login email, sessions, two-factor/recovery state, push subscriptions, and access assignments. Yukab may retain an anonymous internal account identifier in historical records when needed to preserve database integrity, security history, or operational records.

For access, correction, deletion, or another privacy question, use the in-product controls where available or contact hello@veltar.net. Requests may be limited where retention or processing is required for security, legal obligations, fraud prevention, dispute resolution, or the rights of others.

9. Security

Yukab uses technical and organizational safeguards intended to protect accounts, credentials, hosted workloads, and control-plane information. These safeguards include scoped authorization, session controls, encrypted transport, hardened service boundaries, and security logging. No system can guarantee absolute security.

If you believe an account or server has been compromised, stop using the affected credentials and contact support promptly.

10. Children

Yukab is a hosting-management service for authorized users and is not directed to children under 13. Do not provide Yukab accounts to anyone who is not authorized to manage the applicable infrastructure.

11. Changes to this Privacy Policy

Yukab may revise this Privacy Policy at any time. Unless a later effective date is stated, a revised policy becomes effective when it is posted at this URL. Yukab is not obligated to provide individualized or advance notice of a change, except where applicable law requires notice, consent, or another specific procedure. Where applicable law requires consent for a new use of information, Yukab will seek that consent before relying on the new use.

The “Last updated” date may be changed when this policy is revised. Continued use of Yukab after a revision takes effect constitutes acknowledgment of the revised policy to the extent permitted by applicable law.

12. Contact

For privacy or support questions, email hello@veltar.net. Account-specific requests may also be directed to the Yukab administrator that issued your account.