Nothing about you travels further than you chose, and every step outward is something you switched on.

What you posted, as you wrote it.

kept until the member deletes the post. No clock ages out a member's own thing while they still use it. On account deletion, 30 days (retention policy §5).

Carried out by the code

What you wrote in reply under a post, and which reply you were answering.

kept until the member deletes the comment; on account deletion, 30 days (retention policy §5).

Carried out by the code

What you wrote in reply to somebody else.

kept until the member deletes the comment; on account deletion, 30 days (retention policy §5). The live comment table is post_comments; this is its predecessor.

Decided — the code for it is not written yet

Which mark you put on which post in the live feed. Itemised, like post_reactions, and carrying no weight anywhere.

kept until the member removes the reaction, or the post it sits on is deleted; on account deletion, 30 days (retention policy §5).

Carried out by the code

Which of the eight marks you put on which post. Itemised, and carrying no weight anywhere.

kept until the member removes the reaction, or the post is deleted; on account deletion, 30 days (retention policy §5). The live table is reactions.

Decided — the code for it is not written yet

Which posts you kept for later.

kept until the member unsaves, or the post is deleted; on account deletion, 30 days (retention policy §5).

Carried out by the code

What you saved to read later.

kept until the member unsaves, or the post is deleted; on account deletion, 30 days (retention policy §5). The live table is saves.

Decided — the code for it is not written yet

Any picture, video or audio you attached to a post: the file, its name, its size, its dimensions and the description you wrote for it. The row is keyed to your post rather than to you, and your post is yours.

kept with the post it belongs to, and goes when the post goes.

Carried out by the code

Any story you posted -- its text, its picture or clip, its caption, who you let see it, and the hour it expires.

its own expires_at, or the member deletes it first — whichever comes first. Gone at expiry, by design.

Carried out by the code

Which stories you opened, and when.

kept with the story, and goes when the story goes.

Carried out by the code

Any document you put in the reading room: its filename, its type, how many pages, where it is stored and what sensitivity it was labelled. It was listed as "government documents in the reading room" until 2026-09-08 — true of what most of them CONTAIN and false of the row, which carries owner_id. A filename is often the most revealing field in a table.

kept until the member removes the document; with the account.

Decided — the code for it is not written yet

Our log of loading each document you put in the reading room: when, how, and how it went. Your account is on the row as the person who loaded it.

kept until the member removes the document it belongs to; with the account.

Decided — the code for it is not written yet

Letters you wrote and letters written to you: the subject, the body, and when each was opened. The body is sealed at rest and only the two of you can read it; it is in your file because it is yours.

each party deletes their own copy; the row goes when both have. On account deletion, the deleting party's side goes at 30 days and the other party keeps theirs.

Decided — the code for it is not written yet

Who you blocked, and when. Never shown to the person you blocked.

kept until the member unblocks. Never shown to the person blocked, before or after.

Carried out by the code

Who you muted, and when. Never shown to the person you muted.

kept until the member unmutes. Never shown to the person muted.

Carried out by the code

Who you asked to connect with, who asked you, and what each of you answered.

answered, withdrawn, or the account goes. A declined request is not kept as a record against anyone [confirmed by the founder, 13 Sep].

Carried out by the code

Who you are connected with. Your name is on the row from either side.

kept until either party ends it; with either account.

Carried out by the code

Who and what you chose to follow.

kept until the member unfollows; with the account.

Carried out by the code

Which groups you belong to, your role in each, and when you joined.

kept until the member leaves, or is removed by a steward; with the account.

Carried out by the code

Groups you asked to join, the answers you gave to their entry questions, and what was decided.

decided or withdrawn; the answers to the entry questions go with the decision [confirmed by the founder, 13 Sep]; with the account.

Carried out by the code

Any group you founded: its name, its purpose, its rules, its entry questions and who may see it. Joining one is separate and is listed under group_members.

kept while the group exists; a group is its members' place, not a member's own thing, so no member's clock ends it.

Decided — the code for it is not written yet

Any event you created: its title, its description, and the address you gave for it. Attending an event is separate and is listed under event_rsvps; ORGANISING one puts your account on the row and your chosen address in it, and some organisers use their own home.

the campaign's timeline decides — continued (kept live), archived (kept, read-only) or deleted (gone), the organiser's choice at the deadline; archived by default after 30 days of silence [30 confirmed by the founder, 13 Sep]. Silence archives; it never deletes a campaign other people joined and never silently extends one.

Decided — the code for it is not written yet

Which events you said you were coming to.

kept until the member withdraws, or the event is archived or deleted. On an archived event the count stays and the names go [confirmed by the founder, 13 Sep].

Decided — the code for it is not written yet

Events you help organise, and the role you were given on each.

kept until the organiser removes the role, or the event ends its timeline.

Decided — the code for it is not written yet

A milestone an organiser set on an event -- a target, a unit, a figure reached and a link to the evidence. It is keyed to the event, not to a person; the organiser's own account is on the event row, which is listed in your file under events.

kept with the event, and goes when the event goes.

Carried out by the code

A reminder scheduled against an event and an audience, not against a person. Nothing writes this table yet; if a reminder ever names who asked for it, it moves to your file.

kept with the event, and goes when the event goes.

Carried out by the code

Any petition you started: its title, its description and what it is aimed at. Signing one is separate and is listed under petition_signatures; starting one puts your account on the row.

the petition's timeline decides, on the same rule as an event.

Decided — the code for it is not written yet

Petitions you signed, with the name you signed under.

kept with the petition's timeline, on the same rule as an RSVP.

Decided — the code for it is not written yet

Which lessons you have finished.

the learner's own record — kept until the learner clears it, or the account goes. A learner's history is theirs to keep, the same as a post.

