What we collect, and what we do not
Short version: the website tracks nothing, and we hold no personal data about the people who read our posts. The detail is below.
Last updated 29 August 2026
1. Who we are
MLOps MENA Community is an educational community and a services business. We publish free MLOps and AI learning for engineers across the Middle East and North Africa, and we provide paid training, talent outsourcing, software delivery and consultation to companies.
- Website: https://mlopsmena.com
- Contact: hello@mlopsmena.com
- Data protection enquiries: hello@mlopsmena.com
2. What this policy covers
This policy covers two things:
- mlopsmena.com — our public website.
- MLOps MENA Studio (studio.mlopsmena.com) — an internal tool used only by our core team to plan, review and publish the community’s own social media content, and to read how that content performed on our own accounts.
It does not cover the platforms we publish to. When you interact with our posts on LinkedIn, X, YouTube, Facebook, WhatsApp, Discord or Medium, that platform’s own privacy policy governs your data, not this one.
3. What we collect
The public website sets no tracking cookies, runs no advertising network, and builds no profile of visitors. It is a set of static pages.
For core-team members who use Studio — who authenticate through Cloudflare Access before reaching it — we store their name, email address, community team, their role in the tool, and a timestamped record of the actions they take: content created, edited, reviewed, approved, scheduled, published or deleted.
Where we connect our own community accounts to Studio, we store that account’s identifier and name, OAuth tokens for it, and aggregate performance figures for our own posts — impressions, views, reactions, comments, shares, clicks, follower counts and watch time.
We do not collect, request or store personal data about the people who follow, view, like or comment on our content. We read only the aggregate figures a platform reports for our own account. We do not build audience profiles, and we do not sell or share platform data with anyone.
4. How we use it
- To plan, review and schedule the community’s own educational content.
- To enforce an internal approval process, so nothing is published without being checked.
- To keep a record of who approved and published what.
- To understand, in aggregate, which of our educational content is useful.
We do not use any of it for advertising, profiling, automated decision-making about individuals, or resale.
5. Account credentials
- We never ask for, collect or store passwords for any social platform.
- Connections are made through each platform’s official OAuth flow.
- We request the minimum permissions needed to publish our own content and read our own analytics, and nothing more.
- Tokens are encrypted at rest with AES-256-GCM. The encryption key is held separately from the database, so a copy of the database alone cannot be used to reach any account.
- Tokens are never shown in the application, never returned by our API, never written to logs, and never included in data exports.
- Disconnecting an account deletes its stored tokens immediately.
6. Where data is stored
Studio runs on Cloudflare’s infrastructure. Data may be processed in data centres outside your country of residence. Cloudflare acts as our processor.
7. How long we keep it
| Data | Retained for |
|---|---|
| Content, approvals and publication history | Indefinitely — it is the record of what the community published |
| Aggregate performance data | Indefinitely — non-personal, and its value is the long-term trend |
| Raw responses from platform APIs | 12 months, then deleted |
| Internal audit logs | 7 years |
| OAuth tokens | Until the account is disconnected, then deleted immediately |
| Core-team member accounts | While they are on the team. On departure the account is disabled and personal details removed, though their authorship of past content is preserved |
8. Your rights
If you are somewhere that grants data protection rights — including the EU and UK under GDPR, and Egypt under the Personal Data Protection Law — you may ask us for access to, correction of, or deletion of personal data we hold about you, object to how we process it, or ask for a copy in a portable format.
Write to hello@mlopsmena.com. We will respond within 30 days.
Because we hold almost no personal data about people outside our core team, the honest answer to most access requests will be that we hold nothing about you. If you want data removed from a platform where you interacted with our content, that request goes to the platform.
9. Third parties
We publish to, and read our own analytics from: LinkedIn, X, YouTube, Facebook, WhatsApp, Discord and Medium. Each has its own privacy policy, and your relationship with them is not governed by this one.
We use Cloudflare for hosting, security and access control, and Google Forms for referral submissions made by core-team members.
10. Security
- Studio is not publicly reachable. Access is enforced at Cloudflare’s edge, before a request reaches the application.
- All traffic is served over HTTPS.
- Credentials are encrypted at rest, with keys stored separately.
- Access within the tool is role-based and least-privilege.
- Security-relevant actions are logged.
- Access to community platform accounts is reviewed periodically and revoked when someone leaves the team.
11. Children
Our content is aimed at working engineers and students in higher education. We do not knowingly collect personal data from anyone under 16.
12. Changes to this policy
We will update this page when our practices change, and change the date above. Where a change materially affects how we handle personal data, we will say so in our community channels.
13. Contact
Questions or requests: hello@mlopsmena.com