Newsletter publications. Read the latest news.

Cellosign tools of Notifications & Reminders

In today’s fast-paced world, it’s easy to forget important tasks. This is where Cellosign tools of notifications and reminders come in handy. Messages that are sent to the user to remind them of an upcoming task, are a great way to keep users informed and engaged, and can help to increase customer satisfaction and loyalty.

Notifications and reminders can be used in a variety of situations, They can be sent via email, text message, or through the app for a specific or multiple customers. The key is to send them at the right time, and in the right way, to maximize their effectiveness.

One of the primary benefits of Cellosign notifications and reminders tools is that they help to reduce the number of missed deadlines. By sending a timely reminder, you can ensure that your customers pay their bills on time or complete other important tasks. This can help to increase customer satisfaction, as customers are more likely to be happy with a service that is reliable and efficient.

Another benefit of notifications and reminders is that they can be used to encourage customers to take action. For example, if you’re trying to get customers to complete a business process, such as filling out a An accession document or Purchase of services, you can send a reminder that includes a call to action. This can help to motivate customers to complete the task, and can increase your response rates.

When sending a reminder to encourage customers to complete a business process, it’s important to be clear and concise. Your message should include a clear call to action, such as “Please fill out the attached form by the end of the week”. You should also provide any necessary instructions or links to make it as easy as possible for the customer to complete the task.

In addition, it’s also important to be friendly and engaging in your reminder message. Use a conversational tone, and try to connect with your customer on a personal level. For example, you might start your message by saying “Hi David, we just wanted to remind you to fill out our survey”. This can help to create a positive impression, and can encourage the customer to take action.

In summary, Cellsign notifications and reminders tools can help you achieve an effective way to keep customers engaged and informed. They can be used in a variety of situations, and can help to increase customer satisfaction and loyalty. When sending a reminder to encourage customers to complete a business process, be clear, concise, and friendly, and include a clear call to action. By following these guidelines, you can increase your response rates and ensure that your customers stay engaged with your business.

Hello and welcome, we are happy to introduce you with Cellosign, First let’s get the basics.

What is Cellosign?

Cellosign is a data collection application which can help you easily and securely collect data in shape of forms. From the end client point of view this is as simple as form where pieces of data are injected into, validated and submitted. Cellosign is able to collect and validate data in any conceivable method, as simple as make sure that ID number is correct or with complex cases validating data with remote application to ensure data integrity.

But wait there’s so much more..

With Cellosign you will be able to easily configure a complete journey that involves multiple recipients along the way. For example a journey that starts with a remote-client, continue to back office for further inspections can be automated with simple as drag and drop and clicks.

Cellosign is easily integrated with 3rd party applications through APIs and Application connectors to GET, UPDATE, CREATE or DELETE data records in a remote source.

Where do I go from here?

We strongly advise you to read the documentation within the Getting started guide, it includes important information regards getting support, best practices that can get you up to speed with no hassle. Next, for your convenience, our documentation is organized by User Application components, so just pick up the documentation according to your role and your tasks.

Security first

Regardless if you are using Cellosign builtin login or your organization Single Sign On application, keep your password safe:

1. Do not use passwords or tokens that were not granted to you. This is strictly prohibited
2. Do not leave notes with password on your desk
3. Keep your password easy to remember and hard to guess
4. If you have a slight suspicious that something is wrong, logout immediately, report your manager and Cellosign support for immediate response

Testing new business processes

It is recommended that new or changes to existing business processes will be carried out at pre-production environment rather than production. This will help you to develop the process in a secured and controlled environment with no client access and no disruption to production environment.

Every type of business process and it’s related meta data can be easily exported from pre-production and uploaded to production when testes are completed.

New releases are distributed every other month in according to yearly plan that takes into account holidays and peek times such as end of Quarters and end of year.

On Cellosign cloud application typically new releases are distributed to production occurs at Thursday night. There are also reserved time slots for distribution for on premise clients.

Please make sure to read full cycle practice, schedule and change logs in this documentation branch.

Cellosign customers have the option to contact Cellosign support by submitting a ticket using our web form.

Important: in case of critical production issues open a ticket and contact your account manager / support by phone.

What kind of issues can be submitted:

1. General Support issues.
2. Reporting a bug.
3. New request or CR.

Note: in our FAQs section you can find detailed information about common issues.

There are several options to submit a ticket.

In case you can login to Cellosign application the options are:

1. From “Processes” screen (recommended).
2. From main application menu.

In case you cannot login, contact Cellosign support from the web site.

See below a detailed explanation of each option.

---

Contact Cellosign support from “Processes” window

---

1. Login the Cellosign application.
2. Navigate to the “Processes” window.
3. Select the transaction from the list and press “Show Transaction Details” (+).
4. Click “Service call” button. You will be redirected to “Request for support and reporting service” form.
5. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
6. The ticket will be opened automatically with all the attached to the form information.
7. You will receive an email with the ticket number and all the details to the email address filled in the form.
8. To update the ticket or add an additional information click the link in the received email.
9. You will be redirected to the ticket details in the support site.
10. If, for any reason, you have lost access to your Cellosign account, you can still submit a support ticket from the web site (see below).

For more information about “Processes” window read here.

---

Contact Cellosign support from the application

---

1. Login the Cellosign application.
2. Click “Service call” button at the left bottom corner.
3. You will be redirected to “Request for support and reporting service” form.
4. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
5. The ticket will be opened automatically with all the attached to the form information.
6. You will receive an email with the ticket number and all the details to the email address filled in the form.
7. To update the ticket or add an additional information click the link in the received email.
8. You will be redirected to the ticket details in the support site.
9. If, for any reason, you have lost access to your Cellosign account, you can still submit a support ticket from the web site (see below).

---

Contact Cellosign support from the web site

---

1. Navigate to Cellosign site.
2. Click “Support” button at the top menu at the right.
3. You will be redirected to “Request for support and reporting service” form.
4. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
5. The ticket will be opened automatically with all the attached to the form information.
6. You will receive an email with the ticket number and all the details to the email address filled in the form.
7. To update the ticket or add an additional information click the link in the received email.
8. You will be redirected to the ticket details in the support site.

For detailed information about “Privacy statement” read here.

1. Connect to the representative interface page using the URL provided to you by Cellosign:

2. Enter your user name and password and click the ‘Sign In’ button.

If its the first time you are logging in , you will need to set a new password:

Enter a new password on the ‘New password’ field and again on the ‘Confirm password’ field.

Click the ‘Change Password’.

After the successful login in the header of the interface you can see the user name, where under it you can find Profile details and Logout option.

To send a form to the client from the agent’s interface, press the “Show Agent” button.

For a detailed explanation about user application read here.

To send a form to the client from the agent’s interface, press the “Show Agent” button at the top of the screen and select a form prepared for you from the list. For more information about forms templates read here.

Enter the client’s email address or mobile phone number at the top of the screen and press “Connect” button.

At this point, when the client opens the link from the phone message or the email, you can both work together on the form.

Visit Screen sharing section for more information about the screen sharing option.

When the client sends the form (after all the mandatory fields have been filled in) you will receive the signed form by email.

For additional information about how to send a form in Cellosign application read here.

Cellosign system allows sending a template to the client and creating a common interface (client and agent) for filling out a common template. The interface allows the agent to view the values ​​entered by the client and the client to view the values ​​entered by the agent in real time. Each of them (agent, client) can add values according to the editing and viewing permissions given in the template.

The screen sharing option can be implemented in two ways, through the Show Agent interface or Processes interface.

In the Show Agent interface, the option exists by default and under the following conditions:

• Agent has sent the template (a timer indicator will appear next to the target box for sending the template).

• Client opened the link sent to him (a green indicator will appear at the bottom of the screen at the agent side in real time).

If both conditions are met, you can use the screen sharing option.

For more information about Show Agent interface read here.

---

In Processes interface the option exists in the actions screen under the specific transaction.

Press “+” next to the transaction that need to share:

After it press “Show Agent” button to open the transaction from the agent side:

Note: In Processes interface users with organization manager or project manager privileges can also open a client screen by pressing “Show Client” button and view or edit the template with client permissions.

For more information about Processes window read here.

The user application is the user’s main entry point to the application.

At the far left is a navigation bar to the various pages in the system. [See below detailed explanation for each page].

Dashboard

Processes

Projects

Intergrations

Analytics

Users

Templates

Workflows

Transactions File

Data sources

---

In the header of the interface you can see:

• Show Agent button that opens the agent window for running forms.

• Project to which the user is currently connected.

• User name, where under it you can see the user profile and the logout option.
  
  For more information about Profile click here.

At the left bottom corner there is a Service call option to contact Cellosign support:

Sent	All the forms that were sent to clients in last 24 hours.
Viewed	All the forms that were viewed by clients in last 24 hours.
Waiting	All the forms that are waiting for clients in last 24 hours.
Submitted	All the forms that were viewed by clients, completed and submitted in last 24 hours.
Expired	All the forms that were not completed and expired in last 24 hours.
Failed	All the forms that were failed in last 24 hours.

Under each section it is possible to perform search, filter by user and see the details of each transaction.

What is a process on Cellosign?

A process in Cellosign is running a template to its destination and includes the filling of the form and its sending by the customer.
Running a template can be done in 5 ways:

