A Schengen Information System (SIS) alert can do something that surprises many people who encounter one: it can travel further than the notice it accompanies, and it can outlast the notice if the underlying data is never corrected at source. This matter, which concluded in spring 2025, illustrates both problems – and the way a carefully sequenced CCF process resolved them.
A Schengen alert addressed after CCF action describes a situation in which an INTERPOL-linked Red Notice had already generated a SIS entry, restricting the client's movement across the Schengen area. The Red Notice itself was not an arrest warrant and not a judicial decision. By challenging the underlying INTERPOL data through the CCF – INTERPOL's independent review body – the conditions that sustained the Schengen alert were removed. The data correction at INTERPOL propagated, in time, to the SIS entry.
What follows is the situation as we received it, the strategy we applied, and the outcome. All identifying details have been removed.
The situation
The client was a professional based in Western Europe, originally from a CIS jurisdiction. A criminal investigation in the country of origin had led to a Red Notice. That Notice had, in turn, triggered a SIS II alert. The practical effect was immediate: the client was stopped on one occasion at an internal Schengen border and questioned for several hours before being released. Banking relationships had already been affected. Travel within the Schengen area had become unpredictable and, in the client's own words, "functionally impossible."
Every week the notice stood, the file hardened. The requesting state was adding supplementary material to the underlying case. The client had not previously sought specialist INTERPOL counsel. A brief enquiry to the requesting state's authorities had been met with silence.
When we received the instructions, the red threads were clear. The prosecution in the country of origin bore the hallmarks of a commercially motivated dispute that had been routed through the criminal justice system. There was a documented civil proceeding running in parallel – involving the same counterparty, the same facts, and the same alleged loss. The data held by INTERPOL included characterisations of the alleged offence that did not correspond to the publicly available procedural record.
The strategy we applied
The first step was an access request to the CCF under the RPD's access provisions – to establish precisely what data INTERPOL was processing, in what form, and on what basis. Under the applicable rules, an access request is to be answered within four months of admissibility. The response confirmed the notice was live and provided enough detail to calibrate the deletion request that followed.
The deletion file was built on two tracks. The first was data accuracy: the RPD's data-quality requirements impose a positive obligation on INTERPOL to process only information that is accurate, up to date, and consistent with the procedural record of the requesting state. The material we assembled showed discrepancies between the official record and INTERPOL's characterisation of the offence. That alone was sufficient to raise a well-founded data-accuracy challenge.
The second track engaged INTERPOL's Constitution directly. Article 3 bars INTERPOL from processing data connected to offences of a political, military, religious or racial character. Article 2 requires respect for human rights, in the spirit of the Universal Declaration. The parallel civil litigation – documented, current, and directly linked to the same facts – was central evidence of the political and commercial character of the proceedings. We did not merely assert Article 3; we evidenced it through the procedural history of both the civil and criminal files.
In an anonymised matter of this type, sequencing is everything. A weak first file cannot be appealed. There is no appeal against a CCF decision. A review requires new elements. We submitted once, in full, and built the argument to withstand a refusal rather than to invite a second attempt.
In a parallel matter from the same period (a MENA-origin notice, spring 2025), we used a comparable data-accuracy argument to obtain deletion where the requesting state's procedural record contained a material inconsistency with the Notice itself. The structure of that file informed our approach here.
The outcome
The CCF found in the client's favour. The Red Notice was deleted from INTERPOL's databases. Deletion at source is the correct point of intervention: once the data is removed from INTERPOL's systems, the legal basis for the associated SIS alert was undermined. The client's national data protection authority was notified; the SIS entry was subsequently addressed through the relevant national channel.
Travel was restored. The banking position, which had been suspended pending the notice status, was re-evidenced to the relevant institution after the deletion was confirmed. The resolution was not immediate – CCF proceedings take the time they take – but the outcome was durable because it addressed the data at its origin rather than managing symptoms.
One honest note: the SIS correction required a second procedural step at national level. CCF deletion does not automatically cascade to SIS in real time. Clients facing both a notice and a SIS alert need to plan for that secondary stage from the outset.
Related
- Red Notice Removal – build the CCF file and press for deletion at source
- Extradition Defence – act at the first hearing and argue human-rights defences
- Data Inaccuracy – how data-quality grounds under the RPD are argued and evidenced
Frequently asked questions
What are my options from here?
The primary route is a deletion request to the CCF, supported by a file that addresses both the RPD's data-accuracy requirements and, where the facts support it, the grounds in INTERPOL's Constitution. An access request should normally precede the deletion request: it establishes what INTERPOL holds and allows the argument to be calibrated precisely. If a SIS alert is also live, a parallel national-channel challenge will be needed alongside the CCF process.
How long might this take?
A deletion request is to be decided within nine months of admissibility under the applicable rules. In practice, the full sequence – access request, review of the response, and the deletion submission itself – typically runs longer. An access request should receive a response within four months of admissibility. Complexity of the underlying file, the volume of material submitted, and the CCF's own workload all influence the actual duration. We give clients a realistic range at the outset, not a fixed date.
What decides the outcome?
The quality of the first file, above all. There is no appeal against a CCF decision; a review requires genuinely new elements. The cases that succeed are those where the political or commercial character of the prosecution is evidenced rather than asserted, where data discrepancies are documented precisely, and where the submission engages INTERPOL's own rules – the RPD's data-quality requirements and, where applicable, Articles 2 and 3 of the Constitution – rather than making general human-rights arguments.
About NORTHLARK
NORTHLARK is an independent international boutique that acts before the CCF and in related extradition proceedings. We are fully independent – no network affiliations, no parent firms – which is a deliberate feature for clients whose notice originates from jurisdictions where those affiliations would create risk. We act only on lawful mandates. We do not help anyone evade legitimate justice, and we take on a matter only where we see genuine grounds.
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. To discuss whether the facts of your situation disclose real grounds, write to info@northlarkfirm.com or contact us through our secure channel.
Facing an unjustified Red Notice?
Free initial assessment. Challenging Interpol Red Notices and extradition defence.
Request an assessment