Privacy and support boundaries

Published and reviewed

A safe default

Treat journal content as highly personal. If a user asks whether support can casually look inside entries, recover deleted writing, or inspect private content, the safest answer is to avoid promising access unless there is a clearly documented support path.

What support should say carefully

• Bug reports can be investigated without asking users to share more journal text than necessary.
• Deleted account data should be treated as permanently removed unless the team explicitly confirms otherwise.
• If a user is worried about keeping a copy of their writing, point them to export options first.