ShapeShift Studio / Family Feud
Privacy Policy
Operator and scope
Tak Lo, operating as ShapeShift Studio is the contact responsible for this project's privacy questions. This notice describes Family Feud. Contact shapeshiftstudio2026@gmail.com. For workplace/client records, the organization directing their use may have its own legal responsibilities and retention rules. We will coordinate requests with the appropriate record owner rather than treating development of the software as ownership of its records.
Information handled
Team/player names, answers, scores, game options and room/connection information where network play is used.
Information comes from what you enter/select, authorized source records and the technical operation of the features you use. Do not supply private information that is unnecessary for the task.
Where it goes and who can see it
Browser storage can retain setup/scoreboard information. Browser messaging and the configured transport relay synchronize the game screens. Hosts, contestants and audience screens can see displayed team information.
Why it is processed
The information above is used to run a host/contestant game and shared scoreboard, show and save the results of requested actions, coordinate authorized sharing, protect access and investigate service/support problems. A support email is used to handle your request. This notice does not authorize unrelated advertising, marketing, profiling, data sales or model training. Any proposed new optional use requires its own disclosure and any consent required by law.
Providers and cross-border processing
The page host and configured game relay process network requests and game messages.
Network providers process requests under their own terms and settings and may handle data outside your province or Canada, where local laws can permit government access. This notice does not promise Canadian-only storage, zero provider logging or a particular vendor retention/training setting that has not been verified. Opening a third-party link or sending a report to another service brings that destination's practices into play.
Cookies, device storage and permissions
See Storage & permissions for the mechanisms relevant to this project. Browser caches, saved sessions and local files can outlast the current session. Optional device permissions can be managed in the browser/operating system. Reading this notice or continuing to use an essential feature is not blanket consent to unrelated optional tracking.
Retention, deletion and export
Saved records remain for the feature, history or operational purpose that needs them, until removed through available controls or an authorized request, subject to applicable legal and recordkeeping needs. A single automatic deletion period for every record, backup and provider log has not been established. Do not assume records expire when you stop using the app.
To request access, correction, an available export, deletion or withdrawal of consent where applicable, email us with the app name and enough information to locate your records. Do not send passwords, PINs, access links or sensitive attachments in the first message. We may need proportionate identity/authority verification and will explain relevant legal, security or technical limits. A request is assessed under applicable law; this page does not promise instant deletion or a fixed processing time that has not been established.
Local-only records are controlled by the device user and are not remotely recoverable by us. Clearing them can cause permanent loss. Clearing local data does not erase server records, email attachments, recipients' downloads or backups. Deleted server records may remain in restricted backups or provider logs until their applicable retention expires; copies held by other record owners need separate requests.
Children and sensitive records
A responsible adult should guide children's information choices. Before collecting information from a child where guardian consent is required, the responsible operator/organizer must arrange that consent. Do not use a shared gallery, chat, leaderboard or export to disclose a child's identity without appropriate authority. A notice alone is not a verified parental-consent process.
Employment assessments, signatures, school records, private messages, calendar details and identifiable photos can be sensitive. Only submit or share them with appropriate authority and through the feature intended for that purpose.
Security and concerns
No system can guarantee perfect security or recovery. Protect your device and credentials and avoid sharing invitations publicly. Report a suspected privacy/security problem through Contact & reporting. We will assess applicable duties and coordinate incident response with the responsible organization and providers.
Updates
This is policy version 1.0, issued October 31, 2026. Material changes need appropriate notice and any new consent required by law before a new data use begins. The current copy stays accessible through the project's legal/help links.