{"id":24612,"date":"2026-07-13T18:12:38","date_gmt":"2026-07-13T16:12:38","guid":{"rendered":"https:\/\/www.nanobyte.gr\/nb-scanner-privacy\/"},"modified":"2026-07-15T07:53:23","modified_gmt":"2026-07-15T05:53:23","slug":"nb-scanner-privacy","status":"publish","type":"page","link":"https:\/\/www.nanobyte.gr\/el\/nb-scanner-privacy\/","title":{"rendered":"NB Scanner \u2014 Privacy Policy"},"content":{"rendered":"
\n

Effective date: 13 July 2026 \u00b7 \u0397\u03bc\u03b5\u03c1\u03bf\u03bc\u03b7\u03bd\u03af\u03b1 \u03ad\u03bd\u03b1\u03c1\u03be\u03b7\u03c2 \u03b9\u03c3\u03c7\u03cd\u03bf\u03c2: 13
\n\u0399\u03bf\u03c5\u03bb\u03af\u03bf\u03c5 2026<\/strong><\/p>\n

English first \u2014 \u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac \u03c0\u03b1\u03c1\u03b1\u03ba\u03ac\u03c4\u03c9.<\/strong><\/p>\n

\n

Privacy Policy \u2014 English<\/h2>\n

1. About this policy<\/h3>\n

NB Scanner is a ticket check-in application for authorised event
\nstaff, developed and provided by NANOBYTE E.E.<\/strong>
\n(\u201cNanobyte\u201d, \u201cwe\u201d, \u201cus\u201d), a company established in Greece.<\/p>\n

NB Scanner is the companion mobile application to the NB Events
\nplugin for WordPress. It connects authorised event staff to the website
\noperated by their event organiser so that they can validate tickets and
\nrecord attendee check-ins.<\/p>\n

This Privacy Policy explains:<\/p>\n

    \n
  • what information the app accesses, transmits and stores;<\/li>\n
  • where that information is sent;<\/li>\n
  • the respective responsibilities of Nanobyte and the event
    \norganiser;<\/li>\n
  • how users may exercise their data-protection rights.<\/li>\n<\/ul>\n

    This policy does not replace the event organiser\u2019s own privacy
    \nnotice. The organiser is responsible for informing staff members and
    \nattendees about its processing of event, ticket, attendee and check-in
    \ndata.<\/p>\n

    2. Who the app is for<\/h3>\n

    NB Scanner is intended for authorised staff working at event
    \nentrances or performing ticket-validation duties.<\/p>\n

    Staff accounts are created and managed by the event organiser through
    \nthe organiser\u2019s own WordPress website running the NB Events plugin.
    \nUsers cannot create a staff account through NB Scanner.<\/p>\n

    The app is not intended for use by children or by event
    \nattendees.<\/p>\n

    3. Roles and
    \nresponsibilities under the GDPR<\/h3>\n

    For staff accounts, attendee details, tickets, check-in records and
    \nother event-related information, the event organiser is normally
    \nthe data controller<\/strong>. The organiser determines why this
    \ninformation is processed, how long it is retained and who may access
    \nit.<\/p>\n

    Nanobyte provides the NB Scanner application and the NB Events
    \nsoftware. Nanobyte does not normally receive event, attendee or
    \nstaff-account data through its own infrastructure when the app
    \ncommunicates directly with the organiser\u2019s website.<\/p>\n

    Where Nanobyte processes event-related personal data on behalf of an
    \norganiser, for example when providing contracted hosting, maintenance or
    \ntechnical support, Nanobyte acts as a data processor under the
    \norganiser\u2019s instructions and subject to the applicable contractual
    \narrangements.<\/p>\n

    Nanobyte acts as a separate data controller only for limited
    \ninformation processed directly by Nanobyte, such as technical connection
    \nlogs generated by the Nanobyte directory service and information
    \nsubmitted directly to Nanobyte in a support or privacy enquiry.<\/p>\n

    4. Summary<\/h3>\n
      \n
    • Login credentials are transmitted directly to the event organiser\u2019s
      \nwebsite and are not sent to Nanobyte.<\/li>\n
    • Event, ticket, attendee, staff and check-in data is stored on
      \nsystems controlled or selected by the event organiser.<\/li>\n
    • The app uses the camera only to scan QR codes. It does not take,
      \nstore or upload photographs or video.<\/li>\n
    • The app generates a random installation identifier used for security
      \nand check-in audit purposes. It is not a hardware identifier or
      \nadvertising identifier.<\/li>\n
    • The app does not contain advertising SDKs, third-party analytics
      \nSDKs, cross-app tracking technologies or third-party crash-reporting
      \nSDKs.<\/li>\n
    • Nanobyte does not sell personal data or use app data for
      \nadvertising.<\/li>\n<\/ul>\n

      5. Information handled by the
      \napp<\/h3>\n

      5.1 Organiser setup
      \ninformation<\/h4>\n

      To connect the app to an event organiser, the user enters or scans an
      \norganiser setup code.<\/p>\n

      The app sends this setup code to a Nanobyte-hosted directory service
      \nat eventos.nanobyte.gr<\/code>. The directory service returns the
      \ncorresponding organiser website address.<\/p>\n

      The setup request does not include staff login credentials, attendee
      \ndetails, ticket information, ticket QR codes or check-in records.<\/p>\n

      As with any internet request, limited technical information may be
      \nprocessed automatically by the directory service or its hosting and
      \nnetwork providers, including:<\/p>\n

        \n
      • IP address;<\/li>\n
      • date and time of the request;<\/li>\n
      • app version;<\/li>\n
      • device operating-system information;<\/li>\n
      • request and security information.<\/li>\n<\/ul>\n

        This technical information is used only to provide, protect and
        \ntroubleshoot the directory service.<\/p>\n

        5.2 Staff login information<\/h4>\n

        When a staff member signs in, the username and password entered in
        \nthe app are transmitted over an encrypted HTTPS connection directly to
        \nthe organiser\u2019s website for authentication.<\/p>\n

        The login credentials are not sent to Nanobyte\u2019s directory
        \nservice.<\/p>\n

        The app does not store the user\u2019s password. Following a successful
        \nlogin, the organiser\u2019s website provides the app with a session or
        \nauthentication token. The token is stored using secure device storage,
        \nsuch as:<\/p>\n

          \n
        • Keychain on iOS; and<\/li>\n
        • Keystore-backed secure storage on Android.<\/li>\n<\/ul>\n

          The organiser\u2019s website may also return the staff member\u2019s display
          \nname, username, account identifier and role so that the app can identify
          \nthe signed-in user and apply the appropriate permissions.<\/p>\n

          5.3 Random installation
          \nidentifier<\/h4>\n

          When the app is first installed or configured, it generates a random
          \ninstallation identifier, such as a UUID.<\/p>\n

          This identifier:<\/p>\n

            \n
          • is generated by the app;<\/li>\n
          • is not the device\u2019s hardware identifier;<\/li>\n
          • is not the Apple Identifier for Advertisers or Android Advertising
            \nID;<\/li>\n
          • is not used for advertising or cross-app tracking;<\/li>\n
          • is used to distinguish installations for security and check-in audit
            \npurposes.<\/li>\n<\/ul>\n

            The identifier may be sent to the organiser\u2019s website during login
            \nand may be recorded with ticket check-in activity. This allows the
            \norganiser to identify which authorised staff account and app
            \ninstallation performed a particular check-in.<\/p>\n

            Because the identifier may be associated with a staff account and
            \ncheck-in history, it may constitute personal data under applicable
            \ndata-protection law.<\/p>\n

            5.4 Ticket, attendee
            \nand check-in information<\/h4>\n

            For ticket validation and check-in, the app may access and display
            \ninformation supplied by the organiser\u2019s website, including:<\/p>\n

              \n
            • ticket QR code or ticket identifier;<\/li>\n
            • attendee name;<\/li>\n
            • ticket type;<\/li>\n
            • event information;<\/li>\n
            • ticket validity;<\/li>\n
            • current check-in status;<\/li>\n
            • previous check-in information, where available.<\/li>\n<\/ul>\n

              When a ticket QR code is scanned, the ticket code is processed by the
              \napp and transmitted to the organiser\u2019s website so that the ticket can be
              \nvalidated.<\/p>\n

              When a check-in is completed, the organiser\u2019s website may record
              \ninformation such as:<\/p>\n

                \n
              • the ticket or attendee concerned;<\/li>\n
              • date and time of check-in;<\/li>\n
              • check-in status;<\/li>\n
              • the staff account performing the check-in;<\/li>\n
              • the app installation identifier.<\/li>\n<\/ul>\n

                This information is stored on the organiser\u2019s systems or on systems
                \nselected by the organiser. It is not transmitted to Nanobyte\u2019s directory
                \nservice.<\/p>\n

                5.5 Support and privacy
                \nenquiries<\/h4>\n

                If a user contacts Nanobyte directly, for example by email, Nanobyte
                \nmay process the person\u2019s name, email address, organisation, message
                \ncontent and any information voluntarily included in the enquiry.<\/p>\n

                This information is used only to respond to the enquiry, provide
                \nsupport, protect Nanobyte\u2019s legal rights and comply with applicable
                \nlegal obligations.<\/p>\n

                Users should avoid sending ticket databases, attendee lists,
                \npasswords or unnecessary personal information in support emails.<\/p>\n

                6. Camera access<\/h3>\n

                NB Scanner requests access to the device camera solely to scan:<\/p>\n

                  \n
                • attendee ticket QR codes; and<\/li>\n
                • organiser setup QR codes.<\/li>\n<\/ul>\n

                  QR-code recognition is performed through the app\u2019s scanning
                  \nfunctionality. The app does not use the camera to take, store or upload
                  \nphotographs or video.<\/p>\n

                  Camera access can be disabled at any time through the device
                  \nsettings. If camera access is disabled, QR scanning will not be
                  \navailable.<\/p>\n