Skip to content
New: the free AppMetis browser extension puts measured installs and chart places on every Google Play and App Store page →
AppMetis
DevelopersSalesPrivacy

Finding app developer contacts responsibly

What Google Play and the App Store publish about developers, the email rules that apply in the EU, US, Canada and India, and a routine for low-volume, respectful outreach.

AppMetis team Updated 11 Nov 2026 7 min read
Isometric puzzle pieces and code blocks snapping into the back of a phone
On this page

Developer contact details are published on Google Play and App Store listings, but published does not mean fair game. Use only what the stores show, check the email rules in each recipient's country, send a few relevant and personal messages with a clear opt-out, and remove anyone who asks at once. Outreach done this way respects the people behind the apps and tends to work far better than bulk email.

Key takeaways

  • Google Play shows a developer email on every listing and often a website, phone number and postal address. The App Store shows names and links, plus trader contact details in the EU.
  • Many developers are individuals, so their published details are personal data under laws such as the GDPR.
  • Email rules differ by market. EU countries vary, the US works on an opt-out basis, Canada requires consent and India has a new consent-based law.
  • Relevance, low volume and fast removal matter more than any template.
  • AppMetis shows contacts only as published on store listings, masks them on lower plans and offers a removal request flow.

What the stores publish

A developer directory built on store data can only be as complete, and as fair, as what the stores publish. Here is what each one shows, as of November 2026.

Google Play

Every Google Play listing has an app support section. An email address is required for every app, and many developers also list a website, a phone number and a postal address. For individual developers that address can be their home, so treat it with extra care and do not use it for unsolicited mail.

App Store

An App Store product page shows the developer name and, in the information section, the seller. It links to the developer's website, a support page and a privacy policy, but on most storefronts it shows no email address or phone number. To reach an iOS-only developer, look for a business contact on their own website.

EU trader details

The EU's Digital Services Act requires the stores to collect and show contact details for traders, meaning developers who distribute apps as a business. Both stores ask developers to declare their trader status, and traders' address, phone number and email are shown to users in the EU. Apple removed apps without trader status from its EU storefronts in February 2025. These details exist so consumers can reach a business, which is worth keeping in mind before you reuse them for sales.

This section is general information, not legal advice. The rules that apply depend on where the recipient is, not only where you are, so check with counsel before you run a campaign.

GDPR in the EU and the UK

  • A named person's email, phone number or address is personal data even when it is published. A solo developer's business email counts.
  • Legitimate interest can cover relevant business outreach, but only after a balancing test you can show: your purpose is legitimate, contacting this person is necessary for it, and their interests and reasonable expectations do not override yours.
  • When you collect data from a source other than the person, you must tell them who you are, what you hold, why you hold it and where it came from, at the latest in your first message.
  • People have an absolute right to object to direct marketing. Once someone objects, stop and add them to your suppression list.

Email rules in Europe

The EU's ePrivacy rules require prior consent for marketing email to individuals. For email to companies, each member state sets its own rules: some require consent for any marketing email, others allow it to corporate addresses as long as you identify yourself and offer an opt-out. Check the rules in the recipient's country. In the UK, PECR allows marketing email to corporate subscribers without prior consent but treats sole traders and some partnerships like individuals, which covers many independent developers.

CAN-SPAM in the US

The US uses an opt-out model, and it applies to business email too. Messages need honest header information and a subject line that is not deceptive, must be identifiable as advertising, must include a valid postal address and must offer a working opt-out that you honour within 10 business days.

CASL in Canada

Canada's anti-spam law requires consent, express or implied, for commercial email. Implied consent can come from conspicuous publication: the person published the address without saying they do not want unsolicited messages, and your message is relevant to their business role. Every message must identify you and include an unsubscribe option that takes effect within 10 business days.

India's DPDP Act 2023

India's Digital Personal Data Protection Act is built on consent and has no broad legitimate-interest basis. It does not apply to personal data that a person has made publicly available themselves. Whether a store listing counts, and which obligations are in force on the day you send, are questions for your counsel.

