Privacy Policy

Fachelli Family Administration operates the community publicly through Anthony ‘Tony’ Bambino.

• Privacy and data requests may be emailed to vitogamingmedia@gmail.com or submitted through the Contact Desk.
• The public site does not publish the owner’s legal name, residential address, telephone number, registrar contact, ChatGPT username, billing identity, or private account identifiers.
• Domain registration uses accurate private contact information with WHOIS privacy; those registrar records are not copied into this site.

This policy covers information processed through the public site and authenticated member tools.

• Public forms may collect a name or creator name, email, Discord handle, preferred contact method, character and server details, crew and portal interests, availability, experience, creative contributions, and the message or proposal you submit.
• Application review may record Commission notes, status, approved crew, fictional Family rank, local crew role, server assignment, and separate member-portal permission.
• Member tools may process authenticated ChatGPT email and display name, character name, Family position, crew placement, XP entries, awards, biography, profile-image URL, public-profile choice, community permission, account status, policy acceptance, chat messages, moderation events, bulletins, Sit-Down records, content records, hierarchy changes, and activity logs.
• Ordinary technical information may be processed by hosting, authentication, security, and payment providers as necessary to deliver and protect their services.
• Do not submit passwords, payment-card details, government identifiers, medical records, precise private addresses, or other sensitive information.

• Operate the public archive, membership workflow, protected portal, rank-controlled rooms, content publishing, inquiries, moderation, and security.
• Review fit, assign fictional placement separately from real website permission, route questions, communicate through the email or Discord method an applicant supplied, maintain canon, attribute creators, investigate abuse, and enforce policies.
• An approval may create or update a member-access record for the application email; access begins only through the platform's authenticated sign-in process.
• Comply with valid legal obligations, protect rights and safety, prevent fraud, and maintain essential administrative records.
• The Family does not sell application, inquiry, chat, or member personal information.

• The owner-only private office may send a minimized set of authorized operational records to its configured drafting service to prepare counsel and reviewable actions. Eligible context includes the Code digest, crew charters, fictional standing, crew reports, economic summaries, Sit-Down status and precedent, archive records, Commission meeting records, and approved activity summaries.
• Application contact details, account email addresses, Discord handles, direct messages, raw Family chat, private moderation evidence, payment information, and government identifiers are excluded from that context by design.
• The private request is configured not to store the response for provider state, while the Family website may retain the owner conversation, approved directive, approver, and resulting record for accountability and continuity.
• Discord is not silently or comprehensively monitored. Only event summaries intentionally sent through the configured official connection from authorized channels may enter the site record; private and direct messages are not accepted by that connection.
• Do not submit private messages, confidential evidence, sensitive personal data, or another person’s information to the private office. Human administrators remain responsible for verification, access, minimization, correction, retention, and deletion decisions.

• Private Family chat messages are screened before publication for limited policy-risk patterns. A blocked message body is not intentionally published; a minimal moderation event may record the account, room, time, and risk category for security and human review.
• Visible chat messages remain available to authorized room members until removed or cleared under policy. Members may report a visible message; the report records the reporter, room, message reference, time, and selected reason for authorized human review.
• Automated screening is assistive and does not make final disciplinary decisions. Reporting is not anonymous to authorized administrators and does not by itself establish a violation.
• Members may choose whether an approved profile appears publicly. Public profile fields are limited to character/display name, fictional position, crew, local office, server assignment, XP total, biography, profile image, and public awards. Email, private activity, and real community permission are not published.

• OpenAI/ChatGPT Sites and its infrastructure providers process information needed to host the site, authenticate users, maintain security, and operate the configured database under their own terms.
• The owner-only office sends the owner’s prompt and a minimized operational context to the configured OpenAI API project. OpenAI project credentials are encrypted at rest by the site and are never intentionally exposed to members.
• Discord receives limited application or inquiry notifications and may send intentionally configured public-channel event summaries; YouTube, games, host servers, and other linked services process activity under their own policies when you choose to use them.
• Supporter payments are disabled. The site does not presently collect payment-card information. A payment processor may not be activated until this policy, the operator identity, refund terms, and processor disclosures are updated.
• Information may be disclosed when reasonably necessary to comply with law, protect safety or rights, investigate fraud, or respond to valid legal process.

• Collect only what is reasonably needed and limit access according to actual community permissions.
• Applications and inquiries should be reviewed at least annually and deleted or de-identified when they are no longer needed for placement, communication, disputes, safety, or legal obligations. Pending and closed records must not be kept indefinitely merely because storage is available.
• Active member records remain while membership is active; after departure, direct identifiers should be removed or minimized when no longer needed for security, dispute history, licensed publication, or legal obligations.
• Chat bodies should be reviewed on a regular schedule. Clearing a chat removes active message bodies while a minimal moderation event may remain for accountability.
• Published fictional canon, properly licensed content, creator credits, de-identified records, and necessary audit history may remain even when account information is removed.
• These are operating limits, not a promise of instantaneous or automatic deletion. A documented owner review and deletion log must be maintained before public launch.

• The site uses platform authentication for protected routes, server-side permission checks for restricted actions, same-origin checks for state-changing browser requests, restricted Discord ingestion, encrypted API credentials, and attributable administrative logs.
• The operator must maintain reasonable administrative, technical, and physical safeguards appropriate to the size of the project and the sensitivity of the information, including named security responsibility, service-provider review, access review, incident response, and secure disposal.
• No online service can promise absolute security. Members should use secure accounts, avoid sensitive submissions, and report suspected unauthorized access promptly.
• If New York private information is accessed or acquired without valid authorization, the operator will evaluate and provide notices required by New York General Business Law §§ 899-aa and 899-bb and other applicable breach-notification laws without unreasonable delay.
• The site intentionally avoids collecting government identifiers, financial credentials, medical records, and precise private addresses. Do not submit them.

• Use the Contact Desk to request access, correction, deletion, or clarification regarding personal information associated with you.
• You may leave the community and request account closure without fictional or real retaliation.
• Some information may be retained when required for security, fraud prevention, dispute history, legal obligations, or licensed publication.
• You may decline optional forms or Discord participation, but certain information is necessary to operate membership and protected access.

• Authentication, hosting, and security providers may use cookies or similar technologies necessary to sign users in, maintain sessions, prevent abuse, and deliver the service.
• The current site should not activate non-essential advertising or behavioral-tracking tools without updating this policy and providing any notice or consent required by applicable law.
• External YouTube, Discord, payment, and other links are governed by those providers once opened.

• The member community is limited to adults age 18 or older, is not directed to children, and does not knowingly permit minors to register for member tools.
• If the operator learns that a minor submitted personal information, access should be blocked and the information reviewed for prompt deletion except where preservation is legally required for safety or reporting.
• Material policy changes should be posted with a new effective date and communicated through an appropriate official channel.
• Privacy questions and rights requests should be submitted through the Contact Desk under the Privacy topic.