Procedural Defects: Data-Quality Grounds Under Article 12 RPD

Article 12 of the RPD requires that data processed in Interpol’s files be accurate, relevant, not excessive in relation to its purpose, and up to date. That is a real, enforceable standard, not a formality. A notice that rests on incorrect personal details, on stale information, or on allegations disproportionate to any legitimate purpose fails it — and a failure of data quality is a compliance failure the CCF can act on, independent of the political or commercial character of the case.

A Red Notice must rest on a genuine legal foundation — typically a valid arrest warrant or judicial decision in the requesting country. Where that foundation is absent, defective, expired, or has been withdrawn, the notice loses its footing. Similarly, the requesting bureau must be able to show facts genuinely linking the person to criminal conduct. A notice built on a summary that does not connect to a real, current judicial basis is vulnerable on precisely this ground.

The Article 83 conditions are themselves a procedural check. If the alleged offence does not meet the seriousness and penalty thresholds — broadly, a maximum of at least two years for prosecution or at least six months remaining for conviction — or is not of genuine interest to international police cooperation, the notice does not qualify, regardless of how the requesting state characterises it. This overlaps with the commercial-disputes ground, and the two are often argued together.

One of the most useful features of the process: the burden is on the requesting country to substantiate its notice. When the CCF puts questions to a National Central Bureau and the bureau fails to answer despite reminders, that silence creates serious doubt about compliance — and the CCF may delete or block the data without even ruling on the merits of the underlying case. A source country that cannot or will not defend its own request frequently defeats it by default.

Because data must be relevant, not excessive, and up to date, notices can also be challenged as disproportionate or outdated: an old alert for a minor matter, a notice left standing long after circumstances changed, or data retained beyond any legitimate purpose. These arguments rarely carry a case alone, but they add weight and give the CCF additional, objective reasons to act — particularly valuable when your central ground is strong but you want to close every door.

Procedural defects are rarely glamorous, but they are dependable, objective, and hard to rebut — and they pair naturally with every other ground. Their limitation is that a technically clean notice with a solid legal basis will not fall on procedure alone. The smart approach is to plead procedural defects alongside your primary ground, so the CCF has both a substantive and a technical route to deletion. Most such arguments are well within reach of a careful self-filer; see removing a notice without a lawyer.

You can often identify procedural weaknesses yourself, straight from the access response, if you know what to look for. Read it as a sceptic. Does the summary of the allegation actually reference a judicial decision or arrest warrant, or does it float free of any concrete legal basis? Are the dates coherent, or does the matter look old enough that a limitation period may have run? Do the personal details match you precisely, or are there errors and inconsistencies that suggest inaccurate data? Is the description of the offence specific and evidenced, or a vague, sweeping characterisation that could mask a private dispute or a political motive?

Each of those red flags maps to a rule. A missing or defective legal basis undermines the notice’s foundation. Stale information and expired timeframes offend the requirement that data be up to date. Errors in your details offend the requirement that data be accurate. A vague, unsupported summary offends both the seriousness conditions and the demand for facts genuinely linking you to criminal conduct. Note every such flag as you read, and build each into your request as a discrete procedural argument — stacked, where you have one, beneath your primary substantive ground. Because these defects are objective and drawn from the notice’s own text, they are among the hardest points for a requesting country to argue away, and they give the CCF clean, technical reasons to act even where the bigger picture is contested.

The most effective way to use procedural defects is rarely on their own — it is as reinforcement, stacked beneath whatever substantive ground carries your case. A political-motivation argument becomes harder to dismiss when it is joined by the observation that the notice also lacks a proper judicial basis, rests on stale data, or comes from a country that will not substantiate it. Each procedural point gives the CCF an additional, independent reason to act, so that even a Commission unpersuaded by your main ground may delete on a technical one.

Structure this deliberately. Lead with your strongest substantive ground and prove it. Then, in a distinct section, list the procedural defects as discrete points, each tied to the rule it offends — Article 12 for inaccurate or outdated data, the missing legal basis for an unfounded notice, the Article 83 thresholds for an offence that does not qualify, and the source country’s non-cooperation where it applies. Present them as clean, objective observations drawn from the notice’s own text, not as a scattergun of complaints. The value of this layering is redundancy: you are giving the CCF several routes to the same destination, so that your case does not depend on a single argument landing perfectly. Strong requests are built this way — one powerful substantive ground, supported by a tidy stack of procedural defects, each of which alone might be enough and all of which together are difficult to overcome.