← Back to GoGoGo

隐私政策

Privacy Policy

Author and operator: PlutoKeating · Version 1.6 · Updated November 17, 2026

This policy explains how PlutoKeating, operating the GoGoGo (走不走) website as an individual, handles personal information. PlutoKeating is the personal information handler for this website and the contact for privacy matters, reachable at [email protected]. This version takes effect on the date it is published.

1. Scope and current status

The website mainly serves users in mainland China. This policy is made under the Personal Information Protection Law of the People’s Republic of China and other applicable laws. It is provided in Chinese and English; the English text is a translation, and if the two versions differ, the Chinese text prevails.

This policy covers the promotional site, the 狗狗GO page, the website’s information pages and the product pages, as well as questions you send to the operator. After you follow an external link, the other website’s own policy governs its data handling.

The product code in this version includes sign-in, private preferences, location on request, place search, group outings and itineraries; what is actually available depends on the operator’s deployment and service configuration. The promotional site itself does not collect these product fields. The product’s submit button sends your current request to the backend, so please provide only what is needed for the decision. Payments and subscriptions are not currently offered.

Features that have not launched do not start collecting data just because this policy mentions them. Before adding features, we will first update the notice and the choices available to you.

2. Information we may currently process and why

Website access and infrastructure

When your browser visits the website, it sends technical information such as your IP address, the requested path, the time and browser- or device-related request headers to the servers or network infrastructure serving the page. This is used to deliver pages, troubleshoot faults and keep the service secure.

The project is hosted on Cloudflare Pages / Workers. When serving through Cloudflare, it may process request information according to the caching, security and logging settings actually enabled. The application code does not implement its own access-log database or behavioral profiling; this does not mean the hosting platform processes or records no access information at all.

Downloads and release information

When you open the download page, your browser requests the latest official release information directly from the GitHub API; GitHub receives the IP address and request headers needed for the connection. Downloads of attachments are served by GitHub. These requests do not carry your product sign-in token, private profile or conversations. The release page does not set any extra cookies or persistent cache.

Contacting us

When you send an email, the operator receives your email address, the message, attachments and the necessary communication details, and uses them to reply to questions and handle complaints, privacy requests or security incidents. Email is also processed by the email providers you and the operator use. Please share only what the issue requires, and do not send passwords, complete identity documents or unrelated health information.

We will not add your address to a marketing list because you contacted us, and we do not use email content to train recommendation models.

3. What we do not currently do

The application code does not include advertising, third-party behavioral analytics, marketing tracking or browser fingerprinting. We do not sell or rent personal information, and we do not use access records for personalized advertising. Recommendations you request are filtered using the request you submit and the preferences you have authorized; you can change the conditions, reject a plan or stop using the service.

Account service: sign-in and accounts are provided by the PlutoKeating account (id.plutokeating.beer), which the operator runs; GoGoGo shares the same account with PlutoKeating’s other products. When you sign in or register on the web or in the app, you are taken to the account page, which handles your email, password, email verification codes, passkeys or GitHub sign-in. Passwords are stored as one-way hashes, and GoGoGo’s business database does not store passwords. After sign-in, GoGoGo receives only the account identifier, your email address and whether it is verified. For password-free sign-in in the WeChat and Douyin mini programs, the GoGoGo backend sends the temporary login credential to the respective platform to obtain your in-platform identifier (OpenID), then records “which mini program and that identifier” on your PlutoKeating account so the same person can be recognized next time; such accounts may have no email address. You can verify an email inside the mini program, or scan the link code shown on the web with the mini program, to merge the mini-program identity into the email account: conversations and itineraries move with it, and the email account’s existing private profile is kept. Verification-code emails are sent by the PlutoKeating account through NetEase Mail SMTP. PlutoKeating account data is stored on servers outside mainland China (in South Korea); see Section 6.

