ItemEyes Security

SECURITY

Data Security

The ItemEyes App database cannot be mined by ANYONE including the ItemEyes.com team of developers and staff.

Each picture and associated data is coded with a universally unique identifier (UUID), which consists of 32 hexadecimal digits in five groups separated by hyphens in the form 8-4-4-4-12. The hexadecimal digits represent 122 random bits and 6 fixed bits, in compliance with RFC 4122 section 4.4.

This makes the data you input into the app virtually un-hackable to obtain the information within the data. No names or account details are stored with the data, therefore tying locations to tagged items is impossible.

The photos and data can be seen by the public ONLY if user mindfully shares their personal data via the public link within the app. Only then, will the shared photos and relative data be available outside of the database. UUIDs are not something that can be guessed or have their code broken by hash descriptors.

Unfortunately, no method of transmission over the internet or method of electronic storage is 100% secure. Therefore, while we strive to protect your personal information, we cannot guarantee its absolute security. The security methods we use as discussed above show an extremely high level of security and even if the data was breached, no one could put the location of the photos and the field assets together to find them in their entirety.

Additional Information on UUID Security

A universally unique identifier (UUID) is a 128-bit label used for information in computer systems. The term, globally unique identifier (GUID) is also used, often in software created by Microsoft. When generated according to the standard methods, UUIDs are, for practical purposes, unique.

A UUID (Universally Unique Identifier) can be used for multiple purposes, from tagging objects with an extremely short lifetime, to reliably identifying very persistent objects across a network, particularly (but not necessarily) as part of an ASN.1 object identifier (OID) value, or in a Uniform Resource Name (URN).

UUIDs are an octet string of 16 octets (128 bits). The 16 octets can be interpreted as an unsigned integer encoding, and the resulting integer value can be used as a subsequent arc of {joint-iso-itu-t uuid(25)} (or 2.25) in the OID tree. This enables users to generate OIDs without any registration procedure.

UUIDs forming a component of an OID are represented in ASN.1 value notation as the decimal representation of their integer value, but for all other display purposes it is more usual to represent them with hexadecimal digits with a hyphen separating the different fields within the 16-octet UUID. This representation is defined in Rec. ITU-T X.667 | ISO/IEC 9834-8.

Example: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 is the hexadecimal notation that denotes the same UUID as 329800735698586629295641978511506172918 in decimal notation.

+--------------------------------------+

| uuid | +--------------------------------------+

| 4192bff0-e1e0-43ce-a4db-912808c32493 | +--------------------------------------+

DISCLAIMER

Read the ItemEyes Mobile Application Disclaimer.