Privacy Policy

1. Scope and operator

This Policy covers Laitis Legacy 6, Laitis 7 Alpha, the Laitis browser extension, laitis.ru and Laitis online services. Their data flows differ, as set out below. “Personal data” means information that identifies you or can reasonably be linked to you; “processing” includes receiving, using, storing, transmitting and deleting it.

The operator is individual entrepreneur Sergey Andreevich Mikolaitis (ИП Миколайтис Сергей Андреевич), Krasnodar, Russian Federation. Contact for privacy requests: blasterloremaster@gmail.com. This Policy describes processing; reading or acknowledging it is not consent to every possible use of your data.

2. Microphone audio and command history

The application uses microphone audio to recognise speech, run a command or enter text. Voice recordings are not sent to Laitis servers for recognition or stored there as microphone recordings. The log of commands you ran and text you dictated is not uploaded to Laitis servers or included in the cloud synchronisation archive. In Alpha, recent phrases and audio can remain in application memory until you clear the history or close the process.

Local recognition uses an installed model or an available operating-system engine on your device. Downloading the optional model requires a connection to its host, currently GitHub. Choosing local recognition does not disable unrelated network features, such as updates or synchronisation.

When you choose Google cloud recognition, audio is sent directly from the application to Google, along with information needed for recognition, such as the selected language and network metadata. The provider applies its own policy and retention practices. Laitis does not control that provider’s processing. Do not dictate confidential material to a cloud provider unless you are satisfied with its terms.

If you save recognised text in your library or submit a collection for publication, the content you select can be sent separately from your command history. A diagnostic dump you submit can incidentally contain audio or text from process memory; this is a separate support upload (see section 8). Laitis does not use these materials for AI training or advertising.

3. Speech synthesis and older local caches

System speech synthesis can run locally. When you choose a cloud voice, the selected provider receives the text to speak, language and voice settings, and any credentials required for the request. Depending on your configuration, providers can include Google, VoiceRSS, TTS.ai and ElevenLabs. TTS.ai returns synthesized audio via a temporary download link.

Legacy and compatible older speech adapters can leave local MP3/WAV caches of short synthesised phrases; their filenames can include the text. This is separate from the Alpha in-memory recognition history. Legacy providers and protocols do not all have the same security properties; some compatible older provider requests use HTTP. Do not assume that every external connection is encrypted or that an old cache is removed when you sign out.

4. Settings and files on your devices

Laitis stores your command collections, configured phrases, actions, events, variables, speech preferences and device settings locally. It can also retain local backup archives, downloaded models and account or integration credentials needed for the features you enable. Some provider settings contain API keys. Your device’s permissions, disk protection and backups govern access to these files.

Signing out or uninstalling does not necessarily remove every settings file, backup, model or credential previously saved on the device. Remove files and credentials you no longer need using the relevant application and operating-system controls. Keep a separate copy of any library you want to preserve before deleting data.

5. Accounts and cloud synchronisation

For an online account, Laitis stores an account identifier, email, nickname, a password verification value, session information, language, registration and sign-in dates, application version, optional social profile link, role, reputation, achievements, recorded donation amounts and feature counters. An uploaded avatar is stored as a file. Email is used for account operation, recovery and replies to your requests.

In Alpha, automatic cloud synchronisation is enabled by default for compatibility. You can turn it off in Settings, in the backup and restore section, using “Cloud synchronization”. When synchronisation is enabled, the server stores an archive of your settings and command library to transfer your own configuration between computers. This is not a general server history of your microphone recordings or dictation. The archive can contain your command phrases, action texts, events, variables and speech-provider settings, including provider keys or credentials you have configured. Content you put into a persistent variable is part of that library.

Cloud archives are not end-to-end encrypted with a key held only by you: the server can access their content. Do not put secrets or another person’s confidential data into synchronised commands unless you intend that data to be stored in the archive. Turning off automatic synchronisation stops that device’s automatic uploads and downloads; it does not erase an archive already held on the server. Request server deletion using the contact in section 12.

