Your pricing and margins stay confidential
Catalog, pricing and configuration data are handled as confidential or restricted business information. They're used to run your service and for nothing else.
For manufacturers, distributors and the IT and security teams who review software for them. In plain terms: what happens to the data you load, who can see it, where it runs, and how we protect it.
Last updated October 2026. Where this page and your agreement differ, your agreement governs.
Your catalog, your pricing and your customer relationships are the business. Here's what we commit to, in the order buyers usually ask.
Catalog, pricing and configuration data are handled as confidential or restricted business information. They're used to run your service and for nothing else.
Each customer's environment is isolated. We never combine customers' data in a way that could expose one customer's information to another.
A distributor owns its own customer and configuration records. In a manufacturer-sponsored program, the manufacturer never sees a distributor's individual customers.
We don't use your data to train AI models or fine-tune them, and we don't share it with third parties for marketing, analytics or training.
No connection to your systems by default. A proof of concept can run on exported files. Any integration is scoped and approved by you first, and can be revoked at any time.
Source files are deleted after processing unless your scope needs them. Trial data never becomes production data unless you approve it, and deletion requests are handled under your Data Processing Agreement.
Distributors are protective of their customers, and manufacturers want demand insight. Access is designed so both can be true at once.
Intelli.Build is hosted on Amazon Web Services and fully managed by us. Your production data stays inside that AWS environment. We keep no on-premises copy and use no other hosting provider for it. When AI features are used, the relevant inputs go to the model providers named in your agreement.
Signs in with a named account
Managed load balancing. Encrypted connections end here.
Platform services, PostgreSQL and file storage. Not reachable from the internet.
Continuous copies of the database and selected file storage.
Nothing links to your ERP, network or email unless you request it and approve it. Trial work can use exported files.
Data is processed only for the purpose you agreed: catalog preparation, configuration rules, quoting, validation, reporting or integration. Any new purpose is added to your agreement before processing starts.
The assistants answer from your data and act only within the access the person using them already has.
For engineers and security reviewers. A fuller technical description is available under NDA.
This page is the summary. In a security review, you get the documents behind it, and we answer your questionnaire as things actually stand.
The hosting model, trust boundaries and operating controls in full. Shared under NDA.
Master Services Agreement, Data Processing Agreement and Statement of Work. They're authoritative wherever they cover the same ground as this page.
Completed in full. Any partial answer says exactly what is and isn't in place.
An architecture and data-flow walkthrough with your security team, at any stage.
On certifications: Intelli.Build doesn't hold SOC 2 or ISO 27001 certification today. In your review, we'll share where our compliance program stands and when each item is due.
No. Each customer's environment is isolated, and no customer, partner or reseller can see into another's catalogs, pricing, quotes or customers.
No. Where your agreement provides for it, a sponsoring manufacturer sees aggregated, non-personal analytics, such as which products and assemblies are being configured. Never your individual customers.
No. We don't train or fine-tune models on customer data, and our model providers' API terms exclude inputs from training.
You own your customer and configuration records. Ownership and access terms are written into your agreement.
No. There's no connection by default, and a trial can run on exported files. Any integration is scoped, approved and documented first, with credentials limited to that purpose.
On Amazon Web Services, managed by us, with daily backups, point-in-time recovery and copies in a second AWS region.
Temporary source, drawing and geometry files are deleted after processing. Trial data doesn't become production data unless you approve it, and you can request deletion under your Data Processing Agreement.
If a confirmed incident affects your data, you're notified within the timeframe in your agreement: what was affected, the known cause, what was done and what's planned.
Tell us what you need. We'll answer your questionnaire in full, share our technical documentation under NDA, and put our technical lead in front of your security team.
We reply within one business day.
We use your details only to arrange your review.