Terms of use of Google APIs by the igrasu.ru application

This document supplements the general igrasu.ru terms of service and the Google Cloud application privacy policy in one respect: how exactly the service uses Google APIs and which obligations it accepts. It is written for the OAuth consent screen review in Google Cloud Console.

1. Compliance with the Google terms

The application uses the YouTube Data API v3 and the Google Search Console API in accordance with the Google APIs Terms of Service, the YouTube API Terms of Service and the Google privacy policies.

The application 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.

2. What is published through the APIs

a gameplay recording of a game from the igrasu.ru own catalog (browser screen, no third persons in it);
the game title, a short description, a link to the game page and genre tags;
one first comment under the video with a link to the game;
the video thumbnail — a frame taken from the same recording.

3. What the application does not do

it does not create, store or distribute AI-generated non-consensual intimate imagery (AI NCII) or any other non-consensual intimate imagery;
it does not upload third-party content without that party's consent: only material shot and reviewed by the operator reaches the channel;
it does not publish personal data of other people — no faces, names or contact details;
it does not harvest YouTube user data, does not analyse other people's channels and does not send mass messages;
it does not work around API quotas and limits, does not forge requests and does not use someone else's keys;
it does not sell the data received through Google APIs and does not hand it to third parties;
it does not use Google APIs for surveillance, profiling or model training.

4. Complaints and removal

Anyone who believes that published material infringes their rights or the Google terms can write to InExSu@bk.ru. The operator reviews the report and removes the material or the way it is published within 30 calendar days; for evidently non-consensual intimate imagery removal happens immediately, without waiting for the deadline.

If Google reports an API terms violation, the application stops the disputed behaviour, reissues access and reports the measures taken back to the sender of the notice.

5. Limitation of liability

Games and channel materials are provided «as is». The service does not guarantee continuous availability of third-party APIs: if Google changes the terms, quotas or refuses access, publishing stops without harming site visitors — the game catalog works independently of Google APIs.

6. What the user consent covers

Permissions are requested from a single account — the operator's own account. The application is not distributed among third-party users and does not ask them to sign in with Google: the consent screen shows exactly the scopes listed in the privacy policy and nothing beyond them.

Consent is given voluntarily and can be withdrawn at any time on the Google permissions page. After revocation the application loses access immediately, not when the token happens to expire.

The application does not request access to mail, contacts, calendar, drives or browsing history, does not add permissions without re-reviewing the consent screen, and does not ask for permissions «just in case».

7. How a publication happens: process and oversight

Every publication passes through human hands. Automation takes over only the routine: assembling the recording, preparing the title and description, uploading the file, posting the first comment.

the gameplay recording is watched by the operator before upload; a frame containing someone else's personal data or third-party content does not reach the channel;
the title, description and tags are checked against what the video actually shows: clickbait and promises of features that do not exist are forbidden;
a video is published in a status the operator sees in advance, and becomes public only after that check;
taking a video down is a routine operation: on a complaint, on a Google request or by the operator's decision the video is removed with the same tool.

8. API quotas and limits

The application respects the YouTube Data API v3 quotas: uploads run one at a time, in sequence, counting the operation cost against the daily budget. When the quota is spent, publishing is postponed to the next day — the quota is not worked around with second accounts, proxies or any other trick.

Search Console API calls are batched reports for the verified property www.igrasu.ru, issued no more often than the daily report needs; parallel requests and repeated requests for the same report are not made.

9. Rights in the published material

Only material the operator holds rights to reaches the channel: a recording of the operator's own website and the operator's own texts. Third-party music, video, images and assets of other people's games are not embedded in a publication.

Games are uploaded to the catalog by their authors, who are themselves responsible for the rights in them; igrasu.ru moderates the uploads and takes a game down on a well-founded complaint from the rights holder, without waiting for a court decision (see the general site terms of use).

10. Changes to these terms

These terms may change in one direction only: making clearer what the application does, and adding limits on itself. Material changes are published on this page and the edition date is updated.

11. Edition

This edition is dated 9 October 2026. Changes appear on this page and in the application privacy policy.