Skip to main content
All docs

Account and settings

Privacy and your writing

What Inkbreaker stores, what it does not, and who can see your work.

Your text and the prose engine

When you submit a piece for grading, your text is processed server-side to compute your metrics. It is discarded immediately after processing. It is not stored in the metrics pipeline, not sent to a language model, and not used to train any model.

Your text is stored only where you would expect: your notebook (your drafts and published pieces) and your submission history (exercise submissions). That storage is under your control.

Who can see your work

Drafts are private. Only you can see them.

Exercise submissions are stored in your notebook as drafts unless you choose to publish them. The fact that you completed an exercise, and your scores for it, are recorded in your history, but the text of your submission is not publicly visible unless you publish it.

Published pieces are public. Anyone can read them.

What the engine has access to

The prose engine only sees the text you submit in that moment. It does not read your previous submissions, your profile, or any other user data when it computes your scores. Your scores are a function of the text alone.

Account deletion

You can delete your account from Settings. You have 30 days to change your mind. After that it is permanent.

When the deletion completes, we remove your account, your profile, your drafts, your published pieces, your comments, and your submission history.

A few things you made with other people stay, because they no longer belong to you alone:

  • Stories you co-wrote in Exquisite Corpse stay published. Other writers wrote the rest, so the story belongs to everyone who built it. Your section remains, but your name comes off it and you appear as “Former writer”.
  • Feedback you gave another writer stays in their feedback history, credited to “Former writer” instead of your name.

Your name is scrubbed from these, so nothing identifies you once the 30 days are up.

Still stuck? Head back to Support to report a bug or reach the team.