Data You May Share
If you use a newsletter or Trip Pack beta form, you may choose to submit your email, travel month, destination city, source page, consent status, and a hidden anti-spam field. If you use a feedback form, you may submit a feedback type, page or tool surface, source page, optional short comment, optional contact email, and follow-up consent. Do not include passport numbers, identity documents, bank card data, booking codes, full addresses, or detailed private itineraries in any form.
Storage and Use
If you submit a beta form, your email address is stored in a server-side PostgreSQL operational database together with a SHA-256 email hash for duplicate detection. If you submit feedback, the feedback record is stored in the same operational database with its risk level, status, issue key, source page, optional redacted comment, and optional contact email only when you consent to follow-up. If you unsubscribe, a separate suppression record stores the email address, hash, source page, and timestamp so future beta emails can be blocked for that address. These records are used for travel-readiness updates, checklist improvements, Trip Pack beta follow-up, source review, bug triage, and weekly product-signal reporting.
Subscriptions
Newsletter and Trip Pack beta forms require your explicit consent. You can unsubscribe through the /unsubscribe/ page, which blocks future beta signups from the same email. Until a production email provider is connected, you can also send requests to hello@chinatripready.com for manual review.
Local Tool Storage
Checklist progress, address cards, entry-wizard drafts, and privacy preferences are saved in your browser when you use those features. This keeps core travel materials usable without an account. You can reopen Privacy settings from the footer at any time to review your analytics choice, and you can still clear browser storage if you want to remove saved tool data.
Analytics
Optional analytics is only sent to external analytics tools after you allow analytics in the privacy banner. Search analytics uses categories and length buckets instead of raw search queries. Analytics events must not include raw email addresses, passport data, payment data, full addresses, booking codes, free-text comments, or free-text itinerary details, and analytics must not block site functionality.
Advertising and Affiliate Links
If ads or affiliate links appear later, they should stay clearly labeled, should not block the core tools, and should not influence editorial conclusions. Ad and affiliate interactions may be measured with anonymous event data.