Good practice that keeps outreach welcome

  • Relevance. Contact a developer only when you can say in one sentence why your offer fits that app, for example because its SDK list shows a tool you replace.
  • Low volume. Send tens of messages a week, not thousands. If a list is too long to personalise, it is too long to send.
  • Personalisation. Mention the app, a recent version or a theme from its reviews. If you cannot write that line, skip the developer.
  • Clear opt-out. One plain sentence, such as "Reply no and I will not contact you again", plus a working unsubscribe link in any sequence.
  • Honour removals. Keep one suppression list across every tool and teammate, and keep it permanently.
  • Prefer role addresses. Use a partnerships or business address when one is published. An app's support address exists for its users, and sales pitches there are rarely welcome.
  • Never scrape personal social profiles or guess addresses from name patterns. If a developer did not publish it for business contact, leave it alone.
  • One contact per developer. A publisher with 40 apps should get one message, not 40.

What a good first message contains

Keep it short enough to read on a phone:

  1. Who you are and which company you work for, in one line.
  2. Why you are writing to this developer about this app, with one specific detail.
  3. What you offer and the one outcome it improves.
  4. A small next step, such as a reply or a short call, never a demand.
  5. Where you found their address, and a one-line way to opt out.

If any line feels generic, the message is not ready to send.

Keep the data clean

  • Record provenance. Store the source listing, the store and the date you saw each contact.
  • Refresh before you send. Re-check each contact against the live listing shortly before outreach, because developers change addresses and apps get removed.
  • Check deliverability gently. Validate syntax and domains, and drop bounced addresses at once rather than retrying them.
  • Deduplicate by developer, not by app.
  • Hold only what you use. Keep the fields you need, and limit who can export them.
  • Set a retention period. Delete leads you have not used after a fixed time, and keep only the suppression entry.

A worked example

Hypothetical example: you sell a crash-reporting SDK. A filter on SDK data finds 1,400 Android productivity apps that use a competing tool. After removing apps not updated in 12 months, developers already on your suppression list and developers with no business contact, 180 developers remain. You write to 30 a week. Each message names the app and a recent changelog line, says who you are and that you found the address on the app's store listing, and ends with a one-line opt-out. Replies and removals are logged the same day. For the targeting side, see our guide to finding SDK sales leads with app data.

How AppMetis handles contact data

The AppMetis developer directory shows contact details only as published on store listings, with city-level location. Contact fields are masked on lower plans, as shown on the pricing page. Developers can ask us to mask, correct or remove their details through the data removal page, and every request is handled with an audit trail. Our privacy policy explains what we hold and why.

Next steps

Before you build a list, write down the lawful basis and the opt-out wording for each country you plan to contact. Keep the first list short and send the first batch by hand, so you see every reply. If you are a developer and want your details changed in AppMetis, use the data removal page or write to [email protected].

Frequently asked questions

Is it legal to email an app developer whose address is on Google Play?

It depends on where the recipient is and how you use the address. The US allows commercial email with an opt-out, Canada can treat a conspicuously published address as implied consent for relevant messages, and EU countries set their own rules for business email, so check each market.

Do I need to tell developers where I got their email address?

Under the GDPR, yes. When you collect an address from a source other than the person, you should say who you are, what you hold and where it came from, at the latest in your first message, and it is good practice everywhere else.

Can I use an app's support link to pitch my product?

You can, but support channels exist for the app's users and pitches there tend to be ignored or resented. Look for a partnerships or business contact on the developer's website instead.

How do I get my details changed or removed from AppMetis?

Use the form at appmetis.com/data-removal or write to [email protected]. We can mask, correct or remove developer contact details, and we log every request.

How often should I refresh a developer contact list?

Re-check each contact against the live store listing shortly before you send, because addresses change and apps get removed. Delete leads you have not used after a fixed period and keep only the suppression list.

Related guides

All guides →

Also on the blog

Start with real numbers today

Free forever plan. No card needed. Upgrade when AppMetis earns it.