Skip to main content

Legal

Listing Accuracy Policy

Version 1.0Last updated 22 September 2026

Draft, pending legal review. This document is a pre-launch template draft and is not yet in force. The counsel-approved version becomes version 1.0 and takes effect at launch.

AEC Integrations catalogues software products, vendors, and the integrations between them so that architecture, engineering, and construction teams can find and compare them. This policy explains where listing data comes from, who maintains an integration, how to ask for a correction, and the limits of what we will change. It works together with our Terms of Service.

Where listing data comes from

Listings are compiled from publicly available information, including vendor websites, public product and API documentation, public integration directories and marketplaces, and similar sources, together with information contributed by the community and, where applicable, confirmed by vendors. We curate this into an AEC-native taxonomy and keep it as current as we reasonably can.

A listing is a factual catalogue entry, not an advertisement. We do not sell listings or ranking position, and inclusion does not imply any relationship with, or endorsement by, the vendor.

Who maintains an integration

An integration belongs to the vendor that offers it, which the listing names on its "Offered by" line. We record integrations from public sources to start the catalogue. The vendor named as the owner may then claim the integration through its vendor account. Once it does, the owner maintains the integration's details, its edits are published without review by us, and our own catalogue updates no longer change that integration. A vendor may also add an integration of its own, which it maintains from the start. Integrations delivered through a third-party connector product are not yet open to any of this and stay as we recorded them.

An owner may retire an integration it has claimed. A retired integration is taken off the public site but is not deleted, and the owner may restore it. We may also retire an integration a vendor maintains, where this policy lets us remove a listing: to correct an error, or to enforce our terms. Only we may restore an integration we retired.

We aim for accuracy, but we don't guarantee it

We work to keep listings accurate and up to date, but public sources change and may themselves be incomplete or wrong. We do not warrant that any listing is complete, current, or error-free, and listings may lag behind a product's actual state. If something looks wrong, please tell us.

Requesting a correction

Anyone, including a vendor, can ask us to correct a factual error in a listing. Email founders@thewbsproject.com (or use the correction option in the service) and include:

  • a link to the listing;
  • what specifically is inaccurate; and
  • the corrected information, with a public source we can verify where possible.

We review every request, verify it against public sources, and update the listing where the correction is supported. We aim to respond promptly. We may decline or defer a request we cannot verify, and we decide at our discretion how a correction is reflected.

For an integration its owner has claimed, the owner maintains the details, so we take a supported correction up with the owner rather than change the integration through our catalogue updates.

Contesting an integration detail

A vendor whose product is at one end of an integration, and which does not own that integration, has a second route: a contest, sent from its vendor account. A contest names one detail of the integration, the value the vendor believes is correct, and the reason.

Who decides a contest:

  • if the owner has claimed the integration, the owner decides;
  • if the integration has not been claimed, we decide; and
  • a contest about who owns the integration always comes to us, even after a claim.

A contest is decided by whoever was deciding when it was sent, even if the integration is claimed later. While a contest is open, the listing continues to show the value on record and does not indicate that a contest exists.

A contest ends in one of three ways:

  • Accepted. The proposed value replaces the value on record. Where we accept a contest on an integration nobody has claimed, the change is generally published with our next catalogue update.
  • Declined. The decider does not agree with the proposed value. The value on record stays, the contest is closed, and the vendor that sent it is told, together with any note the decider added. Where the owner declined it, the vendor may ask us to review the decision, as described below.
  • Withdrawn. The vendor that sent a contest may withdraw it while it is open. An open contest is also closed as withdrawn if the owner or we retire the integration, and restoring the integration does not reopen it.

Asking us to review an owner's decision

Where the owner declined a contest, the vendor that sent it may ask us to review that decision within 30 days of the decline. Where the owner has not answered a contest for 30 days, we treat it as declined, and the vendor may ask us to review it within the following 30 days. The request gives the vendor's reasons and may include up to three links. The owner may reply once, within 14 days. We may give our view before the owner replies or after that time has passed.

We then say which side we agree with, and give our reasons to both vendors. Our view is advice. We do not change the integration, because the owner maintains its details. The value on record stays unless the owner changes it. Where we agree with the owner, the vendor that asked may not contest the same detail of that integration again for 90 days, unless the value on record changes in the meantime. The vendor that asked may withdraw its request while we are considering it, and it may not ask again about the same contest.

We do not publish anything about a review: not that one was asked for, and not our view.

A contest is separate from a correction request. Anyone may still ask us for a correction under the section above.

What we will and will not change

We will:

  • correct factual errors: for example a wrong vendor name, miscategorised product, broken or outdated capability, or an integration listed in error; and
  • remove listings for defunct companies or discontinued products: where a vendor or product no longer exists or is no longer offered.

We will not:

  • remove an accurate listing simply because a vendor asks us to. AEC Integrations is an independent directory built from public information; a vendor's preference not to be listed is not, on its own, a reason to remove an accurate entry. We remove a listing only to correct an error, reflect that a company or product is defunct, comply with a legal obligation, or enforce our terms.

This independence is deliberate: it is what lets the directory stay useful and trustworthy rather than reflecting only what vendors want shown.

Reviews are separate

This policy covers the accuracy of catalogue listings. Concerns about a review, for example that it is fake, defamatory, or names an individual, are handled under our Review Guidelines, not here.

Changes to this policy

We may update this policy from time to time. The current version and its effective date are shown at the top of this page, and the full change history is the public commit log of this repository.

Contact

Corrections and questions: founders@thewbsproject.com.