Privacy Policy

1. Information we collect

1.1 Information you give us

• Account: your email address, password (stored only as a salted hash), username, and real name if you choose to give one. If you sign in with Google or Discord, we receive your account id with that provider and the email address it gives us. We don't receive your contacts or friends lists. If you ask for email about new games, we keep that choice and when you made it.
• Getting started: when you set up a team, we ask how you heard about BoardFlight, your role and what you want to build. You can also add notes in your own words.
• Teams: team names, members and their roles, and the email addresses of people you invite.
• Your content: builds and their details (version, release notes, commit id and engine version), library listings and media, assets, signing keys and playground projects.
• Playground: your project files and saved versions; your conversations with AI tools in the playground; and a usage record for each AI request, which holds the first 120 characters of your request, the model used, and the number of tokens.
• The assistant: if you use the assistant on the creators' dashboard, your questions, its answers and what it looked up to answer them. For each question we also keep a record with no text in it: when it was asked, which AI model answered, how long it took, how many tokens and lookups it used, which of our help pages it read, what it cost, and your thumbs up or down if you gave one.
• Printed figures you buy: what you ordered, for which game, its price, when you paid and when it was posted, and its tracking number. Stripe takes your payment and your shipping address on its own page; we don't receive your card details, and we keep only the identifiers Stripe gives the payment, which is where we read the address to post your order.
• Messages to us, such as support requests and legal notices.

1.2 Information about the games you install, and your Board

There are two ways to install a game.

Through your Board's own page. You download the game and hand it to your Board yourself, on your home network. Our website doesn't connect to your Board, and we receive nothing from your Board when you install this way.

With the BoardFlight app on your computer. The app connects to your Board on your home network and reports the following to your account:

• Your Board: its name, model and software version, an identifier that lets us recognize the same Board again, and which days the app reached it. Your Board's name is shown only to you.
• Your computer: its name, its operating system, the app's version, when the app was last running, whether you chose to keep it running in the background, and, if the app could not update itself, why not.
• What's installed: which of the games you have access to through BoardFlight are on your Board, and which version. The app reports only those games, never your Board's other apps.
• Installs and updates: each install or update you ask for, from the app or from the website: the game, the build, the Board, whether it worked, and the message your Board gave if it failed.
• Notifications on your phone: if you sign in to the BoardFlight app on a phone and allow notifications, we keep the address Apple or Google gives that phone for them, which kind of phone it is, and when the app last registered it. We use it only to tell you on that phone how an install you asked for ended, naming the game and your Board.
• Your choices for each Board: whether games update automatically, the channel a game follows, and any version you pinned.
• Game pieces: the sets of Board pieces you tell us you own.
• Setup events: as described in 1.4, plus how the app found your Board, how long that took, and whether pairing worked or why it didn't (for example, nobody answered the prompt on the Board).
• Checking that a game is on your Board: when a game shows its update card, or when someone starts typing feedback in a game on your Board (a game can also ask on its own), the app may listen to that game's log on your Board for up to 30 seconds, for a one-time code the game wrote. It tells us only whether it found the code and keeps nothing it read.
• The app does not send us your Board's sign-in token, your Board's network address, your pairing codes, your location, or the list of other apps on your Board. It keeps a log file on your computer to help with problems; the log isn't sent to us unless you send it.

Whichever way you install, we also keep, on our side:

• Your games: the games you add to your library or redeem a code for, and the ones you mark as favorites. When you download a game to install it, we record that download (the game and the build) with your account, as a product usage event (see 1.4).

BoardFlight used to offer an app that ran on a Board. It is no longer offered. If you used it, we still hold what it sent us, for the periods in section 5:

• Your Board: for each account and Board, a record with a one-way hash of the Board's model, name and software version that let us recognize it again. We didn't keep your Board's name itself.
• Installs: the games you installed through that app, whether each install succeeded, and the message your Board gave if it failed.
• What was installed: which games you had access to through BoardFlight were still installed on your Board. The app checked only those games, never the list of other apps.
• Game pieces: the sets of Board pieces you told us you own.
• Library activity: games you viewed and launched from the library on your Board, together with your account if you were signed in. If your Board wasn't identified, we counted unique views using a shortened, hashed form of your IP address.
• Setup events: which setup steps you completed and problems such as a failed pairing. These came with a random identifier created when the app was installed, the app's version, and your account if you were signed in.
• The app did not collect your Board sign-in token, your location, your contacts, anything from your camera or microphone, or the list of other installed apps.

