Privacy Policy

Last updated: June 23, 2026

mcworld.app is an independent third-party iOS tool for creating, repairing, protecting, and deploying world files. This policy explains what data we touch, where it lives, how long we keep it, and the choices you control. It reflects how the product is actually built, not just what we promise.

The one-line version. We read your files on-device by default; we never upload anything for cloud processing without your explicit, task-specific consent; we never overwrite source files — every operation produces a new version; you can delete cloud copies once a cloud task finishes; and server credentials live in the iOS Keychain, never appearing in logs, analytics, or crash reports.

1. Our privacy promises to you

Local-first by default. File-type identification, ZIP structure checks, name and cover reading, simple structural repairs, and basic health reports — anything that can run on-device runs on your device.
Explicit upload consent. Before anything is sent to the cloud for processing, you confirm the upload for that specific task. There are no silent background uploads of your worlds.
Never overwrite source files. Repairs, conversions, optimizations, restores, and deployments all produce new files. Your original files — or pre-deployment snapshots — stay intact and traceable.
Delete anytime. Once a cloud task finishes, you can delete the temporary cloud copy; you can also delete saved backups and your entire account.
Scoped server access. Server connections are either read-only monitoring or full management that you've explicitly authorized. Every deployment clearly shows what will be read, written, and rolled back.

2. The data we handle and where it lives

The table below classifies the data the app handles, listing its default location, whether an account is required, and the default retention period.

Data	Default location	Account required	Default retention
Local world files	App sandbox / your Files	No	You control it
Quality scan results	Device + short-term cache	No	24–72 hours
Temporary upload copies	Private cloud storage	Yes	72 hours after the task
Saved world backups	Private cloud storage	Yes	Per your plan's rules
Server addresses	Account metadata	Yes	Until you delete them
Server credentials	iOS Keychain / encrypted vault	Yes	Until you revoke them
Operation logs	Cloud	Yes	90–365 days, per plan and compliance policy

3. Local-first diagnostics

When you open a world file, we copy it into the app sandbox and scan it on your device. Local diagnostics identify the file type; read the name, size, hash, and cover; check the top-level directory structure and required files; recognize the base version and format; and generate a free diagnostic report — all without uploading anything.

Only when a task genuinely requires cloud processing — for example, advanced repair, Java Edition → Bedrock conversion, large-area generation, or cloud backup — do we ask you to upload, and only for that task.

4. Explicit upload consent and cloud processing

Before any upload, you see what will be uploaded, whether the task runs in the cloud, the estimated time, and what happens on failure. Uploaded copies live in private cloud storage and are automatically deleted 72 hours after the task; you can also delete the cloud copy earlier from the results page.

We never overwrite your source files. Cloud processing writes out a brand-new output file. Your input file and a safe copy are kept alongside their hashes, so the result is always traceable back to the file you started with.

5. Accounts and authentication

On-device features (diagnostics, simple repairs, the local library) work without any account. Cloud features — real-map generation, temporary upload processing, cloud backups, server management, and operation logs — use an anonymous account created automatically on first use; we don't ask for your name, email, or any personal identifier. Purchases are tied to a random token unique to each installation, not to your identity.

6. Server connections and credential security

Server Companion has two clearly separated modes:

Monitoring only (free). All it needs is the server address and port. It reports online status, version, player count, and latency. It doesn't read the world directory and has no write access.
Full management (paid). This requires you to explicitly authorize the connection method and world directory. It can create remote snapshots, verify recoverability, perform safe deployments with health checks, and roll back. You can review and revoke these permissions at any time.

Credentials live in the iOS Keychain or an encrypted credential vault. They never appear in plain text in the interface, logs, crash reports, or analytics, and you can revoke them at any time.

7. Analytics

We collect coarse-grained, privacy-preserving usage events to improve reliability and success rates — for example, an anonymous user/account ID, device and app version, task type, file-size bucket, area tier, source channel, duration, and result code. We do not upload world names, precise addresses, or server credentials as analytics fields.

8. Data retention

Quality scan results: 24–72 hours.
Temporary upload copies: deleted 72 hours after the task, or earlier on request.
Saved backups: retained per your plan; you can delete them manually.
Operation logs: retained 90–365 days, depending on plan and compliance policy.
Server addresses and credentials: retained until you delete or revoke them.

9. Account deletion (export first, then delete)

You can delete your account in the app at any time. Deletion follows an export-then-delete flow: before anything is removed, you can export your saved worlds and backups so you don't lose data. Once you confirm, we delete your account metadata, cloud backups, server addresses, stored credentials, and related logs (subject to any short-term legal or operational retention periods we're required to observe). Files stored locally on your device or in your own Files app belong to you and are unaffected.

10. Children

mcworld.app is a productivity and creation tool, not directed at children below the age required by the app store and privacy laws in your region. We do not knowingly collect personal data from children below that age.

11. Third-party data and attribution

The real-map feature uses map data © OpenStreetMap contributors, available under the Open Database License (ODbL). We do not use OpenStreetMap's public tile service as a source for commercial bulk downloading or offline caching. Generation relies on open-source components such as Arnis (Apache-2.0), whose licenses and NOTICE files are preserved in the app's settings page, on this website, and in our release packages.

12. Changes to this policy

If we make material changes, we'll update this page and the "last updated" date, and notify you in the app where appropriate. Branding, disclaimers, map attribution, and paid terms are reviewed before every release.

13. Contact us

Have a privacy question or need to make a data request? Reach us through the in-app support link, or visit the Help Center.

This document is provided for transparency and does not constitute legal advice. The final privacy and paid terms are reviewed and approved by the responsible party before release.