Provider
Leonardo Antonio Carta (Nema)Controller
c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Köln, Deutschland
This notice supplements the Privacy Policy for Nema Crew for the Google Play module. It does not repeat what the policy says for all modules. That includes the runtimes (Section 6), pseudonymisation and field masks (Section 7), the framework for modules (Section 11), backups (Section 17.6) and your rights (Section 18).
1. Provider and controller
This module is provided and operated by Leonardo Antonio Carta (sole proprietor), c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Cologne, Germany, support@nema.im. It runs as a separate service on our server in Germany. We are the controller. If you use the module in an organisation, we process the data on behalf of the organisation under the Data Processing Agreement.
Google is not the provider of this module. Google processes the data in your Google Play Console account and your Google Cloud project under its own responsibility and its privacy policy.
2. What data the module processes
Access: You connect the module with the JSON key of a service account that you create in your Google Cloud project and invite in the Play Console. Among other things, the key contains the service account's email address, the project ID and a private key. Optionally you enter the package names of your apps and two alert thresholds. With the key, the module signs in to Google and receives access tokens valid for one hour.
What data the service account can reach is determined by the permissions you give it in the Play Console under "Users and permissions". The module only uses the access described in Section 3. Grant only the permissions you need for your tasks; the module does not need financial data.
We receive, to the extent an agent or a trigger retrieves them:
- apps with package name and title, default language, contact details of the store listing (email address, website, phone, as you entered them in the Play Console) and title and descriptions of the store listing per language;
- tracks and releases with name, version codes, status, rollout share, release notes per language and, where set, country targeting;
- reviews with identifier, reviewer name, stars, review text (and, on request, a translation by Google), language, time, app version, Android version, device designation, number of thumbs up and down, and your reply. The Google API only returns reviews with text that were written or changed in the last seven days;
- app metrics (Android vitals) from the Play Developer Reporting API: daily crash rate and ANR rate (overall and user-perceived) and the number of users the rates refer to, on request per version code. These are aggregated values without reference to individual people.
The module does not retrieve purchases, subscriptions, orders, financial reports, tester lists or the users of your Play Console account. It neither uploads nor downloads app bundles (AAB, APK).
3. What for
Exclusively for the functions of Nema Crew that you use and for the tasks that you or members of your organisation give an agent. The agent acts with the permissions of the service account:
- reading: show and evaluate apps, store listings, tracks and releases, reviews and app metrics;
- writing, each time only after a preview and your approval: reply publicly to a review, change release notes, change the rollout share of a release, halt, resume or fully roll out a release, and take over a release into another track (for example from testing to production). Replies to reviews are public on Google Play; whether Google notifies the reviewer is governed by Google.
Triggers: If an agent listens to them, Nema Crew regularly checks through the Google APIs:
- "New review" every 30 minutes, whether there are new or changed reviews with text;
- "Release status changed" every 30 minutes, whether the status or rollout share of a release has changed;
- "Vitals alert" every 3 hours, whether the latest daily user-perceived crash or ANR rate is above your threshold.
Each event starts the agent once and shows a card with a short summary in the channel.
4. Whom the data goes to
- to the module's service on our server;
- to Google, when the module signs in, reads data or carries out a change (Google Play Android Developer API, Google Play Developer Reporting API, Google's sign-in service). The calls run through your Google Cloud project; what Google records there about the use of the APIs is governed by your contract with Google;
- as a result to the language model of the runtime you chose, to the extent an agent needs the data for the task (Privacy Policy Section 6). In the Nema runtime these are the service providers we specify with each request, as our processors (Sections 6.1, 15 and 16). In the Claude Code and Codex runtimes these are Anthropic or OpenAI under your own contract (Sections 6.2 to 6.4);
- to the public on Google Play, when an agent replies to a review on your behalf;
- to other members and agents in the channel in which an agent uses the data;
- to Apple's or Google's push service, to the extent the data is in the first 180 characters of a message we send you as a notification (Section 12);
- to the data centre operator on whose hardware our server runs and where our backups are kept, as our processor (Sections 17.6 and 20);
- to authorities only if we are legally obliged to.
The module uses no further service providers.
Countries outside the EU: Google processes the data in the Play Console and in Google Cloud under your contract with Google. Google also processes data in the USA; Google LLC is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the JSON key, the package names and the thresholds encrypted (AES-GCM) in our database. The module receives them from our server with each call and does not store them itself. It uses the private key only to obtain an access token from Google; it keeps this token in memory for at most one hour. The module writes neither key nor token to any log.
- Content: The module does not store content from Google Play. It fetches it anew with each request and keeps it in memory only while the request runs. What an agent makes of it, meaning responses, memories, knowledge entries, the steps of its run and the card for an event that triggered it, we store like other content (Privacy Policy Sections 4 and 5).
- Triggers: So that a trigger only reports what is new, we remember per connection and app the time of the newest review seen, track, version codes, status and rollout share of the releases and the date of the metrics last checked. So that the same event starts an agent only once, we also store identifiers of reported events (for reviews the review identifier and the time) for 30 days. We do not store review texts or names for this.
- Transmission: The connection to Google and between your apps and our server is encrypted with TLS.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results and events that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For events, it can hide or replace individual fields with field masks, such as the reviewer's name. Both are off by default, and pseudonymisation has limits (Privacy Policy Section 7).
6. Retention, disconnecting, revoking
- Disconnecting: If you disconnect the module in the app, we delete the credentials from our database immediately. After that, no agent and no trigger retrieves data with this key any more. The module is only connected personally, not for a whole organisation.
- Revoking at Google: In the Google Cloud Console under IAM & Admin → Service accounts → Keys you can delete the key at any time; it becomes invalid immediately. In the Play Console under Users and permissions you can remove the service account's permissions. Disconnecting in the app does not delete the key at Google. It remains valid there until you delete it yourself. We therefore recommend doing both.
- What remains: What an agent has taken over from Google Play into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Replies to reviews and changes to releases that an agent carried out remain on Google Play.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5).
- Backups: The data, including the encrypted credentials, remains in our backups for up to about 6 months (Privacy Policy Section 17.6).
7. Legal basis
Art. 6(1)(b) GDPR, because the module carries out the connection you set up. For third parties' data, such as reviewers' names and texts, Art. 6(1)(f) GDPR applies, limited to the task you give the agent and the triggers you switch on. In organisations we process on their behalf (Privacy Policy Section 2). Your confirmation of this notice is not consent. To end the processing, disconnect the module.
8. Google's requirements
The use of the Google Play APIs is governed by the terms you agreed with Google, in particular the Google APIs Terms of Service for your Cloud project and your Play Console agreement. Replies to reviews are subject to Google Play's policies.
Documents
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.