Legacy versions and older profiles may have different synchronisation controls. The current server normally retains the latest accepted cloud archive; operational database backups can contain an earlier copy. The service uses a compatible credential protocol rather than promising modern password protection for every historical client. Use a password unique to Laitis and protect session and connection keys.

6. Public profiles and community content

An account’s community profile can make its nickname, identifier, social link, language, registration date, role, achievements, reputation, recorded donation total and activity counters visible to other users. Email and the password verification value are not fields of the public profile. Choose a nickname and profile link you are comfortable making public.

Your private cloud library is separate from the community catalogue. A publication request sends the collection you submit for review. The request, its content and its moderation status can already be visible to other users before review is complete. Approval adds the collection to the shared catalogue, where it can be downloaded. Public content can be copied or indexed outside the operator’s control. Do not publish secrets or other people’s personal data. Contact the operator to correct or remove your official publication or profile data.

7. Browser extension, Connect and MCP

The browser extension needs broad page and tab permissions to carry out configured browser actions. It can read the relevant page URL, page elements, selected text or other requested page content and communicate with the desktop application through local native messaging. Commands and scripts you run can send information to destinations you choose. This is not a routine upload of your entire browsing history to Laitis.

Connect is an optional network relay. The server processes connection keys, account or device identifiers, app version, incoming phrases, commands and replies to deliver them between connected participants. Active connection information is held while the connection is in use. If you use the Alice skill, Yandex sends Laitis the request text and an Alice user identifier, and Laitis returns the reply to Yandex. With older Connect URLs, a phrase or reply can appear in the request address and may therefore be recorded in technical logs. A shared Connect key can allow someone else to send requests; keep it private.

MCP is a separate, user-enabled local integration with an agent client. Depending on the permissions you grant, requested tools can expose your command library, recognised text, clipboard, window titles, processes or browser URL, or execute actions on your computer. The agent client and any AI service it uses apply their own policies to data they receive. Enabling MCP is not consent for Laitis to send all of your microphone audio to an AI service.

8. Statistics, diagnostics and support

The current Alpha composition keeps ordinary command, dictation-length and browser-action counters locally. Legacy clients can send account-linked numerical feature counters, recording mode and language to Laitis. These counters are distinct from the dictated text itself.

Legacy can automatically send some error reports through Slack. A report may include your account email, computer and user names, operating system information, error details and recent technical logs. These may contain fragments of a command or text involved in the failure. You can separately submit a diagnostic archive to Laitis servers. A memory dump may include microphone audio, recognised text and other data from application memory. Ordinary Alpha failures are logged locally without automatically uploading a full memory dump.

If you email support or request a commercial agreement, the operator processes your email address, message and attachments to handle that request. Do not send passwords or full payment card details.

9. Website, cookies, downloads and donations

Web and API requests expose technical metadata to the infrastructure, such as IP address, browser or app information, request address, time and result. Server and proxy logs can contain this metadata; some compatible older API protocols put account or session values in request URLs. Do not treat a request URL as public information. These records support delivery, troubleshooting and abuse prevention.

The application and website are and will remain ad-free. The website does not load advertising trackers, third-party analytics, remote fonts or embedded YouTube players. Following an external link, including YouTube, opens a separate service with its own policy.

• The essential language preference cookie, laitis.language, remembers the language of the Russian or English page you open for up to one year.
• After you request donation details, a short-lived essential cookie authorises access to the bank QR image for 10 minutes.
• The admin area uses essential authentication and security cookies for authorised operators. The authentication cookie is a session cookie.

You can clear or block cookies in your browser; the corresponding preference, QR or sign-in function may stop working. Request limiting temporarily uses network information to prevent abuse. It does not create an advertising profile.

The interactive download request checks your acceptance of the specified Terms revision and your acknowledgement of the Privacy Policy. This check is not an account registration or a consent to marketing. The current download endpoint does not maintain a separate permanent acceptance register.

