Every business gets an isolated instance. Your data does not train shared models. Your knowledge base is not accessible to other clients or to Fulcrum after the engagement ends. We can walk through the technical architecture and data handling specifics in the first conversation.
Your Vantage deployment runs on a fully isolated Supabase project dedicated to your organization—your data is never stored in a shared database or used to train any shared models. No other client and no future AI model ever sees your content.
During the engagement, Fulcrum uses a service account credential to your Supabase project solely to build, maintain, and optimize your system. When the engagement ends, that credential is revoked. You receive your own project credentials, complete schema documentation, and full ownership and control of the database.
We only connect to data sources you explicitly authorize. Typical integrations include CRM records, meeting transcripts, call logs, internal documents, and strategy notes. We do not access financial accounts, personal employee data, or any systems outside the agreed integration scope. The integration list is defined at the start of the engagement and is only changed with your explicit approval.
Your Vantage system is a permanent asset, not a rental and not dependent on Fulcrum’s ongoing operations. If the engagement ended today, your Vantage instance would continue running independently on your own infrastructure and credentials.
Related: Is Vantage HIPAA compliant · What happens to your data if you cancel · What happens when engagement ends
Vantage data security and architecture summary
- Dedicated infrastructure: Each Vantage deployment runs on its own Supabase project, isolated from other clients at the database and infrastructure level. No shared databases or shared knowledge bases.
- Structural isolation: Data isolation is enforced by architecture, not just by policy. Your content never contributes to any shared or global model.