Your data, kept separate
Each company has its own database and its own subdomain.
This page describes the controls Chainlink has in place. Each one can be checked in the product or in the legal documents.
Each company has its own database and its own subdomain.
Web access, the app, Chainlink Wizard and the API use HTTPS. The exception is the status alerts some Zebra printers send over HTTP: they carry no operational data and use a key specific to each printer. Within your local network, the Wizard communicates with printers and readers using each device’s protocol.
Passwords are stored with a one-way algorithm, so they cannot be read. After several failed attempts, access is paused. Each user has a role with permissions defined by your administrator.
Each person uses their own user account. Devices (printers and readers) authenticate with tokens that you issue and revoke from your instance.
Payments are processed by Stripe. Chainlink does not store card numbers.
Each database is backed up every night and a restore is tested every week.
You can export all of your information to CSV at any time. After canceling, you have 30 days of read-only access to review and export it. CFDI invoices are kept for 5 years as required by Mexican tax law.
SAML 2.0 or OIDC with Microsoft Entra ID, Okta, Google Workspace or another provider. It can be enforced for the whole company: two emergency administrators keep their password and each use triggers an alert. On shared handhelds, badge and PIN.
Changes to settings, users, roles and access are chained to one another with a hash. An altered row breaks the chain and verification flags it.
Your instance is created when sign-up is complete, ready to set up your warehouse.
Essentials and Professional are purchased online by card: the first month and the implementation are charged at subscription. 30-day trial by invitation: request it from sales.