Privacy & legal

A plain accounting. No lawyer wrote this, and it asks nothing of you but a moment's reading.

Whose board this is

Summon keeps private boards for Commander pods: one for Kyle's own pod, and others Kyle runs for groups he knows. Each board is kept entirely apart from the others: its own password, and its names, marked days, email list, calendar and Ledger in storage of its own. Nobody on one board can see another, and nothing is ever copied between them. Boards added since v35.21 share one program and one storage area on Cloudflare: each board's records are kept under a label of its own, which the program serving that board can never read past, and each has its own password, admin password, email key and calendar address. They are as separate as the others; it only means a new board needs no new program. Everything below applies to each board on its own.

If you are on two boards (since v35.14), the device that holds both passwords shows you, on each board, the days you said yes on the other one and the games you are in there, so you don't book yourself twice. It is done on your own device: it reads the other board with the password it already keeps, the same way opening that board would, and shows only your own days, never anybody else's names or marks. The boards themselves still never talk to each other, nothing is copied between them, and nothing new is kept anywhere. A device that only has one board's password sees nothing of this.

Each board is kept by Kyle for the people who play at its table. It is free to use. Nothing here is sponsored and there are no adverts. The one place money can change hands is said plainly where it happens: the SHOP TCGPLAYER and BUY ME A COFFEE links at the foot of the front page and The Oracle (below).

Summon is a hobby project. One person, Kyle, builds and runs it in his spare time, for his own table first. It is built to carry no trackers of any kind: no analytics, no advertising code, no third-party scripts, nothing that follows you from page to page or from this site to others. That is kept to the best of his ability, not guaranteed. The services Summon runs on can add things of their own, and when one turns up it is switched off. If you ever find something on these pages that watches you, say so and it will come out: kyle@summon.club.

If Summon ever charges for anything, it will be said here first, in plain words. Nobody will be charged for something they are already using without being told and asked beforehand. What this page promises about your data does not change with it.

It used to live at riddlehere.com under the name Convoke. It is the same board with the same records, moved to its own address; nothing was copied anywhere to make the move.

It is not indexed by search engines. The board and the Ledger were built for the handful of people who were told about them; the life tracker, the keyword book and The Oracle are open to anyone who has the link.

What is asked of you

Two things, and a third only if you want it. The pod's password, which you are given once and your browser keeps, and a name to put your answers under — whatever you like, a first name, a nickname, two letters. Nothing checks the name and nothing is verified. No account, nothing to sign up for.

You can also say what time you can get there and whether you have a table. Both are optional, both are visible to the rest of the pod, and both are blank until you fill them in.

The third is an email address, and it is entirely optional. Give one and it is linked to the name you joined as, so you get a message when a night you said yes to is on, and if it falls apart — plus, as you choose, every other full table, any game the board counts as one, or nothing else. Give none and everything else works exactly the same.

What is kept, and where

On a small program of ours running on Cloudflare: the name you typed, the days you marked and when you said yes to each (when a table seats only so many, the seats go first come, first served), the time you said you could start, and whether you said you could host. Each person gets their own record, so no two of you can write over one another. A day you marked, and everything about it, is deleted about a month after it has passed (since v35.20). A game leaves the board's calendar once its day has passed.

