Message safety
Before your first message, you agree to three rules. They apply to every message, from buyers and makers alike:
- Be kind. No harassment, hate, threats or sexual content, ever.
- Keep payments on Plukio. Never ask anyone to pay another way, and never pay that way yourself.
- No spam or scams. Messages are for the pieces and the people who make them.
You can read the full rules in the Terms.
Plukio never asks for your details in a message
Note
Plukio never asks for card details, passwords or sign-in codes in a message, and Plukio staff never write to you there.
A message that asks for those, or claims to come from Plukio, is a scam. Don't reply to it: report it. See Blocking and reporting.
"Not sent": why my message didn't go
Plukio checks every message when you press Send. A message that reads as a threat or as hate, asks for card, password or sign-in details, or speaks for Plukio is not delivered. You'll see Not sent and the reason, and you can change your message and send it again. The text of a message we stop is kept so that a person at Plukio can review it.
If you see "You're sending messages too quickly", wait a little and try again.
A warning on a message I received
Some messages are delivered with a warning under them, for you alone:
- "Pay only through Plukio checkout." The message asks you to pay some other way. A payment made outside Plukio checkout can't be refunded through Plukio.
- "Be careful with this message." It has signs of a scam, like a shortened link.
Each warning has a Report button. Our emails don't quote a message with a warning: they tell you to read it on Plukio, where the warning is shown.
"This message was removed by Plukio"
When a person at Plukio removes a message that broke the rules, both sides of the conversation see this line in its place.
"Your messaging on Plukio is paused"
If messages you sent broke the rules, we can stop your account from sending messages. We email you when we do. You can still read your conversations, block and report, and your orders aren't affected. If you think we got it wrong, reply to that email.
Last reviewed October 13, 2026