Terms of Service

Terms of Service

Effective Date: October 14, 2026 Version: 1.17

These Terms of Service ("Terms") govern your access to and use of the Synergy In Construction (SynC™) platform, website, and related services (collectively, the "Services") provided by Synergy In Construction, LLC, a Florida limited liability company. By accessing or using the Services, you agree to be bound by these Terms. If you do not agree, do not use the Services.

1. Acceptance of Terms

By creating an account, accessing, or using the Services, you confirm that you have read, understood, and agree to these Terms and our Privacy Policy. If you are using the Services on behalf of an organization, you represent and warrant that you have the authority to bind that organization to these Terms, and references to "you" will refer to both you as an individual and the organization.

2. Eligibility

You must be at least 18 years old and capable of forming a binding contract to use the Services. By agreeing to these Terms, you represent and warrant that you meet these requirements and that your use of the Services complies with all applicable laws and regulations.

Where the Services are offered. SynC offers the Services to customers in the United States and does not direct them to anyone elsewhere. A company that buys seats or credits must be a United States entity, as Section 10.3 states. Reading, commenting on, responding to and exporting a project that has been shared with you, and reading the SynC Standards library, do not depend on where you are: SynC does not block either from outside the United States, and does not direct the Services to any other country. Our Privacy Policy states where personal information is processed and stored, and what it means to use the Services from outside the United States.

3. Account Registration and Security

3.1 Account Creation

To access certain features, you must create an account by providing accurate, current, and complete information during registration. You agree to update such information promptly as needed to maintain its accuracy.

3.2 Account Security

You are responsible for:

• Maintaining the confidentiality of your account credentials
• All activities occurring under your account
• Notifying us immediately of any unauthorized access or security breach
• Using a strong, unique password for your account
• Keeping any API key secret, and treating it as an account credential, as Section 4A states

3.3 Account Termination

SynC may suspend or terminate an account, or access to any part of the Services, as Section 16.2 states.

3.4 Signing In with a Microsoft or Google Account

Where the Services offer it, you may sign in with a Microsoft or Google account instead of, or as well as, a password. If you do:

• You are responsible for the security of that account. Section 3.2 applies to it as it applies to a password, and anyone who can sign in to that account can sign in to SynC as you.
• SynC relies on the provider's confirmation of who you are. Where the provider does not vouch for your email address, SynC verifies it by email as it does for any other account.
• Your relationship with the provider, and what it does with your account, are governed by the provider's own terms and not by these Terms. Section 4.4 applies to it.
• SynC may stop offering sign-in with a provider at any time. Your account and its content are not affected. You can set a password from the sign-in page using your email address, and you may add or remove a way to sign in at any time from your account's security settings, keeping at least one.

Our Privacy Policy states what SynC receives from the provider, what it does with it, and how to remove a linked account.

4. Description of Services

4.1 Core Services

SynC provides a cloud-based platform for construction project management, including but not limited to:

• Project specification management and standardization
• Equipment datasheet repositories and management
• Collaboration tools for construction teams
• Document version control and revisioning
• Project distribution and sharing features
• Company profiles and discovery

4.2 AI-Powered Features

The Services include artificial intelligence and machine learning features, including but not limited to:

• AI-assisted specification writing and analysis
• Automated content suggestions and improvements
• Natural language processing for construction documents
• Predictive analytics and recommendations

These AI features utilize third-party AI services and APIs. By using AI features, you acknowledge that:

• AI-generated content may contain errors or inaccuracies
• You are responsible for reviewing and verifying all AI-generated content
• AI responses are not professional advice (legal, engineering, or otherwise)

How content is transmitted to those third-party services, and the limits on what they may do with it, are addressed in §5.3.3.

4.2.1 Your Conversations with the AI Assistant

Your conversations with the AI assistant are stored by the Services so that a conversation remains available to you after you close it, rather than existing only for as long as the page is open. The messages you send to the assistant are your User Content under §5.1, and §5.3 applies to them.

• A conversation is your own record and is private to you. The Services provide no means by which another user can view a conversation of yours, and conversation content is not included in any published document, revision record, or export of project content. A conversation of yours is retained for you even where you later cease to have access to material discussed in it.
• Conversations are retained for a stated period and are then deleted automatically. The period, how it is measured, and what it does and does not cover are stated in our Privacy Policy, which is the authoritative statement of them; these Terms state no period of their own.
• You may delete any of your conversations at any time, and you may copy one out of the Services as readable text. Deletion through the Services takes effect immediately.
• We limit the number of conversations stored for you and the length of a single conversation. The Privacy Policy describes these limits and what happens when one is reached.

4.3 SynC Standards Wiki

The Services include a collaborative wiki ("SynC Standards") where authenticated users may contribute to, edit, and improve construction reference specifications. SynC Standards are governed by the additional terms in Section 5A below.

4.4 Third-Party Integrations

The Services may integrate with third-party platforms and APIs. Your use of these integrations is subject to the third party's terms of service and privacy policies. We are not responsible for the availability, functionality, or security of third-party services. An app or tool you connect to your account with an API key is a third-party service under this Section; Section 4A states what else applies to it.

4.5 Beta and Preview Features

The Services are under active development, and we may make certain features available on an alpha, beta, preview, pilot, or early-access basis ("Beta Features"), whether or not labeled as such. Beta Features are provided for evaluation purposes; they may be modified, suspended, or discontinued at any time without notice, may be subject to additional usage limits, and may contain errors or produce unexpected results. Beta Features are provided "AS IS," are excluded from any availability or support commitment, and your use of them is at your own risk. Feedback you provide on Beta Features is governed by Section 8.5.

4A. API Keys and Connected Apps

4A.1 What they are

The Services include an application programming interface (the "API") and an address at which AI apps and other tools connect to it. Both are part of the Services. You reach them with an API key: a secret the Services issue to you, which an app or tool you use presents on each request. The Services show a key to you once, when it is created or rotated, and then keep it only in a form that cannot be read back. An app or tool that presents your key, whether a developer tool, a script of your own, or an AI app such as a general-purpose assistant, is a connected app in these Terms.

A key is a way of reaching the Services as you. It is not a separate service, and nothing in this Section 4A is sold. Where the Services issue a credential of another kind for the same purpose, this Section applies to it as it applies to a key.

4A.2 They act as you

Everything a connected app does with your key is done by you under these Terms. Section 3.2 applies: you are responsible for it, as you are for anything done under your account. That includes an action an app takes that you did not ask for, an action it takes because it misread content, and an action it takes because text inside content it read told it to. The Services refuse what a key is not allowed to do (§4A.4); they do not judge whether what it is allowed to do is what you wanted.

You choose which apps and tools to trust, and which of your permissions to give them. Give each the least it needs.

4A.3 Keys are credentials

A key is an account credential. Section 3.2 applies to it as it applies to a password. In particular:

• Keep a key secret. Do not put it anywhere another person can read it, and do not send it to SynC or to anyone else.
• If you think a key has been exposed or misused, revoke or rotate it at once in the Services, and tell us as §3.2 requires. Revoking takes effect on the next request; there is no grace period.
• A lost key is replaced by rotating it. SynC cannot show a key again and will not ask you for one.
• Creating or rotating a key requires you to confirm it is you, as our Privacy Policy describes.

4A.4 What a key may do

Never more than you. A key can do at most what you chose for it and what you can do in the Services at the moment of the request, whichever is less. The Services check both on every request. If you lose a seat, leave a company, or lose access to a project, every key you hold loses the same reach on its next request, with no separate step.

A seat to change things. Reading through a key needs no seat. Making changes needs the seat §10.1 describes, exactly as it does in the browser. A lapse under §10.6 reaches your keys as it reaches you.

Some actions are not available at all, and some only when you grant them by name. The Services do not let a key act on your account, security or sign-in settings, manage keys or other connections, act on billing, seats, company membership or roles, or bring a person into a project or appoint who leads it, whatever permissions you chose; those are done by signing in to SynC. Certain other actions, publishing a revision, sharing or distributing a project, deleting something, and moderating, are available to a key only where you ticked that permission by name when you created the key; they start unticked, and a broad permission to make changes does not include them. SynC may add an action to either group, or move one between them, by changing the Services, as §12.2 provides.

Published revisions stay as they are. Nothing done through a key changes a published revision, because nothing does.

4A.5 Using the API and connected apps

Sections 8.4, 9 and 9.2A apply to everything done through a key. In addition, you agree not to:

• sell, rent or resell access to the Services through a key, or offer a key or a connected app as a way for people to reach the Services in place of their own account;
• use more than one key, app, account or company to get around a limit the Services apply to you, or to get around a permission or a setting that stops a key from doing something;
• probe for, or attempt, an action that §4A.4 says is not available to a key;
• harvest content through the Services beyond the limits the Services state for your keys, by any means. The authorized way to read the Services automatically is a key within its limits; §8.4's "without authorization" means outside that. This restricts the use of SynC's systems and nothing else: it adds no condition to the CC-BY-SA 4.0 license on SynC Standards content, and what you may do with a copy you lawfully hold is as §5A.1, §5A.7 and §9.2A state.

A tool one person runs for colleagues who hold their own accounts acts as that person and is within this Section; the key is personal to its holder, who answers for what it does. A breach of this Section is cause for action under Section 16.2, including revoking a key at once.

4A.6 Limits

The Services limit how many requests your keys may make, by the minute and by the day. The limit is yours, across all of your keys and connected apps together, and it is set by whether you hold a seat: a seat holder's limit is higher than the limit for a person without one. The Services state the limit in force for you, and tell an app when it has reached it and when it may continue. SynC may change the limits, and how they are set, at any time, as §12.2 provides.

A higher limit is available to a company only under a written agreement SynC has signed, as §18.1 provides. A higher limit is not a plan, a tier or a seat type, and §10.1's statement that there are no plans or tiers is unchanged by it.

4A.7 Content that leaves the Services

When a connected app reads content with your key, that content leaves the Services and goes to the app, and from there to whoever runs it. You authorized that. So:

• The provider's terms govern what it does. What the app's provider stores, keeps, trains on or shares is governed by your agreement with that provider, not by these Terms. The commitments SynC makes about its own service providers in §5.3.3 do not reach a provider you connect. SynC cannot see, and does not control, what a provider does with content once an app has read it.
• It is a disclosure you authorized. For §5.6 and §14.3, content read by an app or tool you gave your key to is content disclosed to a user you authorized. SynC's confidentiality commitment is kept when SynC gives the content to the app you chose.
• Your obligations to others travel with it. If content you can read is someone else's confidential information, is licensed to you under terms that limit its use with AI features (§5.5), or was shared with you under Section 6 for a purpose, those obligations apply to sending it to an app as they apply to sending it anywhere else. Connecting an app does not change what you may do with content you did not create.
• If a project was shared with you. A connected app of yours may read a project shared with you only where the person who shared it allowed export (§6.1). Reading it through an app is reading it; what else you may do with it is between you and the sharer, as §6.2 and §9.2A state.

4A.8 Your company's controls

A company's administrators can see which of its members hold a key, when each was last used and how much it has been used; they do not see the individual requests. A company's administrators can also switch off access by API keys and connected apps to the company's projects, in which case no key, whoever holds it, can read or change that company's projects until the switch is turned back on. The switch starts on. It does not change who may read the company's projects by signing in, and it does not change a recipient's access or ability to export. Whether a company uses these controls, and who in the company may, is the company's own decision, as §6.4 leaves sharing to it.

A person who shares a project chooses, when creating the share link, whether recipients may export it; that choice also decides whether a connected app of a recipient's may read it (§6.1).

4A.9 Revocation, changes and availability

Yours. You may revoke or rotate a key at any time in the Services. Each takes effect on the next request.

SynC's. SynC may revoke a key, refuse an app, or suspend the API or the address at which apps connect for everyone, as Section 16.2 and Section 12.2 provide. SynC acts at once, without notice in advance, where a key or an app is used in breach of these Terms, or where it poses a risk to the security or integrity of the Services or to any person. SynC need not tell an app's provider anything.

The API changes. SynC may add, change or withdraw an endpoint, a parameter, a tool an app sees, a limit, or a way of connecting at any time, as §12.2 provides. Where SynC can, the Services say so before the change; SynC promises no notice period and no period of continued support for what it withdraws. Build so that a change does not break you.

No availability promise. §12.1 and §13.2 apply to the API and to the address at which apps connect as they apply to the rest of the Services. Either may be offered as a Beta Feature under §4.5. SynC gives no service level, response time or uptime commitment for them, to anyone, by these Terms; a written agreement under §18.1 may give one to the company that signs it.

4A.10 Records

A change made through a key is recorded under your name, as §16.2 states, and marked as made through the API, so that the record shows it was made by you through a tool. Every request made with a key is logged. Our Privacy Policy states what is recorded and kept, for how long, what you can see, and what your company's administrators can see.

4A.11 Disclaimers and liability

Sections 13, 14 and 15 apply to the API, to connected apps, and to what is done through them. In particular, §13.4 and §14.1 apply to a third-party app, to what it does, and to what its provider does with content it received; and your indemnity in §15.1 reaches a claim that arises from an app or tool you gave your key to.

5. User Data and Content

5.1 Your Ownership

You retain ownership of all data, content, specifications, designs, documents, and other materials you create, upload, or submit to the Services ("User Content"), except as otherwise provided in Section 5A regarding SynC Standards contributions and the use of SynC Standards within projects (Section 5A.7).

5.2 License Grant to SynC

By uploading User Content to the Services, you grant SynC a worldwide, non-exclusive, royalty-free, transferable license to:

• Store, process, and transmit User Content to provide the Services
• Display User Content to authorized users within your organization or projects
• Create derivative works as necessary to provide the Services and to operate them as described in §5.3
• Back up and restore User Content for data protection purposes

This license exists only for the duration of your use of the Services and for a reasonable period thereafter to fulfill backup and legal obligations.

5.3 Limits on Our Use of Your Content

Beyond delivering the Services to you, and the legal and business disclosures described in our Privacy Policy, this Section states the only ways SynC uses User Content. It is a limit on our rights, and grants only the uses this Section names.

5.3.1 We Do Not Train Generative or Foundation Models on Your Content, and We May Use It to Improve the Services

We do not use User Content, or any adaptation or excerpt of it, to train, fine-tune or improve any generative artificial-intelligence model, or any general-purpose or foundation model, whether our own or a third party's, and whether or not it has been anonymized, de-identified or aggregated. We do not license, sell, publish or otherwise disclose User Content to any third party for those purposes.

Removing names or other identifying details from a specification does not change its confidential status. De-identified User Content remains your confidential information, and a project specification remains your confidential work product under §5A.7.2.

This Section applies to all User Content, whenever submitted, including content submitted before this version took effect.

Operational models. We may build and use models that classify, score, match, rank, or detect anomalies in content within the Services — for example, identifying what kind of value a datasheet field holds, flagging a likely duplicate, or detecting an entry outside its normal range. A model of this kind falls outside the prohibition above only if all of the following are true:

• it produces classifications, scores, labels, rankings or similar structured outputs, and does not generate natural-language or free-text output;
• it is used only to operate the Services, and is not distributed, licensed, sold, or otherwise made available outside them; and
• neither the model nor its outputs reproduce, or disclose the substance of, your User Content to any person not already authorized to see that content.

Where such a model is developed using content from more than one customer, we use it only to operate the Services, and never to disclose one customer's content, or any excerpt of it, to another.

Improving the Services. We may use what you upload, and what the Services produce from it, to evaluate and improve the Services: to find out why a result was wrong and put it right, to make the Services read documents and answer questions better, and to measure how well they do. Your content remains your confidential information under §5.6. We do not sell or license it, we do not use it to train, fine-tune or improve any generative, general-purpose or foundation AI model, and nothing we build from it reproduces, or discloses the substance of, your content to anyone not already permitted to see it. Our service providers process it only on our behalf, under §5.3.3. Improving how the Services use a model (what they ask it, what they send it, and how they check its answers) is improving the Services, not the model. A model we build from your content is used only within the Services; we do not sell or license it. A project's administrator can opt that project out, in the project's settings or, until that setting is available, by asking us at privacy@synergyinconstruction.com; a company administrator can set the default for the company's new projects. From an opt-out we stop using that project's content this way and delete the copies we kept of it for this purpose. What the Services learned from it before then stays learned: we cannot take it back out of something already built, and we do not say that we can.

Exception by written agreement. We may use your User Content in a way this Section otherwise prohibits only under a separate written agreement that you execute and that identifies the content and the use. Your acceptance of these Terms is not such an agreement, and we will not require such an agreement as a condition of providing the Services to you.

This Section does not restrict:

(a) Content you offer for inclusion in the SynC Standards library. If you submit content for the purpose of having it included in a published Standard — for example a suggested change containing proposed text — that submission is a Contribution governed by the Contributor License Agreement, not by this Section. Consistent with that Agreement, whether something is a Contribution turns on the purpose for which it was submitted — content offered for inclusion — and not on the channel used to submit it.

Content you write inside your own project for your own project's participants is not a Contribution, and does not become one because it concerns a Standard you imported.

(b) Feedback you direct to SynC, including a report of an error in a published Standard, which is governed by §8.5.

(c) SynC Standards content as published in the public SynC Standards library, which is licensed under CC-BY-SA 4.0. This does not permit us to read that content out of your private project.

(d) The usage and structural statistics described in §5.3.2.

5.3.2 Usage and Structural Statistics

We collect and analyze how the Services are used, and structural measurements derived from content, in order to operate and improve the Services. This includes counts, frequencies, distributions, timings, error rates, and feature-utilization patterns — for example, how many datasheets a project contains, how often a value is deferred to the drawings, how often a publish is blocked because a component is out of date, or how frequently a given field name appears across the platform.

These are measurements about content. They do not include, and may not be used to reconstruct, the text of your specifications or any other User Content. Where a statistic could identify an individual customer, we report it only in aggregate.

5.3.3 Processing by Our Service Providers

Delivering AI-assisted features and search requires transmitting the content you are working with to service providers that perform inference and text-embedding on our behalf. We do not permit those providers to retain your content for their own purposes or to use it to train their models. The same applies to the facts about you that the Services send with a request, as described in our Privacy Policy §4.1A. We enforce this in two ways, depending on how a request reaches a provider. Where a request is sent to a provider directly, on our own account with it, we rely on that provider's terms with us and its published data-handling terms, which are linked from the subprocessor list. Where a request is routed through a routing service, requests are restricted to hosts we have vetted, hosts identified as retaining or training on submitted content are excluded from serving them, and a request fails rather than proceed if no host satisfies those constraints; those hosts are suppliers of the routing service, and we rely on that configuration and on each host's published data-handling terms. The subprocessor list states which providers we may use and how a request reaches them.

The providers we may use and the specific controls we apply are disclosed in our Privacy Policy and on the subprocessor list it references, which links each provider's own documents stating where it processes content; all of these change from time to time. We may change providers, hosts or mechanisms. If a change materially reduces the protections described in this Section, we will give at least thirty (30) days' notice under §18.2 before the change takes effect.

If your engagement requires zero-data-retention processing or a restricted set of processing jurisdictions, contact privacy@synergyinconstruction.com.

This Section is about providers that process content on SynC's behalf. It does not apply to an app or tool that you, or a recipient you share with, connect to a SynC account with an API key (Section 4A). Such an app is provided by a third party under that third party's terms, SynC has no agreement with it about your content, and SynC does not control what it keeps or trains on. What a connected app may read is controlled by the person's own permissions and the permissions on the key, by the sharer's export setting (§6.1), and by the company switch (§4A.8). §4A.7 states this in full.

5.4 Representations and Warranties

You represent and warrant that:

• You have all necessary rights, licenses, and permissions to upload User Content
• User Content does not infringe any third-party intellectual property rights
• User Content does not contain unlawful, harmful, or malicious content
• You comply with all applicable laws in creating and uploading User Content

5.5 User Content Restrictions

You agree not to upload User Content that:

• Violates any applicable law or regulation
• Infringes intellectual property rights of others
• Contains viruses, malware, or harmful code
• Impersonates any person or entity
• Contains confidential information belonging to third parties without authorization
• Reproduces a proprietary master specification library, or other content licensed to you by a third party, beyond what your license from that third party permits, including any limit that license places on storage outside your own systems, on who may access the content, or on its use with AI features. Project specifications you prepare from such content under that license are not affected by this restriction.

5.6 Confidentiality of User Content

SynC holds your User Content in confidence. SynC discloses it only as these Terms and our Privacy Policy allow: to the users you authorize and the recipients you share it with under Section 6; to an app or tool that a user, or a recipient you share with, has connected to their own account with an API key, at that person's direction and within the access they hold, as Section 4A and Section 6 describe; to the service providers that process it on our behalf under §5.3.3 and as our Privacy Policy describes; and where the law requires, as our Privacy Policy states. SynC's staff and contractors access User Content only to operate, support, secure and improve the Services as §5.3.1 states, and to answer a request you make. The limits in §5.3 on our own use of User Content are part of this commitment. Content that is public by its nature is outside it: SynC Standards content in the public library, your company's public profile, and anything you or a recipient publish outside the Services.

Measures. The technical and organizational measures our Privacy Policy describes in its Section 6 are the means by which SynC keeps this commitment, and SynC applies them to User Content as it applies them to personal information. This Section is a commitment about disclosure: that User Content is not read by, or disclosed to, anyone these Terms and our Privacy Policy do not allow. It is not a warranty that the Services will be available, that User Content is backed up, or that User Content will not be lost, corrupted or unavailable. Those matters are governed by §12.1, §13.2 and Section 14. Files you upload are copied each night to a backup, on the schedule and for the periods our Privacy Policy states in its Section 5.1. That sentence describes what SynC runs. It is not a promise that a copy exists for every file at every moment, or that a file can be restored from it, and it does not move the loss or unavailability of a file out of §12.1, §13.2 and Section 14. Keep your own copy of any file you cannot afford to lose.

