The answer is not “None.” Hosted RustGrid depends on third parties to deliver the website and application, store attachments, send transactional email, and process billing. Other providers receive data only after consent or when a customer enables the relevant sign-in, repository, model, or webhook feature.
01
How to read this register
“Data shared” includes data sent to a provider, data the provider receives directly from a browser or worker, and technical request data such as IP address, user agent, timestamps, URLs, and service logs. A provider receives only the data needed for the applicable feature, subject to configuration and the provider’s own terms.
Core means the provider supports the hosted Service or a normal commercial operation. Optional means a user must consent, choose that sign-in method, or enable the integration. A provider used by a customer-operated worker or destination is controlled by that customer and may not be known to RustGrid.
This public register supplements the Privacy Policy. A signed data-processing agreement, order, or provider-specific notice controls where it says otherwise.
02
Core hosted-service providers
| Provider and service | Purpose | Data shared | When |
|---|---|---|---|
| Vercel Privacy notice |
Hosts and delivers the public website and AgentOps web application. A Vercel Function relays AgentOps API requests to the RustGrid API. | IP address, browser and request metadata, requested URLs, diagnostics, and security logs. For proxied application calls, request headers and the account, workflow, integration, or billing payload needed to relay the call. | When a visitor uses the website or hosted AgentOps application. |
| DigitalOcean Spaces and hosted infrastructure Privacy policy |
Stores private ticket or mission attachments and public email assets. DigitalOcean-managed infrastructure may also support hosted RustGrid services. | Uploaded attachments and object metadata; storage request IP, headers, and logs; requests for public email assets; and data or operational logs processed by any hosted infrastructure in use. | When attachments are uploaded, downloaded, scanned, transformed, or deleted; when an email client loads a hosted asset; or when a hosted service uses that infrastructure. |
| Postmark by ActiveCampaign Privacy policy |
Sends account verification, password reset and change, welcome, tenant invitation, project invitation, and email-change messages. | Recipient email address; message template and content; action links and tokens; relevant name or workspace information; timestamp; and, for security notices, IP address and user agent when available. Delivery and bounce events are returned to RustGrid. | When RustGrid sends a transactional or account-security email. |
| Stripe Checkout, Elements, Link, Billing and Tax Privacy policy |
Processes checkout, payment methods, subscriptions, invoices, tax, refunds, disputes, and billing status. | Billing contact and business information, plan and price, usage or quantity, customer and subscription identifiers, transaction metadata, IP and device information, and payment credentials entered directly into Stripe components. RustGrid receives billing identifiers and status, not full card or bank credentials. | When a customer opens billing, checks out, maintains a paid subscription, or a billing event is processed. |
| Google Fonts Google Fonts privacy |
Delivers the Manrope web font used by public RustGrid pages. | IP address, user agent, requested font or stylesheet, referring page information allowed by browser policy, and request timing. | When a browser loads a public page that requests the hosted font. This request is not controlled by the optional analytics choice. |
03
Optional and customer-enabled services
| Provider and service | Purpose | Data shared | Activation |
|---|---|---|---|
| Google Analytics Google Privacy |
Measures use of the public website. | Page URL and title, referrer, interaction events, cookie or browser identifiers, device and browser information, IP-derived approximate location, and timestamps. RustGrid does not intentionally send account email, ticket text, source code, API keys, or other Customer Data. | Only after a visitor accepts optional analytics. The choice can be withdrawn on the Privacy Policy. |
| Google OAuth Google Privacy |
Signs a user into RustGrid with Google. | OAuth authorization request, callback code and token exchange, provider account identifier, email, name or profile data made available by the granted scope, and technical request metadata. | Only when Google sign-in is configured and the user chooses it. |
| GitHub OAuth and GitHub App Privacy statement |
Signs users in, connects App installations and repositories, receives webhooks, reads repository and workflow state, and creates or updates branches, commits, checks, and pull requests. | OAuth and installation identifiers and tokens; GitHub identity and email made available by scope; organization and repository metadata; source and commit data; branches, pull requests, reviews, checks, workflows, webhook payloads, delivery identifiers, and agent-produced changes. | Only when a user selects GitHub sign-in or an authorized customer installs or connects the GitHub integration. |
| OpenAI Codex and configured OpenAI models Business data privacy |
Provides model inference and agent capabilities used during a configured run. | Mission instructions, prompts, relevant repository source and context, attachments or tool results supplied to the run, model inputs and outputs, identifiers, token usage, timing, and error metadata. The exact data depends on the task, permissions, tools, and customer’s OpenAI or ChatGPT configuration. | Only when the customer configures or authorizes an OpenAI-backed agent or model. The customer’s provider account, terms, retention, and controls apply. |
04
Customer-selected recipients and deployment dependencies
- Webhook destinations. RustGrid sends the event payload, delivery identifiers, signature, and request metadata configured for the webhook to the customer-selected URL.
- Worker tools and network destinations. An authorized agent run may call package registries, source hosts, model providers, observability services, deployment platforms, or other endpoints allowed by its manifest, tools, credentials, and network policy.
- Customer-operated workers. Mission context, repository source, commands, generated files, logs, and run credentials are processed on infrastructure selected and controlled by the customer or its operator.
- Alternative storage or service providers. Deployments can use a compatible endpoint or different operational provider. The operator is responsible for identifying that recipient and providing required notices.
RustGrid cannot publish a fixed name for a recipient selected solely by a customer. Enabling one of these destinations instructs RustGrid to send the data needed for that configured operation.
05
Software dependencies that are not data recipients
RustGrid also uses open-source libraries, command-line tools, containers, and local services. They are not listed here merely because their code is installed. A dependency belongs in this register when it independently receives data over a network or operates infrastructure that processes RustGrid data.
For example, locally operated PostgreSQL, Redis-compatible software, ClamAV, Docker, and application libraries do not by themselves send data to their authors. A hosted version of the same technology may introduce a provider that the deployment operator must identify.
06
Changes, questions, and provider terms
Providers, product features, and deployment choices can change. RustGrid will update this page when a material hosted-service recipient changes and provide additional notice where a contract or law requires it. Provider links above describe their own processing and may change independently.
Questions about this register, a DPA, or a specific deployment: hello@rustgrid.com. For product help, use RustGrid Support.