Privacy

Sigil lets you build a public profile. This page says, in plain words, what we keep and who can see it.

What we get from Discord

When you sign in with Discord we ask for your basic identity and the list of servers you are in. We keep your Discord id, your username and the code of your Discord avatar, the day you first signed in to Sigil (your profile shows it as "Joined") and when you last signed in. We don't ask for your email address or your messages, and the permission we ask for can't be used to add you to a server, post for you or read anything you write.

Your list of servers. Each time you sign in, Discord tells us the servers you are in. For each one we keep only its Discord number and name, whether you own it, and what you're allowed to do there (only so we can tell whether you are an Administrator). We use it for one thing: the Choose a server list on the CONQUEST page, and checking that you really are in a server before you pledge to it. It is replaced every time you sign in, is never shown to anyone else, and is deleted with your account.

What you add

Everything you choose to put on your profile: display name, bio, tags, social handles, the words you write for About, avatar, banner, page background, fonts and colors, and any pictures you upload for your gallery. If you add a song for your Now playing card, we keep which song it is (for example a Spotify song id), not the link you pasted, and look up its title, artist and cover picture once, when you add it, so your profile can show them without anyone's browser contacting the streaming service. The cover is saved on this site as one of your pictures.

Who can see it

  • Your card is public. Anyone with the link (/u/ followed by your Discord username, or your Discord id) can open it, signed in or not. We ask search engines not to list it, but that is a request, not a lock.
  • Pictures are unlisted, not private. Each picture has a long random address. Nobody can guess it, but anyone who has it, or who opens your profile, can see the picture. Only upload pictures you're happy to share.
  • Your friends list and your wall (notes other people leave for you) are shown only if you switch them on in the Profile page section of Edit profile. Your friends can also see that you're friends.
  • Servers, Top 4, Get to know me and vouches. On Show off in Edit profile you can choose up to five servers to show, with your level and rank in each, a Top 4 made from your own tags, and up to three Get to know me answers. They are as public as the rest of your profile, and a server's admins can switch off showing their server on profiles. Only your friends can vouch for you, with up to three words each from a fixed list. Your profile shows how many friends chose each word, not who. We keep who gave each vouch so they can change or take it back, and a vouch between two people is deleted when they stop being friends. You can turn vouches off or hide a word.
  • Game covers. The pictures behind a profile's game tiles come from RAWG (rawg.io). When a profile shows one, the visitor's browser loads it from RAWG's servers, so RAWG sees that request (the visitor's IP address and browser details, as with any picture loaded from another site). We send RAWG nothing about the visitor or about whose profile it is.
  • Versus. A signed-in person who opens your profile sees how their own tags match yours, the games you both play, and the servers you show that they are in too, with both levels. It is worked out when the page opens from what is already on your profile; nothing about the match is kept. Your timezone is never part of it.
  • Activity. The Activity tab lists what you have been up to, newest first: reaching a new level in a server you show (we keep the server, the level and the day), new Weave records, vouches and new friends counted by week with no names, new pictures and notes on your wall, and the day you joined. You can switch it off under What visitors can see in Edit profile. A signed-in visitor can react to an item with a heart, a flame or a clap; we keep who reacted to what so they can take it back, and your profile shows how many, not who.
  • Friend suggestions. On for everyone, on the Versus tab of someone's profile and on the Friends page. Sigil compares the tags and games on your profile with those on other profiles and shows you up to six people who match best, with a few of the tags you share. You show up in other people's suggestions the same way, with your name, picture and the tags you share, unless you turn it off with Show me in other people's friend suggestions in Edit profile (or the button under the list). Only whether it is on is kept, not the comparisons. Discord data such as your servers, your activity or your game time is not used to pick people. People you are already friends with or have a request with are left out. Turn it off any time and you stop showing up at once.
  • Game time. Off unless you turn on Count my game time in Edit profile. While it is on, the bot looks at the game Discord shows you are playing (it needs Discord's Presence permission) and adds up the minutes for each game on Sigil's own list, from the day you turned it on. We keep the game's name, your total minutes for it, the day you started and, when a total passes a round number of hours, that milestone for your Activity. With each game we also keep the time its last minute was counted (that is what Playing now below uses), and the minutes you played it on each of the last 35 days (what this week in a game's window adds up), but nothing about what time of day you played. We do not keep what else you were doing, or anything about people who have it off. Your totals show on your profile (Top 3 games, Games I play, Versus and Activity) for the games you have picked. A game you play for at least ten minutes that is not among the games on your profile is added to them, so your profile shows what you play (you can take it off on Edit profile). Turn it off and counting stops and the totals are hidden; they are kept in case you turn it back on, and we delete them if you ask (see the contact address above).
  • Connect. A tab on your own profile that recommends five people to play with (new ones every 30 minutes) and lets you search the people who are shown in friend suggestions, by game, platform, style and more. It only uses the tags and games on Sigil profiles, and nothing about what you searched for is kept. Whether you appear in it is the same switch as friend suggestions. On Edit profile you can add when you usually play (mornings, evenings and so on) and the rank and role you play each game at, which show on your Connect card and when someone compares with you. You can also say you are looking for a group for one of your games for one to 24 hours, with a short note; it shows until then and goes away by itself. You can also say how you like to talk while you play (voice chat, text only or either), which shows as a tag. Pressing Not interested on someone saves that you hid them (their Sigil ID, for you only), so they stay out of your Connect; Show them again clears it. Cards and the Versus screen also show a few trust signals about the person: how many friends vouched for them and the most common word (only the words they show on their profile, never who), whether they were on Sigil today or this week, and the hours counted for them if they count game time. An Ember member can be shown first in someone's search and marked Featured (at most five per search, only if they match it); that only uses that they are an Ember member, and nothing about who saw whom is kept.
  • Playing now. Off unless you turn on Show a Playing now badge on Edit profile (or say Yes to counting hours when you set up your profile), and only while Count my game time is on. People who are signed in then see the game you are in on your profile, your Connect card and the Versus screen, from the time the bot last counted a minute of it, and it goes away a few minutes after you stop. Nothing else is kept for it. Turn either switch off and it stops at once.
  • Message on Discord. Off unless you turn it on, when you set up your profile or on Edit profile. While it is on, people who are signed in see a button on your profile and your Connect card that opens your Discord profile. Sigil only adds the link: it never sends, sees or keeps the messages. On a Connect card the button also copies a friendly hello (made from what you both already show) to the clipboard of the person who presses it, so they can paste it in Discord; nothing is sent by Sigil.
  • Friend requests from Connect. A request sent from the Connect tab carries one line the website writes from the games and times you both already show (for example "Found you on Connect. You both play Hades, mostly evenings."). Nobody types it. It is kept with the request, shown to the person who answers it, and remembers that the request came from Connect.
  • Play requests. Asking someone to play (from Connect) saves who asked, who was asked, the game (one of theirs), the few words you added and when. Only the person asked sees it, on their Friends page. It ends by itself after three days. If they say yes, the two of you can see each other's Message on Discord button for a week, whatever you each set; a Not now is never shown to the person who asked. Old requests are deleted the next time anyone sends one, and nothing is sent to Discord.
  • Blocking. When you block someone we save that you blocked them (their Sigil ID, for you), and remove any friendship, vouches and play requests between you. Neither of you shows in the other's Connect or friend suggestions, neither can send the other a request, and the Message button is hidden between you. They are not told. Unblocking deletes it. Sigil cannot stop people reaching each other on Discord itself.
  • Played together. For two friends who both count game time, we keep, for each game they were in at the same time, the pair, the game, how many minutes the bot saw both of you in it and when it last did. It is deleted when either of you unfriends or blocks the other, and after a year without playing that game together. If you show your friends list, the friends you have played a game with, and for how long, show in the window that opens when someone presses that game on your Games tab (see Game window below). For friends who found each other through a request from Connect we also keep the game you last played together and whether each of you has put away the question "want to vouch for them?", which is asked once after about twenty minutes; that part is deleted after two months without playing together.
  • Game window. Pressing a game on someone's Games tab (or a Top 3 tile) opens a window with the time counted for it and how much of it was this week (if they count game time), the rank and role they set (for signed-in visitors only), how many friends who play it vouch for them and with which words (never which friends), how many people on Sigil have it on their profile, and who they played it with (only if they show their friends list). It is worked out when the window opens and nothing is kept about who looked.
  • Game suggestions. The game box on the Connect search suggests games from Sigil's own list as you type. What you type is only used to look games up, and is not kept.
  • Games you ask for. If you press Can't see your game? on your Games tab and send a name, Sigil keeps that name with your account and the date, so the person who runs Sigil can see which games people ask for and how many people asked. The name is only checked against Sigil's own list as you type, and nothing is kept unless you send it. It stays until that game is added or turned down.
  • Squads. A squad you make keeps its name, its game, the words you wrote and what you said it is like (platform, region, language, when it plays, how it talks, style, rank, how many members, whether it is open), who leads it and who is in it with the day they joined. Anyone signed in can open an open squad's page and see its members; the squad shows on each member's profile. A request to join, or an invite, keeps who it is between, the few words you added and its answer, and is removed when it is taken back, answered with a yes, or after two weeks. Leaving a squad removes you from it, disbanding removes it and everything about it, and blocking someone takes you out of each other's squads. Nothing about squads is sent to Discord.
  • Connect numbers. The person who runs Sigil sees how many times each day the Connect tab was opened, a search was made, friend and play requests were sent and accepted, Message was pressed, someone was hidden or blocked, or /find was used. They are numbers only, with no names, and are kept for 120 days.
  • /find. /find lists the people in the server where you use it who are shown on Connect and play the game you name, from the list of servers Discord gave us when they signed in to the website. Only you see the answer, and nothing is kept about who looked.
  • Level rewards. Every fifth level you reach in a server where levels are on (5, 10, 15 and so on) earns a free Asterism pack, up to two a day. We keep which server and level paid it, when, and when it was paid out as Asterism Astra after you opened Asterism, so the same level is never paid twice. A reward waits until your Discord account is old enough for Asterism to give you its starting Astra.
  • To keep Sigil safe and running, the person who runs Sigil can see a list of accounts (name, Discord username and id, whether you're an Ember member, the day you joined and the day you last signed in) and of the servers the bot is in (name and size only). This is for safety and monitoring: spotting spam, abuse and other bad actors, following up reports, and checking that the site and the bot are working. It is not sold, shared or used for advertising. It never shows your bio, tags or messages, and it doesn't list the people in the servers the bot is in.
  • Friend requests are seen by the person you send them to. If someone declines, they aren't told, and neither are you.
  • Your tags, bio and other profile details are visible to anyone who can see your profile. So is the date you joined Sigil, and, if you are an Ember member, a small gem next to your name.

The Discord bot

  • Anyone in a server with the Sigil bot can use /profile to show your profile there. It shows what your public profile already shows, nothing more.
  • /vibe compares two people's public profiles using only what both already show: the games, shows and other picks they chose. The answer is a picture shown to everyone in the channel where it was used, with both names and links to their public profiles, and it never pings anyone. Nothing about the comparison is kept.
  • When someone uses /leaderboard in a server, the bot checks, one person at a time, whether the Sigil members with the highest levels are members of that server, so it only lists people from there. It remembers each answer for a few minutes.
  • For each server the bot is in, we keep which channel that server's admins chose for welcome cards and who chose it, plus the server's name, how many members it has (just the number) and when we first saw it. We use that to see where the bot is, to check it is working, and to deal with servers that abuse it. It is deleted when the bot leaves the server.
  • If you use /lfg, or press Join on someone's post, we keep your Discord id, the game and note, and who joined. That is deleted about a day after the post ends. The message itself lives in Discord, where Discord's own rules apply.
  • The bot doesn't read your messages, and it doesn't keep a list of a server's members. It only learns that someone posted (who and where, never what was said), which is how Ember members' signature reactions work. There are four exceptions, described next. We don't store anything about messages.
  • Quote cards. When someone right-clicks a message and uses Sigil: Quote card, the bot sees the words of that one message. It draws that message as a picture and posts it in the same channel; the words aren't kept. You can switch quote cards off for your own messages on Edit profile.
  • Spy. While a round of /spy is at its one-word-at-a-time stage, the bot looks at the message of the player whose turn it is, in the channel where the game is being played, only to check that it is a single word. Nobody else's messages are looked at, nothing is looked at outside a game, and the word isn't kept.
  • Bomb party. While a game of /bomb is running, the bot reads the message of the player the bomb is with, in the channel where the game is being played, to check that word against a list of English words. It reads only that player's messages, only while it is their turn. The word isn't stored or logged: the words already used in a game are held in the bot's memory until the game ends, and the game itself is never written to our database.
  • Keep up! While a game of /keepup is running, the bot reads the message of the player who is meant to be typing back the digits they were shown, in the channel where the game is being played, to check it against the digits. It reads only that player's messages, only while it is their turn to type. The moment it has been checked, the bot deletes that message (so the chat stays clear and nobody can copy it), which needs the Manage Messages permission in that channel. What they typed isn't stored or logged: the digits of a game are held in the bot's memory until the game ends, and the game itself is never written to our database.
  • The welcome message (/welcome). When someone joins a server that has it on, the bot posts a welcome that pings them once (unless the server turned that off), and, if the server chose to, sends them a private message. It uses only who joined: their name, their avatar and when their account was made. We keep what an admin set up (the words, colours, pictures and link buttons they chose, the channel, and who last changed it) until the bot leaves the server, and, for each welcome, the server, the person who joined, the message, the text it was posted with and who waved at it, for a week. If the server chose to have welcomes remove themselves, the message goes sooner but that record is still kept for the week. A test welcome removes itself after ten minutes. Sigil never reads what anyone writes. The What do you play? button is switched off for now; if someone pressed Show me to others here on an earlier welcome, we keep the server's number, their Discord number, the game names they chose (only names from Sigil's own list) and the time, show their name next to those games to people in that server only, and remove it when they press Take me off the list, when they leave the server, when the bot leaves the server, and after 90 days. If they later sign in to Sigil for the first time, their new card starts with those games; a card that already exists is never changed by this.
  • Entrance cards. If you're an Ember member and you switch your entrance card on, then when you join a server that has set up Sigil the bot posts your card there: a picture with the words and background you chose, your avatar and your name. For that, Discord tells the bot when someone joins a server. We don't keep a record of the servers you join. You can switch it off at any time, and a moderator can clear its words.