1. Running a template by an operating system (integration)
2. Running a template by a system user
3. Running a template via an external link – from a website or portal (public)
4. With a multi-recipient process – a new process is created for each recipient in the process
5. With a multi-templates process – a new process is created on each template in the process

For every action in Cellosign there is an information line in the “processes tab”.

This screen shows all the processes performed in your projects according to a section of time, with the default when entering the screen being actions created “today”.

At the top of the screen:

• Panel for selecting a date range
• Free text search to find processes that contain certain text such as: phone number, email address or template
• A list of projects to select from in case you have more than one project
• If you have selected a project, you can also select a specific template
• An “Export” button that allows downloading all the processes selected by the searching criteria’s to an excel document

Main table

• At the table header, the column names where the first column # can be used for arranging the table by ascending or descending order.
• At the bottom of the table, the number of columns in the selected section appears, as well as a navigator that moves to the following processes.
  

Column	Description
#	A unique number of the operation in the system
Created	Date and time the process was created [time the form was sent to the client]
Project	The project which the operation is associated to
Destination	The recipient of the process: usually an email address or a phone number. Note: the destination column is sometimes empty, in cases where the action was taken from an external system such as CRM or the action was taken directly from a browser and then no active sending action was actually performed
Agent	The name of the agent who created the process. Sometimes when it comes from a computer creation [one created from CRM for example] the name of the system or a generic name will appear
Expiration	Each action created in the system has an expiration time, during which time the action will no longer be accessible to the representative and the end customer to whom the action was sent.
Deleted	Date and time when the action was deleted. An action will be deleted given three possible cases: – Expiration time has passed – Customer sent the form and copies were also sent to the representative and customer or/and was compiled into the operational systems – The agent or project manager deleted the process
Client logged in	Last date and time the customer opened the form
Submitted	Date and time when the customer submitted the form
Template	Template name
An indicator	Green indicator: everything is fine – Red indicator: error on the operation [see details further down the page]

Process details

Clicking on the green plus to the left of the process opens the process details screen and displays the process update actions:

This action will appear as long as the operation has not been deleted from the system. The buttons allow:

• Manual deletion of the process
• Open the form as client
• Open the form as agent
• Open a service call for support

Bellow them, we have five panels contains the process data, detailed below:

Document

Displays the process IDs and form processing information.

Column	Description
Client View Doc	Date and time when the form was viewed by the end client. Note: This is a different documentation than “client logged in”. The information indicates that the form has been fully opened in the client’s browser and that the form is ready for an update operation.
Doc Generated	Date and time of creating a digitally signed file.
Doc Status	The status of the doc created. ‘true’ if a doc was created. empty if not created yet.
Token	A unique identifier of the operation in the system. Used as a unique identifier for the form sent to the client.
Workflow	If the action is part of a business process that includes several actions, this content is the unique identifier of the process in which this action is included.
Recipient	The number of the recipient during the process. [if this action is part of a process].
Purge schedule	Estimated cleanup date time.Displayed if not purged yet.
Purge	Cleanup date time in actual. will be displayed only if purged

Archive

If there is a connection [integration] between Cellosign and the CRM system in the customer organization, this panel will show the details of the process archive, after the form has been sent and processed.

Column	Description
Posted	Date and time when the archive was created (the process product is sent to the core system).
Doc Number	Document number, if received as a response from the core system in exchange for a successful archive.
Archive Status	The status of the archive. ‘true’ if a doc was created. ‘false’ if failed.
Archive Failed Error	The archive error as received from the core system.

Mail to Agent & Mail to Client

If copies of signed forms are sent to the email boxes of the organization or the client, their details will appear in these panels.

Column	Description
Agent/Client Mail	Mail address of the agent/client. Note: in the template without recipients, when entering the email, a copy of the form will be automatically sent to the client after completion.
Posted	Date and time of sending.
Post Status	The status of sending. ‘true’ if a doc was sent. ‘false’ if failed. Note: this status indicates if the mail was sent from Cellosign but was not necessarily received at the mail address.
Post Failed Error	Error description, if the error failed and was reported to the Cellosign application.

Cellosign is a multi-tenant application, so it knows how to handle multiple clients (projects) in a way that produces complete separation between the various projects.

The advantage of a project is complete separation between users, templates, logs, interfaces, tokens and a separate repository for custom code.

The disadvantage of multiple projects for the client is mainly when using functionality that is not out-of-the-box because then in fact each project manages a separate code repository. Let’s take for example a case where requests from Cellosign to SMTP or SMS server must go through PROXY. In such a case, a specific code should be written for the proxy and be duplicated and maintained for each environment separately.

Moreover, the API for our interfaces include the project code in the URL, which means that the client will have to maintain several different repositories in order to communicate with the Cellosign servers.

If the main purpose of the separation is for access to templates and performed actions, you can use the functionality of teams because it allows you to associate users, templates and actions to a team.

Analytics screen allows you perform the analysis of your transactions and perform filtering by date and specific templates.

In addition it is possible to save parameters and fields in the template and perform search by specific parameters and values.

For more information about saved parameters and fields read here.

Cellosign manages three types of user’s permissions:

Permissions	Ability
Agent	A user with agent permission can: – Access the agent interface and management interface. – Send a form or initiate a process [agent interface, dashboard screen]. – View actions sent by him only.
Project manager	A user with this permission can do everything a user with agent permission can, plus: – View all the actions in the project in which he is set as a manager. – View and update the Project settings. – Create and update Integrations. – View Analytics data. – Create and update Templates. – Create and update Processes. – Create and update Users. – Perform Post Transactions from file. – Create and update Dictionaries [linked lists], Tables and Categories. – Create new dashboards with different widgets.
Organization manager	A user with this permission can do everything that a user with project manager permission can do, plus: – Create and update additional projects in the organization in which he manages. – Set up SSO integration for providing user authentication.

In Cellosign, there is the option to create users and also the option to connect to Active Directory
systems, so the login process will take place as part of the corporate identification system.

In case that Cellosign is connected to the Active Directory system in your organization, the creation
of the user will be automatic, without the need to create the user in Cellosign as well.

---

Users panel

---

This panel can be used to view and locate existing users, add new users and set permissions.

Search box filter	Allows searching by any text relevant to the user: name, email, phone number, etc
Select Project filter	Allows searching by project. Relevant if the organization has several projects
“Search” button	Allows searching after changing filters
+ Add Service	Allows adding a new service
+ Add User	Allows adding a new user
Export	Allows exporting the list of users to the external .csv file

To update a user, select a user from the list. Perform the needed changes and press “Update User” button.

---

Locking mechanism

---

In case the locking policy is “Lock”, the user’s account will be locked by the system after a number of failed retries. The policy and the number of retries are defined in the Security settings of the project, under “Account lock settings”.

In this case the user will get the following message:

The project manager will have to unlock the user by clicking the “Unblock User” button at the user’s account screen:

After the unblocking, the user will be asked to change his password upon next login:

In case the user does not remember his password, the project manager will have to provide him a temporary password, by clicking “Send Temporary Password” button at the user’s account screen.

By clicking the button, a temporary password will be sent to the user’s email defined in the account. In addition, the temporary password will be shown at the field next to the button and can be delivered to the user by the project manager using other communication tools.

In case the locking policy is “Temporary lock”, the user will get the following message after a number of failed retries. In this case, the user’s account will be locked for X minutes defined in the system and then will be able to try again.

In addition, the user can be locked by the project manager by clicking “Block User” button at the user’s account screen.

For more information about locking policies click here.

Templates panel displays the list of templates related to the project. The page is accessible for users with “Project manager” and “Organization manager” permissions.

In the header of the page there are buttons “+ Create New Template” and “Upload Template From File”.

Column	Description
Template Name	Includes the name of the template as well as categories attached to the template.
Status	– Publish: The form is published and can be sent to customers. – Edit: The form is in editing mode, has not yet been transferred to production, can’t be sent to customers.
Updated	Date and time of the last update of the template.
Updated By	The name of the user who performed the last update of the template.

You can filter templates by using “Search by template or tag” field.

BMPN engine

Drag & Drop establishment of exclusive, parallel, or dynamic business processes while integrating a round of approvals between internal and external organizational users, collecting and automatically completing data from tangential systems, creating digital forms, and driving tasks required for the business process by a representative or a core system. The process can begin from any digital point starting from the company’s portal or website of the end user (customers, suppliers, employees), web landing page, CRM, DWH, ERP systems as well as from a representative through individual or multiple sending.

Workflows panel displays the list of workflows related to the project. The page is accessible for users with “Project manager” and “Organization manager” permissions.

In the header of the page you can see buttons “+ New Workflow” and “Import From File”.

Column	Description
Name	Name of the workflow.
Created	Date and time when the workflow was created.
Updated	Date and time of the last update of the workflow.
Active	Status of the workflow, whether it is active or not.

The following options are available in the workflow screen:

• Create new workflow by pressing “+ New Workflow” button.

• Import workflow from file by pressing “Import From File” button.

• Update already existing workflow by selecting it from the list and pressing the name.

For detailed information about this section see “Post transactions from spreadsheet”.

Support and accessibility toolbar incorporated in all forms. The toolbar receives first focus when open a form link so screen readers can read through its content.

To open the menu click the hamburger icon at the top of your frame.

Accessibility features

Activate accessibility option

Transform inputs to valid accessible collection.

