Privacy Policy

Effective date: July 14, 2026

Last updated: November 3, 2026

Six Axes (“Six Axes,” “we,” “us”) is operated by Kerf and Code, LLC, a Washington limited liability company, contact kncadmin@kerfandcode.com, 739 N 95th St Apt 103, Seattle, WA 98103. This policy explains what we collect, why, who we share it with, and your choices.

Six Axes is a session-analytics and campaign tool for tabletop RPG game masters (“GMs”) and their players. Some of you create an account (typically GMs); some of you join through a share link from your GM (typically players). This policy covers both, plus our website and free tools, our Discord integration, our browser extension and Foundry VTT module, and any companion apps.

The short version

• We collect the campaign data you create, optional session audio and the transcripts and analytics derived from it, the dice rolls your table chooses to send us, and the inputs players give us (a play-style inventory, post-session check-ins, party chat, notes).
• We never sell your data and we do not run ads.
• We use named third-party services to run the product (database, hosting, transcription, AI, email). They process your data on our behalf. Two of our AI providers, Deepgram and Anthropic, do not use it to train their models under their commercial terms; the others are named below and are bound by their own terms.
• Audio is only recorded with consent. Online, consent is per person: if you decline, your voice is never recorded and the rest of your table can still record theirs. In person, one microphone hears the whole room, so everyone present must agree or that session is not recorded. The GM is responsible for obtaining consent at their table.
• Session audio is deleted automatically 60 days after it is recorded.
• You can export or delete your data yourself, from Settings.

Information we collect

Account and identity. If you create an account or sign in, we collect your email and display name, and the basic profile your sign-in provider shares (for example, your Discord user ID and avatar, or your Google profile). Players who join only through a share link may be assigned a temporary identifier without a full account.

Campaign content you create. Campaigns, characters, rosters, codex notes, lore, locations, story threads, loot, maps, encounters, combats, sessions, attendance, and similar records you enter. If a GM imports earlier campaign notes, we receive the text they upload.

Session audio (optional). Audio recorded for a session: per-speaker tracks from a Discord voice channel when the GM enables our bot, or a single room recording from a laptop or tablet when a table plays in person. Audio is processed only with consent (see “Recording and consent”). Online, a speaker who has not consented is dropped before upload, so we never receive or store their audio at all.

Dice rolls and game data. If your table uses them, our browser extension reads rolls made on D&D Beyond, our Foundry VTT module sends rolls made in Foundry, and the GM’s dice roller and combat tracker log the rolls made there. Rolls said out loud may also be picked out of a session transcript. We receive the roll, who made it, and when.

Derived data. Transcripts produced from session audio, the structured events our AI proposes from those transcripts and that the GM accepts, session recaps, the campaign journal, and the analytics computed from all of this (engagement, spotlight balance, dispositions, roll statistics, and so on).

Player inputs. Responses to the Player Disposition Inventory, post-session check-ins (a satisfaction rating, a spotlight question, and an optional note), party chat messages, character pages, and private notes.

Messages you send us. If you use the contact form or apply to the pilot, we receive your name, email address, and what you write.

Payment information. Paid plans are not live yet. When they launch, our payment processor (Stripe) will handle your card details. We will receive confirmation and limited billing metadata; we will not store full card numbers.

Technical and usage data. Log data, approximate location from IP address, device and browser information, and essential cookies used to keep you signed in. Our website uses Google Analytics, which sets its own cookies, to count visits and see which pages are used. When you use the free map generator’s AI render without an account, we log your IP address and the time so we can enforce its daily limit. We do not use advertising cookies.

How we use your information

• To provide the product: store your campaign, transcribe audio, generate recaps, the journal and analytics, run dispositions, render maps, and power scheduling, combat, and chat.
• To communicate with you: session recaps, reminders, replies to your messages, and service notices. You can opt out of non-essential email.
• To operate, secure, debug, and improve the service, and to understand how the website is used.
• To process payments and manage subscriptions, once paid plans exist.
• To comply with law and enforce our Terms.

We do not use your campaign content, audio, or transcripts to build advertising profiles, and we do not sell any of it.

AI processing and service providers (sub-processors)

We rely on the following providers to run Six Axes. They process your data only to perform their function for us:

Most providers process and store data in the United States. Deepgram and Anthropic process your content to perform the service and, under their commercial terms, do not use it to train their models. Groq, Replicate, and Google process it under their own terms. The table above is our current sub-processor list. If it changes, we will update it here.

