Privacy Policy

1. Scope and responsible organizations

Pinnary supports employer-managed workforce and service activities, including employee account access, attendance, work schedules, leave, overtime, approvals, company information, employee directories, and service-call management.

For questions about your organization’s use of workforce records, contact your employer or organization administrator. For questions about Pinnary and this Policy, contact YIPINTSOI NEXT Co,.Ltd. using the details below.

This Policy applies to the Pinnary Android and iOS applications. It does not govern an employer’s independent processing outside Pinnary or a third-party service reached through a separate application or website.

2. How we obtain personal data

Personal data may be obtained from:

• the user, including information entered, submitted, photographed, recorded, uploaded, or approved in the app;
• the user’s employer or customer organization, including account, employment, organizational, schedule, attendance, leave, approval, directory, and service-call information;
• the device and operating system, when the user grants a permission or uses a feature that needs device information;
• Pinnary and NEXX SERVICE systems configured for the user’s organization; and
• records generated when the user signs in, accepts a notice, performs an attendance action, manages a service call, synchronizes offline work, or contacts support.

3. Personal data processed by Pinnary

Account, profile, and authentication information

• username and credentials entered to sign in or change a password; employee code, user ID, organization code, unit code, customer code, name, email address, role, position, profile image, and account permissions;
• authentication and session information used to connect the user to the configured organization system; and
• account and organization configuration needed to route requests to the correct Pinnary or NEXX SERVICE environment.

Workforce and human-resources information

• schedules, shifts, clock-in and clock-out records, attendance history, attendance corrections, work-site information, assigned projects and tasks;
• leave, overtime, requests, approvals, remarks, supporting details, and related status history; and
• company news, notifications, organization information, and consent records.

Employee directory information

• employee name, nickname, employee code, position, unit, profile image, email address, business telephone number, mobile number, extension, LINE ID, and reporting-line information supplied by the organization.

Attendance photographs and face verification

• selfie or attendance photographs, location and time associated with the attendance event, and the result returned by the configured face-verification service; and
• photographs used as evidence for check-in, check-out, and other authorized attendance workflows.

When you use an attendance or service check-in feature that requires face verification, Pinnary submits your photograph to the configured verification service and records the verification result.

NEXX SERVICE call information and evidence

• service-call identifiers, project and site information, check-in and check-out times, remarks, findings, causes, solutions, status, and customer rating;
• attendance photos, work photos, uploaded documents and attachments, file names, and customer signatures; and
• location records associated with the active service visit.

Device, application, and operational information

• device platform, operating-system version, device model, app version, build number, organization or customer code, and employee code;
• connection state, synchronization status, permission state, error information, and technical records needed to operate and troubleshoot the app.

Consent and acceptance records

• consent identifier, content and version, effective date, acceptance date, acceptance channel, and the account identifiers associated with the acceptance.

4. Location information

Pinnary collects precise location for location-based attendance actions. For authorized NEXX SERVICE users, it also periodically records location during an active checked-in service visit, including while the app is in the background or the screen is off.

Foreground and event-based location

Pinnary may collect precise latitude, longitude, timestamp, and work-site information when a user performs a location-based action, such as clocking in, clocking out, recording attendance, confirming a work area, or using another form that requests the current location. This information is used to create the requested record and, where configured, determine whether the event occurred near the assigned work site.

NEXX SERVICE background location

Background location is limited to authorized NEXX SERVICE users and an active service visit. After the user grants the required precise and background location permissions and saves Check In, Pinnary records periodic location points while the service visit remains active. Recording can continue while Pinnary is in the background or when the screen is off.

Each point may include precise latitude, longitude, the time recorded, the employee or account context, and the service-call identifier. The point is sent to the configured NEXX SERVICE location-log system. If the device is offline, the point may be queued on the device and sent when a connection becomes available.

On Android, Pinnary uses an ongoing notification while its foreground location service is active. Background location recording stops after Check Out is saved or when no active checked-in NEXX SERVICE job remains. Pinnary does not use background location for an account that has no active checked-in NEXX SERVICE job.

Background recording is subject to device permissions, settings, and operating-system restrictions.

Purposes of location processing

• create and verify attendance and service-visit records;
• record the work location during an active service visit;
• determine proximity to a configured work site where that function is enabled;
• support offline attendance and later synchronization; and
• maintain an auditable sequence of authorized service-call activity.

5. Device permissions and user-initiated features

Pinnary requests device permissions only when they are relevant to an enabled feature. Depending on the device, organization configuration, and the features used, these permissions may include:

• Location: to record attendance locations, verify a work area, display map-related information, and support active NEXX SERVICE background location;
• Camera: to capture attendance selfies, check-in and check-out evidence, service photos, profile images, or attachments;
• Photos and files: to select, upload, save, export, or share images and authorized service documents;
• Microphone and speech recognition: to convert voice input into text when the user chooses to speak to the AI assistant. The app invokes the device’s speech-recognition capability, and the operating-system provider may process the audio according to the device configuration and that provider’s terms;
• Notifications: to show attendance, synchronization, service status, reminders, and organization notifications; and

The employee directory is supplied by the organization. Pinnary does not require access to the user’s personal device address book to display that directory.

6. Why personal data is used

