Privacy

Privacy Policy

Content published:

Introduction

MiaoMiao City respects the privacy of every visitor.

This Privacy Policy explains how information is handled when you visit the MiaoMiao City website or contact us by email.

We follow a principle of data minimization and process only the information reasonably necessary to provide, maintain, secure, and improve the website.

MiaoMiao City is a creative world-building project exploring future cities, technology, nature, and life.

Information We Process

Public pages can be browsed without signing in. Optional website accounts are available through Google sign-in and Supabase Auth. We do not currently offer payments, public comments, or visitor file uploads.

We do not require a legal name, phone number, home address or payment details for public browsing. If you choose to sign in, authentication may involve your Google account identifier, email, display name, optional profile image and session metadata; we do not receive your Google password.

When you visit the website, hosting and infrastructure providers may automatically process limited technical information, such as:

  • IP address
  • Browser type
  • Device and operating system information
  • Access time
  • Requested pages and resources
  • Security, diagnostic, and performance logs

If you contact us by email, we receive the information you choose to provide, such as your email address, message, and any attachments.

AI guide

Machine Cat is an AI. We send OpenAI your question, necessary conversation context, and relevant public sources and observations. A question uses at most three model calls, with up to two rounds of reading public information to investigate and answer. City knowledge, public weather and railway plans can be read together. Do not include secrets or unnecessary personal information.

Temporary chat is the default; signing in does not consent to saving. Temporary mode holds up to 20 turns in the current page or panel’s browser memory and sends at most four recent question-and-answer pairs, trimmed when necessary. Closing the panel or reloading clears this local history.

Signed-in visitors can choose “Enable saving and start a new chat”. Questions and final answers in that new chat are saved as OpenAI Conversation Items and can be restored on another device using the same website account. Existing temporary chats are not uploaded automatically. Supabase keeps a minimal index: the account link, conversation identifiers, dates, citations, and duplicate-request and deletion status. We do not duplicate full chat text in that database or write it to R2.

Saved chats continue using OpenAI’s native conversation context. Current retrieval evidence, internal decisions and instructions are not accumulated as chat messages. Historical answers retain their original citations, which may no longer be current; questions about current conditions trigger fresh public reads. You can open and delete chats from the list. Conversation-count and context-length limits may require deleting an old chat or starting a new one.

Responses API calls use store=false to disable saved per-response state. Conversation Items that you choose to save remain until separately deleted. This does not mean OpenAI retains nothing. Its abuse-monitoring records are retained for up to 30 days by default, with possible legal or safety exceptions; prompt caches involve separate temporary processing. We do not claim Zero Data Retention approval.

OpenAI · API data controls

Language Preferences and Cookies

The language preference cookie mmc_locale lasts up to one year. It remembers your chosen language, not an advertising profile. Browser language may select the initial version.

The signed, Secure, HttpOnly cookie __Host-mmc-guide lasts 30 days and links anonymous AI use to allowances and abuse protection. A cookie is not proof of a unique person. On sign-in, current guest usage is carried into the verified account allowance.

Optional Google/Supabase sign-in stores authentication sessions in browser storage so they can be refreshed. Signing out removes the local session. The login-language cookie mmc_auth_locale lasts 15 minutes; its local-storage counterpart is removed after a successful callback. These technologies support functions you request; blocking them can prevent those functions.

Cloudflare Turnstile processes browser and interaction signals. The widget loads when verification is needed. After server verification, a necessary HttpOnly, Secure, SameSite cookie, __Host-mmc-verification, is issued with pseudonymous verification state in Redis. Normal continuous chat does not reuse a Turnstile Token. Verification expires after 30 idle minutes or a maximum of 12 hours. Signing out, changes in identity, device or network binding, or invalid risk state require fresh verification.

Optional usage analytics is off by default. The choice below is stored in this browser for 180 days and can be changed here at any time. Necessary language, sign-in and security functions do not depend on accepting analytics.

How We Use Information

Technical information is processed only as reasonably necessary to:

  • Deliver website pages and resources
  • Maintain website security
  • Prevent abuse and malicious activity
  • Diagnose technical problems
  • Improve performance and reliability

Information sent by email is used to read and respond to your message, handle privacy-related requests, and maintain reasonable records of the communication where necessary.

Service Providers