• Date input transformed from a date or date-time widget to manual input
• Signature pad will require upload a signature image rather then drawing the sugnature

In addition focus on input or (Tab/Shift+TAB) between fields will draw a border on the focused input

Monochrome option

This option modifying colors to monochromatic that makes to contrast accessible. It is advised to use high contrast as a default, regardless if the Monochrome option is activated or not.

Accessibility statement

Link to our accessibility statement

Assistance

Download file for print

This option, if activated, allow client to download a PDF file based on the data already propagated into the form. please consult with our support for activation of this feature.

Privacy statement

Link to our accessibility statement

About

View display form and client data. On some cases were client has an issue we will require this data

1. Release: Cellosign release
2. Token: Session ID in view
3. Browser: Client browser

Client forms is a user interface that present to a client a list of forms that needs to be filled in an organized and secured fashion. Clients receives one link against they will need to identify and authorized for access.

The interface is highly customizable and include rich function customization and looks configuration to match your brand.

Why do I need this?

Client forms is a great way to communicate with your clients, push new forms that needs to be filled, Client can see show how much time left to complete and all in a single link and one time authentication.

Setting up client forms

Login to projects page and locate “Client forms” and follow the tabs to set it up. Before modifying default colors and backgrounds make sure to read accessibility section below.

Background settings

This setting is optional. It affect the authorization pages only. It does not propagated in transactions page.

Setting	Helper
Background image	Client forms ius responsive and will adapt to any device automatically. We advise to pick an image with 4 (width):3(height) proportions, it scales better. In addition, we advise to upload an image smaller than 100 KB to expedite loading time for your client
Background image setting	There are 3 CSS settings available for your disposal, check what works best for you when device is table, mobile or desktop.
Alternative text	Make sure to enter a meaningful name that represents the image, typically it would be a “background image of <my brand>”

Color settings

Text color

Most of the texts in client forms view will pick on this color, including transactions text and hello text as can be seen in the image above.

Authentication settings

This tab includes a collection of settings to process the authentication stage and configuration of footer links

Suppress leading zeros

Client forms viewer collects all client’s transactions that share the same password, see require password for details. Occasionally the access password is a number, such as ID that has fluid representations to include or exclude leading zeros. As such when client insert the password it will not include leading zero and when the transaction is initiated from your core application it does include it. Essentially, we might end up with mismatch when client enters “7673899” as password and your DB inject “07673899”. These will never match.

This is where “Suppress leading zeros” become handy. It will suppress leading zeros to match. As such “000123” is equal to “123”.

Note: Be aware on what data to use for password authentication. Make sure that “0123” and “123” are not different entities. In

Activate OTP

We encourage you to use this option. OTP will guarantee that clients can access their transactions can do so only after we have doubled checked their identity. To apply OTP to transactions, at least one transaction that match the password will need to have an OTP associated. If there are more that one OTP address then the viewer will list the propagated OTP destinations.

Footer links

By default Cellosign displays links to Accessibility, Privacy and terms of use pages. Use the switch to turn off any of the links. Alternatively. You may override the defaults to include links of your own. Make sure to add valid markup and texts. i.e.:

1. Markup to open external web address: “https://yourdomain.com”
2. To pop up phone app. “tel:0500001234” (For mobile apps)
3. To display only the label please enter “#” in url

Transactions settings

Introduction text

Enter here text that will appear before the list of transactions

Show validity

When activated the date and time on which a transaction will be expired is displayed below the transaction button.

Aggregate

Enable this option if you are using business models and wish to display collections of transactions associated with business case.

In the example below we have two business case aggregations and two stand alone transactions:

1. Loan 12345-67: Has 2 transactions and is expanded
2. Loan 456778-90: Has 3 transactions and is collapsed
3. “Change of banking information” and “Direct debit consent” are stand alone transaction

Note that stand alone transactions are displayed only after business case aggregations.

Show submitted transactions and document options

These options are related with data model option which is not yet released.

Popup

Enter title and texts (or HTML markup). The popup will be displayed after each successful login. In case you are using HTML markup make sure to test the result on different browsers.

Order of appearance

Option	Description
Expiration	Default option for order is transaction expiration. Transactions that are first to expire will be displayed first by default.
Template order number	Order is arranged by template order of appearance
Template name	Order is by template name: Note that evaluation is case sensitive. “z” (small letter) is prior to “A” (Capital)

Note that aggregated transactions appear prior to standalone transactions

Autoplay

Enabling this feature will display client transactions one after the other automatically. First transaction is automatically opened. Once the first is submitted the next pops instantly. A transition page that redirect and inform the client regards the step can be customized to some extent. To setup autoplay, open Transactions settings and click “Autoplay transactions”. Follow this section to customize the option.

Option	Description
Autoplay transaction	Activate the option. Not activated by default. If activated then, once client logs in the first transaction will appear instantly after a transition page and popup, if configured
Loading text color	Text color to transition page. This does not include colors in HTML block
Display form name	Display or not displaying form name in transition stage. If form is part of aggregation (collection of transactions) then the aggregation label will also be included like so: Collection name, form name
Step prefix	Progression, i.e. 3 of 5, is displayed by default. With this option your able to add prefix. i.e. “STEP” will read STEP 3 of 5
HTML block	Free HTML block. If using this option be advised to test the auto play transition both for looks on varous browsers and devices. specifically mobile and also make sure that your content is accessible.

Additional control on looks

Template configuration offers the option to control the icon and the text of the button that opens up a transaction.

Client forms security

We are investing great deal of efforts protecting your and your clients data. For some of the methods we are providing the coverage. others require your attention. Following is a list of protections we have for client forms

Rate limit

This feature is builtin and is not optional. Rate limit prevents a client from posting too many requests for access in a given time window. The conditions of lock and release can be modified from time to time o our discretion.

Captcha

This feature is builtin and is not optional. Google captcha to prevent brute force

Password

This is a preliminary condition to access client forms. We advise to use passwords that cannot be mined such as sequence numbers. Instead make sure that the password include checksum/parity and it needs to be captured as part of the password.

OTP

OTP option is at your discretion and we encourage to make use of it.

Auto logout on idle

On idle (No use of client forms view) client is automatically logged out after 5 minutes

Auto logout if no transactions left on view

When completing a transaction client is be redirected to main client form view. If there are no transaction he will be automatically logged out after 1 minute

Poplast option

When appending ?poplast=true parameter to client forms it will automatically open a form in condition that there is only one transaction in view. Note that transaction will be displayed after authentications and regardless if there is a popup message configured.

Accessibility guideline

As in any other interface builder, we are making our best efforts to bring you all the goodies for collecting data and create amazing interface for your clients that reflect your brands. However this also come with a responsibility on your side. Although we are try to protect you in whatever way we possibly can to avoid accessibility errors, there are couple of ground rules to pay attention to.

Contrasts

Make sure that colors setting has sufficient contrasts. A button with pale background and pale text is not accessible. same goes to background image. make sure to incorporate background and colors sets that has contrast. How much contrast? check out this tester.

Messages and text

Make sure your messages, errors and instructions are clear and not implied. for example “Open” is better than “Transaction” as a text on a button to open new transaction.

This page described how to move a process with all of its related elements into another project on the same environment.

We will have to download/export every element separately in order to do so.

(BPMN processes, templates and also Dictionaries and Tables – if we are using them on our templates)

Follow the bellow steps:

1.Go to all the elements that are used on your process (BPMN processes, templates, Dictionaries and Tables) and download each one of them using the download or the export option.

On a BPMN process, use this button for download:

On a template, use this button for download:

On a Dictionary, click on the arrow next to the export button, and than ‘Export JSON’:

On a table, use this export button:

2. After you are sure that you have all the files related to you process saved on the side, delete from your current project all the data you want to move. (You can’t have identical processes/templates on the same environment)

3. Open the wanted project on the app.

4. Upload the data to the wanted project on this specific order (for remaining current connections):
-Dictionaries and Tables
-Templates
-BPMN processes

5. Connect integrations if needed.

6. Run the all process for making sure its working as expected.

Release management is our process to introduce new versions of Cellosign. Typical release include:

1. New features
2. Bug fixes
3. Maintenance and upgrades to software components
4. Adaptation to regulations and compliance requirements
5. Performance related changes

We are releasing approximately 6 new versions of Cellosign every year. That is every other month.

What a release cycle looks like?

Each release includes the following steps and thresholds. Each cycle is a two months lapse time starting from step 2 to step 7.

Over the past months we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed

Security

Allowed browsers

We have updated our blacklisted browsers.

Rate limit

This new addition is builtin, none optional and controlled exclusively by Cellosign staff. In end-client views this feature limit a client to post too many requests for access in a given time window. The conditions of lock and release can be modified from time to time to our discretion.

Cellosign views that includes rate limit are:

1. Client forms (new addition shipped with this release)
2. OTP and Challenge with Client session

Javascript limitation

Due to security concerns we are reducing our support to Javascript extension in templates. Please make sure that your templates does not contain javascript code. If it does, find configuration alternatives in Cellosign or seek our support team assistance.

Upload file size limits

Forms already include builtin limitations to upload files. Be advises that with this release we have also applied 5Mb limit when:

1. Posting file(s) through API
2. Configuring template
3. Creating Adhoc session

Heads-up for using iframe