If a security incident exposes your User Content. Where SynC confirms that a security incident has resulted in your company's User Content being read by, or disclosed to, a person not authorized to see it, SynC notifies your company without undue delay after confirming it, by email to the addresses of your company's administrators, and tells your company what SynC knows: what was exposed, when, what SynC has done about it, and what SynC recommends your company do. This notice is owed whether or not personal information was affected, and is separate from the notice our Privacy Policy gives where personal information is. It is not owed for an attempt that did not succeed, for access by a user you authorized, or by a recipient, or by an app or tool a user or a recipient connected under Section 4A, within the access and the export setting you granted under Section 6, or for a disclosure the law compelled and forbade SynC to tell you about.

5A. SynC Standards Wiki

5A.1 The SynC Standards Wiki

The Services include the SynC Standards Wiki ("SynC Standards"), a collaboratively maintained library of construction reference specifications. This Section 5A applies to all users of the Services, whether or not you contribute to SynC Standards.

SynC Standards are contributed by users of the Services and are licensed to the public under the Creative Commons Attribution-ShareAlike 4.0 International License (CC-BY-SA 4.0). Because SynC Standards are openly licensed, anyone — including users who have never contributed — may use, share, and adapt them, subject to CC-BY-SA 4.0. When SynC Standards content, or an adaptation of it, is redistributed to the public, the redistributor must give attribution to contributors and license the publicly redistributed version under CC-BY-SA 4.0. Use of a SynC Standard within a project is addressed in §5A.7.

5A.2 Contributions Are Governed by the Contributor License Agreement

If you contribute to SynC Standards, your contribution is governed by SynC's separate Contributor License Agreement ("CLA"), which you accept at the time you submit a contribution. The CLA — not these Terms — sets out the terms that apply to contributions, including:

• the license you grant in your contribution (CC-BY-SA 4.0), the additional permission to use a SynC Standard within a single construction project, and the additional license you grant to SynC to operate and develop the Services;
• SynC's editorial and moderation rights in respect of contributions;
• your representations and warranties, including that your contribution is your original work, that you have the right to contribute it, and the terms that apply to AI-assisted content;
• how contributor attribution is displayed, preserved, and anonymized, including following deletion of your account;
• the irrevocability of your license grant and its survival after your account is closed; and
• your indemnification obligations.

To the extent of any conflict between these Terms and the CLA with respect to contributions, the CLA governs. These Terms do not restate or modify the CLA, and nothing in this Section 5A grants SynC any right in a contribution beyond what the CLA grants. You are not required to contribute, and you do not accept the CLA unless and until you submit a contribution.

5A.3 Moderation and Editorial Rights

SynC reserves the right to:

• Review, edit, modify, or remove any contributed content at its sole discretion
• Establish and enforce editorial standards, formatting requirements, and quality guidelines
• Reject contributions that do not meet community standards or quality requirements
• Suspend or revoke wiki contribution privileges for users who violate these Terms

These editorial and moderation rights operate alongside, and do not limit, SynC's rights under the CLA. As between these Terms and the CLA, the rights exercised over a contribution are those granted by CLA §2E; this Section describes them for the benefit of all users of the Services and adds nothing to them.

5A.4 Attribution

SynC Standards display contributor attribution as required by the CC-BY-SA 4.0 license. The treatment of contributor attribution — including how it is recorded, preserved, and anonymized following deletion of a contributor's account — is governed by the CLA.

5A.5 Disclaimer

SynC Standards are reference specifications developed collaboratively by construction professionals. They are not engineering judgments, professional recommendations, or substitutes for the independent professional judgment of a licensed engineer. Users are solely responsible for verifying the suitability of any standard for their specific project, jurisdiction, and application. Contributors are not liable for downstream use of their contributions.

5A.6 Errata, Holds, and Revocation of Adopted Revisions

5A.6.1 Adopted Revision Immutability

Once a SynC Standards Wiki revision has been formally adopted, its content is immutable. The platform stores adopted revisions as permanent records that cannot be edited, only superseded by later adopted revisions. Projects may import specific adopted revisions as fixed references, and the Services preserve those references, subject to §5A.6.3. A hold withholds identified clauses of a standard, or the standard as a whole, from view while a notice is open, on every adopted revision that carries them; the adopted revisions stay published, and a hold is distinct from a revocation, which withholds one adopted revision. Where material within an adopted revision is placed under a hold, or the revision is revoked, the reference is preserved and the material under notice is withheld from display for as long as the hold or revocation stands.

5A.6.2 Errata Annotations

Notwithstanding the immutability principle in §5A.6.1, SynC reserves the right to issue errata — public, non-destructive annotations attached to an adopted revision — at its sole discretion when an error or other issue is identified after adoption. Errata do not modify the content of the adopted revision; the original content remains intact. Errata are displayed as banners or other visual indicators on every page that references the affected adopted revision, including in projects that have already imported the affected revision.

By using the Services, you acknowledge and agree that:

• Errata may appear on adopted revisions you have imported into your projects after the import has occurred.
• The platform will display errata banners alongside your imported content, including in projects you have shared and to share-link recipients who have accepted access (see Section 6).
• Errata are intended as protective annotations to alert readers (including downstream users of your projects) to known issues; they do not unilaterally remove or alter the imported content itself.
• The decision to act on errata — for example, by upgrading your project to a corrected adopted revision — remains yours.

5A.6.3 Holds and Revocation in Extraordinary Circumstances

In extraordinary circumstances, SynC reserves the right to place a SynC Standard, or identified clauses within one, under a hold, and to revoke an adopted wiki revision. A hold withholds the material under notice from public view and from project specifications that reference it, on every adopted revision that carries that material; the adopted revisions themselves remain published. A revocation removes one adopted revision from public view and from project specifications that reference it. A hold is the ordinary exercise of this authority, and a revocation is the exceptional one. A SynC moderator is a person SynC has appointed to moderate the SynC Standards, whether or not that person is SynC staff; their acts under this Section are SynC's. Both instruments are exercised as narrowly as possible and are reserved for situations including but not limited to:

• Compliance with valid legal process (court orders, subpoenas, regulatory directives)
• Response to copyright takedown notices, including but not limited to notices issued under the Digital Millennium Copyright Act ("DMCA")
• Compliance with data-protection law, including but not limited to erasure requirements under the General Data Protection Regulation ("GDPR") or analogous statutes
• Removal of content found to constitute a credible threat to public safety
• Other circumstances in which retention of the adopted revision would expose SynC, its users, or the public to material legal or safety risk

SynC acts on the material a notice identifies. Where a notice or other basis identifies particular clauses of a standard, SynC places its hold on those clauses and not on the rest of the standard. The clauses under notice are replaced, where they sit, by a statement that material has been withheld, and the rest of the standard continues to render normally on every surface. Where the basis cannot be placed at clause level, or reaches most of a standard, SynC places its hold on the standard as a whole, which withholds every clause of it on every adopted revision. SynC does not act on a project revision as a whole; §5A.6.6 states what is unaffected.

A hold attaches to a position in a standard, not to particular words. It reaches every adopted revision that carries that position, including adopted revisions published after the hold was placed, and editing the material does not end it. A hold on a standard as a whole reaches every adopted revision of that standard, and moving a project to another adopted revision of it does not clear the hold. A hold ends only when a SynC moderator lifts it, or releases it from a stated adopted revision onward, in which case that revision and every later one are clear and earlier ones remain held. While a hold stands on a standard, no new revision of that standard is adopted. §5A.6.8 states what you may do inside your own project while a hold stands.

Holds and revocation are not an editorial mechanism. SynC uses them only where withholding the material itself is the object: legal compulsion, a copyright or other legal notice, a data-protection erasure obligation, or a credible safety risk. Errors of quality, accuracy, scope or formatting are addressed under §5A.6.1 and §5A.6.2, by a corrected adopted revision or by an erratum.

When SynC places, narrows, releases or lifts a hold, or revokes or restores an adopted revision:

• The action is logged in the public moderation log with the actor identified as the platform and the reason category recorded, except where prohibited by law or court order.
• Project owners and administrators of affected projects, the author of the revision the notice identified, the other contributors to the affected standard and, where an adopted revision is revoked or restored, the contributors to that adopted revision, are notified through the platform's notification system and by email, except where prohibited by law or court order. Where the action responds to a copyright notice, the notification to the author and to project administrators states that a counter-notification may be sent (§5B.4), and the author receives by email the copy of the notice that §5B.4 describes.
• Where lawful and practicable, SynC will publish a brief notice of the action. The notice takes a fixed form: what SynC did, what it reached, the level applied under §5A.6.6, and the date, in wording drawn from a published vocabulary. SynC does not publish the free-text note a moderator records internally, on any surface or at any level. SynC may also publish a statement of its own about a particular action. Such a statement is SynC's own speech under §5A.6.5, is not owed, and may be withdrawn. SynC may omit the notice or limit its content where required by law, court order, or where publication would itself create legal exposure.
• Where the action arises from copyright or content-validity concerns rather than legal compulsion, SynC will, where practicable, retain a non-public copy of the withheld or revoked content for the period required to satisfy applicable legal-hold or audit obligations. Our Privacy Policy states how that copy is treated.

What the public moderation log contains. Each entry records the action taken, its date, the reason category, the level applied, the standard and adopted revision it reached while those remain published, and, where the action reached identified clauses, how many clauses and their section numbers within the standard. Each entry has an address of its own and lists the other entries in the same matter, so that a reader sees the course of an action and not a fragment of it. The log does not identify the moderator who acted, the person or organization who reported the material, the author of the material, or any project that holds it. It does not carry the text of anything withheld, and it does not carry any free-text note. Where a standard is no longer published, the section numbers of clauses within it are withheld with it. Entries are not deleted when the material they describe is removed. Our Privacy Policy states how they are retained.

5A.6.4 Limits on SynC's Exercise of This Authority

The errata, hold and revocation authority in this Section 5A.6 is SynC's own platform authority, and this Section states its limits. Errata may appear on, and a hold or revocation may affect, adopted wiki revisions that have been imported into projects, including projects that have been shared with recipients under Section 6. SynC will exercise this authority only in the circumstances described in §5A.6.2 and §5A.6.3, and will not use it to remove or alter content within a customer's project, or to restrict what a customer may do with a standard within their project (§5A.6.8), for ordinary commercial or editorial reasons. Whether a recipient's access to a shared project continues is a matter between the project owner and the recipient under Section 6; nothing in this Section 5A.6 gives SynC any additional right to control, grant, or remove a recipient's access to a shared project.

5A.6.5 No Liability for Erratum or Revocation Action

You acknowledge that SynC's exercise of errata, hold or revocation authority under this section is a protective measure for the user community, the public, or to comply with applicable law. To the maximum extent permitted by law, SynC is not liable to any user, contributor, project owner, project administrator, or share-link recipient for any consequence of an erratum being issued, a hold being placed, maintained, narrowed, released or lifted, or an adopted revision being revoked or restored, including but not limited to: changes to the appearance of imported content, material being withheld from a project specification or from a published project revision, project workflow disruption, the inability to customize or to adopt a revision of an affected standard, downstream notification obligations between you and your share-link recipients, or any business impact resulting from a published erratum, hold, or revocation notice.

Errata issued by SynC as the platform are the platform's own speech, and SynC is responsible for their accuracy as such. Errata issued by community administrators through the wiki errata mechanism are community speech hosted and moderated by SynC; SynC's responsibility for community-issued errata is limited to its role as host and moderator.

SynC's exercise of any authority under this Section 5A.6 is not a representation or statement by SynC about the accuracy, quality, originality, or lawfulness of any content, or about the conduct of any contributor, project owner, or other person. A moderation log entry, and any statement SynC publishes about an action under §5A.6.3, record what SynC did and the category under which it acted. They state nothing about whether any person did anything wrong, and are not to be read as if they did.

5A.6.6 Levels: the Reference Hold and the Full Hold

A hold or a revocation takes effect at one of two levels. SynC records the level on the action and publishes it in the moderation log.

Reference hold (level 1). The material under notice stops leaving the Services. Wherever it would have appeared, the Services show in its place a statement that material has been withheld and a link to the moderation log entry: on the wiki page, its permalink and its history; to members of a project that imported it; to share-link recipients, including those who received access by forwarding; in exports in every format; in search results and snippets; in citation resolution; and through programmatic access, including the API and AI chat. Within an affected project, users with administrator authority over that project keep, for the period stated in §5A.6.7 and no longer, a read-only on-screen reference view of the material under notice, marked as under notice, with export, copying and customization of that material removed. The reference hold is the default.

Full hold (level 2). Everything above applies, and the reference view is withdrawn as well. The material is replaced by the same statement for every reader, including the project's own administrators. SynC applies a full hold from the outset only where it is compelled by law or court order, or during the period after a counter-notification in which the complaining party may file suit. A reference hold also becomes a full hold when the period stated in §5A.6.7 ends.

At either level, the rest of your project is unaffected. A hold or revocation reaches the material under notice and nothing else. Your project remains yours, remains readable, and remains shareable and exportable. The material under notice travels with it, marked.

5A.6.7 How Long the Reference View Lasts, and How Long a Hold Lasts

These are two different periods. This Section states both, because the first is easily mistaken for the second.

The reference view is bounded. The reference view described in §5A.6.6 lasts until the earliest of:

• the project moving to an adopted revision that is clear of the notice;
• thirty (30) days after a corrected revision becomes available or, where the hold is on identified clauses, thirty (30) days after SynC releases those clauses from a stated adopted revision onward; and
• ninety (90) days after the action opened, whether or not a corrected revision is ever produced.

At the end of that period the full hold applies and the reference view is withdrawn. The period runs the same way whether the action reaches an adopted revision or identified clauses within one. SynC notifies project owners and administrators before the period closes.

The hold itself is not bounded. The period above governs only how long a project's administrators keep their reference view. It does not lift, narrow, shorten or end a hold. A hold ends when a SynC moderator lifts it or releases it, and not before. That may be sooner than thirty days or later than ninety, and a hold may stand indefinitely. Nothing in this Section gives you a right to have a hold lifted, or to have material restored at the end of any period.

5A.6.8 What a Hold Does Inside Your Project

While a hold or revocation under §5A.6.3 stands on a SynC Standard your project has imported:

• You may publish a project revision after acknowledging the hold. Before publishing a revision that contains material under a hold, the Services show the person publishing what is withheld: which standards, at what level, and how many clauses. Publishing proceeds once that person has acknowledged it. SynC records the acknowledgment against the published revision: who acknowledged, when, which standards, at what level, and how many clauses. The withheld-material statements are not written into the revision you publish. They are applied when the revision is read, so if SynC later lifts the hold, the material appears again in the revision you already published, with no republication and no action by you. The stored content of a published revision, and any integrity record computed over it, are unchanged by a hold in either direction.
• Distribution and export continue. Share links stay live, forwarded access is unaffected, and exports in every format continue to work. Each carries the withheld-material statement where the material sat.
• You may not customize the affected standard while a hold on the whole of it, or a revocation, stands. Where the hold reaches particular clauses, you may customize the standard. The withheld clauses stay withheld in your customized copy.
• No new revision of the affected standard is adopted while the hold stands. A corrected revision therefore does not become available to your project until a SynC moderator lifts the hold or releases it from a stated adopted revision onward (§5A.6.3).
• You have three ways to leave a hold behind inside your project. You may move your project to an adopted revision that a SynC moderator has released from the hold, where one exists. You may remove the affected standard from your project, or replace it with another. Or, in a customized copy of the standard, you may write your own text into the withheld clause. The Services do not show you the withheld text while you do so. Once you save, your copy no longer carries the hold. SynC records the replacement: who made it, which clause, and when. SynC makes no judgment about the text you wrote. None of these lifts the hold on the standard itself, or for anyone else. Only a SynC moderator lifts or releases a hold.
• Every other standard in your project, and every other part of it, is unaffected. It may be edited, customized, published, shared and exported as usual.

Whether to publish a revision that carries withheld material is your decision and not SynC's. Nothing in this Section requires you to publish one, and nothing in it gives any recipient of your project a right to have material restored.

5A.7 SynC Standards Imported into Projects

5A.7.1 Importing a SynC Standard

The Services allow you to import an adopted revision of a SynC Standard into a project as a starting specification. Importing copies the content of that adopted revision into your project. The adopted revision itself remains available in the public SynC Standards Wiki under CC-BY-SA 4.0 and is not altered, restricted, or removed by your import. Your use of a SynC Standard within a project is supported both by CC-BY-SA 4.0 and by the additional project-use permission that contributors grant under the CLA, and is available to you whether or not you have contributed to SynC Standards.

5A.7.2 The Project Specification

Within a project, you may configure an imported SynC Standard using its built-in datasheet fields, edit its content, and add project-specific requirements. The resulting project specification is your confidential work product. It is private to the project and accessible only to users you authorize and to share-link recipients in accordance with Section 6. Your configuration choices, edits, and project-specific additions are your User Content under §5.1. The SynC Standards content embedded in the project specification remains licensed under CC-BY-SA 4.0; your use of that content within the project is governed by §5A.7.3 and §5A.7.4.

Where a hold or revocation under §5A.6 reaches a standard you have configured, the values you entered remain yours, are retained, and remain visible to you and to every reader of your project at either level. They are your User Content and are not the material under notice. The field labels and units that make those values readable stay visible with them, at either level. The standard's guidance and descriptive text is withheld with the rest of the material under notice.

Your project specification is not used to train generative or foundation models. §5.3.1 states how SynC may use it to improve the Services, and how a project's administrator opts the project out.

5A.7.3 Project Use Is Not Public Redistribution

The ShareAlike and attribution conditions of CC-BY-SA 4.0 are triggered when licensed material, or an adaptation of it, is shared with the public. Importing a SynC Standard into a project, configuring and editing it, and using the resulting project specification within that project — including providing it to the owner, design team, contractors, suppliers, and other identified participants of that project, and submitting it to an authority having jurisdiction for review or permitting — is use of the Standard within a defined project and does not, by itself, constitute making an adaptation available to the public. A project specification used in this manner is not required by CC-BY-SA 4.0 to be published or to be licensed under CC-BY-SA 4.0, and you may treat it as confidential, subject to §5A.7.4.

5A.7.4 Public Distribution Remains Subject to CC-BY-SA 4.0

If you make a SynC Standard, or an adaptation of one (including a project specification derived from a SynC Standard), available to the public — for example by posting it on a publicly accessible website or procurement portal, or otherwise distributing it to the public at large — that distribution is governed by CC-BY-SA 4.0. You must attribute the contributors and license the publicly distributed version under CC-BY-SA 4.0. This obligation applies to the SynC Standards content and adaptations of it; it does not extend to other User Content in your project that is independently authored by you and not derived from a SynC Standard. Nothing in this Section permits you to apply additional restrictions to, or to claim proprietary ownership of, the SynC Standards content itself, as distinct from your own configuration choices, edits, and project-specific additions.

5A.7.5 Attribution of Imported Standards

SynC may display contributor attribution on SynC Standards content imported into projects, including by identifying the source adopted revision. This preserves the attribution and licensing record required by CC-BY-SA 4.0 and is consistent with the Contributor License Agreement.

5B. Copyright Infringement Claims (DMCA Policy)

5B.1 Respect for Intellectual Property

SynC respects the intellectual property rights of others and expects users of the Services to do the same. We respond to notices of alleged copyright infringement that comply with the Digital Millennium Copyright Act ("DMCA"), 17 U.S.C. § 512, and we will remove or disable access to material claimed to be infringing in accordance with this Section.

5B.2 Designated Copyright Agent

Notices of claimed copyright infringement should be sent to SynC's Designated Copyright Agent by email:

Copyright Agent Synergy In Construction, LLC Email: legal@synergyinconstruction.com Subject Line: "DMCA Notice"

The Designated Copyright Agent's current contact details, including any mailing address required to be registered with the United States Copyright Office, are as recorded in the Copyright Office's Directory of Designated Agents.

5B.3 Filing a DMCA Notice

To be effective under 17 U.S.C. § 512(c)(3), your notice must include:

• A physical or electronic signature of the copyright owner or a person authorized to act on the owner's behalf
• Identification of the copyrighted work claimed to have been infringed (or, if multiple works are covered by a single notice, a representative list)
• Identification of the material claimed to be infringing, with information reasonably sufficient to permit us to locate it (for SynC Standards content, the URL or standard identifier and revision)
• Your contact information (name, address, telephone number, and email address)
• A statement that you have a good-faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law
• A statement that the information in the notice is accurate and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner

Under 17 U.S.C. § 512(f), any person who knowingly materially misrepresents that material is infringing, or that material was removed by mistake, may be liable for damages.

What happens to your notice. Where your notice identifies material in the SynC Standards library and SynC acts on it, SynC emails the author of the identified revision a copy of the notice as SynC received it, with your postal address, telephone number and email address removed. Your name, or the name of the organization on whose behalf you act, stays in the copy, and so does everything else the notice contains: SynC does not summarize or characterize it. The copy is sent with a fixed statement that the notice is your statement and not SynC's, and that SynC has made no finding on it. Where SynC has no email address for the author, no copy is sent, and SynC records that. SynC does not provide the removed contact details to the author, except as the law requires, and may disclose the notice in full where the law requires. This paragraph does not apply to a notice about material stored in a project, which is handled under §5B.5 and Section 16.2. If a counter-notification is received, it is forwarded to you as §5B.4 states.

5B.4 Counter-Notification

If material you posted was removed or disabled in response to a DMCA notice and you believe the removal was the result of mistake or misidentification, you may submit a counter-notification to the Designated Copyright Agent containing the elements required by 17 U.S.C. § 512(g)(3), including: your physical or electronic signature; identification of the removed material and its prior location; a statement under penalty of perjury that you have a good-faith belief the material was removed as a result of mistake or misidentification; your name, address, and telephone number; and a statement consenting to the jurisdiction of the federal district court for your judicial district (or, if outside the United States, the United States District Court for the Middle District of Florida) and that you will accept service of process from the person who filed the original notice. Upon receipt of a valid counter-notification, we will forward it to the original complainant and may restore the removed material in 10 to 14 business days unless the complainant notifies us that they have filed a court action seeking to restrain the alleged infringement.

