Ops Platform
…

Privacy Policy

OpsStrike Store Ops · Effective 20 November 2026

What OpsStrike Store Ops is

OpsStrike Store Ops is an internal store-operations tool operated by the OpsStrike team for CP Axtra / Makro. It is used by store employees to carry out and track operational work (for example, aisle gap-scan tasks). Signing in requires a company account issued by your employer — the app is not intended for, and cannot be used by, the general public. The one exception is Help: anyone who cannot sign in can send a support request from the app or the public Help page, described in Help and support conversations.

Data we collect

  • Work identity. When you sign in through the company single sign-on (SSO), we receive your name, work email address, employee identifiers, role, and store/branch assignment. There is no public consumer sign-up. During staff self-enrolment, an employee confirms their existing employment record with an employee ID and SMS code, then registers their face; this creates or activates their OpsStrike SSO account. We never see or store a staff member's SSO password — staff sign in with face login and are never asked to type a password into the app. The only account that signs in with a password is a temporary review-only account we issue to an app store's review team for a single submission and disable afterwards. It belongs to us, not to any employee: we file its password with the app store reviewing the submission, and the app keeps it on the reviewer's own device so their review is not cut short.
  • Face data, used to confirm who you are. Each time you try to sign in — and each time you clock in or out — the app photographs your face with the front camera and sends it to your employer's sign-in service to be matched against the face they enrolled for you. If the match does not succeed the app retries automatically without you tapping anything, so one sign-in can take several photographs. See Face login and face data below for exactly what is collected, who processes it, how long it is kept, and how to have it deleted.
  • Location for attendance and the Clock-out helper. When you record the start or end of a shift, the app reads your device's precise location and sends it with that clock action to confirm you are at the store. It also takes an approximate reading on the home screen, before you clock in, to work out which of your stores you are at — that one stays on your phone and is not sent. From version 1.0.23, if you turn on the Clock-out helper and allow background location, your phone also notices when it leaves or comes back to your store during an open shift and for up to 30 minutes after you clock out, even when the app is closed. See Clock-out helper and the optional departure study below. If you report a situation at your store, such as a flood, you can also choose to add your location to that report — see Incident reports. With each clock action, the app also sends the results of checks that the location is not simulated and that the app and the phone have not been tampered with; if a check fails, the clock action is refused and the attempt is recorded — without your location. See Location and clocking in below for exactly what is collected, what is kept, and who can see it.
  • Operational activity. Tasks assigned to you and the actions you take on them — completions, timestamps, and the aisle/bay they relate to — are recorded as part of the work itself. Clocking in and out is recorded the same way: which store, which action, and when.
  • Attendance correction requests. When you ask to correct your attendance, we collect the reason you write, and a manager can add a decision note. This free text can name people and is stored with the request, along with any translation of it. Requests already filed as well as new ones can be translated as described under Storage, sharing, and retention: any request still waiting for a decision, whatever its age, and any request decided in the last 24 hours.
  • Photos you capture in the app. Gap-scan tasks ask you to photograph store shelving with the camera. These photos are uploaded to company systems as operational records. Some shelf photos are also sent through OpenRouter to an upstream AI provider selected by OpenRouter for automated shelf analysis. The requested model is Claude, but the upstream provider is not pinned. This transfer is used only to operate the shelf-workflow feature, not for advertising. The app does not browse or upload your personal photo library.
  • Incident reports. When head office asks stores to report a situation — for example a flood — you can send a report from the app: how serious it is, a note, photos you take or choose from your gallery, and, only if you tap “Add my location”, your location. See Incident reports below.
  • Sign-in records. Before your first face sign-in on a phone, the app asks for your employee number and records each step of your sign-up and sign-in against it, so your store can help you when signing in does not work. The app also counts how many phones open it, using a random number that is not linked to you. See Sign-in records below.
  • Device and notification data. A push notification token, and basic device information (model, operating system version) used to deliver task notifications and support replies, and to diagnose problems. From version 1.0.20 the app also reports how each location reading ended — for example that it worked, or that the phone's location setting refused it — but never the coordinates. From version 1.0.24 this includes whether a good reading on the clock screen was inside or outside the store area, never the coordinates or the distance. See When a location reading does not work below. From version 1.0.23, if you are offered the Clock-out helper, the app also sends counts of how well it works, in bands, never the times or places — see How we measure the helper.
  • Work manual reading. At pilot stores, the app records which parts of the work manual you open, how long you view them and the words you search for. See Work manual reading below.
  • Support requests. What you write when you ask for help, any screenshot you attach, and basic technical details about the app. See Help and support conversations below.
  • Messages the app keeps for you. When OpsStrike needs to tell you something about your own work — for example that a clock-in did not go through and what to do about it, or that something which was stopping you has been fixed — it keeps that message so you can read it later in the app. What is kept is which kind of message it was, which store it relates to, what the app should tell you to do (chosen from a short fixed list), when it was created, and whether you have opened it. It holds no free text, so nothing about anybody else can be written into it, and it is deleted after 90 days. Only you see your own messages.
  • Ratings and written feedback, while a design is being tried out. From version 1.0.25, the app may ask you for a quick rating after you clock in. A rating and an optional written note are not stored against your account. See Trying out a new design below.

How data is used

