pessimist qotd privacy policy

last updated 22 August 2026

PESSIMIST QOTD PRIVACY POLICY

Effective date: 1 September 2026

Last updated: 1 September 2026

1. SCOPE AND OPERATOR

This policy applies to Pessimist QOTD ("QOTD"), the Discord bot with Discord user ID 1375064321935151114, qotd.pessimist.io, its user and administrator portals, Discord login and setup flows, public profiles, leaderboards, feeds, showcase features and related notifications.

Pessimist QOTD is operated by Pupi.Co Pty Ltd. The Pessimist Privacy Policy also applies and explains Pupi.Co's general security, international-processing, privacy-rights, complaints and contact practices. This policy describes QOTD-specific handling.

2. INFORMATION QOTD COLLECTS

2.1 Identity, account and preference information

QOTD may collect:

(a)

Discord user ID, username, display name and avatar URL;

(b)

profile bio and profile links voluntarily supplied in the portal;

(c)

profile visibility and privacy settings;

(d)

notification and role-membership preferences;

(e)

timezone and the source used to set it;

(f)

last-login, last-notification-view and account timestamps; and

(g)

account status, including a temporary or permanent restriction, reason, source and expiry.

2.2 Questions, answers and reports

QOTD may collect:

(a)

question text submitted by direct message or through the portal;

(b)

original and edited versions of a question;

(c)

answer and reply text, including image URLs deliberately included by a user;

(d)

question, answer and Discord message IDs;

(e)

submission, posting, answer and edit timestamps;

(f)

reports and free-text report reasons;

(g)

reply-chain and notification content needed to route a response; and

(h)

moderation status, reason and related review information.

Do not submit sensitive personal information about yourself or another person in a question, answer, bio, link or report.

QOTD does not read or store unrelated Discord conversations. It processes direct submissions, replies to QOTD posts, reactions or interactions with QOTD, and server information needed for configured QOTD features.

2.3 Engagement and community information

QOTD may collect or derive:

(a)

question views, answer counts and participation history;

(b)

likes and the user associated with a like;

(c)

streaks, achievements, scores and leaderboard positions;

(d)

question-posting and answer history;

(e)

personalised feed and recommendation information;

(f)

QOTD Wrapped summaries;

(g)

whether relevant feed or Wrapped items were displayed or selected; and

(h)

account and feature events such as logins, profile updates, question actions and privacy-setting changes.

2.4 Server and administrator information

QOTD may collect:

(a)

Discord server ID, name, icon and owner ID where needed;

(b)

channel and role IDs;

(c)

leaderboard channel and message IDs;

(d)

optional invite links used for a public server page;

(e)

setup-token and expiry information;

(f)

posting schedule, queue, automation and welcome configuration;

(g)

server member and QOTD-role counts;

(h)

posted-question, answer-count and server-participation history; and

(i)

server notification, reminder and role settings.

2.5 Website and analytics information

QOTD may process:

(a)

requested page, timestamp and external referrer hostname;

(b)

browser, operating system and device category;

(c)

approximate country derived from an IP address;

(d)

raw IP address transiently for country lookup, security and rate control; and

(e)

a salted identifier derived from IP address and user agent for first-party page analytics.

The derived visitor identifier is pseudonymous and is not described as anonymous. It may still constitute personal information.

2.6 Newsletter information

If you directly and explicitly subscribe to QOTD news or product updates, we may collect your email address, optional first name, signup source, consent record and subscription status. QOTD does not collect email addresses from Discord OAuth and does not add a person to a marketing list merely because the person signed into QOTD.

3. WHY QOTD USES INFORMATION

QOTD uses information to:

(a)

authenticate users and administrators;

(b)

provide login links, setup links and account access;

(c)

accept, moderate, select and post questions;

(d)

display answers and route reply notifications;

(e)

provide profiles, public server pages, leaderboards, feeds, achievements and Wrapped summaries;

(f)

calculate views, likes, scores, streaks and engagement statistics;

(g)

personalise question selection and recommendations;

(h)

configure channels, roles, schedules, queues and reminders;

(i)

moderate content, investigate reports and enforce restrictions;

(j)

secure the service, prevent abuse and diagnose errors;

(k)

measure website and service performance;

(l)

create aggregate or properly deidentified analytics;

(m)

send newsletters or product updates where the user subscribed; and

(n)

meet legal obligations and resolve disputes.

4. PUBLIC INFORMATION

QOTD is partly a public and community service. Depending on your settings and participation, the following may be visible on qotd.pessimist.io, Discord, public profiles, feeds, leaderboards or a public showcase:

(a)

question and answer text;

(b)

Discord username or display name;

(c)

avatar;

(d)

bio and profile links;

(e)

timestamps;

(f)

views, likes, answer counts, streaks, achievements and rankings;

(g)

public server name, icon, invite and engagement statistics; and

(h)

reasons a question or answer was selected for a showcase.

Before posting, assume that a question or answer may be copied or shared by other Discord users. Content already posted in Discord may remain there after a QOTD account is deleted because Discord and server administrators control those copies.

A private, hidden or paused profile setting affects future display within QOTD but may not remove content already posted to Discord, cached by another service or copied by another user.

5. AI AND AUTOMATED PROCESSING

5.1 Moderation

QOTD may send question or answer text to OpenAI through the OpenAI API for automated safety moderation. When moderating a question, QOTD may also provide up to five recent rejected questions submitted by the same user during the preceding 24 hours so the system can assess a repeated pattern.

Automated moderation may approve or reject content and may flag a clear repeated pattern for temporary or permanent restriction. A prior rejection does not automatically result in a ban. Factors include the submitted text, recent rejected submissions and configured safety rules.

5.2 Other AI-assisted functions

QOTD may also use OpenAI for:

(a)

ranking or selecting candidate questions;

(b)

assisting an administrator with server setup using relevant channel or role names and IDs; and

(c)

selecting candidate public content for a showcase.

5.3 Provider handling and review

Pupi.Co does not opt QOTD content into model training and does not use Discord message content to train its own models. OpenAI may retain API inputs and outputs for limited abuse-monitoring or legal purposes under its API terms unless Pupi.Co has enabled a different approved retention control.

OpenAI information:

https://openai.com/policies/privacy-policy/

https://platform.openai.com/docs/guides/your-data

Automated systems can make mistakes. You may request human review of a content rejection or account restriction by emailing pessimist@emmasdome.co with your Discord user ID and the relevant question, answer or message ID.

6. NOTIFICATIONS

Where enabled, QOTD may send direct messages concerning:

(a)

a submitted question;

(b)

an answer or reply;

(c)

login or account access;

(d)

a streak, achievement or requested reminder;

(e)

a moderation or account-safety action; or

(f)

a server feature the user or administrator enabled.

You can change available notification settings in the portal or ask us for assistance. QOTD does not send unrelated advertising through Discord direct messages.

7. COOKIES AND SIMILAR TECHNOLOGIES

QOTD may use:

(a)

a user-session cookie for up to 7 days;

(b)

an admin-session cookie for up to 24 hours;

(c)

an admin login challenge for approximately 15 minutes;

(d)

an initial user login token for up to 24 hours;

(e)

a sidebar preference cookie for up to 7 days; and

(f)

first-party page analytics as described in section 2.5.

QOTD does not use Google Analytics, Meta Pixel or a separate behavioural-advertising pixel unless this policy and any required consent notice are updated first.

Where applicable law requires consent for first-party analytics, analytics will not begin for that user until consent is obtained. Essential authentication and security cookies do not support targeted advertising.

8. SERVICE PROVIDERS AND DISCLOSURES

QOTD may disclose information to:

(a)

Discord, for OAuth login, direct submissions, server posts, answers, reactions, roles, notifications and Discord-hosted avatars or icons;

(b)

OpenAI, for the AI functions described in section 5;

(c)

contracted cloud infrastructure, database, storage, security and logging providers;

(d)

Neon or another contracted database provider, where used to store QOTD records;

(e)

Mailchimp, only when a person directly subscribes to QOTD email updates;

(f)

ip-api.com, for IP-based country estimation;

(g)

Top.gg, where public showcase content is deliberately displayed or a user follows a Top.gg link; and

(h)

Google, where a browser loads Google Fonts.

Provider information:

Discord: https://discord.com/privacy

OpenAI: https://openai.com/policies/privacy-policy/

Mailchimp: https://www.intuit.com/privacy/statement/

Neon: https://neon.com/privacy-policy

ip-api: https://members.ip-api.com/privacy-policy

Top.gg: https://top.gg/privacy

Google: https://policies.google.com/privacy

Providers handling Discord API data for Pupi.Co must be bound in writing to act only at Pupi.Co's direction and not use the information for their own purposes.

9. ANALYTICS

QOTD may use pseudonymous first-party analytics to measure page traffic, service performance and broad feature use. Identifiable QOTD participation records are used only where needed to provide user-facing features such as likes, streaks, profiles, rankings and notifications.