Where SynC disables access to material you contributed to the SynC Standards library in response to a copyright notice, the notice SynC sends you under §5A.6.3 states that it has done so and that you may send a counter-notification under this Section. SynC also emails you a copy of the copyright notice as SynC received it, with the complaining party's postal address, telephone number and email address removed and the complaining party's name or organization kept, so that you can decide whether to counter-notify knowing what was claimed and by whom. The copy goes by email only: the notification you see in the Services says that a copy has been emailed to you and does not carry the notice's text. Where SynC has no email address for you, no copy can be sent. The copy is the complaining party's statement and not SynC's; SynC has made no finding on it, and the statement sent with it says so. That statement and the copy are sent to you privately. They are not published, and the public moderation log continues to identify neither the person who reported material nor its author (§5A.6.3); providing the copy to you is not publication. Neither the statement nor the copy is a view by SynC on the merits of the copyright notice. If you send a counter-notification, it is forwarded to the party who sent the notice with the name, address and telephone number it contains, as 17 U.S.C. § 512(g)(2)(B) requires.

5B.5 Repeat Infringer Policy

SynC maintains and implements a policy for the termination, in appropriate circumstances, of users who are repeat infringers. This Section states how it works.

What counts. A copyright notice counts against the author of the material it identified once the notice has stood: SynC acted on it, and either no counter-notification was received within the period stated in §5B.4, or the complaining party notified SynC that it had filed a court action, or SynC otherwise recorded the notice as upheld. A notice that was deficient, that the complaining party withdrew, or after which the material was restored following a counter-notification does not count. SynC keeps an internal record of each notice it receives and of its outcome, which records the author of the material identified; the Privacy Policy states what the record holds and how long it is kept. It does not hold the complaining party's name or the notice's text, and it is not published.

The ordinary consequence. When the notices standing against a user reach the number SynC's policy sets, which may be as low as one, SynC suspends that user's ability to contribute to the SynC Standards Wiki: creating, editing and moderating wiki content, however the user reaches the Services, including through the API and the AI assistant. The suspension reaches nothing else: the user can still sign in, read the wiki, and use their projects, datasheets and their company's work as before. What the user contributed before stays published under its license, with its attribution. SynC notifies the user in the Services and by email; that notice cannot be switched off. The suspension is recorded privately and does not appear in the public moderation log. A SynC site administrator may lift a suspension and records the reason for doing so; a user who believes a suspension was applied in error, or who wants it reconsidered, may write to legal@synergyinconstruction.com. Lifting a suspension does not remove any notice from the record.

Termination. Suspension of contribution privileges is SynC's ordinary first response and not the limit of this policy. SynC will terminate the account of a user, or of a company, in appropriate circumstances, which include: where a further copyright notice stands against a user after a suspension, whether it concerns material in the SynC Standards Wiki or material stored in a project; where the notices standing against a user reach a number that shows the suspension has not answered the conduct; where the infringement is flagrant, which may justify termination on a first notice; and where a user creates or uses another account to avoid a suspension or a termination. This policy reaches every part of the Services in which material is stored at a user's direction. A copyright notice about material stored in a project, rather than in the SynC Standards Wiki, is recorded under this policy and acted on under §5B.3 and Section 16.2; it is not counted toward the automatic suspension described above, which concerns wiki contribution only. Section 16.2 states SynC's rights of suspension and termination generally, including the right to suspend any part of the Services, and nothing in this Section narrows them.

5B.6 Relationship to Wiki Moderation

Where the material subject to a DMCA notice is an adopted SynC Standards revision, access to that material may be disabled through the hold or revocation mechanism described in §5A.6.3, including its logging and notification practices and the levels and periods described in §5A.6.6 and §5A.6.7. Where a notice identifies particular clauses, SynC places a hold on those clauses rather than revoking the adopted revision that contains them. A notice that does not identify the material with the specificity §5B.3 requires is deficient. SynC may ask the complaining party for that identification, and may do so before, during or after acting on the notice. Disabling access to, or removal of, contributed material under this Section does not limit SynC's rights, or a contributor's obligations (including indemnification), under the Contributor License Agreement.

6. Project Sharing and Distribution

6.1 Share Links

The Services allow you to create share links to grant other users access to your projects. When creating a share link, you may specify:

• The level of access granted (Viewer, Editor, or Administrator)
• Whether recipients may export the shared project through the Services; the same choice decides whether an app or tool a recipient has connected to their account with an API key may read it (§4A.7)
• Forwarding limits (whether recipients may re-share with others)
• Expiration dates for the share link

A recipient's export setting cannot be broadened by forwarding: access forwarded from a share link carries at most the export setting of the link it came from. Separately, an administrator of the company whose project it is may switch off access by API keys and connected apps to all of the company's projects (§4A.8); that switch does not change a recipient's access or their ability to export.

6.2 Access Duration and Removal

When a recipient accepts a share link, the recipient is granted access to the shared project at the access level you selected. That access is not permanent. It continues until it ends under this Section:

• You may remove a recipient's access at any time. Removing a recipient's access ends that recipient's ability to view and interact with the shared project through the Services from the moment of removal. You do not need the recipient's consent, and you do not need to give a reason.
• Revoking a share link prevents new recipients from accepting it. Revoking a share link does not, by itself, remove access from recipients who have already accepted; removing a recipient's access is a separate control.
• Deleting a project ends all recipients' access to it, from the moment of deletion. A deleted project can be restored by a user with authority over it for a limited period, which our Privacy Policy states. Restoring a project returns the access recipients held before it was deleted. Whether to restore a project is entirely the decision of the users with authority over it: nothing in these Terms requires you to restore a project, requires SynC to restore one, or gives a recipient any right to have one restored.

What removal cannot do. Removing a recipient's access ends their ability to view the project through the Services. It does not, and cannot, retrieve copies of project content that the recipient exported, downloaded, or printed while their access was active. This reflects the practical reality of construction document distribution: requirements that have been transmitted cannot be recalled from a recipient's own records.

If you are a share-link recipient. Your access to a shared project exists at the discretion of the project owner and may be removed at any time, without advance notice to you and without cause. Nothing in these Terms grants a recipient any right to continued access to a shared project, or any right to export it, and SynC has no obligation to any recipient to maintain, restore, or preserve access to a project shared with them. Whether you may export the shared project through the Services is controlled by the party who shared it with you (§6.1). If your work requires a durable record of project content shared with you: where export is available to you, make that record while your access is active; where it is not, request what you need from the party who shared the project with you. These Terms do not grant you any right to copy or retain project content beyond the access and export the sharer has enabled, and any record-keeping arrangement is a matter between you and the sharer. If you connect an app or tool to your account with an API key (Section 4A), it may read a project shared with you only where the sharer's export setting allows it, and only within the access you hold. The app acts for you. You are responsible for the app you connect and for what its provider does with content the app reads; SynC has no agreement with that provider about the content, and §5.3.3 does not apply to it. Connecting an app does not enlarge what you may do with content shared with you (§9.2A). Access that ended because a project was deleted may resume if that project is later restored, and you will not be notified either way. That is the project owner's decision and not a right of yours; do not rely on it. The guidance above is unchanged: make the record you need while your access is active. Separately, material within a project shared with you may at any time be replaced by a statement that SynC has withheld it under §5A.6. You will not be notified; the notice goes to the project's owners and administrators. That is outside the sharer's control as well as yours, and it is a further reason to make the record you need while your access is active.

Limitation: platform-level moderation of wiki content. The access controls in this Section govern the relationship between you and your recipients. Separately, SynC may issue errata on, place a hold on material within, or in extraordinary circumstances revoke, adopted wiki revisions that your project has imported. A hold or revocation does not end anyone's access to your project and does not change who may read it. Your share links stay live, recipients keep the access you gave them, forwarded access is unaffected, and your exports continue to work. What changes is that the material under notice is replaced, where it sits, by a statement that material has been withheld: for your recipients, in your exports, and, under a full hold, for you as well. See §5A.6 for the scope and limits of that authority, for what each level does, and for the periods involved.

6.3 Forwarding and Delegation

Recipients with appropriate permissions may forward access to additional users through child share links, subject to:

• Forwarding depth limits set by the original sharer
• The access level and restrictions of the parent share link
• Expiration and revocation of the parent share link (which prevents new child link creation)

6.4 Sharer Responsibilities

When sharing projects, you are solely responsible for:

• Selecting the appropriate access level and recipients
• Choosing whether recipients may export the shared project, understanding that an exported copy, and a copy read by an app or tool a recipient has connected to their account, is outside the control of the Services and cannot be retrieved by removing the recipient's access (§6.2, §4A.7), and that an app a recipient connects is provided by a third party under that third party's terms, not SynC's
• Managing recipient access over the life of the project, including removing access when appropriate (§6.2)
• Setting appropriate forwarding limits for your use case
• Ensuring you have the right to share the project content with the intended recipients, including, where you leave export on, the right to let them take it out of the Services in the ways §6.1 names
• Understanding that shared access may be forwarded within the limits you set

SynC is not responsible for any consequences arising from your decision to share project content with specific recipients or from recipients forwarding access within the limits you configured. Where a project specification incorporates content imported from a SynC Standard, your distribution of that specification is also subject to §5A.7.

7. Comments and Collaboration

7.1 Comment Visibility

The Services provide commenting functionality with two visibility levels:

• Internal: Visible only to members of your company. Use internal comments for proprietary notes, pricing discussions, or competitive information that should not be visible to other project participants.
• External: Visible to all participants on the project who have comment access.

7.2 Company Isolation

Comments marked as Internal are isolated by company. The Services enforce this isolation; other companies participating on the same project cannot see, search, or access your Internal comments.

7.3 User Responsibility for Visibility

You are solely responsible for selecting the appropriate visibility level when creating comments. Once a comment has been marked External and viewed by other participants, the information contained in it has been disclosed. SynC is not responsible for information disclosed through comments you have marked as External.

7.4 Comment Export

Comments may be exported to PDF or Word format. Once exported, the exported document is outside the control of the Services, and SynC cannot manage or restrict its further distribution.

7.5 Comments Are Not Feedback to SynC

A comment you write for the participants in your own project is your User Content, is governed by §5.3.1, and is not sent to SynC as Feedback — including a comment about a SynC Standard you have imported. Where a feature of the Services lets you send a comment, question, or error report to SynC about a Standard in the public library, that feature will say so before you send it, and what you send is Feedback under §8.5.

8. Intellectual Property Rights

8.1 SynC Property

The Services and all content provided by SynC, including but not limited to software, text, graphics, logos, icons, images, audio clips, algorithms, and user interface designs, are owned by SynC or its licensors and are protected by United States and international intellectual property laws, including copyright, trademark, patent, and trade secret laws.

8.2 Trademarks

SynC™, the SynC logo, "Synergy in Construction," and "SynC Standards" are trademarks of Synergy In Construction. You may not use these marks without prior written permission, except to accurately refer to the Services. Third parties who fork or adapt SynC Standards content under the CC-BY-SA license may not use the SynC name, logo, or branding to represent their derivative works as SynC Standards.

8.3 Limited License to Use Services

Subject to your compliance with these Terms, SynC grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Services for your internal business purposes.

8.4 Restrictions

You may not:

• Copy, modify, create derivative works of, or reverse engineer the Services
• Remove or alter any copyright, trademark, or proprietary notices
• Use the Services to develop competing products or services
• Sell, rent, lease, sublicense, or transfer your rights to the Services
• Use automated tools (bots, scrapers) to access the Services other than through an API key within its limits (§4A.5), or use the Services to collect content for model training, which §9.2A forbids

For clarity, nothing in this Section 8.4 limits any right granted to you under the CC-BY-SA 4.0 license with respect to SynC Standards content (Section 5A) or under the Contributor License Agreement's Project Use Permission. Those rights are governed by their own license terms, and the restriction on developing competing products or services applies to the Services' software and platform, not to your exercise of rights in openly licensed SynC Standards content.

8.5 Feedback

If you provide feedback, suggestions, or ideas about the Services, or about the content of the SynC Standards library — including reporting an error in a published Standard, or sending a comment or question to SynC about a Standard through a feature that indicates the content will be sent to SynC — ("Feedback"), you grant SynC a perpetual, irrevocable, worldwide, royalty-free license to use, modify, and incorporate such Feedback into the Services and into the SynC Standards library, without any obligation to you.

If we incorporate Feedback into a published SynC Standard, you additionally license the incorporated material to the public under CC-BY-SA 4.0 as part of that Standard, on the same terms as the rest of that Standard. You agree that attribution to you may be omitted from that Standard, and this Section constitutes a request under Section 3(a)(3) of CC-BY-SA 4.0 that attribution information be removed. If you want your contribution to a Standard credited to you, submit it as a Contribution under the Contributor License Agreement instead of as Feedback.

Feedback is content you direct to SynC. Content you write for the participants in your own project is not Feedback, is not licensed by this Section, and is governed by §5.3.1 — including a comment about an imported Standard that you address to your own project team (§7.5).

This Section is a license to use Feedback in the Services and the SynC Standards library. It is not a license to use Feedback to train a generative or foundation model, which §5.3.1 forbids.

9. Acceptable Use and Prohibited Conduct

9.1 Acceptable Use

You agree to use the Services only for lawful purposes and in accordance with these Terms.

9.2 Prohibited Activities

You agree not to:

• Violate any applicable local, state, national, or international law
• Engage in any activity that interferes with or disrupts the Services
• Attempt to gain unauthorized access to any portion of the Services
• Use the Services to transmit viruses, malware, or harmful code
• Impersonate any person or entity or misrepresent your affiliation
• Harvest or collect information about users without consent
• Use the Services for any fraudulent or deceptive purpose
• Overload, spam, or attempt to denial-of-service attack the Services
• Circumvent any security features or access controls
• Share your account credentials with unauthorized parties
• Falsely associate yourself with a company you are not authorized to represent
• Use the Services to collect content in order to train, fine-tune or evaluate a model, as §9.2A states
• Resell access to the Services through an API key or a connected app, or use more than one key, app, account or company to get around a limit, a permission or a setting, as §4A.5 states

9.2A Content Is Not to Be Extracted for Model Training

The rule. You may not use the Services to extract, collect or compile content in order to train, fine-tune or evaluate any artificial-intelligence or machine-learning model, whether you reach the Services through a browser, an API key, an integration, a share link, an export, or any automated means, and whether you do so yourself or through someone acting for you. This applies to content other users and companies have placed in the Services, to content shared with you under Section 6, to the SynC Standards library as served by the Services, and to information about other users.

Your own content is yours. This Section does not limit what you do with your own User Content. You may export it under §16.4 and use the export as you choose, including to train a model, and you may use the API to read your own company's records for any purpose, within the published rate limits.

Content shared with you. A project shared with you under Section 6 is another company's confidential work product. You may read it, comment on it, respond to it, use the Services' features on it, read it with an app or tool you have connected to your account where the sharer's export setting allows (§6.1, §4A.7), and export it where the sharer enabled export, for the purpose it was shared for. You may not collect it, or what you derive from it, to train, fine-tune or evaluate a model. Whether you may make any further use of it is a matter between you and the sharer, as §6.2 states.

SynC Standards. SynC Standards content is licensed to the public under CC-BY-SA 4.0, and this Section adds no condition to that license. Anyone who holds a copy of a SynC Standard may use it as the license allows, including to train a model. What this Section restricts is the use of the Services as the means of collection: reading the public pages, using the API within its published limits, and the exports the Services offer are how a copy is obtained; bulk or automated harvesting of the library through the Services beyond those is not permitted, because it is a use of SynC's systems and not an exercise of the license.

Integrations and API keys. A person or company that reaches the Services with an API key or through an integration, whether for itself or on a customer's behalf, may not use that access to collect content for the purposes this Section forbids, and may not keep content obtained through the Services beyond what the integration needs to do what the customer asked of it. A key used in breach of this Section may be revoked. Section 4A states what else applies to a key and to an app or tool connected with one.

Other users' information. Collecting information about other users, including their names, roles, companies and what they did in the Services, to train, fine-tune or evaluate a model is a breach of this Section and of §9.2.

What this Section does not reach. Using a tool, including an AI tool, to read, search, summarize or check content you are entitled to read is not collection for training and is not restricted by this Section. Nor is the ordinary use of the Services' own features, including the AI assistant and automated checks, on content you can read.

A breach of this Section is cause for action under Section 16.2.

9.3 Consequences of Violations

A violation of this Section is cause for action under Section 16.2, including immediate suspension or termination of your account, removal of User Content, and legal action.

10. Fees and Payment

10.1 What Is Sold, and What Is Not

Reading, commenting on, responding to, and exporting project content that has been shared with you does not require payment. Starting projects, authoring specifications and datasheets within a company's projects, and building and maintaining a company's libraries of standards, including their categories and errata, require a seat, and use of the AI assistant beyond any allowance requires credits, and this Section 10 addresses the fees for those. Seats and credits are held by the organization on whose behalf you use the Services (your "company", as described in Section 1), not by you individually.

SynC sells three things:

• Full seats, each of which lets its holder start projects, author within your company's own projects, and work on your company's libraries;
• Collaborator seats, each of which lets a person from a different company author inside your company's projects and nowhere else; and
• AI credit packs, which are prepaid credits held by your company for use of the AI assistant (Section 10.5).

There are no plans or tiers: every seat includes every feature of the Services. Seats are sold by subscription for a monthly or an annual period, and credit packs are bought once. The fee for each is the price shown in the Services at the time of purchase or, where you and SynC have agreed seat or credit fees in a quote, order form, or other written agreement (an "Order"), the fee stated in that Order. No plan or fee is selected or incurred by registering an account. All fees are stated in U.S. dollars, are exclusive of any applicable taxes, and are non-refundable except as required by law, as expressly stated in these Terms or in your Order, or as provided in Section 16.3 (pro-rata refund upon termination by SynC without cause).

10.2 The Introductory Seat and the Trial

Every company receives an introductory full seat when it is created, and a trial of additional full seats for a fixed period that begins on the day the company is created; the Services state what a newly created company receives. Neither is purchased and neither carries a fee. The introductory seat is an allowance, not a plan or a subscription: SynC may change what newly created companies receive at any time, and may change or withdraw an existing company's introductory seat on notice given under Section 18.2. The trial ends on the date the Services state. When the trial ends or an allowance is withdrawn, the result is a lapse under Section 10.6, not a termination: nothing your company has created is deleted, locked, or hidden.

10.3 Purchasing, and the Payment Method

Purchases are made on behalf of your company, by a person your company has authorized to manage its billing, on a payment page hosted by our third-party payment processor. You give your payment card details to the processor directly, on its page. SynC does not receive or store payment card numbers or bank account numbers. The processor holds the payment method against your company's billing account with the processor; the Services do not hold it. Our Privacy Policy states what SynC sends to the processor, what the processor sends back to SynC, what you give the processor directly, and where the processor processes that information.

A United States entity. Seats and credits are sold to companies in the United States. By making a purchase, the person making it represents, on behalf of your company, that the company being billed is a United States entity. A company owned from outside the United States qualifies through its United States entity, and that entity is the company billed. This is applied in two places. A person authorized to manage your company's billing records its billing country in the Services before a plan is chosen, and a purchase is not opened unless that country is the United States. The billing address entered on the payment page is checked after the purchase completes: a purchase completed with a billing address outside the United States is undone, the charge is refunded, and no seat or credit is granted by it. A false representation under this paragraph is a breach of these Terms and a ground for termination for cause under Section 16.2.

Authorization to charge. By purchasing a seat subscription, you authorize SynC, acting through the processor, to charge the payment method your company has given the processor for the subscription fee at the start of each subscription period, and for the pro-rated fee for any seats added part-way through a period, until the subscription is cancelled under Section 10.4. By purchasing a credit pack, you authorize a single charge for that pack. These Terms authorize no other charge.

Purchases made during the trial. If your company buys seats while its trial (Section 10.2) is still running, the payment method is collected at purchase, the seats are available at once, and the first charge is taken on the day the trial ends — unless the trial ends within the following two days (49 hours), in which case the first charge is taken at purchase. The Services state the date of the first charge at the time of purchase and afterwards.

An invoice or receipt for every charge is available from the billing portal described in Section 10.4. Questions about a charge may be sent to billing@synergyinconstruction.com.

10.4 Subscription Period, Renewal, Changes, and Cancellation

A seat subscription runs for the period chosen at purchase, monthly or annual, and renews automatically at the end of each period for a further period of the same length, at the fee then in effect for it (subject to Section 10.7), unless it has been cancelled before the period ends. The fee for each period is charged in advance, at the start of the period.

Your company may change the number of seats, or cancel, at any time through the billing portal that the processor hosts and that the Services link to. The portal also allows your company to update its payment method and to view and download its invoices.

• Adding seats takes effect at once. The added seats are charged, pro-rated, for the remainder of the current period, and are included in the fee at renewal.
• Removing seats takes effect at the end of the current period. Your company keeps the seats it has paid for until then and renews at the lower count. No part of the current period's fee is refunded.
• Cancelling stops the renewal. Your company keeps the seats it has paid for until the end of the current period, and the subscription ends then. No part of the current period's fee is refunded.

The Services state the number of seats a subscription will renew at and the date it renews or ends. Where the fee shown in the Services and the fee stated in an Order differ, the Order governs.

10.5 AI Credits

Use of the AI assistant is measured in credits. Each full seat brings its holder a personal credit allowance for each month of the subscription that provides the seat. That month begins on the day the subscription renews and, for an annual subscription, on the same day of each month within the paid year; for a seat that no subscription provides, such as the introductory seat, it is the calendar month. The allowance refreshes at the start of each such month while the seat is in place, including while a failed payment is being retried under Section 10.8, does not carry over from one month to the next, may be used only by that seat holder, and ends when the seat lapses. Your company may also buy credit packs. Credits from a pack are held by your company, are drawn as they are used according to the drawing setting your company's administrator has chosen, do not expire at the end of a month, and remain available to your company for as long as its account remains open. Purchased credits are not refundable, are not redeemable for money, and have no cash value. SynC does not charge for credits after they are used and does not extend credit: the credits your company holds are the limit of what it can use, and the Services tell a person when they are exhausted and what the next step is. The number of credits an exchange with the assistant costs depends on the work the exchange involves and on the length of the conversation it is part of, and is shown with the assistant's answer. The same request can cost more late in a long conversation than at the start of a new one. SynC does not publish the rate at which it converts its costs to credits and may adjust it.