Not everything that sounds like AI is. The rules compendium’s voice lookup runs speech recognition inside your browser, so that audio never leaves your device. The disposition model, roll statistics, encounter maths, and dice roller are ordinary statistics and code, not AI.

Recording and consent

Online, consent is per person, not per table. When a session is recorded over Discord, each speaker is captured as a separate stream. If you have not given consent, or your GM has excluded you from a particular session, your stream is discarded when the recording ends: it is never uploaded to us, never transcribed, and never used in recaps, statistics, or any analytics. One person declining does not stop the rest of the table from recording.

In person, consent is for the whole room. A single microphone cannot leave one voice out, so the GM confirms before recording that everyone present agrees, and that agreement is stored with the session. If anyone at the table says no, that session should not be recorded. Telling voices apart in a room recording happens within that one recording; we do not build or keep a voiceprint of anyone.

What declining does not do. It removes your voice, not your presence. Other people at the table who did consent may still say your name, quote you, or describe what your character did, and those references will appear in their transcripts and in any recap or analytics built from them. If you want no record of your participation at all, talk to your GM about not recording that session.

While the Discord recorder is running, the Six Axes bot is visibly present in the voice channel, and the GM can end the recording at any time with the /stop command. The GM is responsible for obtaining consent from everyone at the table and for complying with the recording laws that apply where their players are, including jurisdictions that require all parties to consent. We store consent records so it is clear who agreed. You can request deletion of audio at any time. Take particular care recording minors (see “Children’s privacy”).

How your group sees your data

Six Axes is collaborative, so some data is shared within your table by design:

• The GM can see the campaign data, accepted events, analytics, rolls, audio, and transcripts for their campaign.
• Players see what the GM shares with them, plus their own inputs. During a fight, players see the turn order but not monster hit points or monsters the GM has hidden.
• Party chat is private to players by default. The GM cannot read it unless a player grants a specific time-window of access, and the player can revoke that.
• Private notes are private to the player who writes them. The GM cannot read them. On a character page, the player chooses which sections are shared with the GM.

Public pages. A GM can publish a campaign wiki. Only entries the GM marks public appear on it, and anyone with the link can read them without an account. If the GM also lists the campaign, the page can be found by search engines, and a search engine may keep a copy for a while after it is unpublished.

We also share data with the service providers listed above, when required by law or to protect rights and safety, and in connection with a merger or sale of the business (you’ll be notified). That’s it, no other sharing, and no sale.

Data retention and deletion

We keep your data while your account is active and as needed to provide the service. Session audio is deleted automatically 60 days after it is recorded, whether or not you ask. You can export everything we hold about you, and delete your account, from Settings. Deleting your account removes your recordings, your transcribed words, your self-reports, your dispositions, your notes and your check-ins. Your characters remain in their campaigns with your personal link severed, because the story your table told together is theirs as well as yours. We aim to delete or anonymize data within 30 days of an account-deletion request. Backups are purged on a rolling 7-day schedule.

Your rights and choices

Depending on where you live (for example under GDPR or the CCPA/CPRA), you may have the right to access, correct, export, delete, or restrict processing of your personal data, and to object to certain uses. You can exercise these yourself in the app, under Your account, Settings, where you can export everything we hold about you and delete your account. You can also email kncadmin@kerfandcode.com. We will not discriminate against you for exercising them. We do not sell or “share” personal information for cross-context behavioral advertising.

If you are in the EEA/UK, our legal bases are: performing our contract with you, your consent (for audio recording, analytics cookies, and non-essential email), and our legitimate interests in operating and securing the service.

Children’s privacy

Six Axes accounts are intended for adults 18 and older. Tabletop games are often played by minors, so a minor may participate at a table through a GM’s share link. In that case the GM or the child’s parent or guardian is responsible for any consent, especially for audio recording. We do not knowingly collect personal information from children under 13 without verifiable parental consent as required by COPPA, and we do not knowingly direct the service to them. If you believe a child under 13 has provided us personal information without that consent, contact kncadmin@kerfandcode.com and we will delete it.

Security

We protect data with encryption in transit, row-level security in our database, scoped access controls, and least-privilege service credentials. No system is perfectly secure, so we cannot guarantee absolute security.

International users

We operate in the United States and process data there. If you access Six Axes from outside the US, you consent to that transfer and processing, subject to the protections described here.

Changes

We will update this policy as the product evolves and post the new date at the top. Material changes will be communicated by email to account holders and by notice in the app.

Contact

Questions or requests: kncadmin@kerfandcode.com, Kerf and Code, LLC, 739 N 95th St Apt 103, Seattle, WA 98103.