After the applicable analytics period, records are deleted or converted into aggregate or properly deidentified statistics. We call information anonymous only where it is no longer reasonably linkable to a person.

We do not sell personal information, disclose Discord API data to advertising networks or use QOTD information for targeted advertising.

10. RETENTION

Subject to a valid user or Discord deletion request and legal requirements, QOTD's intended standard retention is:

(a)

user-session cookie: up to 7 days;

(b)

user login token: up to 24 hours and deleted within 30 days after expiry;

(c)

admin challenge: approximately 15 minutes;

(d)

admin session: up to 24 hours;

(e)

setup and timezone tokens: until use or expiry and deleted within 30 days afterward;

(f)

active account, profile and preferences: while the account remains active;

(g)

questions and answers: while used for QOTD's community features, subject to deletion or deidentification described in section 11;

(h)

identifiable likes, streaks, achievements, rankings and notification routes: while needed to provide those active features;

(i)

posted-question and server history: ordinarily up to 24 months after posting, after which it is deleted or deidentified unless still needed for a visible history feature;

(j)

moderation reports and restriction history: ordinarily up to 24 months after closure, unless deletion is required sooner or longer retention is required by law;

(k)

pseudonymous website analytics: ordinarily up to 13 months, followed by deletion or aggregation;

(l)

event and security logs: ordinarily up to 90 days, unless needed for an active incident;

(m)

newsletter subscription data: until unsubscribe or deletion, with a minimal suppression record retained to honour the opt-out; and

(n)

aggregate or properly deidentified statistics: may be retained without a fixed period.

Discord API data is promptly deleted when the user or Discord validly requests deletion, when it is no longer necessary for QOTD's approved functionality, or when QOTD stops operating, unless retention is required by law.

11. ACCOUNT DELETION AND DEIDENTIFICATION

You may request deletion through an available portal control or by emailing pessimist@emmasdome.co. A blocked or frozen user may use the email process even if ordinary portal controls are unavailable.

On a verified deletion request, Pupi.Co will, subject to lawful exceptions:

(a)

remove the active profile and account association;

(b)

delete notification routes and preferences;

(c)

delete answers or remove their association with the user;

(d)

remove the link between retained questions and the user;

(e)

replace a displayed attribution with a neutral deleted-user label where retaining non-identifying question text is appropriate;

(f)

delete or deidentify likes, streaks, achievements, event records and recommendations associated with the user; and

(g)

instruct relevant service providers to delete Discord API data within their control.

A question is retained after account deletion only if its link to the user and any personal information within the text have been removed so it is no longer reasonably capable of identifying the user. Otherwise it is deleted.

Content already posted in Discord may remain in Discord. Restricted backups may retain a copy temporarily until ordinary rotation, during which time the deleted information is put beyond ordinary use.

12. ACCESS, CORRECTION AND OTHER RIGHTS

The portal may allow you to view or export some profile, question, answer and preference information. A portal export may not contain every technical or moderation record.

For a comprehensive access, correction, deletion, objection or human-review request, email pessimist@emmasdome.co with your Discord user ID and relevant message or server IDs. We may request proportionate identity verification.

We aim to complete verified requests within 30 days. The full rights and complaint provisions in the Pessimist Privacy Policy apply.

13. CHILDREN

QOTD is not directed to anyone below Discord's minimum age or the minimum age required by applicable law. If Pupi.Co learns that prohibited child data has been collected, it will take reasonable steps to delete it. A parent or guardian may contact pessimist@emmasdome.co.

14. SECURITY AND INTERNATIONAL PROCESSING

The security and international-processing provisions in the Pessimist Privacy Policy apply. Information may be processed outside Australia by Discord, OpenAI and contracted providers. We use access controls, session protections, content-safety controls and provider security measures, but no online service can guarantee absolute security.

15. COMPLAINTS

Privacy questions and complaints may be sent to pessimist@emmasdome.co. We aim to provide a substantive response within 30 days. Further complaint information, including possible contact with the Office of the Australian Information Commissioner, appears in the Pessimist Privacy Policy.

16. CHANGES

We may update this policy as QOTD changes. We will update the date above and provide reasonable notice of a material change. A materially different use of Discord API data will not begin until any required user notice, Discord approval or consent has been completed.

17. CONTACT

Pupi.Co Pty Ltd

Suite 44173, 3/2237 Gold Coast HWY

Mermaid Beach

Queensland

4218

Australia

Email: pessimist@emmasdome.co