TXT24 — Video to Text | PDF to Text
DEVELOPMENT PREVIEW NOTICE

Privacy and data handling

This notice describes the current implementation. Operator contact details, production safeguards and retention policies require review before a public launch.

Information in the workspace

Account information includes a name, email address, password hash and session records. If Google sign-in is configured and used, the application stores the linked provider identity. Workspace information includes membership, invitations and relevant audit events.

Uploaded files, file names, type and size information, extracted text, saved transcripts, article drafts, notes, comments and generated results are stored so the workspace can provide its tools. Saved content may include revision history.

Who can access content

Workspace access depends on membership and role. Content in a shared workspace is not limited to the person who uploaded it. Do not add someone to a workspace unless that access is intended.

The implementation uses membership checks, password hashing, session controls and file inspection. Production transport security, encryption-at-rest settings, backup access and operational monitoring must be configured and verified for the actual deployment. This local preview does not establish those production guarantees.

Processing and external services

PDF conversion and English OCR use the application’s document worker. When you submit a provider-dependent job, selected text, audio or sampled video frames are sent to the configured AI provider. The selected provider is OpenAI; automatic jobs remain unavailable when its credentials and models are missing.

Video URL jobs contact the source host to obtain the requested video. Google sign-in, if configured, exchanges identity information with Google. If billing is enabled later, provider-hosted checkout will process payment information, while TXT24 stores subscription identifiers and status.

Responses requests use store:false. That setting does not by itself establish zero retention across every provider endpoint or account. Provider terms, account settings and applicable data controls must be reviewed for the intended deployment.

Cookies and local email

Essential cookies maintain browser sign-in and, when used, the short-lived Google sign-in challenge. The current web implementation does not add a third-party advertising tracker.

The local development setup sends account verification and recovery email to its local mail preview service. Production delivery and sender details have not been established by that local setup.

Retention, deletion and account access

Uploaded files stay in the workspace until removed using its controls. Moving a file to Trash allows restoration; permanent file deletion is a separate action. Account deactivation revokes sign-in access but does not automatically erase shared workspace content.

Saved transcript and article deletion, version-history cleanup, audit retention and backup deletion need an operator-defined lifecycle. Automated production retention periods and backup erasure windows have not been finalized. Keep that distinction in mind when evaluating the preview for real data.

Questions and launch review

The operator’s legal identity and production privacy contact have not been published in this preview. The Contact page records that status. Public launch requires completing those details and reviewing rights requests, provider processing, security, retention and applicable obligations.