1.3 Information from games that use our feedback layer

A game's developer can turn BoardFlight's in-game feedback and analytics on or off for their builds. Play analytics are on by default for a web game published to the library. Where these are on, we collect the following on the developer's behalf and give it to them:

• Feedback: your message; whether it's a bug or an idea; a screenshot of the game screen if you attach one and the developer allows it; and your device model, operating system version, game version and language. For web games, the device model is your browser's user-agent string. If the BoardFlight account that paired a Board is on a game's team, or was given the game by its team, feedback sent from that game on that Board can carry the account's name, shown to the team as coming from that account's Board. The game itself can send such feedback without anyone typing. Every report that carries your name is listed on your Account page, where you can take your name off it or turn this off for all your Boards. The person typing can also send anonymously. It never carries a Board player's name. If you send feedback from your phone by scanning a game's code, we receive your message and your phone's language setting and, if you're signed in and don't choose to send it anonymously, your account.
• Play analytics: a random identifier created for that game on your Board, the device model, Android version, language and time-zone offset, and when each play session starts and ends. We don't record what happens in the game, your input or what's on the screen. Each time a game reports that it has started, we also count one play of that game for the library, and keep a shortened, hashed form of the IP address the report came from. We use it only so that starts from the same address within 30 minutes count as one play. These are kept as library plays (see section 5).
• Game events: With game events on, this channel's builds send BoardFlight the events the game's own code reports (what happened, its numbers and identifiers) under a random install id, with each Board profile replaced by a one-way code that differs in every game. BoardFlight never receives player names, Board profile ids, free text, screen contents or input. The game's developer chooses what their game reports and is not allowed to include personal information.
• Achievements and leaderboards: With achievements or leaderboards on, this channel's builds send BoardFlight the achievements the game awards and the scores it posts, under a random install id, with each Board profile replaced by a one-way code that differs in every game. BoardFlight never receives player names or Board profile ids. A player's scores appear under a generated name unless the player links the game to their own BoardFlight account; a public link shows their username and their profile to anyone.

1.4 Information collected automatically

