
Privacy Policy
Effective date: November 3, 2026
Information and purposes
We process account email, password verification data, account identifiers and your age attestation and policy-acceptance records; chosen profile details; community, group and messaging content; and moderation reports and decisions. We use this information to provide the features you request, control access, prevent abuse and handle support and disputes.
Security checks process technical information and activity counters. Contact delivery uses your reply email, subject and message. Its local ledger stores request references, keyed hashes, status and timestamps, not the email address or message body. Delivery and mailbox systems can retain email copies. An accepted delivery request does not prove receipt or reading.
Who can see information
Public contributions and public profile cards are visible to visitors. A private profile does not hide your name on public contributions. Group content is restricted to group members, and private messages to their participants through the site. Reports and appeals share relevant material with staff.
Public forum threads and replies can appear in search engines such as Google. After a post is removed, copies in search results can take some time to disappear.
Messages are checked before delivery and are not end-to-end encrypted. Authorized operators and service providers can process stored information. Other members may copy what they receive. Removing your own public forum post erases its title and body unless an open report or a documented legal or security hold requires retention. Retained text is erased when no open report or hold remains. Removing a forum thread also hides its replies but does not erase other members’ text. Staff can restore forum posts hidden by staff, but cannot restore author-withdrawn posts or older removals whose origin is unknown. Removing a guild post hides it from guild views but does not itself erase its stored text. The account-closure rules below also apply to guild text.
Guild directory and applications
A Guild Master can list their guild in the public guild directory. A listing shows the guild’s name and the pitch the Guild Master writes, its faction, region, ruleset, guild language and play style, the roles and classes it is looking for, its member count and its upcoming raid times from the guild’s raid schedule. Member names, guild threads, notes and attendance are not shown. The Guild Master can remove the listing at any time, and moderators can remove one that breaks the House rules.
When you apply to a listed guild, its Guild Master and Officers see your community name, the character name, class, roles and professions you enter, and your message. If they accept, that character joins their guild roster. Guild names and pitches, applications and decline notes are checked before they are saved, like chat messages.
The Guild Master and Officers of a listed guild receive at most one email an hour about new applications, unless the Guild Master turns these emails off. You receive an email when your application is accepted or declined. To send these emails we read the recipient’s account email from our authentication provider when sending; it is not stored with the guild or the application.
Open applications close after 30 days. Applications are deleted 30 days after they are accepted, declined, withdrawn or closed. Reports about guild listings are kept until a moderator reviews them. Account closure deletes your applications and reports.
If the Guild Master’s adventurer card is public, the guild’s page also shows their community name and links to the card.
Forever census
The Forever census asks which faction, race, class, region and ruleset you plan to play. Answering is optional and needs no account. We keep your answer, when you gave or changed it, and a random identifier that your browser stores in the tavern-census cookie for up to two years, so this browser changes its answer instead of adding another. If you answer while signed in, your answer is linked to your account and shown as verified.
The census page shows only totals, and a group’s results appear once it has at least 25 answers. A member’s answer appears on their public profile card only while they choose to show it there.
Visitors who answer without an account pass a Cloudflare Turnstile check. To limit repeated answers, we count answers per network for one day using a one-way code made from your network address with a secret key. The code changes daily, is deleted within a day and cannot be turned back into your address, which we do not store. Answers that have not changed for two years are deleted, and closing your account deletes your answer.
Group board
Signed-in members can post a group on the group board. A post shows your community name, the activity and the detail you write, its faction, region, ruleset and levels, its open places, when it starts and your note. Each post belongs to a party in your party planner; if you don’t choose one, a new party named after the post is created for you. The party’s name and its members’ names are not shown on the board.
When you join a group, you take one of its places and join its party with the character name, class and role you enter. The group’s leader and the party’s members see your community name and that character, as in any party. On the board, others see only the class in the place you took. Group posts and notes are checked before they are saved, like chat messages.
A post stays on the board until its closing time: two hours after it is posted or renewed, or two hours after its start time. It leaves the board sooner when every place is taken or its leader closes it. Posts and their places are deleted a day after their closing time, and a post a moderator removed is deleted 30 days after removal. Parties stay in the party planner. Reports about a post are deleted with it. Account closure deletes your posts, the places you took and your reports.
Forum notifications
When someone replies in a forum discussion you started or replied in, or answers one of your posts, you get a notification in the bell at the top of the site. A notification records the discussion, its newest reply, how many replies arrived since you last read it and whether one answered you. You are never notified about your own replies.
You can mute any discussion from the bell or from the discussion itself, and we keep that choice until you turn notifications back on. Read notifications are deleted after 30 days and unread ones after 90 days. Notifications for a removed discussion stop showing straight away. Account closure deletes your notifications and mutes.
A reply that answers another post shows the community name of that post’s author and the start of its text, linked to it. Each post can be edited three times.
The bell also tells you when someone applies to a guild you lead or are an officer of, when your own guild application is accepted or declined, when someone joins your group, when you receive a whisper, and about an hour before a guild raid you said you would attend. These notices record what they are about and the public names needed to show them (the guild, group, raid or community name), never message text. They are deleted on the same schedule as forum notifications, and account closure deletes them.
Services involved
The site uses Cloudflare hosting, including Workers, Durable Objects, D1 and R2. Supabase handles authentication. OpenAI checks full chat and private-message text for moderation. Cloudflare Turnstile provides account and contact security checks.
Resend handles contact delivery and account emails. The configured sending domain is auth.theforevertavern.com and its Resend region is North Virginia, United States. Supabase Authentication is configured in West US, Oregon. Apple iCloud Hide My Email forwards owner contact messages to the approved private inbox. PayPal handles optional tips on its own pages. These project regions do not describe every provider processing location. Service providers may retain their own logs, service records and backup copies under their policies and settings.
Information is not guaranteed to stay in your country or Canada. Fonts and optional music are served by this site. Opening an external link sends your browser to that site and its own privacy practices.
OpenAI also checks guild directory text, and Resend also sends the guild application emails.
Cloudflare Turnstile also checks census answers from visitors without an account.
OpenAI also checks group board posts.
Discord and Google offer optional sign-in. If you use one, it shares your account ID there, your username or name, your email address and your profile picture with Supabase, which keeps them with your sign-in account. We use the email address and account ID to sign you in. The site never posts for you and cannot see your Discord servers or messages or your Google contacts. Discord and Google handle your use of their services under their own privacy policies.
If you choose to show your Discord username, members of your parties and guilds can see it on their rosters, and you can turn this off on your profile. Guild leaders can connect a channel in their guild’s Discord server. The site then posts the guild’s new raids, raid reminders and new applications there (character name, class and role, never the application message), and Discord handles those posts under its own policies.
Guild leaders can also choose to post a guild thread they start to that channel.
Retention and requests
Common Room message text becomes eligible for erasure after 30 days, private-message text after 12 calendar months, and resolved chat and private-message moderation evidence after 90 days. Open reports, pending appeals and documented specific legal or security holds can preserve relevant text longer. Routine cleanup runs in bounded hourly batches, so outages or a backlog can delay completion. The owner checks maintenance results during the daily operational check and addresses failures or remaining work. Routine text cleanup preserves structural message records and ban and block records. Forum and guild history follows the removal and account-closure rules described in this policy. These periods do not erase other members’ copies, provider records or backups.
An automatic moderation decision starts its evidence period when issued. A pending appeal pauses erasure, and completed human review starts a new 90-day period. If evidence has expired, an appeal remains available and must be reviewed using the information still available. You can request account closure through our privacy contact. After verification and review of group ownership, other people’s information and any specific legal or security hold, we remove your profile and authored text from the live site and close the sign-in account. Generic placeholders preserve other members’ contributions. We explain any pending step or limited information that must remain for a documented reason.
Contact ledger records become eligible for cleanup at most 36 hours after ticket issue. Contact attempt counters become eligible 24 hours after their 10-minute window. The hourly maintenance process removes eligible records in bounded batches. Outages or a backlog can delay completion. These rules do not delete email or backup copies.
We verify requests before sharing or changing account information and may ask for proportionate confirmation through your registered account email. We review exports to protect other people’s information and agree a private delivery method with the verified recipient. Contact correspondence is kept while needed to handle the request or a documented dispute, and is reviewed at case completion. Working exports are removed after confirmed delivery and case completion unless a specific documented hold applies. A limited, access-restricted case and closure record can remain while needed to handle the request, enforce closure or prevent erased information from returning after restoration. We review that need when the case is completed and before restoration.
Removal from the live site may not immediately remove every provider record or backup copy. We keep the instructions needed to preserve a completed closure outside ordinary restorable backups. Before making a restored site accessible, we reapply those instructions and check that erased content has not returned. We explain verified provider or backup limits relevant to a request.
Browser storage and cookies
Server-managed ft-auth cookies, sometimes split into numbered parts, have a seven-day maximum age per write and may be renewed. Sign-out clears this browser’s cookies. Temporary account failures can preserve recoverable session state. Password recovery asks an already signed-in person to sign out before continuing; saving a password clears this browser’s session.
The tavern-language cookie lasts up to one year. Local storage keeps background and volume preferences until changed or cleared. Session storage keeps music position and pending invitation tokens. A cross-tab account-change signal is written and immediately removed without identity, tokens or drafts. Contact drafts remain only in page memory.
You can clear browser storage, which may sign you out or discard preferences and invitations. This does not delete your account. Music starts only when you press Play. Security checks can involve additional browser processing.
The tavern-census cookie lasts up to two years and only lets this browser change its census answer.
Local storage also keeps conveniences on this browser: your name shortlist, map layers and leveling side, the guild you opened last, the name, class, role, faction and ruleset you last used in the group finder, and whether you closed the profile welcome card. Session storage keeps an unsent forum reply and your Common Room table until the tab closes.
Local storage also remembers whether your home page strip had anything to show last time, so the page does not jump while it loads.
Site statistics
Cloudflare Web Analytics counts visits without cookies or browser storage. It processes page addresses, the referring site, browser and device type, page load timing and approximate country, and shows us only totals.
Google Analytics runs only if you choose Allow in the cookie notice. It then sets _ga cookies that expire at most 13 months after your last visit, and sends Google the pages you open with their titles, the referring site, browser, device, screen and language details, approximate location, time on page, scrolling, file downloads and clicks on links to other sites. Page addresses are sent without the part after ? or #, except campaign tags that start with utm_.
We do not send account details to Google and do not use its advertising features. Google processes this information, including in the United States. Event-level data is kept for 2 months; summary reports can be kept longer.
Your choice is saved in the tavern-analytics cookie for six months, then we ask again. Use Cookie settings at the bottom of any page to change it. Turning analytics off stops Google Analytics in this browser and deletes its cookies here. Statistics already sent are not deleted.
News links
The main news feed saves headline details and supplied author credits from Blizzard and Blizzard Watch. Class News uses official Blizzard sources only. Each listing is checked at most hourly when used. Publisher descriptions and images are discarded, and full articles and forum messages are not fetched. Staff-topic coverage is limited and does not include every reply. Opening a headline contacts its publisher.
Who we are and how to contact us
The Forever Tavern is an independent community for people aged 18 and over. We operate from Ontario, Canada. Our privacy contact is Privacy Officer, The Forever Tavern. Use Contact the owner or gunk-blimp3b@icloud.com for privacy questions or requests for access, correction, a copy of your information or account closure. Do not send passwords, sign-in links or identity documents.
The owner checks the contact inbox daily at launch and aims to acknowledge requests within two business days. An acknowledgement is not completion of a request; identity checks, scope and applicable requirements can affect the response time.