Data is used solely to operate the store-task workflows: assigning and tracking tasks, verifying task completion, sending notifications about work assigned to you, answering your support requests, receiving reports from stores during a crisis such as a flood, counting how the work manual is used at pilot stores, suggesting your clock-out time when you have turned on the Clock-out helper and forget to clock out, measuring how well the Clock-out helper works, studying branch departure and return patterns with phones whose owners opted into the study, translating the reason or note on an attendance correction request, and troubleshooting the service. Within OpsStrike, access is limited to your employer's operations teams and the people who run the service. External services that process data are named where this policy describes them, including under Storage, sharing, and retention.

Face login and face data

Signing in to OpsStrike uses face login, against the face your employer enrolled for you in their single sign-on. This section describes how that face data is collected, used, shared, retained and deleted. It is required reading before you sign in for the first time.

Where face capture happens

When you tap Sign in — or start a clock-in or clock-out — OpsStrike opens a camera screen inside the app and shows you a live view from the front camera. It takes a photograph when the screen has counted down in front of you, or when you tap the button. If the match does not succeed, the app tries again by itself — one photograph per attempt — so one visit to that screen can take several photographs without you tapping anything. Ordinarily it makes three such attempts, spaced a few seconds apart, and then stops and waits for you to press the button. There is one case where it keeps going: if your employer's sign-in service is busy, the app pauses for about a minute and then tries again on its own, and that can repeat while you stay on the screen. Leaving the screen always stops it. Nothing is captured before you reach that screen, backing out of it captures nothing, and the app does not open a browser to sign you in.

That photograph is sent directly to your employer's sign-in service, which compares it with the face your employer enrolled for you and returns only whether it matched. It is never added to your photo library, and the app does not keep it, queue it, or hold on to it once the request finishes. What the sign-in service keeps is described under “How long it is kept” below.

To be precise about the device itself: taking the photograph writes it briefly to a private temporary file in the app's own storage — this is how the phone's camera works and it is not visible to other apps or to your photo gallery. The app reads the image from there and then erases the file immediately, before sending the image. If the app is force-closed or the phone shuts down in the moment between those two steps, that temporary file can be left behind in the app's private storage until the operating system clears it; nothing reads it, and it is not visible to other apps. Apart from that, the only lasting copy is your enrolled face record held by the matching service described below.

Older versions of the app, still in use until everyone updates, instead opened your employer's SSO page (sso.cpaxtra.io) in a secure system browser view and captured your face there. Everything else in this section — what is collected, who it is shared with, how long it is kept, and how to withdraw consent — applies the same way to both.

What is collected, and why

A photograph of your face is captured when you enrol, again on each attempt to sign in, and again each time you clock in or out, so it can be compared with the face enrolled for you. It is used for one purpose only: to confirm that you are the employee the account belongs to — including confirming that the person recording the start or end of a shift is the person that shift belongs to. It is not used for monitoring your movements, profiling or advertising. We do not use it to train face-recognition models, and we have not allowed the cloud provider to.

To be plain about what that means for your working hours: your clock-in and clock-out times are a record of attendance, and the app asks you for a face match before it records one. What is stored against your shift is the store, the action, the time and the location described below — not the photograph, and not the result of the match, neither of which is attached to the attendance record.

From version 1.0.26, when an extra check is turned on, the app may also ask for a short video. This happens when your photograph matches but the check that a live person is in front of the camera is not sure. The screen asks you to do simple actions, such as blinking or turning your head, and the front camera records a few seconds of video with no sound. If the first try does not pass, it can ask once more. The video and that photograph are sent to your employer's sign-in service and on to the cloud provider described below, for the same purpose: to confirm that you are the employee the account belongs to.

Who it is shared with

Face photos are processed by a cloud provider's face recognition service, which performs the matching. Your enrolled face record is stored in that service under an internal person identifier. The cloud provider processes this data only on our instructions, and is required to provide the same or equal protection for face data as described in this policy. Face data is not shared with any other third party, and is never sold or rented.

ภาพถ่ายใบหน้าจะถูกประมวลผลโดยบริการจดจำใบหน้าของผู้ให้บริการคลาวด์ซึ่งทำหน้าที่เปรียบเทียบใบหน้า และข้อมูลใบหน้าที่ลงทะเบียนไว้ของคุณจะถูกเก็บในบริการนั้นภายใต้รหัสบุคคลภายใน ผู้ให้บริการคลาวด์ประมวลผลข้อมูลนี้ตามคำสั่งของเราเท่านั้น ข้อมูลใบหน้าจะไม่ถูกเปิดเผยแก่บุคคลภายนอกอื่น และไม่มีการขายหรือให้เช่า เราไม่ใช้ข้อมูลใบหน้าเพื่อฝึกโมเดลจดจำใบหน้า และไม่ได้อนุญาตให้ผู้ให้บริการคลาวด์ทำเช่นนั้น

မျက်နှာဓာတ်ပုံများကို cloud ဝန်ဆောင်မှုပေးသူ၏ မျက်နှာမှတ်သားသည့် ဝန်ဆောင်မှုက စစ်ဆေးပြီး သင်၏ မှတ်ပုံတင်ထားသော မျက်နှာမှတ်တမ်းကို ထိုဝန်ဆောင်မှုတွင် အတွင်းပိုင်း ကိုယ်ပိုင်အမှတ်ဖြင့် သိမ်းဆည်းထားပါသည်။ ဝန်ဆောင်မှုပေးသူသည် ကျွန်ုပ်တို့၏ ညွှန်ကြားချက်အတိုင်းသာ ဤအချက်အလက်ကို ဆောင်ရွက်ပါသည်။ မျက်နှာအချက်အလက်ကို အခြားပြင်ပအဖွဲ့အစည်းများနှင့် မမျှဝေပါ၊ မရောင်းချ၊ မငှားရမ်းပါ။ မျက်နှာမှတ်သားသည့် မော်ဒယ်များကို လေ့ကျင့်ရန် ကျွန်ုပ်တို့ မသုံးပါ၊ ဝန်ဆောင်မှုပေးသူကိုလည်း ထိုသို့ သုံးခွင့် မပေးထားပါ။

