When CleanPlay can make a report
CleanPlay first shows a privacy choice. If automatic reporting is
kept on, it can prepare a report when dialogue analysis or scene
scanning stalls or fails, after a suspected processing-related
crash, hang, or unexpected exit, and when a saved recovery attempt
succeeds or fails. A development build can also offer a button for
sending the same kind of report manually. Normal playback and
successful processing do not create ordinary incident reports,
apart from a narrowly linked recovery result.
What a report can include
A report can include the CleanPlay version and exact build,
processing-engine and model revisions, macOS and general Mac
hardware facts, memory, power, disk, and thermal conditions,
broad media facts such as source type, container, codecs,
duration, resolution, and audio format, and typed processing facts
such as the current stage, progress, timings, resource limits,
helper status, checkpoint health, and recent technical events.
These fields are fixed and bounded; arbitrary notes and private
error text are not accepted.
What CleanPlay never sends
These reports do not contain movie or title names, file names or
paths, drive, server, or share names, library contents, artwork,
audio, video, movie frames, screenshots, recognized dialogue,
subtitle or profanity text, mute-window or scene edits, passwords,
account credentials, access tokens, or security bookmarks. No
movie content is uploaded as part of CleanPlay diagnostics.
Network security and limited service logs
As with any internet request, the hosting provider can process
basic network and security information such as an IP address,
request time, route, response status, and abuse signals to
deliver and protect the service. CleanPlay's own diagnostic
application logs contain categorical event and status fields
only. They do not record the report body, movie or file details,
installation, signing-key, challenge, or receipt identifiers,
secrets, or arbitrary error messages. Remote collection remains
disabled until Jintus Labs has reviewed the hosting provider's
log redaction and retention settings.
Pseudonymous links, not media names
CleanPlay uses a private secret held by that app installation to
create one-way HMAC identifiers. They can show Jintus Labs that
reports came from the same CleanPlay installation, or that repeat
reports on that installation concerned the same movie or source.
They do not reveal the movie, file, path, drive, server, or person,
and they are not shared for advertising. The report-signing key
establishes continuity for an app installation; it is not an
Apple identity or Jintus Labs account.
Support intake and automated repair analysis
A report is signed by CleanPlay and sent to the Jintus Labs support
intake, where an accepted copy can be delivered to
[email protected].
Privacy-screened reports may also be examined by Jintus Labs'
CleanPlay-specific automated diagnostic and repair system. That
system can match a report to Jintus Labs' preserved source code,
reproduce approved synthetic faults, run tests, and prepare a
proposed source-code fix in an isolated workspace. A proposed fix
remains subject to safety checks, testing, and Jintus Labs review.
It cannot remotely modify a user's installed app, settings,
library, movie files, subtitles, edits, external drives, or network
shares. Users receive changes only through a separately released
CleanPlay update.
Retention and your choice
Pending reports can remain on the Mac for up to 30 days while
CleanPlay waits for the privacy choice or a connection. Turning
automatic reporting off deletes locally saved pending reports,
report history, and diagnostic journals without deleting movie
preparation, edits, or library data. An accepted server report and
its delivery receipt are scheduled for deletion after 30 days.
The server also keeps a pseudonymous registration record so it can
authenticate future reports from the same CleanPlay installation.
That record contains a random installation identifier, a public
signing key and fingerprint, sequence/status information, and
activity dates—not movie, library, subtitle, or dialogue
content. It is scheduled for deletion after 90 days without
registration or report activity, once no retained report or
short-lived registration record still refers to it.
A copy delivered to the support mailbox is kept only as long as
reasonably needed for support, troubleshooting, validation, and
basic records, unless the law requires otherwise. Turning the
setting off cannot recall a report already delivered; you can
contact Jintus Labs to ask about a previously sent report. Source
archives used to reproduce a build are Jintus Labs code records,
not copies of a user's media or report content.