VDF AI Documentation

Privacy & Security

Review the end-user privacy and security practices that matter when you sign in, connect apps, upload files, and share outputs.

What this page covers

This page explains privacy and security topics from the end-user perspective. It is not a legal contract or a technical architecture reference.

Protect your account

  • Use a strong, unique password if your workspace uses password sign-in.
  • Revoke access to accounts or devices you no longer use.
  • Reconnect apps only through the official integration flows inside VDF AI.
  • Contact your workspace owner if you believe your account was accessed unexpectedly.

Be deliberate with connected apps

When you connect Google, Microsoft, Jira, GitHub, Slack, Zoom, or other tools, only approve the access your team actually needs.

Good habits:

  • use the correct work account
  • review the permission screen before approving
  • disconnect unused apps
  • reconnect apps when access changes instead of sharing workarounds

Be careful with uploaded content

Before uploading or pasting content:

  • confirm the material is appropriate for the workspace you are using
  • avoid including secrets, passwords, or tokens in prompts
  • remove highly sensitive personal data unless it is necessary and approved for that workflow

If a document contains sensitive information, make the prompt as narrow as possible so the result stays focused.

Review outputs before sharing

VDF AI can generate strong drafts quickly, but you should still review:

  • factual accuracy
  • recipient list before sending or sharing
  • customer or employee names
  • sensitive details in exported reports or summaries

When to reconnect or revoke access

Reconnect or revoke a connected app if:

  • the wrong account was authorized
  • access expired
  • a team member left the organization
  • you no longer want that app available in the workspace

When to contact support or your workspace owner

Ask for help if:

  • you think the wrong person has access to the workspace
  • a connection behaves in a way you did not expect
  • content from the wrong account appears in results
  • you need confirmation about approved usage for a sensitive workflow