Item 26 - Agreement with Allied Network Solutions, Inc. for Adobe Software and Subscription

Home Browse Search

Security and Hosting Overview June 2015 The criteria for archiving data are as follows: • Data remains in the active database for 24 months, at which point eligible data is moved to the archive database. • Data remains in the active report database for 24 months, at which point eligible data is moved to the archive report database. • Archiving begins with the worker. When a worker's end date is more than 24 months old, the worker and all associated data including the worker's work orders, job seeker record, job posting, time sheets, expense sheets, and payment -related items such as invoices are archived. • The archive process is run as a batch job on a weekly basis to move data from the active databases to the archive databases. • Data cannot be moved back from the archive database to the active database. SAP Fieldglass does not delete data from its archive databases and has data older than 7 years. In the future, if SAP Fieldglass decides to delete archived data, we will ensure that a minimum 7 years of data is retained. 1.6.3 Data Deletion Data deletion occurs only when required by a customer. SAP Fieldglass' data deletion capabilities allow customers to remain compliant with data privacy, data protection, and other related data directives. • Deletion logic is based solely on a customer's business requirements. A custom script is developed by SAP Fieldglass. • Results are verified in a non -production environment by both SAP Fieldglass and the customer prior to executing in production. • A "Preservation" flag is available for use. Customers can set this flag on any data to override logic that would otherwise delete the data. This is useful during times when litigation or eDiscovery efforts are in progress and certain data must be preserved. • Script execution frequency is determined by the customer. SAP Fieldglass is contractually obligated to retain at least 7 years of data for customers. 1.6.4 Data Usage Customer data is required in non -production environments for various reasons: • Second level help desk support for customer defect investigation and resolution. • Supporting customer requests for updating data, whether it be for desired changes or corrections for data modified by the customer in error. • Customer sandboxes — these are non -production environments configured only with the customer's data (customer's data is "sliced" out from the multi - tenancy production database). These sandboxes are required for many SAP Fieldglass Page 15 121