Terms of Service

The agreement

These Terms of Service form an agreement between the customer organization using BridgeComp and the company operating it. [LEGAL REVIEW REQUIRED — COMPANY LEGAL ENTITY]

Enterprise agreements come first. Many BridgeComp customers sign a separately negotiated agreement — a master service agreement, order form, statement of work, data processing agreement or service level agreement. Where a signed agreement covers the same subject matter as these terms, the signed agreement governs to the extent of the conflict; these terms fill the gaps it does not address. [LEGAL REVIEW REQUIRED — DOCUMENT HIERARCHY]

Using BridgeComp — signing in, connecting a system, activating a flow — means the organization you act for accepts these terms.

Accounts

• Registration. BridgeComp accounts are created for your organization and its invited users; there is no self-serve public registration. Information provided at setup must be accurate and kept current.
• Authorized users. Accounts are for named people in (or engaged by) your organization. Credentials must not be shared; each user signs in as themselves, and the audit trail records who did what.
• Administrators. Your organization's administrators control users, roles, group membership and go-live rights, and are responsible for keeping those assignments right as people change.
• Account security. You are responsible for safeguarding credentials and for activity performed under your organization's accounts. Two-factor authentication is available to every user and enforced for administrator roles; tell us promptly at the address below if you suspect an account is compromised.

Authorized use

BridgeComp is licensed for your organization's internal business use: building, operating and monitoring integrations and automations between systems you are authorized to connect. The following are prohibited, and we may suspend or terminate access that engages in them:

• Unlawful activity, or processing data you have no legal right to process.
• Accessing, or attempting to access, third-party systems without authorization — BridgeComp connects systems; it does not license you to reach systems that are not yours to reach.
• Using connected third-party APIs in breach of those providers' terms, or at abusive volumes designed to circumvent their limits.
• Probing, scanning or attacking BridgeComp infrastructure, interfering with the service, or attempting to reach another tenant's data.
• Reselling or operating the service for third parties without an agreement that covers it — managed service providers should talk to us; that arrangement is supported, but by agreement.

A standalone Acceptable Use Policy may later replace or supplement this section; until then, this section is the acceptable-use framework.

Customer responsibilities

• Authorization to connect. You are responsible for having the right to connect each system, database and API you configure — including the credentials you store and the data your flows move.
• Business rules. Your flows encode your business rules. BridgeComp executes the configuration your organization approved; deciding that the configuration is correct for your business is yours.
• Production approval. BridgeComp provides validation, dry-run and monitoring tools precisely so that nothing needs to go live untested. Taking a flow live is your organization's decision, made by your administrators, and recorded in the audit trail.
• Legal compliance. You are responsible for ensuring the data you process through BridgeComp is processed lawfully — including any notices or consents your own customers require.

AI-generated automations

BridgeComp's AI features help people create and modify automations from natural-language descriptions. The intended path is deliberate:

Prompt → AI-drafted automation → validation → testing (dry-run) → your approval → activation.

• AI-generated configurations are drafts. They must be reviewed and tested by your organization before production activation — the platform's validation and dry-run gates exist to make that practical, not optional.
• AI output is not guaranteed to be correct, complete or fit for your business rules. The deterministic runtime executes exactly the configuration that was approved; it does not re-judge it.
• What AI features send to model providers, and what they never send, is described in the Privacy Policy. AI features can be left unconfigured, and flow execution never depends on them.

AI can build it. Your organization stays in control.

Customer data

• Ownership. Your business data is yours. Flow configurations you create for your organization are yours. Nothing in these terms transfers ownership of customer data to us.
• Processing rights. You grant us only the rights needed to operate the service: to process and transmit data as your flows direct, to store what the platform stores (configuration, credentials in encrypted form, execution history, the audit trail), to troubleshoot problems, to maintain security, and to meet legal obligations.
• Confidentiality. Your data and configuration are confidential. Platform staff access tenant data only through the audited, banner-marked support mechanism described in the security overview.
• Backups. Managed deployments are backed up on a schedule described in the security overview. In on-premise deployments, backups run on your infrastructure and are your responsibility to verify.
• Export and deletion. Job payloads and configuration are inspectable and exportable from the product; ask us for a fuller export. On request — and by default at the end of a contract — we delete a company's job data or the company itself.
• Legal requests. If we are legally compelled to disclose customer data, we will notify you unless the law forbids it, and disclose no more than required. [LEGAL REVIEW REQUIRED]
• Third-party systems. Systems you connect — ERPs, warehouses, SaaS applications — are governed by their own terms and privacy policies. Data your flows deliver into a third-party system is thereafter held under that system's terms.

