Privacy Policy for Our Social Media Tools
This is a convenience translation. Only the German version is legally binding: Deutsche Fassung
contentforge (content.dynaforge.ai) and postiz (postiz.dynaforge.ai) · As of: October 17, 2026
You can find the privacy policy for the website dynaforge.ai in theLegal Notice & Privacy. Terms of use: Terms of Use for the Social Media Tools.
1. Controller and roles
SIS Automation GmbH, Alfred-Nobel-Allee 42, 66793 Saarwellingen, Germany
Represented by the Managing Director Daniel Müller · Amtsgericht Saarbrücken (Local Court of Saarbrücken), HRB 64387
Email: Show email address
Legal notice: dynaforge.ai/en/legal-notice.html
“Dynaforge” is a trademark of SIS Automation GmbH. No data protection officer has been appointed because there is no legal obligation to do so.
For personal data of third parties (creators, commenters) in the workspace of an invited co-user, the respective co-user is the controller; SIS Automation GmbH processes this data as a processor (Art. 28 GDPR) on their instructions. In all other cases, SIS Automation GmbH is the controller.
2. Purpose and functions
contentforge is a tool of SIS Automation GmbH with which a personally invited group of users plans, approves and publishes posts for their own social media accounts. In addition, publicly visible posts by other creators can be analyzed as a template for your own content and comments under your own posts can be managed. Publishing takes place via the self-operated service postiz. Access is only possible after invitation and login; there is no public offering, no tracking and no advertising.
Currently not active are the Apify integration, the Meta Ad Library, cloud AI services, image generation and the embedding of C2PA provenance information. Before any activation, this policy will be supplemented.
3. Data subjects, data and sources
- Invited users: Email address, name, login ID, role per workspace; login and MFA data in the self-operated login service (Authentik). Source: you yourself.
- Connected accounts: Channel names (handles) and access keys (tokens) of the platforms. Source: you yourself, through logging in to the respective platform.
- Own posts: Text preview of published posts (at most 200 characters), link, status, uploaded media, and metrics (insights) of your posts that the platform provides through its interface.
- Creators whose public posts are analyzed: Title, description text (caption), handle, public metrics and, where applicable, transcripts of publicly visible posts. Source: the platform or the public address of the post that a user enters. No profiling or evaluation of individuals takes place.
- Commenters under own posts: Name or handle and text of the comment. Source: the platform through its interface. These may contain information that allows conclusions about special categories of personal data (Art. 9 GDPR, e.g. political opinions); we do not collect this deliberately.
- Advertisers: The Meta Ad Library is currently not connected.
- Logs: Audit entries (action, user ID, IP address, time) and server logs (see section 11).
4. Legal bases
Art. 6(1)(f) GDPR (legitimate interest); for user accounts additionally Art. 6(1)(b) GDPR (terms of use agreement). Our interest is to plan, publish and improve our own posts and to reply to comments under our own posts. For third parties, we process only data that they have made public themselves, on a small scale and without republication. We delete third-party media immediately after analysis, transcripts after 30 days at the latest. Since you can object at any time (section 5), your interests, in our assessment, do not override ours.
5. Information pursuant to Art. 14 GDPR
We do not receive data of creators and commenters from you, but from the platform or from publicly accessible sources (source and categories see section 3). Individually notifying all affected persons would require a disproportionate effort because we do not collect their contact details; we therefore provide the information on this publicly accessible page (Art. 14(5)(b) GDPR).
6. Browser extension
Invited users can optionally use a browser extension with their own account. Whether they do so is the user's own decision. The extension serves only the respective user for their own account.
7. Recipients and third countries
- postiz: self-operated on our servers, no external service provider.
- Platforms: Social networks receive, through their official interfaces, the posts, replies and media that a user publishes on their own account. The platforms process data under their own responsibility in accordance with their own privacy terms; some are based in the USA (overview in section 13).
- AI: Drafts and analyses run on local models on our own servers. Cloud AI services are currently not active; before any activation, this policy will be supplemented.
The system itself is operated on SIS Automation GmbH's own infrastructure. A transfer to third countries takes place through publication on the platforms named, not through our own systems.
8. Joint controllership with Meta (page statistics)
For statistics (page insights) on Facebook pages and Instagram and Threads accounts that we retrieve through Meta's interfaces, there is joint controllership with Meta Platforms Ireland Ltd. pursuant to Art. 26 GDPR. You can find Meta's terms in thePage Controller Addendum.
9. Security
Access is only possible after login through our login service with multi-factor authentication. contentforge stores the platforms' access keys in encrypted form (AES-256-GCM). postiz stores the access keys of the connected accounts in its own database on our server; access is only possible internally.
10. Cookies
We use only technically necessary cookies on the basis of § 25(2) No. 2 TDDDG (German Telecommunications Digital Services Data Protection Act):cf.sid (session in contentforge, only after login) andauthentik_proxy_* (session of the login service for postiz, 12 hours). Before login, no cookies are set on the public pages. There is no tracking and no advertising.
11. Server logs
When the service is accessed, the IP address, time, requested address and browser identifier are logged to secure operation. The web server log is deleted after 7 days, the access logs of the reverse proxy after 4 weeks, its error logs after approx. 10 weeks.
12. Retention periods
| Data | Period |
|---|---|
| Third-party media for analysis | immediately after the analysis |
| Transcripts | 30 days |
| Comments | 90 days after processing; unprocessed 12 months; comments deleted on the platform are generally removed by us within 24 hours of deletion (daily reconciliation; except LinkedIn, whose comments reach us only via the browser extension and are not reconciled) |
| Metrics (insights) | 24 months |
| Audit entries (with IP address) | 12 months |
Published posts for listing (listed) | 12 months |
| Evaluated third-party posts (title, caption, handle) | 12 months after last use (posts that are in a collection are not anonymized as long as they remain in it); afterwards we delete title, link, caption and the assignment to the creator (the handle is replaced by “[Creator]”), leaving an anonymous structure card with no personal reference. Deletion on request at any time |
| Server logs | see section 11 |
| User account, post previews, style profile | until deletion of the account or workspace; backup copies upon expiry of their rotation period |
13. Platforms
We publish only on accounts that a user has connected themselves. You can revoke access at any time in the settings of the respective platform (section 17) or ask us to disconnect.
Google / YouTube
When a YouTube channel is connected, we use the YouTube API Services. TheYouTube Terms of Serviceand the Google Privacy Policy apply. You can revoke access at any time atmyaccount.google.com/permissions.
The use and transfer of information received from Google APIs is carried out in accordance with theGoogle API Services User Data Policy, including the Limited Use requirements.
Meta (Facebook pages, Instagram, Threads)
The provider is Meta Platforms Ireland Ltd.; privacy information atfacebook.com/privacy/policy. For joint controllership for page statistics, see section 8.
X
Posts are published on the connected X account. Data processing by X takes place under its own responsibility in accordance with x.com/privacy.
TikTok
Posts are published on the connected TikTok account. Data processing by TikTok takes place under its own responsibility in accordance with tiktok.com/legal.
Posts are published on the connected LinkedIn account. Data processing by LinkedIn takes place under its own responsibility in accordance with linkedin.com/legal/privacy-policy.
Twitch
Connecting a Twitch channel is done voluntarily by the user. Data processing by Twitch takes place under its own responsibility in accordance with twitch.tv/p/legal/privacy-notice.
Bluesky, Mastodon, Pinterest, Reddit, Discord
Posts are published on the account or channel connected by the user. The respective operators (for Mastodon, the respective instance) process data under their own responsibility in accordance with their privacy terms; some are based in the USA.
WhatsApp is currently not connected.
14. Public media
Media intended for publication on a platform are stored by postiz atpostiz.dynaforge.ai/uploads. This path is publicly accessible via link (read access only) so that the platforms can retrieve the files. Upload only media there that you are permitted to publish.
15. AI labeling
Drafts created by AI are marked in the system with a flag (ai_generated). When publishing on X, the “made with AI” flag is set if an AI image is included; on TikTok, the platform's AI-content label is set. A visible label in the text is possible depending on the workspace setting. Users are responsible for labeling their content themselves (seeTerms of Use).
16. Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR), as well as the right to withdraw consent given (Art. 7(3) GDPR). Send requests to the contact address in section 1. You can also lodge a complaint with a data protection supervisory authority, for example the Unabhängiges Datenschutzzentrum Saarland (Independent Data Protection Center of Saarland), Fritz-Dobisch-Str. 12, 66111 Saarbrücken. The objection as a creator or commenter is described in section 5.
17. Data deletion
Here is how to have your data deleted or revoke access:
- Via Facebook or Instagram (automatic): Remove the app in your Facebook settings under “Apps and Websites” and request deletion of your data. Meta then calls our deletion interface. We automatically delete the stored access keys, comments and metrics of the connections you established and disconnect the channel in our publishing tool. Meta shows you a confirmation code and the link to a status page on which you can see completion. Connections established before October 17, 2026 cannot be assigned by us in this way; please have these disconnected via item 2.
- Have a channel disconnected: Send an email to the contact address in section 1 with the name of your account or channel and the platform. Invited users can also disconnect the connection themselves in the application. Upon your request, we delete the stored access keys and the associated data.
- Remove access in the platform: Revoke the app's access in the platform's settings:
- Facebook: facebook.com/settings?tab=business_tools
- Instagram: instagram.com/accounts/manage_access
- Google / YouTube: myaccount.google.com/permissions
- X: x.com/settings/connected_apps
- Other platforms: in the account settings under connected apps or applications.
- Data as a creator or commenter: An email with your handle is sufficient; we delete all data stored about you (creator entry, evaluated posts with cards, collection entries, comments) and block your handle so that it is not added again. You will receive a deletion confirmation.
We process your request without undue delay, at the latest within one month of receipt (Art. 12(3) GDPR). Comments that you delete on the platform are generally removed by us within 24 hours (except on LinkedIn) from our records (daily reconciliation). Backup copies are deleted upon expiry of their rotation period. Content that you have already published on a platform must be deleted by you there.
18. Status
As of: October 17, 2026. We will adapt this policy when functions or the legal situation change. Legal notice: dynaforge.ai/en/legal-notice.html.