Transparency Centre
Our services, and who helps us run them
Eurosky and mu are operated by Stichting Modal, a Dutch non-profit foundation (Kranenburgweg 135 A, 2583 ER The Hague, RSIN 868779465). This page lists the providers we currently use to run our services, what each one does, and where it processes data. The commitments are ours, and they are set out in our Privacy Policy: EU-headquartered hosting with EU data centres for our primary services, no advertising networks, no data brokers, no data sales. We choose providers that let us keep those commitments, and where a provider processes personal data on our behalf, it does so under a data processing agreement with us.
We update this page when providers change. Swapping a provider within the same category, under the same safeguards, is reflected here and in the change log below; changes that expand what we process or who receives it are announced in advance under §16 of the Privacy Policy.
Last updated: 19 August 2026.
Current providers
| Service | What it does | Provider | Location |
|---|---|---|---|
| Eurosky PDS hosting | Hosts your account, identity, and content | Hetzner Online GmbH | Germany (EU data centres) |
| Eurosky Portal hosting | Runs portal.eurosky.tech | Hetzner Online GmbH | Germany (EU data centres) |
| mu hosting | Runs mu's own servers and storage | Bunny.net (BunnyWay d.o.o.) | Slovenia (EU); origin and storage in EU data centres |
| Analytics (mu web) | Aggregate, cookie-free usage statistics | Plausible Insights OÜ (Plausible Cloud, hosted on Hetzner DE) | Estonia / Germany (EU) |
A note on Bunny's edge network. Bunny.net is an EU-headquartered company, and mu's servers and storage sit in EU data centres. Bunny also operates a global network of edge locations for fast content delivery. Requests are routed to the nearest edge, so users in the EU and EEA are served from European edge locations in normal operation. If you access mu from outside Europe, cached public content may be served from an edge location near you; an edge location sees only the standard technical data involved in serving a request (IP address, user agent, the file requested).
Bluesky Social, PBC (transition period)
mu runs on the AT Protocol and currently relies on infrastructure operated by Bluesky Social, PBC (United States) in several roles. We are in the process of replacing the first of these with our own infrastructure; this table reflects the current state and will be updated as the transition completes.
| Role | Status |
|---|---|
| Appview (content indexing and delivery) | Currently Bluesky's appview; our own appview is in testing and mu will switch to it |
| Search | Bluesky's search service; expected to continue for some time after the appview switch |
| Media delivery (CDN) | Bluesky's CDN; our own CDN may be used in combination later |
| Direct Messages | Bluesky's DM service (not end-to-end encrypted; see Privacy Policy §22.2) |
| Moderation labels | Bluesky's public labelling service, applied on mu as the baseline while our own moderation layer is introduced |
Mobile platform services (from the release of the mu apps)
| Role | Provider | Location |
|---|---|---|
| App distribution and payments | Apple App Store / Google Play | United States |
| Push notification delivery | Apple Push Notification service / Firebase Cloud Messaging | United States |
| Crash reporting and diagnostics | OS-provided opt-in diagnostics only (Apple / Google); no third-party crash processor | United States |
What we never do
No provider on this page receives data for advertising. We do not sell personal data, we do not profile anyone for advertising, and we do not share data with advertising networks or data brokers. The full commitments are in §7 of the Privacy Policy.
Policy change log
| Date | Document | Change |
|---|---|---|
| 19 Aug 2026 | Privacy Policy v1.1 | Published; takes effect 19 September 2026 (earlier on express acceptance). Mobile apps in scope; providers moved to this page; appview, search, and CDN transition disclosed; analytics restated as commitments; sign-in routes (OAuth and app password) disclosed; material changes defined in §16. |
| 19 Aug 2026 | Terms of Service v1.1 | Published alongside Privacy Policy v1.1; same transition framing, sign-in routes, mobile apps, and paid-features clause. |
| 16 Jul 2026 | Copyright Policy | Published at hello.mu.social/copyright. |
| 11 Jun 2026 | Terms of Service, Privacy Policy, Community Guidelines | First unified versions covering the Eurosky PDS, the Eurosky Portal, and mu. |
Archive
Previous versions of each policy remain available:
Questions?
If you have questions about our providers or data processing, get in touch.