10.6 Lapse

A seat lapses when the subscription that funds it ends, when the trial ends, when an allowance is withdrawn, or when your company releases it. A lapse is not a termination under Section 16, and nothing is deleted, locked, or hidden by it. The person whose seat lapses keeps the ability to read, comment on, respond to, and export what they had access to, and every revision, comment, and export they produced remains exactly as it was. What they lose is the ability to change specifications and datasheets, to save revisions, to start projects, to create or change your company's libraries, standards and categories, to issue or withdraw errata, and to write with the assistant. Before your company's trial ends, the Services give notice of the date. A lapse does not change a person's role in your company, and a person who administered your company before a lapse administers it after. Where a seat funded a person's role on a project, that role becomes read-and-comment access when the seat lapses, and the role is restored when your company gives the person a seat again.

10.7 Price Changes

SynC reserves the right to modify fees with at least 30 days' notice. A change does not alter the fee for a subscription period that has already been charged, or a fee agreed in an Order for the period that Order covers; it applies from the first renewal after the notice period, and to new purchases and new Orders made after it. If you do not accept a changed fee, cancel under Section 10.4 before the renewal at which it would apply; continued use of a subscription past a renewal at which a changed fee applies constitutes acceptance of the new fee.

10.8 Failed Payment and Non-Payment

If a charge to your company's payment method fails, the processor retries it and SynC notifies your company. The seats the subscription funds remain in place while the charge is being retried. If the charge cannot be collected, the subscription ends and the seats it funded lapse under Section 10.6 at the end of the last period that was paid for. Failure to pay when due an invoice issued under an Order, or a charge that cannot be collected after the processor's retries, may also result in suspension or termination of your company's access to the Services under Section 16.2. These Terms impose no interest, late fee, or collection charge.

11. Privacy and Data Protection

Your use of the Services is subject to our Privacy Policy, which describes how we collect, use, disclose, and protect your personal information. By using the Services, you consent to our collection and use of information as described in the Privacy Policy.

12. Service Availability and Modifications

12.1 Service Availability

While we strive to provide reliable Services, we do not guarantee uninterrupted or error-free access. The Services may be unavailable due to maintenance, updates, or circumstances beyond our control.

12.2 Modifications to Services

We reserve the right to modify, suspend, or discontinue any aspect of the Services at any time, with or without notice. We will make reasonable efforts to notify users of material changes. Section 12.4 states what applies where SynC discontinues the Services as a whole.

12.3 No Liability for Changes

Except as Section 12.4 and Section 16.3 provide, SynC shall not be liable to you or any third party for any modification, suspension, or discontinuance of the Services.

12.4 If SynC Discontinues the Services

Section 12.2 lets SynC change, suspend or discontinue a feature of the Services. This Section applies where SynC discontinues the Services as a whole, or discontinues the storing and reading of projects, specifications and datasheets, so that you could not keep your content in the Services by any means. An assignment under Section 18.5 under which the Services continue is not a discontinuation. Where SynC discontinues the Services in that sense, other than because a legal requirement, a court order or an event described in Section 18.6 prevents it from continuing:

• SynC gives at least ninety (90) days' notice to every account's registered email address, and in the Services, before the Services end;
• throughout that period the exports described in §16.4 remain available in the Services;
• SynC refunds the pro-rata unused portion of any subscription fees your company has paid for a period that runs past the end of the Services, and refunds unused purchased credits at the price paid for them, as §16.3 provides for a termination by SynC without cause; and
• SynC takes no renewal charge for a period that would run past the end of the Services.

Where a legal requirement, a court order or an event described in Section 18.6 prevents SynC from giving that notice, SynC gives as much notice as it can and does what it can to keep export available for as long as it can. Section 12.3 does not excuse what this Section requires.

13. Disclaimers and Warranties

13.1 "AS IS" and "AS AVAILABLE"

THE SERVICES, INCLUDING ALL CONSTRUCTION STANDARDS, SPECIFICATIONS, DATASHEETS, AI-GENERATED CONTENT, SYNC STANDARDS WIKI CONTENT, AND RELATED MATERIALS PROVIDED BY SYNC ("MATERIALS"), ARE PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED.

13.2 Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, SYNC DISCLAIMS ALL WARRANTIES, INCLUDING BUT NOT LIMITED TO:

• WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT
• WARRANTIES THAT THE SERVICES WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE
• WARRANTIES REGARDING THE ACCURACY, RELIABILITY, OR COMPLETENESS OF MATERIALS
• WARRANTIES THAT DEFECTS WILL BE CORRECTED
• WARRANTIES REGARDING AI-GENERATED CONTENT OR RECOMMENDATIONS
• WARRANTIES REGARDING THE ACCURACY OR COMPLETENESS OF COMMUNITY-CONTRIBUTED STANDARDS
• WARRANTIES THAT THE API, OR THE ADDRESS AT WHICH APPS CONNECT TO IT, WILL BE AVAILABLE OR UNCHANGED, OR THAT ANY THIRD-PARTY APP OR TOOL WILL WORK WITH THEM

13.3 Professional Responsibility

THE MATERIALS AND AI-GENERATED CONTENT ARE FOR INFORMATIONAL PURPOSES ONLY AND DO NOT CONSTITUTE PROFESSIONAL ADVICE (LEGAL, ENGINEERING, ARCHITECTURAL, OR OTHERWISE). YOU ARE SOLELY RESPONSIBLE FOR:

• Verifying the accuracy and suitability of all Materials for your specific use
• Engaging qualified professionals for project design and implementation
• Ensuring compliance with all applicable codes, standards, and regulations
• All decisions made based on information obtained through the Services

13.4 Third-Party Content

SynC is not responsible for the accuracy, legality, or safety of third-party content, links, or integrations accessed through the Services.

14. Limitation of Liability

14.1 Exclusion of Damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL SYNC, ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, OR LICENSORS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO:

• LOSS OF PROFITS, REVENUE, OR BUSINESS OPPORTUNITIES
• LOSS OF DATA OR INFORMATION, OTHER THAN LOSS OF CONFIDENTIALITY OF USER CONTENT THROUGH UNAUTHORIZED DISCLOSURE IN BREACH OF SECTION 5.6, WHICH §14.3 ADDRESSES
• LOSS OF GOODWILL OR REPUTATION
• BUSINESS INTERRUPTION
• COST OF SUBSTITUTE SERVICES
• PROJECT DELAYS, CONSTRUCTION DEFECTS, OR FAILURES ARISING FROM RELIANCE ON MATERIALS
• DAMAGES ARISING FROM USE OF AI-GENERATED CONTENT OR THIRD-PARTY SERVICES
• DAMAGES ARISING FROM INFORMATION DISCLOSED THROUGH COMMENTS OR SHARED PROJECTS
• DAMAGES ARISING FROM RELIANCE ON COMMUNITY-CONTRIBUTED STANDARDS CONTENT
• DAMAGES ARISING FROM THE ISSUANCE OF AN ERRATUM ON, THE PLACING OF A HOLD ON MATERIAL WITHIN, OR THE REVOCATION OF, AN ADOPTED WIKI REVISION (SEE §5A.6)
• DAMAGES ARISING FROM WHAT AN APP OR TOOL YOU CONNECTED TO YOUR ACCOUNT WITH AN API KEY DID, OR FROM WHAT ITS PROVIDER DID WITH CONTENT IT RECEIVED (SEE §4A)

THIS LIMITATION APPLIES REGARDLESS OF THE LEGAL THEORY (CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE) AND EVEN IF SYNC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

14.2 Cap on Liability

TO THE EXTENT PERMITTED BY LAW, AND EXCEPT AS §14.3 STATES, SYNC'S TOTAL LIABILITY TO YOU FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICES SHALL NOT EXCEED THE GREATER OF: (A) THE AMOUNT YOU PAID TO SYNC IN THE 12 MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY, OR (B) $100 USD.

14.3 What the Exclusions and the Cap Do Not Reach

The exclusions in §14.1 and the cap in §14.2 do not apply to a liability that the law does not allow to be limited or excluded.

A higher cap for unauthorized disclosure and for SynC's indemnity. The following are outside the cap in §14.2 and are subject instead to the cap in this paragraph: SynC's breach of §5.6 by which User Content is read by, or disclosed to, a person not authorized to see it; SynC's use of User Content contrary to §5.3.1; and SynC's indemnity in §15.2. For these, SynC's total liability to your company shall not exceed two times the amount your company paid to SynC in the 12 months preceding the event giving rise to the claim. The amount is what your company paid, whatever the number of its seats or users. A company that has paid nothing in that period has no remedy under this paragraph, and §14.2 applies to it.

This paragraph reaches unauthorized disclosure and nothing else. Loss, corruption or unavailability of User Content, from any cause, including an incident that destroys content without disclosing it, remains within the exclusion in §14.1 and the cap in §14.2.

Each cap is an aggregate across all claims of your company, not a limit per claim. An amount SynC pays your company under §14.2 also counts against the cap in this Section.

14.4 Exceptions

Some jurisdictions do not allow the exclusion or limitation of certain warranties or damages. In such jurisdictions, the above limitations and exclusions will apply to the fullest extent permitted by law.

15. Indemnification

15.1 Your Indemnity

