Instance Control

Terms of Use

Version and effective date:

These Terms of Use (Terms) govern the Instance Control application, the Account Service, and the connected features described below. The Provider is Oleksandr Beschasnyi. A registration request includes the user's agreement to these Terms, but the contract becomes effective only after the user successfully verifies the single-use activation link or code, the account is activated, and the accepted document versions are recorded.

1. Provider and Contact Details

The service provider is Oleksandr Beschasnyi (Provider).

Technical Support and the formal complaint procedure in section 15 are separate. Support requests are also governed by the Support Terms of Use made available on the Support website.

2. Definitions and Scope

In these Terms:

  • Instance Control or App means the full macOS command centre, its local helper components, and account-connected features made available by the Provider.
  • Account Service means the Provider's service for account activation, authentication, sessions, devices, security, legal-document review, notifications, remote requests, and transfer coordination.
  • User means the individual who requests and, after activation, holds an account or uses the App with proper authority.
  • Device means a computer enrolled with an account or used for an authorized Instance Control workflow.
  • Windows Device Bridge means the limited outbound-only Windows companion. It is not the full macOS command centre.
  • Connected Service means an optional third-party service used with Instance Control, such as Telegram, Webex, transactional email, an IDE, database tooling, or an AI provider.
  • Remote Action means a supported request initiated through an account-connected interface and revalidated by the selected Device before local execution.
  • Project Transfer means an explicitly approved encrypted workflow that moves selected project content, and optionally supported database material, between trusted Devices.
  • Plan means a defined level of account-connected access or functionality.
  • Feature Entitlement means a permission associated with an account that controls access to one or more account-connected features.
  • Legacy means a free Plan or Feature Entitlement that may be assigned by the Provider and that does not, by its name alone, promise lifetime, permanent, grandfathered, or irrevocable access.
  • Account Suspension means a temporary restriction of account access or selected account-connected features.

Instance Control is intended for authorized development and test workflows. The macOS App can coordinate supported Guidewire projects, local processes, IDE and runtime workflows, build and readiness state, project profiles, local database tools, account Devices, notifications, and transfers. Windows Device Bridge can discover and publish limited local state and can act as an explicitly approved encrypted transfer source; it does not provide server lifecycle or IDE control, receive or apply a transferred clone, expose an inbound listener, or provide a general remote-command channel.

Third-party software, projects, data, services, and trademarks remain subject to their owners' licences, terms, and policies. These Terms do not replace them.

3. Eligibility and Authority

You may enter this contract only if you have the legal capacity to do so. If you use Instance Control for an employer, client, company, project owner, or other organization, you must have authority for the systems, projects, credentials, data, Devices, and Connected Services involved.

You remain responsible for complying with applicable employment, client, confidentiality, source-code, data-handling, security, and third-party licence obligations. Accepting these Terms does not override an employer's or client's access, security, code-handling, or approval policy. Do not transfer or process content that you are not permitted to access, use, modify, or disclose.

Mandatory protections that apply to consumers or qualifying sole traders are preserved as described in section 15.

4. Account Registration and Contract Duration

To request an account, you provide a valid email address, choose a password, agree to the exact current Terms, and acknowledge the exact current Privacy Policy. Submitting a registration request, selecting the checkbox, or opening a legal document does not by itself create an account or contract.

The contract takes effect after the user successfully verifies the single-use activation link or code, the account is activated, and the accepted document versions are recorded. An invalid, expired, abandoned, superseded, or obsolete registration creates no contract or acceptance record.

The contract continues for an indefinite period until the account is deleted or the contract is otherwise lawfully terminated. Signing out, disconnecting an integration, uninstalling the App, or stopping local use does not by itself delete the account or terminate the contract.

The current Terms and Privacy Policy are available before registration through their first-party website pages and as the exact document versions presented in the App. You can print or save the public pages for later reference. Merely fetching, opening, printing, or saving a document does not constitute acceptance.

You must keep your password, passkeys, sign-in codes, session credentials, Device private keys, and integration credentials confidential. Use the available session revocation, Device removal, recovery, and security controls if access may be compromised. Notify the Provider promptly through the legal contact if you cannot safely regain control.

5. Plans and Feature Entitlements