Over the past year browser providers were and still consistently preventing and deprecating usage of iframes. Technology wise the prevention is about blocking cookies and outbound communications from the guest. Eventually, it is widely accepted, that iframe technology will be deprecated all together sooner or later.

Although Cellosign allows to deploy views in iframes, we encourage you to adapt other methods.

Signature verification

We have implemented functionality to validate signatures capture directly with internal services. This might take one or two more seconds when interacting with data collection.

Template changes

Signature field button text

Added option to change default text for signature button

Default values for select field

Added preference to pick default option for select field

Lock template

Until this release a template could be edited and changes are reflected on live sessions. With this new release we are promoting template lock per session for which a session will also hold the template properties at the time a session is initiated, which eventually result that changes in templates will have no impact on forms that have sent to clients. No clients will automatically work like so and by the end of Q1 2025 we shall enforce this change.

Font David Removed

Font David deprecated from Template configuration for the reason that it has issues with mixed char-sets and special characters, such as “@”. Be advised to replace template to other font face in case you are using it.

Autodate field

Added formats to auto date and now include breakdowns for day, month and year.

Zip and password

Depreciation notice. Zipping files in archive email has been depreciated.

Download PDF for print

We have added a new feature for client toolbar to create and download a PDF out of the data that is incorporated in a form without submitting the form.

Changes in connector integrations

Added functionality to modify integrations inline when moving template from one environment to another.

Read only

Added a read only configuration for session that disable the ability to submit a form.

Integrations

Filter archive web hook data

Added ability to exclude data and paragraph filed types in archive web hook.

Group data

Added “group_data” array to archive api for future use.

Dashboards

Expiration widget

Updated search expiry, Added 3 days and 1 week options.

Applications

BDI

Builtin BDI interface.

Electronic 101 form (טופס 101)

We have renewed our 101 certification. Please consult with your reference regards fully compliant 101 template.

All new client forms application

Refactor of client forms application. It includes many new configuration and UI settings to match your brand looks

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: xx
• Production [app.cellosign.com]: yy

New features & enhancements

Heads-up for using iframe

Over the past year browser providers were and still consistently preventing and deprecating usage of iframes. Technology wise the prevention is about blocking cookies and outbound communications from the guest. Eventually, it is widely accepted, that iframe technology will be deprecated all together sooner or later.

Although Cellosign allows to deploy views in iframes, we encourage you to adapt other methods. Sooner the better.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed

Enhancements

Client forms enhancement

Added automatic play to transactions. With this feature client forms application display is displaying client transactions one after the other automatically.

Bug fixes

N/A

Security

N/A

Compliance

We have renewed our ISO 27001/27799 certification.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be released at 28/07/24

New features & enhancements

Attachments to client email

With Cellosign we have two types of recipients that may receive an email at the end of a business process: agent and client. At the end of a business process a recipient of type agent will get on email that includes: signed PDF, raw data (Typically json file), attachments that were collected during the process. Client receives only the signed PDF.

With this change. A file upload and image upload controls include option to attach the file to client email as well.

Search in list of values field

Typically a remote search in LOV fields should include some flexibility to avoid cases where spell is wrong or an hyphen is in between words. This is called a “Fuzzy” search. Cellosign search works this way and it’s good for most cases, in other cases it doesn’t. Mostly it doesn’t work well when the words are long 7 letters or more. For that purpose we have added option for select type. The default one is “Fuzzy” as it is today and the new option is “Strict”. The values Cellosign will look for are only ones which were typed.

Fort more information see List of values control.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be released at 19/06/24

New features & enhancements

Email validation

On previous releases, Cellosign validated email extensions. With this release email validation is conformed to RFC 5322 standard which is basically composed of a string given that it includes “@” and a”.” in specific places. With this change there is no limitations on domain or sub domains.

Company seal from image

Cellosign includes a signature feature that embeds company details: name, company ID altogether with a graphic signature. With this release we added a new feature for which a client will be required to upload an image that will be used as a background for graphic signature.

Email buttons recolored

With this release button colors in emails has been modified from yellow to grey that conforms with contrast requirements for accessibility.

Get sessions API enhancement

Get sessions API enhanced to include assignee filter, that is the user whom created a session or was assigned to (“puh client”). See API Documentation for further details

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be announced separately

New features & enhancements

Company Registrar API

We are happy to announce that we have added an interface to Israeli companies registrar (“רשם החברות”). The interface allow you to validate that a company number actually exists. In addition the interface enable to fetch the following company details: name (Hebrew and English) and company status.

This feature is available on cloud installation. Please contact our support to check your eligibility for this feature

SMTP Authentication

Added new option to SMTP integration that requires no authentication. Please read the following documentation prior to implementation

Security enhancement: blocked login pages on iframe

In order to protect your data and your users from Click jacking and phishing vulnerabilities we have disabled the ability to carry out user login from an iframe. This security enhancement added to all pages that requires your users authentication: Login to main application, Login to Agent application and Login Tasks application.

Client authentication to open invitations, client forms and OTP remain unchanged.

Form control dependencies split

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 17/08/23
• Production [app.cellosign.com]: 23/08/23

New features & enhancements

Default date and date time to date control

Currently date control accepts a fixed date as a default value. With this release we have added the option to configure Date control to accept the date when transaction is generated. To configure current date apply “$now” to default value.

Salesforce formula editor

We have added into Salesforce “Percent” data type and now it can be edited and converted prior to propagation into form.

Enhancements to paragraph control

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 26/6/23
• Production [app.cellosign.com]: 06/07/23

New features & enhancements

Table footer

We have added to Table control ability to configure footer row to include textual values and SUM function that SUM column values. See here for more details

SMTP/SASL XAUTH2 Autentication

We have added SASL XAUTH2 authentication for SMTP integrations. SASL protocol is a secured way to Authenticate SMTP requests with services such as GMAIL, Office exchange etc. See here for more details

Validation errors

Ordered lists font

We have made changes to ordered lists to include formatting of bullet items. See here for more details

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 18/5/23
• Production [app.cellosign.com]: 01/06/23

New features & enhancements

Connectors filters

We have enhanced our connector functionality greatly to query and sort data from remote source based on complex conditions. Conditions can now meet any complexity of “AND/OR”, querying based on field types and compared with either fixed values or values already populated in a form. This option improves connector flexibility and to simplify connectors configuration.

More details in Integrating a connector.

Connector fields mapping

We have enhanced our data mapping for filling forms automatically. On top of building a formula for converting native datasets, we have added the ability to CONCATENATE values and into one string and also the ability to repeat those as many as records matches the query. For instance this feature will enable you configure a result that include first, last name and DOB for all account contacts. More details in Integrating a connector.

Client forms

Transaction board

Bug fixes

1. On earlier releases search items on multiple selections in PDF documents was not enabled. Please see notes on configurations in List of values.
2. Fixed issue with a display of conditions in a control group after modifying control ID.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Enhancements to paragraph control

Enhancements to table control

Connector description

Data tables enhancements

Faster SEAL document

SEAL API is used to create sealed (closed) PF documents without user intervention. We have improved this feature to response faster by 50%. This features requires activation. Submit ticket to our support to apply.

Salesforce package enhancements

We have added new methods to Salesforce package:

1. SEAL: Create signed documents
2. Delete: Revoke transaction

See more details in Salesforce guide

Apply signatures at bottom of PDF pages

Bug fixes

1. On earlier releases landscape documents could be uploaded for which the result could have contain errors in signed documents. To prevent that, we have added an error response when landscape PDF document is uploaded with an API or agent application

Announcements

Cloud migration

As previously announced, an upgrade to our cloud infrastructure (migrate to Azure) in production is planned at 23/4.

As a result of the upgrade our IP addresses will also be changed.

This is a list of current production IP and new infrastructure IPs:

Segment	Current IP	New Ips
Inbound: Requests to https://app.cellosign.com, i.e. login, API request for new sessions	34.120.149.102	20.31.141.237
Outbound Requests from Cellosign for Outgoing requests are API, Webhooks, SMTP, FTP, SSO and all custom integrations that submitted from Cellosign to your infrastructure. The new infrastructure includes only one IP that serve as a proxy for outbound traffic.	35.195.39.157 34.140.217.128 35.195.63.175 34.78.57.112	20.126.234.162.

Please make sure to list the new IPs before the planned migration date 24/03/2023 to prevent service blockage.

As soon as the IP addresses have been whitewashed, please submit a service request to set up a joint inspection date.

Make sure the new IP addresses are enabled before the test. We recommend for a joint test as soon as possible.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Temporary account lock

Prior to this change, five consecutive failed logins were locking a user account. Only user with project admin or above can release the account. While this is remain the default option, we have also added the option for a temporary lock.

With this option, you will be able to setup a lock policy:

1. Lock policy: Lock account after X consecutive failed logins. [That is the default policy]
2. Temporary lock to prevent login for X minutes

temporary lock based on two parameter:

1. After how many consecutive failed logins the temporary lock kicks in
2. For how long (in minutes) the account will be locked

What‘s next?

We advise you to review this change together with your organization security officer and choose appropriate lock policy for you.

Adhoc form permissions

Accessibility enhancements

Over the last minor releases 4.3.1 to 4.3.5 we have released various changes and bug fixes for accessibility.

Initial focus

Prior to the following change the initial focus was applied to START button. With this modification, the focus has been moved to Hamburger icon on the Top-Left corner in left-to-right forms and Top-right corner in righ-to-left forms.

