Privacy
Last updated 17 November 2026
This policy explains what personal data TrustedWins collects, why, who it is shared with, how long we keep it, and the rights you have. It covers sellers, the clients named in case studies, and buyers who read pages.
The short version
- We collect what we need to run TrustedWins and to keep its records honest. We do not sell personal data, and we show no adverts.
- No advertising or tracking cookies. Buyers reading a page get no cookies at all.
- Private client details and original screenshots are stored encrypted. Only the cleaned copy a seller publishes is public.
- We never see anyone’s ID document or selfie. Our provider runs the ID check and tells us the result.
- You can ask to see, correct or delete your data at any time: support@trustedwins.com.
1. Who is responsible
TrustedWins is run by The Candid Store LLC, 30 N Gould St, Ste R, Sheridan, WY 82801. For data protection law we are the “controller” of the data described in this policy, with one exception. When a seller enters details about their own clients, or receives a message from a buyer, the seller decides how that data is used and we handle it on the seller’s behalf (see the data processing terms). For those, you can contact the seller or us.
Questions and requests about your data: support@trustedwins.com.
2. What we collect
If you are a seller (you have an account)
- Account. Your email, from Google or LinkedIn when you sign in. We don’t receive your password, and we don’t use your profile photo or contacts from them. The sign-in provider may also send your name and a link to your photo; we don’t use them for anything else.
- Your page. What you choose to publish: name, headline, photo, links, your stated numbers and your case studies. This is public once your page is live.
- Your signed statement. The name you sign with, the date and the wording you agreed to.
- ID check (optional). If you choose it, our provider Stripe checks a government ID and a selfie. Stripe sends us your name, date of birth and the country of the document. We keep your name in encrypted form, a one-way code made from your name and date of birth (to stop one person holding several accounts or returning after a ban), the country, and the result. We do not keep your date of birth, and we never receive the images.
- Payments. Stripe takes your card details; we never see them. Stripe holds your cards and billing history under its own privacy policy. We keep your plan, the amounts, dates and Stripe’s reference numbers.
- When you cancel. The reasons you pick, the one follow-up answer for each, a few words if you choose “Other” (up to 200 characters), whether you would come back, an optional note on what could keep you (up to 500 characters), and the plan and date. Please don’t put other people’s details in the notes. We collect this to improve TrustedWins and to decide on private offers. Only TrustedWins administrators can see it; we don’t show it to other sellers or on any page, and we don’t share it.
- Security. A one-way code of your IP address and of a device cookie, used to notice when a seller tries to approve their own case study.
- Support. Messages and screenshots you send us, stored encrypted, with basic technical details (page, browser, device type).
- Use of the service. When you last signed in, your email choices, how you first reached us (for example the site that linked to us), and how many AI drafts you used.
If you are a client named in a case study
- What the seller enters. Your name, email, role, optional location, your results, the story and screenshots. Your full name, your email, the seller’s private notes and the original screenshots are stored encrypted and are never public. The page shows only the display name chosen for it (which can be initials or “Anonymous”), your role, the results, the story, and the screenshots after private details were hidden.
- When you verify. If you sign in with LinkedIn, LinkedIn sends us your name, email, whether that email is verified, your LinkedIn account ID and whether you have a profile photo. We keep them encrypted, plus one-way codes used to match and to prevent fraud. We do not keep your LinkedIn password, access, photo or connections. If an ID check is used instead, it works as described for sellers above.
- Your answer. Whether you approved, asked for changes or said no, any note you wrote, the date, the version you saw, and a one-way code of your IP address.
- If you say no. The case study is removed, and we keep one-way codes of your name and email so that a new case study about you can’t be published.
We do not email clients. The seller sends you the link themselves.
If you are a buyer or visitor
- Reading pages. No account, no cookies. We count visits with a code that changes every day, and we never store your IP address (see section 6). The code can’t be linked back to you, unless you send a message: then that day’s code and how you reached the page are saved with it.
- Sending a message to a seller. Your name, email, phone number, your answers and your message. They go to that seller, with how you reached the page (for example a shared link). We also keep a one-way code of your IP address for 90 days to stop spam.
- Reporting a page. The reason, your note, your email if you choose to give it, and a one-way code of your IP address.
- Checking a record. The verify page takes a record number or link. We don’t keep who looked up what.
3. Why we use it, and on what legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Providing your account, page, case studies and plan | Seller account, page and payment data | Our contract with you |
| Keeping the record of who signed and who approved | Signed statements, client sign-in details and answers | Our legitimate interest in an honest, checkable record, and that of buyers who rely on it |
| Preventing fake approvals, duplicate accounts and abuse | Security codes, ID check results, block lists, Stripe's card fingerprint (a code for a card, not the card number), automated checks | Our legitimate interest in preventing fraud |
| Running an ID check | ID document and selfie (processed by Stripe) | Your consent, given to Stripe before the check starts |
| Passing a buyer’s message to the seller | Buyer’s name, contact details and message | Steps you asked for before a possible contract with the seller |
| Counting visits and showing sellers their results | Daily visit codes, referring site, device type | Our legitimate interest in basic, privacy-friendly statistics |
| Service emails (receipts, plan, verification, deadlines) | Seller email | Our contract with you |
| Weekly reports and reminders about your page | Seller email | Our legitimate interest; you can turn each one off |
| Updates, news and offers about our own service | Seller email | Our legitimate interest in keeping our customers informed; you can turn it off in every such email and in your email settings |
| Learning why sellers leave, improving the service, and deciding on private offers | Cancel answers, plan and dates | Our legitimate interest in improving the service and in making offers that fit |
| Fixing errors and keeping the service secure | Error reports with personal details removed | Our legitimate interest in a working, secure service |
| Tax, accounting and legal claims | Payment records, records of removals | Legal obligation, and our legitimate interest in defending claims |
Where we rely on legitimate interest you can object (section 10). Where we rely on consent you can withdraw it at any time.
4. Automated checks
When a client answers a verification link, our system runs automatic checks: for example whether the name and verified email match what the seller entered, and whether the answer came from the seller’s own account or device. If the details don’t match, the answer isn’t recorded. If something looks unusual, the approval is held and a person on our team reviews it. If you think a check got it wrong, write to support@trustedwins.com and a person will look at it.
5. Writing help from AI
Sellers can ask TrustedWins to turn their notes into a draft. For that, we send our AI provider (Anthropic) the seller’s notes, the client’s first name as displayed, role and result numbers. We do not send a client’s full name or email, or any screenshots. Under its business terms, the provider does not use this data to train its models.
6. Cookies and visit counting
We use only the cookies needed to make TrustedWins work and to keep it secure. That is why there is no cookie banner.
| Cookie | Who gets it | What for | How long |
|---|---|---|---|
| Sign-in cookie | Sellers | Keeps you signed in | Until you sign out, or about a year |
| Device cookie | Sellers | Security: lets us notice a seller approving their own case study | 1 year |
| Verification cookies | Clients | Keep you signed in while you verify a case study | Up to 2 hours |
- Buyers reading a page get no cookies from us.
- Your browser also stores a few unfinished drafts (for example a half-written form) so you don’t lose them. They stay on your device.
- On the checkout form, Stripe’s payment form may set its own security cookies and run its own fraud check (hCaptcha). It may also load Apple Pay or Google Pay to see whether they are available on your device, which contacts Apple or Google. When you send a form, our bot check (Cloudflare Turnstile) may set its own security cookie.
- Visit counting. We count page visits ourselves, without cookies. Each visit is turned into a code made from the day, the page, and your IP address and browser type. The code changes every day, and we never store the IP address itself. It can’t be linked back to you, unless you send a message to a seller: then that day’s code and the visit source are saved with the message. We respect the Global Privacy Control signal: if your browser sends it, we don’t count your visit.
7. Who we share data with
We share personal data only with the companies that help us run TrustedWins, each under a contract that limits what they may do with it:
| Provider | What for | Data |
|---|---|---|
| Supabase | Database, file storage and sign-in | All account, page and case study data |
| Railway | Hosting the website | Data passing through the site |
| Stripe | Payments and ID checks | Email, payment details; ID document and selfie for ID checks |
| Resend | Sending emails to sellers | Seller email and the email content |
| Anthropic | AI writing help | See section 5 |
| Sentry (EU) | Error reports | Technical error data with emails and tokens removed |
| Cloudflare (Turnstile) | Checking a form is sent by a person | IP address and browser signals, when you send a form |
| Google and LinkedIn | Sign-in | Your sign-in happens on their site; they tell us your email and name |
| Apple and Google (wallets) | Apple Pay and Google Pay at checkout, if you use them | Handled by Stripe and the wallet provider |
- Sellers. A buyer’s message goes to the seller it was sent to. A client’s answer goes to the seller who asked.
- The public. A live page, its case studies and its records are public, and may be indexed by search engines.
- Video. If a case study has a video, we show a preview image that we fetch ourselves. Your browser contacts YouTube, Vimeo or Loom only if you click to watch.
- The law. We may share data when the law requires it, or to protect our rights or someone’s safety.
- A change of owner. If TrustedWins is sold or merged, data moves to the new owner under this policy.
We do not sell personal data, and we do not share it for advertising.
8. Where data is processed
The Candid Store LLC is based in the United States, and our providers process data in the United States and the European Union. When personal data from the EEA, the UK or Switzerland is sent to a country without an adequacy decision, it is protected by the European Commission’s Standard Contractual Clauses (and the UK Addendum), or by the provider’s certification under the EU–US Data Privacy Framework. You can ask us for a copy of the relevant safeguards.
9. How long we keep it
| Data | Kept for |
|---|---|
| Your account, page and case studies | Until you delete them. Deleting your account removes them from our live systems straight away, and from backups within 30 days. |
| Case studies after a plan ends (cancelled, or unpaid after the retry days) | 6 months from the day the plan ends. Then the case studies, their verification records and certificates, and their screenshots are permanently deleted. We email you before. Subscribe again within that time and they come back as they were. Your client cards stay on your page. Deleting your account deletes everything at once. |
| Private client details, notes and original screenshots | Until the case study or the account is deleted. If a client has a case study removed, within 30 days of the removal. |
| A client’s sign-in details (encrypted) | While the case study exists, then deleted within 30 days. |
| One-way codes that block a removed case study or a banned person from returning | For as long as we run the service. They can’t be turned back into a name or email. |
| Messages from buyers | Until the seller deletes them or closes the account, and at most 24 months. |
| Visit counts | 400 days, then deleted. |
| Security codes (IP and device) | 90 days. |
| Reports and admin logs | 24 months. |
| Support messages | 24 months after the ticket is closed. |
| Error reports | 90 days. |
| ID check | We keep the result and your encrypted name while you have an account. We ask Stripe to delete the document and selfie images once the check is finished; Stripe may keep some data to meet its own legal duties. |
| Cancel answers | While your account exists. Deleting your account deletes them. |
| Payment records | 7 years, for tax and accounting. |
| Card details and billing history held by Stripe | Held by Stripe, not by us, for as long as Stripe’s own policy says. |
10. Your rights
Wherever you live, you can ask us to:
- tell you what data we hold about you and give you a copy;
- correct data that is wrong;
- delete your data;
- stop or limit a use you object to, including uses based on legitimate interest;
- give you your data in a portable format;
- have a person review an automated decision (section 4).
Write to support@trustedwins.com. We answer within one month and we don’t charge for it. We may need to check it is really you. Some data can’t be deleted straight away, such as payment records we must keep by law.
- Sellers can also delete a case study, a message or the whole account from inside the app, and change email choices from any email or in Billing.
- Clients can have a case study about them removed through their verification link, or by writing to us.
- Buyers who sent a message can ask the seller or us to delete it.
If you are in the EEA, the UK or Switzerland, you also have the right to complain to your local data protection authority. If you live in a US state with a privacy law, the rights above apply to you; we do not sell or share personal data as those laws define it, and we do not treat you differently for using your rights.
11. Security
Data is encrypted in transit. Private client details, original screenshots and support messages are also encrypted in storage, with keys kept separately. Our team signs in to the admin console with a passkey. Opening a client’s name or an original screenshot needs a typed reason and is logged. Other admin reads, such as support messages, happen inside that passkey-protected console. No system is perfectly secure; if a breach affects your data, we will tell you and the authorities as the law requires.
12. Children
TrustedWins is for adults. Accounts are for people aged 18 or over, and case studies must not be about children.
13. Changes
If we change this policy we will update the date at the top. If a change is significant we will email account holders before it applies.
14. Contact
The Candid Store LLC, 30 N Gould St, Ste R, Sheridan, WY 82801. Email: support@trustedwins.com.