Security & Trust

In Good Company is a light culture game, and it is built to hold as little sensitive information as possible. This page is a plain summary of how we handle data, for the people who review that on your behalf.

What we collect and why

Only what the game needs: a first name and last initial, the answers a participant chooses to share (text, numbers, this-or-that, and an optional photo), a picked illustrated avatar, and live-play guesses. Our hosting providers also log basic technical data such as IP address and request times to run and protect the service. We do not request emails, phone numbers, or special-category information to play. Full detail is in our Privacy Policy.

Where data lives

Game data is stored and served by established providers in the United States. Our sub-processors are:

How it is protected

• In transit: all traffic runs over HTTPS/TLS.
• At rest: data is encrypted at rest by our database and hosting providers.
• Access control: game tables use row-level security and are reachable by apps only through a single controlled server interface. Each game is gated by a game code, and every host holds a private token for their own game.
• Least privilege of data: because there are no accounts, emails, or passwords, there is very little to expose in the first place.
• Photos: shrunk on the participant's own device before upload, reviewed by the host before they are shown, and never used for facial recognition or any biometric identifier.
• AI isolation: only counts, rates, and a score are sent to the AI provider. Personal answers, names, and photos are not.
• Confidentiality: people with access are bound by confidentiality obligations.

Our infrastructure providers (Supabase and Vercel) maintain their own independent security programs and audits. We are happy to share their current attestations on request as part of a review.

Data lifecycle

A game's data exists for as long as the game does. A recap can be set to expire, for example after a week, and can be protected with a password. A host can delete a game at any time, which permanently removes that game's participants, answers, guesses, and photos. On the end of a customer relationship, we delete or return data as agreed.

Privacy and compliance

We support the rights and obligations under the GDPR, UK GDPR, and CCPA/CPRA. When we run a game for an organization, we act as a processor under that organization's instructions, and we make a Data Processing Addendum available for enterprise agreements. See our Privacy Policy and Terms of Service.

Reporting a concern

If you believe you have found a security issue, please contact us at security@berryapplabs.com and give us a reasonable chance to address it before public disclosure. For privacy requests, contact privacy@berryapplabs.com.