Beta Privacy Notice

Data we handle

• Account and profile details, including your email address and optional profile information.
• Workspace membership, plan, entitlement, trial, support, and security records, including optional two-factor authentication status and protected recovery-code records.
• Source and translation documents, paragraph text, alignment, annotations, and related project data you submit.
• Technical records needed for security and reliability, such as sessions, request identifiers, audit events, and service logs.

How we use it

We process this data to provide the translation workspace, authenticate users, enforce access and usage limits, import and export documents, respond to support requests, prevent abuse, diagnose failures, and maintain the service.

Transactional email is used for account verification, password recovery, invitations, and account or security notices. It is not used by the current product for newsletters or bulk marketing.

Optional analytics load only after you choose Allow analytics. Google Analytics 4 measures public page visits and basic actions such as registration, sign-in, plan views, and subscription requests. Private page addresses, query strings, names, email addresses, and manuscript content are excluded. Advertising signals are disabled.

Microsoft Clarity records clicks, scrolling, and masked page interactions only on public marketing and Academy pages without URL queries or fragments. It does not run on sign-in, account, administration, or manuscript workspace pages. All page text is masked. Google and Microsoft process technical usage information for these services.

Your analytics choice is stored in a necessary preference cookie shared between vajechin.com and app.vajechin.com for six months. Optional analytics cookies are used only after acceptance. You can reject analytics or withdraw permission through Analytics preferences; withdrawal reloads the page to stop the tracking scripts.

See how Google uses information from sites using its services and the Microsoft Privacy Statement.

Where manuscript data lives

Editable application data is stored in PostgreSQL. Permanent uploaded document binaries are stored in private object storage. Preview, parsing, and export may use short-lived container temporary files; VajeChin does not use a permanent local-upload fallback.

AI features are optional. When you request an enabled AI feature, selected text and necessary context, or the chosen document for whole-document translation, are sent to the configured AI provider.

Service providers

Infrastructure and transactional-email providers process data only as needed to host the application, database, private object storage, networking, deliver account messages, and support related operations. Access to workspaces is controlled through authenticated account and organization relationships.

Deletion and backups

Deleting a project removes its live project records and managed source object through the application lifecycle. Security or audit records and older protected backups may remain after live deletion. A fixed public backup-expiry schedule has not yet been approved for the beta, so do not rely on a specific backup-deletion deadline.

For an account or data inquiry, contact @vajechin_support or use signed-in Support. Account deletion is currently handled through a verified support request rather than a self-service control. Authorized operations staff revoke account access and sessions, then remove or de-identify account data according to ownership relationships. Projects and files controlled solely by the requesting user follow the normal deletion lifecycle when safe. Content belonging to shared workspaces may remain available to other authorized members. Legal-retention conflicts require manual review.

Security and your choices

VajeChin uses authenticated sessions, tenant-aware authorization, encrypted network transport, private backend services, operational logging, and optional authenticator-app two-factor authentication. No internet service can promise absolute security. Use a unique password, protect your active sessions and recovery codes, and upload only content you are authorized to process.

You can export translation work to DOCX, delete projects you control, and review active sessions in account settings. See Support for help.

Changes to this notice

The beta will evolve. Material changes will be reflected here with an updated date.