Reference · 7 min read
Privacy, data, and licensing
Understand local execution, service processing, connected accounts, and Gyroscape's proprietary license.
On this page
Gyroscape is proprietary
Gyroscape is proprietary software. It is not an open-source distribution, and these guides explain product use rather than granting access to, modification of, or redistribution rights for source code.
Use is governed by the account plan, license terms, Terms of Service, and applicable organization agreement. Internal implementation names are not separate user-facing products.
What runs locally
Project file access, terminal commands, local previews, and desktop UI execution occur on the device within app permissions. Adding a project does not require uploading the entire repository.
Prompt text, selected file context, tool results, and conversation state needed for a response are processed through Gyroscape's service and infrastructure used for the selected model. Do not include prohibited data.
Connected accounts and browser data
Browser profiles and connector credentials can access external systems. Separate profiles by purpose, review scopes, and remove access when no longer needed. Remote side effects remain controlled by permissions.
Your project remains yours
Gyroscape edits selected local files and does not take ownership of the repository. You are responsible for backups, source-control policy, third-party licenses, and reviewing changes before release.
Binding terms
This guide is not a replacement for the current Privacy Policy, Terms of Service, license, or enterprise agreement. Refer to this site's legal pages for binding terms.
Related articles