Server tools

  • Auto threads (/autothread). For a channel where an admin turned it on, we keep the channel's number, the server's number, who turned it on, how threads should be named, how long they stay open and, if an admin chose it, how long after starting a thread is locked. When someone posts there, the bot starts a thread under their message. It doesn't read the message: the thread is named from the poster's name in that server and the date, unless an admin put {title} in the name, and then the bot reads the first few words of that post (only while the Message Content permission is on) just to name the thread, and keeps and logs nothing. If threads are locked after a while, we also keep each thread's number and when to lock it until it has been locked. All of it is deleted when an admin turns it off, or when the bot leaves the server.
  • Scheduled posts (/schedule). We keep what an admin typed into the command (the text of the message, the channel, a role to mention if they chose one, when to post it and in which time zone, a heading and a picture address if they chose them, and whether it is paused) and who scheduled it, until it has been posted for the last time or is cancelled. If a server picks a time zone for its scheduled posts we keep that too, until the bot leaves. It can also be made, changed and cancelled on the website (the same information is kept). It is deleted when the bot leaves the server.
  • Sticky messages (/stick). We keep what an admin typed (up to three messages for a channel), the channel and server, who set it, how many messages to wait before it moves if they chose that, and the number of the bot's own copy so it can be replaced. When someone posts in that channel the bot only counts that a message was posted, never what it says. It is deleted when an admin removes it with /unstick, or when the bot leaves the server.
  • Counters (/counters). We keep which channels are counters, what each one shows, a goal if an admin set one, which role for a counter of a role's members, and the last number it showed. The numbers (members, bots, online, boosts, roles, channels, emoji, and how many members have a role) are totals from Discord: the bot never lists who is in a server or who has a role. A counter is deleted when an admin removes it, or when the bot leaves the server.
  • Media-only channels (/mediaonly). We keep which channel it is on for, how it is set up (pictures only, a few replies, or threads, the reply limits and an optional channel to send people to) who set it up, up to five roles an admin let post anything, and how many messages it has removed (only the number), until an admin turns it off, the channel is deleted or the bot leaves the server. To tell whether a message has a picture, video, sticker or link preview, Discord has to pass the bot the message, which is why this needs the Message Content permission; the bot uses only that it has one, and whether it replies to one, and never reads, keeps or logs what anyone wrote. How many replies a picture has had is counted in memory only, never stored, and forgotten after a few days or when the bot restarts. A message that breaks the channel's rule is deleted, and the person gets a short note that removes itself.
  • Speech locks (/uwulock, /lisplock, /shakelock). Off until a server manager turns them on. While they are on, for each person who is locked we keep the server, the person, who locked them, which of the three locks it is and when it ends, until it ends, the person leaves, an admin turns it off or the bot leaves. A server can also pick the roles that may use the locks, and we keep those role numbers with the server's other settings until an admin changes them or the bot leaves. This is the one place the bot reads what someone wrote: the text of a locked person's messages, only until the lock ends, only to post it again in uwu-speak, with a lisp or in Shakespearean English under their name. It needs the Message Content permission, nothing anyone wrote is kept or logged, and nobody else's messages are read for it.
  • Thank-you notes. Now and then, after someone uses a Sigil command in a server, the bot sends them a short private note that thanks them and links to a vote on top.gg and to Ember for servers. For that it keeps two things in its memory only, never in the database: how many commands each server has used since its last note, and when each person was last thanked (so nobody sees it more than about once a week). Both are forgotten when the bot restarts. We keep a daily total of how many notes were shown, with no server and no person in it. Ember members and servers with Ember for servers are never sent one, and the developer can switch it off for everybody.
  • Pulse Check (/pulsecheck, and the Pulse Check tab on the Dashboard). We keep what an admin set up for each check: the channel it watches, how long the channel must be quiet, the words it posts, the role it mentions, the hours it may post in, whether it is paused, when it last posted and how many times, and who made it, until an admin deletes it, it fails to post several times in a row, or the bot leaves. To tell when a channel has been quiet, the bot notes when a person last wrote in each watched channel, and nothing else about the message: it never reads or keeps what was written. That time is held in the bot's memory only, never in the database, and is forgotten when the bot restarts.
  • Bot look (the Bot look tab on the Dashboard). For a server with Ember for servers, or whose owner has Ember, we keep what an admin chose for Sigil's look there: the name, the about line, the picture and the banner (re-encoded copies of the pictures they uploaded, which we keep only to send to Discord), who last changed it and when, and what was last applied or why it failed, until an admin resets it or the bot leaves. They are sent to Discord as Sigil's profile in that one server. A server with neither plan can try this once for 24 hours: for that we keep that the trial was used, who started it and when it starts and ends, until the bot leaves the server.
  • Levels (the Levels tab on the Dashboard). Levelling is on for every server that has been set up, until an admin turns it off. For each person who earns XP in a server we keep their Discord number, the server, their XP total, the XP they earned this week, how many messages they have written there (a number, counted from the day we began counting for them) and when it last changed. We count that a message was written, a minute was spent in voice, or a command was used; what a message says is not read or kept. /messages shows the message number: to the person it is about, and to people who manage the server for anyone, in a reply only the person who asked can see. The settings an admin chose (XP amounts, level roles, channel and role rules, where level-ups are announced) are kept with the server. A person's XP and message count in a server are removed when they leave it, when an admin resets levels, and when the bot leaves, and everything about a server's levels is removed when the bot leaves. A vote on top.gg gives 15% more XP for 12 hours, using the vote record described below.
  • Weekly report (the Analytics tab on the Dashboard). If an admin switches it on, we keep the channel, the weekday and hour it is posted, when the last one was posted, why the last one could not be posted (if it could not), and who last changed it, until an admin switches it off or the bot leaves. The report itself is made from the daily totals the Analytics tab already shows (counts of joins, leaves and messages, the busiest channels and commands), is posted in the server's channel and is not stored anywhere else. It never contains what anyone wrote.
  • Get started steps (the Overview tab on the Dashboard). If an admin skips a step, we keep which step it was for that server, and when. It goes when Sigil is removed from the server.
  • Likes and dislikes (the What's new page). If you are signed in and like or dislike an update, we keep which update it was, your Discord id, whether it was a like or a dislike, and when, until you take it back by pressing the same button again. Everyone can see how many likes an update has; only Sigil's developers can see the dislikes and who voted.
  • Plans and the pricing pages. So the developer can tell which links lead to a plan, the site and the bot count, as daily totals for the whole site (never who or where): how many people opened a pricing page and which link they came from (a short label such as "thank-you note" or "menu", carried in the link), how many checkouts were opened, how many plans started or ended, how often someone ran into a feature or limit that needs a plan, and how often a thank-you note could not be sent and why. When you start a checkout, that short link label is sent to Stripe along with it so the plan can be counted against it; it holds nothing about you.
  • Purge (/purge). To choose what to delete the bot looks at the latest messages' authors, whether they are pinned and how old they are, never what they say. After a purge that deleted something we keep one line in the server's dashboard history (who ran it, when, how many messages and in which channel) for 90 days, like the other changes described below. Nothing about the messages themselves is kept.
  • AFK (/afk). We keep the server, the person, the reason they typed and when they went AFK, until they write something in that server (which clears it), they leave the server, a week passes, or the bot leaves. The bot only checks who wrote a message and who it mentions, never what it says.
  • Role menus (/rolemenu, and the role menu builder on the Dashboard). We keep what an admin set up: the menu's title and words, its roles and their labels, the channel and message it is in, and who made it. A picture an admin uploads for a menu is stored like a card picture (unlisted, not private: it has to be reachable by Discord to show in the menu), counts toward that admin's picture storage, and is cleaned up (the next time that admin uploads a menu picture) once no menu has used it for a day, or removed when the admin's pictures are removed by a moderator. When someone presses a button on a menu the bot gives or takes off that role; it does not keep a list of who picked what, except for a role that lasts a limited time, where we keep the server, the person, the role and when it runs out, until the role has been taken back. The Match my Sigil profile button reads the games and other picks on the profile of the person who pressed it, only to decide which of the menu's roles to give them, and keeps nothing from it. A menu is deleted when an admin deletes it, when its message or channel is deleted, or when the bot leaves the server; a role's timer is deleted when the role is. How many times each role is picked is counted as a daily total for the server's Analytics, never who picked it.
  • Reminders (/remind, and Sigil: Remind me on a message). We keep your Discord number, the words you typed, when the reminder is due, how it repeats, where it should be sent (a private message, or the server and channel you made it in) and, if you set one, your time zone. For a reminder made from a message we keep only the link to that message, never what it says. A one-off reminder is deleted about two days after it was sent (so its Snooze and Done buttons keep working for that long), a repeat stays until you stop it, and you can cancel any of yours with /remind list. If you add Sigil to your own Discord account, Discord tells the bot where you used a command (the server or chat), which is only used to send the reminder back.
  • The server dashboard (Dashboard). To show your servers we use the list Discord gives us when you sign in (the servers you are in and what you may do there), which is already kept as described above. For each server that has the bot, the bot sends the website a copy of its structure: the server's name and icon, how many members it has, the names and order of its channels and roles, the colour of each role and which permissions each role has and the bot has. Never who is in the server, who has which role, or anything anyone wrote. Only people who manage that server can see it, and it is deleted when the bot leaves. When you change something there we keep a short history for that server (your name, when, and one sentence like "Saved the welcome message", never the content) for 90 days, so the server's managers can see who changed what. A /purge that deleted messages is noted in the same history. Buttons like Send a test leave a short request for the bot (who asked, which server, what happened), kept for a day.
  • Server analytics (the Analytics tab of the Dashboard). For each server that has been set up, Sigil keeps daily totals: how many people joined and left (and how old their accounts were when they joined, and how long they had been in the server when they left), how many messages were sent in total, in each channel and in each hour of the day, how many different people wrote something that day (a number only: the people are counted in the bot's memory and forgotten when the day is over), how many times each Sigil command was used, time spent in voice channels, what Sigil did (welcomes and goodbyes posted, roles given, scheduled posts sent), and the server as it stood (its size, boosts and how many channels, roles and emoji it has). Never who did any of it, and never what anyone wrote: Sigil counts that a message was sent, the same way it already knows when to add a reaction. Only people who manage that server can see the numbers. Days older than 90 are deleted, everything is deleted when the bot leaves the server, and an admin can switch counting off or delete the history at any time on the Analytics tab.
  • Invite tracking (the Invites tab of the Dashboard, and /invites). Off until someone who manages the server turns it on. While it is on, for each person who joins, Sigil keeps their name as it was then, which invite link they used and who made that link (when Discord lets the bot tell), and when they joined and left. Nothing else about them, nothing about people who joined before it was turned on, and nobody who is a bot. Discord does not say which invite was used, so the bot works it out by comparing the server's invites before and after, which is why it needs the Manage Server permission. Only people who manage the server can see who joined (the dashboard); /invites shows everyone only totals (how many people someone brought in and how many are still here), never the names of the people who joined. If an admin sets up rewards we also keep the roles and the number of people each needs, and the fact that a person was given a reward role (their number, the role and when) so it is given once, until that person leaves the server; if an admin picks a channel for the weekly thank-you we keep the channel and when it last posted. The post names the people whose invites brought the most new members that week, with the numbers, never who joined. History older than a year is deleted, an admin can delete it all or switch it off at any time, and it is all deleted when the bot leaves the server.
  • The bulletin (/bulletin). An admin can make a locked voice channel whose name changes every few minutes between facts about the server: the newest member, how many members there are and how many joined today, how many are online, the day's message count, the busiest channel, how many are in voice, the busiest hour, boosts, whose birthday it is and milestones. It keeps the channel's id, the name it last showed, the name of the person who joined last (as it was then) and how many joined today, and a few markers so a milestone is announced once. The numbers come from Discord and from the server's daily counts described above; nothing anyone wrote is read. Names are shown unless an admin runs /bulletin names:False, which shows counts instead. /bulletin off deletes the channel and the record, and they are deleted when the bot leaves the server.
  • The bump reminder (/bumpremind, and the Bump reminder page on the Dashboard). When an admin turns it on, Sigil notices when DISBOARD answers a /bump in the server and posts the server's own reminder later (two hours after a bump, or 30 minutes if the server says it has DISBOARD Pro). Sigil does not read what anyone writes to do this: it only sees that a message came from DISBOARD and that it was the answer to the /bump command, and who used the command. We keep what the admin set up (on or off, the words, up to three roles to ping, the channel, the words, title and removal time of the little confirmation message posted right after a bump, whether the server has DISBOARD Pro, and who last changed it) until the bot leaves the server, and, while a reminder is waiting, the server, the channel, the person who bumped and the time it is due. That is deleted as soon as the reminder has been posted, when it is turned off, or when the bot leaves the server. For a server that says it has DISBOARD Pro we also keep the times of its bumps for the last 24 hours (nothing else about them), because Pro's waiting time depends on how many bumps there were in a day; each time is deleted 24 hours after the bump, or when the bot leaves the server.
  • The starboard (/starboard, and the Starboard page on the Dashboard). An admin chooses an emoji, a channel and a number of stars for each star type. Sigil then looks at reactions made with that emoji, and only the ids: which message, which channel and who reacted. When a message reaches the number of stars, Sigil reads that message once (its words, pictures and the message it replied to) to copy it to the channel the admin chose, and only if the bot has the Message Content permission. A message from a channel the whole server cannot see is not copied to a channel the whole server can see. We keep the settings the admin chose, and for each message that was given a star the ids of the message, its channel and its author, its number of stars and the id of its copy, and for each star the id of the person who gave it. That is deleted when the message is deleted, when a moderator deletes its copy, when the star type is deleted, or when the bot leaves the server. The words of a message are not kept by Sigil: the copy is a message in the admin's own channel, and Discord keeps it there. The leaderboard (/starboard leaderboard) is only offered to people who can see the star type's channel; the answer is an ordinary message in the channel where it was asked, so everyone who can read that channel can read it.
  • Trigger words (/triggerwords, and the Trigger words page on the Dashboard). An admin lists words or short phrases. When the bot has the Message Content permission, Sigil compares each new message in that server with the list, in memory, and forgets the message at once if it has none of the words. A message that has one is posted again through a webhook under the writer's own name and picture, and the original is deleted; the copy is a message in the server, and Discord keeps it there. Only plain text is posted again. We keep whether the feature is on, the words, who added each and when, until an admin removes them or the bot leaves the server. We do not keep the messages. On one server a trigger word can also give a role to the person who used it, or take one away (/triggerrole); for that we keep the word, the role's id and which of the two it does. This works like /uwulock, but by what a message says rather than who wrote it.
  • The jail (/jail, and the Jail page on the Dashboard). An admin chooses a jail channel and role, how many thumbs-up a vote needs, and which roles may use /jail and which may start /jail vote. Sigil reads no messages for this. When someone is jailed, Sigil takes away the roles it is allowed to manage and gives them the jail role, and gives the roles back when they are let out. While a person is jailed we keep their id, the ids of the roles they had, who jailed them (or that it was a vote), the reason the moderator typed, when they were jailed and when they will be let out. That is deleted when they are let out. For a vote we keep who it is about, who started it and the ids of the people who pressed the thumbs-up until the vote ends, and the vote itself for a day after. Sigil also changes the jail role's permissions in each channel of the server so that it can see only the jail channel. All of it is deleted when the bot leaves the server.
  • Custom booster roles (/boosterrole, and the Booster roles page on the Dashboard). When an admin turns it on, a member who boosts the server can make a role of their own and choose its name and colour. Sigil reads no messages for this. To know who may, it uses the date Discord gives with the command for when a member started boosting. We keep whether the feature is on and the role the personal roles are placed under, and for each personal role the member's id and the role's id. The name and colour are the role's own, in Discord. About every ten minutes Sigil asks Discord whether each of those members still boosts the server, and removes the role (and what we kept) when they stop, leave, or the role is deleted. All of it is deleted when the bot leaves the server.
  • The autoresponder (/autoresponder). An admin lists words or short phrases and an answer for each. When the bot has the Message Content permission, Sigil compares each new message in that server with the list, in memory, and forgets the message at once. A message that has one of the words gets the answer as a reply. We keep whether the feature is on and the triggers and answers with who added each and when, until an admin removes them or the bot leaves the server. We do not keep the messages.
  • Going-live alerts (the Going live page on the Dashboard, an Ember for servers feature). An admin can choose Twitch, YouTube and Kick channels and a channel to post in, and Sigil posts when one goes live. Sigil only asks each site whether the public channel is live, and reads the public details of the broadcast (its title, what it is playing, its picture and address and when it started). It reads nothing about the people watching, and nothing about anyone in the server. We keep what the admin set up (the site and channel name, the Discord channel and role, the words, who added it) and the id of the last stream announced, so the same stream is never announced twice, until the admin removes the alert or the bot leaves the server.
  • Birthdays (/birthday). If you save your birthday we keep the month and the day (and the year only if you choose to give it, which is never shown, not even as an age), on your Sigil profile. On the day, a server you are in that has a bulletin and shows names can name you in it, and nobody else sees it. It follows the time zone you set with /remind timezone (UTC if you haven't). /birthday clear removes it everywhere.
  • Creator profiles. If you choose a creator profile, the big button, weekly schedule, featured things, links and Discord invite you enter are kept with your profile and shown on it to everyone. Your links, button and invite are followed through a Sigil address so they can be counted: we keep a number per link per day (for 90 days) and show it only to you. We don't keep who followed a link, and robots and link previews aren't counted. We also count how many visits a creator profile gets from each place (the website the visitor came from, or a name the creator put on their link with ?src=): a number per place per day for 90 days, shown only to a creator who is an Ember member, and never who visited. For an Ember member creator, a signed-in visitor can press “Remind me” on the schedule: that makes an ordinary reminder for that visitor (see Reminders above), and the creator is not told. The card for a Ember creator's Discord server shows its member and online counts, which the site reads from the creator's public invite (what Discord itself shows next to an invite) and keeps for half an hour. Switching back to a personal profile hides these but keeps what you entered; you can empty them any time on Edit profile.
  • Confessions (/confess). What a member writes is posted in the server's confession channel with no name attached, and nobody in the server (admins included) can see who wrote it. Sigil does keep who wrote each confession, with its text and where it was posted, only so the developer can step in over abuse; it is never shown to anyone in the server. They are deleted when the bot leaves the server.
  • Goodbye messages (/goodbye). We keep what an admin set up (the words, colour and picture choice, the channel, and who last changed it) until the bot leaves the server. When someone leaves and the server has goodbyes on, the bot posts a message using their name, their avatar and how many members are left; it doesn't keep anything about the person who left, and it never pings anyone.
  • Auto roles (/autorole). We keep what an admin set up (the roles for new members and for new bots, the delay, whether to wait for rules screening, and who last changed it) until the bot leaves the server. When someone joins the bot gives them those roles; if they have to wait (a delay, or rules screening), we keep the server, their Discord number and the time until they get their roles, they leave, or a week passes. The bot uses only the fact that someone joined and whether they have passed rules screening.
  • Colour roles (/colour, /colours, /colourroles). We keep what an admin set up (which palettes are offered, the colours they added, the limits, the role the colour roles sit under and the role needed to use it) and the colour roles the bot made in each server: the role, its colour and when it was made. For each person who chose a colour we keep the server, their Discord number, which colour role they wear and since when, so the colour list can say how many people wear each colour. That is removed when they take the colour off, when they leave the server, and when the bot leaves it; a colour role nobody wears any more is deleted about an hour after it was made or last worn. To offer Match my avatar, the bot looks at the colours of your Discord avatar once, in memory, and keeps nothing from it; Match my Sigil profile reads the colour theme of your own profile. The bot never reads what anyone writes.
  • Votes on top.gg (vote unlock). Four server tools (scheduled posts, auto threads, counters and invite tracking) can ask a server for one free vote for Sigil on top.gg before the server sets them up; one vote opens all four. When Sigil asks for a vote it posts a message in the channel where the command was used, with a vote link that names the server; we keep which server, channel and message that is, and who used the command, for up to a week, so the message can be updated when the tools open. When you vote, top.gg tells us your Discord number, the time, whether it was a weekend vote, and the server the link named (so the server opens by itself). That is all we keep about the vote: nothing about your top.gg account, and anything else added to the vote link is ignored. A vote is removed after 30 days, used or not. If you use your vote to open a server, we also keep which server, the day and that it was you, until the bot leaves that server. It is used for nothing else.

CONQUEST

  • If you take part in CONQUEST we keep which server you pledged to and when, when you last changed it, and how many times you changed it. Your gathering jobs (what, how long, and how they ended) are kept while the season runs, and the resources they earn go to your server's shared stockpile, never to you personally.
  • Every CONQUEST action is written to a log that only the people who run Sigil can see, so mistakes and cheating can be found and put right. It names the person who did something. The news feed on the CONQUEST page shows only your own server's events and never names anyone.
  • If you are banned from CONQUEST we keep that, and the reason given. Whether you want a direct message when a job finishes is kept too; it is off unless you turn it on with /conquest notify.
  • For each server that joins, we keep its name, which channel its CONQUEST news is posted in and who chose it, its stockpile, and (only for the website) whether that channel is working. The bot checks that channel; it doesn't read anything anyone writes in it.

Ember, trials and gifts

We keep whether you're an Ember member and, when it was given for a limited time, the day it ends. When you start a free trial, or the person who runs Sigil makes you an Ember member for a while, we keep a short record of it: which account, what kind, when it started and ends, and for a gift the person's own note (only they see it). That record is only used to run the offers and answer questions about them. A free trial is started on Stripe's page with a card, which is charged when the free days end unless you cancel first (see the Terms); the card itself is handled only by Stripe, as described below.

If you get Ember, the payment happens on Stripe's page. We never see or store your card number. We keep only your Stripe customer and subscription ids, the state of the subscription (for example active or cancelled), and the day the period you have paid for ends, so we can keep you an Ember member and let you manage or cancel it. What Stripe itself holds is covered by Stripe's privacy policy.

Ember for servers. A Discord server can have its own plan, bought by someone who manages it. For that we keep which server it is for, the Discord number of the person who bought it (so they can move it to another server or manage the billing, and so they are an Ember member while it runs), the Stripe ids and the day the paid period ends, as above. A server plan given by the developer keeps who gave it and any note. This record is kept even if the bot is removed from the server, because the plan belongs to whoever paid for it and may be moved or resumed; it holds no member of the server, only the server's number. The server's Bulletin look (its frame, font and wording) is deleted when the bot leaves, like its other settings.

Your Ember number, gem and drops. When you become a member we keep your Ember number, the day you became one and how many days you have been a member (which is what gives your gem its stage). They are kept when a membership ends, because the number is yours for good. We also keep which season's drop you claimed, and the looks you chose from it, with the rest of your profile choices.

The monthly recap. On the 1st of each month, for anybody who played enough, we write one record for the month that has just ended: your hours in games (only if you turned on Count my game time), your three most played games, how many days you played, your Weave days, longest run and points, and your level. An Ember member sees it as a picture and can have it sent as a private message; somebody without Ember sees a blurred copy. Only you can see yours, and recaps are deleted after twelve months.

Gifts. When somebody gives Ember we keep the code, who bought it (their Discord number and the Stripe checkout), whether it has been used, and who used it and when. The person who opens a gift link sees “Somebody gave you Ember” and nothing about who it was from.

Notes about Ember. On your own profile and on the Weave page we may show you a short note, for example that a Weave streak just ended or that a recap is waiting. We keep which notes you put away so that they do not come back. They are only ever shown to you on the site, never in a server.

Weave, the daily word game

When you cast a word in Weave we keep the word, its points and the day, tied to your account, so you can see your results, your streak and your scores, and so the list of everyone's words (with no names) can be shown to people who have cast that day. We also keep your score and when you cast it for each server you are in that has the Sigil bot, so that server's board can show your Sigil name and score once the day is over. During the day a server's board only shows who has cast. A word is never shown to a server. Board entries are removed after two weeks and when the bot leaves a server; your own casts are kept for your record. To find your servers, the site uses the list of servers Discord gave it when you signed in, as CONQUEST does.

Your scores also add up to rankings (this week, this month and all time), which show your Sigil name and your points to anybody. You can switch both the server leaderboards and the global ranking off with “Show me on Weave leaderboards” under Privacy on Edit profile: it is on until you do. You can still play and see your own results, and nobody else sees you on a leaderboard or is told you played.

Weave can also be played as an Activity inside Discord. Signing in there uses Discord's own sign-in and asks for the same two things as signing in on this site: who you are, and which servers you are in. The site checks them once and gives the game a signed token that works only for Weave and runs out after twelve hours. It sets no cookie. Nothing is kept beyond what is described above.

We also keep, for each server whose board you have been on, the last day you played there and whether you asked not to be pinged. The server's daily Weave message, or the first time the game is posted that day, uses it to mention people who have played there in the last month and whose last game was played in that server, so you are pinged in the one place you last played and not in all of your servers. To know that place we keep which server (or your private messages with the bot) you last played in, and when: it comes from the server message you followed a link from, the Activity you opened, or the command you used. A server's administrators can switch pings off for the whole server, and you can switch them off for yourself on the Weave page. This is forgotten two months after you last played there (a choice not to be pinged is kept so it is still respected if you come back), and when the bot leaves the server. While the day is on, the message also shows who has cast today as mentions of their Discord accounts, which is how Discord shows names.

If a server's administrators choose a weekly champion role we keep that role, who holds it now and which week it was last given for. Each Monday the bot picks, from that server's board for the week before, the person with the most points (only people who are on Weave leaderboards can be picked), gives them the role and takes it off the champion before; it names them in the server's Weave channel. The Copy result button and /weave share:True write a few lines (your points, how long your word was, your place that day and your streak) for you to copy; nothing is kept and the word is never in them. The past days page shows each of the last two weeks' letters, how many people played and the best score, and your own score if you are signed in, and never a word or a name.

Weave in private messages. Weave also works in your private messages with the bot, in a chat with a friend and in group chats. In your messages with the bot, if you use /weave there or switch "Direct messages" on in your Weave settings, we keep that you have a personal game: your Discord number, your private channel with the bot, the id and day of the game's message (so it can show your result), the time of day you last played (so the reminder comes then) and the last day you played. The message shows only your own result, never a word. The bot sends the daily reminder there only if that is where you last played and you have played in the last week; you can stop it any time with /weave pings:False there or on the Weave page, and it stops by itself if Discord says the bot can't write to you. In chats with other people the bot can only answer your command, so it keeps nothing about those chats.

Weave extras for Ember members. We also keep which days you used a streak freeze on, and the words you played from the archive (a missed day), which are marked as such and are never on a board or in a ranking. If you are in a private league we keep that you are a member, its name and its invite code. The other members of that league can see your Sigil name and your totals (never your words), whether or not you have switched leaderboards off, because joining is your choice and only members can look inside. You can leave a league any time; if the person who made it leaves or deletes it, it is deleted for everybody.

Reports and moderation

Anyone signed in can report a picture or a profile. Reports, including any note the reporter writes, are seen only by moderators. The person reported is not told who reported them. Moderators can remove a picture, an avatar or a background, and can stop an account from uploading pictures. Reports are kept as a record of what was done.

To keep Sigil safe, moderators and the person who runs Sigil can also erase text and pictures from a card (a bio, a display name, the words in a text box, social links, uploaded pictures, an avatar or a background) without waiting for a report, for example if it is abusive, hateful or illegal. Erasing is permanent. We keep a short log of it (who did it, whose card, what was removed, when, and the moderator's own note), which only the person who runs Sigil can read. Moderators cannot erase a developer's or another moderator's content.

Counting visits to this website

To learn which pages are useful and where visitors come from (a search, a bot list, a link in a post), the site counts page views. It keeps only daily totals: on this day, visitors who arrived from this place looked at this page this many times. The place is the page that sent you (as your browser reports it) or a name carried in the link (like ?src=topgg). It sets no cookie, saves no address and keeps nothing that could be traced back to you. To tell "100 views" from "30 different people", a short fingerprint is made from your address and browser using a random secret that lives only in the server's memory; it is never written down and is forgotten when the day ends. Only the site's public pages are counted (not signed-in tools, your profile, or pictures), and totals older than about six months are deleted. The commands of the bot are counted the same way, as a daily total for each command with no server and no person attached. Programs that read the site (search engines and similar) and the previews that Discord and other apps make of a pasted link are told apart from people and counted on their own.

Views of a card. A card shows how many times it has been looked at. That is one for each different person who is signed in (counted once a day) plus one for each different visitor who is not (counted once a day, using the same short fingerprint that is forgotten at the end of the day, which is never saved). The profile's owner looking at their own profile is never counted, and neither are robots. Nothing is kept about who looked at a card beyond that a signed-in visitor looked on a day.

Which parts of Asterism are used. To see what is worth improving, the site counts how often each part of Asterism is used (opening a star's panel, accepting a contract, opening a window and so on). It keeps a daily total for each part and, for signed-in people, how many different people used it that day: a number only. The people are counted in the server's memory and forgotten when the day ends. It does not keep who used a part or what they looked at (which star, which contract, which answer), sets no cookie and saves no address. The developer's own use and robots are not counted, and totals older than 90 days are deleted.

Where visitors stop and what they press. To see which parts of the public pages work and which are skipped, a small script on those pages notes, as you leave, which parts of the page you scrolled to (for example "plans" or "matchmaking"), which part you were at, and which links and buttons you pressed (for example "link:/invite"), and sends only those names to the site. They are added to a daily total for the page and totals older than 90 days are deleted. Nothing you type is read, no address and no cookie is saved, and nothing is tied to your account or to you: a total cannot be traced back to a person. Pages that are yours (your profile, your settings, the dashboard) are never measured. It does nothing at all if you have Do Not Track or Global Privacy Control switched on, and robots, link previews and the developer are not counted.

Cookies

We use only the cookies the site needs to work: one that keeps you signed in, and small ones that protect forms from forgery and carry a message from one page to the next. There is no advertising and no tracking of individuals: the visit counts above use no cookie. The one exception is the site's developer, whose own browser is given a cookie that only says "don't count my visits", so their own browsing does not skew the numbers; nobody else ever gets it.

Other companies

  • Discord handles sign-in, and your Discord avatar is loaded from Discord's servers.
  • Stripe handles payments for Ember plans, on its own page with its own cookies. It is only involved if you choose to subscribe.
  • Music services. Your Now playing card has a button that opens the song on Spotify, YouTube, Apple Music or SoundCloud, but only when a visitor presses it; nothing is loaded from those companies when a profile is viewed. The fonts on this site are hosted here and are not loaded from anyone else.

Pictures we keep

Uploaded pictures are re-saved by the site, which removes hidden details such as the location a photo was taken. A picture you upload but don't use on a saved card or in your gallery is deleted automatically after a day. Removing a picture from your gallery deletes it, and taking off your banner or your song deletes the banner or the cover we kept. Banners and gallery pictures can be reported and removed like any other picture.

Removing your data

You can delete your pictures, remove your background and avatar and empty your profile yourself. There isn't a button to delete your whole account yet; to have it removed, or to ask what we hold about you, contact sigildev26@gmail.com .

The rules for using Sigil are on the Terms page.