You agree to defend, indemnify and hold harmless SynC, its affiliates, officers, directors, employees, agents and licensors from and against any claim brought by a third party, and the liabilities, damages, losses, costs and expenses (including reasonable attorneys' fees) that result from it, to the extent the claim arises out of:

• your User Content, including a claim that it infringes or misappropriates a third party's rights or violates the law;
• your sharing or distribution of project content to third parties under Section 6, including a claim by a recipient about what you shared with them or about the ending of their access;
• your public distribution of a SynC Standard, or of a project specification derived from one, otherwise than as permitted under §5A.7;
• your use of Materials or AI-generated content in a construction project, including a claim arising from a design, a specification or a construction decision made in reliance on them (§13.3);
• your breach of these Terms or of applicable law, including a breach by a person using your account or by an app or tool you connected to your account with an API key (§4A.2); or
• your contributions to SynC Standards, to the extent the Contributor License Agreement provides.

This indemnity does not apply to the extent a claim arises from SynC's breach of these Terms, or from a matter for which SynC indemnifies you under §15.2.

15.2 SynC's Indemnity

SynC will defend you against a claim brought by a third party alleging that the Services' software, as SynC provides it and as used in accordance with these Terms, infringes that third party's United States patent, copyright or trademark, or misappropriates its trade secret, and will pay the damages and costs finally awarded against you by a court or arbitrator for that claim, or agreed by SynC in a settlement of it.

This indemnity does not cover a claim to the extent it arises from: User Content; SynC Standards content, which is contributed by users under the Contributor License Agreement and licensed under CC-BY-SA 4.0; AI-generated content; a third-party service or integration (§4.4); your use of the Services in breach of these Terms; the combination of the Services with anything SynC did not provide, where the claim would not have arisen without the combination; or your continued use of a part of the Services after SynC has told you to stop using it and offered a replacement.

If a claim of this kind is made, or SynC believes one is likely, SynC may, at its option: procure your right to continue using the Services; modify or replace the affected part so that it no longer infringes, without materially reducing what it does; or, where neither is commercially reasonable, withdraw the affected part of the Services from your company on notice and refund the pro-rata unused portion of any subscription fees paid for the current period and the price paid for unused purchased credits.

This indemnity is owed to your company where it has paid SynC in the 12 months preceding the claim, and is subject to the cap in §14.3, which is measured by that amount; a company that has paid nothing in that period has no claim under this Section. This Section states SynC's entire liability, and your sole remedy, for a claim that the Services infringe or misappropriate a third party's intellectual property rights.

15.3 Procedure

The party seeking indemnity gives the other prompt written notice of the claim; a delay excuses the indemnifying party only to the extent the delay prejudiced it. The indemnifying party has sole control of the defense and settlement of the claim, and the indemnified party gives reasonable cooperation at the indemnifying party's expense and may take part in the defense with its own counsel at its own expense. The indemnifying party may not settle a claim in a way that admits fault on behalf of the indemnified party, or imposes an obligation on it other than to stop the conduct claimed, without the indemnified party's written consent, which is not to be unreasonably withheld.

The obligations in this Section 15 survive termination of these Terms and your use of the Services.

16. Termination

16.1 Termination by You

You may terminate your account at any time by contacting support@synergyinconstruction.com or using the account termination feature in the Services.

16.2 Suspension and Termination by SynC

What SynC may do. SynC may suspend or terminate your account, or your company's account, and may suspend, limit or withdraw your or your company's access to any part of the Services, including any feature, any content, any share link, any API key, and the AI assistant, in whole or in part, at any time. SynC may also remove, disable access to, or decline to display any User Content or contribution. SynC chooses the action: it may take a lesser action before a greater one, or act at once. Sections 5A.3, 5A.6 and 5B state how this authority is used for the SynC Standards Wiki and for copyright notices, and nothing there narrows it.

For cause, without prior notice. SynC may act at once, and without notice in advance, where the action responds to: a violation of these Terms or of the Contributor License Agreement, including a false representation under Section 10.3 that your company is a United States entity; conduct SynC reasonably believes to be unlawful, fraudulent, or infringing, including under the repeat-infringer policy in Section 5B.5; a risk to the security or integrity of the Services, to other users, or to any person; non-payment (Section 10.8); a legal requirement, a court order, or the request of a public authority; or the creation or use of an account to avoid a suspension or a termination. Where the law allows, SynC tells you the ground for the action and how to ask for it to be reconsidered, unless doing so would prejudice an investigation, endanger a person, or is prohibited. No refund is owed for an action under this paragraph.

At SynC's discretion, on notice. SynC may also suspend or terminate an account, or withdraw a part of the Services from an account, for any reason or for none. Where SynC does so and none of the grounds in the paragraph above applies, SynC gives at least thirty (30) days' notice to the account's registered email address before the account is terminated, the refund in Section 16.3 applies, and the export period in Section 16.4 runs from the date of termination. This paragraph does not limit Section 12.2 (changes to the Services generally) or Section 10.2 (an allowance withdrawn on notice). Section 12.4 states what applies where SynC discontinues the Services as a whole.

What a suspension does to your content. A suspension, on any ground, does not delete User Content. Your company's projects, specifications, datasheets and records stay as they were, and are there when the suspension ends. While an account or a company is suspended, its ability to export through the Services is suspended with it. On request to support@synergyinconstruction.com, SynC provides the exports described in §16.4 during a suspension, unless the suspension responds to a risk to the security or integrity of the Services, or to a legal requirement, a court order or the request of a public authority, that prevents SynC from doing so, in which case SynC says so in answer to the request. What happens to User Content on termination is stated in §16.3 and §16.4.

Inactivity. SynC may close an account that has not been used for an extended period, after notice to its registered email address.

People and companies. Terminating a person's account does not terminate their company's account and does not remove the company's projects, specifications, or datasheets, which remain with the company and its administrators. Terminating a company's account ends its members' access to that company's projects; Section 16.3 states what follows.

Your name on a company's records. Your work in a company's projects and libraries is recorded under your name as part of that company's records: that you published a revision, uploaded a file, wrote a comment, created or accepted a share link, or adopted or changed a standard. A record keeps the name you had when you made it, and shows that name to everyone who can read the record, including the recipients of a revision the company has distributed. Changing your name afterwards does not change the record, and neither does the termination or deletion of your account. A name is shown differently from how it was recorded only through an act that is recorded and shown on the record with its reason and date. The company that holds a record may instruct SynC to withhold your name from its records. SynC may withhold a name, or mark it as disputed while SynC looks into a report about it, where the name impersonates a person, is abusive, puts a person's safety at risk, or belongs to an account whose identity SynC could not confirm, and withholds a name where the law requires it. You may choose to show your current name on your own earlier records; you cannot withhold your own name. Our Privacy Policy states what is kept, for how long, and what you can ask for. Attribution in the SynC Standards library is governed by the Contributor License Agreement (§5A.4), not by this paragraph.

Your rights under local law. If you are a consumer, nothing in this Section removes a right that the law of your country gives you and that cannot be waived by agreement.

16.3 Effect of Termination

Upon termination:

• Your right to access and use the Services immediately ceases
• We may delete your User Content after the export period in §16.4 has ended; our Privacy Policy states what is retained after that, and for how long
• A company's records of your work in its projects and libraries keep your name as it was recorded (§16.2)
• You remain liable for all fees incurred prior to termination
• If SynC terminates your account under the discretionary paragraph of Section 16.2 (that is, other than for cause as that Section describes it), we will refund the pro-rata unused portion of any subscription fees your company has paid for the current subscription period; purchased credits that remain unused at such a termination are refunded at the price paid for them
• API keys issued to the account are revoked and its sessions are ended
• Access you have granted to other users through share links is not automatically removed by termination of your account; it remains governed by Section 6 and may later end as described in §6.2 (for example, if the project is deleted or a recipient's access is removed by a user with authority over the project)
• Contributions to SynC Standards licensed under CC-BY-SA 4.0 remain available under that license
• Your conversations with the AI assistant (§4.2.1) are retained through the period in which your account can still be restored, so that restoring it recovers them, and are deleted when your account is permanently deleted. The Privacy Policy states this rule and its relationship to the retention period for conversations
• Sections that by their nature should survive (including limitations of liability, indemnification, and dispute resolution) will continue to apply

16.4 Getting Your Content Out

Your content is yours (§5.1), and this Section states how you get it out. Nothing in it is charged for.

What you can export yourself, at any time. The Services let a user with the right to do so export the following in the browser, without asking SynC:

• a project revision as a PDF package: a cover page and every specification in the revision, with the values of its datasheets, for the revision you are viewing, whether a working draft or a published revision;
• a project revision as Markdown: one file per specification in SynC's markup syntax, zipped, for the revision you are viewing;
• a project revision's datasheet data as JSON, with the project's metadata and section structure; the JSON carries values and not the text of the specifications, which the PDF and Markdown exports carry;
• a standard in your personal or company library as a PDF or as a Markdown file, and a whole library as one PDF or as a zip of Markdown files with a manifest;
• a project's comments as a PDF or Word document (§7.4); and
• a project's coordination checklist as a CSV file.

Each project export takes the revision you are viewing, so every published revision of a project can be exported, one at a time. Which of these a share-link recipient may use is controlled by the person who shared the project (§6.1); this Section concerns your own content.

What the Services do not export. The Services do not export as a file: the history of a project as one record; access records, including who accepted a share link and when; the record of acknowledgments and replacements made under §5A.6.8; and your account's activity records. Your conversations with the AI assistant can be copied out as text (§4.2.1) and are not otherwise exported. Those records can be read in the Services where your role allows it. These Terms promise no copy of them beyond what the Services let you see and export yourself.

The formats. SynC does not promise a format this Section does not name. SynC may add a format, may change how a format is laid out, and may replace a format with another that carries the same content; SynC gives notice under §18.2 before withdrawing a format without a replacement.

After termination. For thirty (30) days after your account or your company's account is terminated, whoever terminated it and on whatever ground, you may ask support@synergyinconstruction.com for the exports described in this Section, and SynC provides them, except where the termination responds to a risk to the security or integrity of the Services, or to a legal requirement, a court order or the request of a public authority, that prevents SynC from doing so. After that period we may delete your data as §16.3 states.

17. Dispute Resolution; Arbitration Agreement; Governing Law

PLEASE READ THIS SECTION CAREFULLY. IT REQUIRES MOST DISPUTES TO BE RESOLVED THROUGH BINDING INDIVIDUAL ARBITRATION RATHER THAN IN COURT, AND IT WAIVES THE RIGHT TO PARTICIPATE IN CLASS ACTIONS. YOU MAY OPT OUT OF ARBITRATION AS DESCRIBED IN SECTION 17.10.

17.1 Governing Law

These Terms and any disputes arising out of or relating to these Terms or the Services shall be governed by and construed in accordance with the laws of the State of Florida, without regard to its conflict of law principles, except that the Federal Arbitration Act (9 U.S.C. § 1 et seq.) governs the interpretation and enforcement of the arbitration agreement in this Section 17.

17.2 Informal Dispute Resolution First

Before initiating arbitration or any other proceeding, you and SynC agree to first attempt to resolve any dispute informally. The party raising the dispute must send the other a written notice describing the nature of the dispute and the relief sought (to SynC: legal@synergyinconstruction.com; to you: your registered email address). You and SynC agree to negotiate in good faith for at least 60 days after the notice is received. Completion of this informal process is a prerequisite to initiating arbitration or litigation. Applicable statutes of limitations are tolled during this period.

17.3 Agreement to Arbitrate

Except as provided in Section 17.4, you and SynC agree that any dispute, claim, or controversy arising out of or relating to these Terms or the Services (a "Dispute") shall be resolved by final and binding arbitration on an individual basis, rather than in court. This agreement to arbitrate is mutual: it binds you and SynC equally.

17.4 Exceptions to Arbitration

This arbitration agreement does not apply to:

• Claims that qualify for small claims court, which either party may bring in a small claims court of competent jurisdiction
• Claims for injunctive or other equitable relief to prevent the actual or threatened infringement, misappropriation, or violation of a party's intellectual property rights, which either party may bring in the courts identified in Section 17.9
• Any claim that, under applicable law that cannot be waived by agreement, may not be subject to mandatory pre-dispute arbitration

17.5 Arbitration Procedures

The arbitration will be administered by the American Arbitration Association ("AAA") under its Consumer Arbitration Rules (for individual users) or its Commercial Arbitration Rules (for organizations), as applicable, each as modified by this Section 17. The AAA's rules are available at www.adr.org. A single arbitrator will be appointed in accordance with those rules. The arbitration will be conducted by videoconference or telephone unless the arbitrator determines an in-person hearing is necessary, in which case the hearing will take place in the county where you reside (for individual users) or in Orange County, Florida (for organizations), unless the parties agree otherwise. The arbitrator has exclusive authority to resolve any dispute about the interpretation, applicability, or enforceability of this arbitration agreement, except that only a court may decide the enforceability of the class action waiver in Section 17.7. Judgment on the arbitration award may be entered in any court of competent jurisdiction.

17.6 Arbitration Fees

Payment of AAA filing, administrative, and arbitrator fees will be governed by the applicable AAA rules. For individual users, if you are unable to obtain a fee waiver and your claim seeks less than $10,000, SynC will pay the portion of the AAA filing fee that exceeds the cost of filing the same claim in the courts identified in Section 17.9, together with the administrative and arbitrator fees allocated to consumers under the AAA Consumer Arbitration Rules. Each party bears its own attorneys' fees and costs except where applicable law provides otherwise or the arbitrator determines that a claim or defense was frivolous or brought for an improper purpose.

17.7 Class Action Waiver

TO THE EXTENT PERMITTED BY LAW, YOU AND SYNC AGREE THAT EACH MAY BRING DISPUTES AGAINST THE OTHER ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING. The arbitrator may not consolidate more than one person's claims and may not preside over any form of class or representative proceeding. If a court of competent jurisdiction holds this class action waiver unenforceable as to a particular Dispute, then the agreement to arbitrate in Section 17.3 shall not apply to that Dispute, which shall instead proceed in the courts identified in Section 17.9; in no event shall any class, collective, or representative Dispute proceed in arbitration.

17.8 Coordinated Filings

If 25 or more demands for arbitration raising similar Disputes are filed against SynC with the assistance or coordination of the same counsel or coordinated counsel, the parties agree the demands shall be resolved in staged proceedings: up to ten demands selected by claimants' counsel and up to ten selected by SynC shall proceed first as bellwether arbitrations, while the remaining demands are held in abeyance (with filing fees deferred and limitations periods tolled). Following the bellwether arbitrations, the parties shall engage in a good-faith global mediation before any remaining demand proceeds. If this Section is held unenforceable as to any demand, that demand shall proceed in the courts identified in Section 17.9.

17.9 Jurisdiction and Venue for Court Proceedings

For any Dispute not subject to arbitration under this Section 17, you agree that the action shall be brought exclusively in the state courts located in Orange County, Florida, or in the United States District Court for the Middle District of Florida (Orlando Division), and you irrevocably consent to the personal jurisdiction and venue of such courts.

17.10 Your Right to Opt Out of Arbitration

You may opt out of the arbitration agreement in Sections 17.3 through 17.8 by emailing legal@synergyinconstruction.com with the subject line "Arbitration Opt-Out" — including your name, the email address associated with your account, and a clear statement that you wish to opt out of arbitration — within 30 days of the date you first accept these Terms. Opting out of arbitration does not affect any other provision of these Terms, including Section 17.9 (Jurisdiction and Venue). An opt-out applies only to the individual or organization that submits it.

18. General Provisions

18.1 Entire Agreement

These Terms, together with our Privacy Policy and any additional terms applicable to specific Services, constitute the entire agreement between you and SynC regarding the Services and supersede all prior agreements and understandings.

Negotiated terms. An Order (§10.1), or another written agreement that SynC has signed, may vary these Terms for the company that signed it, including the limits in Section 14, the indemnities in Section 15 and the export commitments in §16.4. It does so only to the extent it identifies the provision it varies and states the variation. Where it does, it governs over these Terms for that company, and these Terms govern everything it does not address. A quote, invoice, purchase order or other document that one party issues alone varies nothing, and terms printed on a purchase order that conflict with these Terms have no effect.

18.2 Modifications to Terms

SynC may modify these Terms. We give notice of a material change by:

• Posting updated Terms with a new Effective Date
• Sending email notification to your registered email address
• Displaying a prominent notice in the Services

A material change takes effect no sooner than thirty (30) days after that notice, except: a change that the law requires, which takes effect when the law requires it; a change that applies only to a new feature of the Services or to a Beta Feature (§4.5); and a change that only adds to your rights or reduces your obligations. Those may take effect on posting. §5.3.3 and §10.7 state their own notice periods, which this Section does not shorten. Continued use of the Services after a change takes effect constitutes acceptance. If you do not agree to a change, stop using the Services before it takes effect; §16.4 applies to your content. A change does not apply to a Dispute of which one party gave the other notice under §17.2 before the change took effect.

18.3 Severability

If any provision of these Terms is found to be invalid, illegal, or unenforceable, the remaining provisions shall continue in full force and effect.

18.4 Waiver

No waiver of any provision of these Terms shall be deemed a further or continuing waiver of such provision or any other provision. Our failure to enforce any right or provision of these Terms shall not constitute a waiver of such right or provision.

18.5 Assignment

You may not assign or transfer these Terms or your account without our prior written consent. SynC may assign these Terms or its rights hereunder without restriction.

18.6 Force Majeure

SynC shall not be liable for any delay or failure to perform resulting from causes beyond our reasonable control, including acts of God, war, terrorism, labor disputes, governmental actions, internet disruptions, or failure of third-party services.

18.7 Export Compliance

You agree to comply with all applicable export and import laws and regulations in your use of the Services.

18.8 Government Use

If you are a U.S. government entity, the Services are "commercial computer software" and "commercial computer software documentation" as defined in FAR 12.212 and DFARS 227.7202, and your rights are limited to those expressly granted in these Terms.

18.9 Relationship of Parties

Nothing in these Terms creates a partnership, joint venture, agency, or employment relationship between you and SynC.

19. Notice and Contact Information

19.1 Notice to SynC

All notices to SynC must be sent by email to:

Synergy In Construction, LLC A Florida limited liability company Email: legal@synergyinconstruction.com

19.2 Notice to You

We may provide notices to you via email to your registered email address, posting on the Services, or by mail to your address on file. You consent to receive communications electronically.

19.3 Customer Support

For customer support inquiries, contact us at: Email: support@synergyinconstruction.com

20. Acknowledgment

By clicking "I Accept," creating an account, or using the Services, you acknowledge that:

• You have read and understood these Terms
• You agree to be bound by these Terms
• You have the authority to enter into these Terms
• You understand the limitations and disclaimers regarding AI-generated content and construction Materials
• SynC does not use your content to train generative or foundation AI models, and de-identifying content does not make it non-confidential (§5.3.1) — except for content you deliberately submit to the SynC Standards library, which the Contributor License Agreement governs, and feedback you direct to SynC, which §8.5 governs. SynC may build models inside the Services that classify, score, or flag content without generating text, on the conditions stated in §5.3.1. SynC may use what you upload, and what the Services produce from it, to evaluate and improve the Services; your content stays confidential, is not sold or licensed, and nothing built from it reproduces or discloses its substance to anyone not already permitted to see it; a project's administrator can opt the project out and a company administrator can set the default for new projects (§5.3.1). We do measure how the Services are used (§5.3.2), and we transmit the content you are working with to inference and embedding providers that are barred from retaining or training on it (§5.3.3); an app or tool that you, or a recipient, connect to a SynC account with an API key is not one of those providers and is outside those constraints (§4A.7, §6.1)
• Your conversations with the AI assistant are stored, are private to you, are retained for the period stated in the Privacy Policy and then deleted, and may be deleted by you at any time (§4.2.1)
• Reading, commenting, responding, and exporting are not charged for; seats and AI credits are bought for your company on a third-party payment processor's hosted pages, and SynC never receives card numbers (§10.1, §10.3)
• The Services are offered to customers in the United States; a company that buys seats or credits represents that it is a United States entity, and a false representation is a ground for termination; reading, commenting, responding and exporting do not depend on where you are (§2, §10.3, §16.2)
• A seat subscription renews automatically, and the payment method your company has given the processor is charged at the start of each period, and pro-rated for seats added, until your company cancels from the billing portal; removing seats and cancelling take effect at the end of the paid period, with no refund of that period; purchased credits are prepaid and are not refundable (§10.3, §10.4, §10.5)
• When a seat lapses, the person keeps reading, commenting, responding, and exporting, keeps their role in your company, and loses nothing they made; what they lose is authoring, in projects and in your company's libraries (§10.6)
• You understand that a project owner may remove a share-link recipient's access to a shared project at any time, and that removal does not retrieve copies of project content a recipient exported while their access was active (§6.2)
• You understand that SynC Standards are licensed to the public under CC-BY-SA 4.0, and that if you contribute to SynC Standards your contribution is governed by the separate Contributor License Agreement (§5A.2)
• You understand that SynC may issue errata on, place a hold on material within, or in extraordinary circumstances revoke, adopted SynC Standards revisions that you have imported into your projects, as described in §5A.6, and that while a hold stands you may publish after acknowledging it, may not customize the affected standard where the hold reaches the whole of it, and receive no corrected revision of it until a moderator acts (§5A.6.8)
• You understand that a SynC Standard imported into your project and configured for that project is your confidential work product, while the embedded SynC Standards content remains licensed under CC-BY-SA 4.0 and its public distribution remains subject to that license (§5A.7)
• You understand that comment visibility is your responsibility and that External comments are visible to all project participants
• You may not use the Services to collect content, including content shared with you, the SynC Standards library as served by the Services, or information about other users, in order to train, fine-tune or evaluate a model; your own content is yours to export and use as you choose (§9.2A, §16.4)
• An API key, and any app or tool you connect to your account with it, acts as you, within the permissions you chose for it and what you can do at the time; you are responsible for what it does; content it reads leaves the Services and is governed by that app's provider's terms, not by SynC's commitments about its own providers; some actions are never available to a key and some only when you grant them by name; limits are yours across all of your keys, follow your seat, and may change; a sharer's export setting decides whether an app of a recipient's may read a shared project, and a company's administrators can switch off access by keys and apps to the company's projects; SynC may revoke a key and may change the API, and promises no availability for either (§4A, §6.1)
• SynC holds your User Content in confidence and notifies your company where a security incident SynC confirms has exposed it (§5.6)
• You can export your content yourself at any time in the formats §16.4 names, SynC does not charge for export, a suspension does not delete your content, and export stays available for thirty days after termination (§16.2, §16.4)
• Your work in a company's projects and libraries is recorded under your name as part of that company's records; a record keeps the name you had when you made it, after a change of name and after your account is terminated or deleted, and a name is shown differently only through a recorded act that the record shows (§16.2)
• If SynC discontinues the Services as a whole, you get at least ninety days' notice, export throughout, and a refund of what your company prepaid past the end (§12.4)
• SynC's liability is limited, with a higher cap, scaled to what your company paid, for unauthorized disclosure of your content, use of it contrary to §5.3.1, and SynC's indemnity (§14.3); you indemnify SynC for claims arising from your content, your distribution and your breach, and SynC indemnifies you for claims that its software infringes (§14, §15)
• A material change to these Terms takes effect no sooner than thirty days after notice, with the exceptions §18.2 states, and a signed Order may vary these Terms for your company (§18.1, §18.2)
• You understand that Section 17 requires most disputes to be resolved through binding individual arbitration and waives class actions, subject to the exceptions and the 30-day opt-out right described in that Section

21. Summary of Changes from Version 1.1

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.4 carries Terms of Service v1.1 forward in full, integrates two amendments that were previously drafted and reviewed as separate parallel tracks (the v1.2 errata/revocation-authority draft and the v1.3 standards-project-use draft), and adds the protective provisions adopted in the June 2026 legal-document review. No prior obligation, definition, or user right from v1.1 is removed, except that the dispute-resolution provisions in §17 are restructured as described below.

• New §5A.6 (Errata and Revocation of Adopted Revisions). Establishes adopted-revision immutability, SynC's reserved authority to issue public non-destructive errata (including on revisions already imported into projects and held under Vested Access), a narrow revocation authority for extraordinary circumstances (legal process, DMCA, GDPR erasure, public-safety, or material legal/safety risk), the relationship of this authority to Vested Access, and a no-liability provision distinguishing platform-issued errata (SynC's own speech) from community-moderator errata (hosted community speech). (From the v1.2 draft.)
• New §5A.7 (SynC Standards Imported into Projects). Clarifies that importing a SynC Standard into a project and configuring/editing it produces a confidential project specification; that project-internal use and distribution to identified project participants and to an authority having jurisdiction is not public redistribution under CC-BY-SA 4.0; and that public distribution of a Standard or an adaptation of one remains subject to CC-BY-SA 4.0 attribution and ShareAlike. (From the v1.3 draft.)
• Restructured §5A (SynC Standards Wiki). Section 5A no longer restates the contribution license grant or contributor representations and warranties. Those terms are governed by SynC's separate Contributor License Agreement (CLA), to which §5A.2 now defers (the CLA controls in the event of any conflict as to contributions). This removes the overlap and potential conflict between the prior ToS §5A.1/§5A.2 and the CLA — for example, the prior §5A.4 stated contributors are "credited by name," which is inconsistent with the CLA's automatic anonymization of attribution on account deletion. Section 5A retains the wiki-and-license information relevant to all users — including readers and project users who never contribute: that SynC Standards are licensed to the public under CC-BY-SA 4.0 (§5A.1, incorporating the v1.3 clarification that attribution and ShareAlike attach to public redistribution, not to private or project use), the moderation and editorial rights (§5A.3), how attribution is displayed (§5A.4, with details governed by the CLA), the reference-material disclaimer (§5A.5), the errata and revocation authority (§5A.6), and project use (§5A.7).
• §6.2 (Vested Access). Adds a limitation clause putting project owners on notice that Vested Access does not prevent SynC from issuing errata or revoking imported adopted wiki revisions, cross-referencing §5A.6. (From the v1.2 draft.)
• Conforming cross-references. §5.1, §6.4, §14.1, §15, and §20 were updated to cross-reference the new §5A.6, §5A.7, and the CLA where relevant. These are conforming edits, not new obligations.
• Entity-name correction. The provider is now identified consistently as "Synergy In Construction, LLC, a Wyoming limited liability company," correcting the prior description "a Wyoming corporation" in the preamble and conforming the notice block in §19.1. This aligns the Terms with the legal entity named in the Contributor License Agreement and the Privacy Policy. It corrects the entity's legal description only and does not change any party's rights or obligations.
• New §5B (Copyright Infringement Claims / DMCA Policy). Adds a complete DMCA notice-and-takedown framework: a Designated Copyright Agent and contact details (§5B.2), the required elements of an infringement notice (§5B.3) and counter-notification (§5B.4), a repeat-infringer termination policy (§5B.5), and the relationship between DMCA removals and the wiki revocation mechanism in §5A.6.3 (§5B.6). This implements the apparatus required for the DMCA §512 safe harbor for user-contributed content.
• New §17 (Dispute Resolution; Arbitration Agreement). Replaces court litigation plus a standalone class-action waiver with a mutual agreement to resolve Disputes by binding individual arbitration (AAA rules), with carve-outs for small-claims court and intellectual-property injunctive relief (§17.4), consumer-protective fee allocation (§17.6), the class-action waiver relocated inside the arbitration agreement with a blow-up clause sending class Disputes to court rather than class arbitration if the waiver is held unenforceable (§17.7), a staged-bellwether protocol for coordinated mass filings (§17.8), and a 30-day right to opt out of arbitration entirely (§17.10). The 60-day informal-resolution prerequisite from v1.1 §17.3 is retained as §17.2.
• New §4.5 (Beta and Preview Features). Disclaims availability and support commitments for features offered on an alpha, beta, preview, pilot, or early-access basis, reflecting the platform's active-development status.
• §5.3.3 (AI Training). Retitled "Current Practice and Opt-Out Rights"; states that as of the Effective Date SynC does not train AI models on User Content and that the Section preserves the right to do so, and commits to obtaining opt-in consent where applicable law requires it before using User Content for AI training. This aligns the Terms with the Privacy Policy's GDPR legal-basis disclosure.
• §8.4 (Restrictions). Adds a clarification that the restrictions — including the restriction on developing competing products — do not limit rights granted under the CC-BY-SA 4.0 license to SynC Standards content or under the CLA's Project Use Permission, resolving the apparent tension with §8.2's acknowledgment that third parties may fork openly licensed content.
• §10.1 / §16.3 (Fees and Termination). Adds a pro-rata refund of prepaid subscription fees for the current billing period if SynC terminates an account without cause.
• §13.1. Corrects the typographical error "SYNCING STANDARDS WIKI CONTENT" to "SYNC STANDARDS WIKI CONTENT."
• §20 (Acknowledgment). Adds an acknowledgment of the arbitration agreement, class-action waiver, and arbitration opt-out right.

22. Summary of Changes from Version 1.4

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.5 carries Terms of Service v1.4 forward in full. Every section other than those listed below is unchanged. Section 21 above is retained verbatim as the historical record of what v1.4 changed; the entity-name correction it describes reflected the entity's then-current Wyoming domestication, which this version supersedes.

• The entity redomesticated from Wyoming to Florida. Synergy In Construction, LLC completed a statutory conversion from a Wyoming limited liability company to a Florida limited liability company, effective upon the entity becoming active in Florida on August 2, 2026. A statutory conversion is a change of the entity's state of organization, not the creation of a new entity: the same legal entity continues, with the same Employer Identification Number, and it remains bound by and entitled to enforce every agreement it had already entered into. No contract, account, subscription, license grant, or obligation is transferred, assigned, novated, or terminated by the conversion. The provider is accordingly now identified throughout as "Synergy In Construction, LLC, a Florida limited liability company" (preamble, §19.1). This change of description does not, in itself, affect any party's rights or obligations.

• Governing law moved from Wyoming to Florida (§17.1). This is a material change and it does affect the parties' rights: the substantive law applied to these Terms and to disputes arising under them is now Florida law rather than Wyoming law. The prior text read:

  These Terms and any disputes arising out of or relating to these Terms or the Services shall be governed by and construed in accordance with the laws of the State of Wyoming, without regard to its conflict of law principles, except that the Federal Arbitration Act (9 U.S.C. § 1 et seq.) governs the interpretation and enforcement of the arbitration agreement in this Section 17.

  It now reads:

  These Terms and any disputes arising out of or relating to these Terms or the Services shall be governed by and construed in accordance with the laws of the State of Florida, without regard to its conflict of law principles, except that the Federal Arbitration Act (9 U.S.C. § 1 et seq.) governs the interpretation and enforcement of the arbitration agreement in this Section 17.

  The Federal Arbitration Act carve-out is unchanged: the FAA continues to govern the interpretation and enforcement of the arbitration agreement in §17, so the change of governing law does not alter the law applied to the arbitration agreement itself. Only the law applied to the balance of these Terms, and to Disputes that are not subject to arbitration, changes.

• Court venue moved from Wyoming to Florida (§17.9). This is a material change and it does affect the parties' rights: the forum in which a non-arbitrable Dispute must be brought has moved. The prior text read:

  For any Dispute not subject to arbitration under this Section 17, you agree that the action shall be brought exclusively in the state or federal courts located in Sheridan County, Wyoming, and you irrevocably consent to the personal jurisdiction and venue of such courts.

  It now reads:

  For any Dispute not subject to arbitration under this Section 17, you agree that the action shall be brought exclusively in the state courts located in Orange County, Florida, or in the United States District Court for the Middle District of Florida (Orlando Division), and you irrevocably consent to the personal jurisdiction and venue of such courts.

  The federal forum is now named expressly rather than by reference to "federal courts located in" the named county, because the federal court sitting in Orange County, Florida is the Orlando Division of the Middle District of Florida. The carve-outs in §17.4 are unaffected: small-claims claims may still be brought in any small claims court of competent jurisdiction, and claims for intellectual-property injunctive relief are routed to the courts identified in §17.9 as they were before. §17.6 (which measures SynC's filing-fee contribution against "the cost of filing the same claim in the courts identified in Section 17.9") and §17.7 and §17.8 (which send class Disputes and unenforceable coordinated-filing demands to "the courts identified in Section 17.9") pick up the new forum automatically and were not otherwise changed.

• Arbitration hearing location moved from Wyoming to Florida (§17.5). Where an in-person arbitration hearing is required, the location for organizational users is now Orange County, Florida rather than Sheridan County, Wyoming. This affects organizational users' rights as to hearing location. The rule for individual users is unchanged and unaffected: an in-person hearing for an individual user still takes place in the county where that user resides.

• DMCA counter-notification default forum (§5B.4). For a counter-notifying party located outside the United States, the consented federal forum is now the United States District Court for the Middle District of Florida, replacing the District of Wyoming. This conforms the §512(g)(3)(D) consent to the district in which SynC may now be found. It affects the rights only of a counter-notifying party outside the United States, and only as to forum.

• The street address was removed; contact is by email (preamble, §5B.2, §19.1). SynC no longer publishes a street address in these Terms. The party is identified as "Synergy In Construction, LLC, a Florida limited liability company," and notices to SynC are given by email to legal@synergyinconstruction.com (§19.1), DMCA notices and counter-notifications by email to the Designated Copyright Agent at the same address (§5B.2), and support requests to support@synergyinconstruction.com (§19.3). These are the same mailboxes the Terms already designated for these purposes, so no method of contact available to you under v1.4 has been withdrawn other than postal mail, and the informal-dispute-resolution notice in §17.2 and the arbitration opt-out in §17.10 were already email-based and are unchanged. §5B.2 now also states that the Designated Copyright Agent's registered contact details, including any mailing address required to be registered with the United States Copyright Office, are as recorded in that office's Directory of Designated Agents. Notice to you (§19.2) is unchanged and still may be given by mail to your address on file.

• No other change. No definition, license grant, disclaimer, limitation of liability, indemnity, fee term, termination right, wiki or standards provision, arbitration procedure, class-action waiver, or opt-out right is added, removed, or modified by v1.5.

Notice of these changes. Section 18.2 requires SynC to give notice of material changes by posting these Terms with a new Effective Date, sending email notification to your registered email address, and displaying a prominent notice in the Services. The governing-law, venue, and arbitration-location changes above are material, and notice is given by all three of those means. Section 18.2 does not prescribe an advance-notice period, and none is taken here; these Terms take effect on their Effective Date. The changes operate prospectively.

23. Summary of Changes from Version 1.5

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.6 carries Terms of Service v1.5 forward in full. Every section other than those listed below is unchanged. Sections 21 and 22 above are retained verbatim as the historical record of what v1.4 and v1.5 changed; their references to "Vested Access" describe provisions as they existed in those versions.

• "Vested Access" is removed; project access granted through share links is now revocable by the project owner (§6.2). This is a material change. Former §6.2 provided that a recipient who accepted a share link obtained permanent access to the shared project revision, that revoking a share link did not affect access already granted, and that the sharer could not unilaterally revoke a recipient's access. The Services now provide the opposite: a project owner may remove a recipient's access at any time, and deleting a project ends all recipients' access. New §6.2 (retitled "Access Duration and Removal") states this, states what removal cannot do — it does not retrieve copies a recipient exported, downloaded, or printed while their access was active — and puts recipients on notice that access to a shared project exists at the project owner's discretion and that these Terms grant a recipient no right to continued access. No recipient accepted a share under the v1.5 language, so no access granted under the former provision exists to be affected by this change.
• §6.1 and §6.4 disclose the per-link export control. A sharer now chooses, per share link, whether recipients may export the shared project through the Services, and access forwarded from a share link carries at most the export setting of the link it came from. §6.2's recipient notice conditions its record-keeping guidance on this setting — a recipient whose export is not enabled is directed to the sharer, and the Terms grant no right to copy or retain content beyond the access and export the sharer enabled. §6.4 makes the export choice, and its consequence — an exported copy is outside the control of the Services and is not retrieved by removing access — an express sharer responsibility.
• §5A.6.4 restated as a freestanding limit on SynC's authority. Former §5A.6.4 ("Effect on Vested Access") framed SynC's errata and revocation authority as an exception to the Vested Access principle. With that principle removed, §5A.6.4 (retitled "Limits on SynC's Exercise of This Authority") restates the same commitment as a direct limit: SynC exercises the §5A.6 authority only in the circumstances described in §5A.6.2 and §5A.6.3 and will not use it to remove or alter content within a customer's project for ordinary commercial or editorial reasons. The scope of the errata and revocation authority itself (§5A.6.2, §5A.6.3) is unchanged.
• Conforming edits. §5A.6.2 (errata-banner acknowledgment), §6.4 (sharer responsibility for managing recipient access), §16.3 (effect of account termination on shared access), and §20 (acknowledgment) were conformed to the removal of Vested Access. These carry no obligations beyond those stated in §6.2 and §5A.6.4.
• No other change. No definition, license grant, disclaimer, limitation of liability, indemnity, fee term, wiki or standards provision, arbitration procedure, or opt-out right is otherwise added, removed, or modified by v1.6. The retention of records of distribution events is addressed in the Privacy Policy (v1.7), not these Terms.

Notice of these changes. The replacement of §6.2 is a material change and notice is given by the three means Section 18.2 provides. As of the Effective Date, no share had been accepted under the former §6.2, so the change operates prospectively and affects no access previously granted.

24. Summary of Changes from Version 1.6

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.7 carries Terms of Service v1.6 forward in full. Every section other than those listed below is unchanged. Sections 21 through 23 are retained verbatim as the historical record of what v1.4, v1.5, and v1.6 changed.

Every change in this version but one runs in the same direction: SynC gives up rights it had reserved over your content, and states more precisely what it does instead. No fee, liability, indemnity, dispute-resolution, or sharing provision is touched.

The one exception is §8.5 (Feedback), which is broader than before. It now reaches feedback you direct to SynC about the content of the SynC Standards library, which it did not previously cover, and it takes a perpetual, irrevocable licence over that material — including, where SynC incorporates it into a published Standard, a licence to the public under CC-BY-SA 4.0. That is a genuine extension and it is described in full below. It applies only to content you choose to send to SynC; §7.5 and §5.3.1 keep everything you write for your own project outside it.

• §5.3 renamed and reframed as a limit, not a grant. The heading "Data Usage for Service Improvement and AI Training" and the notice "You grant SynC the right to use User Content in the following ways" are replaced by "Limits on Our Use of Your Content" and a statement that the Section is a limit on SynC's rights. The Section's carve-in for legal and business disclosures described in the Privacy Policy (for example, response to legal process under §5A.6.3, and business transfer) is stated expressly so the limit is accurate rather than absolute.

• §5.3.1 replaced: SynC will not use your content as training or research material. This is the substantive change. Former §5.3.1 permitted SynC to anonymize User Content — by removing names, company names, and project names — and to use the result to train AI models, develop features, conduct research, and create industry benchmarks, and stated that once anonymized the content "is not considered confidential." That permission is withdrawn in full and does not survive in any form. New §5.3.1 states that SynC does not use User Content, or any adaptation or excerpt of it, to train, fine-tune, or improve any generative AI model, or any general-purpose or foundation model, whether SynC's own or a third party's, and whether or not it has been anonymized, de-identified, or aggregated; and does not license, sell, publish, or otherwise disclose User Content to any third party for those purposes. It further states that removing identifying details from a specification does not change its confidential status.

  Two boundaries are drawn expressly rather than left to interpretation. Operational models — models that classify, score, match, rank, or flag content inside the Services, such as identifying what kind of value a datasheet field holds or detecting an entry outside its normal range — sit outside the prohibition, but only if all three stated conditions hold: the model produces structured outputs and does not generate text; it is used only to operate the Services and is never distributed, licensed, or sold; and neither it nor its outputs reproduce your content to anyone not already authorized to see it. Where such a model is built from more than one customer's content, it may be used only to operate the Services and never to disclose one customer's content to another. The "does not generate text" condition is the load-bearing one: a model that emits only labels and scores has no channel through which a specification could surface, which is a property that can be verified from the model's design rather than asserted about its behaviour.

  Separately, SynC may use User Content in a way §5.3.1 otherwise prohibits only under a separate written agreement you execute that identifies the content and the use. Accepting these Terms is not such an agreement, and SynC will not require one as a condition of providing the Services to you — so the exception cannot become a default by attrition.

  The former clause was also internally inconsistent with §5A.7.2, which promises that a project specification is your confidential work product. Both could not be true of the same document. That conflict is resolved in favour of confidentiality.

  This change is retroactive. New §5.3.1 applies to all User Content whenever submitted, including content submitted before this version took effect. Nothing was ever done under the former clause — v1.6 §5.3.3 already stated that SynC did not train AI models on User Content — so no use made under it needs to be unwound.

  §5.3.1 states four things it does not restrict: content you offer for inclusion in the SynC Standards library, which the Contributor License Agreement governs (a); Feedback you direct to SynC, which §8.5 governs (b); SynC Standards content as published in the public library, which is licensed under CC-BY-SA 4.0 (c); and the statistics described in §5.3.2 (d). Paragraphs (a) and (b) describe content you deliberately send outward, not content that sits in your project: §5.3.1 states expressly that content you write inside your own project for your own project's participants is not a Contribution and does not become one because it concerns a Standard you imported.

• §5.3.2 replaced: the line is drawn at expression. Former §5.3.2 permitted collection and analysis of "usage patterns, feature utilization, and interaction data." New §5.3.2 keeps that and states what it covers and what it does not: counts, frequencies, distributions, timings, error rates, and feature-utilization patterns are measurements about content, and may not include or be used to reconstruct the text of your specifications. Where a statistic could identify an individual customer, it is reported only in aggregate. This narrows what §5.3.2 permits by drawing an express boundary that the former text left open.

• §5.3.3 replaced: the AI-training opt-out is removed because the use it opposed is gone. Former §5.3.3 stated that SynC did not currently train on User Content, reserved the right to begin doing so, and offered an opt-out and a commitment to obtain opt-in consent where law required it. The reserved right is withdrawn by new §5.3.1, so the opt-out has nothing to operate on and is removed. No user is disadvantaged: the practice being opted out of never occurred, and the new position is stronger than any opt-out — the use is forbidden for everyone rather than declinable by request. New §5.3.3 addresses what actually happens instead: delivering AI features and search requires transmitting the content you are working with to inference and embedding providers, and SynC does not permit those providers to retain your content for their own purposes or to train on it, enforcing this by technical configuration rather than by a direct contract with each host. It names no vendor and no jurisdiction, because both change; those are disclosed in the Privacy Policy and on the subprocessor list it references. SynC may change providers, hosts, or mechanisms, and will give notice under §18.2 before a change that materially reduces the protections described in the Section takes effect. The Section deliberately does not freeze the level of protection at the level in force when you accept — it commits to telling you before it moves downward, so that you can decide what to do about it.

• §5.2 conformed. "Create derivative works as necessary to provide and improve the Services" becomes "to provide the Services and to operate them as described in §5.3." A general "improve the Services" grant sitting above a Section that forbids model improvement is a seam; the licence is now expressly bounded by §5.3.

• §8.5 (Feedback) extended to the SynC Standards library. Former §8.5 licensed feedback "about the Services." It now expressly covers feedback about the content of the SynC Standards library — including reporting an error in a published Standard, and sending a comment or question to SynC about a Standard through a feature that indicates the content will be sent to SynC — and the licence extends to incorporating Feedback into the library as well as the Services. Two limits are stated in the same Section. First, Feedback is content you direct to SynC; content you write for the participants in your own project is not Feedback and is governed by §5.3.1. Second, the licence is to use Feedback in the Services and the library — it is not a licence to train models on it, which §5.3.1 forbids regardless.

  A third limit closes a licensing gap in the same Section. The SynC Standards library is published to the public under CC-BY-SA 4.0. A licence permitting SynC to incorporate Feedback into the library would not, by itself, permit SynC to publish the incorporated material under CC-BY-SA — so the first time a report containing proposed text was folded into a Standard, SynC would be publishing material it had no right to licence onward, and §5A.1 would be false as to that material. §8.5 therefore also licenses the incorporated material to the public under CC-BY-SA 4.0 as part of the Standard, and treats the Section as a request under CC-BY-SA 4.0 §3(a)(3) that attribution be omitted. Anyone who wants their contribution credited is directed to submit it as a Contribution under the Contributor License Agreement instead, which preserves attribution under CLA §2B.

  This closes a gap the amendment would otherwise have opened. Contributor License Agreement §1 excludes discussion, commentary, and feedback features from the definition of a Contribution, so a report of an error in a Standard is not a Contribution; and new §5.3.1 forbids SynC from using User Content to improve anything. Without this change an error report would have been covered by neither instrument, and SynC could not have acted on it.

• New §7.5 (Comments Are Not Feedback to SynC). States in the comments Section what §5.3.1 and §8.5 establish: a comment you write for your project's participants stays with your project, and a feature that sends something to SynC about a public Standard will say so before you send it. This creates an obligation on SynC, not on you — the labelling requirement is what makes the distinction between §5.3.1 content and §8.5 Feedback observable rather than a matter of SynC's characterization after the fact.

• §5A.2 and §5A.3 conformed to the Contributor License Agreement. §5A.2's list of what the CLA governs now also names the additional licence contributors grant SynC (CLA §2D) and SynC's editorial and moderation rights (CLA §2E). §5A.3 states that the rights it describes are those granted by CLA §2E and that this Section adds nothing to them. This is a correction of a structural defect, not a new right. §5A.2 provides that nothing in Section 5A grants SynC any right in a contribution beyond what the CLA grants, and that the CLA governs any conflict — so §5A.3's moderation rights were, as drafted, subordinated to a CLA that did not expressly grant them. CLA v2.4 §2E now does.

• §5A.7.2 (The Project Specification). One sentence appended: your project specification is not used as training or research material, cross-referencing §5.3.1. The Section's substance is unchanged; the sentence puts the promise where a reader looking at project confidentiality will find it.

• §4.2 (AI-Powered Features). One sentence appended cross-referencing §5.3.3 for how content reaches third-party AI services and what they may do with it. No change to the AI disclaimers.

• §20 (Acknowledgment) corrected. The acknowledgment "You acknowledge that SynC may use anonymized User Content for AI training and service improvement" stated the opposite of v1.6 §5.3.3's operative term and is deleted. It is replaced with a plain-language statement of §5.3.1, §5.3.2, and §5.3.3 and their exceptions. A reader who reads only the acknowledgment now gets the same answer as a reader who reads the operative text.

• Drafting annotations removed. The inline reviewer's notes carried in the v1.6 reference file were editorial annotations addressed to counsel, not terms, and were already excluded from the published v1.6 by the publishing migration's content guard. They are not carried into this version's text. No operative sentence they annotated is changed by their removal. Open items are recorded in Appendix A, which is not part of these Terms.

• No other change. No definition, disclaimer, limitation of liability, indemnity, fee term, termination right, sharing or distribution provision, wiki errata or revocation provision, arbitration procedure, class-action waiver, or opt-out right is added, removed, or modified by v1.7, other than the removal of the AI-training opt-out described above, which is removed because the practice it applied to is now prohibited outright.

Notice of these changes. The withdrawal of a reserved right to use User Content for AI training, the removal of the corresponding opt-out, and the extension of the Feedback licence are material changes, and notice is given by the three means Section 18.2 provides. The changes to §5.3 operate retroactively as stated in §5.3.1, which is to your benefit; every other change operates prospectively.

25. Summary of Changes from Version 1.7

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.8 carries Terms of Service v1.7 forward in full. Every section other than those listed below is unchanged. Sections 21 through 24 are retained verbatim as the historical record of what v1.4 through v1.7 changed.

This version makes one change, and it is a disclosure rather than a reallocation of rights. The Services now store your conversations with the AI assistant instead of holding them only in your browser. No licence, ownership, disclaimer, limitation of liability, indemnity, fee, sharing, wiki, or dispute-resolution provision is added, removed, or modified.

• New §4.2.1 (Your Conversations with the AI Assistant). States four things: that conversations are stored so that they remain available to you after you close them; that a conversation is your own record and private to you — no other user can view one through the Services, conversation content enters no published document, revision record, or export of project content, and a conversation is retained for you even where you later cease to have access to material discussed in it; that conversations are retained for a stated period and then deleted automatically; and that you may delete any conversation at any time and copy one out as readable text. It also states that the messages you send to the assistant are your User Content under §5.1, so §5.3 — including the prohibition on using your content as training or research material in §5.3.1 — applies to them.

  The retention period is not stated here. §4.2.1 cross-references the Privacy Policy, which defines the period, states how it is measured, and states its relationship to account deletion. This follows the practice these documents already use for the AI-provider constraints in §5.3.3 and for the distribution-record retention rule: one definition, in one document. A period restated in two instruments is a period that will eventually be stated two different ways.

• §16.3 (Effect of Termination) extended by one bullet. Records that conversations are retained through the period in which a terminated account can still be restored — so that restoring the account recovers them — and are deleted when the account is permanently deleted. This is where a reader closing an account will look for it.

• §20 (Acknowledgment) extended by one bullet, stating §4.2.1 in plain language so that a reader of the acknowledgment gets the same answer as a reader of the operative text.

• No other change. Nothing in §5 (including §5.1 ownership and the §5.3 limits), §5A, §5B, §6, §7, §8, §9 through §15, §17, §18, or §19 is added, removed, or modified by v1.8.

Notice of these changes. The Services beginning to retain a category of your content that was not previously retained is a material change, and notice is given by the three means Section 18.2 provides, in step with the corresponding Privacy Policy version. The change operates prospectively.

26. Summary of Changes from Version 1.8

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.9 carries Terms of Service v1.8 forward in full. Every section other than those listed below is unchanged. Sections 21 through 25 are retained verbatim as the historical record of what v1.4 through v1.8 changed.

• §5.5 (User Content Restrictions) — one bullet added. The new bullet names one case of a restriction §5.5 already imposed: content you hold under a license from a third party, such as a subscription master specification library, may not be reproduced on the Services beyond what that license permits, including any limit the license places on storage outside your own systems, on who may access the content, or on its use with AI features. This adds no new restriction. §5.4 already had you warrant that you hold the licenses needed to upload your content, and §5.5 already prohibited infringing content; the bullet names the situation so that it is not overlooked. It states in your favour, because it is true, that project specifications you prepare from licensed content under that license are not affected: preparing and distributing project specifications is what such a license is for. It grants SynC no right, changes no allocation of responsibility, and does not make SynC a party to, or a judge of, your license with the third party.

This version replaces Section 10 (Fees and Payment) in full, so that it describes what SynC actually sells and how it actually charges. Former §10 was written for a product that did not exist: it said subscription fees were billed "as selected during registration" and that "you authorize SynC to charge the payment method on file for all applicable fees," when no plan was ever selected at registration and the Services never held a payment method. SynC now sells seats by subscription and prepaid AI credit packs on a third-party payment processor's hosted pages, with the payment method held by the processor, subscriptions that renew automatically, and a hosted billing portal for changes and cancellation. New §10 states that, and states the things that protect you — what is free, what a lapse does and does not do, what is refunded and what is not — in the same place. §10 remains about fees for the Services and nothing else. No licence, ownership, disclaimer, limitation of liability, indemnity, sharing, wiki, or dispute-resolution provision is added, removed, or modified.

• §10.1 (What Is Sold, and What Is Not) — new. States first what is not charged for: reading, commenting on, responding to, and exporting content shared with you. States that a seat is required to start projects and author, and that credits are required for the AI assistant beyond an allowance. Names the three things SynC sells — full seats, collaborator seats, and AI credit packs — and that there are no plans or tiers. Seats and credits are held by your firm, not by you individually. The fee is the price shown at purchase or, where seat or credit fees have been agreed in writing, the fee in that "Order"; nothing is selected or incurred by registering. Fees are in U.S. dollars, exclusive of taxes, and non-refundable except as required by law, as these Terms or an Order state, or under §16.3. The former rule that an Order was the only source of a fee is withdrawn, because the Services now sell directly.

• §10.2 (The Introductory Seat and the Trial) — new. States that every firm receives one introductory full seat and a fixed-period trial of additional seats at creation, that neither is purchased or carries a fee, that the introductory seat is an allowance and not a subscription, that SynC may change what new firms receive at any time and may change or withdraw an existing firm's introductory seat on §18.2 notice, and that the end of either is a lapse under §10.6, not a termination.

• §10.3 (Purchasing, and the Payment Method) — new, and it grants the authorization former §10.2 claimed without basis. Purchases are made for your firm by a person it has authorized, on the processor's hosted page; card details go to the processor and SynC does not receive or store card or bank account numbers; the processor, not the Services, holds the payment method. Authorization to charge: buying a seat subscription authorizes the charge of the firm's payment method at the start of each period, and pro-rated for seats added mid-period, until cancellation; buying a credit pack authorizes a single charge; nothing else is authorized. States the rule for a purchase made during the trial: payment method collected at purchase, seats available at once, first charge on the day the trial ends unless the trial ends within 49 hours, in which case the charge is immediate. Invoices and receipts are available from the billing portal; the billing mailbox is named.

• §10.4 (Subscription Period, Renewal, Changes, and Cancellation) — new. A subscription runs monthly or annually and renews automatically for the same length at the fee then in effect, charged in advance, unless cancelled. Through the processor's billing portal your firm may add seats (effective at once, charged pro-rated for the rest of the period), remove seats (effective at the end of the period, nothing refunded), cancel (the renewal stops, the paid period runs out, nothing refunded), update the payment method, and download invoices. The Services state the count a subscription renews at and the date. An Order governs over a fee shown in the Services if they differ.

• §10.5 (AI Credits) — new. Each full seat carries a personal monthly allowance that refreshes on the first of the month, does not roll over, is the seat holder's alone, and ends with the seat. Packs are the firm's balance, drawn under the administrator's drawing setting, not expiring at month end, available while the account is open. Purchased credits are non-refundable, not redeemable for money, and have no cash value. SynC does not bill for credits after use and does not extend credit; the cost of an exchange is shown with the answer; the conversion rate is not published and may change.

• §10.6 (Lapse) — new, and it is the retention and export term the entitlement specifications required before the first paying customer. Defines a lapse (subscription end, trial end, allowance withdrawn, seat released), states that a lapse is not a termination, and states what is kept — reading, commenting, responding, exporting, and every revision, comment, and export exactly as it was — and what is lost: changing specifications and datasheets, saving revisions, starting projects, writing with the assistant. Notice precedes a lapse whose date is known. Reseating restores the prior role.

• §10.7 (Price Changes) — carried forward and conformed. The 30-day notice period is unchanged. A change does not alter a period already charged or a fee agreed in an Order for its period; it applies from the first renewal after the notice period and to new purchases and Orders after it. A sentence is added telling you how to decline a changed fee — cancel before the renewal at which it applies — and acceptance is tied to continuing past that renewal, not to mere continued use of the Services.

• §10.8 (Failed Payment and Non-Payment) — replaces former §10.4 (Late Payment). States what actually happens when a charge fails: the processor retries, SynC notifies the firm, seats stay in place during the retries, and if the charge cannot be collected the subscription ends and the seats lapse under §10.6 at the end of the last paid period. Suspension or termination under §16.2 remains available for non-payment of an Order invoice or an uncollectable charge. No interest, late fee, or collection charge is imposed.

• §16.3 (Effect of Termination) conformed. The pro-rata refund on termination by SynC without cause now refers to fees your firm has paid for the current subscription period, and is extended to purchased credits that remain unused at such a termination, refunded at the price paid. Without the extension, a firm terminated without cause would lose a prepaid balance it had no chance to use.

• §20 (Acknowledgment) — the former §10 bullet is replaced by three, stating §10 in plain language: what is free and where purchases are made; that a subscription renews automatically and the firm's payment method is charged each period until cancelled from the portal, with decreases and cancellation effective at period end and no refund of the paid period, and credits prepaid and non-refundable; and what a lapse keeps and loses.

• §11 (Privacy and Data Protection) unchanged. It continues to refer you to the Privacy Policy, which as of Privacy Policy v1.11 discloses the payment processor, the integration between it and the Services, what each side sends the other, and where it processes.

• No other change. Other than the §5.5 bullet described above, nothing in §1 through §9, §5A, §5B, §12 through §15, §17, §18, or §19 is added, removed, or modified by v1.9. §16.2's "non-payment of fees" ground for termination is unchanged. §14.2's liability cap, measured by "the amount you paid to SynC in the 12 months preceding the event," is unchanged; under new §10 that amount is what your firm has actually been charged for seats and credits.

Notice of these changes. The replacement of the fee and payment terms is a material change, and notice is given by the three means Section 18.2 provides, in step with the corresponding Privacy Policy version. No payment was ever taken under former §10, so nothing already charged is affected; every change operates prospectively, and the authorization in §10.3 is given by the act of purchasing, after these Terms are in force, and by no other act. The §5.5 bullet is a clarification of an existing restriction and is not by itself a material change; it is noticed together with the §10 changes.

27. Summary of Changes from Version 1.9

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.10 carries Terms of Service v1.9 forward in full. Every section other than §10.5 is unchanged. Sections 21 through 26 are retained verbatim as the historical record of what v1.4 through v1.9 changed.

• §10.5 (AI Credits) — the month a seat's credit allowance runs for is now the subscription's billing month. Version 1.9 said the personal allowance "refreshes on the first day of each month," which is the calendar month. Under this version the allowance runs for each month of the subscription that provides the seat: the month begins on the day the subscription renews and, for an annual subscription, on the same day of each month within the paid year, so that a firm's invoice and its credit month name the same day. A seat that no subscription provides, such as the introductory seat, keeps the calendar month. The allowance is in place while the seat is, including while a failed payment is being retried under §10.8, and ends when the seat lapses. Nothing else in §10.5 changes: the allowance still does not carry over and is still the seat holder's alone, and the sentences on credit packs, refunds, cash value, and the absence of any charge after use or extension of credit are as they were. A firm that holds a subscription when this version takes effect moves to its billing month at once; no allowance in use on that date is reduced by the change.

• No other change. Nothing in §1 through §9, §5A, §5B, §10.1 through §10.4, §10.6 through §10.8, or §11 through §20 is added, removed, or modified by v1.10.

Notice of this change. The change alters when a seat's allowance refreshes, not its amount, and grants SynC nothing. It is noticed by the means Section 18.2 provides.

28. Summary of Changes from Version 1.10

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.11 carries Terms of Service v1.10 forward in full. Every section other than those listed below is unchanged. Sections 21 through 27 are retained verbatim as the historical record of what v1.4 through v1.10 changed.

This version makes two sets of changes. The first discloses the hold, the instrument SynC ordinarily uses to withhold material from an adopted SynC Standards revision, and what a hold does inside a project (§5A.6, §5A.7.2, §5B.6, §6.2, with conforming edits to §14.1 and §20). Those changes are material under §18.2. The second discloses that deleting a project is reversible for a limited period (§6.2). That change is not material under §18.2: it adds a capability for project owners and removes nothing from anyone.

The moderation changes.

• §5A.6 now describes the hold, which is the instrument SynC ordinarily uses, alongside errata and revocation. Former §5A.6 authorised two instruments. The Services operate three: an erratum annotates an adopted revision, a hold withholds identified material while the adopted revision stays published, and a revocation removes the adopted revision itself. §5A.6.3 is redrafted around all three and around the rule that SynC acts on identified clauses where a notice identifies them, on the standard as a whole where it does not, and never on a whole project revision. A hold on identified clauses withholds those clauses on every adopted revision that carries them; a hold on a standard as a whole withholds every clause of it on every adopted revision; a revocation withholds one adopted revision. The heading of §5A.6 and the first paragraph of §5A.6.1 are conformed. This is a material change under §18.2, because it discloses restrictions on what a customer may do with their own project that former §5A.6 did not describe.
• A hold attaches to a position within a standard and is ended only by a SynC moderator. It reaches every adopted revision carrying that position, including later ones; editing the material does not end it; moving a project to another adopted revision does not clear a hold on the standard as a whole; and while a hold stands, no new revision of that standard is adopted. Material: it withdraws the ability to move to a corrected revision without SynC acting first, and former §5A.6.1's commitment to preserving imported references is made expressly subject to it.
• §5A.6.3 defines "SynC moderator". A SynC moderator is a person SynC has appointed to moderate the SynC Standards, whether or not that person is SynC staff, and their acts under §5A.6 are SynC's own. A hold is therefore SynC's act whoever performs it, which is how the public moderation log already states it; a community-issued erratum remains community speech under §5A.6.5.
• §5A.6.6 names and defines the two levels. A reference hold (level 1) stops the material leaving the Services on every surface while project administrators keep a read-only on-screen reference view; a full hold (level 2) withdraws that view as well. A full hold is applied from the outset only under legal compulsion or during a counter-notification period, and a reference hold becomes one when the §5A.6.7 period ends. The levels were already recorded on each action and published in the moderation log; no document defined them. Material as to the full hold, which withdraws a view a customer would otherwise keep.
• §5A.6.7 states two periods and distinguishes them. The project administrators' reference view is bounded: thirty days after a corrected revision becomes available or the held clauses are released from a stated revision onward, and ninety days after the action opened, whichever is earlier. The hold itself is not bounded, ends only when a moderator lifts or releases it, and may stand indefinitely. Material: a reader of the published period would otherwise take it for a limit on the withholding.
• §5A.6.8 states what a hold does inside a project. A project revision may be published after the publisher acknowledges what is withheld, and the withheld-material statements are applied at read time rather than fixed into the revision, so a later lift restores the material inside an already-published revision. Distribution and export continue, carrying the statements. Customization of the affected standard is not available while a hold on the whole of it, or a revocation, stands, and is available where the hold reaches particular clauses; no corrected revision becomes available to the project until a moderator acts. The customer's three exits are stated: move to an adopted revision a moderator has released, remove or replace the standard, or write their own text into the withheld clause of a customized copy, after which that copy no longer carries the hold. SynC records the replacement and makes no judgment about it, and none of the three lifts the hold on the standard itself. Material, and it is also the disclosure that makes the acknowledgment SynC now asks for at publish time intelligible.
• §5A.6.4's limit is extended from altering project content to restricting what may be done with a standard in a project, so that the limit reaches the authority §5A.6.8 describes. Favourable to the user.
• §5A.6.5's disclaimer reaches holds, in addition to errata and revocation, and now names the consequences §5A.6.8 discloses. Material: extending a liability disclaimer to a new class of act reduces a user's ability to claim. A third paragraph adds that SynC's exercise of this authority is not a representation about the accuracy, quality, originality or lawfulness of any content or about anyone's conduct, mirroring CLA §2E.3, which binds contributors only, so that it binds as to all users and readers. The second paragraph now says that community-issued errata are issued by community administrators, which names the role that issues them; the two categories of erratum, and SynC's responsibility for each, are unchanged.
• §5A.6.3 states what the public moderation log contains and what it does not. Former §5A.6.3 promised two things; the log publishes the action, date, reason category, level, the standard and adopted revision reached, the number and section numbers of clauses reached, an address for each entry, and the related entries in the same matter, and publishes no moderator identity, no reporter identity, no free-text note, no withheld text, no author, and no project. Entries are not deleted when what they describe is removed. Publishing more than promised removes nothing, and the register is the one place SynC's own conduct is on the record.
• §5A.6.3's two unqualified commitments, the log entry and the notification, gain the carve-out the third already carried, "except where prohibited by law or court order". Both are now actually performed, and this covers the only case in which SynC could not perform them.
• §5A.6.3 says "project owners and administrators". The Services notify every user with administrator authority over an affected project, which is broader than "owners" and is what SynC performs.
• §5A.6.3 reconciles the published notice to what SynC actually publishes. The notice takes a fixed form drawn from a published vocabulary; a moderator's internal free-text note is never published at any level; and SynC may, at its discretion, publish a statement of its own about an action, as its own speech, withdrawable.
• §5A.7.2 states the datasheet carve-out. Values you entered are your User Content, are retained, and stay visible at both levels, together with the field labels and units needed to read them. The standard's guidance and descriptive text is withheld with the rest.
• §5B.6 is conformed. Access to material subject to a DMCA notice may be disabled through the hold or revocation mechanism; where a notice identifies clauses, SynC holds those clauses rather than revoking the revision; a notice lacking the identification §5B.3 requires is deficient, and SynC may ask for that identification before, during or after acting.
• §6.2's moderation paragraph is conformed and made complete. A hold or revocation does not end anyone's access to a project and does not change who may read it. What changes is that the material under notice is marked as withheld where it sat: for recipients, in exports, and at a full hold for the project's own administrators. §6.2's recipient paragraph records the same fact from the recipient's side, in one sentence.
• §14.1 and §20 are conformed. The exclusion of damages in §14.1 names the placing of a hold beside the issuance of an erratum and a revocation, which §5A.6.5 already covered; and the acknowledgment in §20 names the hold and states §5A.6.8 in plain language, so that a reader of the acknowledgment gets the same answer as a reader of the operative text. Neither adds an obligation beyond those stated in §5A.6.

The restore-window change.

• §6.2 discloses that deleting a project is reversible for a limited period, and that restoring it returns recipients' access. The Services now allow a user with authority over a project to restore it after deletion, for a period stated in the Privacy Policy. Former §6.2 stated only that deleting a project ends all recipients' access: still true, and still the immediate effect, but silent on the fact that the deletion can be undone. This is not a material change under §18.2: it adds a capability for project owners and removes nothing from anyone. The amended bullet states expressly that no one, not the owner and not SynC, is obliged to restore a project, and that a recipient acquires no right to have one restored. This is consistent with, and does not disturb, the existing statement in the same Section that SynC has no obligation to any recipient to maintain, restore, or preserve access.

• §6.2's recipient paragraph records that access may resume, silently, and that a recipient should not rely on it. Removal of access has always been silent as to notification; restoration is silent in the same way. The paragraph's existing guidance, to make the record you need while your access is active, is unchanged and is the reason this is stated rather than left to be discovered.

• No other change. Beyond Sections 5A.6, 5A.7.2, 5B.6, 6.2, 14.1 and 20 as described above, no definition, license grant, indemnity, fee term, seat or billing term, arbitration procedure, or opt-out right is added, removed, or modified by v1.11. The retention of a deleted project's content, and the length of the restore period, are addressed in the Privacy Policy (v1.12), not these Terms; so are the retention rules for moderation records.

Notice of these changes. The moderation changes are material, and notice is given by the three means Section 18.2 provides, in step with the corresponding Privacy Policy and Contributor License Agreement versions. Section 18.2 does not prescribe an advance-notice period, and none is taken here; these Terms take effect on their Effective Date, and every change operates prospectively. The restore-window change is not material and is noticed together with the moderation changes.

29. Summary of Changes from Version 1.11

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.12 carries Terms of Service v1.11 forward in full. Every section other than those listed below is unchanged. Sections 21 through 28 are retained verbatim as the historical record of what v1.4 through v1.11 changed.

This version makes five sets of changes. The first states SynC's repeat-infringer policy as it operates (§5B.5), states that the author of material in the SynC Standards library that SynC withholds in response to a copyright notice receives a copy of that notice by email, with the sender's contact details removed (§5B.3, §5B.4), and conforms §5A.6.3 to the notices the Services send. The second restates SynC's rights of suspension and termination in one place (§16.2), with §3.3 and §9.3 now pointing to it and §16.3 conformed. The third states where the Services are offered: to customers in the United States, with a paid plan requiring a United States entity (§2, §10.3, §16.2, §20). The fourth states what applies when you sign in with a Microsoft or Google account (§3.4). Those changes are material under §18.2. The fifth corrects §5.3.3's description of how a request reaches an inference provider, conforms its pointer to the subprocessor list as now published, and extends its commitment to the facts about you that a request carries. That change is not material under §18.2: it corrects a description in the user's favour and adds a commitment.

The repeat-infringer policy and copyright notices (§5B.5, §5B.3, §5B.4, §5A.6.3).

• §5B.5 states the policy in full. Former §5B.5 was one sentence: SynC would, in appropriate circumstances, terminate the accounts of repeat infringers. The Services now operate a graduated policy, and the Section describes it: what counts as a notice standing against a user; that the ordinary consequence when the notices standing against a user reach a set number, which may be as low as one, is suspension of the user's ability to contribute to the SynC Standards Wiki and nothing else; that the user is notified, that the suspension is recorded privately, that a site administrator may lift it with a recorded reason, and that the user may write to legal@synergyinconstruction.com; and that SynC will terminate the account in appropriate circumstances, with examples. It also states that a notice about material in a project is handled under §5B.3 and §16.2 and is not counted toward the suspension. This is a material change: it discloses a sanction with a low threshold that former §5B.5 did not describe. It withdraws nothing: the ordinary consequence is narrower than the account termination former §5B.5 named, and account termination remains available in the circumstances stated.
• §5B.3 tells the sender of a copyright notice what happens to it. Where a notice identifies material in the SynC Standards library and SynC acts on it, the author of the identified revision receives by email a copy of the notice as SynC received it, with the sender's postal address, telephone number and email address removed and the sender's name or organization kept, together with a fixed statement that the notice is the sender's statement and that SynC has made no finding on it. SynC does not summarize or characterize the notice. Where SynC has no email address for the author, no copy is sent and that is recorded. The paragraph does not apply to a notice about material stored in a project. Former §5B.3 said nothing about what became of a notice once received. This is a material change as to the sender, whose name now reaches the author of the material identified, and it is stated where a sender will read it before filing.
• §5B.4 states what the author receives, and why. The notice of a disabling action tells you that you may counter-notify, and SynC emails you the copy described above, so that the sworn statement a counter-notification requires can be made knowing what was claimed and by whom. The copy goes by email only; the notification in the Services says that a copy has been emailed and carries none of the notice's text. The copy and the statement sent with it are private, are not a publication, and are not a view by SynC on the merits; the public moderation log continues to identify neither the reporter nor the author. §5B.4 also says in plain words that a counter-notification is forwarded to the sender of the notice with the name, address and telephone number it contains, which former §5B.4 already provided for. Favourable to contributors.
• §5A.6.3's notification bullet names every party the Services notify: project owners and administrators, the author of the revision the notice identified, the other contributors to the standard, and on a revocation or restoration the contributors to the adopted revision. It states that on a copyright basis the notification carries the counter-notification statement and that the author receives the copy of the notice by email. Former text named project owners and administrators only. Favourable to contributors, and it matches the Privacy Policy and CLA §2E.1.

Suspension and termination (§16.2, §3.3, §9.3, §16.3).

• §16.2 now says in one place what SynC may do and on what terms. Former §16.2 listed grounds and ended "at our discretion for any reason or no reason". The Section now states three things separately. What SynC may do: suspend or terminate a person's or a company's account, or suspend, limit or withdraw access to any part of the Services (a feature, content, a share link, an API key, the AI assistant), and remove or decline to display content. When SynC may act at once and without prior notice: for cause, with the grounds listed, and with a statement of the ground and a route to reconsideration where the law allows. When SynC acts at its discretion for any reason or none: on thirty days' notice, with the refund in §16.3 and the export period in §16.4. It also states that terminating a person's account leaves their company's projects with the company, and that a consumer's non-waivable local rights are untouched. This is a material change: the authority to suspend a part of the Services and the authority over a company's account are stated for the first time; the notice and refund on the discretionary path are new commitments in the user's favour.
• §3.3 and §9.3 now point to §16.2 rather than stating termination rights of their own.
• §16.3's refund bullet is tied to the discretionary paragraph of §16.2 instead of to a parenthetical, and a bullet states that API keys are revoked and sessions ended on termination.

Where the Services are offered (§2, §10.3, §16.2, §20).

• §2 states that SynC offers the Services to customers in the United States and does not direct them elsewhere. Former text was silent on where the Services are offered. §2 now says so, and says in the same paragraph what does not depend on where you are: reading, commenting on, responding to and exporting a project shared with you, and reading the SynC Standards library. SynC does not block either from outside the United States. The promise in §10.1, that everyone who receives your project reads, comments, responds and exports free, is unchanged by this version, and a recipient outside the United States is a recipient like any other.
• §10.3 requires a United States entity for a paid plan. Seats and credits are sold to companies in the United States. The person making a purchase represents, for the company, that the company billed is a United States entity; a company owned from outside the United States qualifies through its United States entity, which is the one billed. The rule is applied twice: the billing country the company records in the Services must be the United States before a purchase is opened, and a purchase completed with a billing address outside the United States on the payment page is undone and refunded and grants nothing. A false representation is a breach and a ground for termination for cause, which §16.2 now names. This is a material change: it adds a representation a purchaser gives and a ground on which SynC may act at once. It reaches only companies that buy; nothing about registering an account, the introductory seat, the trial, or reading and responding is conditioned on where you are.
• §20 states the posture in plain language, so that a reader of the acknowledgment gets the same answer as a reader of §2 and §10.3.

Signing in with a Microsoft or Google account (§3.4).

• New §3.4 states what applies when you sign in with a third-party account. The Services now offer sign-in with a Microsoft or Google account. §3.4 states four things: that you are responsible for the security of that account, to which §3.2 applies as it applies to a password; that SynC relies on the provider's confirmation of who you are, and verifies your email address itself where the provider does not vouch for it; that your relationship with the provider is governed by the provider's own terms, to which §4.4 applies; and that SynC may stop offering a provider at any time, in which case your account and content are unaffected and you can set a password using your email address, and that you may add or remove a way to sign in at any time, keeping at least one. This is a material change: it places responsibility for a third-party account's security on the person who uses it to sign in. It applies only to people who choose to sign in this way. What SynC receives from a provider, and how a linked account is removed, are in the Privacy Policy (v1.13), not these Terms.

The service-provider description (§5.3.3).

• §5.3.3 now describes both ways a request reaches a provider. Former text stated that SynC did not contract directly with any inference host and that every host was a supplier of a routing service. Since 2026-09-16, requests from the AI assistant have been sent to the serving provider directly, on SynC's own account; requests for semantic search remain routed. The Section states both paths and what SynC relies on for each. This corrects a description; it does not change the commitment, and a direct contract is the stronger position.

• §5.3.3's pointer to the subprocessor list now reads "the providers we may use". The subprocessor list, as now published, names every provider SynC uses or may use for inference and text-embedding, without stating which of them serves a given request; a request goes only to a provider on it. Former text read "which providers we use". These Terms name no provider, as before; the list carries the names.

• §5.3.3's commitment now reaches the facts about you that a request carries, as the Privacy Policy §4.1A describes them, so that the no-retention-for-their-own-purposes and no-training commitment plainly covers a first name or a role label as well as content.

• §5.3.3's second paragraph no longer says that where a provider processes content is disclosed on the subprocessor list. The list links each provider's own documents, which state that, and does not restate them; the paragraph now says so. The notice commitment in that paragraph is unchanged.

• Terminology. These Terms now say "company" where they said "firm", in §5B.5, §10, §16.2, §16.3 and §20. The word is changed and nothing else: the term still means the organization on whose behalf you use the Services, as §10.1 describes it, and no right, obligation, fee or definition changes with it.

• No other change. Beyond §2, §3.3, §3.4, §5.3.3, §5A.6.3, §5B.3, §5B.4, §5B.5, §9.3, §10.3, §16.2, §16.3 and §20 as described above, no definition, license grant, indemnity, fee term, seat or billing term, arbitration procedure, or opt-out right is added, removed, or modified by v1.12. The retention rules for the notice record and the suspension record, and what SynC keeps of a copyright notice, are in the Privacy Policy (v1.14), not these Terms.

Notice of these changes. The repeat-infringer, copyright-notice, termination, United States entity and third-party sign-in changes are material, and notice is given by the three means Section 18.2 provides, in step with the corresponding Privacy Policy version. Section 18.2 does not prescribe an advance-notice period, and none is taken here; these Terms take effect on their Effective Date, and every change operates prospectively. The service-provider correction is not material and is noticed together with the other changes.

30. Summary of Changes from Version 1.12

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.13 carries Terms of Service v1.12 forward in full. Every section other than those listed below is unchanged. Sections 21 through 29 are retained verbatim as the historical record of what v1.4 through v1.12 changed.

This version makes eight sets of changes, and every one of them is a commitment SynC gives or a limit on a right SynC held, and two rewordings that state a behaviour where former text warranted a mechanism. None narrows a right of yours, and none adds an obligation of yours except the procedure in §15.3, which binds both parties alike. The changes answer the questions a company's counsel asks before signing: what SynC's liability is and what it is not, whether the indemnity runs both ways, how you get your content out, what happens if SynC closes, whether SynC keeps your content confidential and tells you when it is exposed, how much notice you get of a change, what a suspension does to your content, and whether a signed agreement can vary these Terms. Under §18.2 as now written, a change that only adds to your rights may take effect on posting; each change below states whether it is material and whether SynC nonetheless gives the advance notice.

Confidentiality of User Content (§5.6, §20).

• New §5.6 states that SynC holds your User Content in confidence and discloses it only as these Terms and the Privacy Policy allow, names the three channels through which it may be disclosed (the users and recipients you choose, the providers that process it on our behalf, and the law), limits SynC's own access to operating, supporting and securing the Services and answering your requests, and makes the §5.3 limits part of the commitment. It excludes content that is public by its nature. Former text implied confidentiality in §5.3.1 and §5A.7.2 and stated no general obligation. This is a material change in your favour: it creates an obligation of SynC's that did not exist, and one that §14.3 now backs with a higher cap where it is broken by unauthorized disclosure.
• §5.6 names the Privacy Policy's security measures as the means by which SynC keeps the commitment, and applies them to User Content as to personal information. The measures are those the Privacy Policy describes, and §5.6 adds none of its own. The Section says in plain words what it is and is not: a commitment about disclosure, not a warranty of availability, backup or freedom from loss, which §12.1, §13.2 and Section 14 govern. It also states that files you upload are copied each night to a backup on the schedule the Privacy Policy states, that this describes what SynC runs and is not a promise that a copy exists for every file at every moment or that a file can be restored from it, and that you should keep your own copy of any file you cannot afford to lose; the Privacy Policy states the practice in full.
• §5.6 commits SynC to notify your company when a confirmed security incident has exposed its User Content, without undue delay, by email to your company's administrators, stating what was exposed, when, what SynC did and what it recommends. The notice is owed whether or not personal information was affected. Former text gave notice for personal information only (Privacy Policy §6.3). Favourable to you. The Section states no fixed hour count: the notice is owed without undue delay after SynC confirms the exposure.

If SynC discontinues the Services (§12.2, §12.3, §12.4, §16.2, §20).

• New §12.4 states what SynC owes if it discontinues the Services as a whole: at least ninety (90) days' notice by email and in the Services; export throughout that period; a pro-rata refund of subscription fees paid for a period running past the end, and a refund of unused purchased credits at the price paid; and no renewal charge for a period that would run past the end. Where a legal requirement, a court order or a force-majeure event prevents the notice, SynC gives as much as it can and keeps export available as long as it can. An assignment under which the Services continue is not a discontinuation. Former §12.2 allowed discontinuance "with or without notice" and §16.2 said its thirty days did not limit §12.2. §12.2 keeps the right to change or withdraw a feature; §12.3 and §16.2 are conformed to point at §12.4. This is a material change in your favour: it takes a right SynC held and puts a notice period, an export period and a refund on it.

The limitation of liability (§14.1, §14.2, §14.3, §14.4, §20).

• §14.1's exclusion of loss of data no longer reaches loss of confidentiality of User Content through unauthorized disclosure in breach of §5.6. Former text excluded "loss of data or information" outright, which could have been read to bar a claim that your content was disclosed. What the change gives is exactly that: a disclosure claim is not defeated by the loss-of-data exclusion. What it does not give: loss, corruption or unavailability of data, from any cause, stays excluded as it was in v1.12. The change is in your favour and is narrow.
• New §14.3 states the one thing the exclusions and the cap do not reach: a liability that the law does not allow to be limited or excluded. Former §14 said this only through §14.3's (now §14.4's) jurisdictions sentence. No category of fault is named: the Section does not invite an argument about whether conduct was negligent, grossly negligent or intentional, and it concedes no category of injury that §13.3, §5A.5 and the AS-IS terms are written to deny. Conduct the law will not let SynC cap is uncapped by the wording; nothing else is.
• §14.3 sets a higher cap for unauthorized disclosure and for SynC's indemnity. It reaches SynC's breach of §5.6 by which User Content is read by or disclosed to a person not authorized to see it, SynC's use of User Content contrary to §5.3.1, and SynC's indemnity in §15.2, and nothing else. For these, SynC's total liability is two times what your company paid SynC in the preceding 12 months, measured per company and not per seat or user, with no floor: a company that has paid nothing in that period has no remedy under §14.3 and keeps §14.2's cap of the greater of 12 months' fees or $100, unchanged from v1.12. The Section says in terms that loss, corruption or unavailability of content, including an incident that destroys content without disclosing it, stays under §14.1 and §14.2. Each cap is an aggregate across a company's claims, and an amount paid under §14.2 counts against §14.3. This is a material change in your favour for a company that pays: SynC's exposure for a disclosure of its content is doubled and scaled to its fees. It gives a free account nothing beyond v1.12. Former §14.3 (jurisdictions that do not allow an exclusion) is renumbered §14.4, unchanged.

Indemnification (§15, §20).

• §15.1 narrows your indemnity to third-party claims that arise from your content, your distribution, your public distribution of a Standard outside §5A.7, your reliance on Materials or AI-generated content in a construction project, your breach of these Terms or the law, and your contributions under the CLA. Former §15 covered "your use or misuse of the Services" and "any negligent or wrongful conduct by you", which reached a claim of any kind, including one between you and SynC. The indemnity now excludes a claim to the extent it arises from SynC's own breach or from a matter SynC indemnifies. This is a material change in your favour: it removes the two broadest grounds and confines the indemnity to claims by third parties.
• New §15.2 gives SynC's indemnity for a claim that the Services' software infringes a United States patent, copyright or trademark or misappropriates a trade secret. It excludes User Content, SynC Standards content, AI-generated content, third-party services, use in breach of these Terms, combinations SynC did not provide, and continued use after SynC has offered a replacement. SynC may procure the right, modify or replace the affected part, or withdraw it with a pro-rata refund. It is owed to a company that has paid SynC in the preceding 12 months, is your sole remedy for such a claim, and is subject to the §14.3 cap, which is measured by that amount; a company that has paid nothing has no claim under it. Former text gave no indemnity by SynC. This is a material change in your favour for a company that pays.
• New §15.3 states the procedure for both indemnities: prompt notice, control of the defense by the indemnifying party, cooperation at its expense, no settlement admitting the other party's fault or imposing an obligation on it without consent, and survival. This is the one new obligation of yours in this version, and it binds SynC identically.

Getting your content out (§16.2, §16.3, §16.4, §20).

• §16.4 is rewritten as an export commitment and states what the Services export today. Former §16.4 said only that you could request export within 30 days of termination by contacting support. The Section now lists what you export yourself, in the browser and without asking SynC: a project revision as a PDF package with datasheet values, as a Markdown zip, and as datasheet JSON, each for the revision you are viewing, so every published revision can be exported one at a time; a standard or a whole library as PDF or Markdown; comments as PDF or Word; and the coordination checklist as CSV. It states what the Services do not export as a file (project history as one record, access records, hold acknowledgments, account activity; conversations are copied out as text under §4.2.1), that those records can be read in the Services where your role allows it, and that these Terms promise no copy of them beyond what the Services let you see and export yourself. It states that no export is charged for, that SynC promises no format it does not name and gives notice under §18.2 before withdrawing one without a replacement, and that for thirty days after termination on any ground the exports remain available on request, except where a security or legal ground prevents it. This is a material change in your favour: the self-serve exports existed and were promised nowhere, and the no-charge statement is a new commitment.
• §16.2 states what a suspension does to your content. A suspension deletes nothing; export through the Services pauses with it; and on request SynC provides the §16.4 exports during the suspension unless a security or legal ground prevents it, in which case SynC says so. Former text was silent. Favourable to you.
• §16.3's deletion bullet now points at §16.4 and the Privacy Policy instead of "a reasonable retention period", so that the two documents state one rule. It remains permissive: SynC may delete after the export period, and the Privacy Policy states what is retained after that. No purge process is described because none is run.

Negotiated terms and changes to these Terms (§18.1, §18.2, §20).

• §18.1 states that a signed Order or written agreement may vary these Terms for the company that signed it, including Section 14, Section 15 and §16.4, to the extent it identifies the provision and states the variation, and that a purchase order's printed terms have no effect. Former §18.1 was an entire-agreement clause with no precedence rule, and §10.1 made an Order govern fees only. Favourable to a company that negotiates; it changes nothing for one that does not.
• §18.2 gives thirty (30) days' advance notice of a material change, with three exceptions that may take effect on posting: a change the law requires, a change confined to a new feature or a Beta Feature, and a change that only adds to your rights. It preserves the notice periods §5.3.3 and §10.7 state, points at §16.4 for a person who leaves rather than accept a change, and provides that a change does not reach a Dispute already noticed under §17.2. Former §18.2 gave notice by three means and no period. This is a material change in your favour. Because §10.2 gives notice of an allowance's withdrawal "under Section 18.2", a withdrawal is now on thirty days' notice as well.

The acknowledgment (§20).

• §20 gains five bullets so that a reader of the acknowledgment gets the same answers as a reader of §5.6, §12.4, §14, §15, §16.4, §18.1 and §18.2.

Two statements of behaviour in place of warranties of mechanism (§5A.6.1, §7.2). Two sentences carried forward from earlier versions described how the Services are built rather than what they do. Each is reworded to state the behaviour, which is unchanged.

• §5A.6.1 states that the Services preserve a project's fixed references to adopted revisions, subject to §5A.6.3. Former text said the platform "commits to preserving those references as a load-bearing feature of the Services" and that the commitment was subject to §5A.6.3. What a project imports, how a hold or a revocation reaches it, and the carve-out in §5A.6.3 are as they were; the sentence no longer describes the feature's place in the design. Not a material change: no right of yours and no behaviour of the Services is altered.
• §7.2 states that the Services enforce the isolation of Internal comments and that other companies on the project cannot see, search or access them. Former text added that the isolation "is enforced at the data layer and cannot be overridden by other project participants", which described the implementation. The isolation is as it was; the sentence describes what you get rather than how it is built. Not a material change.

A notice promise narrowed to the notice the Services send (§10.6). Former §10.6 said that where the date of a lapse is known in advance, the Services give notice before it. The Services send that notice before a company's trial ends. They did not send it before a subscription set to cancel at the end of its period ends, before a scheduled decrease in seats takes effect, before a person's own trial ends, or before an allowance is withdrawn. The sentence now promises the notice that is sent: before your company's trial ends, the Services give notice of the date. A cancellation or decrease you schedule is still shown with its date on your company's billing page. This is a material change: it withdraws a promise of notice that a reader of v1.12 held.

• No other change. Beyond §5.6, §5A.6.1, §7.2, §10.6, §12.2, §12.3, §12.4, §14.1, §14.2, §14.3, §14.4, §15, §16.2, §16.3, §16.4, §18.1, §18.2 and §20 as described above, no definition, license grant, fee term, seat or billing term, arbitration procedure, or opt-out right is added, removed, or modified by v1.13. The AI and content terms in §4.2 and §5.1 to §5.5 are untouched, and §5A is touched only by the §5A.6.1 rewording above. The Privacy Policy (v1.15) states the disclosure side of §5.6 and tightens what aggregated statistics SynC shares; these Terms do not restate it.

Notice of these changes. The confidentiality, discontinuance, liability, indemnity, export and advance-notice changes are material. Each adds to your rights or reduces SynC's. These Terms take effect on posting: version 1.12, under which this version is published, sets no notice period, and SynC gives notice by the three means §18.2 provides, in step with the corresponding Privacy Policy version. The thirty days §18.2 now prescribes apply to every change after this version. The procedure in §15.3 binds both parties and is noticed with the rest. The narrowing of §10.6 is material and takes effect with the rest. The §5A.6.1 and §7.2 rewordings are not material and are noticed together with the other changes.

31. Summary of Changes from Version 1.13

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.14 carries Terms of Service v1.13 forward in full. Every section other than those listed below is unchanged. Sections 21 through 30 are retained verbatim as the historical record of what v1.4 through v1.13 changed.

This version states correctly what a seat is for and what a lapse does, after a change to how roles and seats work in a company. A person's role in a company and their seat are now separate: the role says what the person may administer, and the seat says whether they may author. Two passages of v1.13 described the earlier arrangement.

Work on a company's libraries requires a seat (§10.1, §10.6, §20).

• §10.1 states that building and maintaining a company's libraries of standards, including their categories and errata, requires a seat, and the description of a full seat says it lets its holder work on the company's libraries. Former §10.1 named starting projects and authoring within a company's projects and did not mention libraries. Collaborator seats are unchanged: they reach another company's projects and nothing else.
• §10.6 lists the library work a person loses when a seat lapses: creating or changing the company's libraries, standards and categories, and issuing or withdrawing errata. Former §10.6 listed project authoring only. What the person keeps is unchanged.
• This is a material change: it names work that a person without a seat cannot do. Under §18.2 it takes effect for an account that accepted an earlier version thirty days after this version is posted, and at once for an account that accepts this version.

A lapse does not change a person's role in the company (§10.6, §20).

• §10.6 states that a lapse does not change a person's role in the company, so a person who administered the company before a lapse administers it after. Former §10.6 said a person whose seat lapsed is restored to their prior role when the company seats them again, which no longer describes a company role: the role is not changed by the lapse, so there is nothing to restore. §10.6 states the one case in which a role does change. Where a seat funded a person's role on a project, that role becomes read-and-comment access when the seat lapses and is restored when the company gives the person a seat again, as before. Not a material change: it keeps a role that the former text treated as lost, and narrows nothing.

• §20's lapse bullet now says that the person keeps their role in the company and that the authoring they lose includes the company's libraries.

• No other change. Beyond §10.1, §10.6 and §20 as described above, no definition, license grant, fee, billing term, arbitration procedure, or opt-out right is added, removed, or modified by v1.14. Seat and credit prices are unchanged.

Notice of these changes. SynC posts this version with a new Effective Date and displays it in the Services for acceptance. The library seat requirement is material and takes effect as stated above. The §10.6 statement about roles is not material and takes effect on posting.

32. Summary of Changes from Version 1.14

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.15 carries Terms of Service v1.14 forward in full. Every section other than §10.5 is unchanged. Sections 21 through 31 are retained verbatim as the historical record of what v1.4 through v1.14 changed.

What an exchange with the assistant costs (§10.5).

• §10.5 states that the credits an exchange costs depend on the length of the conversation as well as on the work the exchange involves, and that the same request can cost more late in a long conversation than at the start of a new one. Former §10.5 named the work alone. How credits are counted, shown with each answer, and drawn is unchanged.
• No other change. Beyond §10.5 as described above, no definition, license grant, fee, billing term, arbitration procedure, or opt-out right is added, removed, or modified by v1.15. Seat and credit prices are unchanged.

Notice of this change. The change describes how the cost of an exchange already varies and adds no fee, charge, or obligation. It is not a material change and takes effect on posting. SynC posts this version with a new Effective Date and displays it in the Services for acceptance.

33. Summary of Changes from Version 1.15

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.16 carries Terms of Service v1.15 forward in full. Every section other than those listed below is unchanged. Sections 21 through 32 are retained verbatim as the historical record of what v1.4 through v1.15 changed.

This version makes two sets of changes. The first states the rule for your name on a company's records (§16.2, §16.3, §20). The second adds one obligation on users and one permission for SynC (§9.2A, §5.3.1), and conforms eight passages to the body of §5.3.1 (§5.3's opening, its heading, §5.6, §5A.7.2, §8.4, §8.5, §9.2 and §20). No fee, liability cap, indemnity, arbitration procedure or dispute-resolution provision is touched. The first three paragraphs of §5.3.1, which forbid training generative, general-purpose and foundation models on User Content, anonymized or not, are unchanged word for word.