Color switcher

We have removed “Normal” color toggler from accessibility menu. With this change when “Monochrome” is activated form colors will be mokdified

Preview texts

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Salesforce integration

With this release we are very happy to introduce you with Salesforce integration to Cellosign. This feature opens up a world of new possibilities were the entire digital journey can be implementation with no APIs on the client can be carried out with APIs integration. Simply couple Cellosign and Salesforce, configure what data is connected for two ways integration.

For more information please visit Connectors and Salesforce documentation pages.

Geo location

Added ability for Geo coding client location that includes a visible map, inserting an address or location manually or automatically with Client GPS or IP when applicable. Read more

Passwords vulnerability check

In addition to the regular passwords complexities, two-factor authentication we have applied additional security layer that check passwords renewals and passwords for new users with an internal vulnerable passwords database. When a user applying new password, password will first match the complexity and length according to your organization requirements and than match the password with passwords known to be vulnerable.

Underline placeholder for empty fields

New design option added to entry fields. Checking this option will include an underline where input value is empty. This is specially helpful when you need the final PDF result will show an empty value. To set this option:

1. Click on template field
2. Click on Design tab
3. Check “Apply underline in result PDF when field has no value”

Note: This option is available for field of type: text, number, select, textarea, paragraph, date, pad, date, email, phone only.

Email on Archive errors

On previous version we have added a feature that post Email to configured recipients notifying them regards failed archive. Within this release we have incorporated meta data file that includes identical content and structure to data which was pushed through the API.

Note: We advise you not to use the meta data from email to your application from number of reasons:

1. Email servers are typically rendering files content, encoding etc
2. We can’t always be sure regards the failure reason so you may consider the meta data file as unsafe

As a result of the notes above we will not be able to support cases where meta data from email is failed to upload into your APIs.

Fixes

1. #DEV-1052: Archive error notification in email are now posted with updated archive structure
2. #BUG-1173: Signature padding on HTML to PDF when additional field on same column is now fixed
3. #BUG-1351: Redirect URL at the end of session fail to redirect
4. #BUG-1477: Client form screen fail to render data fields but instead display fields id

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Updated Content Security Policy (CSP)

We have updated our security policy to prevent access from forms to unknown web resources.

Why is that important?

We are considering that any form that posted to remote client contain sensitive and valuable information (health, financials etc). By adding external resources to forms, such as image backgrounds from external URLs or PIXEL implementation such as google-tag-manager, the form is exposed to external Attack that prevent us from keeping you and your clients data safe.

What has been carried out on our side in that respective?

We have scanned your templates, checked and validated external resources and explicitly added resources that are secured to our CSP whitelist.

What should be done on your side?

1. Background images to forms using URLs must be avoided. Use base64 strings for background images. This is how to do it.
2. Case you require PIXEL support, please submit a ticket our support team. Add your PIXEL URLs to ticket for inspection.

Software upgrades

Software packages that are effecting remote client forms and agent application (co-browse) has been updated to latest release.

We have carried out comprehensive testing to make sure applications are intact. However, in case your templates includes Custom CSS and Javascript we advise to carry out tests to make sure your custom software works as expected. To see custom code, login to application console. For each template, open “Settings” and on the right pane click “Javascript” and “Stylesheet”, case the left pane is not empty, please double check your template at work.

Public page enhancement

As you probably aware, template and BPM processes can be launched using a public template. Typically public pages require an input to initiate a process. Up to this release, public page is presenting page with required input. With this upcoming release input requirements can be added to URL in a querystring format.

For example:

Open the this url. https://preprod.cellosign.com/public/02774a7724ae4211a903043bd4171c96. It display a page where you will be required to enter name, mail and phone number.

Alternatively, you can open this URL. All the required parameters are injected using a query string and the form will be opened instantly. Be advises that although this option is available use it wisely. Public pages with client data should be secured and posted to clients directly. DO NOT leave public URLs with client data out for grabs.

Apply user context to form

With this release you will be able to apply Agent context into form automatically. This can be helpful if you require Agent name,phone or email to appear on form automatically with no user intervention.

To do so, you will need to apply context as default values to field in a form. For example, you would like an agent email to appear on form automatically.

1. Add email field to form
2. On field settings add “$initiator.email” to default value.
3. Once new session is created the agent email will be displayed automatically

Note: It is advised to use this option when it’s required. Do not expose your employees data when not needed.

The following contexts are available for your disposal:

Data	Context	Note
email	$initiator.email
User login name	$initiator.username	Typically email
Phone	$initiator.phone
First name	$initiator.first_name
Last name	$initiator.last_name

Added “Table” element

Due to multiple requests, we have added “Table” element to our form builder.

For more details see reference to table in this guide.

Data tables enhancements

We have added new feature to data tables, that is the ability for data table cell to include input elements as well as static data.

When this is useful?

Let’s assume that you have an “Insurance proposal” that needs to be implemented. Your proposal might end up with hundreds or thousands of texts and input elements that are varied as our client engaging with the form, for instance, when “Second driver” is required, we want to show legal notice and inquire regards the potential driver(s).

One way of doing this is implement the entire data set within the form as it’s normally being done, this can be tedious when there are lots of form elements…

Another way is to implement it with data tables. With this enhancement, data table cells can include input elements as well as static data, so when client selects “Second driver” in the form, the entire set of texts and input will be displayed automatically, without the need to configure them in the form itself.

More details in data tables reference.

Fixes

1. #BUG-1436: Date element accept wrong format when entered manually is fixed and now accepts manually entered values as configured in data time format options.
2. #BUG-1362: On previous releases, when file was added to Google drive through Archive integration, date-time stamp was added to file name. This has been removed and file name includes only the file name convention, without date-time stamp.

Over the past weeks we have been working on improvements to Cellosign platform. In this blog post, you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Other than routine maintenance and bug fixes, the highlight for this release is infrastructure for Connectors. In this release and the next releases to come we will deploy direct connections to applications and databases that will enable you to design end to end applications with no APIs.

NEW FEATURES & ENHANCEMENTS

Data Tables

Think about it as a custom table hosted in Cellosign. You can customize it any way you want and connect it to template.

What it’s for?

Consider the option when you have large repository of texts that needs to be incorporated into business process either as initial value, as a condition to other selection or per user engagement. Up until now that way to handle this process would have required to configure fields and conditions inline the template.

In case texts needs to be incorporated into large amounts of fields and templates, this can be quite tedious. With this new feature you will be able to configure relational table with keys and data and use it in cellosign templates using our connector editor. This is specially become handy when you have extensive conditions to handle the texts and in case you have texts such as terms/legal that are expanded over large amount of templates, so you can keep it all in one place.

Configuring data table

To configure data table login to application and click “data sources” and “Tables”.

Click add table and define: table name, columns as instructed on screen. Click to add rows.

Eventually, you will have a data table with rows and columns.

Note that “key” type columns are designated for the connector in next step so you can search matching records.

“Preset” is the ability to get values from the table on session initiation, requires no user intervention.

“Live” will be configured when the connector require some of interaction from the user such as selecting value or click on a button.

“Submit” and “Post submit” are for databases and apps such as salesforce or Dynamics [that are coming up in next releases].

To configure connector to data table click “add” on “Preset” or “Live” sections.

1. Select data table you have configured
2. Set status “Active”
3. Define the lookup:
   • keys from the data table [one or more]
   • Equation [for data table equal only is applicable]
   • To which entity to compare with: form field value, label [integration] or fixed value
   • Add conditions as many is needed for the lookup
4. Define what happens if query return no results, one or more than one result
5. On “Live” you will need to configure how the connector is activated
   • on “Change”: As the user types in. Select the field from the list to attach the connector with
   • on “Click”: select a button from the form that will activate the connector
6. Finally map the query result into the form fields. which value from data table goes to which field in form

Connectors

We have created a consolidated editor for all communications with a template. That includes:

1. Integration with Webhooks
2. Template integration to get data from remote source [See additional notes below]
3. Data tables described in the section above
4. Upcoming connector to Salesforce in Release 85 [next release]
5. Upcoming connector to Dynamics and Databases in R86

What it’s for?

Consolidation of connectors has been carried out to provide the user a complete 360 view on all inbound/outbound integrations with a business process.

What has changed for Webhooks?

Webhooks for template, on previous release, is configured under Template->integrations -> Webhooks.

With this change Webhooks can be now edited under Connectors view. The new view is also includes “implicit” webhooks by default.

What has changed for Template services?

Template services, previusly on Template->integrations -> Template services, has no migrated both UI and functionality to Connectors with webhook.

A new webhook type has been defined “WHEF_FORM_FIELD_CHANGED”. The new webhook, like any other webhook allow to define the endpoint for integration: url, methods and many more capabilities, on top of the previous implementation, such as authentication method, timeout etc.

Once defined, on the project resources, it can be defined per template as well by adding fields mapping and behavior, button click or field on change.

Form preview

We have added the ability to view form before submission. This is very useful feature when you required that the end client will see the final PDF view before submitting it.

To activate this feature, log in to template editor, click settings icon and tick “Show form before submission”. preview will be displayed with watermark so it cant be used as an evidence before actual submit.

Note: up to release 84, this feature was available in PDF or Hybrid forms. Starting this release this feature is also available in HTML forms as well.

Recipient password

