Privacy Policy

Effective date: 2026-10-08

This page describes the current, verified VI Engine implementation in plain language. We keep it evidence-based and update it when the product changes, rather than making broad claims that the app does not currently support. This policy applies to the customer app hosted on app.viengine.social.

What we collect to run the service

  • Account and workspace details you provide, such as email address, profile information, workspace name, and team membership.
  • Content and media you create or upload so VI Engine can draft, schedule, publish, and review your work.
  • Connected-platform authorization results when you link a social account through an official authorization-code flow.
  • Browser-side session-presence hints and workspace/UI state needed for sign-in, billing snapshots, onboarding state, and FounderSpace internal access.
  • Only after you accept Analytics, configured PostHog product analytics receives page views and page-leave events. Identified sessions use the internal user ID and workspace group. Email, token and OTP values, URL query strings, and identifier-like URL path segments are scrubbed before analytics events are sent. Automatic interaction capture and surveys are disabled. Session replay masks all rendered text and form inputs, records no canvas or network payloads, and is disabled on authentication, billing, settings, connections and inbox pages, and on URLs with query strings or identifier-like path segments. Do Not Track and the PostHog opt-out stop browser analytics and session replay.
  • When server-side analytics is configured for a deployment, our server also records a few account milestones in PostHog: connecting a social account, publishing your first post, and becoming an active user. These events are keyed only to the internal user ID and carry the platform name, never your name, email, tokens or social media content.
  • When Sentry is configured for a deployment, it receives essential error diagnostics to help diagnose the app; Sentry session replay is disabled. Default PII collection is disabled. Email, token, OTP, cookie, header, query-string and request-body data are scrubbed or removed before events are sent. Stack traces retain file and line references but contain no source context or local variable values; source maps are not uploaded or shipped. Browser performance tracing and logs are disabled.
  • Agent conversation sessions—including message content, prompt history, and thread summaries—are also stored in this browser's local storage so conversations can be restored. This browser copy is separate from the HttpOnly authentication cookies and remains until a conversation is removed or this site's browser data is cleared.

How browser sessions currently work

Customer authentication currently uses a short-lived access token together with a refresh token. Both are set by the backend as first-party HttpOnly cookies rather than being stored in browser-readable storage.

The frontend keeps session-present and UI/workspace hints in browser storage. During email verification or password reset, it also keeps the address for that in-progress code flow in tab-scoped sessionStorage, with a same-tab memory fallback if browser storage is unavailable, and clears it after successful completion. These values do not include raw auth tokens.

FounderSpace uses a separate internal auth flow. After internal credentials are verified, the backend sets a signed HttpOnly vi_founderspace_session cookie for the admin API surface. No raw FounderSpace credential is persisted in browser-readable storage.

Connected social accounts

VI Engine connects social accounts through official OAuth 2.0 authorization-code flows. We do not ask you to type your social platform passwords into the VI Engine app.

Platform credentials returned by those flows are stored on the backend in encrypted form using AES-256-GCM and are used only for the actions you authorize, such as publishing, analytics sync, or account status checks.

Retention and deletion

  • AI prompt and response logs are purged after 30 days.
  • Account deletion requested in the app takes effect immediately after confirmation and cannot be recovered. Inactive-account deletion follows email warnings and a three-day recovery period.
  • Soft-deleted gallery media is permanently removed after a 30-day grace window.
  • LinkedIn member comments and related commenter details synced to the Inbox are deleted within 48 hours.
  • Older published-content records may be anonymized after 180 days while non-identifying aggregate learnings remain.
  • Workspace-specific campaign learnings stay isolated to the correct workspace and are not described as cross-workspace learning.

When data is shared with third parties

Data is shared with third-party services when a feature requires it — for example, when you use an official social-platform connection, complete billing checkout, invoke an AI provider, use product analytics when PostHog is configured, or use error monitoring when Sentry is configured.

Different providers apply their own terms and privacy notices while you are on their domains or using their APIs.

Contact

For privacy questions or data requests, contact privacy@viengine.social.