App Developer Email Finder: Google Play, App Store, Steam avatar

App Developer Email Finder: Google Play, App Store, Steam

Pricing

from $1.05 / 1,000 app with developer emails

Go to Apify Store
App Developer Email Finder: Google Play, App Store, Steam

App Developer Email Finder: Google Play, App Store, Steam

Find the public developer email, website, address, phone and privacy policy of any app on Google Play, the Apple App Store, Steam or the Chrome Web Store. Give app URLs or IDs, or a keyword per store. $0.0015 per app with an email; apps without one are free. No login.

Pricing

from $1.05 / 1,000 app with developer emails

Rating

0.0

(0)

Developer

Data Gleaner

Data Gleaner

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

12 days ago

Last modified

Features

Limited permissions

Share

App Developer Email Finder: Google Play, App Store and Chrome Web Store

Find an app developer's email and contact details on three stores with one tool: Google Play, the Apple App Store and the Chrome Web Store. It answers the searches "app developer email", "app developer contacts", "app store developer contact", "google play developer email" and "chrome extension developer email". Give it app URLs or IDs (any of the three stores), or search the App Store by keyword, and get each developer's public support email, website, postal address, phone and privacy-policy URL, plus installs, rating, category and last update. You pay $0.0015 only for an app whose developer has a public email; an app without one is returned free. No login, no API key, no CAPTCHA, no browser.

Built for AI agents and lead-generation pipelines as well as people: one row per app, the same fields for every store, and the price tied to the answer you wanted.

What it finds

Every store asks developers to publish a way to reach them, and this Actor reads it from the store's own data for that app:

StoreEmailWebsiteAddress and phoneOther
Google PlayThe listing's developer email, plus the trader email when the developer declared oneYesFrom the trader declaration (most apps)Privacy policy, installs, rating, category, last update, price
Apple App StoreThe developer's website (from Apple's iTunes API), then an email found thereYesNoRating, category, release and update dates, price
Chrome Web StoreThe developer's contact emailYesFrom the trader declaration, when givenSupport page, privacy policy, users, rating, last update

On Google Play and the Chrome Web Store the contact block is read from the app's own record, never from a scan of the whole page, so the emails of "similar apps" on the same page never leak into a row.

With followLinks on (the default), it also visits up to 3 pages of the developer's own site (the website, its contact page, the support page or the privacy policy) to add emails and the developer's social profiles (X, LinkedIn, Facebook, Instagram, YouTube, GitHub, Discord and more). Only addresses that belong to the developer are kept: the site's own domain, or a domain named after the developer, or the domain of an address the store already listed. Free-mail (webmail) and personal-looking addresses (first.last@) are never returned. Hosting, agency and platform addresses on those pages are dropped. A developer with 40 apps has its website read once per run.

Use cases

  • App-marketing and ASO agencies: build outreach lists of apps in a niche (habit tracker, meditation, budget app) with the developer's email and install band.
  • User-acquisition and ad networks, SDK and B2B SaaS sales: find the developers of apps in a category and reach the right company, with its legal name and address.
  • App scouts and publishers: list App Store apps by keyword with the developer's website and email.
  • Chrome extension acquisitions and partnerships: contact the developers of extensions with a given number of users.
  • An AI agent or enrichment pipeline that needs "the developer's email" for a list of store links, paying only for hits.

Input

FieldMeaning
appsStore URLs or IDs from any of the three stores; the store is read from the URL. Google Play com.example.habits, App Store id1000000001, Chrome extension ID (32 letters).
datasetIdDataset of another Actor (for example Google Play or App Store scraper results) to read apps from. See "Run it after Google Play Scraper" below.
maxDatasetItemsMost apps taken from that dataset (default 1000).
searchKeywordsFind apps by keyword, e.g. habit tracker, in the App Store. Google Play and Chrome Web Store keyword search are retired (their robots.txt disallows search); give those apps in apps.
storesStores to search: appStore (default); googlePlay and chromeWebStore are retired for keywords (a free error row).
maxAppsPerKeywordApps taken from each keyword in each store (default 30). The App Store up to 200.
countryTwo-letter storefront (default us). Sets the storefront searched and the price currency.
followLinksVisit up to 3 pages of the developer's site for more emails and socials (default true).
onlyWithEmailOutput only apps with a developer email (default false). Apps without one are free either way.
maxConcurrency, delaySecs, requestTimeoutSecs, respectRobotsTxtPacing and network options. No proxy is used. Robots.txt is always honoured, including Google Play and Chrome Web Store pages and any Crawl-delay; respectRobotsTxt is kept only so old inputs still run. A disallowed store page gives a free row saying it was not fetched.

Leave everything empty to run a sample of 5 App Store apps for "habit tracker" (Google Play and Chrome Web Store keyword search are retired because their robots.txt disallows it; those apps still work by URL or ID) (about 10 seconds).

