1. Current list.
| Provider | What it does for Vlozi | Personal data involved | Region we choose |
|---|---|---|---|
| Cloudflare, Inc. | Edge compute (Workers), DNS, object storage (R2), static hosting (Pages), inbound email routing, bot checks (Turnstile) | All content and traffic that passes through the platform, in transit; stored media; inbound mail | Global edge network |
| Neon, Inc. | Managed Postgres databases | Account, workspace and product data; email records; contacts | AWS ap-south-1 (Mumbai) |
| Amazon Web Services (SES, SNS) | Outbound email delivery, and delivery, bounce and complaint events | Recipient addresses, message content in transit, delivery events | ap-south-1 (Mumbai) |
| Resend, Inc. | Delivery of mail sent from vlozi.app (login codes, invitations, notices, replies from Vlozi's own mailboxes), and fallback delivery when Amazon SES cannot deliver a message | Recipient address and content of those messages | Chosen by the provider |
| Vercel, Inc. | Hosting of the dashboard web application | What the dashboard shows you, in transit; request metadata | Chosen by the provider |
| Razorpay Software Pvt. Ltd. | Payment processing | Billing contact and payment details (card data is held by Razorpay, not Vlozi) | India |
| Anthropic, PBC | AI model processing for features that use it (chat, content assistance) | Only the content needed for the request | Chosen by the provider |
| Google LLC (Gemini) | AI model processing for features that use it, as the alternative or fallback model | Only the content needed for the request | Chosen by the provider |
| OpenAI, L.L.C. | Text embeddings for knowledge search | Text chunks you add to a knowledge base | Chosen by the provider |
| Plausible Analytics | Cookieless, privacy-friendly analytics for the marketing site (vlozi.app) | Page views and events, no personal profile | Chosen by the provider |
A region is named where Vlozi chooses it (the database and email delivery) or where the provider operates in a single country (Razorpay). Where the provider decides, we do not name one.
2. Identity providers.
If you choose to sign in with Google, Google tells us who you are (name, email) and we tell Google that you signed in. Google acts as its own controller for that; it is not a Vlozi sub-processor.
3. Services you connect.
If you connect Vlozi to a third-party service of your own (a messaging app, a social platform, a custom domain, a webhook you configure), that provider is your service provider, and you are responsible for your relationship with it. Vlozi sends data to it on your instruction.
4. Changes and objections.
We email customers at least 14 days before adding a sub-processor that handles personal data. If you object on reasonable grounds, write to [email protected] within that time and we will discuss options; if we cannot resolve it you may cancel without penalty.
5. Questions.
[email protected]. Postal: Dipanshu Vishwakarma, trading as Vlozi, Devgaon, Azamgarh, Uttar Pradesh 276201, India.