The Provider may assign an account a free, promotional, preview, Legacy, or, if offered separately in the future, paid Plan together with the account-connected features available under that Plan. A Plan may provide general Account Service access or one or more Feature Entitlements, and availability may differ between accounts according to the assigned Plan or stated eligibility.

Legacy is a free account Plan or Feature Entitlement that may be assigned by the Provider. The name does not promise lifetime, permanent, grandfathered, or irrevocable access unless a separate written offer expressly states otherwise.

The Provider may automatically assign or move an account to a free Plan or Feature Entitlement, including Legacy. Automatic assignment does not create a paid subscription, authorize a charge, or otherwise create a payment obligation.

The Provider may correct, replace, limit, or withdraw a free Plan or Feature Entitlement for an individual account or for a group of accounts, including all accounts using that entitlement, only where there is a valid reason. Valid reasons include product development, changes in operating costs or third-party dependencies, security or legal requirements, discontinuation of the relevant feature or service, correction of an assignment error, loss of stated eligibility, misuse, or a material breach of these Terms.

If Legacy is withdrawn, the account may remain active while some account-connected features are unavailable until another available Plan is selected where that option exists or is assigned. Withdrawal of Legacy does not by itself suspend the account, terminate the contract, or delete the account.

An account will not be moved automatically from a free entitlement to a paid Plan, and no fee will be charged, without a separate explicit purchase or subscription action by the user and clear disclosure of the applicable price and renewal terms. If paid Plans are offered in the future, continued use of a free Plan or of the App will not by itself constitute that purchase or subscription action.

Material changes that negatively affect access will be communicated clearly and, where required by applicable law, in advance on a durable medium. Applicable rights to terminate the contract remain unaffected. Nothing in this section limits mandatory rights that may apply to a free digital service, including a service supplied in exchange for personal data.

6. Technical Requirements and Special Risks

The full App requires macOS 13 or newer and a release compatible with the Device architecture. Current, more detailed release requirements are published at https://obcardinal.com/projects/instance-control/#download. Windows Device Bridge requires a supported Windows environment capable of running its self-contained x64 package. Availability of a feature can also require:

  • internet access and availability of the Account Service or a Connected Service;
  • a supported local Guidewire project structure and compatible project configuration;
  • compatible IntelliJ IDEA or Guidewire Studio, Java or JDK, build tooling, database tooling, Docker, PowerShell, or other feature-specific software;
  • sufficient local file, process, Accessibility, network, key-storage, database, and automation permissions; and
  • a current App version and supported provider API.

Instance Control does not promise compatibility with every Guidewire, IntelliJ, Guidewire Studio, JDK, database, operating-system, plugin, network, messaging-provider, or corporate-security configuration. Unsupported local modifications, stale generated files, unavailable tools, restricted permissions, provider changes, or modified project conventions can make a feature unavailable, and the action is blocked when the required checks cannot be completed.

Meaningful technical risks include interrupted process or database work, conflicting IDE or build activity, incorrect project or environment selection, incompatible local tools, stale or compromised Devices, exposed credentials or integration tokens, incomplete network delivery, and disclosure to a wrongly selected transfer target. Security controls reduce but do not eliminate these risks. Keep operating systems, the App, local tools, accounts, and Connected Services appropriately secured and updated.

7. Software Licence and Intellectual Property

Subject to these Terms, the Provider grants you a limited, non-exclusive, non-transferable right to install and use the distributed App on Devices that you control or are authorized to use, for authorized internal development and test workflows. No fixed Device count is imposed by these Terms.

You may not resell the App, present it as your own product, distribute unauthorized copies, remove proprietary notices, or circumvent account, security, signing, update, or feature safeguards. These restrictions do not limit rights that applicable law does not permit the Provider to restrict, including statutory rights concerning software interoperability, observation, study, testing, backup copies, or decompilation where the legal conditions are met.

Rights in Instance Control, its website, and Provider-created materials remain with the Provider or the applicable licensors. Open-source components remain governed by their own licences. Third-party products and trademarks remain the property of their respective owners.

The Provider does not acquire ownership of your projects, source code, imported databases, customer data, generated customer content, AI conversation content, or Connected Service data merely because you use Instance Control. You must already have the rights needed for any content on which you ask the App to operate.

