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 Instagram 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.
Meta, the operator of Instagram, is not the provider of this module. Meta processes the data in your Instagram account under its own responsibility and its privacy policy.
2. What data the module processes
The module only works with Instagram professional accounts (Business or Creator). You sign in with Instagram for this ("Instagram Login").
Permissions the module requests from Instagram when connecting:
instagram_business_basic: read the profile and posts of your account;instagram_business_content_publish: publish images, reels and carousels;instagram_business_manage_comments: read, answer and hide comments and @mentions;instagram_business_manage_insights: read statistics on your account and posts;instagram_business_manage_messages: read and answer direct messages.
We only receive data that you allowed Instagram to give us access to when connecting:
- when connecting, the identifier, username, name and type of your account and the list of granted permissions;
- your profile with username, name, profile picture, number of followers, of accounts followed and of posts, biography and website, and your publishing quota;
- your posts with identifier, type, caption, link, time, number of likes and comments and the addresses of the images and videos;
- comments on your posts with text, username and identifier of the person who commented, time, number of likes, whether it is hidden, and the replies to it;
- @mentions of your account in comments, and posts by other accounts in which your account is tagged, each with text or caption, username of the other account, link and time;
- direct messages: the list of your conversations with the participants (identifier, username) and, per conversation, the up to 20 most recent messages with sender, recipient, time, text and attachments (address, name and type of images, videos and files). These include private messages from other people to your account;
- statistics (insights) on your account and posts, such as reach, views, interactions, likes, comments, shares and saves, and followers gained and lost, as totals only.
The module does not delete posts or comments, does not publish stories, does not start conversations on its own and does not write to anyone who has not written to your account in the last 24 hours. The only exception: if you have set this in an auto-reply rule, it sends a person who commented under your post one private reply to that comment (Instagram allows this only once per comment and only within 7 days). It does not reach Facebook Pages.
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 on your behalf with the permissions you granted Instagram:
- reading: show the profile, posts, comments, mentions, conversations and statistics;
- writing: publish images, reels and carousels, answer, hide and unhide comments, reply to @mentions and answer direct messages with text or an image. The agent first shows every write as a preview; it is only carried out after confirmation (
confirm). The exception are auto-replies: once you create and confirm a rule ("comment or direct message containing keyword X → reply with text Y" or "→ reply along the lines of instruction Y"), the agent answers matching comments and direct messages without asking again and tells you afterwards. Before sending, the module itself checks against the text at Instagram whether the rule really applies; it replies at most once per comment or message, never to your own account, and for direct messages only within the 24-hour window. You can change, pause or delete rules at any time. Posts and replies to comments and mentions are public on Instagram. For images and videos, you or the agent provide an address; Instagram downloads the file from there itself. If the file is in the agent's workshop, the agent uploads it to us instead (Section 5).
Triggers: When connecting, the module subscribes your account to notifications from Instagram (webhooks) for three events:
- "New comment on my post" with the comment text, the person's username and identifier and the post's identifier. Comments by your own account trigger nothing;
- "Mentioned in a comment" with the identifiers of the post and the comment;
- "New direct message" with the identifier of the person who wrote (Instagram does not give a username here), the text and the attachments. Your own and unsent messages trigger nothing.
Meta sends these events to our server. We use them to start an agent if you have set one to the event. In an organisation, the organisation can block such triggers for the module.
4. Whom the data goes to
- to the module's service on our server;
- to Meta (Instagram), when an agent reads or writes;
- as a result or event 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 Instagram, when an agent publishes a post or replies to a comment or mention on your behalf, and to the person an agent sends a direct message to;
- to the servers behind the addresses of images and videos you have published: Instagram fetches the files there, not the module. Files from the workshop Instagram fetches from us;
- 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: Meta also processes data in the USA; Meta Platforms, Inc. is certified under the EU-US Data Privacy Framework (Art. 45 GDPR), and Meta Platforms Ireland Limited also uses standard contractual clauses for transfers from the EU (Art. 46 GDPR). For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the Instagram access token encrypted (AES-GCM) in our database, together with the identifier, username and type of your account, the granted permissions and the expiry date. Instagram issues the token for 60 days; we renew it in good time before it expires and store renewed tokens likewise. The module receives the credentials from our server with each call and does not store them itself.
- Files for publishing: If an agent uploads an image or video from its workshop, the module stores the file briefly on our server under a random, unguessable address for publishing, so that Instagram can fetch it there. We delete it as soon as Instagram has processed it, after one hour at the latest; files that were not completely uploaded are also deleted after one hour.
- Auto-reply rules: The module stores your rules (name, keywords, reply text or instruction, the post if any, the ID of the user who created the rule, timestamps) per Instagram account in a file on our server. They remain until you delete them; without a connection they have no effect. On request we delete them via support@nema.im.
- Answered comments and messages: So that no auto-reply appears twice, the module keeps, per Instagram account, the IDs of automatically answered comments and direct messages, the ID of the reply, the rule and the time, without text and without usernames, in a file on our server. We delete entries after 30 days.
- Content: Beyond that, the module does not store content from Instagram in a database or file. It fetches it anew with each request. 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).
- Caches: So that the same request is not published or sent twice, the module keeps a checksum of the request and the result (such as the identifier and link of the post or the identifiers of sent messages) in memory, for at most 1,000 requests. A restart of the module deletes them.
- Events: We keep events from Instagram encrypted (AES-GCM) in our queue until they are processed. After that we delete them after 7 days, and those that could not be processed after 30 days. During that time we also recognise duplicate deliveries.
- Transmission: The connection to Instagram and between your apps and our server is encrypted with TLS. We only accept events from Meta with a valid signature.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results and the events that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For events, the organisation can hide or replace individual fields with field masks, such as the username and identifier of the person who commented or wrote, and the text. 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 retrieves data from this Instagram account any more, and we no longer assign events from this account to anyone. If an Admin or Owner connected the account for an organisation, only the organisation can disconnect it.
- Revoking access at Instagram: In the Instagram app under Settings → "Apps and websites" you can withdraw Nema Crew's access at any time. The token stored with us 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 authorisation at Instagram and does not end the subscription to events. Both remain there until you withdraw access yourself. We therefore recommend doing both.
- What remains: Auto-reply rules and the IDs of answered comments and messages remain as described in Section 5. What an agent has taken over from Instagram into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Posts, replies and direct messages an agent published or sent stay on Instagram.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Accounts connected for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted token, 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 comment, mention your account or send you direct messages, Art. 6(1)(f) GDPR applies, limited to the task you give the agent. 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. Requirements of Meta
Deleting your data: This is how you have the data deleted that Nema Crew received through Instagram:
- Disconnect the module in Nema Crew (Modules → Instagram → Disconnect). We delete the credentials immediately.
- Remove Nema Crew in the Instagram app under Settings → "Apps and websites".
- If you also want content deleted that agents took over from Instagram, delete it in the app or write to support@nema.im. We will then delete it without undue delay. You have the right to deletion regardless of whether you have an account with us (Privacy Policy Section 18).
Sharing: We do not sell or license data we receive through the Instagram API. We only pass it on to the recipients in Section 4.
Questions about this module and about data protection: support@nema.im.
Documents
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.