1. Who this policy is from
UniConn is software published by its developer, rohansen856 (“we”, “us”), an individual based in India. You can reach us at support@uniconn.live. This policy covers the UniConn app for Android, Linux and Windows, and this website.
2. In short
- Every device signs in to a UniConn account with your Google account. Our server keeps your Google account's identifier and email address, and which devices are on your account and when each last checked in, and it passes along only encrypted traffic it cannot read. On the same network your devices talk directly, and we run nothing they pass through.
- While UniConn is in beta, the app sends crash reports to Sentry and counts of which features are used to PostHog, with your account's email so a problem can be followed up, and on Android, only if you turn it on in Settings, a recording of the app's screens with every text and picture hidden; the app from Google Play never records. Never what your devices share. It collects no advertising identifiers and shows no ads.
- UniConn uses no artificial intelligence of its own and sends nothing to an AI service. Coding sessions show on your phone the Claude Code or Codex you run on your own computer, under your own account with them.
- What you share moves only between your own devices, on your account and allowed by you, end-to-end encrypted, over your own network, directly across the internet, or through UniConn's relay.
- This website sets no cookies and runs no analytics. Its host keeps ordinary request logs, and the download count adds one per file delivered, keeping nothing about who.
3. The UniConn app
What we receive
What our server keeps to run your account, described below under the UniConn account, and while UniConn is in beta, its crash reports and usage counts, described next. Nothing else: what you copy, send, play or show goes between your devices, never to us in a form we can read.
Crash reports and usage during the beta
While UniConn is in beta, the app reports problems and use, so they can be found and fixed:
- To Sentry: when the app crashes or an error happens, what went wrong and where in the code, the app's version, your device's model and system, and which page was open. On a computer, also the last crash of UniConn's background service.
- To PostHog: that the app was opened, which pages are shown, and which features are used, such as a file offered or the webcam started, with counts and kinds only, and when a sign-in fails, why, in the words of the step that failed. On Android, and only if you turn on Settings › Privacy › Record screens for bug reports, a recording of the app's own screens with every text, picture and field hidden, which shows where things are, not what they say; other apps are never recorded, and turning it off stops it at once. The app from Google Play offers no recording at all.
- Both name you by your UniConn account's email while you are signed in, so we can follow a problem up with you. On Android, both also say how the app was installed, such as from Firebase's tester app or from our own computer, so our testing can be told apart from yours. Before a report goes to Sentry, the app removes file paths and any other email address.
- Never: what you copy, what is in the files you send, messages, or what a camera or a shared screen shows.
- Your devices also tell our server which version of the app they run, kept on each device's entry with your account. Our server reports its own failures to Sentry too, naming what failed, never you.
Sentry and PostHog handle these under their own privacy policies (Sentry, PostHog). They end with the beta. To have yours deleted, write to support@uniconn.live.
Coding sessions
A coding session is Claude Code or Codex running on your own computer, which you installed and signed in to with Anthropic or OpenAI yourself. UniConn shows its screen on your phone and carries what you type back, end-to-end encrypted between your two devices, through no server of ours that could read it. What you send to that tool goes to its maker under your account with them, and their terms and privacy policy apply to it, not ours. UniConn itself uses no artificial intelligence and sends nothing to any AI service.
What stays on your devices
Each device keeps, on itself only:
- An encrypted vault holding its keys, its pairings, the permissions you gave each paired device, and its settings. The vault is encrypted with a key held by the system: the Android Keystore on the phone, the Secret Service keyring on Linux, Credential Manager on Windows.
- Clipboard history. An ordinary entry expires after two hours. An entry marked sensitive, such as a password, is never stored and is gone after one minute. A copied image is kept in the app's cache, the five most recent each way. Copies from your other device are placed on this device's own clipboard, where other apps on it can read them as they can any copy; the phone can turn this off.
- Files you accept, saved where you choose. Nothing is saved without your accepting it.
- Screenshots you take from the phone's screen window on the laptop, saved to the laptop's Pictures folder.
The phone's camera, its screen, its microphone and the laptop's audio are streamed live and never recorded by UniConn.
What your paired devices learn about each other
To show and reach each other, paired devices share with each other, and with no one else:
- each device's name, its platform, and a key derived from its hardware so a reinstalled device is recognised;
- whether it is awake, its battery level and whether it is charging, and whether its connection is metered;
- whether it is signed in to the UniConn network, and, if you use Tailscale, its address there;
- the permissions each has given the other.
Permissions on the phone
- Notifications, to stay reachable in the background and to ask you about requests.
- Camera, to lend the camera as the laptop's webcam, which you approve each time.
- Microphone, to lend the microphone to the laptop, which you approve each time. Android shows that it is in use, and UniConn shows a notification with Stop.
- Nearby devices, to pair with the laptop as a Bluetooth speaker, and to hear a laptop that has lost its internet ask for the hotspot. That listening never works out where you are.
- Your fingerprint or face, which Android checks itself each time you unlock the laptop. UniConn never sees it; it only learns that Android accepted it.
- Screen capture, which Android asks you for each time the laptop is shown the screen, and accessibility access, which you switch on only for a session in which the laptop may tap and type, and which switches itself off afterwards. UniConn's accessibility service listens to nothing and reads no window.
Refusing a permission switches off only the feature that needs it.
Removing your data
Forgetting a device, on its page under Devices, removes everything that referred to it. Erase UniConn on this device, in Settings, destroys the vault's key, which makes everything in it unreadable. Uninstalling the app removes it and its data from that device, except on Windows, where uninstalling asks whether to delete the laptop's encrypted vault too, and keeps it for a reinstall unless you say yes. None of this is held by us; your account is deleted as described below.
The UniConn account
Every device signs in to your UniConn account with your Google account; it is how your devices know they belong together. Our server keeps the identifier Google gives your account and its email address, and when you last signed in with them (never a password, and no Google token, on the server or on your devices), an identifier for the account that carries nothing about you, which devices are on the account by their keys and what kind each is, when each was added and until when it counts as checked in (moved on at each daily check-in and written to the hour), which devices paused after a week without checking in and which you removed, how many relayed connections your account opened this month and today, and a log of any change an administrator makes to your account. It tells each of your devices which others are on the account, by key and kind, never by name. Like any relay it sees the addresses your devices connect from, when they are connected, and how much passes between them.
It never sees what you share. Everything between your devices is end-to-end encrypted, and the server holds no key that opens it; on the same network, and whenever a direct connection is possible, it is not used at all. A device you remove keeps no way back: its key is refused at sign-in.
Signing in with Google tells Google that you signed in to UniConn, and gives it a one-time value made from your device's key that reveals nothing about it. We ask Google for your account's identifier and email address and nothing else. Whoever controls your Google account can sign a device in, though it can join yours only after you tap Allow on one of them: protect your Google account with two-step verification.
Deleting your account. In the app, open Settings › Account and, at the bottom, Delete account, then choose your Google account to confirm it is you. Any Plus subscription is cancelled at Razorpay first, so nothing more is charged; then the account, its devices, its plan and its checkouts are deleted at once, and every device is signed out. Without the app, write to support@uniconn.live from the account's email. What is kept afterwards, and for how long, is on deleting your account.
How long it is kept
- Your account and its devices: until you delete the account, or remove a device.
- A device that has not checked in for a week is paused, and stays on the account until you remove it.
- Relayed connections counted for the plan: this month's and today's, then they are replaced.
- Records of payments: as long as Indian tax law requires, up to eight years, no longer linked to you once the account is deleted.
- The administrators' log: a line for each change made to an account; a deleted account's line keeps its random identifier, not its email.
- Crash reports and usage counts: until the beta ends, or sooner if you ask.
- Email you send us: until it is no longer needed to answer you.
Paying for Plus
If you buy Plus, Razorpay processes the payment: it learns your email address, your phone number and the UPI account or card you pay with, and that the payment is for UniConn Plus. On Android its checkout runs inside the app while you pay. Razorpay handles these under its privacy policy. The app from Google Play sells nothing: it shows your plan, and Plus is bought elsewhere, such as on the Plus page at network.uniconn.live/plus. There you sign in with Google, which tells Google you signed in to it, and the page keeps one cookie, a random session number that lasts 30 minutes, for that and nothing else; Razorpay takes the payment on its own page. Our server keeps Razorpay's references to your subscription and payments, the price, the amounts, dates and states, and whether you paid by UPI or card; never your card number, UPI address or phone number. We tell Razorpay an identifier for your account, never your email. Records of payments are kept as accounting law requires, even after your account is deleted, with your account forgotten.
Tailscale
If you already use Tailscale, your devices can also reach each other through it, a separate service you choose to install and sign in to. UniConn's data stays end-to-end encrypted inside it. Tailscale's handling of your account and devices is covered by its own privacy policy.
4. This website
This website sets no cookies, runs no analytics or tracking, embeds nothing from third parties, and serves its fonts itself. It and the downloads (the Linux package and the Windows setup, from downloads.uniconn.live) are served by Cloudflare, which processes the technical details of each request, such as your IP address, your browser's identification and the file asked for, to deliver them and protect them from abuse. Cloudflare handles these under its privacy policy; we do not use them to identify you. Email to support@uniconn.live is received through Cloudflare's email routing.
The Android beta
While the Android app is in a closed beta it comes through Firebase App Distribution, a Google service. Joining gives Google the email address you join with, and installing through Firebase App Tester gives it your device's model and Android version and which builds you install; we see the same in its console, to know who is testing. Google handles these under Firebase's privacy and security terms. Ask us at support@uniconn.live and we remove you from it. The app itself sends Google nothing for this.
The download count
When a file is downloaded from downloads.uniconn.live, a counter adds one for that file's platform, its version and the day. That is all it keeps: not your IP address, not your browser, not where you came from, and no cookie. The totals are public, at downloads.uniconn.live/stats.json, and are the number this site shows. To keep the count honest, a burst of requests from one address is served but not counted; that address is used for this check in the moment and never stored.
5. If you write to us
If you email us, we use your address and message only to answer you, and delete them when they are no longer needed for that. Ask us at any time to delete them sooner.
6. Age
UniConn is for people 18 and over. Someone under 18 may use it only with a parent's or guardian's permission, and may not buy Plus. It is not directed at children, an account needs a Google account, and if we learn that an account belongs to a child without that permission, we delete it. This website collects personal data from no one.
7. Your rights
Under the law that applies to you, including India's Digital Personal Data Protection Act, 2023, you may ask what personal data we hold about you and ask us to correct or delete it. For the app, that is your account as described above; for it, or an email you sent us, write to support@uniconn.live.
8. Changes
If this policy changes, the new version is published here with a new date. A change that would collect anything more from you would be stated here plainly first.
9. Contact
Questions about this policy: support@uniconn.live. See also the terms of use and how UniConn is secured.