TypeFlowTrust center

Trust center

Privacy

TypeFlow keeps typing content out of product history and clears live job payloads when a run ends. This page explains the data that is still needed to operate accounts, devices, billing, and optional AI features.

Last updated September 4, 2026

Data TypeFlow processes

  • Account profile data from Clerk, including your account ID, email address, name, image, and subscription state.
  • Paired-device metadata such as device name, platform, architecture, app version, session status, and last-seen time.
  • Settings, feature entitlements, and usage counters needed to operate your account and enforce plan limits.
  • Typing text, cursor hints, and target-preview images only while a browser-to-desktop job is active or awaiting recovery.
  • Text or screenshots submitted to optional grammar, translation, cursor-targeting, or Auto Fill features.

Typing-content boundaries

TypeFlow does not provide a user-facing typing history. When a desktop job completes, fails, or is canceled, its title, text, cursor hint, target preview, and target coordinates are cleared. The remaining record contains operational status needed for idempotency and recovery.

TypeFlow does not read or retain the contents of the destination field for active-field typing. Local refresh credentials are stored with operating-system encryption or the operating-system keychain; plaintext fallback is not used.

AI and service providers

Optional AI features send the submitted text or screenshot to the provider configured by TypeFlow. The hosted service currently supports Google Gemini for text and vision features, with an operator-configured OpenAI-compatible endpoint available for text features. Those providers may process data under their own terms.

TypeFlow also relies on Clerk for authentication and billing, Convex for application data, Vercel for web hosting, and Google for Google Docs authentication and document access.

Retention and deletion

Usage records store counts, feature names, token totals, and input lengths rather than submitted content. Device sessions and settings remain until they are revoked or the account is deleted. Deleting the Clerk account triggers deletion of TypeFlow-owned account, settings, device, job, template, usage-log, and pending-reservation records.

Third-party processors may retain data according to their own policies. Destination applications, including Google Docs, may keep revision history independently of TypeFlow.

Your choices

  • Do not use an AI feature if you do not want its input sent to the configured AI provider.
  • Revoke a paired desktop from the account device page.
  • Delete your account through the Clerk account controls to trigger TypeFlow data deletion.

For a privacy question or deletion problem, use the private contact route described on the support page.