Vendinav legal · Version 1.0
Subprocessors
Vendinav uses the following providers to deliver and operate the service. Data disclosed depends on the feature used.
Effective July 16, 2026
Current providers
Supabase
- Purpose
- Authentication, database, realtime features, and file storage
- Relevant data
- Account and company records, workflow content, messages, files, preferences, and authentication data
Vercel
- Purpose
- Application hosting, delivery, and operational infrastructure
- Relevant data
- Requests, technical logs, device and network data, and application content processed to provide the service
Stripe
- Purpose
- Vendinav subscription billing and customer billing management
- Relevant data
- Billing contact details, customer and subscription identifiers, payment-method details handled by Stripe, invoices, and transaction status
Postmark
- Purpose
- Transactional and workflow email delivery
- Relevant data
- Recipient and sender addresses, message content, delivery metadata, and email preference links
Upstash QStash
- Purpose
- Queued and scheduled workflow processing
- Relevant data
- Job identifiers, workflow instructions, delivery metadata, and limited content required to perform queued tasks
OpenAI
- Purpose
- AI-assisted drafting, normalization, and classification features
- Relevant data
- Prompts and the job, RFQ, category, Vendor, website-evidence, or uploaded spreadsheet content needed for the selected feature
Firecrawl
- Purpose
- Retrieval of public Vendor website evidence
- Relevant data
- Public Vendor website URLs and the resulting public page content
Stripe’s limited billing role
Stripe processes Vendinav subscription billing and associated billing management. It does not process Buyer-to-Vendor payments through Vendinav, and Vendinav is not the merchant of record for an external Buyer–Vendor transaction.
Questions
Privacy and data-processing questions may be sent to privacy@vendinav.com.