Data retention limits and automatic review of files

The longer a Red Notice stays on INTERPOL's systems, the more damage it does. Travel closes down. Banking relationships break. Visa applications stall. And, crucially, the underlying file of data hardens into something that feels institutional and permanent. As of mid-2025, practitioners before the CCF are seeing a sustained rise in matters where the requesting state has simply allowed a notice to age, with no realistic prospect of extradition and no corresponding review of whether the data still meets INTERPOL's own processing conditions.

Data retention limits and automatic review of files are a recognised ground to challenge an INTERPOL Red Notice or diffusion before the Commission for the Control of INTERPOL's Files (CCF). The RPD – INTERPOL's Rules on the Processing of Data – sets data-quality, data-accuracy and retention conditions that every notice must continue to satisfy. Where a notice has been held beyond a period proportionate to the underlying allegation, or where no periodic review has been conducted as the rules require, the data may no longer meet those conditions. That is a concrete ground for deletion, independent of the merits of the underlying prosecution.

This analysis examines when the ground applies, how it is evidenced before the CCF, how it interacts with other grounds under INTERPOL's Constitution, and what realistic weight it carries when argued alone or in combination.

What do data retention limits actually mean in INTERPOL's system?

Retention limits are the rules that govern how long personal data may be processed inside INTERPOL's systems before it must be reviewed or removed. They are not a technicality. They are a substantive data-quality obligation embedded in the RPD's data-accuracy and proportionality requirements, and they apply to every notice on INTERPOL's files – including ones where the underlying criminal allegation is genuine.

The core question is not whether the original processing was lawful. It is whether continued processing remains justified. A notice that was properly issued in 2018 may no longer meet the RPD's data-accuracy requirements in 2025 if the underlying proceedings have stalled, the requesting state has failed to confirm the notice, or the basis for the allegation has materially changed.

In our practice, we see two distinct failure modes. First, a notice that was renewed or confirmed by the requesting National Central Bureau without any substantive review of whether the conditions for processing still exist. Second, a notice where no confirmation was sought at all – where the data has simply sat in INTERPOL's systems beyond a proportionate period, unremarked and unchallenged.

The RPD's data-accuracy requirements apply at every stage of processing, not only at the point of initial submission. That principle is the foundation of this ground.

When does the retention and review ground arise?

The ground arises when the continued processing of data about an individual can no longer be justified against the RPD's conditions for lawful processing. Several concrete situations give rise to it.

The most common is age without progress. Where a notice has been outstanding for a significant period and the requesting state has not demonstrated any real movement towards extradition – no formal request to the state of residence, no hearing, no updated warrant – the proportionality of continued processing becomes open to challenge. INTERPOL's rules do not set a single fixed lifespan for all notices. But the RPD's data-quality obligations require that the data remain accurate and relevant. A notice pursuing someone who cannot, as a legal matter, be surrendered to the requesting state is neither accurate in its purpose nor proportionate in its retention.

A second situation arises where the underlying criminal proceedings have concluded, been discontinued or fundamentally altered. If charges have been dropped, time-barred under the requesting state's own law, or resolved by acquittal, the legal basis for the notice dissolves. The RPD requires that data reflect current legal reality. Stale data is, by definition, data that fails the accuracy test.

Third, the ground arises where the requesting NCB has failed to conduct the periodic review that INTERPOL's rules contemplate. The RPD's retention and review conditions place an obligation on the processing party – not only on the subject of the data – to confirm that processing conditions continue to be met. Where that confirmation has not occurred, the subject has standing to raise it before the CCF.

A fourth, subtler situation: the requesting state has confirmed the notice, but the confirmation itself contains no substantive assessment of whether the data remains accurate. Confirmation in form without review in substance is a weak position when challenged.

How does this ground relate to the INTERPOL Constitution?

Retention and data quality sit alongside – and reinforce – the Constitution's own requirements. Article 2 of INTERPOL's Constitution requires that INTERPOL's activities respect human rights in the spirit of the Universal Declaration. A notice retained indefinitely, without review and with no realistic prospect of achieving its stated purpose, engages that obligation directly. Continued processing of data that no longer serves a legitimate end is not a neutral act. It is an ongoing interference with the subject's rights.

Article 3 of the Constitution bars INTERPOL from processing data linked to offences of a political, military, religious or racial character. In many of the matters where retention limits are in issue, there is also a political-character argument. The two grounds are not mutually exclusive. In our experience, they are often strongest when argued together: the notice was improper at the point of issue under Article 3, and even if that argument were rejected, it has now been held beyond any proportionate retention period under the RPD.

