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
  • No Warranty
  • Ownership
  • Compliance with Law
  • API Limitations
  • API Key Change Notice
  • Non-Exclusivity
  • Trademark & Brand Usage
  • Date of Last Update

Was this helpful?

  1. Legal
  2. Terms & Policies

Screena API Terms of Service

First of all, thanks again for using Screena’s API to build an application!

By accessing or using our API, you are agreeing to the terms below.

If there is a conflict between these terms and additional terms applicable to the Screena API, the additional terms will control for that conflict.

Collectively, we refer to the terms below, any additional terms, terms within the accompanying API documentation, and any applicable policies and guidelines as the "Terms".

You agree to comply with the Terms and that the Terms control your relationship with us. So please read all the Terms carefully.

If you use the API as an interface to, or in conjunction with other Screena products or services, then the terms for those other products or services also apply.

Under the Terms, "Screena" means PANACEA INFOTECH SARL-S or its subsidiaries dba Screena unless set forth otherwise in additional terms applicable for a given API.

We may refer to "Screena" as "we", "our", or "us" in the Terms.

No Warranty

All services and content of the Screena API are provided under Screena Terms on an "as is" basis, without warranty of any kind, either expressed or implied, including, without limitation, warranties that the provided services and content are free of defects, merchantable, fit for a particular purpose or non-infringing.

The entire risk as to the quality and performance of the provided services and content is with you. In no event shall Screena be liable for any damages whatsoever arising out of or in connection with the use or performance of the services.

Should any provided services and content prove defective in any respect, you (not the initial developer, author or any other contributor) assume the cost of any necessary servicing, repair or correction.

This disclaimer of No Warranty constitutes an essential part of these Terms. No use of any services and content of Screena is authorized hereunder except under this disclaimer.

Ownership

Screena retains all rights, title and interest in and to its API, products, upgrades, documentation, and any other related documentation.

The Screena software, API or any other materials provided by Screena (including without limitation all patents, copyrights, trademarks, trade secrets and other intellectual or industrial property rights embodied in any of the foregoing) remain its exclusive property.

Screena does not acquire ownership in your API Clients, and by using our APIs, you do not acquire ownership of any rights in our APIs or the content that is accessed through our APIs.

"API Clients" refers to software applications or systems that interact with an Application Programming Interface (API) provided by a specific company or platform. An API Client is a software component or code designed to access and utilize the functionality and data exposed by an API. It acts as a bridge, enabling communication and information exchange between different software applications. The API Client is responsible for making requests to the API, providing necessary input parameters, and receiving responses or data in return.

Compliance with Law

You will comply with all applicable law, regulation, and third party rights (including without limitation laws regarding the import or export of data or software, privacy, and local laws).

You will not use the API to encourage or promote illegal activity or violation of third party rights.

You will not violate any other terms of service with Screena (or its affiliates).

You will require your end users to comply with (and not knowingly enable them to violate) applicable law, regulation, and the Terms.

API Limitations

Screena sets and enforces limits on your use of the API (e.g. limiting the number of API requests that you may make or the number of users you may serve), in our sole discretion.

You agree to, and will not attempt to circumvent, such limitations documented with each API.

If you would like to use any API beyond these limits, you must obtain Screena's express consent (and Screena may decline such request or condition acceptance on your agreement to additional terms and/or charges for that use).

API Key Change Notice

Any and all API key changes must be verified and validated before being put into production usage. Failure to do so may result in errors, inaccuracies or other issues that could impact the proper functioning of the system. Therefore, we strongly recommend that you carefully review and test the application after any API key changes before implementing them in a production environment.

By using the system and making any API key changes, you acknowledge and agree to this notice and accept full responsibility for any consequences that may result from such changes.

Non-Exclusivity

The Terms are non-exclusive.

You acknowledge that Screena may develop products or services that may compete with the API Clients or any other products or services.

Trademark & Brand Usage

If you plan to utilize Screena’s trademark or branding in the visual design of your application or website, please adhere to Screena’s Trademark & Brand guidelines.

Please take note of the following:

"Screena" cannot be the first word in your application’s name. It can be used in the name of your app, though. For instance "x for Screena" or "x with Screena", etc. This makes it clear that your application is created by you and not by Screena.

You must clearly state that your application is "not created by, affiliated with, or supported by Screena" in your application description.

By using the Screena marks you agree to properly follow the above Trademark & Brand guidelines as well as our Terms of Service.

Date of Last Update

This agreement was last updated on May 11th, 2023.

PreviousWebsite Terms of UseNextScreena API Data Policy

Last updated 2 years ago

Was this helpful?

To seek such approval, contact the relevant for information.

Please be aware that changes to API keys may impact the features provided by the system, including but not only the feature.

For further information, please contact the .

Screena API team
Delta Screening
Screena team