Privacy

Last updated: 2026-07-14

This page is meant to survive scrutiny, not just reassure you. If you’re an admin deciding whether to trust MemoryCord with your server, read this before you invite it. If you already have, and something here is unclear, ask in the support server or email the address at the bottom - don’t just assume.

The short version

MemoryCord stores messages your community explicitly chooses to save, and only in channels an admin explicitly opted in. It never logs, samples, or scans general chat. Deletion commands are real deletions, not “flagged for removal.”

What triggers storage

A message becomes stored data only when one of these happens, and only in a channel that’s opted in:

• Someone reacts to it with the pushpin emoji (subject to the self-flag and rate-limit rules in Saving to the Wiki).
• Someone runs /wiki save on it.
• It’s captured as the question or answer half of a /solve pair.
• An admin bulk-seeds it with /import pins or /import history (see Importing and Exporting for exactly what those scan and skip).

Nothing else writes message content to the database. A channel that has never been opted in is never read for capture purposes - the bot does not scan it, sample it, or hold anything from it in memory.

Exactly what’s stored, field by field

For a wiki entry (a pushpin//wiki save/import capture): the message text (up to 4,000 characters, truncated beyond that), the message ID, the channel ID, the server ID, the original author’s Discord user ID, the ID of whoever flagged or saved it, the reaction count at time of capture, whether it was captured live or imported, a link back to the source message, and a capture timestamp.

For a Q&A pair (a /solve capture): the question text and the answer text (each up to 4,000 characters), the question message ID and answer message ID, the question author’s user ID, the answer author’s user ID, the user ID of whoever ran /solve, the thread ID (if applicable), a link back to the answer message, and a capture timestamp.

For server configuration: which channels are opted in and who opted each one in, the digest schedule (day/hour/timezone) and destination channel, and the Discord user ID of whoever first installed the bot.

For the digest log: the time window covered, whether the post succeeded, and aggregate counts only (how many wiki entries, how many Q&A pairs, how many unresolved threads) - never message text.

What is never stored

Full chat history. Messages that were never flagged, saved, or solved. DMs - the bot only operates in servers. Presence or online-status data. Member lists. Voice activity. Attachment files themselves (an attachment-only message stores the filename as placeholder text, not the file - see Saving to the Wiki). Content from a channel that was never opted in.

The search permission model

/ask and /wiki search only return results from channels the searching member can currently view in Discord. This is enforced by the search query itself, not filtered after the fact - a result from a channel you can’t see is never fetched from the database in the first place, so there’s no path by which search could leak restricted content to someone without access. See Searching for detail.

The weekly digest applies a stricter rule than search: it only ever includes content from channels visible to @everyone, even if the source channel is opted in and restricted to certain roles. Restricted-channel content can appear in /ask results (to people who can see that channel) but never in the digest (which anyone in the digest channel can read). See Weekly Digest.

Every way to delete data

Action	Who can do it	What it removes
/wiki delete message_link:<link>	The flagger/saver, the message author, or an admin	One wiki entry
/forgetme	Any member, for themselves	Every wiki entry and Q&A pair where you’re the author, flagger, question author, answerer, or solver, in that server
/optout purge:True	An admin	Every wiki entry and Q&A pair captured from that specific channel
/forgetserver	An admin	All data for the entire server - opt-ins, wiki entries, Q&A pairs, digest configuration and log
Deleting the original Discord message	Anyone who can delete the message	Its wiki entry, automatically
Kicking the bot from the server	Anyone who can kick the bot	All data for that server, automatically, the moment Discord notifies the bot

/forgetme only covers the server you run it in - repeat it in each server if you want your data gone everywhere. If you’ve left a server and can’t run commands there anymore, email the contact below with your Discord user ID.

The honest caveat: Q&A pairs and edits or deletions

When the original message behind a wiki entry is deleted in Discord, its copy is deleted automatically - that’s the one line in the table above worth double-checking, and it’s true. /solve Q&A pairs work differently: deleting the original question or answer message in Discord does not automatically delete the saved Q&A pair. The pair was captured as a snapshot of both messages’ text at the moment /solve ran, and it lives on independently of whether those Discord messages still exist or have since been edited. If you need a specific Q&A pair gone, the people who can remove it are the question’s author, the answer’s author, or whoever ran /solve on it (via /forgetme), or an admin (via /optout purge:True on that channel, or /forgetserver). There is currently no single-pair delete command the way /wiki delete exists for wiki entries.

Similarly, editing a Discord message after it’s been captured does not retroactively update the stored copy - the wiki entry or Q&A pair keeps the text as it was at capture time (re-flagging a wiki entry does refresh it; re-running /solve on the same question/answer pair does not create a duplicate, since it’s keyed to the same two message IDs).

Backups and third parties

Nightly, encrypted-in-transit backups are kept in maintainer-controlled storage and pruned after 30 days - deleted data leaves backups within that window rather than lingering indefinitely. Your data is never sold, shared, or made available to any third party. It’s used only to power /ask, /wiki search, and the digest for your own server; data from one server is never visible in another.

Requests outside Discord

If you can’t use the in-Discord commands - you’ve left the server, for example - email [email protected] with your Discord user ID and what you’re asking for (deletion or a copy of your data). We aim to handle these within 30 days.

Questions about anything on this page: [email protected], or the support server.