Privacy Policy

Your account. You sign in with Google or GitHub through Google Firebase Authentication. From that sign-in we get and keep your email address, the name and photo on that account, and an account id. If you use GitHub we also keep your GitHub username and the year your GitHub account was created. We never get your password, and we don't ask Google or GitHub for anything else (no contacts, repositories or calendar).

The first time you sign in we ask for a short profile: a display name, your role (for example engineering or design), a range for your years of experience, optionally the areas you work in, and optionally a link to your LinkedIn profile, which we show back to you but do not check. We also keep the version of these terms and this policy you agreed to and when, a list of the rooms you have hosted or joined, for Your jams, and, if you pick one there, the colour theme your new rooms start in. Only you can read your profile and that list.

When you start or join a room, the room stores:

• your account id, the name you choose for the room, your role and your years range, whether you are connected, and when you last were
• the prompts and ideas you submit, and when you submitted them, and, for a pre-mortem's early warning or way to head a risk off, which risk it covers, which everyone in the room sees like the idea itself
• the room's vote and rating totals, and whether each person has started or finished voting (so the room can see who it is still waiting on), never which way
• if you tap "I've got something" while the room talks, your room name in that section's speaking queue, which everyone in the room sees, until you leave it, the host moves on or the section is locked
• which version of these terms and this policy you agreed to, and when

Your votes are anonymous in storage, not only on screen. What you vote for, how you sort ideas, which lines you keep or cut, how likely and how bad you rate a risk in a pre-mortem, and whether you tap Agree, Unsure or Concern are stored apart from the room, where only your account can read them, so your phone can show you what you picked. The room itself, and everyone in it, sees only the totals. Tapping your reaction again to send more of it to the big screen is counted the same way: the room keeps how many of each reaction were sent, and your private record keeps only when you last sent one, so a phone can't flood the room. Our own systems read the votes only to work out the totals by role described next. One limit: totals move the moment a vote lands, and a second or two later the room learns that you have started or finished. Someone watching the room's live data closely while few people are voting may be able to guess whose vote moved a total.

The room's screens, documents and stored data never show who voted for what. We use your role to describe which kinds of people backed a decision in the room's finished document and seed packet (for example "engineering 3 of 4"), worked out once the vote has closed and stored only as that result, but only for a role with at least three voters in that vote, and never where a smaller group's votes could be worked out from the totals, so it never singles out one person's vote. If everyone in a group voted the same way, the breakdown shows that, as a vote count shows it when a whole room agrees. Your role and years range never change how much a vote counts. Your email, LinkedIn link and GitHub username are never shown in a room.

Firebase keeps you signed in by storing a sign-in session in your browser. Your browser also remembers, for itself, the room you were last in, an idea you started typing but haven't sent, the GitHub repo you typed on a recap, the room you last opened checkout for (so it can take you back there after paying), how many rooms you have hosted from it, and, on a big screen, whether you switched it between live and calm and which celebrations it has already played. Those stay on your device, except that the hosted count is sent with analytics as a rough range (none, one, a few, many) so we can tell whether hosts come back. Clearing your browser's site data removes all of it.

We do not ask for your location. Anyone who has a room's four-letter code can read everything in that room, including the names, roles and years ranges of the people in it, and including after the session ends.

We use Vercel Web Analytics to count page views and a few product events, such as a room being created, a session finishing or a seed packet being copied. Events carry counts, room codes, which AI tool a packet was opened in and that rough hosted range, never names or anything you typed. It does not set cookies and does not build a profile of you. Our hosting provider also keeps standard server logs (IP address, browser, page requested) to deliver the site and protect it from abuse.

