On this page · jump to a step
Choose the scope. Review the capabilities.
An Relayard endpoint is bound to a specific project. System selection and project bookmarks authorize local access; each call still checks the project and permissions. A remote client does not gain access merely by possessing the URL.
OAuth governs client access
The client signs in through OAuth and requests a defined scope. Local and server-side checks limit the available capabilities. Unknown tools or changed definitions need review. Enable only the read, edit, execution or Simulator capabilities your task requires.
Where does the data go?
| Content | How it is handled |
|---|---|
| Project files and native builds | Remain and run on your Mac. |
| Requested source excerpts and logs | Pass through the hosted relay to the authorized AI client. |
| Previews and screenshots | Return through the relay and image transport path, which may use cloud object storage depending on the version. |
| Account, device and authorization records | Are processed by the product service for sign-in, connection and access control. |
Pause, revoke and roll back are different
- Pause: stops new native dispatch. It does not establish that an already running operation was cancelled.
- Revoke: prevents the client from continuing through that authorization.
- Roll back: restores source changes as a separate project action. Pausing and revoking do not automatically roll back completed work.
Project scope is not a complete execution sandbox
Builds, macros, plugins and tests may execute project code. Work with trusted projects and keep a Git checkpoint before edits. Avoid simultaneous agents editing the same project, and do not rely on automatic coordination of unsaved editor buffers.
What this page covers
This page explains product access and data flow. It does not replace the privacy policy or terms for a specific release. Retention periods, regions and service arrangements depend on the actual release and operator policies.
Documentation updated: 2026-10-08