How long it is kept

  • Your enrolled face record is kept for as long as your account is active — that is, while you are employed and authorised to use OpsStrike.
  • Records of individual sign-in attempts — the account identifier, whether the match succeeded, a confidence score, the time and the IP address, but no face image — are automatically deleted after 90 days.
  • The short video described above is not kept by the sign-in service. The app writes it to a private temporary file and erases that file before sending it. We have not confirmed how long the cloud provider keeps it.

Deleting your face data and withdrawing consent

You can withdraw consent to face login at any time. Ask your store manager, or the OpsStrike support channel, to remove your face enrolment. Your account is deactivated and your enrolled face record is deleted from the face-recognition service; the sign-in attempt records described above are deleted along with it.

Please note: face login is currently the only way for staff to sign in to OpsStrike. Withdrawing consent therefore means you will no longer be able to use the app, and your store will record your work through another route.

App data usage

When usage collection is enabled for a supported app version, OpsStrike records counts of data uploaded and downloaded by its own app, the feature involved, and cellular, Wi-Fi or unknown connection type. The purpose is to understand and reduce the mobile data burden on staff. App transfer and connection figures are estimates; Android can additionally report its own app usage totals. These measurements are kept separate and are not carrier billing records.

A dedicated random app-installation identifier groups reports from the same installation. Transfers captured while signed in can be linked to your work account in a restricted first-party report for HR and platform administrators. Signed-out transfers and Android usage buckets are not assigned to a staff account. This identifier is separate from the anonymous app-open identifier. We do not collect traffic from other apps, SIM identifiers, network names, request contents or URLs through this feature. Usage records are retained for no more than 90 days after their reporting period. Collection is initially disabled pending validation and the applicable store privacy disclosures.

Sign-in records

To help you and your store fix sign-in problems, the app asks for your employee number on the screen where you agree to face sign-in. From then on we record each step of your sign-up and sign-in: when you agreed, whether your number was found, SMS codes sent and checked, and whether a sign-in worked or why it failed (for example "face not recognised" or "no connection"), with your phone type and app version. No face photo is kept in these records, and neither is your phone number. From app version 1.0.31 a step that failed also carries a random id, the same one a Help request sent from that error screen carries.

Your store manager, your area manager and HR can see these records to help you. They are deleted after 90 days; totals without names are kept. The record that you agreed is kept while you are employed, as proof of the agreement. The employee number is also kept on your phone, so the app can show "Signing in as" with the last four characters and fill it in when you register. Anyone using a shared phone can tap "Not you?" to remove it.

Separately, each time the app is opened it sends an anonymous install ID — a random number created by the app on that phone, not a hardware or advertising identifier — with the phone type, app version, language, and whether someone on that phone has agreed and is signed in. It never carries your employee number or your name, so it cannot be linked to you. It is used only to count how many phones open the app and how far they get, and is deleted 90 days after the phone was last seen.

Work manual reading

From app version 1.0.19, staff at the stores taking part in the pilot can read the work manual (คู่มือการทำงาน) in the app. When you open it, the app records which process or step you opened, how long you viewed it and the words you searched for, together with your employee identity, your store, your role and position, and the app version and phone platform (Android or iPhone) you used.

These records are used only to count how the manual is used — for example how many people open each process at each store or in each role. Reports show counts only, never names or employee numbers. The records are deleted after 90 days; totals without names are kept.

Location and clocking in

OpsStrike records the start and end of your shift, and it uses your device's location to confirm that you are actually at the store when you do. This section describes exactly when location is read, what is sent, what is kept, and who can see it.

When location is read

The ordinary attendance flow reads location while the app is open in front of you at two moments. The third case below happens only if you turn it on:

  • On the home screen, while you are not clocked in, the app takes one approximate reading to work out which of your stores you are standing in, so it can offer you the right “clock in” button. This reading is used on your phone only and is not sent anywhere.
  • When you actually clock in or out, the app takes one precise reading, and on Android one more if the first is too coarse to place you. It checks the reading against the store's location and sends it with that clock action; only the reading used is sent.
  • From version 1.0.23, if you turn on the Clock-out helper and allow background location, your phone also notices when it leaves or comes back to your store while your shift is open (at most 18 hours after you clock in), and for up to 30 minutes after you clock out, even when the app is closed. It notices only that the phone crossed a circle around your store, not where you go. See Clock-out helper and the optional departure study.

Separately from attendance, an incident report can carry one precise reading, but only when you tap “Add my location” on the report. That reading is sent with the report and handled as described in Incident reports, not as an attendance record.

Background location is separate from ordinary attendance. It is used only if you turn on the Clock-out helper and allow it, described below. If you decline foreground location permission, or your phone's location services are off, the app cannot clock you in and sends no location — it records only that the reading did not work, and why, as described next.

Clock-out helper and the optional departure study

