Privacy Policy

Last updated: August 2026

Scope

This policy describes the data processing of screph.com, the desktop program Screph and the standalone program Voice2Text. Local and network operations are listed separately.

Site and account data

  • Site visit: path and method of request, time, IP address, User-Agent, referral source and technical sign of automatic request. For a logged-in user, the entry can be associated with an account.
  • Account: user name, email address, interface language, session data and available network transaction balance.
  • Downloads: name and size of the output file, time, technical status of the transfer, IP address, User-Agent and referral source.
  • Support: message text, explicitly attached images and technical data necessary to continue the dialogue.
  • Diagnostics: only the archive that the user has explicitly chosen to send. Logs may contain paths, project names, and information about the working environment.

Local program data

Projects, source images, markup, local computer vision results, models, logs and settings are stored on the user's computer. Screph does not upload the project to the cloud just because it is opened or saved.

API keys and account tokens are stored in the system credential store when supported by the selected connection. File paths, service addresses, and common preferences can be stored in local settings without encryption.

When data is transferred over the network

  • Cloud speech recognition: the selected audio recording and recognition parameters are sent to the specified service.
  • LLM: the selected text, context, and attachments are sent to the service from the active profile. The composition of the context depends on the specific operation.
  • Network flows: the program connects to the address specified by the user.
  • Models and updates: when checking or downloading files, the server receives the usual technical data of an HTTPS request. The project and personnel are not included in such requests.
  • Account Screph: program connection, profile, support and available server operations require authorization and transmit data to the selected function.

Local Vosk and local connections LLM do not push content to an external cloud provider, but require an installed model and a running local service.

Cookies and Browser Storage

The site uses service cookies for session, form protection and selected language. The browser's storage may store the language, display name, and session token; The password is not written there. Cleaning site data removes these local values.

External recipients

Data can be received by the infrastructure necessary for the operation of the site, user-selected LLM and speech recognition providers, model sources and specified network flows. Video pages load the YouTube player, and the site design can be loaded from jsDelivr. These services apply their own terms and policies.

Data may also be disclosed if required by applicable law or to protect the safety of the service and users.

Storage period and deletion

There is no single automatic deletion deadline for all data. Local projects, models, logs, and caches remain until the user deletes them or clears the corresponding function. Server logs, support tickets, and submitted reports are retained until administrative deletion or processing of the applicable user request. The timing of external services is determined by their policies.

Locating and clearing local data is described in the local storage help.

Security

Technical and organizational measures are used to protect data, but neither local storage nor transmission over the Internet can be considered absolutely secure. Do not post secrets to public Issues, forum or Telegram.

User requests

Subject to applicable law, the user may request access, correction, deletion or restriction of the processing of personal data. For account or personal information related queries, please use the personal support chat in your profile.