Privacy Policy

How CupTalks handles privacy and personal information.

Effective date: August 19, 2026

Privacy basics

CupTalks should be used with care. Members should share only what they are comfortable sharing and avoid posting identifying details about themselves or other people.

Public forum posts, replies, profile fields marked public, public helper signals, polls, and resource feedback may be visible to other members or visitors depending on the feature.

Optional website analytics

With a visitor's permission, CupTalks uses Google Analytics on nonsensitive public pages to understand general traffic and improve the website. Analytics is not loaded until permission is granted.

CupTalks does not enable analytics on private messages, consultations, help requests, member profiles, safety reports, account or administration pages, searches, or individual community conversations. Names, usernames, email addresses, account IDs, search terms, message content, consultation subjects, and post content are not intentionally sent to Google Analytics.

Advertising storage, Google Signals, and ad-personalization signals are disabled. Visitors may decline analytics or reopen Analytics preferences from the site footer.

Information used by the app

  • Account details such as name, email, profile settings, and login status.
  • Forum posts, replies, polls, messages, help requests, consultation messages, and uploaded attachments.
  • Safety reports, moderation decisions, administrator review notes, and notification records.
  • Helper profile information such as support topics, strengths, availability, and self-described experience.

Privacy boundaries

  • Private messages and consultation rooms are intended for supportive conversation, not crisis management or sensitive records.
  • Administrators or moderators may review reported content to protect community safety.
  • Members can change profile visibility and open-to-help settings from their profile page.
  • Uploaded files should be treated as shareable with the conversation recipient and should not include sensitive documents.
#policy#safety