From version 1.0.23, if you turn on the Clock-out helper, the app can suggest the time your phone left the store when you forget to clock out, so that you can fix your clock-out time in one step. It is off until you turn it on. The app explains it on its own screen, from Settings or from a card after you clock in, and asks your phone for background location permission only after you tap “Turn on”. It is never part of signing in, and turning it on or not has no effect on your attendance. When you turn it on, we record that you agreed and when, with an installation identifier, your phone's platform and model, and the app and operating-system versions, until you turn it off.

What is detected. While your shift is open, and for at most 18 hours after you clock in, Android or iOS notices when your phone leaves or comes back to a circular area around your store, including while the app is closed or not in use. Only those crossings are noticed: we do not upload a continuous route or the coordinates of your movements.

The 30 minutes after you clock out. When you clock out at the store with the app, your phone keeps watching the same circle for up to 30 minutes more, even when the app is closed. This is used only to measure how well the helper works: the phone notes the first time it leaves, works out how many minutes after your clock-out that was, and sends only that count, in a band (see How we measure the helper). That exit time stays on your phone, is never sent, and never fills in anything: your clock-out is already recorded, so there is nothing to suggest. Nothing from these 30 minutes goes into the departure study, even if you ticked it.

Where the time is kept. The time your phone left the store stays on your phone, for your own open shift, for at most 48 hours. If you forget to clock out, the app fills it in on the “Forgot to clock out” form. You check it, change it if it is wrong, and send it yourself. The people who review your request see the clock-out time you send, as with any request, and whether it started from the phone's suggestion and by how many minutes you changed it, so they can work out when your phone left the store. They never see where it went, any other time it left or came back, or a location. The helper never clocks you out, changes your attendance, or treats leaving the store as proof that you finished work. Your manager still approves the time.

The optional departure study. On the same screen there is a separate tick, off unless you choose it, to also include your exits and returns in a study of how often and how reliably phones detect leaving the store. Only phones with that tick send exit and return times to us. Study observations are associated with your work identity, branch and original clock-in session. They contain exit and return times, monitoring and permission status, an installation identifier, app and operating-system versions, device model, and the version of the store boundary. We also record monitoring availability so that missing observations are not mistaken for remaining at the store. Authorized administrators see aggregate study reports only, without names. The study helps assess detection reliability and departure patterns; it does not establish whether someone outside the store is still working.

When it stops. Each monitoring authorization ends at clock-out (or, when you clock out at the store with the app, at most 30 minutes after it, as described above), when you turn the helper off, or 18 hours after clock-in, whichever comes first. If a shift is closed elsewhere while your phone is offline, the server excludes study observations after that closure. A remote stop cannot immediately reach an offline phone; the app reconciles when it next runs, and unregisters expired monitoring when the operating system lets it run.

How long it is kept. If you ticked the study, valid observations recorded before ordinary clock-out may be queued on the phone for up to seven days and uploaded later under the original account, and identifiable study records are deleted after 90 days. This retention is separate from your attendance record. Whether a correction used the suggestion, and by how many minutes you changed it, is kept with that correction request, like the rest of the request.

Turning it off. You can turn the helper off at any time in the app's Settings, or remove background location in your phone's settings. Turning it off stops monitoring and deletes the exit times kept on that phone. Withdrawing clears pending study observations on that phone and stops new uploads when the server receives the withdrawal. The “Forgot to clock out” form keeps working without a suggested time.

How we measure the helper

From version 1.0.23, so that we can tell whether the Clock-out helper works before offering it at more stores, the app sends us counts of how it went. Each is one choice from a short fixed list: whether the helper's screen was shown and whether you chose “Turn on” or “Not now”; which location permission you then gave, and whether you later turned it off; whether monitoring started for a shift, or why it could not; after a clock-out at the store, how many minutes later your phone left, in bands (for example 2 to 5 minutes, up to 30, or not within 30); whether the phone left and came back during that shift; how fast the battery went down per hour while it was monitoring, in bands, or that the phone was charging; and whether a suggested time was shown, sent unchanged or changed. They are sent without any time of leaving or clocking out and without any place. The battery band is read from the phone's ordinary battery level, which needs no permission.

The counts travel the same way as the location-reading results described next: with the app version, your phone's model and operating-system version, the language you chose and the time the app recorded each one. They are stored against your account and your store, and are deleted after 90 days. The dashboards we watch add them up by kind, phone platform and store; they carry no name or account. A count never changes your attendance or a correction request.

When a location reading does not work

From version 1.0.20, each time the app tries to read your location — on the home screen, when you clock in or out, or when you help a colleague clock in — it reports how that attempt ended: that it worked, that it needed a second try, that the phone's location setting or the app's permission was off, or that no reading arrived in time. With it the app sends the app version, your phone's model and operating system version, the language you chose in the app, and a random number that changes every time the app is started. It sends no coordinates and no text you typed. Each kind of result is sent at most once per screen each time the app is started. From version 1.0.24, when the clock screen gets a good reading, the app also reports whether that reading was inside or outside the store area, roughly how accurate it was (as a band, such as 10 to 30 metres) and whether it was precise, but never the coordinates or the distance from the store. On Android it also reports your answer when the app offers to turn on location with one tap, or that the offer could not be shown. These results are stored against your account and your store so that support can see why you could not clock in and so that we can count which phones and settings fail most often and how often a reading stops a clock-in as outside the store area, and they are deleted after 90 days. When a reading fails, the same result is also sent to our crash-reporting service without your name, employee number, store or location, and without any numbers from the phone's error message.

What is collected, and why

