Desktop App Terms
These terms cover the UpliftOS desktop application for macOS, Windows and Linux. They are in addition to our Terms of Service, which govern the service the desktop app connects to, and our Privacy Policy, which governs the data we hold.
The desktop app is a different thing from a website, and the difference is the point of this document: it runs on your computer, with access to your computer. Section 3 says exactly what that access is.
1. Your License
We grant you a personal, non-exclusive, non-transferable, revocable license to install and run the desktop application on computers you own or control, for as long as your UpliftOS account is in good standing.
You may not redistribute it, sell it, rent it, or make it available to people outside your organization. You may not reverse-engineer, decompile or disassemble it, except where that restriction is unenforceable under the law that applies to you.
The application is ours. This license transfers nothing.
2. It Is a Client, Not the Service
The desktop application is a way to reach UpliftOS. Your account, your organization, your applications and your data live on the service, governed by the Terms of Service and the Privacy Policy. Uninstalling the desktop app does not close your account, and closing your account ends your right to use the desktop app.
Where a feature is available on the desktop and not in a browser, or the other way round, that is a product difference and not a different set of rights.
3. What the Desktop App Can Reach on Your Computer
The desktop app requests more from your machine than a web page can. Every capability below is one the application actually has. Your operating system gates several of them behind a permission prompt, and you can decline any of those — some features then stop working, which is the intended trade.
- Files you choose. The app can read files and open a file picker. It reads what you point it at; it does not sweep your disk.
- Local code repositories. If you connect a repository on your own machine, the app reads it, runs git against it, and keeps a local record of the repositories and checkpoints you have connected.
- A terminal. The app can start interactive terminal sessions and run commands on your computer, because that is how it builds and runs projects locally. Commands run as you, with your permissions.
- Screen and window capture, including system audio. For recording and sharing what is on your screen. This is off unless you start it, and macOS and Windows require you to grant screen-recording permission before it can begin.
- Your microphone, for voice and calls. Off unless you start it, and gated by an operating-system permission.
- System notifications, so the app can tell you something happened while it is in the background.
- Starting at login, which you turn on and off yourself. It is not on by default.
- Network access to our service and to hosts you ask it to reach, including local addresses on your own machine when you are running a project locally.
- The upliftos:// link handler, so links can open the right screen in the app.
We do not sweep, index or upload the contents of your computer. What leaves your machine is what a feature you used needs in order to work — the repository you connected, the screen you chose to record, the audio of a call you joined. The Privacy Policy governs what we then do with it, and App Ownership & License governs who owns it, which is you.
4. Where Your Sign-In Token Is Kept
Signing in stores a token on your computer so you do not sign in again every time. We would rather tell you exactly where it is than describe it vaguely.
It is written to a file in your user application-support directory, with permissions set so that only your user account can read it. It is not stored in your operating system's keychain today. Anyone with administrative access to your computer, or the ability to read your user account's files, can read it — the same as any other credential file on your machine.
Signing out removes it. If you believe a computer holding your token has been lost or compromised, sign out of that device and change your password.
5. Updates
The desktop app updates itself, and it asks first. When an update is available the app tells you and you choose when to take it.
Updates are cryptographically signed and the app verifies that signature before installing anything. An update that does not verify is not installed. We distribute them from our own release storage, over HTTPS, per platform — so a release on one platform does not move the version on another.
We may stop supporting older versions. A version too old to talk to the current service will tell you to update rather than failing quietly.
6. Third-Party and Open-Source Components
The desktop app includes open-source components, each under its own license. Those licenses govern those components, and nothing here restricts a right they grant you. Where a component's license requires that we make its source or its notices available, we do.
7. Provided As-Is, and Where the Limits Sit
The desktop app is provided as-is. We do not warrant that it is free of defects, compatible with every configuration, or uninterrupted.
Because it runs commands and builds projects on your computer, you are responsible for what you run through it and for the state of the machine you run it on. Keep backups of local work. A failed build, a command you ran, or a repository operation that did not go the way you intended is not something we can undo for you.
Our liability is limited as set out in the Terms of Service. Nothing here excludes liability that cannot lawfully be excluded, and nothing here reduces rights that consumer law gives you and does not let you waive.
8. Ending It
You may stop using the desktop app at any time by uninstalling it. Uninstalling removes the application; it does not delete your account or the data held on the service. Data Rights covers deleting that.
We may suspend or end your license to the desktop app if your UpliftOS account ends or if you use the app in breach of these terms or the Acceptable Use Policy.
9. Changes to These Terms
We update these terms as the desktop app changes. Material changes are notified as the Terms of Service requires, and the date at the top always reflects the current version.
Questions: [email protected].
10. Related Documents
- Terms of Service — the agreement behind the account
- Privacy Policy — what we hold and why
- App Ownership & License — who owns what you build
- Mobile App EULA — the same relationship on iOS and Android
- Acceptable Use Policy — what may not be run