We use cutting-edge AI.
Your data is not used to train it.
At FoundryOps, you should not have to choose between useful AI and clear boundaries. We built our platform to deliver both.
Our privacy architecture
Enterprise AI, no customer training
We use Google Vertex AI within our GCP project under enterprise data protection terms. Customer data is not used to train models for us or for Google.
We also mask selected PII before AI processing where appropriate.
Your data is not our product
We make money by solving data quality and workflow problems, not by reselling customer information.
- We do not resell customer data.
- We do not train models on customer records.
- We do not use one customer's CRM data to improve another customer's results.
- We do not create hidden data co-ops from your records.
Practical security controls
- TLS encryption in transit
- Role-based access with authenticated product access
- Isolated customer workspaces
- Privacy-conscious data handling across product workflows
How we use AI
What our AI does
- Uses Google Vertex AI under enterprise data protection terms
- Processes in isolated workspaces per customer
- Runs in inference-only mode rather than training on your records
- Masks selected PII before AI processing where appropriate
What our AI does not do
- Route production customer data through public consumer AI tools for convenience
- Train on one customer's data to benefit another customer
- Turn your records into a shared learning pool for competitors
- Use your data to train third-party models
Built on open data, not your data
Our matching intelligence comes from the Foundry Graph - a knowledge base built from public sources like Wikidata, SEC EDGAR, and Companies House. Not from harvesting your customer records.
Accuracy improves from better algorithms and better open data - not from learning on your customer records.
Your competitor should never benefit from your CRM data.
Frequently asked questions
If you use AI, how can you still claim privacy?
We use Google Vertex AI under enterprise data protection terms, we do not train on customer records, and we mask selected PII before AI processing where appropriate. Customer workspaces are also isolated.
Do you use customer data to improve matching quality?
No. Matching improves through better algorithms and our Foundry Graph built from public registries and open data sources, not by learning from customer data.
Can employees see our data?
Access is restricted to explicit support or operational needs under role-based controls, with customer workspaces isolated and production access handled carefully.
What happens when we ask for deletion?
You can request export or deletion of primary customer data. Limited operational, security, billing, and audit records may still be retained as needed to run the service, investigate abuse, comply with law, or resolve disputes.
We want the privacy position to be understandable at a glance.
If you need the structured version for procurement, questionnaires, or a buyer security review, use the Trust and Security page.
Your trust should come from clear boundaries, not vague promises.