Effective date: September 27, 2026
🏰 This post contains affiliate links. Our planning guides are free, but using our links helps support us at no extra cost to you.
Operator and scope
Your Disney is operated by 武源國際有限公司 (WY Internet INC.), 2 F., No. 20, Minquan W. Rd., Zhongshan Dist., Taipei City 104626, Taiwan (R.O.C.). This notice describes personal-data handling on www.yourdisney.com.tw, yourdisney.asia and the ThemeParkHelper features on those sites.
Our privacy contact is oscar@yourdisney.com.tw. Do not include identity documents, payment information or other private information in public comments or newsletter replies.
Reading, comments and article subscriptions
You can read our articles without subscribing or providing an email address. Where comments are available, your comment and display name may be public. The English site currently requires a name and email address for comments, without requiring login. Comments are currently disabled on the Traditional Chinese site; this does not establish that historical comments or associated data have been deleted.
The sites use Akismet to help identify spam; processing may include comment content, submitted information, IP address and browser information. Article subscriptions use Jetpack/WordPress.com, which processes your email address and choices to send post or comment notifications and manage subscriptions. On the English site, you can currently subscribe only through the comment form. Confirming a subscription sets up a WordPress.com account for managing it, which Automattic handles under its own terms and privacy policy. The Traditional Chinese site does not currently offer article subscriptions. Without a subscription email address, we cannot send notifications to that address. This does not prevent reading articles or using the planning tool without email.
You can unsubscribe through the link in a notification email or on WordPress.com’s subscription-management page. Jetpack newsletter replies are currently configured for public comments. Send privacy requests directly to the contact above.
Analytics, advertising and browser storage
The sites are connected to Google Analytics, AdSense and Tag Manager; the Traditional Chinese site is also connected to Google Ads. These services support analytics or advertising and may process cookies, identifiers and technical browsing information. We do not currently use Meta Pixel or Facebook/Instagram retargeting, or newsletter/contact-form services outside Jetpack.
ThemeParkHelper’s trip timeline and refurbishment pages are an exception: they do not load the site’s Google Analytics and Google Ads tags, AdSense or its ad-blocking recovery message, Jetpack Stats, Stay22 or Travelpayouts. These pages use only the ThemeParkHelper measurement described below.
The English site shows a cookie consent banner. Google Analytics and Jetpack Stats do not collect data until you choose Accept, and stay off if you choose Decline. The Traditional Chinese site currently has no consent banner: once you interact with a page, Google Analytics, Jetpack Stats, Google Ads and AdSense load. Google Ads includes remarketing, which shows ads to people who have visited the site, and AdSense’s third-party advertising partners may set their own cookies. You can block or delete cookies in your browser, or manage personalised ads in Google’s My Ad Center (myadcenter.google.com).
Both sites use the Travelpayouts affiliate program, which runs regardless of your cookie choice. It sets a cookie named am_user_session, lasting about 30 minutes, as a session identifier while its script runs, and may turn partner links in articles into links carrying a commission-tracking code.
Both editorial sites’ Analytics properties currently retain user and event data for 14 months, with retention reset on new user activity enabled. These controls do not limit retention of standard aggregated reports. ThemeParkHelper uses a separate Google Analytics property that retains user and event data for two months, without resetting retention on new activity.
For privacy questions and requests to access, obtain copies of, supplement, correct or delete personal data, or stop its collection, processing or use, contact oscar@yourdisney.com.tw.
ThemeParkHelper trip data
ThemeParkHelper currently requires no account or email address. Park dates, optional travel and accommodation details, your choice about showing the document-preparation task, and preparation progress are used to calculate and display your timeline in the browser. The tool also stores a time zone, random identifiers and calendar-export records to keep trips and reminder items consistent and show changes after an export. An export record does not prove that you imported a calendar or received an alert. Using the tool does not require nationality, document numbers, names or exact dates of birth.
Where permitted, your browser stores this information for the website on which you use the tool. Loading the tool’s code from themeparkhelper.app does not synchronise it between websites. The current tool does not upload the trip as a server backup. Changing browsers or devices, blocking storage or clearing site data may make your original trip unavailable. With storage blocked, you can still calculate a timeline on the current page.
Once more than 90 days have passed after the trip’s last entered date, the tool deletes the expired local trip when it next loads. It cannot delete data in the background while your browser is closed. You can also use the tool’s clear function or clear site data in your browser. Clearing local data does not erase copies you have shared or imported into another calendar service.
ThemeParkHelper measurement
To learn whether the timeline is useful, ThemeParkHelper records a limited set of events on its trip timeline and refurbishment pages, such as creating a timeline, marking an item done or not needed, downloading or adding calendar events, seeing or selecting hotel links, and choices in “Which notification would you want?”. Those choices show interest only; they do not activate alerts or ask for an email address.
Each event contains the event name, random event and trip identifiers, the resort, the language and the page address without its query string or anything after #. The event and trip identifiers are not derived from dates or personal details. Depending on the action, an event may also include a task or action category, a broad accommodation-status category, the official hotel shown or selected, and a hotel-link or “Which notification would you want?” option. We do not record actual park or travel dates, hotel-search or stay dates, document-related choices, information about children, email addresses or text you type. Events go to a Google Analytics property used only for ThemeParkHelper, with ad personalisation and Google signals turned off. Google may set cookies or use identifiers under its own policies.
Events are recorded only when:
- On the Traditional Chinese site: your browser does not send Global Privacy Control (GPC) or Do Not Track (DNT), and you are not signed in to the site.
- On the English site: the same conditions apply, and you have chosen Accept for statistics cookies in the cookie banner.
- On both sites: your browser asks themeparkhelper.app whether measurement applies in your region. The answer is only “allowed” or “not allowed”, without the country; this check sets no cookie, and the country is not added to the tool’s measurement events. No measurement event is recorded in the EU, the European Economic Area, the United Kingdom, certain excluded territories, or when the location cannot be determined.
If you withdraw consent on the English site, the tool stops recording and clears its measurement record from your browser. The tool keeps a measurement record named tph.analytics.v1 in your browser so the same event is not counted twice. It contains a random trip identifier, duplicate-count markers and expiry times. Each marker expires within 90 days; a new event that needs duplicate-count protection can renew the trip record’s 90-day period. Expired records are removed the next time the tool is permitted to use browser storage. A Global Privacy Control (GPC) or Do Not Track (DNT) refusal, or withdrawal of cookie consent, also clears the record. Without measurement, the timeline, calendar downloads, printing and sharing still work.
Sharing and calendars
The current share link carries only selected park dates after the # in the URL; the page identifies the resort. It excludes travel dates, accommodation, document choices, progress, time zone and trip identifiers. Anyone receiving the complete link can read the dates and create their own trip. This part of the URL is not sent with an ordinary page request to the website server, but scripts on the page can read it. Share only dates you intend others to receive.
A calendar download creates a file on your device. Choosing a Google Calendar add link or importing the file into another service provides that service with the relevant event dates and content, handled under its privacy policy.
Partner booking links (when available)
When you follow a partner booking link, it carries a random commission-attribution code and any complete check-in and check-out dates you entered in the hotel-search area. It does not automatically use park or travel dates or include party details, document choices or preparation progress. Search dates remain temporary within the current search area and are not saved as accommodation in your trip. The partner receives connection information and handles further browsing and bookings under its own policy. This explanation does not mean links awaiting verification have been enabled.
Retention and deletion
| Data | Handling |
|---|---|
| Public comments | Generally retained while the associated article is public and the comment remains relevant; you may request deletion or anonymisation. The email address you enter is not published; it is kept with the comment and deleted with it. Commenters’ IP addresses are used to prevent spam and comment flooding and are cleared after 30 days. Spam and trashed comments are deleted automatically. |
| Subscription information | Used to send notifications while subscribed. Unsubscribing stops notifications and removes you from the site’s subscriber list. The WordPress.com account created on confirmation, and records Automattic holds, are handled under Automattic’s policies |
| Privacy-request correspondence | The approved policy is deletion of request emails and attachments 30 days after resolution, except for an ongoing dispute or legal retention requirement. |
| WordPress sent-mail logs | FluentSMTP keeps records that can be reviewed and resent. Deletion is configured after 30 days on the Traditional Chinese site and 14 days on the English site, separately from the privacy mailbox |
| Site backups | Our host, Rocket.net, backs up each site daily and currently keeps 30 copies for each site. Separately, UpdraftPlus backs up files and databases daily to Google Drive, retaining three scheduled copies of each; replaced and manual Google Drive backups are deleted within 7 days. |
| ThemeParkHelper measurement (Google Analytics) | The dedicated property keeps user and event data for two months, without resetting on new activity. Events use random identifiers, so we cannot find a particular person’s events by name or email address. |
| Browser measurement record (tph.analytics.v1) | Each duplicate-count marker expires within 90 days; a new one-time event can renew the trip record’s 90-day period. Expired records are removed on the next permitted use of browser storage. Cleared on GPC/DNT refusal or withdrawal of cookie consent; you can also clear site data. |
The privacy mailbox uses Zoho Mail’s free plan. Mail in Trash and Spam is currently deleted permanently after 30 days. Under Zoho’s policy, mail that leaves Trash stays on its servers for a further 30 days for recovery and is then purged. Zoho’s eDiscovery retention does not apply to this plan. Provider recovery copies may therefore remain for up to 30 days after we delete a message.
Providers, processing locations and your rights
The sites are hosted by Rocket.net in Singapore and delivered and protected through Cloudflare Enterprise; host access logs are kept for 72 hours, and security logs, which record IP address, country, request method and URL, are kept for 30 days. The sites use Automattic’s Jetpack/WordPress.com and Akismet for subscriptions and spam protection, Google for analytics, advertising and backup storage, and Zoho Mail for correspondence. ThemeParkHelper code is served from themeparkhelper.app; the request to download it is separate from uploading your trip.
You may contact oscar@yourdisney.com.tw to request access, copies, supplementation, correction, cessation of collection/processing/use, or deletion of personal data. We handle requests under applicable requirements and ask only for identity-verification information needed to process the request. Local browser trips are not uploaded as server backups; use the tool or browser controls to clear data on that device.
We will provide policy updates and their effective dates on this page. For website-use conditions, see the Terms of Use.