Home / Privacy
Your trip stays here. A checker request goes further.
The trip planner and payment checker handle data differently. These notes describe the current site implementation, not a promise that visiting a website creates no server records.
Implementation reviewed .
Trips and saved guides stay in your browser
The trip planner stores your trip titles, dates, checklist completion, custom groups and tasks, and saved guide IDs in this browser’s localStorage under setengo.trip-workspace.v1. The planner does not upload that workspace to our server. There is no trip account, cloud backup or cross-device sync.
LocalStorage persists between visits until you delete the data or your browser clears it. Use the planner’s delete controls to remove a trip, or clear this site’s browser storage to remove the whole workspace. Clearing storage, changing browsers or using another device can make your saved trips unavailable; private browsing may discard them when the session ends.
Saved trips are also specific to the website address. Our primary address is www.nihaonana.com. The old nihaonana.com address now redirects to www, including the trip planner. Trips saved under the old address are not copied or deleted, but the redirect means the old planner no longer opens there. Those trips will not automatically appear on www.nihaonana.com. Trips saved on our previous workers.dev trip planner remain accessible at that address and are also not automatically transferred. Clearing the old address’s browser storage deletes its saved trips.
Anyone using the same browser profile may be able to view saved trips. Avoid putting passport details, card numbers, passwords or other sensitive information in trip titles or tasks. Following a saved guide opens a normal web page; it does not upload the rest of your checklist.
Installing the web app
Adding nihaonana to your home screen or desktop does not create an account or sync, copy or migrate your trips. Some browsers keep home-screen or Dock apps in separate storage. Check your trips in the app before clearing the original browser’s data.
On supported secure browsers, a service worker stores only the connection-loss page and its Nana icon in a small local cache. It does not cache guides, trip-planner pages, checker requests or checker answers for offline use, and it does not read or change your trip workspace. You still need a connection to load those pages and use the checker. Clearing site storage can remove both this cache and your saved trips.
What the payment checker sends
Submitting a check sends a request to our Supabase-hosted compatibility function. It includes the selected card network and operation, fixed mainland China / Alipay payment context, and any issuer name, issuing country or region, card type and account context you supply. Account context describes a category such as foreign visitor, not an account login.
The form does not ask for a full card number (PAN), expiry date, CVV/security code, bank login or Alipay credentials. It does not connect to your card account or process a payment. Do not enter those details in the optional issuer field.
The browser keeps form values and the displayed response in the current page’s memory, rather than saving them as a trip. Submitting still sends the request to the service, so this is not an entirely on-device checker.
Checker storage and automated research
The backend can store a normalized version of the card context and canonical input alongside a hashed lookup key and the scoped answer it matched. A hash does not make the accompanying context anonymous. It also retains operational records such as research attempts, timestamps, outcome or error information, provider request IDs and usage or budget records. Reusable research can be stored as compatibility claims and cited evidence.
If current evidence cannot answer a check, the configured service may send normalized context to OpenAI for embeddings and web-assisted research. That context can include your normalized issuer name, country, network, card type, operation and account category. Research may also fetch public source pages. Avoid supplying personal information in the checker.
Evidence and answer expiry control whether a result can be reused; they are not deletion deadlines. The current application does not define an automatic deletion schedule for checker mappings and research records, and we do not promise a fixed retention period for those records or infrastructure logs. Clearing browser storage does not delete a request already processed by the backend or its providers.
Optional Google Analytics
Production builds can enable Google Analytics 4 to help us understand page visits, traffic sources and site usage. When enabled, pages load Google’s analytics script and send browsing information to Google, including page URLs and titles, referrers, browser and device information, and interaction or session events. Google also receives the connection information needed for those requests. Analytics uses first-party cookies to distinguish browsers and sessions; it is not a count of identified people.
Our analytics configuration disables Google signals and advertising-personalization signals. We do not send trip titles, dates, checklist contents, saved trips or payment-checker form values as analytics event parameters, and we do not set an analytics User-ID. Do not put sensitive information in page URLs, because URLs may be included in analytics.
Analytics is disabled when no Measurement ID is configured and during local development. The current site does not include a cookie-consent interface. You can block Google Analytics with browser privacy tools or use Google’s Analytics opt-out browser add-on. Clearing cookies resets browser identifiers but does not delete data already received by Google. See Google’s privacy policy for its data handling.
Hosting, fonts, images and outside links
Cloudflare hosts the site, and Supabase hosts the checker service. Like other web infrastructure providers, they receive the connection information needed to serve requests, which can include your IP address, requested URL, browser headers and request time. Their infrastructure logging and retention are separate from the trip planner’s local storage.
Pages load DM Sans and Outfit from Google Fonts, so those font requests contact Google’s servers even if you do not use the checker. The current illustrations, app icons and destination photographs are served as site assets rather than embedded third-party image requests.
Source links, app links and provider links take you to other services. Their privacy policies and terms apply there; opening a link may disclose normal browser connection or referrer information. Mentioning a provider does not give nihaonana control over its data handling.
Your choices and privacy questions
You can read the guides without submitting a checker request or creating a trip. Local trip storage supports the planner rather than cross-site tracking; optional analytics is separate from that storage. Blocking analytics does not disable the planner or checker. Hosting, fonts and linked services can still receive normal connection information.
Our contact page states whether a public contact channel is available. Never share payment credentials, identity documents or your full trip workspace with someone claiming to provide site support. We cannot recover trips that existed only in browser storage after you delete them.
These notes may change as the implementation changes. They do not assert a legal certification or replace the privacy policies of external providers.