See what Vexa covers, how rollout is handled, and which conditions apply to active use.
Privacy Policy
Privacy Policy
This policy explains what data Vexa processes, why it is processed, when it may be shared, and how privacy requests are handled.
What to expect
Clear obligations, privacy handling, and commercial context
Understand account access, lawful data use, and internal approval discipline.
Review the data categories, retention context, and processor protections that apply.
Data categories
What Vexa processes
Account and workspace data
Login identifiers, role settings, authentication metadata, and workspace administration details.
Product and business data
Product records, variants, taxonomy, media references, and connector configuration used for catalog distribution.
Audit and operations data
Events, timestamps, queue status, security logs, and rollout evidence used for reliability and traceability.
Privacy workflow data
Consent records, export requests, deletion requests, and related admin handling notes where applicable.
Why data is used
Processing supports service delivery and service protection
- Authenticate users and enforce tenant isolation.
- Run catalog, connector, and approval workflows.
- Maintain security, support, and auditability.
- Meet legal and contractual obligations.
When data may be shared
Sharing stays limited and purpose driven
- With providers needed to operate the service.
- With marketplaces or connectors when the customer initiates actions.
- With professional advisers bound by confidentiality.
- When law, court order, or regulation requires disclosure.
FAQ
Privacy questions
Does Vexa sell customer personal data?
No. Customer personal data is not sold.
Can customers request deletion or export?
Yes. Privacy workflows are tracked and handled through the current service process.
Can data cross borders?
Depending on infrastructure and connector needs, data may be processed in other jurisdictions with appropriate safeguards.
Need a commercial or legal conversation?
Talk with the Vexa team if you need clarification on rollout scope, privacy handling, or contract terms.