Security & Trust
See how Vendo manages data access, storage, credentials, and activity.
Vendo connects systems that contain important business and customer data. You can expect clear data boundaries, protected credentials, controlled access, and practical safeguards throughout your data workflows.
Choose Vendo-managed infrastructure, bring your own data warehouse, or work with us on a custom private-cloud deployment.
Deployment options
Choose how Vendo runs
Vendo can adapt to your organization's infrastructure, security, and data-governance requirements. The right option depends on your cloud environment, integrations, and operating model.
Vendo-managed infrastructure
Vendo manages the warehouse and supporting cloud infrastructure required to operate your data workflows. This is the simplest option for teams that want Vendo to manage the underlying environment.
Bring your own data warehouse
Connect Vendo to a supported warehouse controlled by your organization. Your warehouse remains your primary data environment while Vendo operates approved workflows using the access and permissions you provide.
Custom private-cloud deployment
Enterprise customers can work with Vendo on a dedicated deployment within an agreed private-cloud environment. Architecture, networking, data access, operating responsibilities, and support are defined before implementation.
Tenant isolation
Your workspace stays your workspace
Vendo keeps application data, warehouse paths, and service access tied to the relevant customer account.
Account-scoped access
Users must be authenticated and belong to the appropriate Vendo workspace before they can access its account-scoped data and configuration.
Separated warehouse environments
Vendo-managed BigQuery workflows use account-specific dataset boundaries so each customer’s warehouse data path remains tied to its configuration.
Authorized service access
Background services and administrative tools access customer data through authorized server-side processes tied to the relevant customer account.
Encryption & credentials
Your data and credentials are protected
Vendo applies safeguards according to whether it is handling customer data, credentials for a connected platform, or a Vendo API key.
Encryption in transit
Traffic between your browser, Vendo, and supported platform APIs is protected using HTTPS and encrypted connections.
Connected-platform credentials
Credentials for connected sources and destinations are encrypted before storage and decrypted only by authorized server-side processes when needed to run a configured workflow.
Vendo API keys
Vendo-issued API keys are stored as cryptographic hashes rather than readable plaintext. They are account-bound and can be scoped, expired, rate-limited, or revoked.
User access
Access follows your team
Access begins with an authenticated identity and the relevant customer workspace. Additional enterprise identity requirements can be reviewed as part of your implementation scope.
Workspace roles
Workspace access currently uses Owner and Member roles. We help you understand how those roles apply to your team during setup.
Multi-factor authentication
Users can enable multi-factor authentication for additional protection. Privileged Vendo administrative access requires an MFA-verified session.
Separate programmatic access
API access uses account-bound credentials instead of shared user passwords, making programmatic access easier to control and revoke independently.
Operational visibility
Understand what happened in your workflows
Available operational information helps your team inspect workflow health and gives Vendo the context needed to support investigation and recovery.
Job status and history
Available workflow records can show status, timing, record counts, warnings, errors, and the most recent successful run.
Activity records
Supported product and workflow activities may be visible within Vendo. Coverage depends on the resource and workflow and is not presented as a complete immutable audit archive.
Operational support
When a workflow does not run as expected, Vendo uses available records and service information to investigate the issue and support recovery.
Privacy
Privacy starts with clear responsibility
You control what customer data enters Vendo and why it is used. We make Vendo's role and handling responsibilities clear before implementation.
You decide what connects
Your organization decides which systems and data are connected to Vendo and the purposes for which that data may be used.
Clear responsibilities
Vendo generally acts as a processor or service provider for customer data handled on your instructions and as a controller for its own account, billing, security, sales, and support information.
Purpose-based data handling
We work with you to identify the systems and fields required for the intended workflow. Vendo does not sell personal information.
Policies & response
Know what to expect if something goes wrong
Vendo follows a structured process to assess, contain, remediate, and recover from security incidents. Customer communication follows applicable law and contractual commitments.
Incident response
Read how Vendo identifies, assesses, contains, recovers from, and communicates about security incidents.
Read the incident response planPrivacy policy
Review the information Vendo collects, how it is used, service providers, retention, international processing, and privacy rights.
Read the privacy policyTalk to us about your security requirements
Bring your security questionnaire, preferred deployment model, and first data workflow. We'll explain how Vendo handles each requirement and identify anything that needs to be agreed before implementation.