Copyright & Content Removal Policy

Version 1.0. Effective 2026-10-16.

This page is for people who are not our customers and want something changed in the openbinary corpus: a rights holder whose software we analysed, or anyone else with a concern about what we published. If you have an account, our Terms of Service also apply to you. If your concern is your personal data rather than your rights in software, our Privacy Notice explains that route and this page will still get you to the right place.

What the corpus is

openbinary analyses software and publishes the analysis: metadata, behaviour, components, dependencies, vulnerabilities, capabilities, verdicts and indicators. It covers software we obtained from public sources and analysed ourselves, and files our users have chosen to publish. See our Privacy Notice for what the corpus means for personal data.

What we never publish

• The file itself. We do not publish, distribute or offer downloads of any binary, firmware, package or source file. We publish analysis; we never redistribute the analysed work.
• Anything unlawful, ordered to be removed, or that we conclude violates a person's rights.

Credentials and keys

Analysis of a public file can include credentials, keys, tokens and certificates found inside it. We publish them, because a credential shipped inside a binary is a finding — often the most important one — and because the file is already publicly available to anyone who cares to look. We do not publish them out of private files.

If a credential we published is still live, tell us and we will take it down quickly. Write to security@openbinary.ai or legal@openbinary.ai. The practical order of operations is rotate first, then ask us: we can remove what we published, but we cannot un-publish it, and the credential is in the file you shipped regardless.

Copyright complaints

One process serves everyone, and the DMCA route is the United States version of it. You do not need to know which one applies to you: write to legal@openbinary.ai and we will handle it under whichever law gives you the better claim.

If you own rights in software that appears in the corpus and you believe our analysis infringes them, write to legal@openbinary.ai. A notice we can act on should:

1. be signed by you or someone authorised to act for you;
2. identify the work you say is infringed;
3. identify what you want removed, with the URL or the file's hash;
4. give your name, address, phone number and email address;
5. state that you have a good-faith belief the use is not authorised by the owner, its agent or the law; and
6. state that the notice is accurate and that you are the owner or authorised to act, under penalty of perjury.

We remove or restrict access to material identified in a valid notice, promptly and usually within 3 business days, and we notify the uploader where there is one. We log every notice and our response. We may ask for more detail before acting, and we may decline where we conclude the use is lawful, telling you why and how to take it further.

We may also remove or restrict material at any time, with or without notice, including where we cannot satisfy ourselves that publishing it is lawful, where a court or regulator has asked us to, or where keeping it puts us or someone else at risk. We do not have to give a reason for removing our own published analysis.

Counter-notice. If your material was removed and you believe it should not have been, write to the same address with your signature, identification of what was removed and where it was, a statement under penalty of perjury that it was removed by mistake or misidentification, and your contact details. We forward it to the complainant and restore the material within 10 to 14 business days unless the complainant starts court proceedings.

Repeat infringers. We terminate the accounts of users who repeatedly publish infringing material, in appropriate circumstances.

Designated agent. Our agent for notices under the US Digital Millennium Copyright Act, and for every other route on this page, is legal@openbinary.ai. Registration with the United States Copyright Office — which is what makes the US safe harbour available for content our users publish — is in progress, and our process does not depend on it.

If we have to name the publisher. Where a file was published from a workspace rather than harvested, we may tell a complainant who published it, as our Terms of Service permit and where we judge the claim credible. We will tell the publisher before we do unless we are prohibited.

Other things you may want changed

• Your personal data in the corpus — names, paths, addresses, and anything else that identifies you. Write to legal@openbinary.ai. We will redact or remove it where your interest outweighs publication, and we can de-attribute a record instead of removing it, which is usually what a publisher actually wants. The Privacy Notice sets out the process, the timescales, and two limits: a file's existence and factual properties stay in the record, and we cannot recall what has already been read.
• Something that should not be public at all — a leaked secret, an internal document, material about a child, or anything unlawful beyond the malware we analyse deliberately. Write to security@openbinary.ai or legal@openbinary.ai and we will treat it as urgent.
• A vulnerability in our own software — see our security contact at security@openbinary.ai.

Why removal stops at display, not at record

We publish the analysis ourselves, and we run this process so that a rights holder has somewhere to go and gets a straight answer. That is a choice we make; it is not a statement about our legal status, and nothing here waives any defence available to us.

We treat a published finding as a fact. We will stop displaying analysis, and we will not republish it. We will not state that a file was never analysed, and we will not withdraw a finding already relied on in our own security work or in another user's.

What we cannot do

We cannot remove analysis that was already exported, cached, indexed or copied by someone else before we acted. We cannot recall a finding. And we cannot act on a request that does not identify what should be removed well enough for us to find it.

Contact

legal@openbinary.ai — copyright and content removal, and personal data security@openbinary.ai — a leak or a vulnerability 68 Circular Road #02-01, Singapore 049422 if you prefer paper