Privacy Policy

Summary: Professor Compressor processes videos locally in your browser. Finished files, including fitting MP4s sent without recompression, pass through the relay to Discord. The relay does not write those files to disk.

1. Scope

This policy describes how the hosted Professor Compressor Discord bot and browser compressor (the “Service”) process information. It does not govern Discord, your browser, or independently operated services.

2. Information processed

• Discord interaction data: Discord user, server, and channel identifiers, interaction metadata, and the applicable Discord upload limit are processed to create a session and return results to the correct channel.
• Output files: finished MP4 files, including fitting MP4s sent unchanged, and their filenames are transmitted over HTTPS and held temporarily in server memory while they are validated and delivered to Discord.
• Security data: an IP address is processed temporarily in memory to enforce request-rate limits and protect the Service from abuse.
• Operational data: aggregate process counters may track sessions, queued files, delivered bytes, failures, and rate-limited requests. Installation notifications sent privately to the operator may include a server name, server identifier, member count, and totals. Private compression-session, browser progress, expiration, and outcome notifications also include the command user's Discord username and user ID so the operator can correlate a session with a delivery issue. Browser progress reports cover link opening, file selection count, pressing Compress, cancellation, and page exit or reload. A page-exit report is best-effort and may not arrive if the browser or connection fails. These alerts do not include filenames or video files.
• Optional feedback: email feedback and support links open your email application. No feedback is sent unless you choose to send an email. If you do, the operator receives the email address and message you provide. The support-server link opens Discord; anything you post there is subject to that server's visibility and Discord's policies. Do not share private videos or session links.

3. Video processing and storage

Videos needing conversion or compression are processed by FFmpeg WebAssembly inside your browser; only their resulting MP4 files are uploaded. A fitting MP4 may skip recompression, in which case the original file is uploaded unchanged through Professor Compressor to Discord. Uploaded files are held only in volatile memory while awaiting delivery and are released after delivery, failure, cancellation, expiration, or a service restart. Professor Compressor does not intentionally write video files to disk.

After delivery, Discord stores the resulting message and attachments under Discord’s own policies and the settings of the destination server.

4. How information is used

Information is processed only to operate the compression workflow, route files to the requested Discord channel, enforce technical limits, secure the Service, diagnose failures, and understand aggregate reliability.

5. Sharing

Information is shared with Discord when commands are received, operational notifications are sent, and completed files are delivered. Infrastructure providers may process network traffic as necessary to host and secure the Service. Professor Compressor does not sell personal information or use it for targeted advertising.

6. Retention

Unused links expire after a short period, active compressor sessions expire automatically, and delivery data is kept in memory only as long as needed to complete or fail the request. IP-based rate-limit entries expire after their short rate-limit window. Aggregate counters reset when the process restarts. To recover an interrupted delivery response without sending files twice, the relay keeps a bounded in-memory delivery receipt for up to one hour. It contains the session authentication secret, outcome, and file count, not video bytes or filenames. Active browser processing can renew a session for a bounded period; idle sessions expire normally. Discord may retain delivered attachments according to its own policies.

7. Cookies and tracking

The compressor does not use advertising trackers or third-party analytics. It uses one short-lived, first-party, HTTP-only browser cookie to let the same browser reopen a claimed link after a refresh and check a delivery already in progress. The cookie contains a random secret, not your name or video, and expires after at most three hours. The relay also uses a separate short-lived page secret to authorize uploads and status checks.

8. Security

The Service uses HTTPS, expiring single-use links, browser-bound session secrets, file validation, rate limiting, and bounded in-memory queues. No system can guarantee absolute security, and the relay is not end-to-end encrypted because it must send the completed files to Discord.

9. Your choices

You may choose not to use the Service, cancel before uploading completed files, remove the bot from a server you manage, decline to send optional feedback, or delete delivered files from Discord if you have permission to do so. The Service does not maintain user accounts or a persistent personal-information database. Operator alerts and feedback emails may remain in the operator's Discord channel or mailbox until deleted.

10. Age requirements

The Service is intended only for people permitted to use Discord under Discord’s terms and applicable law.

11. Changes and contact

This policy may be updated when the Service changes. Material changes will be reflected by the effective date above. Questions or privacy concerns may be sent by email to email or through the support server. Do not include private videos, credentials, or session links in public channels.