Have questions? We’ve answers. If you can’t find what we are looking for, feel free to get in touch.
Regulatory Updates: Display real-time updates on regulatory changes (e.g., ESG compliance, GDPR, SEC reporting).
Document Repository:
Compliance Status Tracker:
Audit Trail:
Portfolio Overview:
Transaction History:
Version Control:
Pre-Built Templates:
Dynamic Reporting Engine:
Audit Checklist:
Third-Party Integrations:
Role-Based Access Control (RBAC):
Data Encryption:
Activity Monitoring:
Performance Metrics:
Risk Analysis:
ESG Integration:
iClerk AI Agents are designed to let professionals and companies of all sizes leverage the power and efficiency gains AI provides, to create, reason, remember, and interact with key information across all enterprise systems, through secure and extensible AI agents that connect platforms and content types. iClerk helps integrate teams and machines with secure agents that operate on private data and applications, answer queries, and automate repetitive tasks without the need to code. iClerk agents allow you to specify the context window of your chat, search, or custom retrieval operations on customer data and to take action by sharing with teams, messaging, scheduling, or generating summary output via text forms, audio, or video highlights for human interactions, or via API outputs to communicate with other software systems.
AI Agents perform three basic functions: they operate across complex sets of data to set the information context, agents perform custom Retrieval Augmented Generation (RAG) workflows on both structured and unstructured data, and they take action, to save, share, or output for humans via text, audio, or video summaries, or via API to other integrated software environments.
Capture voice, video or text in any language. Generate meta-data about the captured content:Transcribe, translate, and summarize in text & video formats. Group and role support allow you to collaborate and share with your team and to identify team and individual performance trends over time, generate custom forms, short video generation and context-based search across people, topics, and time. iClerk offers Knowledge Agents that allow you to build private, secure, knowledge agents that learn as the underlying content changes. iClerk allows you to reason across products, policies, conversations, and competitors as they change. iClerk Sales Agent allows you to hear the customer voice, focusing on what the customer said, not the other members of your team, generate short video clips of every time the customer speaks providing traceable links back to the original data source so you do not have to trust in AI generated summaries.Reduces call review times by more than 50%.
iClerk Agents help save time and money by automating work in sectors including education, healthcare, research, insurance, and across includes sales, knowledge management, compliance, and training job functions.
iClerk Agents provides a way to remember, reason and interact with all the information about people, conversations, and topics that take place across time and across platform, and to automatically create new text, voice, video, or machine output.
Example customer agents:
iClerk is a no-code, native AI platform that provides support for cloud and on-prem operations, enterprise-secure data infrastructure to keep your IP private, multi-LLM support for extensibility, proprietary speaker identification and diarization technology for cross-platform identification of people and topics over time, and the tools and integrations necessary to operate in a heterogeneous enterprise environment.
Our intellectual property provides freedom to operate with 3 granted patents, 2 pending non-provisional, and 3 pending provisional patents.
The integration of AI into operations is expensive for companies. Customizable iClerk AI Agents require no coding and help with tasks and save measurable time for a much lower cost.
iClerk Agents provide the operating environment, the guard-rails and tools required to leverage AI into existing enterprise operations with minimal cost or integration effort:
All iClerk managed content and data-at-rest, including live data, are encrypted with long-term-storage data, backups and restores. All transmitted data is encrypted via TLS. Data stored in Kubernetes pods are private with an internal network that is not accessible from outside of the Amazon Virtual PrivateCloud. All iClerk user data are segregated via Access Control Lists andPolicies defined at the individual row layer in the database. Each authenticated user is granted a limited time JSON Web Token that expires every24 hours and is required for every transaction both at the web-app layer and at the database layer. iClerk data are restricted per user access controls and policies within the database meaning that a user would be unable to obtain or reconstruct a valid JWT that has not yet expired, they would only be able to access that single account data, even if they had access directly to the database. Expired tokens will not work and there is no possibility of accessing a separate user’s data. iClerk implements essential security measures to ensure data protection and compliance with requirements of privacy legal frameworks such as the GDPR and the CPRA/CCPA: encryption techniques to secure sensitive data both in transit and at rest, access controls that grant appropriate permissions to authorized individuals while limiting access for others to help prevent unauthorized individuals from gaining access to personal data. Agblox regularly conducts security audits to assess and address any potential vulnerabilities or risks, ensuring the ongoing integrity and confidentiality of the data we handle. By combining encryption, access controls, and regular security audits, we prioritize data security and compliance, providing our users with protection of their personal information.
We maintain data privacy and security and strictly adhere to a policy of not selling or sharing data.
iClerk enforces a strict policy of not mixing private and public data. Our data management procedures ensure segregation and prevent accidental or intentional overlap of these datasets.
iClerk leverages a combination of proprietary, open-source, and private AI models, all of which adhere to regulatory requirements.
Our proprietary models are used to automatically identify and differentiate speakers in audio recordings with a high degree of accuracy. These models are compliant with a number of security standards, including HIPAA, GDPR, and NIST SP 800-53.
OpenAI’s Whisper, implemented as a self-hosted model, is used for translation, transcription, and text generation.
iClerk implements OpenAI’s TL;DR, a summarization model, to summarize the origin text into small, medium, and large summaries and is accessible through the interface or API. The Whisper and TL;DR models are compliant with security standards including HIPAA, GDPR, and NIST SP 800-53 and are subject to a number of security controls, including access control, auditing, and encryption.
OpenAI's GPT3.5 or Meta’s Llama2 model is used for content tagging and topic determination.
OpenAI's GPT3.5 or Meta’s Llama2 model is used for sentiment analysis and trend identification.
The iClerk system adapts and learns from your personal information over time. We consistently monitor developments and changes in regulatory policies and legislative frameworks that affect both privacy and artificial intelligence across multiple relevant jurisdictions. Our objective is to stay ahead of any issues that may impact our data management procedures, or our processing of customer data, implementation, integration of AI models and algorithms, or security surrounding all of these aspects of our business.
JWTs are created when a user successfully authenticates in the iClerk SaaS Platform. The users can authenticate via username/password combination or via third-party providers such as Google or Microsoft. Once a user has authenticated, they are provided with a JWT that identifies who they are within the system. All secured web-application calls require a JWT to be validated before any read/write transaction can occur. iClerk enforces this by putting into place a security pipeline that requires authorization before any data transfers can occur. Additionally, the JWT is required for any call to the database.
Are in place and require a valid non-expired JWT to authenticate the user. If the JWT is expired or if the user does not have valid access to the data requested no data will be transferred. The JTWs are stored in the database in a private security schema and access is controlled by Row Level Security.
Restrict which users can modify or access table rows and this feature is especially useful in a multi-tenant cluster as it allows individual tenants to have full SQL access to the database restricting private information from other tenants.
Are implemented and maintained in the software development lifecycle. Changes and additions are accepted and assigned by a security officer and implemented by a sanctioned DevOps team where, once changes pass code review, a regression test is done in an isolated environment to ensure that the policies are effective. Only when the regression testing has completed and passed is the change pushed to our production environment.
iClerk implements Let’s Encrypt to digitally sign and validate end-user communication with the iClerk Platform where all communication is encrypted using TLS. iClerk is HTTPS by default and it is not possible to access the iClerk platform via unencrypted HTTP access.
iClerk uses Amazon AWS’s logically isolated Virtual Private Cloud (VPC). Only the iClerk web server is accessible from the greater internet. This is protected by AWS Firewalls and Nginx ingress controller. iClerk services are only available from within theVPC and traffic between services is encrypted via TLS. Each Kubernetes pod is logically isolated and traffic can flow between nodes in the pod internally.This traffic cannot be accessed from anywhere outside of the pod.
iClerk uses Amazon AWS RDS instances for database technology. Amazon RDS encrypted DB instances use the industry standard AES-256 encryption algorithm to encrypt customer data on the server that hosts that customer’s Amazon RDS DB instances. After customer data are encrypted, Amazon RDS handles authentication of access and decryption of customer data transparently with a minimal impact on performance. Customers do not need to modify existing database client applications to use encryption.Amazon RDS encrypted database instances provide an additional layer of data protection by securing your data from unauthorized access to the underlying storage.
(S3), all Amazon S3buckets have encryption configured by default and objects are automatically encrypted using server-side encryption and Amazon S3 managed keys (SSE-S3).Encryption settings apply to all objects in a customer’s Amazon S3 buckets, database access to S3 buckets and folders is controlled by ACL controls andJWTs in the same manner. No data can be accessed and unencrypted without a valid non-expired JSON Web Token. An end user will not have direct access to their S3 buckets or folders. For each front-end web application request, iClerk creates a publicly available URL specifically for the JWT that has been authorized to access the data. This URL has an expiry time of 10 minutes and is recreated upon every page load.
iClerk designs it sprocesses and procedures related to the system to meet its objectives. Those objectives are based on the service commitments that iClerk makes to customer entities, the laws and regulations that govern its services, and the financial, operational, and compliance requirements that iClerk has established. The system services are subject to the security commitments established internally for its services. Commitments to user entities are documented and communicated in service-level agreements (SLAs) and other customer agreements and in the description of the service offering provided online. Security commitments include, but are not limited to, the following: Platform features and configuration settings designed to authorize user access while restricting unauthorized users from accessing information not needed for their role; Use of security monitoring to prevent and identify potential security attacks from users outside the boundaries of the system; Continuous vulnerability scans over the system and network, and annual penetration tests over the production environment; Operational procedures for managing security incidents and breaches, including notification procedures. Such requirements are communicated in iClerk's system policies and procedures, system design documentation, and contracts with customers. Information security policies define an organization-wide approach to how systems and data are protected.