• Product usage: the pages and panels you visit, download clicks, and actions such as creating a game, uploading a build or starting a playground. We use PostHog to understand which parts of BoardFlight people use and where they get stuck. These events carry random browser identifiers or internal account and resource IDs. We send page templates rather than private links, and broad referral categories rather than referring URLs. We don't send names, email addresses, passwords, invitation codes, project content, AI conversations or feedback text, and we don't record your screen or automatically capture everything you click or type.
• Library pages on the web: when you open a game's library page, we count a view of that game for its developer's statistics, together with your account if you're signed in. With each view we also keep a shortened, hashed form of your IP address, used only so that views from the same address within 10 minutes count as one. These are kept as library views (see section 5).
• Getting-started steps: if you open the getting-started steps in the library, we record which steps you saw, skipped or finished, how long they took, and whether you created or signed in to an account there. These events come with a random identifier that is created in your browser when you open the steps, the version of the website, and your account once you're signed in. If you've turned off product analytics in the browser or app you opened them in, or your browser sends Do Not Track or Global Privacy Control, we record none of this and create no identifier.
• Starting a game from the BoardFlight app: when you press Play in the BoardFlight app on your computer and your Board accepts it, we record which game, which of your Boards, and when, with your account. We use this to help when something goes wrong with your account. It isn't counted as a play, and it isn't connected to what the game itself reports. It's kept and switched off the same way as the getting-started events.
• Requests: like any online service, our servers receive your IP address and basic information about your browser or app with each request. We use IP addresses briefly to prevent abuse, and our hosting provider keeps request logs for a short time.
• Errors: when a page of our website or the BoardFlight app fails, it sends us the error message, which page it was, with any code or name in its address removed, and your browser's name, so we can fix it. It doesn't say who you are. We hold it for up to two days to send it to ourselves in a daily email, and keep no other record of it.
• Sign-in sessions: we keep a record of each signed-in session with a label, such as your browser's name or, for the command-line tool and the BoardFlight app, your computer's name, and when it was last used. We also record which days you used BoardFlight, and whether that was in a browser, in the BoardFlight app, or with the command-line tool or an editor plugin. We use this to count how many people use BoardFlight each day, week and month.
• Cookies and browser storage: BoardFlight sets three cookies that are needed for signing in. One keeps you signed in; scripts on our pages cannot read it. One only marks this browser as signed in, and holds nothing about you. One is short-lived, for security while you sign in with Google or Discord. Product analytics uses three more, shared by boardflight.app and create.boardflight.app so that a visit to both counts once: a random visitor identifier, a random usage-session identifier that lapses after 30 minutes without use, and one that remembers whether you turned product analytics off. Turning product analytics off deletes the two identifiers, and while it is off, or your browser sends Do Not Track or Global Privacy Control, they aren't set. None of these cookies holds your name, email address or account, and none is used for advertising. A short-lived access key, your email address, preferences and drafts are kept in your browser's local storage, and so are the product analytics identifiers and choice in a browser that doesn't accept those cookies. The getting-started steps keep their random identifier there too, along with where you left off. If you connect a ChatGPT account to the playground, its credential is kept in your browser and copied into your playground sandbox while the sandbox runs. We don't store it on our servers. We use no advertising cookies.
• Activity records: we record significant actions, such as invitations, access grants, publishing and signing-key changes, along with who took them.

1.5 Information from other people

A team member may give us your email address to invite you to a team. A developer may give us your email address to grant you access to a game. Google or Discord give us the information described above if you use them to sign in.

2. How we use it

• To provide the Service: accounts and teams, distributing and installing games, the library, the playground, the assistant, and feedback and analytics for developers.
• To show developers activity and feedback for their own games.
• To send service emails, such as address verification, password resets, invitations, library review decisions, feedback players send to your games, and important changes.
• To email you news about new games on BoardFlight, only if you ask for it (when you sign up or in your account settings). It is off unless you turn it on, and every such email includes a way to unsubscribe. We send no other marketing email.
• To keep the Service safe, prevent abuse, review games for the library, and enforce our Terms.
• To understand and improve the Service, for example to find where people get stuck, or to rank games in the library by popularity.
• To comply with the law and protect our rights and the rights of others.

We don't use your personal information for advertising, and we don't use it to train AI models.

3. Who can see it

3.1 Other BoardFlight users

• Anyone in BoardFlight who sees you listed, such as the developers of games you test, sees only your username, unless you share a team with them.
• Members of your teams see your username, your real name if you gave one, and your email address.
• Developers of games you have access to see, for their own games: your username and, where the BoardFlight app on your computer reports it (or the former app for Board reported it), when you installed the game and whether the install worked. If they turned on analytics, they also see whether the game is still installed and when it was played. They never see your Board's name or your computer's name.
• Developers see the game events their game reports, with each Board profile shown only as a one-way code. Game events aren't linked to your account.
• Developers see the feedback you send to their game, and we email it to the people on the team that made it who choose to receive it. Feedback you send from your phone while signed in shows them your username, or your name if you're on their team, unless you choose to send it anonymously. If you're on a game's team or were given the game by its team, feedback sent from it on a Board you paired shows them your username (your name, if you're on their team) as your Board's, unless it's sent anonymously or you've turned this off. Other feedback isn't linked to your account.
• Library listings, including the name of the team that made each game, are public.
• Your conversations with the assistant are yours. Your team-mates can't see them, and we don't read them: our own tools show how much the assistant is used and what it costs, never what anyone asked.

3.2 Service providers

These companies process information for us, only to provide their services to us:

