Privacy Policy

Effective date: September 12, 2026

This Privacy Policy explains how the operator of this Group Test Manager deployment ("Operator," "we," "us," or "our"), Group Test Manager operator, collects, uses, discloses, and retains information when you use the website, an account, a Telegram or Discord bot, automated report analysis, notifications, or related features (collectively, the "Service"). The Operator is responsible for the Service's processing; Telegram, Discord, Google, laboratories, payment providers, and AI providers process information under their own terms for their respective services.

Do not upload personal or medical information in laboratory reports. The Service is designed for product/sample reports, not patient records, clinical care, or protected health information. It is not represented as HIPAA-compliant.

1. Information we collect

Account and profile information

Username, email address, password hash, optional Telegram and Discord usernames, linked platform user/chat identifiers, notification preferences, digest settings, account status, administrator status, and account dates. We do not store your plaintext password.

Group-test and participation information

Participation requests and decisions; participant name or handle; region/state and U.S.-based status; vial-donor, order, verification, shipping, payment, amount owed/paid, payment-method preference, notes, and timestamps; and group-test descriptions, vendors, samples, batches, costs, payment destinations, laboratories, and results. Some payment destinations or wallet addresses entered by administrators may be visible to eligible participants. The Service does not collect payment-card credentials through its own forms.

Reports, public results, and analysis records

Uploaded PDF/image files, public report URLs, report titles and descriptions, tags, itemized laboratory values, submission/review state, source fingerprints and technical metadata, AI-proposed findings and confidence values, administrator decisions, provider/model identifiers, request identifiers, token/usage metadata, errors, and bounded diagnostic logs. Public Results are shared with Service users and enabled bot browsing interfaces; group-test results are limited by the Service's access rules.

Bot and notification information

Telegram or Discord public profile details supplied by those platforms; stable user, chat, channel, guild, thread, message, callback, and update identifiers; messages, commands, arguments, buttons, files, links, and replies you send to a bot; account-link tokens and their expiry/use timestamps; command invocation timestamps; notification and digest events; webhook delivery metadata; and Telegram webhook source IP addresses. The Service processes only events delivered to its configured bot or webhook endpoints, subject to platform and administrator scope settings.

Device, usage, and security information

The hosting platform, reverse proxy, application server, and optional analytics tools may process IP address, request time, requested URL, referring page, browser/device and operating-system information, cookie or session identifiers, approximate location derived from IP address, error records, and security events. Authentication uses a session cookie, and forms use a security token to prevent cross-site request forgery.

2. How information is collected

We collect information directly from you and administrators; automatically from use of the website; from your Telegram or Discord interaction; from public report links you submit; from enabled laboratories or third-party services; and from AI providers that return an analysis. If another person enters information about you as an organizer or administrator, they are responsible for having authority to do so.

3. How we use information

create, authenticate, secure, support, and administer accounts;
coordinate group tests, participation, cost allocation, payment status, samples, and result access;
publish approved Public Results and deliver authorized reports;
link messaging identities, execute bot commands, and send transactional notices and digests;
extract proposed laboratory values and route them to administrators for review;
detect abuse, prevent duplicate processing, investigate errors, enforce terms, and protect users;
measure and improve Service reliability and usage; and
comply with law, resolve disputes, and protect legal rights.

Where a law requires a legal basis, processing may rely on performance of our agreement with you, legitimate interests in operating and securing the Service, consent for optional technologies or communications, and compliance with legal obligations. You may withdraw consent where processing is based on consent, without affecting earlier processing.

4. Telegram bot processing

The Telegram bot can link an account; list tests and results; report status; request participation; execute administrator-configured commands; send password resets, status notices, and digests; accept a public link or PDF/image laboratory report; and support administrator review in a private chat, group, channel, or forum thread. Depending on the chat and Telegram's bot privacy settings, the bot may receive messages directed to it or broader group activity. Other chat members may see your commands and bot replies. Telegram independently processes your Telegram account and messages; review Telegram's Privacy Policy.

5. Discord bot processing

The Discord bot can link an account; provide test, status, participation, and Public Results commands; run administrator-configured commands; and deliver direct or channel messages. It receives interaction data that Discord provides, which may include your Discord user/display name and ID plus guild, channel, thread, command, and interaction identifiers. Other server or channel members may see non-private interactions. Discord independently processes platform data; review Discord's Privacy Policy.

6. Root and other webhook notifications

Administrators may configure Discord webhooks and a generic outbound "Root" webhook. The Service sends the rendered notification body and configured sender name to the destination URL. The recipient controls the destination system and may log, display, or redistribute the message. Do not configure a webhook destination unless its operator is authorized to receive the intended notification content.

7. Automated analysis providers

