Your work does not train a model.
Nothing you give it trains a model, on any plan, Free included, unless you send it to us as feedback. The rule is written into our Terms, not left to a setting.
Sending a support request alone is not training consent. If you choose to contribute an example, that is a separate, explicit choice on that example.
Read the exact wording →Your chats stay in your browser.
Chats in the web app are kept in your browser, encrypted with a key that never leaves it. They are not on Wynfall’s servers, and they do not follow you to other devices yet.
You can delete every chat kept in a browser from Settings, under This browser.
To answer you, your message does go to our hosted model, and our access logs record metadata such as key, model, tokens, status and latency.
Signing in.
You sign in with an emailed code or with a passkey, and you can add passkeys in Settings. Changing passkeys needs a sign-in from the last 10 minutes.
Sign-in cookies are marked HttpOnly and Secure.
How staff changes are checked.
Changes staff make to accounts and limits need a fresh confirmation, an emailed code or a passkey, and they are recorded in an audit log.
Downloads are made for your account.
Wynfall Desktop and Wynfall Code downloads come from a link made for your signed-in account. The link names one file and lasts 10 minutes. Each installer lists its checksums on the download page so you can check the file you got.
See the downloads →This website.
The site runs no analytics or advertising trackers, and it is served over HTTPS. Forms use Cloudflare Turnstile to block automated abuse, and it loads only when you start filling one in.
Read the privacy notice →Report a security problem.
Write to hello@wynfall.dev with what you found and how to reproduce it. We will answer, and we ask that you give us time to fix it before you share it. Our contact details are also in security.txt.