8. Authorized Use

You may use Instance Control only for lawful purposes and only with systems, projects, accounts, databases, Devices, and services that you are authorized to access. You must not:

  • gain or attempt to gain unauthorized access to another account, Device, project, network, database, or service;
  • submit malicious commands, files, payloads, SQL, transfer content, or automation;
  • bypass or probe activation, authentication, Device proof, transfer trust, rate limits, confirmations, signing, or other safeguards except as permitted by law for legitimate security or interoperability work;
  • use the Account Service or messaging infrastructure in a way that creates unreasonable load, spam, harassment, or service disruption;
  • upload, transmit, or process unlawful content; or
  • violate applicable law or another person's confidentiality, privacy, intellectual-property, contractual, or security rights.

9. User-Controlled Local Operations and Backups

Instance Control executes technical operations selected or authorized by the user. Depending on the selected feature, an operation may:

  • start, stop, restart, or terminate processes;
  • open or control supported IDE, build, Application, and runtime workflows;
  • modify supported project, IDE, VM-argument, generated-output, or profile configuration;
  • manage only Instance Control-owned marker-delimited blocks in AGENTS.md;
  • generate or apply SQL, clean or restore a supported database, or replace database files or endpoints;
  • copy, clone, transfer, import, or delete selected project resources; or
  • change Build Accelerator, Fast Server Mode, Lightweight IDE, or other supported performance and development profiles.

Before an important operation, verify the selected project, Application, environment, database, source Device, target Device, action, and credentials. Review previews, summaries, dry runs, fingerprints, and confirmation screens where provided. Test important changes in an appropriate development or test environment and maintain current, usable, independent backups of important source code, configuration, databases, and other data.

Instance Control is not a backup, archival, disaster-recovery, production-change-management, or data-recovery service. A transfer, project copy, generated output, or database operation must not be treated as the only backup of important data.

These responsibilities do not make a Provider defect your responsibility merely because you selected a supported action. Liability remains allocated by cause under section 13 and applicable law.

10. Connected Services, Remote Actions, and Transfers

Connected Services operate only after the required account, integration, bot, recipient, or Device configuration is completed. You must have authority to connect and use each service. A third-party provider can process and retain delivered messages, events, routing details, and related metadata under its own terms and privacy rules. Disconnecting a service prevents new Instance Control use of that connection but does not erase records retained independently by the provider.

Telegram may expose only the supported state-aware Start, Stop, and Restart actions. Webex may expose read-only account, Device, and project summaries, a supported Refresh request, and the same allowlisted lifecycle actions in an authenticated direct bot conversation. Webex Stop and Restart require a short-lived confirmation. Every remote action is queued only to the selected enrolled Device, and that Device revalidates the exact current project, Application, and local state before it may act; a stale, unsafe, unauthorized, changed, or unsupported request is rejected. Opening, reading, or copying a bot message never runs an action. Webex may also send selected lifecycle and security notifications to the account profile email. Notification and reply delivery can be delayed, rejected, duplicated, or unavailable; delivery of every message is not promised.

Project Transfer requires explicit source and target selection, approval, and trust confirmation. Verify the displayed Device identity, pairing code, and fingerprints before proceeding. Transfer payloads are encrypted for the selected target, but the Account Service still processes the limited routing and transfer information needed to coordinate them, including the selected Devices, size, state, expiry, acknowledgement, and integrity information. Encryption does not eliminate all metadata or protect content after a selected target decrypts it.

Windows Device Bridge can prepare and encrypt an approved project clone and, when specifically selected and supported, can include a best-effort database snapshot or backup. It does not apply the clone on Windows. The receiving App and local tools remain responsible for verified decryption, import, and supported target preparation.

11. Updates, Availability, and Third-Party Compatibility

The Provider may issue updates for security, compatibility, defects, legal requirements, or product development. A feature may require a current App version, and preview or unavailable functionality may change, be limited, or be withdrawn. The Provider may temporarily limit the Account Service for maintenance, security response, abuse prevention, dependency failure, or legal reasons.

