Church of Meta Privacy Policy

Website

Privacy Notice

What this website collects

The Shared Soliloquy form collects the reflection, name or handle, email address, and consent choices you submit. The Systems Literacy Hub form collects your name, email address, selected interest and subject, optional organization, message, and consent choices. Each form also records the version date of this notice. Nothing submitted through either form is published automatically.

The forms also send a subject line, a submission category, the notice-version value, and an anti-spam field. Only selected optional consent boxes are submitted. There is no file-upload field or automatic publication.

How submissions are used

Submitted information may be used to review and respond to your message, administer public programs, protect the community from abuse, and maintain an internal record of the request. A Soliloquy reflection or attribution requires editorial review and separate confirmation before publication. An optional request for program updates is recorded separately from permission to answer a specific inquiry.

Technical information and service providers

The web host may process ordinary request information such as an IP address, browser details, requested pages, and timestamps to deliver and protect the site. When you submit a form, Formspree receives the form contents and technical submission information used to deliver and screen the message. The browser continues to Formspree for any verification and the submission result. Notification and reply emails also create records in the receiving mailbox. The public page does not load third-party fonts, animation libraries, analytics, or advertising trackers.

External platforms

Links to Discord, Reddit, Medium, Ko-fi, Cash App, and Venmo lead to services with their own privacy practices. Those services receive information only when you choose to follow a link or use their service.

The description above concerns links from this website. Processing through DFV Bot is described separately in the DFV Bot section below and may occur within Discord without a visit to this website.

Retention and young visitors

Submissions should be deleted when they are no longer reasonably needed to respond, document consent, protect the community, or meet a legal or recordkeeping obligation. These general-purpose forms are not directed to children under 13. A parent or guardian should contact Church of Meta on behalf of a younger child.

Your choices

Do not submit information you do not want reviewed. To ask about a submission, correction, or deletion, email hello@churchofmeta.org. Requests may be limited by legal, safety, or recordkeeping obligations.

Security and updates

No internet transmission or storage system is guaranteed to be completely secure. This notice may change. The effective date below identifies this version.

DFV Bot

Operator: Church of Meta
Application: DFV Bot, Discord application ID 1340426261364740166
Privacy, support, and moderation review: hello@churchofmeta.org
Related terms: DFV Bot Terms

Scope and providers

DFV Bot supports the DeepFuckingValue Discord community. Church of Meta selects the community configuration and controls the community records described here. DFV Bot is the community’s MEE6 Custom Bot, also called Bot Personalizer; Discord supplies the platform. Provider-controlled records are separate from community-held copies. See the MEE6 privacy policy and Discord privacy policy.

Functions and information

The configured community functions include onboarding and roles, custom and slash commands, activity levels and rank cards, moderation and event logging, invite tracking, optional birthdays, and a virtual economy. Features and their visibility depend on the server configuration and channel permissions. Those functions may use the following information within the channels and permissions available to the bot:

• Discord user IDs, names or display names, server and channel identifiers, roles, and membership events for identification, onboarding, and community workflows.
• Command inputs, message identifiers, available message content, timestamps, relevant edit or deletion events, and moderation reasons or actions for configured commands and moderation. Where an edit log captures both versions, a record can include earlier and revised message text.
• Member identifiers and activity, XP, levels, rank, achievement and role-reward information for community participation features. A rank card can display current member-status information provided through Discord.
• Invite identifiers, inviter relationships, join/leave events and invite counts for invite statistics and leaderboards.
• A birthday supplied through birthday commands, including a year if supplied, for birthday reminders, age displays and related commands. Birthday outputs may be visible in the configured community channel. Members can use the available birthday-removal command or contact us.
• User identifiers, virtual coin balances, item inventories, game actions and daily-claim or streak information for the configured virtual economy.
• Voice-channel join and leave events for configured event logs. These event records concern channel participation; a join/leave log is not an audio recording.

Some processing can occur automatically in channels available to the bot without an individual command or website visit. A bot permission does not mean every available field is retained. Joining the server, using a command, or reading this page is not blanket consent to unrelated processing.

Community logs and visibility

The designated moderation and member-event log channels are mee6-log and join-log. The community's designated access is DFV Bot and two authorized administrators. Discord users with Administrator privileges may have platform-level access despite private-channel restrictions.

Command responses, onboarding messages, or rank-card outputs may be visible to members who can access the channel where they appear. Private log access is distinct from that output visibility. Deleting or editing an original message does not necessarily delete a separate log copy; logs can also be incomplete when the bot did not receive an event.

Church of Meta does not run a separate bot logging or export system outside Discord. This does not describe MEE6’s or Discord’s own storage. A support or privacy email creates a separate mailbox record; copies supplied for an incident or request are handled for that purpose.

Use and disclosure

Community-controlled records are used for the described bot functions, community safety, incident review, support, and handling privacy or moderation-review requests. Access is limited to the community roles described above and the service providers supporting these functions. Disclosures remain subject to applicable law and Discord's developer requirements.

Retention and deletion

Community logs in mee6-log and join-log do not expire automatically. Two designated community administrators remove records manually. We retain community-controlled API data only while it remains necessary for the bot’s disclosed functions. We promptly delete the relevant API data when it is no longer needed, when the applicable user or Discord requests deletion, when we stop operating the bot, or when deletion is otherwise required, except where applicable law requires retention. Board consultation may support governance decisions but does not delay required deletion.

MEE6 and Discord control records on their own systems. Removing a community log or original message does not guarantee erasure of provider-held copies or backups. Provider retention is governed by their own policies and processes; no fixed provider retention period is promised here. No internet transmission or storage system is guaranteed to be completely secure.

Requests and human review

Email hello@churchofmeta.org for access, correction, deletion, support, or human review of a bot-related moderation action. This route remains available after you leave the server. Include your Discord user ID and relevant message or record references if available. Do not send passwords, bot credentials, or identity documents.

Church of Meta's designated administrator handles requests and may ask for limited information to verify your connection to the records. We can address community-controlled copies we can locate and manage; requests concerning provider-controlled information may also need MEE6 support or Discord's privacy process. Human review does not guarantee reversal of a moderation decision.

Other features and changes

A feature shown in a provider’s catalog does not by itself mean it is configured for this community. Before introducing materially different processing, such as a new AI conversation or ticket-transcript workflow, we will update this notice and provide any additional information and choices required for that feature. This notice does not authorize unrelated reuse of private conversations or sensitive records.

Policy changes

Updated policies and their effective dates are maintained on this website. Material changes will also be announced to the DeepFuckingValue Discord community, with any further notice or choices required by applicable law.