This page explains what VanguardOps collects, how it’s stored, and what your rights are. We aim for clarity, not legalese.
Last updated: May 27, 2026.
When you create an account: your name, email, company name, Salesforce role, and the pain point you described on the beta signup form. This information is stored in our database and used to provide you access to VanguardOps and to communicate with you about the product.
When you connect a Salesforce org: an OAuth refresh token scoped to metadata APIs only. The token is encrypted at rest using Fernet symmetric encryption. We never see your Salesforce password.
When you run a scan: Salesforce metadata only — object schemas, field definitions, permission sets, automation logic, integration configuration. We never collect or store customer records, contacts, opportunities, files, emails, or any record-level data from your Salesforce org. See our Security page for the architectural enforcement of this.
When you use the product: standard application logs (IP address, browser, timestamps, actions taken). We use these for debugging, abuse prevention, and security monitoring.
We do not sell, rent, or trade your information with third parties.
VanguardOps relies on a small set of trusted infrastructure partners:
Each subprocessor handles a specific function and only the data necessary for that function.
You can:
VanguardOps infrastructure is hosted in the United States (Railway US East region). If you access VanguardOps from outside the U.S., your information will be processed and stored in the U.S.
For users in jurisdictions with specific data protection laws (GDPR, CCPA, etc.), we honor data subject rights including access, correction, deletion, and portability. Email chris@vanguardops.ai with requests.
We will update this page when the policy changes. Material changes will be communicated by email and posted at the top of this page.
Email chris@vanguardops.ai.
Last updated: May 27, 2026.