Files and local development
Arya Code reads the project folders and files you open. Editor preferences, recent-project information, extension state and logs can be stored in your user profile on this computer. The built-in native Arya compiler, language server and formatter run on your computer.
Running a script, package manager, debugger or project server executes the selected tools with your account’s permissions. Those tools, your project code and installed extensions can access files and make their own network requests. Review workspace trust and the extensions you install before running unfamiliar code.
Telemetry and network connections
The Arya Code 2.0 product configuration disables core telemetry, supplies no application-update endpoint, and disables the built-in AI/chat features by default. These settings do not describe every extension, runtime or program you may choose to run.
Browsing and downloading extensions contacts Open VSX. Git operations can contact your configured remotes. Package installation and runtime setup can contact package registries and the selected tool providers. Opening documentation, support links or release downloads contacts the portfolio, GitHub or the service named in the link. These services receive the network information needed to handle a request and apply their own privacy practices.
Optional Google sign-in
Google sign-in is optional. If you configure your own Google Desktop OAuth client and choose to sign in, consent takes place in your external browser. The provider requests only openid, email and profile scopes, verifies the returned identity, and stores the account identifier, email label and OAuth tokens through the editor’s machine-local SecretStorage. The OAuth client configuration is stored there too, rather than in project settings.
An extension that you authorize to use this authentication provider can receive an access token. Refreshing a requested session and revoking a grant contact Google. Sign out removes the local session and attempts to revoke its grant; Remove configuration also removes the saved OAuth client configuration. If revocation cannot complete, review the grant in your Google Account connections.
Local servers, credentials and logs
The managed Live Server, PHP, database and administration services bind to the loopback interface on your computer. The applications you serve can still make outbound requests. Local database files remain in per-user storage after servers stop, so a later session can reuse them. Database credentials use the editor’s secure secret storage.
Compiler, terminal and service output can contain file paths, request information and text produced by your application. Review logs before sharing them with support, and remove passwords, tokens and unrelated private information. Installed extensions can maintain their own logs and storage.
Your controls and support requests
Use workspace trust to control project execution, review or disable extensions, and use the Google sign-out and configuration-removal commands for account data. Local preferences, caches, logs and project databases have separate lifetimes; uninstalling the application does not necessarily remove its user profile or your project files.
If you choose to send Hamza Arya a support request, the contact details, message and attachments you provide are handled through the channel you select to respond to the request and investigate the issue. This notice covers the first-party Arya Code desktop application; hosting providers, Google, GitHub, extension publishers and other tools have their own services and policies.
Contact and changes
For privacy questions or information you have sent through support, contact Hamza Arya. This notice may be revised as the application’s features change; review the notice for the version you use.
Arya Code downloads and documentation · Google Account connections