- It can keep relevant transaction context connected and provide reporting tools.
- It cannot make every member truthful, every parcel successful or every outcome predictable.
- Protection weakens when users move communication or payment outside the supported system.
Account controls reduce avoidable exposure
If you suspect account access, use the current password and support controls promptly. Do not send credentials, one-time codes or recovery links to another member. Official support should not need your password.
Listings and badges provide context, not certainty
A structured listing lets buyers inspect product, options, price and shipping expectations before paying. Seller history, reviews and verification may add context. No single badge confirms that a particular description is accurate or that an order will have no problems.
Use several signals together. When profile claims, listing details and platform messages conflict, ask one focused question or leave the transaction. Report a listing when the issue concerns prohibited content or a clear rule breach rather than negotiating privately.
Each layer protects a different part of the journey
| Layer | Useful record or control | User responsibility |
|---|---|---|
| Account | Login and recovery tools | Protect credentials and associated email access. |
| Offer | Listing, profile and visible trust signals | Read the current details and resolve material contradictions. |
| Conversation | Platform chat linked to the account | Keep item-related promises in the supported channel. |
| Payment | Checkout and order status | Reject external transfers or links sent by members. |
| Delivery | Dispatch and carrier information where available | Use valid details and retain relevant receipt evidence. |
| Incident | Block, report, dispute or support route | Submit a concise timeline and proportionate evidence. |
Platform chat preserves boundaries and evidence
Keep availability questions, selected options and dispatch agreements in SecretUndies chat. Moving to a personal messenger can expose phone numbers or social identities and remove essential context from the order. Sellers can decline intrusive questions; buyers can end a conversation that becomes pressuring or unrelated.
A message history does not guarantee a decision in either party's favour. It gives support relevant material to assess. Keep the record concise and avoid sharing documents or personal background that the order does not require.
Checkout connects payment to the item
Before confirming, review the selected listing, option, delivery choice and final total. Use only the payment methods presented in the live checkout. A private transfer, gift card request or wallet address sent in chat separates money from the supported transaction and may breach marketplace rules.
Read the current buyer protection and dispute terms. Payment handling can provide traceability, but it is not an absolute guarantee. Eligibility, evidence and the facts of the order can affect any review.
Reporting works best with specific facts
For conduct, identify the message or account action that crossed a boundary. For an order issue, collect the order number, listing, relevant chat, payment status, dispatch status and focused evidence of the discrepancy. Do not publish another person's private information while seeking help.
The dispute procedure explains the order route. The verification guide describes what badges can signal, and the Trust Report provides the wider trust context.
Limits that matter
Does verification remove the need to check a listing?
No. It is one signal about an account or process. Always assess the specific offer, messages and checkout.
Can support review a private transfer?
Do not rely on that. Private payment is outside the connected checkout record and may fall outside marketplace protection.
What should a report contain?
Name the account or order, describe the exact issue, give a short timeline and attach only relevant evidence.
