Security and data handling for real workflows
RuleFoundry is built for teams that need review, traceability, and controlled handling. This page covers what we can state publicly today and how to start a security review.
What we can say clearly before a sales call
The point is not to inflate the posture. It is to make the trust model clear enough for teams deciding whether to evaluate the product.
No model training on customer data
Customer workflow data is not used to train models.
Source-linked outputs
Rules, gaps, and follow-up questions stay tied to what the expert actually said.
Human review before build
RuleFoundry is built around review before implementation, not blind handoff.
Raise constraints early
If a workflow is sensitive, start with the security conversation before a broader pilot begins.
What larger teams usually want to clarify first
If you need a security review before trying the product, start there. The goal is to make the evaluation path explicit before the workflow gets broader.
- NDA or procurement questions before a pilot
- Data-handling expectations for the workflows you want to test
- Whether a narrower initial scope makes more sense than a broad rollout
- Retention, identity, audit, or support requirements for larger teams
For larger teams, the enterprise path can include identity, retention, audit, and support requirements alongside the evaluation plan.
What this page covers
This page covers the public security and evaluation posture for RuleFoundry. The website privacy policy covers the marketing site and contact inquiries separately.
Need a security review or NDA conversation first?
Start there. If the path looks straightforward, the best next step is still to try one real workflow.