Once something has been submitted, verified or approved, there is no way to edit it in TiM without requiring the crewmember to re-confirm, ensuring that all involved are kept abreast of changes.
Sensitive Information Redacted
To ensure the safety of crewmember data, after a packet has been successfully delivered to its final destination, TiM automatically erases sensitive information from the database while simultaneously scrubing documents stored on the servers. For reference purposes, a small fraction of the sensitive information remains permanently viewable (in the case of a Social Security Number, the last four digits remain while the rest of the number is erased from TiM).
Two Factor Authentication
Access to our servers and database can only be attained by designated employees of TiM and only from predetermined sites. This access can only be achieved via strict, two factor authentication protocols. Only mission-critical TiM staff are given access.
Security is the most important thing we do.
Documents are stored in Amazon S3 using Server Side Encryption as well as AES256, a symmetrical, 256-bit encryption algorithm that has been accepted by the U.S. and Canadian governments as a standard for data transmission and data at rest.
SHA512 is the encryption we use to securely store passwords and sensitive information in our database. This cypher ensures that no two pieces of information are encrypted the same way even if they are identical, making it extremely difficult for anyone to access usable sensitive data, even in the event of a data breach.
Secure Login and Connection to Servers
Passwords are stored using SHA512 encryption and cannot be unencrypted once created, meaning that the crewmember is the only one who will ever know or have access to said password. Additionally, we use a Secure Socket Layer (SSL) to create a secure, encrypted connection between TiM and the the user’s web browser.