To secure forms for online clients Cellosign has OTP, password and authentication functionality that can be activated on a template

Currently OTP and authentication are activated both globally and also on recipients level, meaning a template can be configure that first recipient requires OTP and second requires authentication.

We have modified password functionality to be activated on recipient level as well.

All templates carrying passwords functionality will be migrated with the new functionality.

Note: Make sure to double check on pre-prod or production rollout that templates are working correctly.

Extended recipients

We have extended the maximum capacity for recipients in template configuration.

Up until now max number of recipients per template was 7. With this enhancements there’s no limit on number of recipients that can be configured.

Legacy archive: depreciation notice

By the end of the year we will deprecate legacy archive method. The replacement for legacy archive is Webhook archive.

This is relevant for you if you are using archive in one of these ways:

1. Configurable archive in template settings
2. Use “archive_url” tag on integration

Please be aware that deployments with this feature will not be supported by the end of 2022. Feel free to consult our support for transition.

Other changes and Fixes

1. Tokens removed from web server response headers to reduce visibility on application information
2. Per WCGA 2.0 for accessibility best practice we have removed high contrast view and applied changes for better engagement on “Monochrome” view
3. Israeli ID validation now includes requirement for 9 digits

Over the past weeks we have been working on improvements to Cellosign platform. In this blog post, you can see a list of what has been changed, updated, and/or what bugs have been fixed. Some of the highlights for this release are:

A) Visibility: We’re continuously investing lots of efforts to collect, provision and deliver to you quality heads up on errors. This release includes automatic notification on errors and ability to report directly from application console onto our ticket system while collecting valuable information that can save time on turn-around.

B) Consistency: Several changes has been made to ensure inbound and outbound data with external applications is exchanged timely and accurately. Both SMS and Email default providers has been replaced to provide consistent service. New services our complied with ISO-27001, ISO-27799 and GDPR standards.

NEW FEATURES & ENHANCEMENTS

Errors notifications

As part of our efforts for consistency we have published a tool that will alert closed circle of application administrators to receive email notifications regards errors in business processes.

Errors may occur from time to time as result of incorrect process configurations, connectivity with 3rd party applications or issues with software. Rest assure we are constantly monitoring business processes on our monitors. When an issue occurs admins will receive an email with as much information as possible to extract  from Cellosign in order to complete process manually so valuable data will not be comporomised.

For example, a business process is completed, Cellosign is failed to transmit the product to an API [i.e signed pdf, attachments and metadata]. In this scenario Cellosign will deliver the signed document and metadata to admins in order to be archived manually.

We are constantly improving our visibility on failures and this feature is planned to be improved in every new release .

To configure admins to receive error notifications you will need organization or project manager privilege.

Log into Cellosign, on the left tool bar click projects and enter email(s) in field “Send logs and errors to this address” on “Messages” tab

We advise to add at least one recipient

Inline ticket submission

We have incorporated a ticket form within the application. Ticket can be submitted from two locations in the application:

1. At the bottom of the leftmost toolbar, click the headset icon
2. In transaction board, toggle a transaction and click the headset icon

We will collect as much information as possible into the ticket including the reporter contact details and post it to our support team.

Clear field toggle button

New functionality added to enable inline clear button in form.

1. Using this functionality requires opt-in per field (turn it on)
2. Clear button is enabled only when edit permissions are granted

To turn on clear button enter into field configuration -> Values & Display tab and toggle on “Show clear button”

Old browsers deprecation notice

Cellosign is designed to provide clean and smooth user experience both for agents and remote clients. As part of our efforts, we have started a process of deprecating old browsers, first in line is IE11. [Specific notice for IE 11 published at April 18th].

We are planning to deprecate more browsers down the line. Heads up will be published in advance.

For a remote client we will display the view below that will enable the client to capture QR code that carry the url provided and also a click to copy into other browser.

Default Email provider

We are in process for replacing our email provider from Mailchimp to Sendgrid. Over the last month we have successfully deployed Sendgrid service on our per-production and lower grade environments. Sendgrid proven to be more reliable in delivery and tracking.

You may test the new mail provider on our per-production service on your convenient. The service will be rolled out to production altogether with this release.

Specifically In case emails from Cellosign are transported to you by an organization mail server (i.e. Exchange) please make sure emails are not blocked.

Certificate change

During the upgrade of this release we will also replace our outdated certificate which due to expire on June 24th. New certificate is already installed on our per-production service. Should you require a CA file to flush it onto your ends please contact our support at service@cellosign.com

Other changes and Fixes

1. Templates listing is now ordered by Template name
2. Added the ability to release user from lock where the Authentication system is remote such as in OKTA, Active Directory or Azure Ad
3. Replaced SMS provider. we have deployed inforu as SMS provider which has been prove to be more timely and consistent service. The change is seamless and does not require any action on your end. you’re welcome
4. Per WCGA 2.0 for accessibility best practice we have removed high contrast view and applied changes for better engagement on “Monochrome” view

First and foremost we are happy to announce that we have been certified for both ISO-27001 & ISO-27799. As you probably aware, certification process requires lots of efforts to make sure we are working and abiding to information security’ best practices and standards in order to keep your data safe.

Nevertheless, we haven’t slowed down with enhancements and over the last weeks, we have been working on improvements to Cellosign platform. In this blog post, listed what has been changed, updated, and/or what bugs have been fixed.

NEW FEATURES & ENHANCEMENTS

Client Identity Verification

CIV module authenticates remote client identity, throughout comparing an official document such as ID or Driving License with a liveness test and a live selfie . The entire verification process is completely automated and does not require an agent intervention.

Read more about this feature on this post.

Image Upload and Compression

First, for your convenient, we have removed upload limitation on image upload file size.

And couple of notes on this change:

1. All images uploaded to Cellosign are compressed and resolution is reduced to 1300px max (width/height)
2. Mostly after compressions, image file tends to reduce up-to 1Mb. Please be aware to set up your APIs in case your forms use lots of image uploads

OTP screen re-design

One time password screen for clients has been re-designed now includes more engaging UI, Send again and post OTP to other location buttons.

Fixes

1. Transactions are now displaying list of destinations where invite posted to and not just the first destination
2. Accessibility: PDF files generated from Cellosign are now compatible to be read automatically with NVDA screen reader
3. Accessibility: Paragraph elements are now added with new attribute presentation used by assistive technologies
4. Accessibility: Improve Monochrome and High contrast for accessibility mode
5. Accessibility: Headings has been modified to adapt context hierarchy to headings:
   • Page heading defaults to H1. Styling options moved to page style tab
   • Section heading defaults to H2
   • Template/form heading has been modified with shorthand “…” case template name is too long
   • Logo on top is now hidden on mobile screen

Using chrome browser:

1. On your chrome browser page, click F12.
2. Right click the refresh image:
   

A menu will open with 3 options.

3. Choose the 3rd option – Empty Cache and Hard Reload:

Emails and text messages in Cellosign are posted through 3rd party services. In case a message was posted successfully from Cellosign and acknowledged by the provider, you will see a green check next to to recipient address in the transaction board. Green check means that message has been provider has accepted Cellosign request for posting a message to the recipient. We do not have the visibility if messages actually delivered to recipient or has been blocked somewhere on delivery.

Message block may occur for any number of reasons, such as, Phone that has no permit for text messages, company email that may receive message from known source.

In case your organization requires a complete visibility on messages delivery it is advised that you will integrate with service providers to gain access to full transaction trail. Please see SMTP and SMS integrations to connect with your provider

For security reasons, file that is uploaded into form is scanned and also a check for its identity is carried out. Cellosign process does not take the file extension for example “.txt” that was uploaded for granted but rather check that the file signature (“identity”) and calculate the output file extension. In some cases a file could be uploaded as “.txt”, “.pdf” for example but the archived document could be “.bin”. That is because the file carries binary identity, mostly octet-stream identity.

OK, so what do I do next? Since this file cannot go through Cellosign with the original extension contact your client to get the file in other mean.

Each block printed on a PDF includes a markup to clear and preserve space from the content above it. The block also takes into account the height it needs to preserve. Mostly this would work just fine as expected. However on large text blocks (Mostly with paragraphs and tables), in case that the block appears in top of the page please use the following class remove-clear on section level (As appear in the image) to prevent your text-block from “jumping” to the next page.

Step 1: check mandatory fields

First, check with the client if he has filled in all the mandatory fields in the form. If the mandatory fields are not filled in, the customer will not be given the opportunity to send the form.

In Cellosign, verification of the correctness of data is activated for certain fields.

Therefore, make sure that the mandatory fields are filled in according to the requirements. For example: ID field contains a proper 9-digit number, an email address in a proper format, a customer number in the accepted format, and so on.

In these cases, there is a red note under the field that the value entered to the field is incorrect.

Step 2: Check internet connection

If the client is still unable to send the form, it is recommended to check the Internet connection.

If the client’s internet connection is fine, there may be a problem with the application of the form.

Step 3: Check if submit size exceeded

Templates may include Image and File collection controls. Specifically files can get to 5Mb each. Assuming template has many controls to collect files and images, the entire submit might exceed Cellosign limit for maximum body size: On production the limit is set to 50Mb. On Pre-production environment the limit is set to 30Mb.

How to verify that this is the issue?

Open browser console and search for HTTP code 413 which implicates that this is indeed the problem.