And if somebody has put up an event — a prerelease, a draft night — the board keeps its name, day, time and place, a web link if one was given (a shop's registration page, say), who added it, and whether each person said they were going. All of that is visible to the pod, which is the point of it.

And if somebody has put up a drop — a Secret Lair sale or anything the pod might buy together (Summon v33.7, October 2026) — the board keeps its name, the day and time it goes on sale, its link if given, who added it, and who said they're in. All of it is visible to the pod. Drops are gone from the board a few days after the sale. Summon never buys anything and takes no payment; the link goes to the seller's own site.

The last two are optional and blank until you set them. A host flag is only ever the word yes or no beside your name — no address is asked for, stored, or shown, because the people who would come already know where you live.

A night’s details (since v35.15). Anyone on the board can write down what the pod agreed for a night: a start time, where, and a short note. The board keeps them with the name of whoever last changed them, and everyone on the board can see and change them. They go in the board’s calendar and in its emails about that night, and if the pod uses Discord, a post says the time and place of a game when they are set or changed (never the note or who wrote it). They are dropped once the day has passed. Please don’t put a full home address in them.

If you gave an email address, it is encrypted where it sits, so reading the storage on its own does not reveal it, and it is kept with the name you joined as, along with which other nights you asked to hear about. That link is what lets an email be about your nights, lets any of your devices say whether your email is on, and makes sure the address goes when you are taken off the board.

It changed in October 2026 (Summon v26). Before that, addresses were kept apart from every name, and the board could not tell whose was whose. Nobody's earlier address was linked without asking: each got one email asking which name was theirs, kept getting the emails it always had until then, and was removed a month later if it never picked one.

The board can say whether a name has an email on, and which emails it gets, and anyone with the pod's password could look — the same way they can see your marks. Anyone in the pod could also change which emails a name gets; when that happens, or another address is linked to your name, the address already there is told, with a link to put it back. The board never says what an address is, and how many addresses are on the list is the only other thing it shows. Entering an address that is already on gets you a note saying so, and changes nothing.

On your own device, the browser remembers seven things and no more: the pod's password, which name you joined as, which filled days it has already shown you, the address you gave if you gave one, the day it last asked for a confirmation email for it (only for the week the link lasts, so the board can tell you to check your inbox), which board you opened last (since v35.0, so the Board and Ledger tabs take you back to it from any page; those two tabs only appear once the browser holds a board's password, and the tab bar only looks whether one is there, never at it, and sends nothing), and — if you are the one who sets up the board — the admin password. Nothing else is written there, and none of it is a cookie. Clearing this site's data clears all of it, but note that it does not unsubscribe you; see below.

The Ledger — a longer memory

Beside each board there is The Ledger, where a night gets written down: how many games were played, who won each one, and what each person was playing. It sits behind the same password, uses the same names and the same colours, and is the same handful of people.

It is worth being plain that this is a different kind of record from the board. The board keeps what might happen and forgets it about a month after the day has passed. The Ledger keeps what did happen, on purpose and for as long as you keep it — that is the entire point of a record book, and it would be dishonest to add one without saying so.

What it holds: a date, who played, what they called their deck (since v35.12 including, while a game is being played, what each person is on for it, so every device at the table sees the same), and, if somebody on the board saves one, that deck's bracket. Deck names are whatever somebody types. The Ledger itself consults no card database, looks nothing up, and sends no request to anyone else's server — the same as the board.

A deck's bracket comes from The Oracle, saved by somebody on the board (how, below), or is set by the pod itself, shown with a dashed edge beside what The Oracle said. What is kept: the bracket, The Oracle's three readings, the commander's name and the date, and the deck's list if whoever saved it left ALSO SAVE THE CARD LIST ticked (below). Nobody on the board can see a kept list: the board never shows it, to anyone. Anyone on the board can change or clear a deck's bracket, and it goes when the deck is taken off the shelf.

RECORDS (since v35.9) opens with YOUR CORNER: your own games, decks and best moment, picked out by the name this device joined the board as. It is worked out on your own device, from the same nights everyone on the board can already see in THE BOOK, and shows only you, only where the board was joined as you; nothing new is kept or sent to make it. Below it are the pod's story, its decks (a deck's toughest opponent is another deck, never a person), milestones and nights. Everyone's own numbers are still there, folded away and listed by name, never in order of who wins most.

While a night is in progress it is also kept on the phone keeping score, so the sheet still works where the signal does not. It goes up when the connection returns.

Ask and a night goes altogether, or the whole record does: kyle@summon.club.

Two things stay after that, and you should know both. Someone taken off the board keeps their name and colour beside their games in the Ledger, so the book still says who played; nothing else of theirs is kept. And the Ledger keeps backup copies of the whole book, one from each of the last ten days it changed, so a mistake can be undone. A night that is deleted stays in those copies until newer ones replace them, which on a quiet board can take a few months. They sit with the board on Cloudflare; nobody on the board can read one, and only the board's admin can put one back.

