SynapticCODE INTELLIGENCE
LEGAL / 07

Public service terms

Terms built for a B2B code intelligence service.

These terms cover the public site, hosted service, trials, and evaluations. A signed enterprise agreement or order form takes precedence where it says something different.

AudienceBusiness users
Customer sourceRemains yours
Contract prioritySigned terms control
01

Scope and order of precedence

These Terms govern access to Synaptic websites, hosted services, trials, previews, and evaluation environments. By creating an account or using the service, you agree to them for yourself and, when applicable, the organization you represent.

If your organization has a signed master services agreement, order form, data processing agreement, or other negotiated contract with Synaptic, that agreement controls where it conflicts with these Terms. Open-source Synaptic Engine components remain governed by their applicable open-source licenses.

02

Business accounts and administrators

You must provide accurate account information, protect credentials, and use the service only if you have authority to bind the organization or project you select. Organization owners and administrators can invite members, configure access, connect repositories, manage data lifecycle settings, and take other actions that affect the workspace.

  • Do not share personal sessions, API keys, MCP tokens, or one-time workspace credentials.
  • Notify your organization administrator if an account or credential may be compromised.
  • Your organization is responsible for assigning appropriate roles and project grants.
03

Customer content and source access

You retain ownership of repository content, workspace changes, prompts, queries, and other material submitted to the service. You grant Synaptic only the rights needed to host, copy, process, and secure that content to provide the service, comply with your instructions, and prevent abuse.

You represent that you have the rights and provider permissions required to connect each repository and submit its content. Hosted graph creation requires a temporary checkout of an authorized immutable commit. The worker retains the derived graph artifact and removes the per-job checkout as described on the Security page.

04

Acceptable use

Do not use Synaptic to violate law, another party's rights, or the security of the service. In particular, you may not:

  • access repositories, projects, artifacts, or accounts without authorization;
  • probe, bypass, or defeat authentication, rate limits, tenant boundaries, or runtime isolation;
  • upload malware or use extraction resources to attack third parties;
  • interfere with service availability or attempt to obtain another customer's data;
  • resell or provide the hosted service to third parties unless an agreement permits it; or
  • remove proprietary notices or misuse Synaptic trademarks.

Good-faith security research should be reported through the channel described on the Security page and must not use production customer data.

05

Service, plans, and third parties

Features and limits depend on the selected plan and deployment model. Payment, renewal, usage, support, and service-level commitments shown in an order form or signed agreement control. A public status page reports only configured probes and is not an uptime warranty.

The service can connect to third-party source, billing, email, identity, observability, hosting, and storage providers. Their services are governed by their own terms. Synaptic may change integrations or technical requirements while preserving contracted commitments.

06

Security and confidentiality

Synaptic uses technical controls described on the Security page, including scoped authorization, forced PostgreSQL row-level security, isolated repository processing, private artifact scope, and content-blind operational logging. Some protections are application controls; others must be configured and qualified in the production deployment.

No system can guarantee absolute security. You remain responsible for repository permissions, endpoint security, secret scanning, access reviews, and promptly revoking credentials that are no longer needed.

07

Suspension and termination

Synaptic may limit or suspend access when reasonably necessary to contain a security incident, prevent material harm, comply with law, address nonpayment, or stop a material violation of these Terms. Where practical, we will limit the action to the affected account, project, or capability.

Organization deletion uses a cooling-off workflow, is blocked by active legal holds, and attempts to remove private artifacts and revoke credentials before relational tenant data is deleted. Contractual retention or export obligations in a signed agreement continue to apply.

08

Warranties and responsibility

Trials, previews, and evaluation environments are provided without a service-level commitment unless Synaptic agrees otherwise in writing. Production warranties, indemnities, liability limits, support obligations, and remedies—if any—are those in the applicable signed agreement or order form.

Synaptic graph output is technical analysis, not legal, compliance, security, or professional advice. You are responsible for reviewing output before relying on it for production or governance decisions.

09

Changes and contact

We may update these Terms as the service changes. The date at the top identifies the current version. Material changes will be presented through an appropriate account or contractual channel before they take effect when notice is required.

Questions about these Terms or commercial agreements can be sent to enterprise@synaptic.dev.