How to resolve?

Reduce the amount of file and image collection and make sure to reduce the maximum weight allowed for each.

Step 4: Contact support

Please contact support in your organization, if issue is not resolved, your support should contact Cellosign support with the relevant details

If no problems were found in the form implementation, please contact Cellosign support.

The definition of the length of time in which a form can be filled out or a business process can be completed in Cellosign is determined by the implementer of the form, according to the definitions and needs of the organization.

The default form availability for a client is 48 hours, however for various reasons such as a time limit or on the other hand a complex form that requires complex input of fields and attachments, it is possible to extend or shorten the time that the form will be available for the client.

Every time we send a form to the customer, we send a unique link. If the defined period of time has passed, the form will no longer be available and it is required to send the form one more time, by sending a new unique link.

If the expiration of the form has not passed, the client should enter the same link again, and continue until the end of the process. All the details entered by the client and/or the agent will be saved in the form, until the end of the availability period of the form.

For more information about the expiration of the form read here.

If the expiration of the form has not passed, however the customer clicked the link again and the form still did not open, please contact Cellosign support to check or restore the form.

In this case there can be several options.

The first and most common possibility is that the customer did not actually complete the form submission process.

To verify that the client has indeed sent the form, check in the Processes screen, under “Submitted” column.

If no information (date and time) appears under “Submitted” column, it can be concluded that the client did not complete the process of sending the form at all, and therefore the form was not received by email. See the image below.

A second option is when the information appears under “Submitted” column, meaning that the customer did send the form. Please check that the email was not received in spam or another folder.

If an email was not received in spam or other folders, then the next option is to check in the application of the form.

In the process of creating the digital form, you can choose with each sending of the form who will receive a signed copy. Often the reason why a form does not reach the email is that the definition has been changed to another email or there is “no email” defined.

If this option has also been checked and rejected like all the other options, please contact Cellosign support to check or restore the form.

There are three ways to check if the client has opened the form:

• Verification from Dashboard.
• Verification from Processes screen.
• Verification online from the Show Agent screen.

---

Verification from Dashboard

---

In Dashboard screen there is a section called “Viewed” where you can see all the forms that were viewed by clients in last 24 hours.

In addition, in all the other sections there is a column “Viewed”, that is automatically updated with the date and time details once the client opened the form.

For more information about Dashboard read here.

---

Verification from Processes screen

---

There is another way to check if a client has opened the form, for any user with agent or project manager permissions.

In Processes screen there is a column with the title “Client logged in” and there you can check last date and time the client opened the form.

For more information about Processes window read here.

---

Verification online

---

A representative from the organization works in screen sharing with a remote person online. The work is done on top of Show Agent interface.

Once the client opens the form the green indicator will appear at the bottom of the screen at the agent side for a short time.

For more information about Show Agent read here.

There are three ways to check if the client has submitted the form:

• Verification from Dashboard.

• Verification from Processes screen.

• Verification online from the Show Agent screen.

---

Verification from Dashboard

---

In Dashboard screen there is a section called “Submitted” where you can see all the forms that were submitted by clients in last 24 hours.

For more information about Dashboard interface read here.

---

Verification from Processes screen

---

There is another way to check if a client has submitted the form, for any user with agent or project manager permissions.

In Processes screen there is a column with the title “Submitted” and there you can check date and time when the client submitted the form.

For more information about Processes interface read here.

---

Verification online

---

A representative from the organization works in screen sharing with a remote person online. The work is done on top of Show Agent interface.

At the end of the process after the client completed and submitted the form the green indicator will appear at the bottom of the screen at the agent side for a short time.

For more information about Show Agent interface read here.

First, check that the client is properly connected to the Internet.

Then check the time settings of the form. Every time we send a form to the client, we send a unique link that is valid for a certain period of time determined by the implementer of the form, according to the definitions and needs of the organization.

For more information about the expiration of the form read here.

If the defined period of time has passed, the form will no longer be available and it will be necessary to send the form one more time, by sending a new unique link.

If the expiration of the form has not passed, please contact Cellosign support to check or restore the form.

In Cellosign system it is possible to define permissions for each field separately, who is allowed to enter data into a certain field. Data can come from another system in the organization or can be entered by the agent or by the client or both, and so on.

First, need to check with the form implementer that the client is allowed to enter data. See the image below.

If it was defined that the client does not have permissions to enter data in a certain field, he will not succeed.

It can be said that in most cases where a client will not be able to enter data into a certain field, the problem is in the permissions of the specific field.

If the issue is checked by an implementer and indeed permission is given to the client and yet he is unable to enter data, apparently this is a malfunction. Please contact Cellosign support to check the form.

Agent screen can be opened again from Processes interface, for any user with agent or project manager permissions.

Press “+” next to the transaction that needs help:

After it press “Show Agent” button to open the transaction from the agent side:

For more information about Processes window read here.

There are several options to send a form in Cellosign application:

• From Show Agent screen.

• From Dashboard screen.

• From Templates screen.

---

Send a form from the Show Agent screen

---

Press the “Show Agent” button at the top of the screen and select a form from the list.

Enter the client’s email address or mobile phone number at the top of the screen and press “Connect” button.

At this point, when the client opens the link from the phone message or the email, you can both work together on the form.

For more information about Show Agent read here.

---

Send a form from the Dashboard panel

---

There are two options to send a form from the Dashboard:

• Initiate New Process section.

Select a form from the list and press Send.

The template will be opened at the Agent screen.

Add phone number of the client or email address where the client will be able to open the form and add the relevant details. Press “Connect” button to send the form to the client.

• Initiate Ad-Hoc Process section.

Drag PDF file to the field or upload it by pressing “click here to upload” and selecting PDF file location.

By pressing “Send” button the file will be opened at the Agent screen.

Press “Add Fields” button to add controllers.

Add phone number of the client or email address where the client will be able to open the form and press “Connect” button to send the form to the client.

For more information about Dashboard read here.

---

Send a form from the Templates screen

---

Templates panel displays the list of templates related to the project. The page is accessible for users with “Project manager” and “Organization manager” permissions.

Go to the Templates screen, select a form template from the list and click the template name.

From the template toolbar press the “Show Agent” button to open the template in the Agent screen.

For more information about Templates read here.

Our current approach for supported browsers is blacklist and no whitelist. Blocking specific browsers and releases intends to remediate:

1. Popular browsers that are vulnerable or EOL with the limitation of popularity
2. Browsers or UA that known to be vulnerable
3. Browsers that does not make adequate use or no use at all to new technologies. Specifically use of cookies, local storage, recent CSS etc.

In the near future we intend to modify our approach to whitelist. In that event only specific browsers and versions will be allowed for service

What browsers are blacklisted?

Browser	Version	Note
Chrome	97 or lower
Samsung Browser	17 or lower
Firefox	116 or lower
Safari	18.0 or lower
Internet explorer	All version
Edge	97 or lower
Opera	83 and below

We are dedicating significant effort to safeguarding your data and your clients’ data. While some methods are fully covered by us, others require your attention. Below is a list of the protections we provide for forms.

Before we begin let’s clarify that we have a separate set of rules for “User” which are authenticated and authorized personnel whom are permitted to access Cellosign resources. Typically these users are connected to Cellosign through your organization IDM. (Azure Ad, LDAP etc..)Forms that needs to be filled by your users will require their authentication.

This page is about end-clients. Obviuous

Introduction

This privacy statement (“Statement”) applies to Republix Ltd. which develop and operate the Cellosign system (together “Company” “we,” or “us” and the “System”).

The security and privacy of your information are very important to us. Whether you are using one of our services as a cust-omer, potential customer, or just visiting our website, we want you to trust us with managing and protecting the information that you provide us with. We have prepared this statement to explain more about who we are and how we collect and manage your information.

This site is a general audience site which is neither designed nor intended to collect personal information from children and/or minors. In order to ensure compliance with the provisions of the law, children under the age of 13 should not provide use this site or the System.

By using any of our products or services (including our website) and/or by agreeing to this Statement, e.g., in the context of registering for any of our services or by any other means, you understand and acknowledge that we will collect and use Personal Data as described in this Statement.

It is important to note that this statement applies only to the data which is being collected and processed in our website by the company. Cellosign System is a product of the Company, which allows Company’s customers to easily create and manage forms for the collection of data. It should be emphasized, that the Company is not the owner of such data, is not allowed to use any of this data and has no control regarding the use of this data. Any inquiry or complaint regarding the data collected by any form in the system should be addressed to the relevant company/organization which is the owner of the data.  

Who we are and how can you contact us

Republix Ltd.

Kibutz Kefar Szold,

pob180, 12230

Israel

Phone +972 -525-794-833

Email Info@Cellosign.com

While you are visiting our website, we might collect some information about your use in our website for our purposes, as set forth by this Privacy Statement. Therefore, and with regard to any such Personal Data collected, we are deemed as the Controller for GDPR purposes.

Questions, comments, requests and complaints regarding this Statement and the information we hold are welcome and should be addressed to us by using the contact details above. All requests will be dealt with promptly and efficiently.

You have the right to make a complaint at any time to the relevant supervisory authority for data protection issues. however, we will appreciate the chance to deal with your concerns before you approach the authorities, so please feel free to contact us in the first instance.

Information we may collect from you

“Personal Data”, or personal information, means any information about an individual from which that person can be identified.

