Statement of use
Advertising & Google Ads API use
RSC Labs both buys advertising, to acquire players for our own games, and shows advertising inside those games. This page describes exactly what we do in each role, and how we use the Google Ads API. It is maintained as our public statement of use.
Last updated: 20 August 2026 · Maintained by RSC Labs · API contact rodrigo@rsclabs.net
In one sentence: we use the Google Ads API for internal use only — to manage and report on Google Ads campaigns that belong to RSC Labs, promoting apps published by RSC Labs. We do not provide, sell, resell or expose any Google Ads functionality to third parties, and no party outside RSC Labs has access to our developer token or the tooling built on it.
Role one · Advertiser
We buy installs for our own games.
Our marketing consists of user-acquisition campaigns for Legacy XI, run from Google Ads accounts owned by RSC Labs and paid for by RSC Labs. There is no agency, no client and no media reselling.
- Advertised products
Legacy XI (com.rsclabs.legacyxi), published by RSC Labs on Google Play and the App Store. Future RSC Labs titles will be advertised from the same accounts.
- Campaign types
App-install and app-engagement campaigns, plus limited search and display activity for our own brand terms.
- Accounts
Google Ads accounts owned by RSC Labs, linked under our own manager account. We do not manage, access or bill any account belonging to another business.
- Landing destinations
The Google Play and App Store listings for the advertised app, and pages on this website. We do not operate affiliate, arbitrage or content-farm destinations.
Role two · Publisher
We show advertising inside our games.
Legacy XI is free to download and is partly funded by advertising served through Google AdMob, alongside optional in-app purchases.
- Ad network
Google AdMob. Our publisher ID is pub-5734852262506917, declared in app-ads.txt on this domain.
- Formats
Rewarded and interstitial placements at natural breaks in play. Advertising never obstructs a match in progress and is never required to continue playing.
- Consent
Consent for personalised advertising is requested on first run using Google's consent management, and can be changed later in the game's settings. Where consent is declined or unavailable, non-personalised advertising is served.
- Audience
Legacy XI is a general-audience title and is not directed to children. We do not knowingly serve personalised advertising to users under the applicable age of consent.
- Removing ads
An optional in-app purchase removes advertising. See the Legacy XI page for what purchases do and do not affect.
Google Ads API
Statement of use, in the terms the policy asks for.
- Use category
Internal use only. The API is used solely by RSC Labs, on Google Ads accounts owned by RSC Labs, to manage and report on advertising for apps published by RSC Labs.
- Purpose
To automate routine campaign operations and to pull our own performance data into an internal reporting view, rather than doing both by hand in the Google Ads interface every day.
- Who uses the tooling
Employees and contractors of RSC Labs only. The tooling is an internal script and dashboard; it has no public interface, no sign-up, no customer accounts and no login for anyone outside the company.
- Third-party access
None. We do not offer the tooling as a product or service, do not share or sublicense our developer token, and do not act on behalf of any other advertiser or agency. No third party can trigger a Google Ads API call through anything we operate.
- Accounts accessed
Only Google Ads accounts owned by RSC Labs and linked to our own manager account.
- Required Minimum Functionality
Under Google's published policy, RMF does not apply to internal-use-only API clients. Should our use ever change — for example if we opened tooling to advertisers outside RSC Labs — we would notify Google and comply with the applicable requirements before doing so.
- Expected volume
Well within the Basic Access level allowance of 15,000 operations per day. Our activity is a small number of accounts and campaigns, polled on a daily cadence.
- Authentication
OAuth 2.0 credentials belonging to a Google Cloud project owned by RSC Labs, used with our own developer token. Credentials are held in server-side configuration and are not distributed in any client application.
What the tooling does
Operations we automate
Each of these acts on RSC Labs' own campaigns, in RSC Labs' own accounts.
- Reporting
- Daily retrieval of spend, installs, and campaign and ad-group performance for our own accounts
- Budgets & bids
- Scheduled budget and bid adjustments against targets we set ourselves
- Campaign state
- Creating, pausing and resuming our own campaigns and ad groups
- Creative rotation
- Uploading and retiring our own ad assets
- Monitoring
- Alerting us when a campaign of ours stops delivering or overspends
Data handling
What we do with what we pull
Campaign data retrieved through the API is business data about our own advertising, not personal data about players.
- Stored where
- A private Google Cloud project owned by RSC Labs
- Who can see it
- RSC Labs personnel only
- Sharing
- Not shared, sold, licensed or made available to any third party
- Player data
- Handled separately and described in our privacy policy. We do not upload player identifiers to Google Ads for audience building
- Compliance
- We operate under the Google Ads API Terms & Conditions and the Google Ads API policies, and keep the API contact email in our manager account current
Contact
Policy and API correspondence.
If you are reviewing an application, auditing our use, or need any of the above confirmed in writing, write to us directly. We monitor this address daily and reply within five business days.
- Entity
- RSC Labs · CNPJ 66.442.055/0001-60
- Address
- Rua 14 de Julho, 460, Porto Alegre, RS, Brazil
- API contact
- rodrigo@rsclabs.net
- Publisher ID
- pub-5734852262506917 · app-ads.txt
- Privacy
- Privacy policy · Account deletion