Skip to article
DOCS
DashboardProduct
Browse documentation
DocsPrivacy & data
COMPANY & LEGAL

AEXGrid Privacy Policy.

Effective date: 2026-09-18.

Published documentAEXGrid / Gridspawn LLC
On this page

1. Scope

This Privacy Policy explains how Gridspawn LLC (“Gridspawn,” “we,” “us,” or “our”) handles personal information when you use AEXGrid’s desktop software, websites, documentation, dashboard, hosted account and connection services, downloads, support, and updates. It does not govern independent model providers, repositories, command-line tools, or connected applications, which publish their own policies.

2. Who is responsible

Gridspawn LLC is responsible for AEXGrid information it controls. Our published mailing address is 5830 E 2ND ST STE 7000 32269, Casper, WY 82609, United States. Current privacy and support contact routes are linked from AEXGrid’s Contact page.

3. Information we handle

  • Account information, such as account identifiers, sign-in records, and information you provide when creating or managing an account.
  • Device and workspace metadata, such as device and workspace identifiers, display names, availability, application and protocol versions, operating-system information, and connection state.
  • Service and security data, such as IP address, request and connection timestamps, diagnostics, authentication events, error information, abuse signals, and operational logs.
  • Support and communications, including messages, attachments, and contact details you submit when requesting help or reporting a problem.
  • Configuration and authorization information for providers and connected applications, including the grants and identifiers needed to provide an integration.
  • Prompts, files, task data, tool requests, projections, and commands only when they are intentionally transmitted through a feature or are needed to provide support you request.

4. Information stored locally

AEXGrid stores substantial information on your device or in the workspace you choose, including workspace settings, room geometry, plans, task and manager state, launch profiles, application configuration, agent metadata, and provider-owned resume references. Plans are ordinary Markdown files in the selected workspace.

Provider credentials remain provider-owned where supported. Protected device identity uses the operating system’s credential backend where available. Custom executable arguments are stored as configuration and must not contain secrets. Local information remains subject to your operating-system account, filesystem permissions, backups, and any synchronization software you use.

5. Direct workspace connections

To connect the dashboard to a desktop workspace, discovery and connection services process the account, device, workspace, version, availability, and network metadata needed to locate and admit the host. After admission, the dashboard and host exchange the bounded workspace view and commands through a protected direct connection when available. Network relays may assist connection delivery where required by network conditions.

The dashboard is not arbitrary remote desktop access. Only the application data and commands supported by the AEXGrid protocol are exchanged. Connection metadata and operational logs may still be processed by hosted infrastructure even when application traffic is delivered directly.

6. Providers and connected applications

When you instruct an agent or connect an application, prompts, selected files, tool requests, responses, account identifiers, and related metadata may be sent to the provider or application you selected. Those third parties determine their own processing, retention, training, and security practices. Review their policies and configure their accounts appropriately.

AEXGrid does not treat the presence of an integration as universal authorization. Application actions require the connection, grants, and role checks described in the product.

7. Why we use information

  • Provide accounts, workspace discovery, secure connection setup, dashboard access, support, updates, and other requested features.
  • Authenticate users and devices; enforce admission, permissions, limits, and plan entitlements.
  • Maintain reliability, diagnose failures, prevent fraud and abuse, and protect users, Gridspawn, and third parties.
  • Communicate about the Service, security, legal notices, and support requests.
  • Comply with law and enforce agreements.
  • Improve the Service using aggregated, de-identified, or appropriately protected operational information.

9. How information is shared

We may share information with infrastructure, identity, security, support, and other processors that help operate AEXGrid; with providers and applications you choose; with professional advisers; when required by law or necessary to protect rights and safety; and in connection with a merger, financing, acquisition, reorganization, or sale of assets. Processors may use information only for the services they provide to us.

We do not sell personal information for money. We do not use the AEXGrid website or documentation for third-party behavioral advertising.

10. Website and documentation data

Documentation search runs locally against a bundled index. Reading and motion preferences are stored in browser localStorage under aexgrid.reading-view and aexgrid.motion-paused. The authored product site and documentation do not include third-party analytics, advertising trackers, or remote fonts.

Hosting and content-delivery providers may process ordinary access logs, including IP address, browser information, requested path, timestamps, and security events. The dashboard may use storage or cookies needed for authentication, security, and application state.

11. Retention and deletion

Local data remains until you remove it, clear the application profile, or delete the relevant workspace files, subject to your backups and synchronization. Hosted account and operational information is kept only as long as reasonably necessary for the purposes described above, including security, dispute resolution, legal compliance, and service continuity. Retention periods vary by data type and legal requirement.

Third-party providers and applications control their own copies. Removing an AEXGrid connection does not necessarily delete information already transmitted to them.

12. Security

We use technical and organizational measures designed to protect information, including authenticated access, scoped admissions and grants, protected connection transport, bounded protocol messages, and platform credential storage where supported. No software, device, or network can be guaranteed completely secure. Keep your operating system, AEXGrid, providers, and connected tools updated, and protect account and device access.

13. International processing

Gridspawn is based in the United States. We and our service providers may process information in the United States and other countries whose laws differ from those where you live. Where required, we use recognized safeguards for international transfers.

14. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information, and to appeal or complain to a regulator. You may also manage local application data, disconnect applications, stop dashboard availability, and remove provider profiles through available controls. Some information may be retained where legally permitted or required.

To exercise a privacy right, use the Gridspawn LLC contact route linked from AEXGrid’s Contact page, identify AEXGrid, and provide enough information for us to verify and respond to the request.

15. Children

AEXGrid is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information, contact us so we can investigate and take appropriate action. Additional local age requirements may apply.

16. Changes and contact

We may update this Policy as AEXGrid, our service providers, or legal requirements change. We will publish the effective date and provide additional notice when required. For questions, requests, or security-sensitive privacy reports, use the Gridspawn LLC contact route linked from AEXGrid’s Contact page and identify AEXGrid.

KEEP EXPLORING

Search AEXGrid documentation

Explore the documentationLOCAL SEARCH

Copy this link

Your browser did not allow automatic copying. Select and copy the address below.