The igrasu.ru application: its purpose, its login-free home page and its use of Google APIs

This page answers the questions asked during the OAuth application review in Google Cloud Console: what the application does, why its home page is open without a login, why the application name matches the name on the home page, and how the application complies with the Google APIs Terms of Service. The page is public — viewing it requires no login, no registration and no Google permission.

1. What this page is and who needs it

The review of an OAuth application in Google Cloud Console asks four things of a developer: the home page must be viewable without a login, the home page must state what the application is for, the configured application name must match the name on the home page, and the application must comply with the Google APIs Terms of Service. This page exists to answer those four points directly, separately from the general site policies, so that a reviewer does not have to collect the answers from different documents.

It complements the Google Cloud application privacy policy and the terms of use of Google APIs rather than replacing them: the sections on data, permissions and deletion should be read together with it. The operator is a sole proprietor who owns igrasu.ru and the IgraSU Google Cloud project; the support contact is InExSu@bk.ru.

In the console fields this address is registered as the application home page, so it has to lead into the site itself: the igrasu.ru home page, the game catalog and the blog — all three open anonymously.

2. The application name

The application is named igrasu.ru — the same name that appears in the <title> and the header of the home page, in the domain address and in the Google consent screen. The operator uses no other name: neither "IgraSU" nor any transliteration or derived form appears in the consent screen.

• the home page igrasu.ru carries the name in its <title>, in the header logo and in the first-screen text;
• the OAuth console lists the application as igrasu.ru with the authorized domains igrasu.ru and www.igrasu.ru;
• the Google consent screen shows the same name igrasu.ru and links to this page, to the privacy policy and to the terms of use.

3. The home page is open without a login

www.igrasu.ru is not behind a login page: neither the home page, nor the game catalog, nor an individual game page, nor the blog, nor the policies require registration, a password or any Google permission. An anonymous visitor is served the same content a signed-in visitor is, and a plain HTTP request without cookies proves it.

Signing in is needed only by the operator to manage content and does not affect the availability of information about the application. This page, /GCC_Privacy and /CCC_Terms are anonymous as well — no cookies, no account, no scopes.

• the catalog of browser games with search, genres and collections — a visitor plays right away, without registering;
• every game page with its description, screenshots and frequently asked questions;
• the blog pages, the site terms of use and the site privacy policy;
• the /upload page, which explains how the operator publishes gameplay recordings and is likewise open without a login.

4. Purpose of the application

igrasu.ru is a catalog of browser games that run directly in the browser without installation. The application under review serves that site: it records gameplay of games from the operator's own catalog, publishes the recordings in the operator's own YouTube channel and reads the search statistics of the site itself to understand which games people look for and which ones are missing.

The application is not distributed among other users and asks nothing of them: it is an internal tool of the operator, working with one Google account — the account that belongs to the operator.

• record the browser screen while a game from the own catalog is played through;
• prepare the video: the game title, a short description, a thumbnail and genre tags;
• upload the video to the operator's own channel through the YouTube Data API v3 and leave one first comment under it with a link to the game page;
• read the aggregate Google Search Console reports of the verified property www.igrasu.ru in order to add the games people actually search for.

5. Which Google APIs and which permissions

The application calls two APIs: the YouTube Data API v3 (publishing videos to the own channel) and the Google Search Console API (reading aggregate reports about the own site). Permissions are requested in the minimal sufficient amount and only from the operator's own account.

6. What publishing looks like: the path of one video

Every video goes through a path that leaves no room for other people's content and no room for an unattended upload.

• the operator picks a game from the own igrasu.ru catalog and plays it through in the browser;
• the browser screen is recorded; the frame contains only the game — no face, no voice, no chat, no unrelated browser tabs;
• the operator watches the whole recording and cuts everything extra out; at this step a video can be rejected and never published;
• the video is uploaded to the own channel and gets the game title, description, thumbnail and genre tags;
• one first comment with a link to the game page is published under it.

7. Compliance with the Google APIs Terms of Service

The application uses Google APIs in accordance with the Google APIs Terms of Service, the YouTube API Terms of Service and the Google privacy policies. It is not a Google product and is not affiliated with Google; the name igrasu.ru is never presented in a way that suggests Google ownership or endorsement.

The application does not create, store, upload or distribute intimate imagery generated with artificial intelligence (AI-generated NCII) or any other non-consensual intimate imagery. What is recorded is a browser screen showing a game from the own catalog: there are no people, bodies or clothing in the frame, so the subject does not arise, and a human watches every recording before it is published.

• it does not collect YouTube user data and does not analyse other people's channels;
• it does not send mass messages, does not inflate view counts and does not work around API quotas;
• it does not use Google APIs for surveillance, profiling or training machine learning models;
• it does not sell or hand over to third parties the data received through Google APIs;
• it does not upload third-party content without that party's consent.

8. Whose content and whose data

Only material shot by the operator reaches the channel: the games belong to the own igrasu.ru catalog or are distributed under open licenses, the screen recording is made by the operator and the thumbnail is a frame of that same recording. No third-party rightsholders take part in the publications.

The application does not process personal data of other people — no faces, names, contact details or device identifiers. From Google APIs it receives information about its own channel and aggregate search reports about its own site; that data is kept for a limited period, described in the retention section of the privacy policy.

9. Who grants access and how it is revoked

Consent is granted by the operator alone — with the operator's own Google account, manually, for the IgraSU project. Other users never receive a consent request: the application does not serve them and does not touch their data.

Access can be revoked at any moment on the Google permissions page; revoking it stops publishing immediately, without contacting the operator. Questions about access and data processing go to InExSu@bk.ru; a complaint about published material is reviewed within 30 calendar days, and evidently non-consensual intimate imagery is removed immediately.

10. Related documents

If the reviewer needs a live confirmation: every address above answers an ordinary GET request without cookies and without authentication.

• /GCC_Privacy — the Google Cloud application privacy policy: APIs, scopes, retention and deletion;
• /CCC_Terms — the terms of use of Google APIs: what is published, what the application never does, complaints and liability;
• the site privacy policy and terms of use — for visitors of igrasu.ru whom the Google APIs do not concern.

11. Edition

This edition is dated 10 October 2026. Changes in how the application uses Google APIs are published on this page together with updates to the privacy policy and the terms of use.

Privacy policy for site visitors · Terms of use for site visitors