Your name on a company's records (§16.2, §16.3, §20).

• §16.2 states that your work in a company's projects and libraries is recorded under your name as part of that company's records, and that a record keeps the name you had when you made it. Changing your name afterwards does not change the record, and neither does the termination or deletion of your account. Former text said that a company's projects remain with the company when a person's account is terminated, and said nothing about the name on the company's records. The paragraph states it where every user accepts these Terms, at sign-up and on re-acceptance, because a rule that outlasts the account has to be agreed to before the work is done.
• The same paragraph names the only ways a record comes to show a name differently from how it was recorded, each of them an act that is recorded and shown on the record with its reason and date. The company that holds a record may instruct SynC to withhold your name from its records. SynC may withhold a name, or mark it as disputed while it looks into a report, on four grounds, which are stated in full: impersonation, an abusive name, a person's safety, and an identity SynC could not confirm; and SynC withholds a name where the law requires it. You may choose to show your current name on your own earlier records, and you cannot withhold your own name. Former text gave SynC no stated power over a name on a record. The grounds are a closed list, and the paragraph does not reach attribution in the SynC Standards library, which the Contributor License Agreement governs (§5A.4). What is kept, for how long, and what you can ask for are in the Privacy Policy (v1.18, carried forward in v1.19), which these Terms do not restate.
• §16.3 and §20 each gain one bullet pointing at §16.2, so that a person closing their account, and a reader of the acknowledgment, get the same answer as a reader of §16.2.

