Chrome Extension Privacy Notice

1. What this notice covers

This notice explains what the Chrome extension “AppFoyer — Store Publishing Helper for Google Play & App Store” (the “extension”) does with data. The extension is published by AppFoyer, operated by Hasanaga Mammadov, Mahammad Hadi 58A M400, Baku AZ1123, Azerbaijan (the “Operator”, “we”).

It covers the extension only. The AppFoyer service itself — the dashboard at app.appfoyer.com, its API, the /mcp endpoint and the pages we host — is covered by our Privacy Policy. Where this notice says a request is handled “under the Privacy Policy”, that document applies to it.

2. Using the extension without connecting

The extension opens a side panel next to Google Play Console and App Store Connect and shows what each console page asks for. That reference information is packaged with the extension; showing it needs no network request.

Without an AppFoyer connection the extension collects nothing and sends nothing. The length counter under a field runs inside the panel: text you paste there is counted on your device, is not stored and is not sent anywhere.

3. “Follow my page” (optional)

If you click Follow my page, Chrome asks whether the extension may access play.google.com/console and appstoreconnect.apple.com. Only if you allow it, the panel reads the address of the active tab when that tab is on one of those two sites, so it can open the matching section of the panel.

• It never reads the content of a console page. The extension has no content script and never changes, clicks or submits anything in a console.
• It reads nothing on any other website.
• The address is not sent anywhere. If you are connected (section 5), the console’s identifier for your app, taken from that address, is kept on your device to remember which AppFoyer app goes with it.

Stop following removes the permission again; you can also remove it in Chrome’s extension settings.

4. What is kept on your device

The extension uses Chrome’s local extension storage (chrome.storage.local) on your device for:

• your panel choices: the store and the section you picked last, whether you dismissed the “Connect AppFoyer” card, the AppFoyer app you picked last, and which AppFoyer app you chose for each console app;
• when you are connected, the AppFoyer sign-in tokens (section 5).

None of this is sent to us or to anyone else, except that the sign-in tokens are sent to AppFoyer to authorise its own requests. Information the panel reads from your AppFoyer account is shown while the panel is open and is not written to this storage.

Disconnect deletes the sign-in tokens from your device and asks AppFoyer to revoke the connection. Removing the extension makes Chrome delete everything the extension stored on your device; it cannot tell AppFoyer, so the connection stays listed on the dashboard’s Agent page until you revoke it there; the tokens themselves stop working after 30 days without use.

5. “Connect AppFoyer” (optional)

If you have an AppFoyer account, you can connect it to see your own app’s values and store-form answers beside the console’s fields.

• Signing in. Clicking Connect AppFoyer opens AppFoyer’s own sign-in and consent page in a Chrome window. Signing in there is signing in to AppFoyer, under the Privacy Policy. The extension never sees your password; it receives sign-in tokens from AppFoyer.
• Read-only. The connection is granted the apps:read permission only. The extension can read your account; it cannot change anything in it.
• What it reads. The list of your apps, an app’s settings (such as its name, support email and page addresses, and whether those pages are published) and its store-form answers, all from app.appfoyer.com. It sends requests nowhere else.
• How those requests are handled. They are ordinary requests to the AppFoyer service, treated like any request from a connected agent: each one is recorded in your account’s audit log with the IP address, and they are covered by the Privacy Policy.
• Seeing and ending it. The connection appears on the dashboard’s Agent page, where you can revoke it at any time, and Disconnect in the panel ends it as well (section 4).

6. What the extension does not do

• It runs no analytics and no advertising, and it does not track your browsing.
• It does not read the content of any web page.
• We do not sell or transfer data from the extension to anyone, do not use it for any purpose other than the panel’s single purpose — showing what the store consoles ask for and, if you connect, your own app’s values — and do not use it to determine creditworthiness or for lending.
• It does not load or run code from the internet. All of its code is in the package Chrome installs; from AppFoyer it receives only data.

Links in the panel — to the stores’ help pages, or to AppFoyer — open in a normal browser tab, where the website you open handles your visit under its own policy. A Copy button puts a value on your clipboard only when you click it.

7. Changes to this notice

When the extension starts handling data differently, we update this notice before the new version is published. The effective date at the top of this page identifies the version; every version is preserved in the public change history of this website.

8. Contact

Questions about this notice or the extension: support@appfoyer.com.

---

Questions about this document: support@appfoyer.com. Previous versions are in the public change history of this site.