Independent app studio · Seoul, South Korea

Starfathom

Two ends of one scale.

Logarithmic, in metres. The studio sits at neither end.

We make small mobile apps and publish them ourselves. Not one category, on purpose.

The studio

Starfathom is the publishing brand of STEFANCHO LABS, a one-person studio in South Korea. We design, build, and ship apps for iOS and Android, and we release them under our own name rather than through a client or an agency.

The name takes the two ends of that scale and puts them in one word. Neither is a market we work in. They are the size of thing the studio likes to think about, and they are why the index below has a passport-photo tool next to a cold-water log next to a stock app. What those share is not a category. It is that each does one thing a person actually needs on a given day, and has to be worth opening again tomorrow.

Everything is made in-house. We write the code, produce the store assets, run the release pipeline, and answer the support mail ourselves. That is also why this site is short.

Google Ads API — Starfathom Ads Manager

Advertiser · Internal use only · One operator, one advertiser account

Starfathom Ads Manager is the internal command-line tool, with local reporting output, that STEFANCHO LABS uses to advertise the apps listed below. It uses the Google Ads API on one Google Ads advertiser account that we own, under our own manager account, and on nothing else. What follows is the detailed description and the mock-ups of that tool, set out in the order of Google’s own sample design document for developer token applications.

Business model

STEFANCHO LABS is a one-person studio in South Korea, registered as a sole proprietorship under business registration number 118-04-31442. We publish the mobile apps listed below under the Starfathom name. They earn through in-app advertising and in-app purchases, and we buy installs for them ourselves. We advertise only apps we own and publish, and we do not manage ads for anyone else.

Running those campaigns by hand in the Google Ads web interface costs more clicking with every app we release, which is the whole reason for the tool.

Tool access and use

STEFANCHO LABS is the sole advertiser and the sole user of the tool. The studio is one person, so the tool has one operator and no external users. No client, customer, contractor, reseller, or other third party can sign in to it, connect an account to it, receive Google Ads data from it, or cause it to make an API request. There is nothing here to sign up for. We do not provide advertising services to anyone else, we do not manage Google Ads accounts on behalf of anyone else, and we will not distribute, sell, or license the tool.

Tool design

Starfathom Ads Manager account topology The tool authenticates with OAuth and our developer token, calls the Google Ads API, and reaches exactly one advertiser account under our own manager account. No third-party accounts are involved. Starfathom Ads Manager Internal command-line tool · one operator · STEFANCHO LABS OAuth 2.0 — scope adwords developer token · Cloud project 124877619497 Google Ads API CampaignService · CampaignBudgetService · AdGroupService AdGroupAdService · AssetService · GoogleAdsService.search Explorer Access today — Basic Access requested production reach verified 12 Aug 2026 Our own Google Ads accounts Manager account 496-983-3441 Advertiser account 956-331-4519 — the only account, ours
Every API call the tool makes lands on the one advertiser account we own, under our own manager account. No third-party account, no external user, and no other Google service is involved.

API services called

That is the entire scope. We do not create customer accounts, manage third-party users or billing, run keyword planning, resell API access, or expose our developer token through any other service. Expected volume is low, on the order of hundreds of operations a day, well inside the 15,000 operations a day that Basic Access allows.

Tool mock-ups

$ starfathom-ads campaigns list CAMPAIGN STATUS BUDGET/DAY CPI INSTALLS icelog-kr-app-install ENABLED ₩30,000 ₩1,240 24 onecut-kr-app-install PAUSED ₩20,000 ₩1,890 11 goalnine-kr-app-install ENABLED ₩25,000 ₩1,510 18 # GoogleAdsService.search across our one advertiser account $ starfathom-ads budget set icelog-kr-app-install 40000 campaign_budget/8342119076 ₩30,000 → ₩40,000 per day Apply this change? [y/N]
The command surface as designed. Every change that costs money stops for operator confirmation. The figures are illustrative: the token reached Explorer Access on 12 August 2026 and the tool is being brought up against our production account, but no real campaign has run yet.

Why Basic Access is required

Setup is complete and verified. Our advertiser account is linked to our own manager account, advertiser verification was completed on 25 July 2026, OAuth credentials are issued, and our developer token is linked to Google Cloud project 124877619497 and confirmed by a live call to the Google Ads API. That Cloud project passed OAuth brand verification on 27 July 2026.

On 12 August 2026 Google automatically upgraded our developer token from Test Account Access to Explorer Access, and we verified it the same day with live calls: GoogleAdsService.search returns production data from our advertiser account, and a validate-only campaign mutation passes authorization. Explorer Access caps production use at 2,880 operations per day and excludes services we do not use, such as account creation, user management, keyword planning, and billing. We request Basic Access for the standard 15,000-operation daily limit and the full service surface, so the same tool keeps working as campaigns roll out across every app we publish.

To be exact about where the work stands: authentication, the developer-token link, and the account topology above are built and verified against the live API, and as of 12 August 2026 the token reaches our production account under Explorer Access. The campaign and reporting operations described above are specified and scoped, and we are bringing them up against our own account now. We are describing the tool we are building for our own account, not a product we sell.

Data handling

The tool signs in with a Google Account we own and reads and writes campaign settings, budgets, ad assets, and aggregate performance figures on that one advertiser account. Credentials stay in private local configuration. Reporting data is cached locally only for our own campaign analysis, and none of it is sold, shared with third parties, or used to train machine-learning models. The tool requests no access to Gmail, Drive, Calendar, or contacts. Anything received from Google APIs is handled under the Google API Services User Data Policy, including its Limited Use requirements, and the full statement is in our privacy policy.

Index — in order of release

Contact

Support, press, and partnership enquiries: support@starfathom.com. We read every message and normally reply within two business days.

Privacy

We do not collect personal information through this website. Each app has its own policy — see the Starfathom privacy policy for how our apps handle data and for links to the per-app policies.