With each clock-in and clock-out we store the latitude and longitude of the reading and its accuracy (how large an area the reading covers, in metres), attached to that clock event. If your phone is set to share only an approximate location — Android's “Approximate” option, or turning off Precise Location on iOS — the app records the less exact reading it is given instead, and the accuracy figure is what tells you which you got. The purpose of the stored coordinates is a single one: showing that a shift was started and ended at the store it was worked at. That is what makes the attendance record trustworthy to your store and to payroll, and it is why an out-of-area clock-in is refused rather than recorded.

One exception, and it is the only one: if you forget to clock out, the system closes the shift for you after 18 hours (or the period your store has set). That automatic clock-out involves no camera and no location — it records only that the shift was closed, and that the system rather than you closed it.

Apart from the diagnostic result described above (inside or outside the store area, in bands), nothing else is derived from it. It is not used for productivity monitoring, not compared between colleagues, not used to build a movement history, and never used for advertising or shared with advertisers.

Each clock-in and clock-out also carries the results of the checks below. They exist so that a clock action cannot be faked — for example, by an app that makes a phone report a location it is not at:

  • whether your phone itself reported the location reading as simulated;
  • a check that the request came from the genuine OpsStrike app, not a modified copy — made on Android by Google Play Integrity, which also checks that the phone has not been rooted or otherwise modified, and on iPhone by Apple App Attest;
  • on iPhone only, a check the app makes on the phone itself for the traces a jailbreak leaves, such as jailbreak tools being installed. Only the answer — yes or no — leaves the phone.

Google and Apple provide their checks under their own terms. The app receives a signed answer and sends it with the clock action, and what we receive is that answer — whether the app and the phone passed — and nothing about your other apps, your files or your messages. On iPhone the answer is signed with a key the phone's security hardware creates for the app the first time it is needed; we keep the public part of that key, the account that registered it, and when it was registered and last used, so that later clock actions from the same installation can be checked, and delete them once the key has gone 90 days without being used. These results are used for two things only: deciding whether that clock action is accepted and, when a check fails, keeping the record described next so the attempt can be followed up.

If a check fails, the clock action is refused, and we keep a record of the attempt: who tried, at which store, whether it was a clock-in or a clock-out, when, which kind of phone it was, the phone's model and operating system version — for example “samsung SM-A135F” and “Android 13” — and which check failed or could not be made. The model and the version describe a kind of phone, not your phone: every handset of the same model reports the same two words, so neither tells your phone apart from anyone else's of the same kind, and we keep no serial number, no device identifier and no name you have given the phone. They are there because a failed phone check does not say whether a phone has been modified or is simply an older model that its maker no longer certifies — and if several people on one model are being turned away, that is something for us to fix centrally rather than to ask them about. That record does not include your location. We keep the same record, but let the clock action through, when the check cannot be completed on our side — for example, because Google's checking service cannot be reached from our servers at that moment — and when a check fails while we have switched refusals off for a time, for example to look into phones of one model being refused wrongly. These records exist so that a clock action that may have been faked can be followed up, and they are not used for anything else.

When a clock action is refused, the app also keeps a message for you, so that you are not left guessing. It tells you what to do — turn off a mock-location app and try again, scan your face again, update the app, or ask your store manager to clock you in — and nothing about which check failed. When something that was stopping you is fixed, you get a message saying you can clock in again. If a notification is sent to your phone for one of these, the notification itself carries only a short line and a reference: never which check failed, never where you were, and never anyone else's name. What to do about it is in the app, where only you can read it.

If you often forget to clock out, we may send you a reminder to clock out during your shift, about 8 hours 45 minutes after you clock in. To learn whether these reminders help, only some staff receive them, chosen at random. We choose who may get one from your own clock-out record (how often the system had to clock you out), and we keep a record of which reminders were sent so we can measure the result, deleted 90 days after the trial ends. The notification itself says only that you should remember to clock out: never your name, your store or your times.

หากคุณมักลืมลงเวลาออกงาน เราอาจส่งการแจ้งเตือนให้ลงเวลาออกงานระหว่างกะ ประมาณ 8 ชั่วโมง 45 นาทีหลังจากลงเวลาเข้างาน เพื่อดูว่าการแจ้งเตือนช่วยได้หรือไม่ จะมีพนักงานเพียงบางส่วนที่ได้รับ โดยสุ่มเลือก เราเลือกผู้ที่อาจได้รับจากประวัติการลงเวลาออกงานของคุณเอง (ระบบต้องลงเวลาออกให้บ่อยเพียงใด) และเก็บบันทึกว่าส่งการแจ้งเตือนใดไปบ้างเพื่อวัดผล โดยลบภายใน 90 วันหลังการทดลองสิ้นสุด ตัวการแจ้งเตือนบอกเพียงให้อย่าลืมลงเวลาออกงาน ไม่มีชื่อ สาขา หรือเวลาของคุณ

When it was a phone check that failed, that record also holds the short result the checking service itself gave — for example the words Google Play Integrity returned about the phone, or which step of Apple's check did not pass. These are fixed words from a short list, and they describe the phone and the app, not you: they are not an identifier for your phone, they do not tell your phone apart from another of the same kind, and they say nothing about your other apps, your files or your messages. We keep them because “a check failed” on its own does not say whether a phone has really been modified or is simply old, or not certified by its maker — and that is the difference between something to fix on a phone and a question to ask a person. They are used for that and nothing else, are not shown on any manager screen, and are deleted with the rest of the record.

A clock action is also refused when the location your phone reports is outside the store's area. When that happens we keep a record of the attempt: who tried, at which store, whether it was a clock-in or a clock-out, when, how far from the store the phone reported being, and how accurate that reading was. It does not include the location itself. These records are used for two things only: setting each store's area correctly, so that people clocking in from inside the store are not turned away, and following up a refusal.

