Wound Up

Your data stays yours.

Privacy notice · Last updated October 12, 2026

What we read

When you sign in, Ravelry gives Wound Up temporary access to your account. We read your Ravelry username and your projects, favorites, queue and stash, plus public details of the patterns you made, such as the category and the designer.

We only read. Wound Up never posts, edits, messages or changes anything on your Ravelry account, and we never see your Ravelry password.

What we keep

Nothing is saved on our servers. Your recap is worked out when you sign in, and the result, a short summary of counts and names for your cards, is kept in an encrypted cookie in your own browser for up to one day.

Our access to your Ravelry account is thrown away as soon as your recap is built, and in any case within ten minutes. To come back later, you sign in again.

“Sign out and forget me” at the end of your recap clears it from your browser straight away. You can also remove Wound Up’s access at any time from your Ravelry account settings.

Who else sees it

No one. Your recap is only shown to you, and we do not sell or share your information.

Cards you choose to share are public wherever you post them. They show your Ravelry username and can include names from your notebook, such as a project, a pattern or a designer. Look each card over before you share it.

Anonymous counts

We count how the site is used so we can keep it running and see what people enjoy: page views, how many recaps were made, how many cards a recap had, which knitting animal it ended with, and when a card was shared or saved.

These counts are collected with Vercel Web Analytics, which uses no cookies and does not identify you. Your username and the contents of your notebook are never included.

Hosting

Wound Up runs on Vercel. Like any web host, Vercel handles each request to the site and briefly sees technical details such as your IP address and browser type.

About this notice

Wound Up is an independent project and is not affiliated with Ravelry. If the way the site handles information changes, this page will be updated first.

Back to start