Their Christmas list.
Not their data.

A wishlist shouldn’t need a life story.

Last updated October 3, 2026.

What we save

Your optional list title, product links, gift names, notes, priorities, ordering, anonymous gift claims, and timestamps. The list builder does not ask for product photos. Existing lists may still contain image links saved before this change. We store a hash of your private edit key, not the key itself. Please avoid private information in names and notes. To make repeated product imports faster, we cache successful product previews for up to six hours. Deleting a list does not immediately clear those product previews. Wishlists do not load retailer images. Gift inspiration pages may show product images hosted by other sites; those servers may receive your IP address.

What we don’t ask for

No account, email, password, age, birthday, home address, school, location, phone number, or social profile. We do not sell personal data or build child profiles. Our business is eligible shopping commissions.

Public means anyone with the link

Your public list can be read by anyone who has its URL. It is not a private vault. We ask search engines not to index user lists, but that is not an access restriction. Recipients can forward links, save screenshots, or copy information.

Your edit link is a key

Keep it somewhere safe. Anyone with it can edit or delete the list. We don’t require an email, so we cannot recover a lost edit link for you. Edit pages do not send their URL as a referrer. Share the public link, not the private one.

Gift coordination and surprises

Shoppers can anonymously claim a hint. Claims are hidden in the editor and creator view on the device that saved the list. Someone who opens the public list in a different browser can see shopper claims. We cannot guarantee secrecy without identifying the creator. A claim is not a purchase or reservation at a retailer.

Analytics and basic security

We count daily product events, such as list starts, shares, and shop clicks, without including names, notes, product URLs, edit keys, persistent visitor IDs, or advertising identifiers. These aggregate counts can show item additions and completion time buckets. For rate limits, we store an hourly hash of the requesting IP address, and remove expired rate records as new requests arrive. There are no ad pixels or session replay scripts. Our hosting provider may process network and security logs to operate the service.

What stays on your device

We use browser storage for a creator-view preference and anonymous claim release keys. This helps keep surprises out of your own shopper view and lets a shopper unclaim a gift from the same browser. Clearing browser data removes these keys. Lists themselves are stored on our servers.

Affiliate links

On an eligible shop click, we may add approved affiliate tracking. Otherwise we use the original product URL. We never replace your chosen product to earn a commission. Retailers and affiliate networks have their own privacy practices and may use cookies after you leave SantaHints.

Optional Rakuten links

Our shopper tips link to Rakuten using a referral code. Joining is optional and happens on Rakuten’s website, where its account requirements and privacy practices apply. SantaHints does not receive your Rakuten account details or load Rakuten tracking scripts. We count referral-link clicks only as aggregate events.

Deletion and retention

Delete a list using its private edit link. This removes the saved list and its gift claims from the active database. Public links stop working. Lists expire one year after their last edit; expired lists are inaccessible immediately and are purged as new lists are created. Aggregate event counts contain no list or visitor identity. Hosting backups and security logs may persist under the provider’s retention policies. We cannot remove copies other people saved.