These checks come with a new version of the app, and there is a changeover while everyone moves to it. During the changeover, a clock action that arrives without the checks — from an older version of the app, or from a phone on the new version that could not carry a check out at that moment — is still accepted, as it was before, and the location rules above still apply to it. When the new version tells us it could not carry out a check, we keep the same record for that clock action, without refusing it. The changeover ends once everyone is on the new version: from then on, a clock action without the checks is refused and recorded like any other failed check.

Who can see it

The coordinates are kept as an audit record. No manager screen, report or export in OpsStrike displays where you were: what your managers see is that you are clocked in, at which store, and since when. The one screen that draws the readings at all is used by the small team who set up each store's area: it shows the readings accepted at a store as unnamed dots on a map, with no name or time attached, so they can check that the area fits where people really clock in. The coordinates themselves are reachable only by the small team who administer the service directly, and only for the purposes above — for example, investigating a disputed shift. They are stored on the same company-managed cloud infrastructure as the rest of the service and are not shared with any third party. This is about the coordinates recorded with a clock-in or clock-out. A location you choose to add to an incident report is different: it is shown with that report, as described in Incident reports.

Managers also see refused clock actions. Managers with store-management access in OpsStrike can see, on the store's page, who tried, whether it was a clock-in or a clock-out, when, on which kind of phone, and which check failed — so that it can be followed up. The record holds no location, so none is shown. The checking service's own result and the phone's model and operating system version, described above, are not on that screen: they are reachable only by the small team who administer the service, and only to look into why a phone was refused. They are kept on the same infrastructure and are not shared with any third party.

A clock action refused for being outside the store's area is seen by the same small team who set up each store's area: who tried, at which store, whether it was a clock-in or a clock-out, when, how far away the phone reported being and how accurate that reading was. Again, no location is kept, so none is shown.

How long it is kept

The precise location recorded with a clock-in or clock-out is kept for 90 days and then deleted. Your attendance record itself — that you clocked in at a store, and when — is kept for as long as employment records are kept under your employer's data-retention policy, because it is a record of your working hours. After 90 days that record no longer carries the coordinates.

The records of these checks described above — of a refused clock action, and of one let through — are kept for 90 days and then deleted. An iPhone's registered key, and what we keep with it, is deleted once it has gone 90 days without being used.

The record of a clock action refused for being outside the store's area is kept for 90 days and then deleted.

AI suggestions on correction requests

When you file a correction request, an AI service (Tencent Cloud's model service, in Singapore, or Anthropic's Claude, in the United States, if that fails) may review a pseudonymised summary of your clock records for that request to suggest a decision to the person who approves it. It does not see your name, employee code, phone, face or exact location. A person always makes the decision. The summary is kept for 24 months.

คำแนะนำจาก AI สำหรับคำขอแก้ไขเวลาทำงาน
เมื่อคุณส่งคำขอแก้ไขเวลาทำงาน บริการ AI (บริการโมเดลของ Tencent Cloud ในสิงคโปร์ หรือ Claude ของ Anthropic ในสหรัฐอเมริกา หากบริการแรกใช้งานไม่ได้) อาจอ่านสรุปบันทึกการลงเวลาของคุณสำหรับคำขอนั้น ซึ่งผ่านการทำข้อมูลแฝง (pseudonymisation) แล้ว เพื่อแนะนำผู้อนุมัติว่าควรตัดสินอย่างไร AI จะไม่เห็นชื่อ รหัสพนักงาน เบอร์โทรศัพท์ ใบหน้า หรือตำแหน่งที่แน่นอนของคุณ คนเป็นผู้ตัดสินเสมอ และสรุปข้อมูลนี้จะเก็บไว้ 24 เดือน

အလုပ်ချိန်ပြင်ဆင်ရန် တောင်းဆိုချက်များအတွက် AI အကြံပြုချက်များ
သင် အလုပ်ချိန်ပြင်ဆင်ရန် တောင်းဆိုချက်တစ်ခု တင်သွင်းသောအခါ AI ဝန်ဆောင်မှုတစ်ခု (စင်ကာပူရှိ Tencent Cloud ၏ မော်ဒယ်ဝန်ဆောင်မှု၊ သို့မဟုတ် ၎င်း အလုပ်မလုပ်ပါက အမေရိကန်ပြည်ထောင်စုရှိ Anthropic ၏ Claude) သည် ထိုတောင်းဆိုချက်အတွက် သင်၏ အလုပ်ဝင်/ထွက်ချိန် မှတ်တမ်းများ၏ အမည်ဝှက်ထားသော (pseudonymised) အနှစ်ချုပ်ကို စစ်ဆေးပြီး ထိုတောင်းဆိုချက်ကို အတည်ပြုပေးမည့်သူအား ဆုံးဖြတ်ချက်တစ်ခုကို အကြံပြုနိုင်ပါသည်။ AI သည် သင်၏ အမည်၊ ဝန်ထမ်းကုဒ်၊ ဖုန်းနံပါတ်၊ မျက်နှာ သို့မဟုတ် တိကျသော တည်နေရာကို မမြင်ရပါ။ ဆုံးဖြတ်ချက်ကို လူတစ်ဦးက အမြဲ ချမှတ်ပါသည်။ ထိုအနှစ်ချုပ်ကို ၂၄ လ သိမ်းဆည်းထားပါသည်။