When you make a bank donation, the bank handles the transfer and applies its own rules. The recipient may receive the payer name, payment comment, amount, time and other transaction details provided by the bank. The website does not ask for your card details. If a donation is associated with a Laitis account, its recorded total can appear in that account’s community profile.

10. Purposes, grounds and recipients

The operator processes the information needed to provide the features you request: account access, synchronisation, community publication, Connect delivery, updates, support and administration. Where recognised by applicable law, this processing is necessary to perform the agreement with you and deliver the requested service. Security and limited technical records support service reliability, prevention of abuse and protection of lawful interests. Legal and payment records may be processed to meet applicable obligations.

Where applicable law requires consent for a particular optional operation, it must be obtained separately and can be withdrawn. A licence acceptance or the download acknowledgement does not replace such consent. Core local features can be used without an online account; declining an optional data flow can make that particular online feature unavailable.

Data can be accessed by the operator and infrastructure or communications providers to the extent needed for the service, by people who receive content you publish or relay, by a speech or AI service you select, by Slack for Legacy error reporting, and by a bank handling a transfer. Information may also be disclosed where required by a valid legal obligation or necessary to establish or defend legal rights, subject to applicable law. This Policy does not authorise unrestricted disclosure.

11. Location, protection and retention

Data hosted on Laitis infrastructure is currently stored in the Russian Federation. An external speech provider, GitHub, email provider, bank, AI service or Slack may process information in other countries under its own arrangements. Public publications are accessible internationally. A local recognition choice does not change the location or terms of an independently enabled cloud feature.

Server access controls, authenticated service routes and release integrity checks reduce some risks, but no device, network or storage system is completely secure. Do not infer end-to-end encryption of cloud saves, modern hashing for all older login protocols, or encryption of every third-party speech request from the use of HTTPS on this website.

There is currently no fixed automatic deletion schedule covering all accounts, error reports, server logs and operational backups. Account and service records can remain until they are removed manually or in response to a request. Retention must be limited to the relevant service purpose, applicable legal duties and the establishment or defence of legal claims. You can ask what remains and request deletion; the operator will assess and act on that request under applicable law rather than treating inactivity as permission for unlimited retention.

Local history lasts for the local application session unless cleared earlier. Local settings, downloaded models and backups remain under your device’s controls. A new accepted cloud save replaces the current server archive, but an earlier copy can remain in an operational backup. Backups are separate from the active service and may require separate deletion or expiry; an immediate purge of every backup is not promised. Any legal reason to retain requested data will be explained where required.

12. Your choices and requests

You can choose a local speech engine, stop microphone capture, revoke operating-system or extension permissions, disable integrations, clear local history and, in Alpha, turn off automatic synchronisation for a device. These controls do not themselves delete information already held by an external provider or in a server backup.

Write to blasterloremaster@gmail.com to request information about your data, access or a copy, correction, account or cloud-archive deletion, restriction or objection, or withdrawal of a consent you gave. Where applicable, you can request data portability and complain to the competent data protection authority, including Roskomnadzor in Russia or your local supervisory authority. The scope and exceptions of these rights depend on applicable law.

Identify the account and describe the request. The operator may ask for proportionate information to verify ownership before disclosing or deleting data; do not email a password. Requests are handled within applicable legal time limits. There is currently no self-service account-deletion button. Uninstalling the application and disabling synchronisation are separate from deleting server-held information. For data held by a selected external service, contact that service as well.

13. External policies and changes

Review the policies of the services you enable: Google, Microsoft, Apple, Yandex, TTS.ai, ElevenLabs, VoiceRSS and GitHub. A link does not mean every provider is enabled, available or suitable for every platform. Consult the bank or AI client directly for its current policy.

Laitis is not directed specifically at children. If you believe a child’s data has been provided inappropriately, contact the operator. A person’s voice can contain sensitive information about them or other people; avoid collecting or sharing more than your chosen task requires.

Changes will be published with a new revision date. Material changes to data flows will be explained, and a separate consent will be requested where required.