Who can see an email address

Nobody using this board. Not the pod, not whoever set it up, not you. The board is never sent an address by the program that holds them — not yours, not anyone's, not a masked or partial one. There is no password that reveals them and no screen that lists them. The address shown back to you on the board is remembered by your own browser, not by the board.

The board will say how many people get email, and, to the phone of the person it belongs to, whether theirs is on. Like anything else on the board, someone in the pod who went looking could ask that about another name; the answer is a yes or a no, never an address.

Two parties can, and it would be dishonest not to name them.

Kyle, who runs the board, holds the key that decrypts them and could look — and since addresses are linked to names, could see whose each one is.

Resend (resend.com), which delivers the mail. Nothing can deliver a message without knowing where to send it, so Resend is given your address and the text of the message at the moment one goes out. Two things follow, and they are worth saying out loud:

That is the whole list. Nobody else is sent an address, for any reason.

Stopping the email

Every message has a link at the bottom. It opens a page with a single button; press it and the address is deleted — not marked, not hidden, removed. No password, no account, no question asked. It works from any device, whether or not you still have the browser you signed up from. A second link beside it changes which emails you get, the same way.

If you are taken off the board, your address goes with you, at once. Nobody who has left the pod keeps hearing where and when it is playing. The one gap is an address from before October 2026 that has not yet picked a name: the board can't tell whose it is, so it goes when its month to pick one is up, or sooner if you press the link to stop, or ask Kyle.

The button is there for a reason. Mail programs and company security scanners often fetch the links in a message before you ever see it, to check them — so a link that acted on its own could take somebody off the list who never touched it. A scanner will follow a link; it will not press a button.

Clearing your browser data does not unsubscribe you. It only makes this board forget the address you gave, so it can no longer show it back to you — the emails carry on. That is on purpose: being able to stop them should never depend on still having the browser you signed up from. The link in any message is how you actually stop, and it always works.

An address that is never confirmed is thrown away within a week. If somebody typed yours by mistake, doing nothing at all is the whole remedy.

What leaves, and when

When enough people mark the same slot, an email goes out to the people in it who gave an address, and to anyone who asked to hear about other nights, carrying the date, the start time, the first names of whoever is in, and whose table it is if somebody offered one. Another follows if the game later falls apart.