Questions about your location data

Ask your store manager or the OpsStrike support channel, as for any other request under this policy. Because a location reading is the evidence that a shift was worked where it was recorded, it is kept for the 90 days above rather than removed on request; if you believe a clock-in was recorded incorrectly, raise it and it will be investigated. The same goes for a clock action you believe was refused wrongly.

Incident reports

When something affects stores — for example a flood — head office can ask chosen stores to report the situation from the app. Sending a report is up to you.

What is collected, and why

  • Your report: how serious the situation is (a choice from a short list), the note you write, the store and the time.
  • Photos you take with the camera or choose from your gallery. Only the photos you pick are sent. A photo from your gallery can carry details your phone saved with it, such as when and where it was taken, and the photo is stored as it was sent.
  • Your location, only if you choose to add it. The app reads your precise location once, only when you tap “Add my location”, and you can remove it before sending. Your phone may ask for location permission at that moment; saying no still lets you send the report without a location.
  • Who reported. Your employee identity is kept with the report as an audit record. It is not shown to the people who read the reports.

These reports are used for one purpose: so head office can see what is happening at each store during a crisis and respond to it — for example sending help or deciding whether a store can open.

Who can see it

Head-office staff who use the OpsStrike web dashboard with a head-office role, and the administrators who run incident campaigns. They see the store, the severity, the note, the photos, the location if you added one, and the time. They do not see who sent the report. Your employee identity is reachable only by the small team who administer the service. Reports are stored on the same company-managed cloud infrastructure as the rest of the service and are not shared with any third party.

How long it is kept

Reports, their photos and any location you added are kept while the incident is relevant and then in line with company data-retention policy. A report made by starting a Help conversation with the campaign's keyword is deleted together with that conversation, as described in Help and support conversations.

เมื่อเกิดเหตุที่กระทบสาขา เช่น น้ำท่วม สำนักงานใหญ่อาจขอให้สาขาที่เลือกไว้รายงานสถานการณ์ผ่านแอป การส่งรายงานขึ้นอยู่กับคุณ รายงานประกอบด้วยระดับความรุนแรง ข้อความที่คุณเขียน สาขา เวลา รูปที่คุณถ่ายหรือเลือกจากคลังรูปภาพ และตำแหน่งของคุณเฉพาะเมื่อคุณแตะ “เพิ่มตำแหน่งของฉัน” เท่านั้น รูปจากคลังรูปภาพอาจมีข้อมูลที่โทรศัพท์บันทึกไว้ เช่น เวลาและสถานที่ถ่าย ผู้ที่ใช้แดชบอร์ดเว็บ OpsStrike ที่มีบทบาทของสำนักงานใหญ่ และผู้ดูแลแคมเปญจะเห็นรายงาน รูป และตำแหน่ง แต่ไม่เห็นว่าใครเป็นผู้ส่ง ข้อมูลผู้ส่งเก็บไว้เป็นบันทึกตรวจสอบเท่านั้น รายงานจะถูกเก็บไว้ตราบเท่าที่เหตุการณ์ยังเกี่ยวข้อง และตามนโยบายการเก็บรักษาข้อมูลของบริษัท

Help and support conversations

If you ask for help from inside the app or from the public Help page, a central support team answers you there. You can ask without signing in, for example when you cannot register or sign in.

What is collected, and why

  • What you write, and any screenshot you choose to attach. Only the photo you pick is sent, never the rest of your photo library. A photo can carry hidden details such as where it was taken; our servers remove them and store only the picture itself.
  • Basic technical details, sent with your messages and kept from the first one so the team can tell what went wrong: app version, phone operating system version, language, the screen or registration step you asked from, an error code, and the time. From app version 1.0.31 this also includes your phone's model.
  • Who asked. If you are signed in, the conversation is linked to your OpsStrike account. If you are not, it is linked to a random code stored on your phone or in your browser. In the app you can later choose to move it into your account after signing in. From app version 1.0.31, if you ask from a sign-in or registration error screen, the conversation also carries a random id for the attempt that failed. The same id is on that attempt's sign-in record, so our system can match the conversation to that attempt and show the support team what went wrong with it. The support team is not shown the employee number that was tried.
  • A notification token, only if you allow notifications, so we can tell you a reply has arrived. It is stored encrypted, and the notification itself contains no message text.

Speaking instead of typing

When tap-to-speak is available and you are signed in to the app, you can tap to speak your message in Thai instead of typing it. This is your choice, and typing always works. Your phone asks for microphone permission the first time. The microphone is on only while the screen shows that the app is listening, for up to 60 seconds, and it stops if you leave the app.

The recording goes to our server and is sent on to a cloud provider's speech recognition service, which turns it into text and may process it outside Thailand. The text comes back into your message box for you to check and edit, and it is sent to the support team only when you tap send. The app and our servers handle the recording in memory and do not save it to storage or write the recording or recognized text to logs. A failed clip can stay in memory for retry while you use the app. It is discarded when conversion succeeds, you cancel, leave support, change account or the app goes into the background. The cloud provider keeps the recognized text on its servers for up to 24 hours. We have not confirmed how long it keeps the recording itself. We do not use it to identify you, and the support team never hears it.

Who can see it

The central support team sees your conversation, screenshots and the technical details, and may keep internal notes about your request that are not shown to you. They use it only to answer and resolve your request; they cannot change your attendance, employee details or face registration through it.

How long it is kept

