Updated 20 November 2026 · Applies to the Addonaut app for iOS (bundle com.addonaut.app), versions 1.0 and later
Addonaut is a studio for making pixel-art character skins and packs. From version 1.2 it also has a Browse tab: a catalogue of add-ons, textures, maps, skins and shaders made by other people, which you can look through, download and pass to the iOS share sheet. From version 1.4 you can also write comments and send setups (sets of catalogue items) and game servers for other people to see. From version 1.11 it has Discussions: posts written by us, with comments and sometimes a poll. From version 1.12 the catalogue also lists works whose file you get on the author's own page, not from us. This page says plainly what the app does with data. It covers version 1.0 and every later version; where they differ, the page says which one it is talking about. If a later version changes any of this, the page changes first.
The app is published by Alona Lashkul (Odesa, Ukraine), the developer named on the App Store listing. The online services of our own that the app talks to — the report inbox, from version 1.2 the catalogue, from version 1.4 comments, setups and servers, and from version 1.11 Discussions — are operated for the publisher by MCModsHub (mcmodshub.com). For anything on this page, write to support@mcmodshub.com.
Your skins, drafts, packs, wardrobe choices and settings are stored only on your iPhone or iPad, inside the app's own storage. Photos you pick with the system photo picker are read on the device and are not uploaded. A skin made from a text description is composed on the device; the description is not sent anywhere unless you report the result (see below). If iCloud Backup is on for your device, Apple backs these files up under your own Apple Account, like any other app data; we have no access to that backup.
| When you… | What is sent | To whom |
|---|---|---|
| look up a skin by a player nickname | the nickname you typed | Mojang's public profile API (api.mojang.com, sessionserver.mojang.com, textures.minecraft.net), operated by Microsoft. We do not store the nickname on our servers. |
| report a generated skin | the description you typed for the generator, what you write about the problem, and the usual connection details (IP address, app version) | our report inbox at api.mcmodshub.com |
| browse or search the catalogue 1.2 and later | the text you type into search, the filters you choose and which item you open — from 1.9 together with the app's language, so that the item and its comments can come with a ready translation — with the usual connection details (IP address, app version). Search text is used to answer the request; we do not build a search history from it. | our catalogue service at api.mcmodshub.com |
| download a catalogue item 1.2 and later | which item you asked for. The file itself then comes either from our own storage or straight from the file servers of the site where its author published it (CurseForge), and that host sees your IP address like any download server does. When the download ends the app tells us the item, whether it succeeded, how many bytes arrived, which attempt it was and, on failure, the kind of failure; this is recorded with your country and IP address. | our catalogue service; our file storage (Cloudflare R2); CurseForge's file servers (Overwolf) |
| see the picture of a catalogue item 1.2 and later | a request for the picture. The app loads only the picture addresses our service gives it: covers, previews and screenshots of catalogue items come from our own file storage, also for works listed from an author's page; the preview of a video in an item's card comes from YouTube; pictures in Discussions posts come from our website. That host sees your IP address like any web server does. | our file storage (Cloudflare R2, files.mcmodshub.com); YouTube (Google, i.ytimg.com) for video previews; our website (mcmodshub.com) for Discussions pictures |
| open the original page of an item listed from its author's page 1.12 and later | for these works we give no file: the app opens the author's page in the Safari app, and you download there. That website sees your visit like any website does, and its own privacy policy applies. Usage statistics record one event that the button was tapped (the kind of work and where you tapped it), not what you do on that website; nothing is sent to our service. | the author's website; Google Analytics for Firebase |
| share or save a downloaded item 1.2 and later | the item, whether you shared it, saved it, cancelled or it failed, and the system name of the destination you picked in the share sheet (for example AirDrop or Save to Files). Never who you sent it to, and never the file. | our catalogue service |
| report a catalogue item 1.2 and later | the item, the kind of report, what you write, a contact if you choose to give one, and the usual connection details (IP address, country, app version) | our report inbox at api.mcmodshub.com |
| ask us to remove your work, as its author or its rights holder 1.12 and later | the form under Is this your work?: the item; your name or nickname as it appears on the original page; an e-mail address; a link to the page or profile that shows the work is yours; whether you want this item or all your work removed; for a rights holder, what was infringed; and the usual connection details (IP address, country, app version). Every field is required: we need the e-mail to write back to you, and the name, the link and the text to check that the claim is yours before anything is removed. A person reads the request. The notice that tells that person a request came in carries your name, the link and the text, but not your e-mail, and is delivered through Telegram. We use the e-mail only to answer this request. | our report inbox at api.mcmodshub.com; the notice: Telegram |
| hide an author 1.2 and later | the list of hidden authors stays on your device. One message is sent saying that an author was hidden from this item, with no text and no contact. | our report inbox |
| use the app 1.1 and later | that the app was opened and how (icon, link or notification); which screens and tabs you open; what you do in the catalogue (opening a type, applying filters, downloading, translating a description, hiding an author, reporting) — the kind of action, never the text you type; that a skin was exported, in which file format and for which game edition; that the app asked for a rating, and after how many exports; from version 1.2, that a catalogue download ended, with the kind of item and whether it succeeded, failed or was cancelled; from 1.3, whether an advertisement before a download was started, watched to the end or closed early; from 1.4, the first successful download and the first export, a purchase with its price and currency, and the revenue an advertisement earned; from 1.4, opening comments, setups and servers and sending them — the kind of action, never the text. With them come Google's standard measurements — device model, iOS version, language, app version, approximate region derived from the IP address, and a random app-instance identifier. Never your skins, anything you type, or the advertising identifier. | Google Analytics for Firebase (Google) |
| the app crashes 1.4 and later | a crash report: where in the app's code it stopped, device model, iOS version, app version, free memory and disk, and the same random app-instance identifier. No skins, nothing you typed. | Firebase Crashlytics (Google) |
| the app recovers from an error 1.12 and later | a report of the same kind as a crash report, for an error the app handled without crashing: where in the app's code it happened, short codes for the part of the app and the kind of error (for example an HTTP error number), and the same device details and random identifier. No skins, nothing you typed, no nicknames or comments. | Firebase Crashlytics (Google) |
| install the app 1.4 and later | once per install, the app asks Apple whether it was installed from an Apple Ads advertisement. Apple answers with the campaign, ad group and keyword, or "not from an ad"; that answer is added to the usage statistics above. Apple does not tell us who you are. | Apple (AdServices); Google Analytics for Firebase |
| translate a description 1.3 to 1.8 or a comment 1.5 to 1.8 | nothing: the translation is done on your device by iOS. iOS may download a language once, from Apple. | — |
| translate a description, or a comment on a catalogue item 1.9 and later | which text it is (the identifier of the item or the comment) and the app's language, with the usual connection details (IP address, app version) — not the text, and nothing about you. If our service has translated that text before, the translation comes back at once. If not, our service sends the text itself — the item's published description or a published comment, nothing else — to a machine-translation provider and keeps the translation, so that the same text is translated once for everyone. The translation is stored with the text only, never with anything that says who asked. The request itself, like every request to our service, is in our server's access log (IP address and the address requested), which is overwritten within about a day. When our service has no translation to give, and always for comments on game servers, the translation is done on your device by iOS, as before; iOS may download a language once, from Apple. | our catalogue service at api.mcmodshub.com; for a text it has not translated before, its machine-translation provider (see Third parties) |
| start the app 1.1 and later | a request for the app's current settings, carrying a random installation identifier that is created on your device and is not your advertising identifier | Firebase Remote Config (Google) |
| buy something 1.1 and later | the purchase is made with Apple. The app is told by Apple which purchases are active for your Apple Account; we receive no name, card or billing detail. Analytics may record that a purchase happened, and which one. | Apple; Google Analytics for Firebase |
| see an advertisement 1.1 and later, only while advertising is on | IP address, device type and settings, which ads were shown and tapped, your consent choices, and the advertising identifier (IDFA) only if you allowed tracking in the iOS prompt | Google AdMob and the advertising partners it works with |
| write a comment 1.4 and later | the text, the nickname you chose, which item or server it is about, the version of the rules you agreed to, and the usual connection details (IP address, app version). Our service answers with a deletion key that stays on your phone. If notifications for answers are on, the notification token is sent with it. | our service at api.mcmodshub.com |
| report a comment, a setup or a server 1.4 and later | what you report, the reason, and a note if you write one, with the usual connection details | our service |
| hide an author of a comment or a setup 1.4 and later | nothing about the author: the list of hidden authors stays on your phone. Usage statistics record that an author was hidden. | — / Google Analytics for Firebase |
| download all items of a setup 1.4 and later | the same as for a single download, plus one message that the setup was downloaded, with nothing else in it | our service |
| send a setup or a server 1.4 and later | for a setup: the items you picked, its name, category and your note; for a server: the address you typed and your note; in both cases the version of the rules you agreed to and the usual connection details. Our service answers with a random key that stays on your phone. If notifications for answers are on, the notification token is sent with it. To check a server address our service connects to that address. A published setup can also appear, without your nickname, in the publisher's other apps and on mcmodshub.com; comments are shown only in Addonaut. | our service |
| open My submissions 1.4 and later | for each thing you sent, its number and its key, to ask whether it was published | our service |
| turn on notifications for answers 1.4 and later | the notification token, the app's language, your time-zone offset, the hour you last opened the app, and whether you also want news. Sent again when one of them changes, and about once a day while you use the app. | our service; Apple and Google (Firebase Cloud Messaging) deliver the notifications |
| tap a notification 1.4 and later | if it was a news notification, which campaign it belonged to — nothing else | our service |
| open Discussions or a post 1.11 and later | which post you open, the app's language, and the usual connection details (IP address, app version). If you are signed in to Discussions, your sign-in token is also sent when you open a post, so that your own vote can be shown. | our service |
| read the comments under a post 1.11 and later | which post and page, the app's language so that a ready translation can come with the comments, and the usual connection details. Reading comments only looks up translations our service already has; it never sends a comment to a translation provider. | our service |
| translate a comment under a post 1.11 and later | which comment it is (its identifier) and the app's language, with the usual connection details, not the text. If our service has not translated that comment before, it sends the published comment text to the machine-translation provider and keeps the translation for everyone. | our service; the machine-translation provider named below |
| write a comment or a reply under a post 1.11 and later | the text, which post (and which comment you reply to), your sign-in token for Discussions, the nickname if you set one, the usual connection details and the app version. No device model and no notification token. Before the comment is shown, our service passes the text through an automatic check (see Discussions). | our service; Firebase Authentication (Google) for the sign-in token; Google (Gemini) for the check |
| vote in a poll, or change your vote 1.11 and later | which post, the option you picked, your sign-in token and the usual connection details. A new vote replaces your earlier vote on that poll. | our service; Firebase Authentication (Google) |
| report a comment under a post 1.11 and later | which comment, the reason you chose, a note if you write one, and the usual connection details. No sign-in token and no name are sent. Our service keeps a short code made from your IP address and the day, not the address, and the code cannot be matched across days. | our service |
Our own servers are located in the European Union and are fronted by Cloudflare, which sees the same connection details any website's edge network sees.
Version 1.0 has none. Version 1.1 contains Google's advertising component. Whether advertisements are shown, and to what share of installs, is set remotely and can change without an app update — it may start low and be raised gradually. While advertising is off for your install, the app makes no advertising request, shows no consent form and does not ask for tracking permission. While it is on:
How Google uses data from apps that show its advertisements is described at policies.google.com/technologies/partner-sites.
The evening reminder is a local notification: your iPhone schedules it, nothing is sent to us or anyone else. You can turn it off in More → Daily reminder or in iOS Settings.
Answers 1.4 and later are optional. After you post a comment or send a setup or a server, the app may ask whether to tell you when there is an answer. Only if you agree, and iOS allows notifications, the app creates a notification token and sends it to our service with the app's language, your time-zone offset and the hour you last opened the app; the token is then sent along with your comments and submissions, so that the answer reaches this phone. News is a separate switch in More, off unless you turn it on.
When you turn Answers off in More, or turn notifications off for Addonaut in iOS Settings, the app tells our service and the token is deleted there. Deleting the app makes the token useless.
Our service, like any server, sees the network address a request comes from; it is not stored with your comments or setups, and our connection logs are kept only for the short period described under How long things are kept.
Version 1.0 has none. From version 1.1, purchases are optional and are processed entirely by Apple under your Apple Account. From version 1.12 they include Addonaut Pro, an optional subscription (yearly, monthly or weekly) that turns advertisements off and renews automatically until you cancel it in Settings → your name (Apple Account) → Subscriptions; the terms are in the Terms. Refunds are requested from Apple. Restore purchases in the app brings a purchase back on another device signed in to the same account. We keep no record of who bought what.
Addonaut lets you invite friends: each friend who installs the app and enters your code gives both of you days without advertisements. There is still no account. To know who is who, the app sends our service the purchase record that Apple signs for every copy of the app (Apple calls it the app transaction). We check Apple's signature and use two things from it: Apple's identifier for your copy of the app, and the date you first got the app. We never keep the identifier itself — only a code made from it with a secret key (a keyed hash), which cannot be turned back into the identifier.
For you, our service keeps: that keyed hash, your invite code, the date you first got the app, the date your days without advertisements run until, when you first used invites and when the app last asked about them. For each invite someone confirms, it keeps: whose code it was, the keyed hash of the friend, the code, the result (counted, or why not — for example the code is the friend's own, or this friend was counted before), how many days it gave, the result of the phone check described below, and the date.
The phone check. So that one phone counts as one friend only, the app uses Apple's DeviceCheck. Apple keeps two yes/no marks per phone for our developer account; we set one of them to say «an invite has already been confirmed on this phone». We cannot read anything else about the phone, and Apple does not tell us who you are. The mark stays with Apple for that phone even if the app is deleted.
To stop codes being guessed, our service limits how many invites can be confirmed from one network per hour; the network address is used for that limit and is not stored with the invite records. When someone opens an invite link in a browser, the invite page tells our service that it was opened, with the page language, whether the link had a code and the kind of device (iPhone or iPad, Android, computer); it does not send the code, and nothing that identifies the person is kept.
Deletion. Write to us at support@mcmodshub.com with your invite code, and we delete your invite data: the code is never given to anyone again, and what is kept is only a mark that the code was used. Invite data is also deleted by itself after 12 months in which the app has not asked about your invites. Deleting the app does not delete invite data on our side, because it is not tied to the phone; days you already have keep running on our side until they end.
Discussions are posts written by us, with comments and sometimes a poll. Anyone can read them without signing in. To write a comment or vote in a poll, the app signs you in to Firebase Authentication, a Google service, in the background, anonymously, without an email, a password or an Apple or Google account, and our service creates a Discussions identity for you: an internal number and the nickname you chose, tied to your comments and votes. We do not ask for or store an email address, a phone number or a real name for it. This is the only place where the app uses an identity; catalogue comments, setups and servers still work without one.
Comments under a post go through an automatic check before they are shown, and doubtful ones wait for a person. A comment under a post is shown with your nickname to everyone who reads the post, including readers of our Android apps, which show the same posts. Reports of a comment under a post are anonymous.
Deletion. You cannot delete a comment or a vote inside the app. To have your comments, votes and Discussions identity deleted, write to support@mcmodshub.com and tell us roughly when you wrote, under which post, and your nickname; a person on our team will find and delete them by hand.
Catalogue items belong to their authors; each one shows its author, why we may show it, and a link to where it was published. A skin looked up by nickname belongs to the player who wears it, and Addonaut shows it for preview only. See the Terms and the Copyright & Takedown page for how that content is treated.
Addonaut is not directed at children under 13 and does not knowingly collect personal data from them. From version 1.4 people can write comments and send setups and servers, and from version 1.11 comment in Discussions; every one of them goes through a filter before it appears (the automatic part is done by Google's Gemini, see the list below), and doubtful ones wait for a person. The rules for what may be posted are at mcmodshub.com/addonaut/rules. If you believe a child has sent us personal data, write to support@mcmodshub.com and we will delete it.
If you are in the EU, UK or another place with data-protection law, you can ask what we hold about you, ask us to correct or delete it, or object to how it is used. Because the app has no accounts with an email address or a name, the only data on our own servers that can be tied to you is what you sent — a report (from version 1.12 a removal request also carries the name and e-mail you gave), a comment, a setup or a server — from version 1.11 your Discussions identity with its comments and votes (tell us your nickname), the catalogue records described above (from version 1.2) and, if you turned answers on, the notification token; if you used invites, also the invite records described under Invites (tell us your invite code). Tell us roughly when and what, and we will find and delete them. Consent given in Google's form can be withdrawn at any time in the way described under Advertising. Write to support@mcmodshub.com. You also have the right to complain to your local supervisory authority.
If we change what the app sends or keeps, we update this page and the effective date at the top before the change ships. Material changes are also described in the App Store release notes.