Let’s fill in the details.

No public BiTTU gateway fleet is deployed. Use your own reachable WireGuard gateway and valid profile if you want to test a real connection.

No. A device VPN needs a native client, platform permission, a real gateway and a valid configuration.

It builds a practical checklist from your platform, gateway and profile choices. It does not create a tunnel or collect a private key.

A unique key pair and peer configuration for each device makes ownership and revocation clearer. The operator must configure the real gateway peers.

It is a separate test candidate. Startup checks on APIs 28 and 35 passed, while actual installation, native WireGuard and live tunnel tests remain pending.

The Mac deliverable is DMG only. A signed and notarized production DMG still needs a real Apple build environment, owner signing credentials and device tests.

The repaired x64 and arm64 source builds compile. Native installation, signing, startup and live tunnel validation are still required before a production installer is offered.

An official WireGuard client can use your own valid profile. The custom BiTTU iOS app remains in preparation.

That depends on the router model and firmware. Check its vendor documentation before using a supported configuration path.

A web page cannot supply the native packet tunnel capability needed for a device VPN. The custom iOS app requires Apple development and distribution steps.

No. They are country and territory reference records, separated from actual gateway registry and agent-report counts.

A registered agent reported an active local interface and a peer count. It does not verify a customer handshake, internet egress, DNS or speed.

Its actual internet exit depends on the gateway’s network. A country preference in a website request does not move the gateway.

Check the public endpoint, UDP port, router and host firewalls, server availability and matching public keys. Carrier-grade NAT can prevent inbound reachability.

No. It is an interactive brand and reference visualization, built with public-domain land geometry. It does not show user traffic or live server coverage.

No. Actual results depend on the client, gateway, routes, networks and workload. The project does not publish invented performance measurements.

No. Device requests ask for a public key. Keep private keys, passwords and complete profiles out of support messages.

Account API queries filter device and support records by the authenticated owner. Operator access requires the server-side allowlist.

The operator saves a reply in the request, and you can read it in your account. Email delivery and a support response-time commitment are not active.

No independent audit or certified no-logs claim is currently made. Policies are original prelaunch drafts reflecting the project’s actual state.

Sign in, open My requests and choose Data request. Submission records the request for review; it does not automatically erase gateway or hosting records.

The eight company addresses are planned. Website DNS and HTTPS are active, while actual mailbox provisioning, sender verification and delivery remain separate tasks.

Checkout and recurring billing are not enabled. Plan cards are a product preview.

No. A support enquiry or device request does not collect a payment or activate a paid service.

No current paid offer or refund guarantee is advertised. Final merchant, pricing, renewal and refund terms must be completed before a commercial launch.

It describes the management foundation and launch requirements. It does not create an organization subscription or a service contract.