Carried out by the code

Your answers to lesson questions, and whether they were right.

the learner's own record — kept until the learner clears it, or the account goes.

Carried out by the code

Which pages you opened while signed in, so a course can pick up where you left off.

the learner's own record — kept until the learner clears it, or the account goes.

Carried out by the code

Which milestones you have reached.

the learner's own record — kept until the learner clears it, or the account goes.

Carried out by the code

Reading-level readings taken to pitch a lesson at you, and the date of each.

the learner's own record — kept until the learner clears it, or the account goes.

Carried out by the code

Listings you posted, as you wrote them.

the listing's own expiry, or the member takes it down; with the account.

Decided — the code for it is not written yet

Work you offered or asked for, in your own words. There is no wage figure in it because the board never stores one — only whether the pay is hourly, per job, unpaid or still to be agreed.

the listing's own expiry, or the member takes it down; with the account.

Decided — the code for it is not written yet

A business listing you submitted or claimed, including the email address, phone number and street address on it, anything you wrote in the note from the owner, how the claim was made and when. It was listed as being about a place rather than a person until 2026-09-08. A place does not have an email address; the person who claimed the listing does.

the listing's own expiry, or the member takes it down; with the account.

Decided — the code for it is not written yet

Your email address, if you gave it to a mailing list.

kept until the person unsubscribes.

Carried out by the code

Which lists you are on.

kept until the person unsubscribes.

Carried out by the code

Topics you TOLD us you were interested in. Never a topic we guessed.

kept until the person unsubscribes.

Carried out by the code

The one-click unsubscribe link issued to you.

kept until the person unsubscribes; the token is marked used, never re-served.

Carried out by the code

Which emails were sent to you, and when.

three years.

Carried out by the code

When you opted in or out, and from where — the record that proves we had your consent.

there is no grace period and no scheduled job between their request and the erasure. F2 revised: 'on account deletion EVERYTHING goes -- suppression row, moderation action record, consent event included.' It was KEPT under the 2026-09-13 ruling, because a consent trail you cannot produce is a consent you did not have. Sole exception anywhere in this schedule: content already under a legally required report (18 U.S.C. 2258A -> NCMEC), preserved for the statutory period only.

Carried out by the code

Your address, if you asked never to be emailed again. Kept precisely so the request is honoured.

there is no grace period and no scheduled job between their request and the erasure. F2 revised: 'on account deletion EVERYTHING goes -- suppression row, moderation action record, consent event included.' It was KEPT under the 2026-09-13 ruling: 15 U.S.C. 7704(a)(4) and 16 C.F.R. 316 -- erase the row and the next campaign mails the person who asked not to be mailed. That reason has not stopped being true; he weighed it against a person's right to leave and ruled the other way. THE CONSEQUENCE IS FLAGGED FOR COUNSEL: somebody who unsubscribed and then deleted their account can be mailed again if their address re-enters a list from another source. Sole exception anywhere in this schedule: content already under a legally required report (18 U.S.C. 2258A -> NCMEC), preserved for the statutory period only.

Carried out by the code

Posts or people you reported, why, and what was decided.

three years after the last action; the record of the ACTION is kept and the content is destroyed.

Carried out by the code

Anything you flagged for review, and what a reviewer decided about it -- and, if something of yours was flagged, that fact and the decision.

three years after the last action; the record of the ACTION is kept and the content is destroyed.

Carried out by the code

A report you made, or a report about something of yours, as it moves through review: who reported, who reviewed, and the outcome.

three years after the last action; the record of the ACTION is kept and the content is destroyed.

Carried out by the code

Each action a reviewer took on a report that names you, with the reviewer's own account on it. Created 2026-09-12; nothing writes it yet.

there is no grace period and no scheduled job between their request and the erasure. F2 revised: 'on account deletion EVERYTHING goes -- suppression row, moderation action record, consent event included.' It was KEPT under the 2026-09-13 ruling, because it holds no content and deleting it destroys the ability to answer who acted and when. Sole exception anywhere in this schedule: content already under a legally required report (18 U.S.C. 2258A -> NCMEC), preserved for the statutory period only.

Carried out by the code

Errors you reported to us, and what we did about them.

the correction itself is a permanent record — the ledger is the promise (retention policy §5). The reporter's email address is kept three years and no longer.

Decided — the code for it is not written yet

Listings you reported, and why.

three years after the last action.

Carried out by the code

Job listings you reported, and why.

three years after the last action.

Carried out by the code

A role you hold here, if you hold one.

kept — keeping is the protection. Who held what power, when, and who gave it; a general erasure right cannot reach it while the organisation exists.

Carried out by the code

The two marks your profile can wear -- Founder (from the day you joined, never written down) and Founding Supporter (a named person's confirmation that you gave, with no amount and no payment detail anywhere) -- and your own choice of whether to show them.

kept — keeping is the protection. A thank-you that is deleted becomes a person who was thanked and then unthanked; the member's display choice is theirs to change at any time.

Carried out by the code

Your account: the name you chose, your email, when you joined, and your settings — including whether other members may find you by an exact handle or display name ("Let people find me", on by default for an adult, never for a child).

Founder ruling B and F2 (revised), 2026-09-14, saved at docs/founder-rulings/2026-09-14-second-answers.md. Kept until the member deletes the account, and then erased IMMEDIATELY, on their word. This row promised a thirty-day grace period until that ruling withdrew it. The withdrawn wording is NOT quoted here on purpose: account_deletion_core.a_grace_period_came_back() scans real surfaces for it, and a scanner cannot tell a promise from a record of one -- so the record describes the old wording rather than reproducing it. The phrase itself is kept once, in that module, where the gate can see it is a constant and not a surface.

Carried out by the code