FullSwing

Privacy

Nobody should have to hand a company a list of what they are into. This is built so that we never receive one.

In EU terms, what you mark yes, no or curious is special-category data under Article 9 of the GDPR. The safest way to hold data like that is not to hold it, and that is the whole design rather than a policy on top of it.

Draft — Not legal advice, and not final wording. A lawyer has not read this page. It describes what the software actually does; the formal notice follows once the entity is settled.

The app

Your answers — what you marked yes, no or curious — are written to storage on your own device and are never sent to us. There is no account and no login, so there is no record of you to lose, hand over, or sell. That is not a promise about how we behave; it is a description of a system with nowhere to put the data.

Playing across several phones is the one time anything leaves yours. What travels is encrypted on your device first and can only be read by the phone running the game — not by us, at any point. It is held for the length of the session and deleted when the next one starts. Individual answers are never shared between people in either direction; only the result of combining them.

Play again with the same people and what is remembered is that combined result, never anybody’s individual answers. The combination is something you all disclosed to each other by playing. Your own yesses and nos are not.

This website

Cookies, and why there is no banner

One cookie exists today, and it is strictly necessary — the kind that needs no consent and therefore no banner. There is no analytics cookie, no advertising cookie, and nothing stored in your browser beyond this.

pt
Set only if you enter a playtest code, and only so the next page knows you entered one. It lasts until you close the browser, no script can read it, and it is sent nowhere except back to this site.

An age acknowledgement will be added when there is anything on this site that needs one. It will work the same way: strictly necessary, browser-session only, and named here before it ships. There will not be a third.

What the server sees

Answering any request means receiving your IP address, the way every web server does. Whether the CDN in front of this site keeps a log of that — the ordinary record of which page was asked for and when — is not something we have turned on.

Draft — Access logging is undecided. If it is ever switched on, this section will say so, say what is in the logs and how long they are kept, before it happens. One thing already known: a playtest code travels in a URL, so it would appear in such a log.

If you submit a card

The card submission form stores what you typed into it: the pseudonym you chose, the card, its tags, and any notes. Alongside that it records the date and which version of the rights wording you were shown, because consent attaches to the words that were on the screen.

It does not record your IP address, your browser, or where you came from. Those are the three fields a form usually collects without mentioning it, and they are the ones that would turn a pseudonym back into a person.

You are shown a submission ID when you send a card. Keep it, and that card comes out whenever you say so — without you ever having to tell us who you are. Quote it at Support.

Draft — How long card submissions are kept has not been decided. They are working material for a deck rather than records about people, so the honest answer is probably "until the deck ships" — but that is a decision, and it belongs here in writing once it is made.

Your rights

The usual GDPR rights apply — access, correction, erasure, objection, and a complaint to a supervisory authority. There is deliberately very little for them to bite on, which is the point rather than an evasion:

Draft — A published contact address for privacy requests. Needed before this page is finished, and before the app ships.

Draft — The controller's identity, and the supervisory authority you can complain to, both wait on the entity decision. See Imprint.