Privacy Policy

1. Scope

This policy applies to FORGEX DevStudio and its currently available browser-based features. Future cloud workspaces, account storage, or additional integrations may require changes to this policy before they are released.

2. Source Code and Local Workspaces

When you import files or folders, their contents are loaded into the FORGEX browser workspace. Editing, local inspection, and supported static analysis can operate within the browser.

Workspace drafts, file contents, baseline data, and related settings may be stored in your browser to support recovery. This storage is associated with your browser and device.

Optional connected features may transmit selected information when you explicitly request the corresponding operation. Avoid adding passwords, private keys, or other secrets to files you import.

3. GitHub Integration

If you connect GitHub, FORGEX may access account information, authorized repositories, file contents, branches, commits, and pull request information needed for the operations you choose.

Repository import and publishing may involve communication between the FORGEX server and GitHub. Publishing changes requires explicit confirmation in the application. You can revoke application access through your GitHub account settings.

4. External API Requests

FORGEX supports selected optional API requests from its Preview environment.

• Gemini AI: prompts that you approve may be transmitted to the configured AI provider to generate a response.
• Open-Meteo: approved weather requests may send latitude and longitude values to the weather provider.
• GitHub: connected workflows exchange information with GitHub to perform requested repository operations.

External providers process information according to their own terms and privacy practices. Do not submit sensitive information through an AI prompt unless you understand and accept the consequences.

5. Browser Storage, Sessions, and Logs

FORGEX may use browser storage for workspace recovery, editor preferences, and workflow state. Authentication features may use session cookies.

Servers and hosting services may process technical request information for operation, troubleshooting, and security. The precise logging configuration and retention periods must be confirmed before public production release.

6. Data Retention and Your Choices

Browser-stored workspace data may remain until you clear the relevant site data, the application replaces it, or the browser removes it.

You can export a project backup and clear local browser data when appropriate. Clearing browser data may permanently remove unsaved work.

Information processed by external services, including GitHub, Gemini, and Open-Meteo, is subject to their applicable retention practices. Disconnecting GitHub does not automatically delete previously created commits or pull requests.

7. Security

FORGEX is designed with permission-controlled connected workflows and restricted preview behavior. However, no online service or browser storage system can guarantee absolute security.

Do not treat the local workspace as an encrypted secrets vault. You remain responsible for safeguarding sensitive source code and credentials.

8. International Processing

Optional external providers and hosting services may process information outside your country. The applicable processing locations and contractual safeguards must be reviewed as part of production readiness.

9. Changes to This Policy

This policy may be updated when FORGEX introduces new functionality, changes its data handling, or adopts additional integrations. Significant changes should be communicated through the service.

10. Privacy Contact

For privacy questions or data-related requests, contact braxtonbruzzzy@gmail.com.