The relationship between the grounds matters for how the file is built. A standalone retention argument says: whatever the origin of this notice, it cannot be maintained in its current state. A combined argument says: the origin was improper and the passage of time has compounded the problem. The combined position is usually stronger, but the retention ground alone can succeed where the political-character argument is not available or is not sufficiently evidenced.

What evidence supports the ground before the CCF?

Evidence for a retention and review challenge falls into three categories.

The first is chronological documentation. Practitioners need to establish a clear timeline: when the notice was issued, when and whether it was confirmed, what steps (if any) the requesting state has taken towards actual extradition, and what the current status of any domestic proceedings is. That timeline is built from open sources, court records from the requesting state where obtainable, and any correspondence from national authorities in the state of residence or detention.

The second is legal analysis of the requesting state's procedural position. If the requesting state's own law imposes a limitation period on the underlying offence, and that period has now expired, that is a directly relevant fact for the CCF's data-accuracy assessment. The CCF does not retry the criminal case. But it does assess whether the data – including the data that the notice is designed to serve a legitimate and current enforcement purpose – remains accurate. An offence that is time-barred in the requesting state cannot support a notice that purports to seek extradition for that offence.

The third category is the absence of evidence of review. This is, in practice, a powerful element. If the requesting NCB has not provided INTERPOL with updated confirmation of the notice's basis, that absence is itself evidence that the RPD's conditions for ongoing processing have not been met. The burden of demonstrating that data meets the RPD's conditions rests ultimately on the party that submitted it.

What does not work is a bare assertion that the notice is old. Age alone is not the argument. The argument is that age, combined with the absence of progress and the absence of review, means the data no longer satisfies the conditions the RPD requires. Those elements must each be evidenced in the file submitted to the CCF.

How strong is this ground on its own?

Honestly: it varies significantly by the specific facts, and a candid assessment matters here.

A retention and data-review argument is at its strongest when it is precise and evidenced. A notice that has been outstanding for many years, where no extradition request has ever been made to the state of residence, where the underlying proceedings appear to have stalled or been abandoned, and where the requesting NCB has provided no substantive confirmation – that is a strong factual platform. The CCF's function under the RPD is to assess whether processing conditions are met. On those facts, the answer is likely that they are not.

The ground is weaker – and should be assessed honestly – where the requesting state remains actively engaged: extradition proceedings are underway, the underlying criminal case is live, and the NCB has recently confirmed the notice with substantive reasons. In that situation, a retention argument alone is unlikely to displace the notice, even if the notice is several years old.

The practical answer for most matters is combination. Retention is rarely the only ground. It is typically one layer of a file that also addresses data accuracy in the underlying allegations, the political or commercial character of the prosecution, or defects in the process by which the notice was issued. A well-built CCF file argues each available ground independently, so that if one fails, the others remain in play.

One honest limitation that we name to every client: there is no appeal against a CCF decision. If the first request is refused, a second request requires genuinely new elements. That means the quality of the first file is not a drafting preference – it is a strategic necessity. A weak first file on a retention ground can foreclose a stronger combined argument later.

Can a deletion at the CCF resolve the consequences in national systems?

This is the question that clients often reach last, but it is frequently the one that matters most in practice.

A CCF deletion removes the data from INTERPOL's systems. That matters directly: the notice ceases to appear on INTERPOL's databases, and member states receive notification that the data has been deleted. In principle, national authorities should then act on that information.

In practice, the picture is more complex. Some states maintain their own alert systems – the Schengen Information System (SIS) in Europe being the most significant – that operate independently of INTERPOL. A deletion at the CCF does not automatically translate into a deletion from SIS or from national police databases. Separate steps are often required to address those records, and the sequencing matters: the INTERPOL deletion is typically the anchor, but it is not always the end of the process.

Banking and visa consequences present a similar pattern. A bank that has blocked an account because of a Red Notice should, in principle, review that position once the notice is deleted. In our experience, some do promptly; others require specific written notification and legal correspondence. The deletion is necessary but not always sufficient on its own.

The same is true for ongoing extradition proceedings in a third country. A CCF deletion does not automatically terminate extradition proceedings that are already underway under the national law of the requested state. Those proceedings must be addressed through the courts of the state concerned, typically through allied counsel in that jurisdiction. The INTERPOL deletion strengthens the defence considerably, but it does not replace it.

This is an area where we work in the language of the file and the requesting state – understanding what the deletion achieves in each national system, and what additional steps are needed to make it durable.

