Terms of use draft

1. The service and this agreement

NodCue is being developed to relay supported Codex and Claude Code approval requests from a paired Mac to iPhone and Apple Watch. The NodCue service records decisions; the coding agent and tools on your computer perform the underlying work. NodCue does not provide a coding model or general remote desktop access.

The final agreement will identify the entity providing NodCue and how to contact it. The App Store developer listing alone does not establish that entity for this draft. Before using a released service, review its effective terms and privacy policy. You must have authority to use the connected accounts, computer, repositories, and tools, and to accept the agreement for any organization you represent.

2. Your account and devices

Protect your Apple account, device passcodes, pairing codes, and NodCue credentials. Pair only computers and devices you control or are authorized to manage. Do not share access credentials or let another person approve actions through your account. Report suspected unauthorized access using the verified support channel once available.

You are responsible for reviewing the request, its originating computer, and the action you intend to authorize. A short notification or tool summary may omit important context. If you cannot identify the action, inspect it on your computer before deciding.

3. What an approval means

An Allow decision authorizes the specific pending request, subject to its validity and the service’s final state. It is not a recommendation that the action is safe and does not confirm that it executed successfully. Check the reported execution result and your computer. NodCue does not verify the correctness of generated code or replace the agent’s native permission controls.

A tap, notification, loading indicator, or connection error is not proof that a decision reached the server. Refresh the request to confirm its state. A completed or expired request cannot be approved again. Denying a pending request does not reverse an action that has already executed. Maintain backups and use appropriate native permissions for sensitive operations.

4. Acceptable use

Use NodCue only for lawful actions that you are authorized to perform. Do not use it to access another person’s computer or data without permission, distribute malware, bypass authentication or rate limits, interfere with the service, or impersonate another user. Do not include secrets or unnecessary personal information in request metadata or support reports.

You retain your rights in your code and content. NodCue processes the request information needed to provide the service as described in the privacy policy. This draft does not grant rights to sell your code or use it to train models.

5. Compatibility and availability

Compatibility is limited to the agent versions, tools, operating systems, and Bridge releases that are verified and documented for the released product. Updates to Apple systems or coding agents may affect compatibility. Production login, notification delivery, supported installation, and real-agent execution are still undergoing verification.

Background alerts use iPhone push notifications and Apple’s system routing to Watch. Network access, permissions, Focus settings, and device state affect delivery. Background Watch alerts are not promised when iPhone is off. The foreground Watch app is designed to use HTTPS directly once configuration, credentials, and connectivity are valid.

The service may be unavailable during maintenance, network failures, or third-party outages. No uninterrupted availability or guaranteed notification-delivery time is promised. Do not rely on NodCue for emergency or safety-critical operations.

6. Third-party services and App Store licensing

Apple, OpenAI, and Anthropic provide their own services under their own agreements. NodCue is not endorsed by those providers. You are responsible for any required third-party accounts, permissions, and charges.

The license applicable to an App Store download is identified by its App Store listing and Apple’s applicable licensing framework. These proposed service terms do not replace that license. The final release must confirm whether Apple’s standard license or a separately approved custom license applies; this page is not submitted as a custom App Store EULA.

7. Fees and future changes

This draft does not create a payment obligation, subscription, or automatic renewal. Any future paid offering must present its price, billing terms, and cancellation information before purchase and obtain any required agreement. Third-party services and connectivity may carry separate charges.

8. Ending use and account deletion

You may stop using NodCue. Remove the Bridge integration through the supported uninstall process and revoke paired access where available. Deleting the app or removing local credentials does not by itself delete server records or revoke every remote session.

The server account-deletion flow has been implemented locally, but the in-app flow and live Apple revocation remain unverified. Before release, support guidance must provide the verified deletion steps. Retention, delayed Apple revocation, and deletion-marker limitations are described in the privacy draft.

The proposed service terms permit restricting access when reasonably necessary to address unauthorized use, security threats, legal requirements, or material misuse. The final terms must specify a working contact channel for questions and review requests. Such restrictions do not remove rights you have under applicable law.

9. Warranties, liability, and your rights

Approval tools cannot eliminate errors in generated code, unintended commands, or data loss. No additional promise of fitness, uninterrupted operation, or error-free results is made by this draft. Nothing in the final agreement may exclude non-excludable warranties, consumer protections, or liabilities under applicable law.

Legal review pending: the final warranty language, any lawful liability limits, contracting entity, governing law, and dispute process have not been selected. No monetary liability cap, mandatory arbitration requirement, or waiver of statutory rights is imposed by this draft.

10. Changes and contact

The effective version will show its date. Material changes should be communicated through an appropriate service channel, with additional agreement where required. No retroactive acceptance is inferred from reviewing this draft.

The public operator address and verified contact channel are pending. See support contact status. Do not send credentials, source code, or full terminal logs.