Drafting notes — delete before publishing
- This is the long-form draft. The live page,
apps/website/app/privacy/page.tsx, is shorter and is what applies (live since 2026-10-07); it now carries the controller and processor split and the corrected sub-processor list, but not the legal-basis table, email-record retention or the other detail below (gap-log G60). The sub-processor list lives only on the website page;sub-processors.mdpoints to it.- Retention is the main risk. The text in "How long we keep it" is the intended schedule. Today there is no automatic purge of email logs, message bodies or webhook payloads in the communication service, and nothing erases a deleted account's mail logs. Either implement the purge (see
data-retention-schedule.md) or change those sentences. Do not publish a promise the system does not keep. Every bracketed sentence in §6 is gated on shipped work (gap-log IDs): the 90-day / 13-month / 30-day periods on the retention job (G14, G36); the account-deletion sentence about mail logs on the same job; "erased 90 days after deletion" on the purge pipeline (E2, E3); the consent-record sentence on the hashed-trail erase (E1, G35). Publish a bracketed sentence only when its gap is closed and deployed; until then use "on request within 30 days". Cancelling a plan and deleting a workspace are different things and the page must not blur them (G37).- Analytics: the Security page now lists Plausible, so the pages agree. The loader (
layout.tsx) skips Plausible only when the browser sends the Save-Data hint (Chrome and Edge) and on localhost; it does not check Do-Not-Track or Sec-GPC. The text claims only the Save-Data behaviour.- Sign-in providers: only Google is configured. The auth code mentions GitHub in a comment only.
- Server logs: no setting in the repo sets a retention period (Cloudflare's observability retention applies), and no aggregation code exists. The text says "kept briefly" until the real figure is read from Cloudflare (gap-log G64).
- Neon region: "Mumbai (ap-south-1)" comes from the earlier page and cannot be verified from the repo (gap-log G73).
- Grievance contact: filled 2026-10-07 with the operator (an individual), reachable at privacy@vlozi.app and the postal address. Confirm with counsel whether an individual operator needs a separately named officer.
- Counsel review before publishing. Not legal advice.
Effective 7 October 2026. This policy explains what Dipanshu Vishwakarma, trading as Vlozi, Devgaon, Azamgarh, Uttar Pradesh 276201, India ("Vlozi", "we") collects, why, how it is stored and shared, and the rights you have. It covers the website (vlozi.app) and the product (go.vlozi.app).
1. Our two roles
- As controller, we decide why and how we use the personal data of people who visit our site, create a Vlozi account, contact us or are invited to a workspace. This policy covers that.
- As processor, we handle the personal data of our customers' own contacts and recipients (a customer's newsletter subscribers, form submitters, mailbox correspondents, chat visitors) on the customer's instructions. The customer is the controller of that data and decides who is in it, what they were told and whether they consented. A person who wants access to or deletion of data a customer holds about them should ask that customer first; we will help the customer respond. See the Terms §6.
2. What we collect
| Category | What | Source |
|---|---|---|
| Account | name, email, password hash, workspace id, role, optional MFA factor; sign-in provider identity if you use one (Google) | you |
| Billing | the minimum needed to take a payment; the payment processor holds card data. We keep invoice metadata and credit-balance history. | you, the processor |
| Content | what you create: posts, newsletters, contacts, form submissions, chat transcripts, uploaded media, scoped to your workspace | you |
| Email records | for mail sent through the platform: sender, recipient, subject, delivery status and, for a limited time, message content and provider event data (delivered, bounced, complaint) | the platform |
| Suppression data | addresses that bounced, complained or unsubscribed, so they are not mailed again | the platform, mailbox providers |
| Usage and logs | timestamp, IP address, route, status and latency, for debugging and abuse prevention | automatic |
| Support | what you send us when you email or use the feedback form | you |
| Site analytics | page views and events from a privacy-respecting, cookieless analytics service (Plausible) on the marketing site; no advertising or cross-site tracking; not loaded when your browser asks to save data | automatic |
| Cookies | essential only (session, CSRF). No advertising cookies. | automatic |
3. Why we use it (and our legal basis)
| Purpose | Basis |
|---|---|
| Provide the product you signed up for: sign in, dashboard, sending mail, serving content | contract |
| Bill correctly, prevent free-tier abuse, keep records the tax law requires | contract; legal obligation |
| Support, debugging, sending service mail (login codes, invitations, notices) | contract; legitimate interest |
| Security: detect compromise, rate-limit, investigate abuse, protect the shared sending reputation | legitimate interest |
| Improve the product in aggregate (counts, latency, error rates, never the contents of your posts) | legitimate interest |
Where the law requires consent, we ask for it and you can withdraw it at any time.
4. Who we share it with
We do not sell personal data, do not share it with advertisers, and do not train models on it. A feature that uses AI sends the provider only the content the request needs, and the provider's API terms apply to it. We share data only with the service providers (sub-processors) needed to run Vlozi, listed in one place: sub-processors list. That list names each provider, what it does and where it processes data. We update it before adding a provider that handles personal data, and tell customers by email at least 14 days before the change.
We may also disclose data when the law requires, to protect people from harm, or in a business transfer, with the same protections.
5. Where it is processed
The main database runs on Neon in Mumbai (ap-south-1). Edge compute and delivery run globally on Cloudflare; uploaded media is stored on Cloudflare R2. Email is sent through Amazon SES in Mumbai (ap-south-1) and through Resend. The dashboard is hosted on Vercel. See the sub-processors list for each provider's role. Where data crosses borders, we rely on the transfer mechanisms the applicable law accepts, such as the standard contractual clauses in a provider's terms where it offers them.
6. How long we keep it
This is the schedule we intend. A sentence in brackets is published only when the job behind it exists (see the drafting notes). The detail is in the data retention schedule, which is internal.
- Cancelling a plan stops charges. It does not delete anything.
- Deleting a workspace: it leaves the dashboard, its API keys stop working and it cannot be exported afterwards, so copy what you need first. Deleting it also cancels its plan and add-ons straight away, with no refund for the rest of the billing period; if the plan can't be cancelled, the workspace is not deleted. To have the data erased, email privacy@vlozi.app; within 30 days we tell you what we erased and what we could not. [Its data is permanently erased 90 days after deletion, unless the law requires us to keep it.]
- Deleting your account removes your login, profile, settings and tasks, stops any app you connected from renewing its access, and removes you from every workspace. You must first delete or hand over every workspace you own. Feedback you sent us stays but is no longer linked to you. Work you created inside a workspace belongs to that workspace and stays with it. [Mail logs that name your address (for example login codes we sent you) age out on the schedule below.]
- Email message content: [90 days], then removed. Email metadata (who, when, delivery status): [13 months]. Since 6 October 2026, one-time login codes, password-reset links and invitation links are not stored in our mail logs.
- Webhook and delivery-event payloads: [30 days].
- A customer's consent record for a subscriber (how and when they signed up) is kept while the subscriber is on the list and erased with the subscriber or the workspace. [When a subscriber is erased, their address is removed from the list, from the send records and from our copies of the emails sent to them, and in that record it is replaced by an irreversible marker. If they had unsubscribed or complained, the opt-out is kept as a suppression record.]
- Suppression records (bounces, complaints, unsubscribes): kept for as long as needed to keep honouring them, because deleting them would mean mailing someone who asked not to be. Other records that contain an address are removed when a workspace is purged; until that job runs, ask us.
- Backups: erased data can remain in encrypted database backups until they age out of our database provider's recovery window [N days, to be confirmed from the Neon plan].
- Server logs: kept briefly. [State the real period once it is read from Cloudflare.] They can contain a recipient's email address when a send fails or is skipped.
- Billing records: the period tax law requires [confirm the period with counsel: it depends on the rules that apply to an individual proprietor].
7. Your rights
Under GDPR (EU/UK), India's Digital Personal Data Protection Act and similar laws, you can: access the personal data we hold about you; get a copy of your data (form submissions, comments and campaign reports export from the dashboard; for anything else, ask and we send it within 30 days); correct it; delete your account and, with it, your personal data on the schedule above; restrict or object to certain processing; withdraw consent; and complain to a supervisory authority.
Email privacy@vlozi.app with the request. We respond within 30 days. For data a customer holds about you, see §1. Under the DPDP Act the controller is the "data fiduciary" and the processor is the "data processor"; the roles in §1 map onto those.
Grievance contact: Dipanshu Vishwakarma, Devgaon, Azamgarh, Uttar Pradesh 276201, India, privacy@vlozi.app.
8. Security
Connections use TLS, the database is encrypted at rest, and workspace data is separated by tenant. Details are on the security page. If we learn of a breach affecting you, we will tell you as the law requires.
9. Children
Accounts must not be opened by anyone under 18. If we learn a minor has an account without a guardian's consent, we will close it.
10. Changes
We will email customers about material changes at least 14 days before they take effect. Minor clarifications are posted here with the date updated.
11. Contact
General: hello@vlozi.app · Privacy and data requests: privacy@vlozi.app · Security: security@vlozi.app · Abuse: abuse@vlozi.app · Dipanshu Vishwakarma, trading as Vlozi, Devgaon, Azamgarh, Uttar Pradesh 276201, India.