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 App Store Connect 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.
Apple is not the provider of this module. Apple processes the data in your App Store Connect account under its own responsibility and its privacy policy.
2. What data the module processes
Access: You connect the module with an API key that you create in App Store Connect: issuer ID, key ID and the private key (content of the .p8 file). The module uses it to sign in to Apple (an access token valid for at most 15 minutes and reused for up to 10 minutes). If an agent sets up webhooks at your request, the module creates a random webhook secret, stores it with your credentials and gives it to Apple so that Apple signs every delivery.
What data the key can reach is determined by its role, which you set in App Store Connect, such as Customer Support, App Manager or Admin. The module only uses the access described in Section 3. Choose the role with the fewest rights that is sufficient for your tasks.
We receive, to the extent an agent retrieves them or a trigger delivers them:
- App Store reviews with identifier, stars, title, review text, nickname of the reviewer, country and time, and your response (text, state, time). Nicknames are often real names or allow conclusions about the person; review texts may contain further personal details;
- public rating figures (average and count per country) from Apple's public iTunes search, without personal data;
- apps with identifier, name, bundle ID, SKU and primary language and, on request, the app information (state, age rating, categories and per language name, subtitle and privacy links);
- versions, submissions and builds with identifier, version number, platform, status, release type, "What's New" and promotional text per language, review and phased release state, build number, minimum operating system and the times of upload, creation and expiry;
- TestFlight testers with identifier, first name, last name, email address, invitation type and status;
- TestFlight groups with identifier, name, whether it is an internal group, public invitation link (if switched on) and time of creation;
- TestFlight feedback with identifier, time, comment, tester's email address, device model, operating system, language, connection type, battery level, app uptime, links to the screenshots and, for crashes on request, the crash log;
- performance diagnostics per build (disk writes, hangs, launch time) with weight and call stacks. Apple aggregates them from devices whose users share analytics; they do not name people;
- webhook events: event type, identifiers, old and new state, time. They contain no personal data;
- signing certificates with identifier, name, display name, type, platform, serial number and expiry date. Name and display name often contain the name of the person or team the certificate was issued to;
- registered devices with identifier, device name, platform, device identifier (UDID), device class, model, status and time of registration. Device names often contain the name of the person who owns the device;
- bundle IDs with identifier, identifier string, name, platform and team prefix, and provisioning profiles with identifier, name, type, status, platform, expiry date and UUID.
The module does not retrieve sales and finance reports, analytics reports or the users of your App Store Connect team.
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 rights of the API key:
- reading: show, filter and summarise the data in Section 2, for example reviews by stars and countries or the state of a review;
- writing (always as a preview first, carried out only after you agree): publicly answer a review, replace or delete an answer; create versions, write "What's New" and promotional text, attach builds, submit for review, withdraw submissions, release versions and control the phased release; invite or remove TestFlight testers, share builds with groups, write "What to Test" and submit builds for beta review; create, change, test and delete webhooks at Apple.
Triggers:
- New review: Every 30 minutes our server fetches the latest reviews of your apps (or of the apps under "Watched apps"). Each new review starts the agents that use this trigger. To avoid duplicates we store per app the time of the last check and shortened checksums of the most recently reported reviews, and the identifiers of reported reviews for 14 days.
- Webhooks: If you had them set up, Apple reports state changes of versions and builds, beta review results and new TestFlight feedback immediately to your personal address at Nema. We check the signature with the webhook secret and start the agents that use these triggers.
4. Whom the data goes to
- to the module's service on our server;
- to Apple, when an agent reads or changes data, with every check for new reviews and when webhooks are set up (including the webhook secret and your personal webhook address);
- 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 everyone visiting the App Store, when an agent answers a review on your behalf: answers are public, and Apple may notify the reviewer;
- to people whom an agent adds as TestFlight testers on your behalf or for whom it shares a build. What they receive is governed by Apple;
- to other members and agents in the channel in which an agent uses the data or a trigger shows an event card;
- 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: Apple processes the data in App Store Connect under your developer agreement with Apple. Apple generally stores data with Apple Inc. in the USA on the basis of standard contractual clauses (Art. 46 GDPR); Apple is not certified under the EU-US Data Privacy Framework. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the issuer ID, key ID, private key and webhook secret encrypted (AES-GCM) in our database. The module receives them from our server with each call and does not store them itself; it only keeps the short-lived access token in memory for up to 10 minutes. Key and secret never appear in logs or responses.
- Content: The module does not store content from App Store Connect. It fetches it anew with each request. What a trigger delivers (such as a new review with text and nickname) and what an agent makes of it, meaning event cards, responses, memories, knowledge entries and the steps of its run, we store like other content (Privacy Policy Sections 4 and 5).
- Trigger state: times and shortened checksums of review identifiers (Section 3), without texts or names.
- Transmission: The connection to Apple, Apple's deliveries to us and the connection between your apps and our server are encrypted with TLS.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results go to the language model pseudonymised, unless the organisation has switched this off for the module. This is off by default, and pseudonymisation has limits (Privacy Policy Section 7). The "New review" trigger has field masks; the reviewer's nickname is suggested for pseudonymisation.
6. Retention, disconnecting, revoking
- Disconnecting: If you disconnect the module in the app, we delete the credentials including the webhook secret from our database immediately, and your personal webhook address becomes invalid. After that, no agent retrieves data with this key any more. The module is only connected personally, not for a whole organisation.
- Webhooks at Apple: Disconnecting does not delete the webhooks at Apple. Ask an agent to remove them beforehand, or delete them in App Store Connect under Users and Access → Integrations → Webhooks. If they remain, Nema rejects deliveries to the invalid address.
- Revoking at Apple: In App Store Connect under Users and Access → Integrations → App Store Connect API you can revoke the key at any time. It then becomes invalid. We remove it from our database when you disconnect in the app or delete your account. Disconnecting in the app does not revoke the key at Apple. It remains valid there until you revoke it yourself. We therefore recommend doing both.
- What remains: What an agent has taken over from App Store Connect into messages, memories or knowledge entries, and the event cards of triggers, remain stored after disconnecting until you delete them (Privacy Policy Section 17.1). Answers to reviews remain on the App Store, testers in TestFlight and changes to versions in App Store Connect until you change them there. Remembered identifiers of reported reviews are deleted after 14 days.
- Deleting your account: With your account we immediately delete your credentials, the trigger state and your 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 people who review your apps, TestFlight testers and people named in certificate and device names, Art. 6(1)(f) GDPR applies, limited to the task you give the agent and to the legitimate interest in answering feedback on your apps and maintaining your apps. 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. Provider requirements
Answers to reviews must follow Apple's rules (App Store Review Guidelines and Apple Developer Program License Agreement). They are public; the agent does not put personal data into them.
Documents
- This notice
- Data Processing Agreement
- Apple Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.