The big screen and the host's device. While a room writes, the big screen groups ideas by meaning using a small open-source language model that runs on the screen's own device. The host's device runs the same model, so that ideas saying the same thing go on the ballot as one. Your ideas never leave either device for this: all the host's device saves to the room is which ideas go together, titled with one of those ideas. To run it, each device downloads the model from Hugging Face and its runtime from jsDelivr, once per browser; like any download, those services see the request (the device's IP address and browser), not what anyone typed.

The seed packet is built in your browser. If you copy it or open it in Claude, Grok or another AI tool, what happens to it there is governed by that provider's terms, not ours.

Continue in your Claude or Grok. Once a room has finished, the account that started it can make a connector link on its done screen. Added to an AI assistant that person chooses (such as Claude at claude.ai, Grok at grok.com, or another tool that speaks the Model Context Protocol), the link lets that assistant read this one room: its topic, finished document, seed packet, the calls the room made with their vote and rating totals, and its tasks with the names of the people who took them and their due dates. Never how anyone voted or who wrote which idea, and nothing it can change. It reads the room only while the session is finished, never during one. Making a link records which version of these terms and this policy its maker agreed to, and when. We keep only a fingerprint of the link (a hash), never the link itself, so we can't show it again. Anyone who has the link can read the room through it until it expires after 30 days, or until the room's creator revokes it, makes a new one, deletes the room or deletes their account, any of which stops it at once. Our hosting provider's logs record the addresses requested, which include the link. What the assistant does with what it reads is governed by its provider's terms, not ours.

Recaps. When a session finishes we save a copy of it (the topic, prompts, ideas, vote and rating totals, the seed packet and, in an unlocked room, the AI-written spec) at a recap link with a long random address. Recaps name nobody except the room name of whoever took a task, never who voted or rated what. The link is stored in the room, so anyone with the room code can find it, as well as anyone you share it with. Until rooms have membership checks, treat a recap as readable by anyone who has the code.

Payments. If you buy a pass or a plan, Stripe collects your payment details, email address and country to take the payment, under Stripe's own privacy policy. We never see or store your card number. We keep which room or team the payment was for, Stripe's ids for the payment, whether it was refunded, and, for a subscription, its status and renewal date. For a team plan we also keep which accounts are on the team, so the rooms they host can be unlocked. We can see the purchaser's email and country in Stripe's dashboard, and use them only to provide and support what you bought.

AI features. When they are switched on, they run in every room, free or paid. A room's prompts, ideas, the lines people add, vote counts, rating totals and which risk each early warning or move covers are sent to Anthropic, never with names, so Claude can group similar ideas, draft the room's deliverable, ask the one question the finished draft doesn't answer (“the question nobody asked”), write the one-sentence teaser and, in an unlocked room, write the spec. Nothing from a room played before these terms is sent. Anthropic processes this as our service provider (a subprocessor) under its commercial terms, which say it may not train models on it.

If you email hello@schleuger.com, we hold that message and your address for as long as it takes to reply and keep a record of the conversation. We do not add you to a mailing list.

Everyone with the room code, by design. Beyond that, only the services that run Seedpack: Google Firebase (signs you in, and stores your profile, rooms and recaps), Google or GitHub (whichever you sign in with, which learns that you used Seedpack), Vercel (hosts the site and counts page views), Stripe (takes payments, and only if you pay), Anthropic (when AI features are on, groups every room's ideas, drafts results and asks the question nobody asked, and writes the teaser and spec for rooms that use them; never with names), Hugging Face and jsDelivr (serve the big screen's grouping model and its runtime, and see only the download), the AI assistant a room's creator connects to the finished room (what it reads is set out in section 1), and anyone the law requires us to.

We do not sell personal information, and we never have.

Rooms are kept for up to 12 months from when they were created, so a team can come back to its seed packet, and then deleted with everything stored under them: ideas, names, votes and the room's place on each member's jam list. While a room exists, anyone with its code can read it. The account that started a room can delete it for everyone at any time from the room itself, which deletes the same things straight away, along with its recap unless someone paid for it. We may delete rooms sooner, for example to stop abuse. To have a room removed that you didn't start, or one started before sign-in existed, email hello@schleuger.com with its code.

Your profile, your jam list and your sign-in are kept until you delete your account, which you can do at any time from Your jams (https://seedpack.app/me). That deletes them straight away, and ends any connector link you made. What you said and voted in rooms stays with those rooms until the room is deleted or expires, when it goes with the room; email us if you want your part removed sooner.

Recap links work for 7 days for a free room, and 1 year for a room with a pass or on a team plan. After that the link stops working. The saved copy is deleted with its room, or once its link has stopped working if the room is already gone. A recap someone paid for stays until its year is up even if the room goes first, including when the person who started the room deletes it. A connector link stops working after 30 days; our record of it (its fingerprint, who made it, when, and the versions they agreed to) is kept with the room and deleted with it, or sooner when it's revoked or replaced or the account that made it is deleted. Payment records are kept as long as tax and accounting law requires, which is usually several years.

You can ask us for a copy of anything we hold about you, ask us to correct it, or ask us to delete it. You can see and edit your profile, and delete your account, yourself from Your jams. For anything else, such as what you said in a room, email hello@schleuger.com from the address you sign in with, with the room code, and we will respond within 30 days. We will not treat you differently for asking.

If you are in the EU or UK you may complain to your local supervisory authority. If you are in California, the rights above cover CCPA/CPRA access, deletion and correction.

Traffic is encrypted in transit over HTTPS. Database rules tie every write to the signed-in account: nobody can list rooms, read someone else's profile or votes, write as someone else, edit or delete another person's ideas, or vote twice. A room is still only as private as its code. No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects you, we will tell you and any regulator the law requires.

Seedpack is not directed at children under 13 and we do not knowingly collect their information. If you believe a child has sent us something, email us and we will delete it.

We will update this page as Seedpack changes. Material changes bump the version at the top.