Privacy policy
This is a standard form adapted to this service. It is not legal advice. Effective November 9, 2026. Version 2026-11-09. This policy covers the website, the Windows app, and retention of prompts and model responses in a private log.
Who this covers
This policy describes the VersicLM website at versiclm.com and the VersicLM Windows app that sits beside UEFN. The operator has not published a separate company name or postal address. Questions, including a request to delete an account or stored chats, can be raised from the support page. That page is self-service and does not promise a staffed reply or a deletion deadline.
Information the service processes
Google sign-in provides the account identity used by the website. The site stores the account record, linked sign-in fields, a browser session, and the time and version of terms and privacy acceptance.
Desktop approval stores hashed codes, the PKCE challenge, expiry, and credential metadata. It does not store the raw desktop bearer token in those credential tables. The Windows app keeps its own credential on the machine.
Stripe checkout and the billing portal handle card entry. The site stores Stripe customer, checkout, subscription, and allowance records. Card numbers are entered on Stripe, not in a card form on this site.
Model requests send the prompt and attached project context from the desktop to the model gateway and then to the configured model provider. That context can include project source or editor information needed for the task. Usage records include spend, request counts, and token counts.
Abuse controls store a keyed hash, scope, minute, and count for the caller. The implementation list is on the data facts page. That page is not a second privacy policy.
Chat logs
The model gateway keeps a copy of each successful and failed completion. The copy includes the messages that were sent, including attached project context, and the model response. Those objects are stored in a private Amazon Web Services S3 bucket used for debugging and abuse investigation.
The bucket is not public. It is separate from the website account database. VersicLM does not sell these logs. A fixed deletion schedule for them has not been published. A deletion request can be described on the support page, which does not promise a staffed reply or a deadline.
Why it is processed
The service uses this information to sign you in, record that you accepted the current terms and privacy policy, connect the desktop app, sell and account for model allowance, send a model request you start, limit abusive callers, and debug or investigate abuse of the gateway. Signing in does not grant model credits.
Who else receives it
Google receives the sign-in. Stripe receives the payment. The model gateway and the upstream model provider receive the prompt and context for a request you start, and the provider generates the response.
Amazon Web Services hosts the website and the gateway infrastructure and stores the private chat-log bucket. The operator does not sell personal information.
The desktop app
The Windows app keeps its own credential on the machine. Website sign-out does not revoke it. You can revoke model and library credentials from Usage on a device you trust. Revocation stops later authenticated use. It does not stop work already in progress, and it does not by itself delete account, payment, project, or chat-log records.
Retention
A fixed retention schedule has not been published. Account, billing, acceptance, and credential records remain while they are needed to run the account, meet payment reconciliation, or keep a revoked credential from being reused. Chat logs remain while they are needed for debugging and abuse investigation. A deletion request can be described on the support page. That page does not guarantee a staffed reply or a deletion deadline.
Children
VersicLM is not directed at anyone under 18. Do not create an account, connect the desktop app, or buy credits if you are under 18.
Changes
Updates to this policy are posted on this page with a version string. The version of this policy is 2026-11-09. If the version changes, signed-in use of account pages and desktop approval requires accepting the posted version. The data facts page remains a description of the current implementation, not a second policy.