Sigeel screens names against sanctions lists published by public authorities. Each list is periodically refreshed from its official publisher. The lists below are the complete set of data sources Sigeel currently uses.
sanctionslistservice.ofac.treas.gov
Published by the U.S. Department of the Treasury's Office of Foreign Assets Control. As a work of the U.S. federal government, this list is in the public domain and may be used and redistributed without restriction.
Public domain (17 U.S.C. § 105)
ofsistorage.blob.core.windows.net
Published by HM Treasury's Office of Financial Sanctions Implementation. Contains public sector information licensed under the Open Government Licence v3.0.
Open Government Licence v3.0
international.gc.ca
Published by Global Affairs Canada. Licensed under the Open Government Licence – Canada.
Open Government Licence – Canada
dfat.gov.au
Published by the Australian Government Department of Foreign Affairs and Trade. Licensed under Creative Commons Attribution 4.0 International.
CC BY 4.0
webgate.ec.europa.eu
Published by the European Commission's Directorate-General for Financial Stability, Financial Services and Capital Markets Union (DG FISMA). Reused under the Commission's Creative Commons Attribution 4.0 International licence.
CC BY 4.0
Sigeel contains public sector information made available under the licences listed above. Attribution is provided in accordance with those licences. Nothing in this attribution implies endorsement by any government, regulator, or public authority of Sigeel, its products, or its services.
Where a licence requires attribution, the required form is the source name as shown on this page. Customers who redistribute Sigeel's responses should retain the list.source field, which identifies the originating list for each match.
Sigeel does not currently include the United Nations Security Council Consolidated List or the Swiss SECO sanctions list. Both are distributed under terms that restrict commercial redistribution without explicit permission or a paid licence. If your compliance obligations require screening against either list, contact us — we can discuss whether that coverage is feasible.
Every /screen response includes metadata about the exact list build that was checked, in the list field: the source name, a Unix timestamp of when the local index was built, and the total entity count at that build. Combined with the Ed25519 signature, this lets you prove months later which version of which list was screened against, and that the response was not altered.
For a data-provenance attestation letter suitable for vendor due diligence, contact legal@sigeel.com.