We collect Personal Data from you voluntarily when you provide such Personal Data to us, or via our services and websites with which you voluntarily interact.  We may also obtain such Personal Data about you as may be provided to us in the course of our legitimate business activities.

You do not have to provide us with your information, but in some cases, if you do not, it may mean that you are unable to use our services.  For example, we may be unable to complete a requested “contact form” inquiry, unless you’ll provide us with your contact details.

When you use our website or services and choose voluntarily to provide us with your information, we might collect and process the following information:

• Identity Data – including full name, username or any similar identifier, title, date of birth and gender and any other information provided by you upon your sole discretion.
• Contact Data – including email address and telephone numbers.
• Usage Data – includes information about how you use our website and services.
• Technical Data – includes internet protocol (IP) address, the device you are using, browser type and version, screen resolution, time zone setting and location, browser plug-in types and versions, operating system and platform and other technology on the devices you use to access this website.
• Marketing and Communications Data – includes your preferences in receiving marketing from us and our third parties and your communication preferences.

We also collect, use and share Aggregated Data such as statistical or demographic data for any purpose. Aggregated Data may be derived from your Personal Data but is not reveal your identity.

How is your Personal Data Collected

We use different methods to collect data from and about you, including through:

• Direct interactions – You may give us your Identity, Contact and Financial Data by filling in forms (e.g. “Contact Us” or “Newsletter Subscription”, etc.) or by corresponding with us by phone, email or otherwise.
• Automated technologies or interactions – As you interact with our website or any other system operated by us, we may automatically collect Personal Data (please refer to the description below, under “Cookies Usage”).
• Third parties or publicly available sources – We may receive Personal Data about you from various third parties and public sources, e.g.: advertising and social networks, analytics providers, search information providers.

Cookies Usage

Like many other websites, our website may use Cookies or Other Technologies (such as “pixel tags”, “web beacons”, links in emails, JavaScript, device IDs assigned by Google or Apple, or similar technologies, collectively “Other Technologies”). Cookies are a small text file that is placed onto an Internet user’s web browser or device and is used to remember as well as obtain information about that party. Cookies and Other Technologies allow us and third parties to obtain information about your visits to our website, including to analyze your visiting patterns, and to deliver online and mobile advertisements, messages, and content for us and others that are specific to your interests. In addition, Cookies may be used on the site in order to improve your experience.

We may use various types of Cookies:

Essential Cookies – which are necessary for the site to work properly;

Functional Cookies – designated to save your settings on the site – your language preference or other view preferences;

Session Cookies – used to support the functionality of the website – such Cookies are stored only temporarily during a browsing session and are deleted from your device when you close the browser.

Targeting Cookies – these cookies are used to collect information from you to help us to improve our products and services as well as serve you with targeted advertisements that we believe will be relevant to you.

Social networks Cookies – Social Plug-In Cookies (e.g. Facebook) enabling sharing of information with your social networks accounts to be smooth and seamless.

Analytics Cookies – give us aggregated information which enables us to improve the way our website works, e.g. Google analytics.

Please note that the data collected by use of Cookies may be linked to and combined with any other data, including Personal Data.

Managing cookies and opting out: aside from the Essential Cookies described above, you can always choose to configure your browser to reject all cookies or notify you when a cookie is set, but sometimes in that case, certain services, features, and functionality in our website may not be available to you.

You can always delete your browser history in order to delete any cookies from your computer.

The Legal Basis for the usage of your Personal Data

We will only process and use your Personal Data when the law allows us to, i.e. when we have a Lawful Basis for such usage. Such lawful and legal basis can be any of the following:

• Processing actions which are related to your reservations and/or requests, to carry out our obligations arising from any contracts entered between you and us. For example, contacting you per “Contact” form filled by you;
• our use of your information is necessary to meet responsibilities we have to our regulators, tax officials, law enforcement, or otherwise meet our legal responsibilities;
• our use of your information is in our legitimate interest as a commercial organization. For example, to operate and improve our services and to keep people informed about our products and services (including for profiling and targeted advertising). In these cases, we will look after your information at all times in a way that is proportionate and respects your privacy rights, making sure our legitimate interest is not overridden by your interests or fundamental rights and freedoms;
• You have provided us with your consent for the process of your Personal Data, upon your sole discretion and free will to use our website for making online purchases.

In general, and as detailed above, we do not rely on consent as a legal basis for processing your Personal Data.  Yet, in any case in which you have provided your consent to our processing of your information, you can withdraw this consent at any time by contacting us through the contact details provided above.

The purposes of the processing

We might use your data in order to: enable you to use our website and services in the most effective way, including the personalization of your experience by presenting content tailored to your interests; to meet or comply with any applicable rules, laws, regulations, codes of practice or guidelines issued by any legal or regulatory body; assess or evaluate the effectiveness of our system and services, as well as any technical and organizational measures designated for the protection of your Personal Data; protect our rights and legitimate interests, as well as defend against any lawsuit, legal claim or complaint; to conduct any other activities that are required to provide our services.

Transfer and disclosure of Personal Data

We are not in the business of selling your Personal Data. However, we may disclose your Personal Data to third parties in a variety of circumstances in the ordinary course of operating our business, such as:

• Disclosure of Personal Data to third-party service providers, providing us with services supporting our website and ordinary course of business, e.g. system, storage and computing services;
• Use of third-party services supporting our marketing efforts, in accordance with applicable law;
• When we have a legal obligation to do so, or when where are allowed to do so under our legitimate interests.

In any such transfer we will take steps to make sure such transfer is carefully managed to protect your privacy rights:

• transfers within our group and affiliates, will be subject to an agreement / policies and procedures made to ensure that your data receives an adequate and consistent level of protection as required by applicable law;
• transfers to any subcontractor or processor will be subject to contractual terms ensuring the security and protection of any Personal Data under any such sub-processor, in accordance with applicable law provisions;
• any transfer of data which originates in the European Union (“EU”) to a country outside of the European Economic Area (EEA), shall be made in compliance with the provisions of chapter 5 of the GDPR. Such transfer can be made to countries which are recognized as providing an adequate level of legal protection or where we can be satisfied that alternative arrangements are in place to protect your privacy rights, e.g. the EU-US Privacy Shield;

any requests for information we receive from law enforcement or regulators will be carefully validated before the disclosure of any Personal Data.

Links to other sites

Our website may include links to third-party websites, plug-ins and applications. Clicking on those links or enabling those connections may allow third parties to collect or share data about you. We do not control these third-party websites and are not responsible for their privacy statements. When you leave our website, we encourage you to read the privacy notice of every website you visit.

How we secure your information

We are committed to protecting the security of your Personal Data. We use a variety of security technologies and procedures to help protect your Personal Data from unauthorized access and use. However, the collection, transmission and storage of information can never be guaranteed to be completely secure. Yet, we take steps to ensure that appropriate security safeguards are in place to protect your information, and we will continue to revise our policies and implement additional security features.

Retaining your information in our systems

We will only retain your Personal Data for as long as necessary to fulfil the purposes we collected it for, including for the purposes of satisfying any legal, accounting, or reporting requirements. We have defined data retention priods for any data item in our systems, ensuring minimization of retention periods.

In some circumstances we may anonymize your Personal Data (so that it can no longer be associated with you) for research or statistical purposes in which case we may save and use this information indefinitely without further notice to you.

Data Subjects’ rights under EU data protection laws – GDPR

Under EU law, EU residents and individuals, have certain rights to apply to us to provide information or make amendments to how we process data relating them:

•  right to access your Personal Data – you can ask us to confirm whether or not we have and use your Personal Data, and if so, you can ask for a copy of your data;
• right to correct your Personal Data – you can ask us to correct any of your Personal Data which is incorrect, after verifying the accuracy of the data first;
• right to erase your Personal Data – you can ask us to erase your Personal Data if you think we no longer need to use it for the purpose we collected it from you. you can also ask for such erasure in any case in which the process of your data was based on your consent, or where we have used it unlawfully or where we are subjsect to a legal obligation to erase your Personal Data. any request for such erasure will be subject to our obligations under the law (e.g. our obligation to keep some records for tax or customs purposes);
• right to restrict our use in your Personal Data – you can ask us to restrict our use of your Personal Data in certain circumstances;
• right to object to how we use your Personal Data – you can object to any use of your Personal Data which we have justified by our legitimate interest if you believe your fundamental rights and freedoms to data protection outweigh our legitimate interest in using the information;
• you can always require us to refrain from using your data for direct marketing purposes;
• you can ask us to transfer your information to another organization and/or provide you with a copy of your Personal Data.

We may not always be able to do what you have asked, for example, if it would impact the duty of confidentiality we owe to others, or if we are otherwise legally entitled to deal with the request in a different way. However, we encourage you to contact us with any such request, and we will be happy to assist you.

Special Notification for California Residents

Individual customers who reside in California and have provided their personal information to us may request information about our disclosures of certain categories of personal information to third parties for their direct marketing purposes. Such requests must be submitted to us through the contact information Specified above.

Changes to this Privacy Statement

We reserve the right to change this statement from time to time at our sole discretion. If we make any changes, we will post those changes here so that you can see what information we gather, how we might use that information and in what circumstances we may disclose it. By continuing to use our site or our services or otherwise provide data after we post any such changes, you accept and agree to this statement as modified.

Effective as for August 2019