The Provider does not promise a service level, permanent availability of every feature, or continued compatibility with every third-party product or API. Reasonable efforts may be made to communicate material planned interruptions or discontinuation where practical and legally required. Third-party outages, policy changes, API changes, certificate changes, local network restrictions, and unsupported project changes can interrupt a workflow outside the Provider's reasonable control.

The Provider does not undertake to operate the Account Service or other server-dependent components indefinitely. Maintenance, security incidents, infrastructure failures, third-party outages, product changes, or permanent discontinuation may make some or all account-connected features temporarily or permanently unavailable. Local features may remain available only where the current App can perform them without the affected server component.

If a server-dependent service is permanently discontinued, the Provider may terminate the affected service or contract subject to the notice and mandatory rights required by applicable law. Permanent discontinuation does not remove mandatory remedies for a non-conforming digital service.

12. Warranties and Service Limitations

Except for guarantees and remedies required by applicable law, Instance Control is provided as available. The Provider does not promise uninterrupted or error-free operation, permanent availability of every feature, successful delivery of every notification, or compatibility with every version or configuration of third-party software, local projects, operating systems, networks, databases, plugins, or Connected Services.

Technical defects and interrupted operations can occur. Unsupported local changes can affect results, third-party dependencies can change without the Provider's control, and security or maintenance work can temporarily limit access. Preview features may change or be withdrawn.

This section does not remove any duty to supply a conforming digital service, update, remedy, or other protection where applicable law makes that duty mandatory.

13. Liability

Liability is determined by the cause of the loss and applicable law. To the extent permitted by applicable law, the Provider is not responsible for loss caused solely by unauthorized use of your account or Device, an incorrect project, Application, environment, database, source, target, credential, or action selected by you, unsupported changes to the local environment, or a third-party service or tool outside the Provider's reasonable control.

Users should maintain current, usable independent backups before performing operations that may modify or remove files, configuration, databases, or project data. To the extent permitted by applicable law, the absence of such a backup may be taken into account when assessing avoidable loss, but it does not exclude liability for a defect or breach attributable to the Provider.

The Provider remains responsible to the extent required by applicable law for defects in Instance Control, failure to perform the contract, and acts of persons for whom the Provider is legally responsible. A supported user action or the involvement of a third-party component does not by itself transfer responsibility for a Provider defect to the user.

Nothing in these Terms excludes or limits liability for intentional misconduct, personal injury where liability cannot lawfully be excluded or limited, mandatory consumer or protected-sole-trader rights, remedies for non-conforming digital services, or any other liability that applicable law does not permit the Provider to exclude or limit.

14. Suspension, Termination, and Account Deletion

You may stop local use at any time. You may request account deletion and termination by emailing [email protected] from, or while identifying, the account email address. The Provider may require proportionate verification before deleting an account. Signing out or uninstalling the App is separate from account deletion.

The Provider may temporarily restrict, suspend, or disable account access or selected account-connected features where reasonably necessary to address a suspected account or Device compromise, unlawful or unauthorized use, an attempt to bypass safeguards, a material breach of these Terms, abuse of account or messaging infrastructure, a security incident, a legal or regulatory requirement, or a serious risk to users or the service. Where practical and lawful, the Provider will explain the reason and allow a reasonable opportunity to remedy a remediable breach. Immediate restriction may be used where delay would create a security, legal, or operational risk. An account will not be suspended merely because the user declines a paid Plan.

A Plan or Feature Entitlement change is separate from Account Suspension, contract termination, and account deletion. A Plan or Feature Entitlement change changes the available account-connected features. Account Suspension temporarily restricts account access or selected account-connected features. Termination ends the contract. Account deletion removes the account and associated Provider-controlled data according to the Privacy Policy.

A restriction or Account Suspension does not prevent the user from obtaining the current legal documents, contacting Support, requesting account deletion, or using security controls that remain technically available and must remain accessible under applicable law.

The Provider may terminate the contract for an unremedied material breach, a legal requirement, or discontinuation of the service. Where practical and required by law, reasonable advance notice will be provided for discontinuation and non-urgent termination. You may contact the legal email to challenge a restriction or termination.

Where the Account Service is permanently discontinued, the Provider may disable further access to the affected server-dependent service after providing any notice required by applicable law. This does not by itself delete the account or local project data. A global closure of the Account Service and an account-level termination are distinct actions even if either action makes server-dependent features unavailable.