Your content and models (§5.3.1, §5.6, §5A.7.2, §8.4, §8.5, §9.2, §9.2A, §20).

• New §9.2A (Content Is Not to Be Extracted for Model Training). You may not use the Services to extract, collect or compile content in order to train, fine-tune or evaluate a model, however you reach the Services, including by API key, integration, share link, export or automated means. The Section states what it does not reach: your own User Content, which you may export under §16.4 and use as you choose; the SynC Standards license, to which it adds no condition, so that anyone holding a copy of a SynC Standard may use it as CC-BY-SA 4.0 allows; and the use of a tool, including an AI tool, to read, search, summarize or check content you are entitled to read. It restricts the use of the Services as the means of bulk or automated collection, reaches integration and API-key holders acting for customers, and makes collecting information about other users for those purposes a breach. §9.2 gains a pointer bullet and §8.4's scraper bullet is conformed. A breach is cause under §16.2.
• §5.3.1, new paragraph "Improving the Services". SynC may use what you upload, and what the Services produce from it, to evaluate and improve the Services: to find out why a result was wrong and put it right, to make the Services read documents and answer questions better, and to measure how well they do. The paragraph states its limits in the Section's own terms: your content remains confidential under §5.6; SynC does not sell or license it; SynC does not use it to train, fine-tune or improve any generative, general-purpose or foundation model; nothing built from it reproduces, or discloses the substance of, your content to anyone not already permitted to see it; service providers process it only on SynC's behalf under §5.3.3; improving how the Services use a model is improving the Services, not the model; and a model built from it is used only within the Services and is not sold or licensed. A project's administrator can opt the project out, in the project's settings or, until that setting exists, by asking SynC; a company administrator can set the default for the company's new projects. On an opt-out SynC stops using that project's content this way and deletes the copies it kept for the purpose; the paragraph says plainly that what was learned before the opt-out stays learned.
• §5.3's opening conformed. It said the Section is "a limit on our rights, not a grant". It now says the Section is a limit on SynC's rights and grants only the uses it names, because §5.3.1 names a permitted use.
• §5.3.1 heading, §5.6, §5A.7.2, §8.5 and §20 conformed. The heading no longer promises that content is not used as "research material", which the body did not say; it states that SynC does not train generative or foundation models on your content and may use it to improve the Services. §5.6 lets staff access User Content to improve the Services as §5.3.1 states, and for nothing more than before. §5A.7.2 points at §5.3.1 for how a project specification may be used and how a project is opted out. §8.5 says "to train a generative or foundation model" where it said "as training or research material". §20 restates the new paragraph and §9.2A in plain language.
• No other change. Beyond the Sections described above, no definition, license grant, disclaimer, limitation of liability, indemnity, fee term, termination right, sharing or distribution provision, wiki errata or revocation provision, arbitration procedure, class-action waiver, or opt-out right is added, removed, or modified by v1.16. Seat and credit prices are unchanged.