Private profiles, itineraries and feedback are stored in a self-hosted PostgreSQL database in mainland China. Since November 17, 2026, conversation records (the text you send, information describing attached images, and 狗狗GO’s replies and recommendation cards) are stored in Cloudflare Durable Objects storage in the Asia-Pacific region (for example Hong Kong SAR, Singapore or Japan), so that replies do not need a cross-border database round trip at every step; the title and time of each conversation are also copied to the database in mainland China for the expiry of guest data, and image files themselves remain in that database. To speed up follow-ups such as “another one” or “closer”, the nearby places already found in a conversation are kept in that storage’s memory for up to 10 minutes; once your location is available on the start screen, nearby places for the four shortcuts are looked up in advance and kept only in your own storage for up to 5 minutes, never shared with other users. To speed up “plan something”, a signed-in user’s “don’t suggest again” list and the interests in their private profile are cached in the same storage for up to 5 minutes and cleared at once when you submit negative feedback, remove an entry or change your profile; the nearby places prefetched on the start screen are also used to build the estimated itinerary. To speed up sign-in checks, your account identifier, sign-in credential version and account status are cached in Cloudflare’s edge key-value store for up to 2 minutes; signing out or deleting your data clears the local copy at once, and other locations stop using it within about 60 seconds. To show your city name faster, the public map answer to “which city and nearest shopping area does this square belong to” is cached in Cloudflare’s edge key-value store for squares about 500 metres across, for up to 7 days; the cache is keyed only by the rounded square’s coordinates and holds no account, device or request-time information. Tianditu receives place keywords, the city, the coordinates you have authorized for the current request and the coordinates of itinerary stops, for search and walking-route planning; it does not receive health information in its original form. When you name a city or district in a message (for example, “I’m in Zhanjiang”) or enter a home city in your private profile, that city or district name is sent to Tianditu to determine the center of the current search; the rest of your message is not sent to map services. To add opening hours, average prices and ratings for nearby places, the AMap open platform receives the current coordinates and place-category keywords, but not your identity or account information. Maps on the web, Douyin and the app are displayed through the backend’s Tianditu service; WeChat may use the host’s place picker or location view when you choose to. The configured model providers receive only the filtered candidate place IDs, names, categories and reference prices; they do not receive your email, password, platform OpenID, health profile or identity. External AI assistants that you authorize by signing in on the PlutoKeating account page can call GoGoGo’s place search and itinerary planning on your behalf, and their requests are handled under your account identity. Model providers are configured by the administrator; their actual names, regions and retention rules must be checked and disclosed by the operator before they are enabled. The catalog service models.dev only provides public information about providers and models.

4. Cookies and browser storage

The promotional site does not set cookies itself. The product uses browser or mini-program platform storage to keep your sign-in token and maintain your session; the token is cleared when you sign out. The product stores your chosen interface language (Simplified Chinese or English) on your device and tells the backend through the Accept-Language header so replies come back in the same language; the promotional site keeps a language you choose manually in your browser’s local storage. Language choices are not used to identify or track you. The product keeps per-account local copies of your private profile (including optional health constraints you provide), messages, history, account summary and itineraries; it reads the local copy first and then syncs with the cloud. The web uses IndexedDB, WeChat and Douyin use host storage, and the app uses AsyncStorage. Signing out does not delete your private profile; it is restored when the same account signs in again on this device. Explicitly deleting your account data clears the corresponding local copies, and you can also clear app data in your device or browser settings. During web sign-in redirects, the browser temporarily keeps a one-time verification value, which is deleted when sign-in completes or fails; the PlutoKeating account page uses its own necessary cookies to keep you signed in. Administrator sessions are kept only in page memory and require signing in again after a refresh.

If the deployment enables Cloudflare security features, the infrastructure may set necessary cookies for security or traffic management, depending on which features are enabled. See Cloudflare’s cookie documentation. This does not mean every cookie listed there is enabled on this site.

You can use your browser settings to inspect, delete or restrict cookies; restricting necessary cookies may affect security checks or access. Before any non-essential analytics or advertising technology is enabled, we will explain its purpose and, where applicable rules require, offer options to consent and to refuse.

We process information only where we have a basis recognized by applicable law, including processing necessary to provide the access or reply you requested, fulfilling legal obligations, and consent obtained in accordance with law. Each basis must match the actual purpose; visiting the website is not treated as authorization for any purpose.

You can choose not to contact us and still browse the public pages. Where processing is based on consent, you can withdraw that consent; withdrawal does not affect processing lawfully carried out before it. For future optional features, the feature’s entry point will explain the specific effect of refusing or withdrawing.

6. Sharing, entrusted processing and cross-border processing

To deliver website content or handle email, hosting, network and email providers may have access to the corresponding information. We use these services only to the extent needed to provide the service. Where disclosure is required by law or genuinely needed to protect lawful rights and interests, we will verify the basis and limit its scope.

Cloudflare uses distributed infrastructure, and email may pass through regions outside where you are. This policy therefore does not promise that all access and email data are stored only within China. See the providers’ statements in the Cloudflare Privacy Policy and the Microsoft Privacy Statement. Third-party policies do not relieve the operator of its obligations for its own processing.

Storage of account information outside mainland China. The PlutoKeating account is run by the operator of this website, and its servers are in South Korea. When you sign in, register or use password-free mini-program sign-in, the following information is stored on that server: the account identifier, your email address and its verification status, an optional name, the password hash and passkey public keys, your GitHub account identifier (if used), and the mini program’s AppID together with your OpenID in that mini program. It is used only to identify your account and complete sign-in. GoGoGo conversations, itineraries, private profiles and location information are not stored on that server; itineraries, private profiles and location information remain in the database in mainland China, and where conversation records are stored is described in the next paragraph. Before you sign in or link an account, the interface asks you to confirm this policy; if you do not agree, you can use the web’s guest mode without signing in. You can exercise access, correction, deletion and other rights under Section 8; to delete the PlutoKeating account itself, contact us by email. The service is currently in beta; before it is formally offered to the public, the operator will complete the assessments and procedures required by law for transferring personal information abroad.

