Privacy Policy

Last updated: 5 August 2026

strAImer is a desktop application for live streamers. It is developed and operated by an individual developer, reachable at straimer.com@gmail.com. This policy explains what data the application and this website handle, and it describes separately the data received from Google APIs.

The application runs on your computer

strAImer runs on your own computer. Your settings, connected accounts, stream statistics and chat history are stored in a database there, not on our servers. Data leaves your computer only in the cases listed below, and each of them is either started by you or is part of a feature you switched on.

Google account and YouTube data

When you connect a YouTube channel, you grant the application the following access. Each permission is requested because a specific feature cannot work without it.

This data is written to the application's local database on your computer. Access tokens are encrypted with the key store of your operating system and never leave your computer. We have no access to your Google password: authorization happens on Google's own page.

You may optionally connect a second Google account, so that chat messages are posted from a separate bot account instead of your own. That account grants the same permissions and is stored in the same way, on your computer only. Connecting it is optional: without it, the application posts from your own account.

Limited Use

strAImer's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data received from Google APIs is not sold, is not used for advertising, and is not transferred to anyone except as described in this policy.

When data leaves your computer

  1. The AI co-host, when you switch it on. The text of the chat message being answered and the display name of its author are sent to the strAImer server, which forwards them to the provider of the language model and returns the generated reply. The strAImer server does not store the message: only the number of tokens is recorded, because the subscription is billed by usage.
  2. Transferring settings to another computer, when you press the button. A snapshot of your settings is uploaded to your account. If you also select the statistics sections, saved chat messages and viewer records are included in that snapshot. Access tokens, passwords and API keys are never included. Snapshots are deleted after your subscription ends: statistics after 30 days, settings after a year.
  3. Web search, when the streamer asks for it. The AI co-host can look something up on the web when a message contains one of the trigger words the streamer configured. In that case the search query, which may include the wording of the viewer's message, is sent to the search provider. Without a trigger word nothing is sent.
  4. Your streamer page, while you are editing it. The page lives on our server, so its content is sent there when you save it — and also while you type: the preview is rendered on the server, so a draft travels there about half a second after each change, before you press anything. Only what you put on the page is sent.
  5. The live badge, once you sign in to your account. While a stream is running the application tells the server which platform it is on, the channel name and the game category, so that your streamer page and the site can show you as live. The switches on the page decide whether it is shown to anyone; the report itself starts with the account, not with the switch.
  6. The idea board, when you post or vote. The title and text of your idea are sent to the server together with your account name, and they are public — that is the point of the board.
  7. Signing in on this website. Your Google email and name are used to create and identify your account in the personal cabinet.
  8. Writing to support, when you press send. The text of your message is stored on the strAImer server together with your account name, the version of the application and your operating system, and it is kept for a year after the conversation is closed. If you tick the boxes for them, two files travel with it: a summary of your setup, which holds no names and no folder paths, and the tail of the application log. The log is written on your computer and does hold your viewers' display names, donation amounts and chat text — that is why it is never attached without asking, and why it is deleted 30 days after it is uploaded. Neither file is ever sent to the language-model provider.

The application's anonymous ping

Once a day the application tells our server that this copy is alive. It sends a random number the application generated for itself, its version, the update channel, the operating system and the interface language — no name, no email, no account, and nothing from your settings or your chat. That number is not linked to anything else we store: it exists only so that two pings from the same copy are not counted as two installations. We need it because the application runs on your computer, so without it we cannot tell how many copies are in use or whether an update actually reached anyone. You can switch the ping off in Settings → Updates, and then nothing is sent at all.

Visits to this website

We count visits to this website ourselves, without cookies and without any third-party analytics service. For each page opened we store the path, the page language, the host of the site you arrived from and whether the device is a phone, tablet or computer. Your IP address and browser string are used only to compute a short hash that separates one visitor from another, and neither of them is stored. That hash also includes the current date, so the same person becomes a different visitor tomorrow and no history can be assembled — not even by us. Downloads of the application are counted the same way. Counting needs no cookies at all; the cookies the site does set are the ones that sign you in, and every one of them is listed on the Cookies page.

With whom we share Google user data

We do not sell, rent or trade Google user data, we do not use it for advertising, and we do not use it to train models. It is shared only with the service providers listed below, only for the purpose named, and only when the corresponding feature is switched on:

We may also disclose data if the law requires it — for example, in response to a lawful request from a public authority. There are no other recipients.

How we protect your data

Your control over the data

Children

strAImer is not directed at children under 13 and we do not knowingly collect their data.

Changes to this policy

Any change is published on this page, and the date at the top is updated. Changes that affect how Google user data is handled are announced in the application as well.

Contact

Questions about this policy or about your data: straimer.com@gmail.com