{
"searchKeywords": ["habit tracker", "meditation"],
"stores": ["appStore"],
"maxAppsPerKeyword": 30,
"onlyWithEmail": true
}
{
"apps": [
"https://play.google.com/store/apps/details?id=com.example.habits",
"https://apps.apple.com/us/app/example-habits/id1000000001",
"https://chromewebstore.google.com/detail/example-notes/abcdefghijklmnopabcdefghijklmnop"
]
}

Run it after Google Play Scraper or any app scraper

Open the source Actor's Integrations tab, add this Actor (datagleaner/app-developer-email-finder) and set its input to:

{"datasetId": "{{resource.defaultDatasetId}}"}

Every time the source run succeeds, this Actor reads the apps from its results: the store URL (url, appUrl or trackViewUrl, such as play.google.com/store/apps/details?id=... or apps.apple.com/.../id123) or the app ID (appId, packageName, trackId or id), the first one present. Items with neither, and duplicates, are skipped, and the developer contacts of each app are looked up (at most maxDatasetItems, default 1000). Apps from the dataset are added to any apps and searchKeywords you also give. Billing is the same: $0.0015 for each app whose developer has a public email, nothing for apps without one. Works with Google Play Scraper (datagleaner/google-play-scraper), Apple App Store scrapers and any Actor whose output has an app URL or ID.

The same works from code, for one finished run:

run = client.actor("datagleaner/app-developer-email-finder").call(run_input={"datasetId": "SOURCE_DATASET_ID"})

The status message tells how many items were read from the dataset, how many apps were found and how many items were skipped, or says so if the dataset could not be read. It also works as an integration: open the source Actor's Integrations tab, choose Add integration and pick this Actor, and the dataset is passed automatically.

Output

One row per app. Fields the store does not publish are null, never invented.

{
"store": "appStore",
"appId": "1000000001",
"appName": "Example Habits - Daily Tracker",
"appUrl": "https://apps.apple.com/us/app/id570060128",
"developerName": "Example Apps Ltd",
"developerId": null,
"developerUrl": null,
"developerEmail": "support@example.com",
"developerWebsite": "https://www.example.com",
"developerAddress": null,
"developerPhone": null,
"traderName": "Example Apps Ltd",
"publisherName": null,
"privacyPolicyUrl": null,
"supportUrl": null,
"emails": [
{"email": "support@example.com", "source": "website", "foundOn": "https://www.example.com/contact"}
],
"socials": {"x": "https://x.com/exampleapps"},
"category": "Education",
"installs": null,
"rating": 4.7,
"ratingCount": 1000000,
"lastUpdatedAt": "2026-10-20",
"releasedAt": "2012-11-13",
"price": 0,
"currency": "USD",
"hasEmail": true,
"pagesFollowed": 2,
"status": "ok",
"error": null,
"input": "https://apps.apple.com/us/app/example-habits/id1000000001",
"scrapedAt": "2026-11-02T10:00:00+00:00"
}

(Illustrative values: the email and counts here are placeholders, not a live result.)

A Google Play row carries developerEmail (for example support@example.com), the trader email, developerAddress, developerPhone, privacyPolicyUrl, installs and rating.

  • developerEmail is the best email: the store's own support email first, then the trader email, then one from the developer's site.
  • emails[].source is store, trader, website, supportPage or privacyPolicy; foundOn is the exact page.
  • installs is the lower bound of Google Play's install band (5000000 for "5M+") and the user count on the Chrome Web Store.
  • rating is a 0 to 5 star average.
  • An app that cannot be read gets a row with status: "error" and an error message, and is not charged.

The dataset has two views: Developer contacts (one row per app) and All emails (one row per email with where it was found).

Pricing

Pay per answer, one event:

  • app-with-email: $0.0015 for each app whose developer has at least one public email.
  • An app with no email is free. It is still returned with its website, address and store data, so you can see why.
  • An app that cannot be read (status: "error") is free.

Worked example. 1,000 Google Play apps, of which about 95% list a developer email: 950 x $0.0015 = $1.43. The 50 without an email cost nothing. Turn on onlyWithEmail to leave them out of the dataset; the price is the same.

Compared with other tools. App-developer contact tools on the Apify Store charge $0.0045 per row whether or not it has an email, or $0.02 to $0.05 per lead, and the popular Google Play scrapers charge $0.002 per app plus a start fee. Here a found email costs $0.0015, with four stores in one run, no start fee, and a miss costs nothing.

Set a maximum total charge on the run and the Actor stops cleanly when it is reached.

What to expect

Measured on a test run of "habit tracker" (62 apps, before the 2026-11-02 changes): 59 had a developer email (95%). Google Play 16 of 16, App Store 14 of 14, Chrome Web Store 16 of 16, Steam 13 of 16 (Steam is retired; App Store emails now come from the developer's website only, so expect fewer). Google Play lists a developer email for nearly every app. App Store emails come from the developer's website. A second check, "budget planner" on the App Store, found emails for 3 of 5 apps: apps sold only in the US carry no EU trader panel, so their email depends on the developer's website.

Limits

  • Google Play is looked up by app URL or package name only; keyword search there was retired on 2026-11-01 because its robots.txt disallows it.
  • App Store emails come only from an email on the developer's own site (Apple's app pages are no longer read, 2026-11-02); apps with none there have none.
  • Steam was retired on 2026-11-02 because the Steam Subscriber Agreement bars scripts and bots. Steam URLs, steam: IDs and the steam store give one free note row. The iTunes API is paced.
  • Developer websites that render entirely with JavaScript may show fewer emails.
  • Only public store listings and the developer's own pages are read; social platforms are listed, never scraped.

