Finally ·Privacy policy

What Finally sends to Coldbricks automatically

Nothing. Finally has no Coldbricks account, analytics, advertising, crash-reporting, telemetry, or automatic diagnostic-upload service. It does not automatically send library, viewing-history, credential, accessory, or usage data to Coldbricks. The user-controlled support handoff and other user-requested network features are described below.

User-submitted support messages

If you choose Submit Bug Report, Finally creates a bounded diagnostic ZIP locally and opens an email composer or Android share sheet. Creating the ZIP sends nothing. Only if you choose a destination and press Send does that destination receive it; if you send it to coldbricks@gmail.com, Coldbricks receives the message and ZIP you chose to send.

The ZIP can contain build and device facts, library counts, allowlisted settings, bounded app events, and playback scalar/receipt facts. It excludes raw paths, URIs, filenames, server/share names, usernames, passwords, tokens, IP addresses, media bytes, arbitrary logcat, exception messages, DRM data, and decoder-initialization data.

What stays on your device

• Your media library. Finally indexes videos and images you point it at. That index (titles, file paths, playback positions, projection settings) is stored in a local database on your headset and never leaves it.
• Network-source credentials. If you configure SMB, FTP, WebDAV, Plex, or Stash, the address and credentials or access token you enter are stored locally on your device solely so the app can reconnect. They are transmitted only to the server you specify and never to Coldbricks.
• Nearby-source discovery. When you choose Find nearby sources, Finally listens for SMB hosts and DLNA/UPnP media servers on your local network. Device names, service names, and local addresses are used on your headset to show the picker; they are not sent to Coldbricks.
• Watch Together. When you explicitly host or join a room, Finally advertises or discovers a service on your private LAN and creates a direct encrypted connection between the two headsets. The peers exchange pairing and playback-session data plus an identity for the selected media. Finally does not upload or relay the media, and Coldbricks receives no room data.
• Optional Bluetooth haptic accessories. If you open the Haptic Control Panel and enable accessory support, Finally can scan for and connect directly to a nearby Bluetooth accessory. Scan results, device identifiers, connection state, and matching .funscript timing remain on your headset and are not sent to Coldbricks. The controls require explicit arming and provide an immediate stop action.
• Optional The Handy service. If you choose Connect The Handy, Finally contacts HandyFeeling, operated by Ohdoki AS, as described below. A verified key is stored encrypted on the headset until you choose Forget Handy key or uninstall.
• Settings. Playback and display preferences are stored locally.

Uninstalling the app deletes Finally’s local database, settings, and saved credentials. It cannot delete records retained by a media server, platform, or third-party service you chose to contact.

Network access

Finally uses the network only to do what you ask it to: discover local media servers, stream media from sources you configure, verify Meta entitlement in a Meta store build, connect two headsets for Watch Together, or control The Handy through HandyFeeling after an explicit connect action. It does not connect to a Coldbricks telemetry, advertising, account, update, or content service.

Some source protocols can be unencrypted if you choose them (for example, plain FTP or an HTTP server on a trusted LAN). Finally labels those choices and does not turn them into Internet-facing services. Watch Together uses TLS.

Optional Bluetooth accessory discovery and control are direct, local device operations. They do not use a Coldbricks service or transmit accessory data to us.

The Handy / HandyFeeling

If you choose Connect The Handy, Finally contacts HandyFeeling, operated by Ohdoki AS, over HTTPS to control the device. Connect sends the Handy connection key, source IP address and normal network-request metadata, connection/status checks, device-setup requests, and a rest-position command. Connect can physically reposition The Handy before ARM; keep clear. While connected and ARMED, script playback or TEST sends motion target position and duration. STOP or disconnect can send mode and stop commands even when not armed.

During script playback, motion values and command cadence are derived on the headset from the local .funscript. Firmware-4-and-newer requests also include Finally’s registered application ID.

Finally does not send the media title, media path, video, or raw .funscript file to HandyFeeling, and Coldbricks receives none of these requests.

A verified connection key is stored encrypted on the headset until you choose Forget Handy key or uninstall. Ohdoki’s current policy says that logs scramble connection keys and IP addresses and are deleted by default after seven days. See The Handy privacy policy for its current retention, deletion-request, and contact terms. Forget Handy key removes Finally’s local copy; it is not a request to delete Ohdoki’s server records.

On an upgrade from a build before 1.0.1, if Android secure storage is temporarily unavailable, the older local key copy can remain dormant until a later encrypted migration succeeds. Finally does not use that dormant copy to connect. It is removed after migration, by Forget Handy key, or by uninstalling the app.

Optional website support

The web field manual may offer optional support links to PayPal, Cash App, or Venmo. Following one leaves finallyvr.com. Those services—not the Finally app—process any contribution, and their terms and privacy practices apply. The app never receives payment credentials.

Platform services

On Meta Quest, store builds perform a one-time entitlement verification at launch through the Meta Platform SDK, which confirms with Meta that your account owns the app. That check is operated by Meta and governed by Meta’s privacy policy. We receive nothing from it beyond a pass/fail result inside the app.

Children

Finally is a general-purpose utility intended for adult users. It is not directed at children and provides no content of its own.

Changes

If a future version of the app ever changes any of the above (for example, adding optional crash reporting), this policy will be updated first and the change will be called out in release notes.

Contact

Questions: coldbricks@gmail.com