Notice of these changes. This version takes effect on posting, in step with Privacy Policy v1.19. SynC posts this version with a new Effective Date and displays it in the Services for acceptance.

34. Summary of Changes from Version 1.16

This summary is provided for convenience and is not a substitute for the operative text above. Version 1.17 carries Terms of Service v1.16 forward in full. Every section other than those listed below is unchanged. Sections 21 through 33 are retained verbatim as the historical record of what v1.4 through v1.16 changed.

This version makes one set of changes. It states what an API key is, what an app or tool connected with one may do, and what you and SynC each owe in respect of them (new Section 4A), and conforms §3.2, §4.4, §5.3.3, §5.6, §6.1, §6.2, §6.4, §8.4, §9.2, §9.2A, §13.2, §14.1, §15.1 and §20 to it. No fee, seat or credit term, liability cap, arbitration procedure or dispute-resolution provision is touched. §9.2A, which forbids collecting content through the Services to train or evaluate a model however you reach them, is unchanged in substance and gains one clause and one pointer sentence. §5.3.1, which forbids SynC from training generative or foundation models on your content, is unchanged word for word.

• New Section 4A (API Keys and Connected Apps). The Services let an AI app or any other tool reach your account with an API key, at the API and at an address published for AI apps. The Section states that a key, and everything an app does with it, acts as you and that §3.2 applies to what it does, including an action an app takes because content it read told it to; that a key is a credential you keep secret, revoke or rotate on exposure, and replace by rotating; that a key can never do more than you can at the moment of the request, that changing things through one needs a seat as it does in the browser, that some actions are never available through a key and some only when you tick them by name when you create it; what you may not do with a key beyond what §9 already forbids (resell access; use several keys, apps, accounts or companies to get around a limit, a permission or a setting; probe for unavailable actions; harvest beyond the limits the Services state), adding no condition to the CC-BY-SA 4.0 license; that limits are yours across all of your keys, follow your seat, may change, and are raised only by a written agreement under §18.1; that content an app reads leaves the Services under the app provider's terms, is a disclosure you authorized for §5.6 and §14.3, and carries your obligations to others with it; what a company's administrators can see and switch off; that SynC may revoke a key and change the API, and promises no availability for either; and that §13, §14 and §15 apply. Section 4A applies to keys that already exist as it applies to new ones.
• §5.3.3, §5.6 and §20 say where SynC's commitments about its own AI providers stop. v1.16 said that content reaches inference and embedding providers barred from retaining or training on it. That remains true of the providers SynC uses. An app or tool that you, or a recipient you share with, connect to a SynC account with a key is not one of those providers: SynC has no agreement with it, and SynC does not control what it keeps or trains on. §5.3.3 now says so, §5.6 names a connected app, acting for a user or a recipient within the access they hold, as a channel through which SynC discloses content at that person's direction and keeps a read by such an app within the access the sharer granted, and §20's bullet says the same in plain language. This is a material change: a reader of v1.16 could have taken those sentences to reach every AI that touches their content, and they do not.
• §6.1, §6.2 and §6.4 state that the share link's export choice also decides whether a recipient's connected app may read the shared project. One control, two effects; the Terms say both where the sharer reads what the control does. §6.1 also states that an administrator of the company whose project it is may switch off access by keys and apps to all of the company's projects, without changing a recipient's access or ability to export. §6.2 tells a recipient that an app they connect reads a shared project only where the sharer allows export and only within the access they hold, that they answer for the app and for what its provider does with what it reads, and that connecting an app enlarges nothing. §6.4 makes the sharer's export choice, and the right to let recipients take content out of the Services in those ways, an express sharer responsibility.
• §3.2, §4.4, §8.4, §9.2, §9.2A, §13.2, §14.1, §15.1 and §20 gain a bullet, a sentence or a phrase pointing at Section 4A, so that credentials, third-party services, automated access, the warranty disclaimer, the exclusion of damages, your indemnity and the acknowledgment each say what Section 4A says.
• No other change. Beyond the Sections described above, no definition, license grant, fee term, seat or billing term, arbitration procedure, class-action waiver, or opt-out right is added, removed, or modified by v1.17. Seat and credit prices are unchanged. What is recorded about keys and the requests made with them, for how long, and what a company's administrators can see, is in the Privacy Policy (v1.23), not these Terms.

Notice of these changes. This version takes effect on posting, in step with Privacy Policy v1.23. SynC posts this version with a new Effective Date and displays it in the Services for acceptance.

---

Last Updated: October 14, 2026 Version: 1.17

For questions about these Terms, please contact legal@synergyinconstruction.com.