If your pod uses Discord, whoever runs your board can connect one of its channels (Summon v29, October 2026). Then a line is posted there when a night becomes a game, when the table fills, and if it is called off. It carries the date, the start time and how many are in, with a link back to the board, which still asks for the pod's password. No names, nobody's table, no email address, and nobody is pinged. The one exception is a drop: when one is added, its post says what it is, when it goes on sale, and who added it (and whether they're in), so the pod knows who to talk to. Nothing more is posted about it after that. Discord (discord.com) keeps what is posted in its channels under its own terms, and everyone in that channel can read it, whether or not they are on the board; that is why nothing goes there that would matter if a stranger read it. A post already made stays in the channel until somebody there deletes it. The channel's posting address is a password of its own: it is kept encrypted, the way email addresses are, and is never shown on the board. A board that has not connected a channel sends Discord nothing at all, and every board says which it is: Discord on or Discord not set up, on the line under your name.

If your board asks for games to be confirmed (Summon v30, October 2026; the admin turns it on), the Discord posts work differently, so the pod can talk a night over where it already talks: a post when a night could happen names who is free, one when someone confirms it names them too, and there may be a reminder the day before and a "called off". Still never an email address and never the calendar address. The people in a night get one email saying it could happen, and, if nobody has confirmed by the day before, one reminder.

Discord pings are your choice. If you add your Discord user ID on the board, posts about nights you are in mention you, so Discord tells you. The ID is kept by our program on Cloudflare, used only to put that mention in the post, and never shown on the board, to you or anyone; the board only says whether yours is on. Turn it off on the board and it is deleted; it also goes if you are taken off the board. A Discord user ID is the number Discord gives your account; anyone in the same Discord server can already see it.

Nothing else about the board is ever sent anywhere.

Those emails are sent one at a time, one message per person. Nobody's address appears in anybody else's copy — deliberately, because that is the easiest way in the world to spill a list of addresses and it is done by accident constantly.

If you subscribe a calendar to this board, your calendar app fetches the list of nights that are on directly. Those requests go to our program on Cloudflare and nowhere else.

What is never done

How Summon is made

Summon's code — the pages, the programs on Cloudflare, their tests — is kept in a private repository on GitHub (since October 2026), with a copy on Kyle's own drive. Only Kyle can see it. It holds the code and the test decks above, and nothing anybody sends: not what you put on a board, not an email address, not a card list saved to a board, not a BRACKET FEEL WRONG? report. Those stay where this page says they are, on Cloudflare. The passwords and keys the programs use aren't in it either. Since v35.7 the site's pages are published from that repository automatically: Cloudflare, which already serves Summon, reads it to put each new version up, and nothing else changes about where anything you send is kept.

Kyle builds Summon with the help of an AI coding assistant, Claude, made by Anthropic, which works on that code. It never gets anything you send or anything a board keeps. The card lists saved to train the test games and the BRACKET FEEL WRONG? reports are for Kyle to read; they are not put into the code and not given to an AI. If that ever changes, this page will say so first. None of this puts AI on any page of Summon: every page still works by itself, with no AI.

Who can see the board

The pod, and no one else. The board is behind a shared password — you type it once and your own browser remembers it, so finding the address on its own shows you a password box and nothing more. Reading the board needs it just as much as marking a day does.

Inside the pod there is no separation, and that is deliberate: anyone who knows the password can mark a day under any name on the board. It is a shared whiteboard among friends, not a set of private accounts.

Email is the one exception, and it is the reason addresses are kept away from the names. Because anyone here can act as anyone, an address sitting on a person's row could be read by the pod — or quietly pointed somewhere else. Kept apart, there is no row to open, so there is nothing to read and nothing to repoint.

Treat the password the way you would a house key. If it ever gets somewhere it shouldn't, tell Kyle and it can be changed in a minute — nobody has to reinstall anything, they just type the new one once.

What cannot be helped

Cloudflare carries the requests, and like every host on earth it sees the address your device is calling from. That is the plumbing of the internet, not a choice of ours. We do not log it, read it, or keep anything derived from it.

The service that delivers the email sees the message it is asked to carry — the date and the first names in it — and the address it is carrying it to, because nothing can deliver a message without knowing either.

Taking yourself off

Clear your marks and your row goes empty. Ask and the record goes altogether, name, days and email address together: kyle@summon.club. If you gave an address, the link at the foot of any message removes it on the spot without asking anyone.

Taken as it comes

Everything here is offered as it is, for the ordinary business of working out when four people are free. No promise is made that it is correct, current, or fit for anything in particular, and it is not a contract or an agreement of any kind. Do not lean on it for anything that matters — a flight, an appointment, a commitment you would be sorry to miss. It is a board for arranging card games, and a game that does not happen is the worst it can cost you.

Summon is a free hobby project, kept up by one person to the best of his ability. The Ledger keeps its own copies and has been built carefully, but no promise is made that a record will never be lost. If your group's history matters to you, keep a copy of your own: DOWNLOAD THE BOOK, in the Ledger, saves all of it as a file on your device.

Who it's for

Summon is meant for adults. It isn't aimed at children, and it doesn't knowingly take an email address from anyone under 13; the board says so where it asks for one. If you think a child has given one, write to kyle@summon.club and it will be deleted. (Anyone can also remove their own address at once from the link in any message.)

Unofficial, and whose Magic it is

Summon, the Ledger, the life tracker, the keyword book and The Oracle are made by people who like the game, for people who like the game. They are not made by, endorsed by, or connected to Wizards of the Coast in any way.

Summon is unofficial Fan Content permitted under the Fan Content Policy. Not approved/endorsed by Wizards. Portions of the materials used are property of Wizards of the Coast. ©Wizards of the Coast LLC.

The keyword book is written in our own words as a quick reference. It is not the official rules and should never be used to settle an argument — for that, the comprehensive rules are the only thing that counts.

The life tracker

The life tracker is open to anyone, with no password, and keeps everything on your own device: the players' names, life totals, poison and commander damage for the game in front of you, so it can carry on after a reload or with no signal, and its two settings, BATTERY SAVER and whether the screen stays lit. A game from a board's Ledger is kept apart from a game of its own, with who sat where that night so the same people go back to the same seats. None of it is sent anywhere — except a game from a board's Ledger, kept on that board turn by turn (below). Clearing this site's data clears it; starting a new game replaces the one of the same kind.

A game from the Ledger (Summon v34.13, October 2026). On a phone that has a board's Ledger open, PLAY IT ON THE LIFE COUNTER passes that game's players' names and decks to the life counter on the same phone, and at the end the life counter passes back who won, who went first, who went out and on which turn. Both are this site's own pages on your phone; nothing is sent anywhere in between. The Ledger saves the game to the board only when someone taps CONFIRM, the same as any game. Since v35.1 a game from the Ledger is kept on the phone apart from the life tracker's own game, until it is finished or ended with END WITHOUT SAVING, so a phone call in the middle loses nothing and the life tracker still opens to a game of its own; the phone also notes which of the two was in use last.

Kept on the board, turn by turn (since v35.11). So that a game from the Ledger survives a phone dying, the life counter saves it to that board each time the turn is tapped: the players' names and board ids, decks, life totals, poison, commander damage, counters, who is out and on which turn, whose turn it is and the turn count. Only a game from the Ledger, never a game of the life tracker's own; only to its own board, behind the pod's password; nothing between turns. Anybody who is in that game then sees it on the Ledger on their own device, with the turn it got to, and can carry on from there; the device that had it is told and stops saving. The board deletes the copy when the game is finished, and forgets it on its own after twelve hours whatever happens. The device that keeps a game also keeps a random number of its own (no name, nothing about you) so the board can tell which device is keeping which game, and each game gets a random number of its own when it starts. Since v35.19, when a game is finished the board keeps, in place of the copy, only a note that that game was finished: its number and those two random numbers, nothing about anyone. It is there so a phone that lost touch mid-game is told the game is over rather than recording it a second time, and it is forgotten after the same twelve hours.

The Oracle

The Oracle reads a pasted Commander list and says which of Wizards' brackets it falls in. It is open to anyone, with no password, and nothing about you is kept. It is our reading of the bracket rules, not an official rating, and it rates a deck, never a person.

What leaves, and only when you press READ THIS DECK: the card names in your list — once each, without quantities — and which of them are your commander. They go to a small program of ours on Cloudflare, a separate one from the board's that holds nothing of the pod's. It asks Commander Spellbook (commanderspellbook.com) for combos and its own bracket estimate, and hands the answer back. Card details come from a copy of Scryfall's card list kept on this site (scryfall.com; v34.0, updated about once a month): your browser fetches only the small parts of it that hold your cards, from summon.club itself. Only a name our copy doesn't have, such as a card newer than it, goes on to the program, which asks Scryfall for it. Scryfall and Commander Spellbook see a request from Cloudflare, not from you: your device's address is not passed on, and your browser never contacts either of them.

What is kept: the public details of each card the program had to ask Scryfall for — its name, colours, type and rules text, the same for everybody — for up to 30 days, so the next lookup is quicker. No prices: The Oracle doesn't show any since v34.0. Your list is not kept (unless you send a BRACKET FEEL WRONG? report, below): once the answer is sent back it is gone, and nothing records who asked or what else was in it. Nothing is written to your device, and the list in the box goes when you close the page.

Saving a reading to your board. On a phone that has already opened one of Summon's boards, The Oracle offers SAVE TO THE LEDGER once a deck is read. It knows by looking for that board's password, which this phone already keeps; it only reads it, and writes nothing. Nothing goes to the board until you tap: once to see whose decks it has, once to save. What is saved is the result: the bracket, the three readings, the commander's name and the date. One tick decides the rest (Summon v34.14, October 2026):

On a phone that has not opened a board, none of this appears and no board is asked anything.

TEST IT (PLAYTEST and POD GAMES until v34.14). Once a deck is read, The Oracle can play it a thousand times alone to see how it draws, then in four-player games against other decks, by the rules, to see how it does. That happens entirely on your device, from the card details it already looked up: nothing more is sent, and the results are gone when you leave the page. The decks it plays against and their public card details are files on this site, the same for everybody. It reports results only, from simple game logic that reads each card's rules text, not an AI.

Which decks it plays (Summon v34.18, October 2026). It starts against official precons and a few real Bracket 2 decks; a deck that wins more than its share moves up and plays real Bracket 3 decks, then Bracket 4. Apart from the precons, those are decks from Kyle's own pod, which he chose to put there: their lists, with their commanders' names and the bracket each is, in a file on this site. No player's name is in it, and no deck anybody saved through The Oracle is in it. Phones no longer ask a board for its decks; from v34.10 to v34.13 a phone that had opened a board could also choose that board's decks opened to testing (above).

Cards it couldn't fully play (Summon v33.8, October 2026). When POD GAMES finishes, the page sends the names of the cards in your deck that the engine couldn't fully play — and nothing else: not the rest of your list, not your commander, not the result — to our Oracle program on Cloudflare. It adds one to each name's count for the month, so we can see which cards the engine most needs to learn and teach those first. Nothing about you is read or kept: not your address, not your device, not when you asked. The counts are card names and numbers, kept about a year, and anyone can see them (they hold nothing about anybody).

BRACKET FEEL WRONG? (Summon v34.12, October 2026). Under a reading there is a button to tell us the bracket looks wrong. Only if you fill it in and press SEND, it sends to our Oracle program on Cloudflare: the deck list as it was read, the Oracle's bracket and its main reasons, the bracket you think it is, and what you wrote. Nothing about you: no name, no email, not your address or device. It is kept 180 days so Kyle, who runs Summon, can read it and use it to improve The Oracle; nobody else can see it. He reads them on a page of The Oracle's that asks for a password his own device remembers; nobody else's device keeps anything for it. Please don't write anything personal in it.

No AI. Nothing you paste is sent to an AI service, or anywhere not named here.

SHOP TCGPLAYER, SHOP MANA POOL and BUY ME A COFFEE

Three plain links sit at the foot of the front page and The Oracle. Nothing on Summon needs any of them, and not clicking them changes nothing.

SHOP TCGPLAYER is an affiliate link. It goes through TCGplayer's affiliate service, Impact (partner.tcgplayer.com), which records the click and may set cookies of its own before sending you on to TCGplayer. Buy something there within two days and Fidget Here, LLC, Kyle's business and the account holder with TCGplayer, may earn a small commission, at no cost to you. It is told how many clicks and sales there were, not who made them.

SHOP MANA POOL is an affiliate link too (since October 2026). It goes straight to Mana Pool (manapool.com), a separate site with its own privacy policy, with Summon's referral code on the end of the address. Mana Pool records the click through its affiliate service, Tapfiliate, and may set cookies of its own. Place a first order there within seven days and Kyle, who makes Summon and holds that account in his own name, may earn a small commission, at no cost to you. Summon itself learns nothing from the click: what Kyle sees is Mana Pool's own report of clicks and orders.

BUY ME A COFFEE opens Kyle's page on buymeacoffee.com, a separate site with its own privacy policy, where you can leave a tip if you'd like to. Summon is not told who tips.

None of the three is loaded until you click it: no button, script or image from any of those sites is on these pages.

The lettering

Press Start 2P and DM Sans, both under the SIL Open Font License 1.1, and both served from this site rather than from anybody else's. Nothing on this page calls out to a third party for anything — no font, script or image is fetched from anybody else's server. (The mail service and Discord, named above, are a separate matter: they are used by the program on Cloudflare, not by this page in your browser.)

If something here is wrong

Tell us, and it will be put right: kyle@summon.club.