Credential boundary
We do not store your Disney credentials. Ever.
We do not ask for your Disney login. We do not store it. We never will. SpotSitter watches for availability without tying your watch to your Disney account.
User credentials
Never requested
Your Disney username, password, and account-specific material do not belong in SpotSitter.
Booking account
You control it
If Disney asks you to log in while booking, that happens on Disney's site.
Saved watches
Criteria only
We need the place, party size, date window, and where to send your alert. Not account access.
The hard line
SpotSitter never asks for, accepts, stores, transmits, or uses end-user Disney usernames, passwords, MyDisneyExperience credentials, OneID tokens, SWID cookies, or user-bound Disney session material.
If someone claiming to be SpotSitter asks for your Disney password or account access material, do not provide it. SpotSitter does not need it to run a watch.
What we do need
A watch needs your email address, your phone number if you want SMS, the restaurant or experience you want, the party size, and the date or time window that would make the alert useful.
Those details describe the opening you want. They do not identify your Disney account, unlock your Disney account, or let SpotSitter act as you.
What a watch contains
A watch contains practical search criteria: venue or experience, party size, date window, meal period, and notification preferences. Those criteria let SpotSitter decide which openings should trigger an alert.
A watch is not connected to your Disney account, and SpotSitter does not use your Disney identity to monitor or complete reservations.
Where booking happens
When an alert arrives, you tap through to Disney and complete the booking directly with Disney. If Disney requires login, you log in there with your own account and make your own booking decision.
SpotSitter does not fill in Disney forms, submit booking requests, make payments, or bind a watch to a specific Disney account.
Related transparency pages