• Cloudflare: hosting, databases, file storage and request logs.
• PostHog: website and product usage analytics. Like any service your browser connects to, it receives your IP address with the request; we disable location enrichment and don't include your IP address in event properties.
• E2B: the cloud sandboxes that run the playground and that add the feedback layer to builds.
• Cheaper Inference (Keak AI, Inc.): the AI model behind the assistant on the creators' dashboard. With each question it receives the conversation so far; your username, the team the conversation is about and your other teams, with your role in each; the page you asked from; the help pages the assistant read; and what it read of your team's games to answer, such as builds, play numbers and feedback, with the names and details the dashboard shows you beside them. In place of your account it receives a code made from it, so it can tell people's requests apart. We send every request with zero data retention, so it goes only to AI model providers that don't keep it or train on it. Cheaper Inference says it doesn't store or train on what requests contain, and keeps information about each request for 45 days.
• Stripe: payments for printed figures. On its checkout page it receives your email address and collects your card details and shipping address, and it works out the sales tax. It handles them under its own privacy policy as well as ours.
• Resend: sending email.
• Vask: real-time notifications.
• Apple Push Notification service and Firebase Cloud Messaging (Google): delivering notifications to the BoardFlight app on iPhone and Android. Each receives your phone's notification address and the notification's text, which names the game and your Board.
• Google and Discord: sign-in, if you choose them.

3.3 Services you connect

When you use OpenAI's Codex or Anthropic's Claude Code in the playground, or connect other tools to it, what you send those tools goes to their providers under your own account with them. When your team connects an AI provider such as OpenRouter or Cheaper Inference, what you send the playground's assistant goes from the sandbox to that provider under your team's account, not through our servers. We use your team's key only to check that it works, to give playground sessions their keys and, with OpenRouter, to read how much each session spent. Their privacy policies apply.

3.4 Board's maker

We don't send your information to Board's maker. Installing a game, whether through your Board's own page or with the BoardFlight app, happens on your home network, between your computer and your Board. What Board's own software collects is governed by Board's privacy policy.

3.5 Legal reasons and business changes

We may disclose information when we believe the law requires it, for example to answer a subpoena; to enforce our Terms; or to protect the safety, rights or property of our users, the public or us. If we are involved in a merger, acquisition, financing, reorganization or sale of assets, information may be transferred as part of it, and it will remain subject to the commitments in this policy.

We don't sell personal information, and we don't share it for cross-context behavioral advertising, as US state privacy laws define those terms. We have not done either in the past 12 months.

4. Children

• BoardFlight accounts are for people 13 and older, and people under 18 need a parent's or guardian's agreement. We don't knowingly collect personal information from children under 13.
• Board is a family device. A child may play games that a parent or guardian has installed on a Board. Information about that play is collected as described above.
• Feedback sent from games is linked to an account only as described in 1.3, and then to the account that paired the Board, usually a parent's, never to a Board player; and we ask players not to include personal information. Our Terms don't allow developers to turn on in-game feedback, analytics, game events, achievements or leaderboards in games directed to children under 13.
• If you believe we have collected personal information from a child under 13, contact us at legal@boardaux.com and we will delete it.

5. How long we keep it

Your account, profile and team memberships

Until you ask us to delete your account.

Builds

