Effective 16 September 2026
OpenShare does not collect, transmit, share or sell your personal data. There is no account, no analytics, no advertising identifier, and no server that ever holds a file you send. This is not a promise about how carefully data is handled — it is a description of an app that has no way to send data anywhere.
The app collects nothing. Its privacy manifest declares no collected data types and no tracking, and that manifest is checked against the source code by an automated test rather than filled in by hand.
There is no account to create, nothing to sign in to, and no identifier that follows you between sessions or devices.
A transfer is the file itself, turned into animated QR codes on one screen or into sound from one speaker, and read back by the other device's camera or microphone.
There is no upload, no relay and no cloud copy. In this version the app makes no transfer-related network request of any kind — a transfer works with both devices in airplane mode, which is the simplest way to see for yourself that nothing is being sent anywhere.
Camera — only to receive by QR. Frames are decoded on the device as they arrive and discarded. Nothing is recorded, saved or uploaded.
Microphone — only to receive by sound. Audio is decoded as it arrives and discarded. No recording is kept.
Sending needs neither. The app does not ask for location, contacts access, health data, or tracking permission, and it contains no advertising or analytics SDK.
Choosing a photo, a file or a contact to send uses Apple's own pickers, which run outside the app and hand over only the one item you picked — so the app never gains access to your library, your files or your address book.
Files you receive are saved in the app so you can open, share or delete them. The app also keeps a short history of recent transfers — file names, sizes, times and outcomes — capped at 100 entries.
All of it is stored locally, in the app's own container. Deleting a file deletes it from the device, and Settings can clear the whole library and the whole history at once. Removing the app removes everything with it.
The app reads file modification times while it is copying and verifying a file. That is the only "required reason" API it uses, declared in its privacy manifest, and it exists to detect a file being rewritten underneath a transfer — not to profile anything.
A received file appears only after its whole-file SHA-256 digest matches what the sender published. Nothing is opened, executed or previewed automatically.
The sending page reads, hashes and encodes your file entirely in your browser, using the browser's own APIs. The file is never uploaded: the page has no upload endpoint and the server that serves it never receives file contents, file names or anything you paste.
Loading the page is an ordinary web request, and like any website it is served by a web server that may keep standard access logs of the request for the page itself. There are no cookies, no trackers and no third-party scripts on it.
The app collects no personal data from anyone, which includes children.
If what the app does with data ever changes, this page and the App Store privacy labels are updated together, and the effective date above changes with them.
Questions about this policy: dev@vuba.one
An idea, or something that broke. Both are useful.