What mistakes undermine a retention-based challenge?

The most common mistake is treating the retention ground as self-evident. It is not. A practitioner who submits a chronology and argues, in essence, "this notice is old and should be deleted" will find the CCF unpersuaded. The Commission is a legal body. It applies the RPD's standards. The submission must engage with those standards explicitly, map the evidence to the specific data-quality and proportionality conditions, and address the CCF's likely counter-reading: that the requesting state has confirmed the notice and that confirmation is sufficient.

A second mistake is ignoring the requesting state's procedural position entirely. The CCF will consider the requesting state's perspective. A file that does not address the state's likely arguments – that proceedings are ongoing, that the notice was recently confirmed – is a file with a gap the CCF will notice.

A third mistake is conflating a national court result with a CCF deletion. This is among the most persistent myths in this area of practice. A person may have obtained a favourable judgment in the courts of the requesting state, or in the courts of the state of residence, that is entirely consistent with the CCF refusing deletion. The CCF applies INTERPOL's rules, not national law. Conversely, a person may secure a deletion at the CCF without any national court ruling in their favour. The two processes are distinct. Success in one does not guarantee success in the other, and failure in one does not foreclose the other.

Every week the notice stands, the underlying file hardens. A requesting state that sees no challenge may treat silence as confirmation that the notice is unchallenged and appropriate. Acting promptly – and acting with a well-built file – is not merely preferable. It materially affects what the CCF has to work with.

The steps above are the general picture. Your specific matter turns on the requesting state, the age of the notice, what the requesting NCB has and has not done, and what evidence is obtainable. That is exactly what an assessment examines.

For a confidential assessment of whether the retention ground applies in your situation, and how it combines with any other available arguments, contact us at info@northlarkfirm.com or through a secure channel (Signal, Telegram or WhatsApp).

If a first CCF request on data-quality grounds produced a refusal, a second reading can identify what elements were not addressed and whether a review is viable – bearing in mind that there is no appeal, so any renewed approach requires genuinely new material.

To understand the realistic prospects of a combined grounds argument before building the file, reach us through our secure channel or write to info@northlarkfirm.com.

Related

• Red Notice removal – building and arguing the CCF file for deletion at source
• Extradition defence – acting at the hearing and coordinating with counsel in the state of detention
• Pre-emptive CCF request – filing before a notice issues, to establish the position on record

Frequently asked questions

When does this ground actually apply?

The retention ground applies when the continued processing of data about you in INTERPOL's systems can no longer be justified under the RPD's data-accuracy, data-quality and proportionality conditions. In practice, this most commonly arises where a notice has been outstanding for a significant period with no real movement towards extradition, where underlying criminal proceedings have been discontinued or time-barred, or where the requesting National Central Bureau has failed to conduct a substantive periodic review of the notice's continued basis.

What evidence supports it before the CCF?

The CCF requires a precise, evidenced submission – not a bare assertion of age. Supporting evidence typically includes a documented chronology of the notice, evidence of any limitation or discontinuation of the underlying proceedings, records showing the absence of any extradition request to the state of residence, and legal analysis demonstrating that the requesting NCB has not provided substantive confirmation of the notice's continued basis. The absence of a periodic review by the issuing bureau is itself a relevant evidential element.

How strong is this ground on its own?

Honestly, it depends on the specific facts. The ground is strongest where the notice is old, no extradition proceedings have been initiated, the underlying criminal case appears to have stalled, and the requesting bureau has provided no substantive recent confirmation. Where the requesting state remains actively engaged and proceedings are live, a retention argument alone is unlikely to succeed. In most matters, retention works best as one layer of a combined file addressing multiple grounds under the RPD and INTERPOL's Constitution.

About NORTHLARK

NORTHLARK is an independent international boutique that acts for individuals facing INTERPOL Red Notices, diffusions and related extradition proceedings before the CCF and in the courts of multiple jurisdictions. We are fully independent – with no affiliation to any firm, network or parent brand – and that independence is a deliberate feature for clients whose notice originates from states where political and commercial pressures can influence legal proceedings. We work in the language of the file and the requesting state, coordinating with allied counsel in relevant jurisdictions where local representation is required.

We act only on lawful mandates. We do not assist anyone in evading legitimate justice, and we take on a matter only where we see genuine grounds to challenge the data INTERPOL holds.

The first assessment is confidential. Our enquiry form does not require your real name, and you can reach us through a secure channel – Signal, Telegram or WhatsApp. For an honest view of whether the retention and data-review ground applies in your case, write to info@northlarkfirm.com.