Affinity appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.
Back to all statisticsForensic verdictBased on 3 appearances across the HTPBE? corpus.
Corpus profile
Affinity (Publisher / Designer / Photo) is a desktop design suite; its PDF export rebuilds the document from Affinity’s composition.
Contextual signal: producer/creator mismatch when Affinity is the latest Producer on an institutional-Creator document.
Role in the workflow
Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.
Name fingerprints
Different version strings and spellings observed for Affinity in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 2 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Related profiles
Other tools that frequently share metadata with Affinity in the same documents. Each card links to its own forensic profile.
Long tail
Smaller cuts of the Affinity corpus — useful context, but treat each row as a single data point rather than a strong signal.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.