WORKCO · SECURITY & COMPLIANCE

WRITTEN FOR HR, IT AND LEGAL

Who sees what, what we hold, and what we do not do.

This page is written for the person who has to answer these questions inside your company: HR, IT or legal. It is written plainly, including the parts where we do not have something yet.

Access enforced in the database No continuous location tracking Every payroll edit recorded

THE FIRST QUESTION, ALWAYS

Who can see what

An employee sees their own. A manager sees the branches they run. HQ sees the chain. Pay is invisible to employees until the owner switches it on.

Data Employee Branch manager HQ WorkCo team
Their own shifts On request
The whole branch schedule On request
Hours and attendance Own only On request
Their own pay and payslip If owner enables If owner enables On request
Anyone else's pay Permission only On request
Branches they do not run On request

These boundaries are enforced at the database level, not merely hidden on the screen, so they hold even if someone queries the data directly. Our own team accesses a customer's data only to support them, limited to named people, and every administrator action is recorded.

WHERE THOSE BOUNDARIES ARE SET

WorkCo team screen listing staff, their roles and who is still active
01 ROLES AND BRANCHES
WorkCo on a computer, the whole branch week on one screen
02 THE BRANCH-LEVEL VIEW

WHAT WE HOLD

Everything we hold about one employee

This list is complete, not a sample. Your HR has to be able to answer this question to your staff, so we write all of it down.

Who they are

  • Name, plus the display name and profile picture LINE provides
  • Their LINE user id, which stands in for a password
  • Phone number, only if it was entered
  • Their role and the branches they run

Their work

  • The shifts they were given, and their confirmations
  • Check-in and check-out times, and the hours they add up to
  • Leave and days off

Only if payroll is used

This group exists only if you use payroll. If you do not, these fields stay empty.

  • Their pay rate, from their contract
  • Bank name and account number
  • Social security number, for Thailand

LOCATION

One point, at the moment they tap

We do not track anyone's location during the day.

When someone clocks in, the system reads their location once, to confirm they are at the shop. Then it stops. There is no repeated reading, no trail, no travel history, and nothing runs in the background once the app is closed.

The radius around each location is set by the owner, and if you would rather not use location confirmation at all, it can be switched off entirely.

WorkCo attendance report comparing planned shift times with the actual check in and check out
03 THE TAP

GETTING IN, AND OUT

No passwords, and no app to wipe.

They sign in with LINE

Staff sign in through their own LINE account, so there is no WorkCo password for them to remember, lose, or reuse somewhere else.

When someone leaves

Set the employee to inactive and their access is cut. There is no device to collect and no app to remove from anyone's phone, because there was never one to install.

Your data, if you ever leave

Attendance, payroll and site-visit reports export to CSV at any time, and payslips to PDF. You do this yourself, without asking us first.

THE RECORD

If a number changes, there is a record of who changed it.

Pay disputes happen. What settles them is a record, not somebody's memory.

Payroll edits

Every time a day's hours or amount is edited, the system records who did it, when, and what it changed from and to.

Employee time corrections

An employee can ask to correct a clock time, but a named approver has to approve it, and both the request and the approval are kept.

Messages that went out

Every schedule and reminder sent into LINE is logged, so the question of who received what, and when, has an answer.

WorkCo payroll screen, each person's amount built from the hours on record
04 THE NUMBERS ON RECORD

LABOUR LAW

The rules are in the calculation, not in a spreadsheet.

Thailand

  • Overtime rates worked out from the shifts actually sent
  • Social security deducted on the payslip
  • Employment contracts held in the system and tied to the pay calculation

Taiwan

  • Annual leave by length of service, 特休
  • Statutory overtime rates, 加班費
  • Labour and health insurance, 勞健保

STATED PLAINLY

What we do not have yet

If we left this out you would have to ask anyway, so here it is.

Not yet
ISO 27001 or SOC 2 certification
We are not certified to these standards. What we do have is a plain description of how the system is built, which is this whole page, and a team who will answer follow-up questions directly.
On request
A data processing agreement
It is not posted here to download. Ask and we will send it, and go through the detail with your legal team.
In progress
A public status page
The health checks already exist and run against the database and every background service. What is missing is a page where you can read the result yourself. We are building it, and it goes live before Early Access ends.
Not yet
Not committed
An uptime commitment
We do not commit to an uptime figure, because we would rather not promise a number we cannot yet prove. When something breaks you message our team in LINE, and the person who answers is on the team that built your system.
Not yet
Self-serve account deletion
You can export your data yourself at any time, but deleting the whole account still goes through us and we do it for you.

REQUEST THE PACK

Request the full pack

Tell us what your legal or IT team needs. We will send the data processing agreement, the detail on access permissions, and answers to your vendor questionnaire.