TermsPrivacyCookiesRefund PolicyService providers

Privacy Policy

Version 2026-11-14 · Effective 14 November 2026

Who we are

VI Engine is a product of CorrelateX (sole proprietorship), Udyam UDYAM-DL-04-0056391, House No. 6, Block A, A-6 Derawala Nagar, New Delhi 110009, India. Contact: ops@viengine.social ("we", "us"). We decide why and how your personal data is processed for VI Engine, so under India's Digital Personal Data Protection Act, 2023 we are the Data Fiduciary (the "controller" under the GDPR).

This policy covers the VI Engine app at app.viengine.social and the website at viengine.social. Contact: privacy@viengine.social.

What we collect and why

  • Account details (email, name, password hash, sign-in method, plan) to create your account, sign you in and run your subscription.
  • Workspace and brand details (workspace name, team members and roles, brand profile, documents you add) to run your workspace and ground AI drafts in your business.
  • Content you create or upload (posts, scripts, photos, logos, voice notes you record for the Agent, generated ads) to draft, render, schedule and publish your work.
  • Connected-account data (see the Facebook, Instagram and LinkedIn sections below) to publish for you and show results.
  • Billing records (plan, amounts, invoice and payment references; never full card numbers) to bill you and handle refunds.
  • Acceptance records: which Terms and Privacy versions you accepted, when, how, and a keyed hash of the IP address and browser used, as evidence of the agreement.
  • Technical data (IP address, browser, error reports, security logs) to keep VI Engine secure and working.
  • Optional analytics, only after you accept analytics cookies (see Cookies and analytics below).
  • Marketing preference: we send blogs, tips and offers only if you tick the box at signup or turn it on in Settings.

We process this data to perform our contract with you, with your consent where we ask for it (analytics, marketing, connecting accounts), to meet legal obligations, and for our legitimate interest in keeping the service secure.

Facebook and Instagram data

When you connect a Facebook Page or Instagram professional account, VI Engine receives, with your permission:

  • the Page's and account's ID, name, username and profile picture, and public profile details such as category, description, website, bio, and follower and post counts;
  • an access token that lets VI Engine act for the Page or account only when you ask it to;
  • the posts you publish through VI Engine and their reactions, comments, shares and insights (views, reach, clicks, saves), plus daily account insights such as followers, reach and profile views;
  • comments other people leave on those posts, including the commenter's name or username.

We use this data only to provide VI Engine's features to you: connecting accounts, publishing and scheduling, showing engagement and analytics, collecting comments in your Inbox and sending the replies you approve, and tailoring AI suggestions to your business. We do not sell it, use it for advertising, or share it with other customers.

When Meta sends a signed data-deletion request, we verify it against the matching app identity. For an identity we can map unambiguously, we remove the connected Meta credentials and account, Meta profile details and history, comments, engagement and insight records, and webhook events linked to that connection. If the identifier cannot be mapped safely, we record the request for review and never delete a VI Engine account or workspace on its basis.

LinkedIn data

When you connect LinkedIn, VI Engine receives your member ID, name and profile picture, and an access token that lets it publish the posts you approve. It does not read your feed, connections or messages, or engagement on your personal posts.

Where LinkedIn Page management is available and you connect a Page, comments on your Page's posts and the commenters' details are synced to your Inbox and deleted within 48 hours, as LinkedIn requires.

AI processing

