What's New

Implemented in the local editor code

The 0.9.5.0 development record includes separate local project vaults for accounts and guests, ownership checks on project changes, and clearing of the active canvas and basket when the account changes. Other open tabs lock when the session changes. Legacy data is preserved rather than assigning ambiguous older guest work to the next login.

These protections separate local sessions. They do not verify age, provide device-level encryption, or enable cloud backup. Production availability of that historical version remains unconfirmed. Gallery inspiration examples do not provide community sharing.

Planned community safeguards — not enabled

Sharing, age assurance, community moderation and the reporting/appeals workflow are not implemented. The following requirements describe the planned safety programme, rather than features available today.

• Private defaults and user choice. Keep projects private, explain what submission would reveal, publish only approved artwork, and provide unpublish, hide and block controls. This applies the design guidance on safer defaults and user controls [2].
• Age-appropriate access. The proposed product policy is 16+ editor access, with ages 16–17 limited to their own private local canvases, and an assured 18+ community pilot for browsing, publishing and sharing. These are PBN Studio policy choices, not statutory ages taken from Australian guidance. Google sign-in, a payment or an age declaration would not establish adulthood. Age checks need additional safeguards and privacy review; see age assurance guidance [3].
• Family-safe publication. Plan automated screening and trained human review before artwork is published; uncertain or failed checks leave it unpublished. Exclude sexual exploitation, non-consensual intimate imagery, public nudity, graphic violence, hate and identifying/contact details. Adult nudity mode stays disabled, and paid access never bypasses safeguards. The content-safety foundation [4] informs this approach; the specific publication policy is ours.
• Reporting and accountability. Plan accessible reporting without registration or payment, protected reporter identities, case acknowledgements, appeals, incident escalation and an emergency publication pause. Do not launch comments, direct messages or ratings in this programme. See the guidance on reporting tools [2] and transparency [5].
• Minimise sensitive data. Plan eligibility evidence without storing raw identity documents or exact birth dates in PBN Studio, and keep age evidence out of public attribution. South African children's-data obligations need qualified review using the Information Regulator's guidance [6].

References

1. eSafety Commissioner — Safety by Design principles. The three principles used to frame our safety requirements.
2. eSafety Commissioner — Empowering users to stay safe online. Private defaults, user controls, accessible reporting and plain explanations.
3. eSafety Commissioner — Age assurance trends and challenges. Methods, limitations and complementary safeguards; the issues paper covers developments through June 2024.
4. eSafety Commissioner — Dealing with illegal and restricted content. Prevention, detection, moderation and response.
5. eSafety Commissioner — Creating transparency frameworks. Explaining safety practices and assessing their effectiveness.
6. Information Regulator, South Africa — Guidance Note on Processing Personal Information of Children (PDF, 28 June 2021). Source for the planned children's-data review under POPIA.

References checked on 17 October 2026. Our proposed age limits and feature restrictions are product decisions informed by these sources.