Personal data is used as necessary to:

• authenticate users and maintain authorized sessions;
• provide the workforce, attendance, leave, overtime, approval, directory, notification, and NEXX SERVICE features requested by the user or enabled by the organization;
• verify attendance evidence and record check-in or check-out activity;
• store work completed offline and synchronize it when a connection is available;
• route data to the correct organization, tenant, and configured service environment;
• maintain consent and acceptance history;
• operate, maintain, secure, diagnose, and improve the reliability of Pinnary;
• provide user, employer, and administrator support; and
• comply with applicable employment, service, accounting, security, regulatory, and legal obligations.

7. Offline storage and synchronization

Pinnary stores certain settings, account information, cached records, and pending work locally on the device so that authorized features can operate reliably.

NEXX SERVICE uses a durable offline attendance queue. Pending check-in, location, check-out, photo, attachment, report, and signature evidence may remain in the app’s private local database until the configured service acknowledges the record. A successfully acknowledged location event is removed from the pending queue.

Signing out does not automatically delete pending offline NEXX SERVICE records. Synchronization status and any records requiring administrator attention are handled separately from account sign-out.

8. How personal data may be disclosed

Personal data may be disclosed only as relevant to the purposes described in this Policy, including to:

• the user’s employer or customer organization and its authorized administrators, supervisors, approvers, support personnel, or other authorized workforce users;
• the Pinnary, NEXX SERVICE, attendance, human-resources, directory, service-management, and organization systems configured for that user;
• YIPINTSOI NEXT Co,.Ltd. personnel who need access to operate, secure, maintain, or support Pinnary;
• service providers supporting hosting, storage, mapping, file handling, speech recognition, notifications, security, or technical operations, where those services are enabled and subject to the applicable organization and service arrangements; and
• government authorities, regulators, courts, or other persons when disclosure is required by law, a binding legal process, or a valid request from the responsible organization.

Employee directory information may be visible to other authorized users within the same organization according to that organization’s access rules. Pinnary is not intended to make non-public workforce information available to the general public.

9. Retention and deletion

Retention periods vary according to the type of record, the organization’s instructions, operational requirements, applicable law, and the need to establish, exercise, or defend legal rights. Relevant criteria include:

• the duration of the user’s account or employment relationship;
• the period needed to provide, synchronize, support, and secure the requested service;
• attendance, payroll, service, customer-support, audit, dispute, and compliance requirements;
• instructions and retention schedules established by the responsible employer or customer organization; and
• applicable statutory or regulatory requirements.

Ending account access or revoking a permission does not automatically delete previously submitted records. To request deletion, use the contact options in Section 12.

Revoking a device permission stops future collection that depends on that permission after the app recognizes the change. Revoking a permission does not automatically delete information already recorded on the device or received by an organization system.

Signing out does not automatically delete pending offline NEXX SERVICE records. Synchronization status is handled separately from account sign-out.

10. Security

Pinnary requires users to sign in to access account-based features and stores some pending records in storage assigned to the app on the device.

Users should protect their credentials, keep their device and Pinnary up to date, use device screen protection, and notify their employer or YIPINTSOI NEXT Co,.Ltd. promptly if they suspect unauthorized access.

No device, network, or storage method can be guaranteed to be completely secure. Security practices may also depend on the infrastructure and controls selected by the user’s employer or customer organization.

11. Permissions and user choices

• Users can allow, deny, or revoke device permissions through the operating-system settings.
• Without foreground location, location-based attendance actions may not be available or may be recorded without coordinates where the configured workflow permits.
• NEXX SERVICE attendance and active-visit tracking require the location permissions requested for those features. Other Pinnary features remain subject to the user’s account permissions.
• Users can revoke location access in their device settings. Disabling location may prevent location-dependent actions, including Check Out, from completing. Previously recorded information is not automatically deleted.
• Users may decline camera, photo, microphone, speech-recognition, or notification permissions, but the feature requiring that permission may not operate.
• Device permission changes do not erase records already submitted or retained for legitimate employment, service, audit, or legal purposes.

12. Access, correction, deletion, and privacy requests

Pinnary accounts are generally issued or managed by an employer or customer organization. Users seeking access to, correction of, or deletion of workforce data should normally contact that organization first because it determines the relevant employment and recordkeeping purposes.

Users may also contact YIPINTSOI NEXT Co,.Ltd. using the details below. YIPINTSOI NEXT Co,.Ltd. will review the request, verify the requester where necessary, respond for data under its control, or coordinate with the responsible employer or customer organization.

When responding to a deletion request, the responsible organization will explain whether any records must be retained, the reason for retaining them, and the applicable retention period or criteria.

13. Employer-managed accounts

The employer or customer organization may configure Pinnary features, determine user eligibility, grant roles and permissions, provide workforce records, review attendance and service evidence, and establish retention or approval rules. Users should consult their organization’s privacy notice, employment policy, and administrator for organization-specific practices.

14. Intended users

Pinnary is intended for authorized users of participating employers and customer organizations.

15. Changes to this Policy

This Policy may be updated when Pinnary features, data practices, organizational arrangements, or legal requirements change. The “Last updated” date will be revised when a new version is published. Where required, users will receive additional notice through Pinnary, their organization, or another appropriate channel.