To draft posts, scripts and replies, VI Engine sends the relevant text to an AI provider: your brief, drafts, business context and, when you ask for a reply suggestion, the comment you are replying to (which may include the commenter's name). Ordinary text goes to DeepSeek, with Google Gemini as the backup. Images, voice-overs, speech-to-text, document reading and photo animation use Google Cloud AI services.

We keep our own logs of AI prompts and responses for 30 days for debugging, then delete them. The providers' own retention is set by their terms and is listed on our Service providers page. We do not use your content to train our own models.

How VI Engine learns what works

VI Engine looks at how your published posts and ads performed and uses that to shape your next plans, posts and ads. It does this in two ways.

From your own results. VI Engine compares your posts with your own average: which opening styles, formats, lengths, topics, posting times and platforms earned more engagement for you. This learning is worked out from your workspace's data, is used only for your workspace, and is deleted with it. No other customer sees it.

From anonymised, combined results across brands. VI Engine also combines results from brands in the same line of business and country, so that every brand benefits from what works in its niche, including a new brand that has no results of its own yet.

What goes into the combined results is limited to patterns: a label for the kind of post (for example "carousel", "opens with a question", "evening"), how many posts had it, and how those posts did compared with the same brand's own average. The text of your posts, your brand and business names, account handles, links, images, videos, audience details, spend, and anything else that could point to you are never included.

A combined result is used only when at least five different workspaces and at least fifty posts contribute to it. Below that, nothing is combined. No single workspace can count for more than a quarter of any combined result. The combined results are recalculated regularly from current data, so when you opt out or delete your account your contribution is left out from the next recalculation.

Your choice. Your results are included by default. You can leave at any time in Settings → Privacy & data → "Learning across brands". Leaving does not change what you get: you keep your own learning and still benefit from the combined results.

This learning is statistics, not AI training. We do not use your content to train AI models, and no AI provider receives your results for this purpose.

Who we share data with

We share personal data only with service providers that process it for us to run VI Engine, with the platforms you connect when you ask us to publish, with payment providers when you pay, and when the law requires it. We do not sell personal data.

The full list, with what each provider receives and where it processes data, is on our Service providers page. Providers apply their own terms and privacy notices when you use their sites or sign-in screens directly.

International transfers

Our app servers, database (Supabase) and media storage run in Mumbai, India. Some providers process data outside India: DeepSeek processes text in China; photo animation runs in Google Cloud's United States region; email, error monitoring and analytics providers are mainly in the United States. We transfer data abroad only as needed to run VI Engine and only to countries the Indian Government has not restricted.

How browser sessions work

You stay signed in through one first-party cookie, __session, set by our backend as HttpOnly, Secure and SameSite=Lax. It holds a short-lived access token and the refresh token that renews it. Page scripts cannot read it, and it is not kept in browser-readable storage.

The app keeps non-secret hints in browser storage: which workspace you selected, whether a session is present, and cached screens. During email verification or password reset it keeps the address for that flow in this tab's sessionStorage and clears it when you finish. Agent conversations (messages and summaries) are also kept in this browser's local storage so they can be restored; they stay until you remove the conversation or clear site data.

Internal staff tools use a separate signed HttpOnly cookie, and no staff credential is stored in browser-readable storage.

Cookies and analytics

  • PostHog analytics runs only after you accept Analytics. It receives page views and page-leave events, keyed to an internal user ID and workspace, and we attach your account email and display name to the PostHog person profile so support can recognise a session. Email, tokens, codes, URL query strings and identifier-like URL segments are removed from events first. Automatic click capture and surveys are off. Session replay records the rendered app and ordinary page text and interactions so we can support you: passwords, one-time codes, payment fields and contact details typed into forms stay masked, sensitive regions are explicitly masked, and replay is off on sign-in, billing, settings, connections and inbox pages. No source code, network payloads or headers are sent to PostHog. Do Not Track and the PostHog opt-out stop it.
  • Server milestones: where server analytics is configured, our server records a few account milestones in PostHog (connecting a social account, first publish, becoming active), keyed only to the internal user ID and platform name.
  • New Relic provides server application-performance monitoring (request timings and errors; no request bodies, emails, tokens or social content) and, only after you accept Analytics, browser performance monitoring (page-load timings, page views and scrubbed client errors; Do Not Track stops it).
  • Sentry error monitoring runs without consent because it is needed to keep the app working and secure. Default personal-data collection is off; emails, tokens, codes, cookies, headers, query strings and request bodies are scrubbed before sending. Replay, browser tracing and logs are off.

Change your choice any time with Cookie settings in the footer or in Settings → Privacy & data. Details: Cookie Policy.

How long we keep data

  • Your account is kept while you use VI Engine. Accounts inactive for 90 days are deleted after email warnings at 60 and 80 days, with a 3-day window to recover.
  • Deleting your account in Settings → Privacy & data takes effect as soon as you confirm and cannot be undone. Your personal workspaces, posts, media, connected accounts and Agent history are deleted. Your user record is kept only as an anonymised placeholder, with your personal details removed, so shared workspace history stays consistent. If you own a workspace that other people use, you must transfer it first; workspaces you joined keep the content you contributed.
  • Published posts and ads stay on Facebook, Instagram, Threads and LinkedIn after you disconnect or delete your account. We cannot delete them for you; remove them on the platform.
  • Connected-account tokens are deleted as soon as you disconnect the account.
  • AI prompt and response logs: 30 days.
  • Platform webhook notifications (which can include commenter names and comment text): 30 days.
  • Deleted gallery media: hidden at once, permanently removed after 30 days.
  • Published-content records: anonymised after 180 days; only non-identifying aggregate counts remain.
  • Combined learning results: hold no personal data and nothing that identifies a workspace or brand. They are recalculated regularly; a workspace that opts out or is deleted drops out of the next recalculation.
  • Payment records are also kept by Razorpay or Dodo Payments under their own legal obligations.
  • Backups of our database may hold deleted data for a limited period until they expire.

Your rights

You can:

  • access and export your data: Settings → Privacy & data → Download Data Export;
  • correct your details in Settings → Profile, or ask us for anything you cannot change yourself;
  • delete your account: Settings → Privacy & data → Delete My Account;
  • withdraw consent for analytics (Cookie settings) or marketing email (Settings → Notifications, or the unsubscribe link in any marketing email); withdrawal does not affect processing before it;
  • nominate someone to exercise your rights if you die or become unable to, by emailing us; and
  • complain to our Grievance Officer (below) and, in India, to the Data Protection Board of India.

Email privacy@viengine.social for any request. We may need to confirm your identity first.

Security and breaches

Connected-account tokens are encrypted with AES-256-GCM. Sign-in cookies are HttpOnly. If a breach affects your personal data, we will tell you and the authorities as the law requires, including the Data Protection Board of India and CERT-In.

Children

VI Engine is for people aged 18 or over using it for business. We do not knowingly process children's data. If you think a child has an account, email privacy@viengine.social and we will delete it.

Grievance Officer

Grievance Officer: Ayush Verma, CorrelateX, House No. 6, Block A, A-6 Derawala Nagar, New Delhi 110009, India. Email privacy@viengine.social. We acknowledge complaints within 24 hours and aim to resolve them within 15 days.

Changes to this policy

Each version of this policy has a version number and effective date. If a change materially affects you, we will tell you in the app or by email and ask you to review it.