Vercel hosts pages and API functions and handles delivery and security logs. With your permission, Vercel Web Analytics measures visits. Cloudflare provides asset delivery, Turnstile and email routing. Google provides optional OAuth sign-in and the project email inbox; Supabase Auth manages website identities and sessions.

OpenAI processes questions, necessary context and public evidence, and stores Conversation Items when visitors enable saving. Supabase Auth manages identity and sessions; its database stores the minimal history index and deletion work. Upstash Redis holds pseudonymous quota and security records and a separate cost ledger. Cloudflare R2 publishes and caches public world data; it is not a visitor chat database. The Supabase browser library is delivered through jsDelivr. Third-party resource requests also transmit necessary technical information.

These providers may process data outside your country, including outside the EEA. We have not verified that all services are confined to the EU. Provider policies describe their processing; actual data regions, contractual safeguards and any applicable transfer arrangements require service-specific verification. Ask privacy@miaomiaocity.com for information about the arrangements relevant to your request.

Vercel · Web Analytics

Cloudflare · Turnstile

Supabase · Privacy

Google · Privacy

Upstash · Privacy

jsDelivr · Privacy

Advertising, Tracking, and Sharing

We do not use advertising networks, behavioural advertising or cross-site advertising profiles, and do not sell personal data.

Optional Vercel Web Analytics uses request-derived hashes and aggregated visit statistics rather than third-party advertising cookies. Its visitor identifier is discarded after 24 hours according to Vercel. Analytics is loaded only after you enable it below; refusing or withdrawing leaves the website usable. We exclude query strings and fragments from analytics URLs.

Changing this setting reloads the current page to apply the choice. Withdrawal stops future collection; it does not erase statistics already processed by the provider. This choice is specific to this browser.

Optional analytics: Off in this browser

Data Security and Retention

HTTPS and server-side identity, challenge, rate and budget checks protect the service; no internet service can guarantee absolute security.

AI quota entries represent rolling 24-hour use and expire within 25 hours of their last use; short network counters and concurrency leases expire sooner. Guest-to-account bindings last 30 days and may be renewed on use. Environment-level request accounting can last up to 32 days. These records use pseudonymous identifiers and do not contain question or answer text.

Separate global cost records contain random attempt IDs, times, token counts, charges and deployment or test references, without dialogue text or direct account identifiers. They currently have no automatic deletion deadline and are retained for budget reconciliation. They are not covered by the 32-day quota-record expiry.

An optional website identity remains until you delete it from Account. Deletion first revokes refresh sessions and removes the Supabase identity; it does not delete your Google account or instantly remove expiring security counters, provider logs or backups. A later sign-in can create a new website account.

Temporary chats are not stored in the history database. Infrastructure logs and backups follow providers’ actual settings and policies; no single retention period has been verified for every provider. Email is retained as needed for replies, unresolved requests or applicable record obligations. You may request deletion.

Saved chats enter the deletion queue 90 days after creation or the most recent successful question. A background job checks for expired chats and pending deletions every 15 minutes. It deletes OpenAI Items individually, verifies that none remain, then deletes the Conversation and site index. Manual chat or account deletion hides the history immediately and schedules the same cleanup. Service failures and unresolved operations may delay completion; work is retained and retried. Hidden history is not reported as erased provider data. This application-level deletion does not guarantee removal of provider logs, backups or legally retained data.

Changes and Contact

Contact the MiaoMiao City website operator at privacy@miaomiaocity.com to ask what information we hold, correct account details or request access or deletion. Where applicable law provides these rights, you may also request restriction or portability, object to processing, withdraw consent and complain to the competent data-protection authority. Rights can have lawful limits; withdrawing consent does not affect earlier lawful processing.

The account page lets you view sign-in details, sign out and delete your website account. Machine Cat’s Conversations panel lets you view and delete chats you chose to save. Contact us by email for corrections or requests unavailable in those pages. We may ask for proportionate information to verify a request; never send passwords or API keys. Temporary chat held only in browser memory cannot be recovered by this site.

We update this policy when actual website practices change. The publication date identifies this content revision, not a routine deployment or fictional city date.

Website account

privacy@miaomiaocity.com

About this page

MiaoMiao City is a fictional future city. This page contains the website’s Privacy policy. Read the document itself for its stated scope; this explanation adds no legal promises, permissions or external endorsements.

Part of: MiaoMiao City website