A conversation, with its screenshots and notes, is deleted 90 days after it is resolved. A conversation that is still open is kept until it is resolved. Copies in backups can remain until those backups expire. Removing the conversations from your phone or browser (the remove or forget option in Help) clears them there and ends that device's access once it can reach our servers, but does not delete them from our servers; to have them deleted sooner, use the request route under Questions and requests.

Trying out a new design

From version 1.0.25, we may try out different designs of the home screen and of clocking in, store by store, to learn which works best. Your store decides which design you see unless you are offered a choice in Settings; a choice you make there stays on your phone. The app works the same in every design.

What is collected, and why

  • Counts of how clocking in went. How long it took, in bands (for example 10 to 20 seconds), how many times you retried, in bands, and the stage where an attempt was left. These are sent with the design, your app version, phone platform and chosen language, and are stored with your store, without your account, your phone's model or its operating system. They are deleted after 90 days.
  • A quick rating. A thumb up or down and, if you write one, a short note of up to 500 characters. It is stored with your store, the design, your app version, phone platform, chosen language and the day, and without your name or account. So please leave names out of a note. It is deleted after 90 days. A rating is always optional, and you can close the prompt.
  • When you were last asked. So that nobody is asked twice in three days, we keep your account and the time you were last asked. It holds no rating, and it is deleted after 30 days or when the trial ends, whichever comes first.

What we do not do

  • No advertising, and no sale or rental of data to anyone.
  • No tracking across other apps or websites.
  • No continuous route collection. Background exit and return detection happens only if you turn on the Clock-out helper and allow it, and only while your shift is open and for up to 30 minutes after you clock out. Ordinary attendance uses the foreground readings described in Location and clocking in.
  • No access to your contacts, messages or files, and no browsing of your photo library: the app receives only a photo you choose to attach.

Storage, sharing, and retention

Data held by OpsStrike is stored on company-managed cloud infrastructure. Push notifications are delivered via Google Firebase Cloud Messaging, which processes the notification token for that purpose. When automated shelf analysis is enabled, shelf photos are also sent through OpenRouter to an upstream AI provider selected by OpenRouter. The external recipients named in this section may process and retain copies under their own applicable retention terms; their copies are not stored on company-managed infrastructure and do not follow the company's retention schedule. Face data is handled separately and is described in Face login and face data above; clock-in/out location has its own retention period and is described in Location and clocking in. Data is otherwise retained for as long as it is needed for the operational and audit purposes above, in line with company data-retention policy, and employee identity data is governed by your employment relationship with CP Axtra / Makro.

To translate the reason or note on an attendance correction request into a language its reader understands, that text is sent to the Gemini API (Google LLC, processed on servers worldwide).

เพื่อแปลเหตุผลหรือหมายเหตุในคำขอแก้ไขเวลาทำงานเป็นภาษาที่ผู้อ่านเข้าใจ ระบบจะส่งข้อความนั้นไปยัง Gemini API (Google LLC, ประมวลผลบนเซิร์ฟเวอร์ทั่วโลก)

အလုပ်ချိန်ပြင်ဆင်ရန် တောင်းဆိုချက်၏ အကြောင်းပြချက် သို့မဟုတ် မှတ်ချက်ကို ဖတ်သူနားလည်သော ဘာသာစကားသို့ ပြန်ဆိုရန်အတွက် ထိုစာသားကို Gemini API (Google LLC၊ ကမ္ဘာတစ်ဝှမ်းရှိ ဆာဗာများ) သို့ ပေးပို့ပါသည်။

HR can export your employee number, name, store, department, position, employment type, sign-up date, leaver status and leaving date, and your clock-in/out times, into the company's own HR and payroll systems through a secured interface. Your location, face data, phone number and device details are never included.

ฝ่ายบุคคลสามารถส่งออกรหัสพนักงาน ชื่อ สาขา แผนก ตำแหน่ง ประเภทการจ้าง วันที่ลงทะเบียน สถานะการลาออกและวันที่ลาออก และเวลาลงเวลาเข้างานและออกงานของคุณ ไปยังระบบงานบุคคลและระบบเงินเดือนของบริษัทเอง ผ่านช่องทางที่มีการรักษาความปลอดภัย ทั้งนี้จะไม่มีตำแหน่งที่ตั้ง ข้อมูลใบหน้า หมายเลขโทรศัพท์ หรือรายละเอียดอุปกรณ์ของคุณรวมอยู่ด้วยในทุกกรณี

App permissions

  • Camera — to photograph your own face when you sign in, to capture live aisle photos for gap-scan tasks, and to photograph a situation at your store for an incident report. See Face login and face data for how the sign-in photograph is handled.
  • Location — to confirm you are at your store when you clock in or out. Ordinary attendance requests “while using the app” access. The Clock-out helper separately requests background access (“Always” on iPhone, “Allow all the time” on Android), only after explaining its purpose and only when you tap “Turn on”. An incident report reads your location only when you tap “Add my location”. See Location and clocking in and Incident reports.
  • Photos — only when you choose a screenshot or photo to attach to a support request or an incident report. The system photo picker shares only the photo you choose.
  • Microphone — only when you tap to speak a support message. See Help and support conversations.
  • Notifications — to alert you to tasks assigned to you and to support replies, and, for some staff, to remind you to clock out.

Questions and requests

For questions about this policy, or to raise a request about your data, contact the OpsStrike team through your store manager or the internal OpsStrike support channel. You may use that same route to request deletion of your OpsStrike account and its associated data; the team will confirm the request and explain any employment records that must be retained under company policy or law.