Help
  • FAQ
    • Introduction
    • Name Matching
      • Does Screena provide rules-based and/or fuzzy matching capabilities?
      • Does Screena have any machine learning or AI capabilities?
      • What are name cultures and how does Screena handle them?
      • How does Screena handle different scripts, diacritics, and transliteration?
      • How does Screena handle common names?
      • How does Screena handle inaccurate data?
      • What methods does Screena use to reduce false positives?
      • What is the percentage of false positives reduced with the methods used by Screena?
      • How does whitelisting work?
      • What differentiates pairwise name-matching between Screena One and Screena Plus?
      • How does secondary attributes-matching work?
      • Can Screena match beyond names and allow firms to blacklist identifiers or locations?
      • What is the difference between 'matchingNames' in screening responses and 'names' in 'targetData'?
    • Watchlists
      • Which lists are available out of the box?
      • Is Screena watchlist agnostic?
      • How is watchlist data loaded into Screena?
      • How frequently is data updated within Screena?
      • Do you provide proprietary watchlist data?
      • What sort of data (e.g., names, known aliases, known associates, etc) is used for name matching?
      • Does Screena support adverse media screening?
      • Do you provide information about whether a list entry is active, inactive or deceased?
      • Do you provide a URL link to the reference article for adverse media screening?
      • How is the data of third-party list providers conveyed to your name-screening API response?
      • Can I screen against specific sanction programs within a watchlist and not all of them?
      • What is the difference between the USA and the OFAC lists?
      • Is there a template to upload private lists into Screena?
      • How many records can I upload to my private watchlist?
      • Can I upload more than one private list?
      • How can I update my private list?
      • Why can't I find Politically Exposed Persons (PEPs) at regional level when I use Instant Search?
      • How do you monitor that watchlists are up to date and correctly uploaded to your platform?
    • Performance
      • Does Screena provide real-time screening capabilities?
      • What is the speed of screening?
      • How do you ensure horizontal and vertical scalability?
      • Does Screena support batch processing?
      • Do you have performance benchmarks?
    • Integration
      • Can clients configure the solution themselves or would they need support from you?
      • Do you partner with any other solutions/vendors?
      • Do you provide technology or solutions to support alert remediation investigation?
      • Can Screena be integrated within third-party platforms and systems?
      • How do you handle changes to your API data model?
    • Personalization
      • What options do I have to optimize my screening results?
      • What screening parameters can I configure to meet my risk appetite?
      • To which extent are the screening thresholds adjustable?
      • What is the difference between the algorithm value "ignore" and the option "nullMatch" set to false?
    • Hosting & Deployment
      • How can Screena be deployed?
      • How do you set resources per customer?
      • How do you segregate the data and configuration between customers?
      • How often does Screena release new versions?
      • How often are models re-trained and what does roll out to clients look like?
      • How do you handle High Availability?
      • What AWS regions do you operate as of now?
      • What operating systems and/or execution platforms are supported?
      • How do you provide bug fixes and distribution across clients?
    • Pricing & Support
      • What is your pricing model?
      • Can you clarify the difference between Screena One, Plus and Firm?
      • What additional modules are not included in your core product pricing package?
      • Do you charge for professional services and/or after-sales services?
      • Do you offer bespoke solutions to clients?
      • Can I test your solution for free?
      • What happens at the end of my trial period?
      • What are my payment options - credit card and/or invoicing?
      • What are your standard support & maintenance agreements?
      • Are there integration costs to work with Commercial-Off-The-Shelve (COTS) lists?
    • Security & Audit
      • Does Screena have security certifications?
      • What security measures do you apply?
      • How do you adhere to GDPR?
      • Does Screena provide versioning capabilities?
    • Tech Stack
      • What is your tech stack?
      • What programming language(s) is Screena written in?
      • What source and version control systems are used to manage development?
      • What testing tools do you use?
  • How To
    • Install Screena Portal
      • Preparing your system
      • Installing Screena Portal backend
      • Launching Screena Portal backend
      • Installing the web server
      • Configuring Screena Portal
    • Start Screena Portal
      • Starting PostgreSQL database
      • Starting Apache HTTP server
      • Starting Screena application
        • Start command
        • Restart command
        • Stop command
  • Release Notes
    • 2.1.17
    • 2.1.16
    • 2.1.15
    • 2.1.14
    • 2.1.13
    • 2.1.12
  • Legal
    • Terms & Policies
      • Website Terms of Use
      • Screena API Terms of Service
      • Screena API Data Policy
    • Privacy & Security
Powered by GitBook
On this page
  • Data we store and process
  • Data we only process
  • Legitimate interests
  • Recipients of data
  • Watchlists data
  • Date of Last Update

Was this helpful?

  1. Legal
  2. Terms & Policies

Screena API Data Policy

Data we store and process

Category
Definition
Retention Policy

Sanctions, Law Enforcement, and Probity

Personal information publicly available relating to sanctions, wanted individuals, and the prevention/detection of illegal acts.

We retain the information in our databases as long as the information is public.

Politically Exposed Persons

Personal information publicly available relating to individuals in prominent public positions.

We retain the information in our databases as long as the information is public.

Third-Party Risk Intelligence

Personal information collected and collated from reliable and reputable sources by our clients and/or specialist third-party companies to identify and manage heightened-risk individuals and entities.

We retain the information in our databases as long as we have a valid contract in place with these clients and/or third-party companies.

Data we only process

We don't store the data of individuals whose names need to be matched against Sanctions, Law Enforcement, Probity, Politically Exposed Persons, and Third-Party Risk Intelligence.

The names are processed and are not kept in our databases.

Legitimate interests

Our existing and prospective clients have legitimate interests in matching personal data to comply with legal obligations with regards to:

  • sanctions, anti-money laundering, know-your-customer, and counter-terrorist financing;

  • law enforcement and border control; and

  • protection of citizens, financial system, and public transportation.

We also pursue our own legitimate interests in developing and improving products and services to serve this market.

Recipients of data

  • Other data controllers, on whose behalf we act as processors

  • Partners who are reselling our services to data controllers, on whose behalf we act as subprocessor

  • PANACEA INFOTECH SARL-S group employees

  • Our hosting and cloud storage providers

  • Third-parties we use to audit and/or monitor the accuracy and performance of our systems

Watchlists data

Please be advised that any watchlists imported into our engine are imported "as is," without modification, alteration, or attempts to improve the quality of the original data. This means that any decisions related to anti-money laundering/counter-terrorist financing and sanctions screening are based solely on sources that are as close as possible to the original data. Please note that the only adaptation performed on the data is an inevitable adaptation to our data model.

Additionally, please note that the timely provision of the data depends on the availability of the websites and other data sources that we use to obtain the information. While we check these websites automatically and regularly, we cannot be held responsible for technical issues that are independent from us and that may prevent us from accessing the data in a timely manner.

As a result, we cannot be held liable for any errors, inaccuracies, or omissions in the original data, and we make no representations or warranties regarding the accuracy or completeness of such data. It is the responsibility of the user to verify the accuracy of the data before making any decisions based on it.

By using our services, you acknowledge and agree that we shall not be held liable for any direct, indirect, incidental, special, or consequential damages resulting from the use of our services, or for any loss or damage of any kind incurred as a result of the use of any information obtained through our services. You further acknowledge and agree that you use our services at your own risk and that we shall not be held liable for any actions taken or not taken based on the information provided through our services.

Date of Last Update

This Data Policy was last updated on May 12th, 2023.

PreviousScreena API Terms of ServiceNextPrivacy & Security

Last updated 1 year ago

Was this helpful?