Privacy

1243116 B.C. Ltd., Parksville, British Columbia, Canada operates KITCHEN COURT. This notice covers the app and kitchencourt.coachcommandcenter.com. Our privacy contact is available through Feedback & help.

On your KITCHEN COURT and with your providers

KITCHEN COURT maintains local household and owner-device identities, settings, activity and conversation records, and creations needed to operate your room. Connected credentials may be held in local configuration or macOS Keychain, depending on the integration. They are used for services you connect and are not automatically attached to feedback.

KITCHEN COURT can run your installed AI command-line tools with the capabilities authorized for a task. Inputs, context and content sent to an AI or other connected provider are processed under that provider’s account and policies. A local app does not mean AI requests stay on your Mac. Review permissions and avoid supplying content you do not want a provider to process.

Enrollment, invitations and updates

Enrollment uses a device signing identity and household allocation to provide a KITCHEN COURT address and authenticate services. Infrastructure processes allocation, invitation, update and certificate/DNS challenge information. Public hostnames, DNS records and certificate information are not secret; the device’s private signing key is separate.

Invitations process recipient emails and delivery, eligibility, expiry and redemption records. The website waitlist, offered while access is by invitation, stores your submitted email, AI preference, submission time and a hashed network address to limit abuse. Invitation-related messages may be sent for these purposes. If you are not on a Mac and ask on the install page to hear when KITCHEN COURT runs on your computer, we store your email, which computer you chose, the submission time and the same hashed network address, and send you one confirmation now and one message when KITCHEN COURT runs on that computer.

When kitchencourt.coachcommandcenter.com offers setup codes, getting one uses Cloudflare Turnstile, an automated human check that runs in your browser; Cloudflare processes information from your browser and connection to perform it, and tells us whether it passed. To limit abuse, we count requests against a hashed form of your network address, per minute and per day, together with a random identifier your browser sends so that a retry returns the same code. We store the issued code only in hashed form, with its expiry and whether it was used; it expires after one hour. Expired codes and request counts are deleted. When a code puts a household online, the resulting enrollment records are kept like any other household’s. We do not ask for an email or an account to issue a code.

Sharing with others

Public publishing sends selected content and display or creator metadata to hosted infrastructure so others can see, play or download it. Public content can be copied. Private remote play is different from public publication, but direct peer connections can reveal network addresses to the other peer. Connection and signaling infrastructure process information needed to connect devices. Share access links only with intended participants.

Private feedback

Website and in-app feedback explicitly submit a category, message and optional reply email. The website also has an anti-spam field. We store the submitted report, a reference, time and hashed network address. Reports are private and reviewed by the team, which may use service providers and AI-assisted support tools to triage and troubleshoot them. Privacy and legal requests are escalated to the operator; AI tools do not independently decide your legal rights. We do not automatically attach logs, screenshots, credentials or app context. Please leave passwords, keys and private links out of your message. A reply email is for follow-up, not a promise of automatic mail.

When a KITCHEN COURT first starts

A new KITCHEN COURT sends one message to kitchencourt.coachcommandcenter.com about ninety seconds after it first starts, to say that it came up. It is the only report the app sends without being switched on, and it is here because a box that fails to start cannot press a switch to tell anyone that it failed. It carries five values and nothing else: the release version, whether the box was installed from the .pkg or is running from a source checkout, the macOS major version (for example “26”), the processor architecture, and how many seconds the app had been running when it sent. There is no household, device, account, serial, name, address or typed-in value in it. The door refuses a message carrying any other field outright rather than ignoring it, and the table it is written into has no column to hold one. We keep your network address only as a salted hash, so that one network cannot file more than ten of these a day, and we delete the record after ninety days. A KITCHEN COURT sends this once per install and, once it has been received, never sends it again. To switch it off, set "firstBootPing": false in your KITCHEN COURT’s household.json; with the switch off nothing is sent and nothing is recorded.

Optional diagnostics and website analytics

App telemetry is opt-in, and it is separate from the first-start message above. When enabled, it sends a bounded set of product event counts and a scrubbed crash diagnostic associated with the house identity. Turning it off stops recording those telemetry events. It does not stop network traffic needed for enrollment, updates or features you choose. Scrubbing reduces sensitive content; it is not a guarantee of anonymity.

The kitchencourt.coachcommandcenter.com website and the games and players it serves also send short diagnostic reports: when something breaks (for example a shared game that does not start, a phone that cannot join, or a song or film that stalls), and a few plain counts that put those faults in context (a new game version loading, a search result pressed, an account sign-in). A report holds only a kind, the part of the site, an outcome, a coded reason, a timing, a game build’s content hash, a screen-size range, whether the screen is touch, and a browser family. It never holds words you typed, what you searched for, a page address, a cookie or who you are. We keep your network address only as a salted hash, to stop one page flooding the service, and delete reports after thirty days. “Don’t send diagnostics” in the site’s footer turns them off in that browser.

We use Cloudflare Web Analytics on the public home, about, install, games, music, video, pricing and hardware pages to understand page use and performance. The configuration excludes EU visitors. It is cookie-less and does not collect URL query strings. We do not enable this beacon on household controllers, shared-game pages or the feedback form.

Cloudflare and other infrastructure providers process request and network information needed to deliver and protect hosted services. Service providers may process information outside Canada, subject to the laws where they operate. AI and connected-service providers have their own policies. We share information as needed for the features you request, with infrastructure providers operating them, or where legally required; this notice is not consent to unrelated purposes.

Safeguards include restricted authorized access and encrypted network transport where implemented. No system or transmission can be guaranteed completely secure.

Retention and your choices

We retain information as needed for the purposes described here, legitimate operational needs and legal obligations. Retention differs by record: for example, active household identity and publication records serve different needs from an expired invitation or a resolved report. When the stated purposes and lawful retention needs no longer require information, we delete or de-identify it. We do not promise one automatic deletion deadline for every record.

You can manage local information on your Mac, change integration and telemetry settings and use supported sharing controls. Local removal and hosted removal are separate. Deletion from backups may take time, and we cannot delete copies other people downloaded or recorded.

If we restrict or remove hosted content, we keep a record of that decision — which page, when, who made it and the written reason — and we keep it after the content is gone, for as long as we need it to show the decision was made properly and to handle a review, a rights claim or a legal request. Asking for the content to be removed does not remove that record.

Access, correction and privacy requests

Use Feedback & help to reach our privacy contact, request access or correction, ask for deletion, withdraw consent where applicable, or raise a concern. Keep the private reference and include an optional reply email for follow-up. We may need to verify your identity or ownership before disclosing or changing information. Do not send identity documents or secrets in the initial form. We will handle requests under applicable law, including any required time limits and exceptions. You may also raise a concern with the applicable privacy regulator.

We will notify you of material changes to this notice or a transfer of KITCHEN COURT to another operator and obtain consent where required, including for materially new purposes. Using the app is not blanket consent to optional telemetry or unrelated data use.