1. Draft First. Share Only When You're Ready.
Every poem you start on VerseLab can stay exactly that — a draft — for as long as you want. Nothing publishes automatically, and nothing requires an audience to exist. Write it, save it, close the app, come back to it next week. Your drafts live in their own space (My Drafts, plus a quick list right on your home screen) where only you can see them.
When you do open a draft back up, the same editor gives you both options side by side: Keep as Draft if it's still not ready, or Publish the moment it is. There's no separate "are you sure you want this to be private" step to forget — staying private is simply what happens unless you actively choose to publish.
2. Private Slams and Private Relays
Slams (head-to-head poem battles) and Relays (turn-by-turn collaborative poems) don't have to be public performances. When you challenge someone, you choose whether that Slam or Relay is public or private — a private one is only ever visible to the two of you, start to finish. You get all the same energy of writing against a deadline and a real opponent, without an audience watching every line land.
3. Private Group Slams — and Now Private Threads, Too
The same choice exists for group writing. A Group Slam inside a Club can be marked private to its participants even when the Club around it is public — so a handful of people can run a real, competitive, turn-based collaborative poem that nobody outside the group ever sees.
We recently extended that same idea to feedback itself: Club Threads can now be scoped to specific people instead of the whole Club. That means a private 1:1 conversation — one piece, one writer, one reader giving notes — is possible inside VerseLab Clubs, not just a whole-group discussion everyone can see.
4. The Bigger Picture: What's Actually Behind Safety for Minors
Privacy by choice matters for everyone. For anyone under 18, VerseLab backs it with defaults that are already on, and enforced in more places than just a settings screen a minor has to find and configure correctly.
Age verification, enforced at the database
A minimum age of 13 is enforced directly at the data layer, not only in a terms-of-service checkbox. Birthdate (and, where available, platform-level age signals from the App Store or Google Play) sets age-appropriate defaults the moment an account exists.
Enhanced Safety is on by default
New accounts start with privacy set to friends-only and Enhanced Safety switched on until a birthdate confirms the account isn't a minor's. It's a fail-safe default, not an opt-in a young user would need to discover and turn on themselves.
You can't quietly make it public
For a minor with Enhanced Safety on, turning friends-only content public isn't just discouraged by the interface -- it's blocked at the server level. There's no client-side workaround.
Messages require a mutual follow
A minor can only be messaged by someone they already mutually follow. A stranger simply cannot start a DM conversation with a minor's account -- this is enforced the same way the privacy lock is, not left to the sender's judgment.
Less discovery, less exposure
Minors are excluded from certain public rankings and recommendation surfaces by default, and comment/mention defaults are tighter -- reducing how often a young user's work surfaces to people they haven't chosen to connect with.
Guardian awareness, in plain language
From Account Settings, a minor can send their parent or guardian a one-time email confirming they're aware of the account. It's a straightforward awareness step -- not a surveillance dashboard, and it doesn't block using the app while pending.
None of this is guesswork about what helps. Research on teenagers and networked platforms describes a specific problem these defaults are built to solve: social platforms by default collapse every audience a person has -- classmates, family, strangers -- into one single, undifferentiated feed, a phenomenon researchers call "context collapse." Teens are left needing real tools to manage who actually sees what, because the platform itself erased the natural boundaries they'd have offline (Marwick & boyd, 2014).
And the risk that creates isn't abstract. A large survey of teenagers found that having strangers in a social network -- not just a large audience in general, but specifically unfamiliar people with access to it -- measurably increased both how much personal information teens disclosed and how often they later regretted posting it. The same study found that higher privacy settings were associated with lower disclosure in the first place (Xie & Kang, 2015). Keeping strangers out of a minor's DMs and discovery surfaces by default isn't a restriction for its own sake -- it's aimed directly at the specific mechanism the research points to.
Having strangers in a teen's social network increased both self-disclosure and regret of posting; higher privacy settings were associated with lower disclosure.
Xie & Kang, Computers in Human Behavior, 2015
5. The Short Version
A draft stays a draft until you say otherwise. A Slam, a Relay, or a Group Slam can be just between the people actually writing it. And for anyone under 18, the defaults that matter most -- who can message you, who can see you, whether your private work can quietly go public -- are already on, enforced where a setting can't be quietly bypassed, with a straightforward way for a parent or guardian to know the account exists. Share when a poem is ready. Not a moment before. For more on why that same philosophy shapes VerseLab Clubs and VerseLab Campus, see our companion piece on why privacy is a feature, not a limitation.
References
- Marwick, A. E., & boyd, d. (2014). Networked privacy: How teenagers negotiate context in social media. New Media & Society, 16(7), 1051–1067. https://doi.org/10.1177/1461444814543995
- Xie, W., & Kang, C. (2015). See you, see me: Teenagers' self-disclosure and regret of posting on social network site. Computers in Human Behavior, 52, 398–407. https://doi.org/10.1016/j.chb.2015.05.059