Security and hosting

Built in Guernsey. Your client data stays here.

Flarion is written and run in St Peter Port by Islands AI. Everything on this page describes the product as it runs today.

Request the Due Diligence Pack Book a demo

HostingIslands AI infrastructure in Guernsey, moving into a Tier III data centre on the island.

EncryptionTLS on every connection. Application data and its backups encrypted at rest.

BackupsEncrypted nightly, held off the production machine, restore tested.

AccessRoles enforced on the server for every request, never only in the browser.

AuditEvery view of a file, a document or a record logged with who, when and where.

Sub-processorsNine categories below, each with what it receives and for what purpose.

The facts

Where it runs, who can see what, and how long it is kept.

HostingProduction runs on Islands AI's own infrastructure in Guernsey, with encrypted nightly backups held elsewhere in the islands. A move into a Tier III data centre on the island is under way.

RegulationGFSC Handbook mapped, chapter by chapter. JFSC in progress. Evidence built for an inspection, not a sales deck.

IdentityDocument authenticity, liveness and face match by our identity verification provider. Images held in your firm's own store, never on a shared provider account.

ScreeningA consolidated sanctions and PEP dataset: UN, EU, UK, OFAC and 200 more sources. Bring your own screening subscription if you have one.

AccessRoles enforced server side, decisions recorded with reason, reviewer and time, append only, every view logged and watermarked document views.

CompanyIslands AI Ltd, 2 Market Street, St Peter Port. Guernsey company 74458.

In more detail

The controls behind those six answers.

EncryptionIn transit, every connection is TLS. At rest, the application data and its backups are encrypted.

BackupsEncrypted nightly backups held off the production machine, in the islands. Restore is tested, not assumed, and each night's backup writes a heartbeat the firm can see.

Screening decisionsEvery decision on a screening hit carries the reviewer, the reason and the time, and is append only: a decision is never edited, it is superseded by a later one.

ViewsEvery view of a client file, a document and a record is logged with who, when, from which device and where. Document views inside an inspection link are watermarked, visibly and invisibly, so a leaked page can be traced to the link it came from.

Identity imagesThe document and face images from a verification are captured into the firm's own store in Guernsey at decision time and served only inside Flarion, with every view logged.

RetentionThe provider's copy of identity data is erased on a schedule against the retention limit the firm sets (twelve months if it sets none). The firm's own record that a check was run, and what it returned, is kept for the six years Fiduciary Rule 2.6.4(1) requires.

Data subject rightsThe firm is the controller; Flarion is its processor. Access, correction, restriction and erasure requests go to the firm and Flarion carries them out on its instruction. One erasure path serves the MLRO's button and the nightly agent, so the answer does not depend on who pressed it.

IncidentsSecurity incidents and vulnerability reports: [email protected], or 07781 146227. A founder answers.

Sub-processors

Who else touches the data, and what each receives.

Each acts on Flarion's instructions, for the purpose named and no other, and none of it is used to train a model. These are the categories; the companies behind them are named where a vendor review needs them.

Category	What it is for and what it receives
Identity verification provider	Document authenticity, liveness and face match. Receives the document images and face capture for the check, and the name and date of birth to compare them against.
Sanctions and PEP data provider	List matching against the consolidated dataset. Receives the name and, where held, the date of birth and nationality of the person or entity screened.
Adverse media search	Web search about the person or entity screened. Receives the name searched; the results come back for a person at the firm to judge.
Document reading and drafting assistance	Reads an uploaded document into the record and drafts a periodic review memo from what changed on the file. Receives the document, or the facts already on the file, for that one task. Reviewed by a person before filing, and never used to train a model.
Meeting booking	The calendar on the demo page of this website, which loads only when a visitor asks for it. Receives the name, email address and any note of someone booking a call. It touches no client data and is not part of the product.
Email delivery	Invitations, reminders and digests. Receives the recipient's address and the message. No documents are ever attached.
Network and content delivery	Carries traffic between the browser and Flarion. Handles everything in transit, including the visitor's IP address; stores no client data.
Hosting in Guernsey	Runs the application and its database, which is where client data is stored. On the island.
IP location lookup	Performed on our own server, against databases held on it. Receives nothing: no address leaves the machine.

The named list of sub-processors, with what each receives and where it processes, is in the Due Diligence Pack and our data processing agreement.

Evidence, not assertions

Read the controls

Everything on this page describes how the product behaves today, and every line of it is something you can put to us in your own review. Where a control is not built, the page says so rather than implying it.

Regulation

GFSC Handbook mapped

Chapter by chapter, with JFSC in progress. Regulators do not approve software; the evidence Flarion keeps is built for an inspection, not a sales deck.

Vendor review

The Due Diligence Pack

Company and ownership details, this hosting overview, the data flow including AI processing, the sub-processor list, data processing terms and a continuity summary. Request it and take Flarion through your own process.

FAQ

Questions about security and hosting

Is Flarion approved by the GFSC or JFSC?

No software is. Regulators do not approve or endorse vendors, and a vendor implying otherwise should worry you. Flarion is built around the GFSC Handbook and your own policies and procedures determine your compliance. The Due Diligence Pack supports your internal assessment and any notification your process requires.

Where is our data held?

In Guernsey. The Hosting row above gives the arrangement in full, and it is the whole of it: client documents, identity images and screening decisions are all held on the island. The Due Diligence Pack sets it out in the form a vendor review needs.

How does the AI handle our client data?

Two tasks use it: reading an uploaded document into the record, and drafting a periodic review memo from what changed on the file. Each sends only what that task needs to a document reading and drafting service, and a person at the firm checks the result before it is filed. Nothing is used to train a model. The sub-processor table above says what is sent.

What assurance material can we have for our vendor review?

The Due Diligence Pack: company and ownership, the hosting and security overview, the data flows including every use of AI, the sub-processor list with what each receives, our processing terms and a continuity summary. Send your own questionnaire with the request and we will complete it in your format.

Can we run Flarion on our own hardware?

Not today. There is one production environment, in Guernsey, run by Islands AI. A firm that needs its own deployment should talk to us about it rather than assume it: it is a conversation, not a switch.

Run your vendor review on us.

Bring your security questionnaire to the demo. The answers are the ones on this page.

Book a demo