Yes, because it is a cloud platform, to use IDpack in the Cloud, you must be connected to a fast Internet connection at all times.

A modern browser is any browser that successfully displays IDpack in the Cloud using the latest web standards. A modern browser must support HTML5, jQuery, JavaScript, PDF, and SVG rendering. A modern web browser must show great performance as you navigate, like Firefox 78 and up, Microsoft Edge, Safari 13 and up, and all versions of Chrome. IDC recommends Google Chrome, as it is available on all platforms (Windows, Android, Chrome Book, and macOS), allows for standardization throughout the company, and makes it easier to support.

We do not provide support for installing or configuring devices such as printers, cameras, signature pads, contactless card readers, or barcode readers. To install such devices properly, please refer to the manufacturer’s instructions. We do not provide support for browser setup or computer configuration either.

Due to technical limitations, IDpack in the Cloud does not support magnetic or smart card encoding. We can receive input from the web browser, but a web browser cannot communicate directly to the computer’s hardware. We must develop a plug-in planned for a future release to add this feature.

Yes, each organization gets a unique SHA-512 encryption key, and all sensitive data is encrypted in our database using that key for maximum security. IDpack in the Cloud is also protected with a 2048-BIT SSL certificate. All data exchanged between your computer and our server is encrypted for maximum confidentiality. IDpack in the Cloud data is backed up every day and kept for 30 days in case of failure. Read our Privacy Policy for more information.

Yes, IDpack in the Cloud supports many ways to import your database. First, from a CSV or TXT file (comma-separated values). You can also cut and paste your data into an IDC form (CSV, TXT, Microsoft Excel, or Google Sheet). And last, with IDC Professional or IDC Enterprise, you can connect your CSV or TXT from an External Database via a Secure URL. JSON, XML, and Scheduled Import are coming soon for this last feature.

No, over the years, we have found that giving database control to our customers is the best way to corrupt the database. But we offer many fields to choose from, and if a field you need is not on the list, you can request field(s), and we may add one or more after review.

Yes, IDpack in the Cloud supports static images (logos) and dynamic images that change depending on the records (e.g., employee photos).

Yes, IDpack in the Cloud supports three ways to Import Photo IDs. First, a webcam can capture a Photo ID while creating or updating a record. You can also import a Photo ID from Producer. And last, import Photo IDs from a ZIP file using Designer in batch. This last feature is available upon request only and at our discretion.

Yes, using our records list filters, you can select up to 100 records and send them to the printer in batch.

Yes, we support any keyboard-emulated 2D barcode reader. You might need to program your barcode to send an ESC char before, then the barcode, and last, an Enter key code (CHR13). When you scan a barcode, IDC will look the card up in the system, and if it finds it, it will open the Card Information tab so the card can be printed or edited.

Yes, we support all Scriptel (EasyScript) models signature pads. EasyScript was built from the ground up to enable a simple and convenient way to capture electronic signatures and magnetic card swipe data (on supported devices) from various usages, including web-based and traditional applications.

Yes, we support keyboard-emulated HID OMNIKEY 5427CK Gen2 reader (R54270101 or R54270111). You must upload our System Config into the reader to work with IDC. When you scan an RFID card, IDC will look for the Contactless Serial Number (CSN) in the system, and if it finds it, it will open the Record Information tab so the card can be printed or edited. You can also Export the records and load the data into another system.