Hi, friends! Dress to Impress collects certain personal data. Here's how we use it!
First off, we'll never sell your private data, ever. It'll only be available to you and our small trusted staff—and we'll only use it to serve you directly, debug site issues, and help you share your creations with others.
To understand how people use our site, we use a service called Plausible. Every time you visit a page, we send them a small packet of information.
Plausible is a privacy-focused service. It doesn't store your IP address in a retrievable way, or add cookies to your browser, or track you across multiple websites or over time. Here's their data policy.
We also use a service called Sentry to track errors. When you encounter an error on our site, we send a copy of it to our Sentry account, to help us debug it later. This might sometimes include personal data, but Sentry will only share it with us. Here's their data policy.
We also use Linode and Fastly for web hosting. Linode stores our database, and handles most web traffic dealing with personal data. Personal data also travels through Fastly's servers temporarily, but they only store aggregate usage logs for us, not any personally-identifying data.
People use Dress to Impress to create, share, and communicate! Some of these things are public, some are private, and some are configurable.
Outfits are the central creation on Dress to Impress: combining a pet with items to make something that looks nice!
Users can log in and save outfits to their account. They can also share outfits by URL without logging in.
When you save an outfit to your account, it's somewhat private, but somewhat public.
It's private in the sense that there is no central place where another user can look up your list of outfits.
But it's public in the sense that anyone with the URL can see it—and, because the URLs are based on a simple incrementing global outfit ID, it's easy to look up all the outfits on the site.
We might change this in the future, to make the URLs hard to guess and genuinely private. Until then, we advise users to not to include sensitive data in the outfits they save to their account.
Logged-in users can track the Neopets customization items they own and want, by saving item lists to their account.
These lists are private by default, but can be configured to either be "public" or "trading" as well.
The "public" status means that anyone who knows your Dress to Impress username, or item list URL, can see this list.
The "trading" status includes the same visibility as "public", and additionally we'll advertise that you own/want this item on its public list of trades.
When a logged-in user enters their Neopets's name on the site, we look up that pet's public data on Neopets.com.
Sometimes, this will download new public outfit data that we've never seen before. For example, you might show us a Draik (a species of Neopet) wearing a new item, and we don't have data for a Draik wearing that item yet.
When that happens, we'll extract that specific piece of data from your pet's outfit, and save it to our database, for other users to mix and match into their own outfits. This process is called "modeling".
When you model new data for us, it's separated from your pet. Users can't discover what pet modeled a certain piece of data, or what else that pet was wearing.
But, if you're logged in when modeling, we'll publicly credit your account for the new "contribution". This will appear in a number of places, including a list of the most recent contributions, and it will add points to your account that contribute to a public high score list. This will publicly display your username.
Right now, modeling contributions from logged-in users are always public. This is a limitation of our system, and we might change it in the future! For now, if you would like to have your public contributions removed from the site, please use the contact link at the bottom of the page.