Storage of conversation records outside mainland China. Since November 17, 2026, conversation records (the text you send, information describing attached images, and 狗狗GO’s replies and recommendation cards) are stored in Cloudflare Durable Objects storage in the Asia-Pacific region, managed under the operator’s account and used only to show you the conversation and let you continue it; Cloudflare processes this data as an entrusted infrastructure provider. If a conversation contains food or health preferences you typed yourself, they are stored with it. You can delete a single conversation in the product, or clear everything with “Delete all my data”; guest conversations are deleted automatically about 48 hours after their last activity. As with account information, the service is currently in beta, and before it is formally offered to the public the operator will complete the assessments and procedures required by law for transferring personal information abroad; if you do not agree, please do not use the conversation feature.

If future services involve providing information to other handlers or new cross-border transfers of personal information, we will, before that happens, state the recipient, purpose, types of information and how to exercise your rights, and complete the necessary assessments, notices and consent procedures required by law. This paragraph is not advance authorization for any cross-border transfer not listed here.

7. Retention and deletion

For signed-in users, profiles, itineraries and feedback are kept until you change or delete them or delete your account data. Places in your “avoid” list stop being used in filtering after 90 days and can be removed earlier. Guest single-person recommendations do not keep business history; temporary constraints from guests who join a group are deleted by a cleanup job when the group ends or after 24 hours. Retention periods for infrastructure logs and backups depend on the actual deployment and cannot be confirmed from the source code as a single number of days; contact the operator to check.

Emails you send are kept only as long as needed to resolve the matter, for necessary follow-up, or to meet legal obligations. Once the need ends they are deleted or anonymized, except for parts that must be kept by law or are genuinely needed for a dispute. After receiving a deletion request, we will verify its scope and tell you the result and any reason something cannot be deleted immediately; we do not promise fixed deletion times that cannot be verified.

The in-product deletion entry is not the same as immediately purging infrastructure backups. The operator maintains, according to the actual deployment, how backups are kept and how deletions are re-applied when restoring, and will explain this on request.

8. Your rights and how to make a request

Within the scope of applicable law, you can ask to know how your information is processed; access or copy it; correct, supplement or delete it; restrict or refuse processing; withdraw consent; and ask for the processing rules to be explained. Where legal conditions are met, you can ask for your information to be transferred. In the product, “Me → Privacy and account” offers data export, sign-out and deletion of all your business data; deletion also revokes your existing sessions. It deletes only GoGoGo’s business data and unlinks it from your account; the PlutoKeating account itself is kept (it may be used for other products), and you can manage your email, password and passkeys on the account page.

Email [email protected], ideally with “Privacy request” in the subject, stating the type of request and the relevant page or the approximate time of the communication. We will verify the requester’s identity in a necessary and proportionate way to avoid disclosing information to anyone not entitled to it; please do not proactively send full photos of your ID card.

We will handle and reply within the time required by applicable law and explain what we have done; if we cannot fulfil a request, we will explain why and what remedies are available. Ordinary requests are free of charge; repeated or excessive requests are handled as applicable law allows. You may also complain to a personal-information-protection or consumer-protection authority with jurisdiction, without first having to contact the operator.

9. Sensitive information and minors

When you open the product page, it asks for system location permission. If you allow it, the current coordinates are sent to the backend, Tianditu and the AMap open platform to determine your city and search for nearby places; you are not tracked continuously. Location comes only from your device’s GPS or a place you choose manually; we do not infer your city or location from your network IP. If you refuse, you can still choose a place manually. Health constraints are optional, confirmed separately when you select them, and used to exclude unsuitable activities; you can change or delete them at any time. Group outings use only authorized, combined constraints and never show other members your original health information. Please do not provide other people’s information without their permission.

If we ever need to process health information, precise location or other sensitive personal information for new purposes, we will first explain the specific purpose, necessity, impact and safeguards, and obtain separate consent as required by law. Where personal information of minors under fourteen is involved, we will obtain guardian consent as required by law and adopt dedicated rules; until those mechanisms are in place, we will not actively collect such information.

If a guardian or the individual believes such information has been sent by mistake, please contact the operator so we can verify and delete what is not needed.

10. Security and incident response

The source code includes database row-level permissions, user and administrator authentication, encryption of provider keys and minimization of sensitive fields. The actual level of protection still depends on correct database roles, networking, keys and deployment configuration; this policy is not a security certification and does not mean production verification has been completed.

If personal information is leaked, altered or lost, we will take the necessary remedial measures and notify the affected individuals and the competent authorities as required by applicable law. No internet transmission or storage can be guaranteed to be perfectly secure. If you find a suspected problem, please report it privately by email, and do not attach leaked data to the public repository.

11. Updates to this policy

Before adding account, location, model, payment or analytics features, we will re-check the data flows, update this policy and give clear notice at the relevant entry point. Significant changes will be announced prominently; where consent needs to be obtained again, we will ask again rather than rely on a unilateral update.

The latest version is always on this page. For any question about how personal information is handled, contact PlutoKeating at [email protected].