Use it from n8n, Make, Zapier or an AI agent

Actor ID: datagleaner/app-developer-email-finder

Minimal input:

{"apps": ["https://play.google.com/store/apps/details?id=com.example.habits", "https://apps.apple.com/us/app/example-habits/id1000000001", "https://chromewebstore.google.com/detail/example-notes/abcdefghijklmnopabcdefghijklmnop"]}

Each tool below runs this Actor with your own Apify API token.

  • n8n: add the Apify node (@apify/n8n-nodes-apify). On n8n Cloud you install it from the community node registry. Choose Run an Actor and get dataset, set Actor to datagleaner/app-developer-email-finder and paste the input above.

  • Make: use the Apify app's Run an Actor module, then Get Dataset Items to read the results. Watch Actor Runs can trigger a scenario when a run finishes.

  • Zapier: use the Apify action Run Actor, then the search Fetch dataset items. The trigger Finished Actor run starts a Zap when a run ends.

  • AI agents (MCP): connect to https://mcp.apify.com?tools=datagleaner/app-developer-email-finder. Without a token, an agent can still find Actors with the search-actors tool, but running this one needs your Apify account. In Claude Code:

      claude mcp add --transport http apify "https://mcp.apify.com?tools=datagleaner/app-developer-email-finder"
    

    Then run /mcp to sign in to Apify in your browser. Then ask in plain language, for example: "Find 30 meditation apps on Google Play and the App Store and give me each developer's email, website and address, only for apps with more than 100,000 installs."

  • LangChain (Python):

# pip install langchain-apify, then set APIFY_TOKEN in your environment
import json
from langchain_apify import ApifyActorsTool
tool = ApifyActorsTool("datagleaner/app-developer-email-finder")
result = tool.invoke({"run_input": json.loads('{"apps": ["https://play.google.com/store/apps/details?id=com.example.habits", "https://apps.apple.com/us/app/example-habits/id1000000001", "https://chromewebstore.google.com/detail/example-notes/abcdefghijklmnopabcdefghijklmnop"]}')})

Claude Desktop and other clients that take an mcpServers config can run the Apify MCP server locally:

{
"mcpServers": {
"actors-mcp-server": {
"command": "npx",
"args": ["-y", "@apify/actors-mcp-server"],
"env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
}
}
}

FAQ

How do I find an app developer's email? Paste the app's store link into apps (or search a keyword in the App Store), run it, and read developerEmail. Every store link format above is accepted.

Do I need a Google Play, Apple or Chrome Web Store account or API key? No.

Where does the App Store email come from? The Actor reads Apple's iTunes API for the developer's website, then looks for an email on that site. It no longer reads apps.apple.com pages.

Is the address the developer's office? It is the address the developer declared to the store as a trader. Individual developers sometimes give a home address; treat it with care.

Can I search Google Play or the Chrome Web Store by keyword? No. Both were retired on 2026-11-01 because their robots.txt files disallow search pages. Use package names, extension IDs or store links in apps, or search the App Store by keyword.

  • Website Contact Details Scraper: emails, phones and social profiles from the developer websites in your results, one row per site.
  • Team Page Contacts: named people, titles and LinkedIn profiles from a developer company's team page, when you need a person rather than a support inbox.
  • Company Enrichment by Domain: a company profile (name, logo, description, official social profiles, contacts) for each developer domain.

Purpose limit

Use the results only for your own lawful B2B or legitimate-interest purposes in the recipient's country. Do not resell bulk lists, and do not send cold outreach where the law or the recipient's objection forbids it. You are the controller of whatever you do with the data. Personal-looking email addresses (free-mail such as gmail.com, or first.last@ style) are not returned, role and company addresses such as support@ are. If a developer's own Impressum or privacy page objects to advertising ("Widerspruch gegen Werbung", "unsolicited advertising"), that site's emails are withheld and the row says why in privacyNotice. Rows from which an address was dropped carry the same privacyNotice.

Removal requests

If you are a developer or an individual named in these results and do not want this Actor to return your email, domain or name, email datagleaner@gmail.com (Keencrest, the publisher; replies come from an AI agent, Crest, and the business is owner-operated) with the address, domain or name. We add it to a blocklist (src/optout_dids.txt, loaded at the start of every run) within 30 days, usually much sooner, answer you, and keep a dated record of the request and our answer. Developers on the blocklist get no contact data in any row.

Responsible use

This Actor reads public store listings and the developer's own public pages only. Email addresses, phone numbers and addresses, especially those of individual developers, can be personal data. You are responsible for lawful use, including consent and opt-out rules for outreach (GDPR, CAN-SPAM and local law), and for respecting the stores' terms.