Privacy Notice

Status of this page

This is a pre-launch privacy draft, not the final privacy notice. The operator and qualified privacy counsel must review the data map, legal bases, retention periods, processor list, international-transfer posture, and rights process before publication.

Data the product may use

The product may process public wallet addresses, signature-authentication records, selected profile fields, public collection references, city and Drop interactions, allowlist or residency submissions, report details, quest activity, and operational security logs. Which fields are public depends on the relevant feature and publication setting.

A wallet address can be personal data in some contexts. Public blockchain data may be durable and independently available even if Mintropolis removes a display of it.

Your message, page path and optional email go to our admin team. Never include private keys, recovery phrases or passwords.

Data Mintropolis should never request

The product is not designed to receive private keys, wallet recovery phrases, seed phrases, or unrestricted token approvals. Do not provide those secrets in profile fields, reports, task comments, or support requests.

Public versus private context

Public profile pages and approved city or Drop pages can expose the fields intentionally published for that page. Moderation, fraud-prevention, access-control, and audit records should remain restricted to authorized operations personnel and should not be exposed through public routes.

Social-task providers and external communities are separate services. A future final notice must name each enabled integration, explain what it receives, and document the relevant authorization and revocation flow.

Email contact, verification, and choices

Mintropolis may require a private email address, confirmed through a one-use verification link valid for 24 hours, before selected high-impact actions such as applying or administering community activity. Profile settings do not require email verification; public profile publishing requires a private email address but not verification. The email address is not part of a public Passport profile; verification only adds an optional public badge.

Members should be able to view their verification state, change their address, request another verification email, and manage notification choices from Profile. New Drop and city Embassy claim announcements should be off until a member opts in; operational updates about creator applications, personal Embassy activity, or moderation may be sent when those choices are enabled.

The final notice must explain the lawful basis for each required or optional message, consent and withdrawal mechanics, and the consequences of not providing or verifying an email address where the product makes it necessary.

Email delivery, links, and message artwork

Mintropolis currently plans to use Resend to deliver verification and product emails. Resend may process the recipient address, message routing data, delivery outcomes, and technical metadata needed to send and troubleshoot those messages. The final notice must name the contracted processor, applicable safeguards, and any international-transfer information.

Verification links are designed to be single-use and valid for 24 hours. The service should store only the controls needed to validate the link and deliver it safely, and should not place the raw browser secret in public analytics or ordinary navigation logs.

Mintropolis emails include a Mintropolis-hosted atlas banner at the bottom. An email client may request that image when a message is opened, which can disclose technical data such as IP address, user agent, and open timing to the media-delivery infrastructure. The final notice must describe this request and any email-client controls available to users.

Google Analytics

Mintropolis uses Google Analytics to measure page visits and site navigation.

Google may receive page URLs, page titles, referrers, and browser or device data, and may set analytics cookies.

Mintropolis does not send custom wallet, transaction, or form fields as analytics identifiers. Google Signals and ad personalization are disabled.

Before launch

The final notice must give a real privacy contact, describe applicable rights and verification steps, state deletion and retention rules, identify the controller or responsible entity, and link to any required regional disclosures.

Before launch, the operator and qualified privacy counsel must review the mandatory-email data flow, verification-link handling, Resend processing, notification defaults and preferences, email/banner request telemetry, retention schedule, security controls, and regional marketing or electronic-communications requirements.