90 days after upload by default (a game's developer can change this), except that each channel keeps its 10 most recent builds.

Install activity

180 days.

Play sessions and install/uninstall records

180 days. After that, only daily totals are kept.

Game events

90 days. After that, only daily totals and each player code's progress through the game are kept, until the game's developer deletes them or the game leaves BoardFlight.

Achievements and leaderboards

What a game sent, 90 days. Which player codes have played a game, as long as the game is on BoardFlight.

Library views and plays

90 days. After that, only totals are kept.

Feedback screenshots

180 days.

Feedback messages and their device details

Until the game's developer deletes them.

Setup events, from the getting-started steps and from the former BoardFlight app for Board, and games started from the BoardFlight app

400 days.

Which days you used BoardFlight, and which days the BoardFlight app reached each of your Boards

180 days.

Your Boards, and which of your games are on each

Until you remove the Board or delete your account.

Installs and updates you asked for through the BoardFlight app or the website

Until you remove the Board or delete your account.

Computers running the BoardFlight app

Until you sign out of the app on that computer.

Phones that get notifications from the BoardFlight app

Until you sign out of the app on that phone, or 270 days after the app last registered it.

Website and product usage events

According to PostHog’s retention settings. Its free service retains events for one year.

Records of playground sessions (who used one, and when)

180 days after the session ends.

Playground projects, versions, AI chat history and AI usage records

As long as the game is on BoardFlight, unless deleted sooner.

Computers linked to a playground

30 days after they were last used.

Conversations with the assistant

30 days after each began, unless you delete one sooner.

Records of questions to the assistant, which hold no text

400 days.

IP addresses used to limit abuse

Up to 24 hours.

Request logs kept by our hosting provider

A short period set by that provider.

Security and audit records

As long as needed for security and legal purposes.

Orders of printed figures

As long as tax and accounting law requires us to keep records of sales, even if you delete your account, when the order is no longer linked to you.

When you delete your account, we delete your personal information or remove what identifies you within 45 days. There are four exceptions:

• Content you made for a team, such as builds and library listings, stays with that team, but no longer shows your name.
• Feedback you sent to games, or that carries your name from your Board, stays with their developers, but no longer shows your name.
• We keep records we need for security, legal obligations or disputes.
• Backups are overwritten on their normal schedule.

6. Your choices and rights

Product analytics is off in this browser. Turn on product analytics

• Product analytics: the control above, which is also in your account settings, turns off future website usage events, getting-started events, games started from the app, and product events for API requests made by this browser, on boardflight.app and create.boardflight.app alike. In the BoardFlight app on your computer, the same switch is under This computer on My Boards, and covers the app's window. It doesn't affect operational records, game analytics, games the app installs in the background, or requests from other devices and tools.
• Profile: change your username and real name in your account settings. To change your email address, contact us.
• Email about new games: off unless you turn it on. Turn it off at any time in your account settings, or with the unsubscribe link in any such email.
• Feedback with your name: on your Account page, turn off naming feedback sent from your Boards, see every report that carries your name, and take your name off any of them. An email a team was already sent about a report can't be recalled.
• Assistant conversations: delete any of them from Your conversations in the assistant. It is deleted at once. The record of each question, which holds no text, is kept for the time in section 5.
• Delete your account: email legal@boardaux.com from the address on your account.
• Developers can delete feedback reports, turn off feedback screenshots, and turn the feedback layer off for any channel.
• Your state's privacy rights. Depending on where you live, you may have the right to know what personal information we hold about you and to get a copy of it, and to have it corrected or deleted. You may also have the right to opt out of its sale, of targeted advertising and of certain profiling. We do none of those three. We honor requests to access, correct and delete information from everyone in the United States, whatever state they live in.
• Making a request: email legal@boardaux.com. To verify your identity, we will ask you to confirm that you control your account's email address. An authorized agent can make a request for you if they show us your written permission. We respond within 45 days, and we won't treat you differently for using your rights. If we decline your request, you can appeal by replying with “Appeal” in the subject line. If you're still unsatisfied after an appeal, you can contact your state's attorney general.
• Do Not Track and Global Privacy Control: we turn off product analytics and getting-started events when your browser sends either signal. We don't track you across other websites or sell or share your information for advertising.
• California “Shine the Light”: we don't share personal information with other companies for their own direct marketing.
• Service emails, such as password resets, can't be turned off while you have an account.

7. Security

Connections to BoardFlight are encrypted. Passwords are stored as salted hashes. Sign-in, API and invitation tokens and redeem codes are stored only as hashes. Signing-key passwords and API keys that teams add are encrypted. Access to production data is limited.

No system is perfectly secure. If a breach affects your information, we will notify you as the law requires. Keep your password safe, and tell us at legal@boardaux.com if you think your account has been compromised.

8. Where we process it

We and our service providers store and process information in the United States and in other countries where those providers operate. The Service is intended for people in the United States.

9. Changes to this policy

We will post any update here with a new effective date. If a change is material, we will tell you by email or in the Service before it takes effect.

10. Contact us

Questions and requests about privacy go to Zeya AI Inc. at legal@boardaux.com.