If automated analysis is enabled, the Service sends the submitted report content and limited contextual fields needed for extraction to the single AI provider selected by an administrator. The available implementations are OpenAI, xAI (Grok), and Anthropic (Claude). The Service stores the provider/model used, structured response, operational metadata, and administrator review. It does not silently send one report to every provider.

OpenAI: API requests are sent with response storage disabled by the application. OpenAI states that API data is not used to train its models unless the customer opts in, while default abuse-monitoring logs may be retained for a limited period. See OpenAI API data controls.
xAI (Grok): API processing is governed by the Operator's business/API agreement and xAI's applicable data controls. See xAI's Privacy Policy and privacy resources.
Anthropic (Claude): API processing and retention are governed by the Operator's commercial terms and workspace settings. See Anthropic's commercial data-retention notice.

Provider terms, retention, regions, and controls can change. Do not submit personal information in a report, and contact an administrator before submission if you need to know which provider and account controls are active.

8. Google Analytics and cookies

The Operator may enable Google Analytics on public or authenticated pages to understand page usage and improve the Service. When enabled, Google Analytics may receive page URLs and titles, referral information, interactions, approximate location, and browser/device/network identifiers, and may use first-party cookies such as _ga and _ga_<container-id> to distinguish users and sessions. The Operator should configure analytics so account fields, report content, laboratory values, bot messages, and other directly identifying or sensitive information are not intentionally sent to Google.

This repository does not itself enable a Google tag or advertising features. If a deployment enables Analytics, the Operator must provide any consent control required by applicable law and update this notice if it enables Google Signals, advertising reporting, remarketing, user-ID measurement, or other advertising features. You can reject analytics through the deployment's consent control where offered, restrict or delete cookies in your browser, or use the Google Analytics Opt-out Browser Add-on. Learn how Google processes data at Google's partner-sites notice.

9. When we disclose information

We disclose information only as reasonably needed:

to users and administrators according to group-test, Public Result, and role-based visibility;
to hosting, database, object-storage, email, Telegram, Discord, webhook, AI, analytics, and support providers;
to laboratories, organizers, or other parties you direct us to involve;
to investigate security incidents, enforce these Terms, protect rights and safety, or prevent fraud;
to comply with lawful process or legal obligations; or
in a reorganization or transfer of the Service, subject to appropriate confidentiality and notice.

We do not sell personal information for money. We do not knowingly use laboratory-report content or bot messages for cross-context behavioral advertising. Some privacy laws may define certain analytics disclosures as "sharing" even without payment; where applicable, you may opt out using the controls described above or by contacting the site administrator.

10. Retention

We retain account, participation, report, review, and configuration records while needed to operate the Service and afterward as reasonably necessary for audit history, disputes, security, backups, and legal obligations. Single-use bot-link tokens expire but their issuance/use records may remain. Command and webhook deduplication metadata, notification events, and analysis records are retained for operational integrity. Diagnostic logs are size-bounded by the application, but hosting and third-party logs follow their own settings. Public content may remain visible until an administrator unpublishes or deletes it. Deletion from active systems may not immediately remove backups or third-party copies.

The application does not currently promise a universal automatic deletion schedule. The Operator should adopt and document a deployment-specific retention schedule and delete information when it is no longer reasonably needed.

11. Security

The Service uses measures that include password hashing, session and form protections, role-based access, expiring link tokens, webhook verification options, bounded uploads, restricted source retrieval, signed object links, secret redaction, and administrator review. No system is completely secure. Use a unique password, keep bot-link tokens private, avoid sensitive report content, and promptly report suspected compromise.

12. International processing

The Operator and service providers may process information in countries other than yours, where privacy laws may differ. Where required, the Operator should use an approved transfer mechanism and appropriate contractual or technical safeguards. Contact the site administrator for deployment-specific hosting and processing locations.

13. Your choices and privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or objection; withdraw consent; opt out of certain sharing or targeted advertising; or appeal a decision. You can update some account and notification settings in your profile, stop interacting with a bot, leave a chat/server, manage platform privacy settings, and control cookies as described above. Submit other requests to the site administrator through the contact channel supplied for this deployment. We may verify your identity and retain information when an exception applies. You may also complain to your local privacy authority.

Browser “Do Not Track” signals are not standardized and the application does not currently respond to them. Where legally required and technically supported by the deployed analytics tooling, the Operator should honor recognized opt-out preference signals such as Global Privacy Control.

14. Children

The Service is not directed to children and is limited to users age 18 or older. We do not knowingly collect personal information from children. Contact the site administrator if you believe a child submitted information.

15. Changes and contact

We may update this Policy as practices, providers, or laws change. We will revise the effective date and provide additional notice of material changes where required. Privacy questions, requests, or complaints should be sent to the site administrator through the contact channel supplied for this deployment.