Deletion or termination can revoke sessions and Device trust, disconnect Provider-controlled integrations, and stop or expire pending Account Service actions and transfers. It does not automatically delete local project copies or other data stored on your Devices, or records retained independently by a Connected Service. Provider-controlled data is handled under the Privacy Policy and may remain only where and for as long as necessary for an in-progress operation, security, legal obligations, or legal claims.

15. Complaints and Consumer Rights

A complaint may be submitted without an active App session through the stated complaint email address, [email protected]. To help route it, the user may include "Formal complaint" in the subject line. The Provider will assess the message according to its substance even if that label is omitted.

Where available, include the account email, a description of the issue, the relevant date or period, the requested resolution, and any supporting information needed to understand the complaint. Missing non-essential information does not invalidate a complaint. The Provider may request clarification where reasonably necessary to investigate or respond. Do not send passwords, activation links, sign-in codes, private keys, access tokens, or unrelated sensitive files.

Technical Support requests and formal complaints may use the same contact channel, but they are handled according to the substance of the message rather than the label selected by the user. The Provider will confirm receipt by email and respond by email unless another durable method is required or agreed. Where Article 7a of the Polish Consumer Rights Act applies, the response will be sent within 14 days after receipt. Otherwise, the Provider will respond within the period required by applicable law.

If you are a consumer, or a natural person conducting business for whom this contract lacks the professional character required by applicable law, you retain every mandatory right that applies to you. Where statutory digital-service rules apply, this includes the applicable rights concerning supply, conformity, updates, remedies, changes, and termination. These Terms do not waive those rights.

Any statutory withdrawal right applies only where the legal conditions for that right are met. Downloading, installing, activating, or using Instance Control does not by itself waive a withdrawal right, and these Terms do not invent or shorten a statutory procedure that may apply.

Consumers may seek information from a municipal or district consumer ombudsman or the Polish Office of Competition and Consumer Protection (UOKiK). Information about out-of-court consumer dispute resolution is available at https://polubowne.uokik.gov.pl/. Use of an available ADR procedure is voluntary unless applicable law provides otherwise and does not remove access to a competent court.

16. Privacy

Personal data is processed as described in the Instance Control Privacy Policy at https://obcardinal.com/instance-control/privacy/. Support-specific processing is described separately in the Support Privacy Notice. Agreement to these Terms and acknowledgement of the Privacy Policy are separate legal actions. Privacy acknowledgement is not consent to unrelated marketing, analytics, or future processing.

17. Changes to the Terms

The Provider may change these Terms only for a legitimate reason, such as a material product or service change, a security requirement, a legal or regulatory change, a change to third-party dependencies, clarification of unclear wording, correction of an identified problem, or one of the valid Plan or Feature Entitlement reasons stated in section 5.

The Provider will identify each version and effective date. Users will be informed of material changes through the App, account email, or another appropriate durable method when required. If acceptance is required, normal product content remains gated until the current version is reviewed and affirmatively accepted; opening the document alone is never acceptance. Sign Out, account-deletion requests, and legally necessary legal or security access remain available.

A change will take effect on the stated effective date or, for an existing user whose affirmative acceptance is required, when that user accepts it. Urgent security or legal changes may take effect sooner only where permitted by law. If you do not accept a required change, you may stop using the service and request account deletion. Changes do not rewrite or replace the acceptance history for earlier versions.

A material negative change to a Plan or Feature Entitlement will be communicated clearly and, where required by applicable law, in advance on a durable medium. No Terms change, Plan change, or continued use creates a paid subscription or authorizes a charge without the user's separate explicit purchase or subscription action. Mandatory rights to terminate the contract remain available.

18. Applicable Law and Jurisdiction

These Terms are governed by Polish law.

If you are a consumer, this choice does not deprive you of mandatory protection provided by the law of the country in which you habitually reside. The competent courts are determined under applicable law. These Terms do not impose an exclusive foreign court or override mandatory consumer-jurisdiction rules.

19. Contact

For legal questions, formal complaints, or account-deletion requests, contact [email protected]. For technical help, use https://obcardinal.com/support/.