Intellectual property

• The platform is ours. BridgeComp — the software, connectors, execution engine, templates and documentation — belongs to the operating company and its licensors. Your subscription is a right to use it, not a transfer of it.
• Your data and configurations are yours, as described above.
• Custom connectors and custom development. Ownership and licensing of connectors or development work we build for a specific customer is set in the applicable order or statement of work. [BUSINESS/LEGAL REVIEW REQUIRED — DEFAULT OWNERSHIP OF CUSTOM WORK]
• Feedback. If you suggest improvements, we may use the suggestion without obligation — it costs you nothing and ties us to nothing.

Subscriptions & billing

• Plans, published prices and what each includes are listed on the pricing section. Enterprise pricing is agreed per customer.
• Subscriptions are billed monthly or annually as agreed at purchase; the published annual price is ten months' fee for twelve months of service.
• Plan changes take effect as agreed with us; there is currently no self-serve checkout, upgrade or downgrade — plan changes are arranged with us directly.
• Prices exclude taxes; applicable taxes are added as required by law.
• [LEGAL REVIEW REQUIRED — RENEWALS, CANCELLATION NOTICE, REFUNDS, OVERDUE INVOICES] — these must match the actual billing agreements in use and must not be invented here.

Service availability

We operate BridgeComp with the monitoring and failure-handling machinery described on this site, and we take availability seriously — but these terms do not promise a specific uptime level, and there is no standard published SLA. Scheduled maintenance may briefly interrupt the service. A contractual SLA with measurable commitments is available on Enterprise agreements; if a standard SLA is published later, it will live at /sla and be referenced here.

On-premise deployments

BridgeComp can be installed on customer-controlled infrastructure. An on-premise deployment is a software license plus services, not a hosted subscription, and several responsibilities shift to the customer:

• You provide and operate the infrastructure — machines, network reachability, operating system, and the backups the installer configures.
• Software updates are applied through the supported deployment mechanism; running unsupported modified versions ends our ability to support the installation.
• Remote support access, if any, happens only as agreed with you.
• On termination, the license to run the software ends and installed copies are removed, while your data remains yours to keep.

[LEGAL REVIEW REQUIRED — ON-PREMISE LICENSE TERMS] License scope, permitted installations and environments, version support windows and termination mechanics for on-premise deployments must be settled in a reviewed license agreement — this section flags the areas; it does not resolve them.

Warranties & liability

This section will contain professionally drafted provisions on warranty disclaimers, limitation of liability, exclusion of consequential damages, third-party services and API failures, customer configuration, force majeure and indemnification. Those limits define the commercial risk allocation of the product and are not something to generate — they are placeholders until counsel drafts them:

• [LEGAL REVIEW REQUIRED — WARRANTY DISCLAIMER]
• [LEGAL REVIEW REQUIRED — LIABILITY CAP]
• [LEGAL REVIEW REQUIRED — CONSEQUENTIAL DAMAGES EXCLUSION]
• [LEGAL REVIEW REQUIRED — THIRD-PARTY SERVICES & EXTERNAL API FAILURES]
• [LEGAL REVIEW REQUIRED — FORCE MAJEURE]
• [LEGAL REVIEW REQUIRED — INDEMNIFICATION]

Factual context counsel should draft against: BridgeComp executes customer-approved configuration against third-party systems whose availability and behaviour we do not control; flows default to dry-run; go-live is an audited customer decision; and the platform records per-step execution evidence.

Term & termination

• These terms apply while your organization uses BridgeComp.
• Either side may terminate as the applicable subscription or agreement provides. [LEGAL REVIEW REQUIRED — NOTICE PERIODS]
• We may suspend access that violates the authorized-use section, endangers the platform or other tenants, or is required by law — narrowly, and restoring access when the cause is resolved.
• After termination, data deletion is the default, as described under customer data; tell us if you need an export first.

Governing law

[LEGAL REVIEW REQUIRED — COMPANY LEGAL ENTITY AND GOVERNING LAW] The final terms must identify the actual legal entity operating BridgeComp, its governing jurisdiction and the dispute forum. This draft deliberately does not choose them.

Changes & contact

We may update these terms as the product and the law evolve; material changes will be announced to account administrators before they take effect, and the date below always states the current version. Questions about these terms: contact us or reach Priotech via priotech.co.il.

Draft — last updated 2026-08-11 · requires legal review before production publication