Headcount requisition and hiring approval for Singapore SMEs: from "we need one more person" to an approved req

Headcount requisition and hiring approval for Singapore SMEs: from "we need one more person" to an approved req

Monday 09:40. The operations manager tells the director in the corridor that the team is drowning and he needs another coordinator. The director says "ok, go ahead, but don't go crazy on salary." By lunch the manager has called an agency he used at his last job, and the agency has a job ad live with a salary range he thought sounded fair. HR hears about it on Wednesday from a candidate, and finance on Friday when the agency's terms arrive. Nobody can say whether this was a new seat or the replacement for the coordinator who resigned in August, what the role costs once CPF is added, or who actually agreed to the number on the ad.

That is the headcount requisition problem for a Singapore SME with 20 to 150 staff: a distributor, a contractor, an F&B group, a clinic chain, a logistics firm. Before anyone advertises a role, someone has to write down what the role is, why it is needed, what it costs in a month, and whether the money is in this year's plan. The right people then have to agree, in order, with their names on it. When this runs on corridor nods, the problem tends to show up at payroll, or when two managers find they hired against the same seat.

This guide is the operator version of a headcount requisition and hiring approval workflow. The runbook has five parts (trigger, extract, route, human gate, tracker) and moves each request through three states: RAISE, COST, SIGN. Job ads and agency briefs get one hold of their own, POST HOLD. Automation collects the request, pulls the headcount plan and the cost of the role, flags anything that needs a second look, and routes the req to the right signers. The HOD, finance and the director decide, and nothing goes out to job boards or agencies until the req is approved to post.

What a headcount requisition means in a 20 to 150 person firm

Search "headcount requisition Singapore" and page one is HR forum threads asking who should raise the request (most answers say the HOD, with HR supporting), a US-style policy template, downloadable manpower requisition forms and HR system feature pages. None of them tell a 40 person firm who signs when the director is overseas, or how the approved salary band affects a job ad on MyCareersFuture.

The short answer, for an SME operator:

Any request to hire, whether a new seat or a replacement, goes into one queue as a requisition with a req ID. The requester states the role, the reason, the reporting line, the salary band and the start date. Automation checks it against the headcount plan, works out the monthly cost and flags anything unusual. The HOD confirms the need, finance confirms the money, and the director signs anything new or outside the plan. Until the req is approved to post, no job ad goes live and no agency gets a brief. The approved band and job description go with the req into recruiting, and an offer outside the band comes back for a fresh signature.

An HR system with a requisition module fits when your approvers and grades are already written down and you open dozens of roles a year across several entities. A service fits when someone first needs to map how hiring requests really start in your firm (a corridor chat, a WhatsApp to the boss, a resignation letter forwarded to HR) and wire a form, a plan and approvals into tools you already use. If you cannot list who approved the last five hires, and at what band, start there.

Operator definition: the desk starts when a manager asks for a person. That covers a new seat, a replacement after a resignation or transfer, a contract role turning permanent, or an extra person for a project. A req ends when a named signer records one of five outcomes: approved to post, approved for later (with a date), sent back for changes, rejected, or withdrawn. An approved req closes when recruiting marks it filled and hands the hire to onboarding, or when it is cancelled.

Where this desk sits between budget, recruiting and onboarding

This is the step before anybody looks at a CV. It decides whether the company should hire and at what cost. Choosing the person comes later.

If you already run purchase requisitions, the shape will look familiar. Our purchase requisition approval workflow asks for a request, a cost, an approver and a clean handoff before quotes are collected. A headcount req follows the same pattern, but the cost repeats every month, the approvers usually include the director, and the handoff goes to a job ad, which has its own rules in Singapore.

Downstream, recruiting runs the ad, screening and interviews against the approved req. Once an offer is accepted, the employee onboarding paperwork desk takes over the contract, the forms and the payroll handoff. Salary reviews, promotions and transfers for people already on payroll stay on their own desks. If an internal transfer leaves a gap that needs filling, that gap comes here as a replacement req.

What MOM and TAFEP rules touch the requisition, in plain words

Most hiring rules bite later, at the ad, the interview and the contract. A few reach back into the requisition, because the req is where the job description, the salary band and the start date get fixed.

All employers in Singapore are expected to follow the Tripartite Guidelines on Fair Employment Practices. They say employers must recruit and select on merit (skills, experience or ability to do the job), regardless of age, race, gender, religion, marital status and family responsibilities, or disability. TAFEP's guide to writing fair job advertisements lists phrases that should not appear. "Below 30 only" and "preferably female" are there, and so are lines a hiring manager might copy straight from the req into the ad, such as "S Pass quota available" or "work passes will be applied for successful candidates". The selection criteria in the ad should be about qualifications, skills, knowledge and experience.

If the role might end up on an Employment Pass or S Pass, the Fair Consideration Framework applies. MOM's pages for the Employment Pass and the S Pass set out what that means for the ad:

• The job must be advertised on MyCareersFuture, open for at least 14 consecutive days, before the pass application goes in. The employer should not make a job offer during those 14 days.
• The salary range must be visible, and the maximum cannot be more than two times the minimum. It must contain the salary offered to the pass candidate.
• The occupation in the ad must match the occupation in the pass application, and the employer in the ad must be the same entity applying.
• Changing details such as the occupation, the salary or the number of vacancies means posting a new ad and waiting another 14 consecutive days. An ad that expired or closed more than 3 months ago cannot be used.
• MOM will reject pass applications linked to ads that are discriminatory or do not represent the job accurately.
• There are exemptions from advertising, for example when the company has fewer than 10 employees, the fixed monthly salary is S$22,500 and above, or the role is short term (not more than 1 month). MOM still expects fair hiring either way and strongly encourages employers to advertise on MyCareersFuture even when exempt.

For the cost line, MOM's S Pass quota and levy page says the S Pass levy has been S$650 a month across all sectors and tiers since 1 September 2025, and that S Pass holders are capped at 10% of total workforce in the services sector and 15% in construction, manufacturing, marine shipyard and process. For local hires, the CPF Board's contribution rates from 1 January 2026 put the employer share at 17% of wages for Singapore Citizens and permanent residents (from their third year) aged 55 and below and earning more than S$750 a month, with lower rates for older age bands. The Skills Development Levy is 0.25% of monthly total wages, with a minimum of S$2 and a maximum of S$11.25 per employee.

The Workplace Fairness Act was passed in two parts, on 8 January 2025 and 4 November 2025. In its November 2025 press release MOM said it aims for the Act to take effect in end-2027, and a February 2026 parliamentary answer repeats that timing. It is not in force yet. TAFEP's May 2026 article on preparing recruitment for the Act reads like a brief for this desk: do a job analysis so the role and its requirements are clear, put a vetting and approval process in place before job ads are published, and keep records of interviews, assessments and hiring decisions for each recruitment exercise for at least one year.

A replacement req often carries personal data about the person leaving (their name, their pay, sometimes why they left). Under section 24 of the Personal Data Protection Act, an organisation must protect personal data in its possession or under its control by making reasonable security arrangements. In practice that means the req form needs a restricted folder and the group chat stays out of it.

This guide is an operating workflow, not legal advice. Check the MOM and TAFEP pages for the version that applies on the day you hire, since rates and rules change.

Why SME hiring approvals need a desk (without a news roundup)

In a 30 person firm the director knows everyone, so approvals happen in conversation. That holds until the firm grows a second layer of managers, or the director travels for two weeks, or two managers each think the August resignation is their seat. Then a resignation turns into a replacement by reflex, at a higher grade, and nobody asks whether the work changed. The band gets agreed in WhatsApp, so the ad says one number, the agency hears another and the offer lands somewhere else.

The money side is usually invisible to whoever asks. A manager sees a monthly salary. Finance sees the salary, plus employer CPF for a local hire or the levy for an S Pass holder, plus SDL, plus whatever bonus your contracts promise, plus a laptop and software seats, plus the agency fee. A req that shows that full monthly figure next to the headcount plan gets a quicker and better decision than one that says "need one more, urgent".

Most of this desk is plain rules (one form, a lookup against the plan, a cost sum, a route by tier, a reminder), which makes it a sensible early workflow for a small team. The decision to add a person stays with people.

The named headcount requisition runbook (RAISE, COST, SIGN)

Print this and write real names in the blanks. A step with no owner is not a process yet.

Trigger (RAISE)

• Resignation or exit. HR logs the exit date, and the workflow asks the HOD whether the seat should be replaced, changed or closed. Replacement is a decision, so it should not start by default.
• New seat. A manager raises a req through one form. A request by chat, email or in the corridor gets pointed to the form.
• Contract to permanent. A fixed-term or contract role that someone wants to convert raises a req like any other.
• Project or seasonal need. Short-term hires get a req with an end date.
• Agency or job board activity with no req ID. Someone spots an ad or an agency brief that does not match any open req. Most firms miss this one.
• Rule: one intake path and one req ID per seat. Hiring three of the same role is three seats on one req, each counted against the plan.

Once a req ID opens, it starts at RAISE and any ad or agency brief for that role sits on POST HOLD.

Extract (COST)

• From the request: role title, department, reporting line, new seat or replacement (and for whom), reason in two or three sentences, location, full or part time, contract or permanent, target start date, proposed salary band, and the job description or a link to it.
• From the headcount plan: approved seats for that department this year, seats filled, seats open on other reqs, and whether this seat is in the plan.
• From payroll or HR records, for a replacement: the leaver's grade and exit date. Their pay stays in the restricted folder and the summary shows only whether the new band is above, the same or below.
• Cost build, monthly, at the top of the band: salary, employer CPF if a local hire, SDL, levy if a work pass is possible, any contractual bonus or allowance spread monthly, and one-off costs (agency fee, equipment, software seats). The rates come from the official pages above and live in one rates tab that finance updates.
• File to a restricted Drive or SharePoint folder: `YYYY-MM-DD_dept_role_REQ`. The summary for signers carries the cost and the reason, while personal details stay in the folder.
• Flags as fixed reason codes: `NOT_IN_PLAN`, `OVER_DEPT_SEATS`, `GRADE_UP_ON_REPLACEMENT`, `BAND_ABOVE_GRADE`, `BAND_TOO_WIDE` (maximum more than two times the minimum), `NO_JD`, `WORK_PASS_POSSIBLE`, `AGENCY_ENGAGED_EARLY`, `AD_LIVE_NO_REQ`, `START_UNDER_30_DAYS`, `CONTRACT_TO_PERM`, `RELATED_PARTY_CANDIDATE`.

`BAND_TOO_WIDE` matters even for a role you expect to fill locally. If the req might later need an EP or S Pass, MOM's two-times rule applies to the ad, and changing the salary after posting means a new ad and another 14 days.

Route (by tier)

These tiers are examples to show the shape. Put your own names, grades and thresholds in.

• Tier 1: HOD confirms, finance manager approves. A like-for-like replacement at the same grade, inside the department's plan, band within the grade, no flags.
• Tier 2: HOD confirms, finance manager costs, director approves. Any new seat that is in the plan, a replacement with `GRADE_UP_ON_REPLACEMENT`, or a band at the top of the grade.
• Tier 3: director approves with finance's written view attached. `NOT_IN_PLAN`, `OVER_DEPT_SEATS`, `BAND_ABOVE_GRADE`, `WORK_PASS_POSSIBLE` (so finance can check quota headroom and the levy), `RELATED_PARTY_CANDIDATE`, or a role reporting straight to the director.
• The requester never signs their own req. If the HOD is the requester, the next level up confirms the need.
• Missing information goes back to the requester as Needs information. Nobody fills a band or a reason in for them.

Human gate (SIGN)

• The HOD confirms the need: the work is real, it cannot be covered by changing the team's load, and the job description describes the actual job. For a replacement, they confirm whether the role should stay the same.
• Finance confirms the money: the seat is in the plan or has a funding line, the monthly cost is right, and the start date fits the budget period. For `WORK_PASS_POSSIBLE`, finance records the quota headroom it checked in WP Online and the levy it added.
• The director signs tier 2 and tier 3, and any req with a written objection from HOD or finance.
• Each signer records Approved to post, Approved for later (with a date), Sent back (with what to change), or Rejected. A thumbs up in chat, or silence after a reminder, does not count as a signature.
• Approval locks the band, the job description version and the number of seats. A change to any of them after approval goes back to SIGN as a new version of the same req ID.
• Automation may collect, look up, calculate, flag, file, route, remind and escalate once. It does not decide whether a role is needed, set or change a band, sign a req, or lift a POST HOLD.

Handoff to recruiting (APPROVED TO POST)

• The posting pack is the approved req: req ID, role title, approved job description, approved band, seats, target start date, and the recruiter or HR owner.
• Before an ad goes live, HR checks it against TAFEP's job advertisement guidance. Words from the req such as "foreigners welcome" or "S Pass quota available" stay out of the ad, along with ages and genders that are not genuine job requirements.
• If the req carries `WORK_PASS_POSSIBLE` and the firm is not exempt, the ad goes on MyCareersFuture, stays open for at least 14 consecutive days, shows the approved band (maximum no more than two times the minimum), and no offer is made in that window. The start date on the req should allow for this.
• Every ad and agency brief carries the req ID. An agency gets a brief only after APPROVED TO POST, and only from the named HR owner.
• An offer inside the approved band goes ahead under your normal offer process. An offer above it comes back to SIGN with the reason.
• When an offer is accepted, the req is marked Filled and the hire moves to onboarding. Unfilled seats on a multi-seat req stay open.

Tracker

• One Sheet, or one view in your HR system, that the backup can open without the primary's laptop.
• Reqs tab: the columns listed in Build 2 below.
• Req statuses: Draft / Needs information / Costed / Awaiting HOD / Awaiting finance / Awaiting director / Approved to post / Approved for later / Sent back / Rejected / Withdrawn.
• Ad and brief statuses: POST HOLD (req not yet approved) / Posted / Shortlisting / Offer out / Filled / Cancelled.
• A weekly match of live ads and agency briefs against approved req IDs. Anything with no ID becomes `AD_LIVE_NO_REQ` and goes to the HR owner.
• Any req waiting more than your agreed number of working days at one signer pings that signer and their backup once.

Worked example (illustrative numbers only)

This example is made up to show the mechanics. The company, people and figures do not come from any client.

A building-services contractor with about 60 staff has a headcount plan agreed in January. HR executive Wei Ling owns the queue, finance manager Suresh costs every req and approves tier 1, and the director signs tiers 2 and 3.

In the same week two reqs come in. The first replaces a site admin executive whose last day is six weeks out. Her project manager raises REQ-0412 at the same grade with a band of S$3,800 to S$4,600. The workflow finds the seat in the plan, shows the band inside the grade, and costs the top of the band for a citizen hire aged 55 or below at about S$5,393 a month (salary, plus 17% employer CPF, plus S$11.25 SDL) before any bonus. No flags, so it goes to tier 1. The projects HOD confirms on Tuesday morning, Suresh approves that afternoon, and Wei Ling posts the ad with REQ-0412 in the reference field.

The second is the operations manager's new coordinator. REQ-0413 is not in the plan, the band is S$3,500 to S$7,500, and his note says "can hire foreigner if needed". The workflow flags `NOT_IN_PLAN`, `BAND_TOO_WIDE` and `WORK_PASS_POSSIBLE`, routes it to tier 3 and puts the agency brief he had already drafted on POST HOLD with `AGENCY_ENGAGED_EARLY`. Suresh adds a scenario line with the S$650 monthly S Pass levy and notes the quota headroom he checked. The director asks for a narrower band and a job description, then approves it for next quarter. When Wei Ling drafts the ad she takes out "S Pass quota available", which the manager had copied from his note.

That is the shape (trigger, extract, route, human gate, tracker) you buy as a service. If a vendor cannot walk your hiring requests through those five steps, they are selling a stack.

Where AI helps and where a person must decide

AI earns its place here in the reading and writing around a decision. It can turn a manager's rambling WhatsApp into a draft req with the gaps marked, show what changed between a new job description and the last one for the same role, draft a first ad from the approved req, check that draft against the phrases TAFEP says to avoid, and write the short summary a director reads on a phone. The rules part (plan lookup, cost sum, flags, routing, reminders) needs no AI at all, and plain formulas are easier to audit.

People decide whether the seat should exist, whether a replacement should change shape, what the band is, whether the money is there, whether a work pass route is acceptable, and whether an ad is fair. A draft ad from AI still needs the HR owner to read it before it goes live, since it goes out under the company's name. Keep candidate scoring off this desk. It belongs to recruiting, after the req is approved, with its own human review.

Who signs what (and who does not)

Write the names before anyone opens a demo.

• Requester (any manager). Raises the req with a reason and a band. Never signs it.
• HOD. Confirms the need and the job description. Signs tier 1 and above as the first signer.
• HR owner. Owns the queue, the tracker and the posting pack, checks the ad, briefs agencies. Not a budget signer.
• Finance manager. Costs every req, confirms the plan and the money, signs tier 1, gives a written view on tier 3, keeps the rates tab current.
• Director. Signs tiers 2 and 3, owns the headcount plan, decides on work pass routes and related-party candidates.
• Backup. Opens the same queue with written limits. Tier 3 waits for the director or a named alternate.
• Agency. Works from an approved brief with a req ID. Not a source of approvals.
• Automation. Collects, looks up, costs, flags, routes and reminds. Not a signer, and the management group chat is not one either.

Small firms combine roles, which is fine when it is written down. In a 25 person company the director may be HOD and approver for the same req. Then finance's costed view is the second pair of eyes.

A form, a Sheet and your payroll system vs an HR system with requisitions

Most SMEs that hire a few times a quarter already have a payroll system, Google Workspace or Microsoft 365, a shared HR mailbox and a budget spreadsheet somewhere in finance. What they lack is one place showing open reqs, who has signed, what each seat costs and which ads belong to which seat.

Stay on a form, a Sheet, your payroll export and email or Telegram reminders when you open tens of roles a year, one entity does the hiring, and the director can sign in one sitting. Check two things first: whether finance can share the headcount plan as a tab the workflow can read, and whether HR can export current headcount by department from payroll each month.

An HR system with requisitions and applicant tracking earns its seat when a consult shows the light stack cannot cope: several entities, grades and bands already kept in the HR system, high volume hourly hiring, or reqs, offers and onboarding that need to live in one record. Write the runbook first anyway, because a requisition module will route a req to whoever you configure, the requester included.

A partner maps your live flow, builds the smallest working version in tools you already use, trains HR, finance, the HODs and the backup, and stays reachable when the plan or the rates change. A vendor sells seats and leaves "boss said ok already" as the real desk.

Steal-this-build DIY (stops before judgement)

The same shape works in Zapier, Make, n8n or Apps Script, with Google Forms or Microsoft Forms, a Sheet, Gmail or Outlook, Drive or SharePoint, and a payroll export. These builds collect, look up, cost, flag, route, remind and escalate once. They do not decide whether a role is needed, set a band, sign a req or release a POST HOLD.

Where these four stop

Stop and talk to a partner when the next sentence is: auto-approve replacements at the same grade, let AI set the salary band, score or rank candidates inside the req flow, post ads to job boards automatically on approval, or roll this out across several entities with different plans.

Failure modes worth designing against

Faster reqs help only if each seat still carries a name and a number.

Replacement by reflex. Someone resigns and the seat refills at a higher grade with the same job description from 2021. Ask the HOD to confirm whether the role should change, and flag `GRADE_UP_ON_REPLACEMENT`.

The band lives in chat. The director said "around four plus" in the corridor. The ad shows one range, the agency quotes another and the offer goes above both. Lock the band at approval, and send any offer above it back to SIGN.

Agencies first, approvals later. A manager briefs an agency before the req exists. Depending on the agency's terms, the firm can owe a fee for a role it then decides not to fill. Agencies get briefs only from the HR owner, with a req ID.

The ad copies the req. Internal notes such as "can hire foreigner" or "prefer someone young and energetic" end up in the public ad. TAFEP lists both kinds of phrase as ones to avoid, and MOM will reject pass applications linked to discriminatory ads. Draft the ad from the approved job description, then check it before posting.

The 14 days were not in the plan. A role that may need an S Pass gets a start date three weeks out, which was never realistic once you count the MyCareersFuture minimum and the no-offer window. Build the advertising window into the req's start date.

No backup. The director is overseas and four reqs wait two weeks. Name the backup and their limits; the leave-cover runbook below is the overlay.

Hard stops: no ad or agency brief without an approved req ID, no requester signing their own req, no band change without a new signature, no offer above the band without a new signature, no internal notes in public ads, one escalation then stop, backup limits written down.

Consult, build, train (lightly)

Three phases are enough.

Consult. Walk the last six months of hires and resignations with HR, finance and one or two HODs. Note who asked, who agreed, what band was used and where the ad came from, and compare that with the headcount plan if one exists. Leave with a yes or no and a scoped runbook. If the real gap is onboarding paperwork or candidate screening, we will say so and point you to that desk.

Build. One form, one Sheet and one routing flow in tools you already use, run alongside the current habit for the next three or four reqs. SIGN and POST HOLD stay with named people.

Train. HR, finance, the HODs and the backup can each explain any row without the builder on the call. Smoke test: raise a fake req that is not in the plan with a band wider than two times, and check that it gets the right flags, goes to the director, and blocks the agency brief. Add a second entity only after the first is trusted.

What to do this week and what to ask vendors

This week (no new software)

• Pick one way to raise a req and tell every manager and the director that hiring starts there.
• Ask finance for this year's headcount plan by department, even if it is a rough list.
• Write down your tiers: which reqs the finance manager can sign and which go to the director.
• Tell your agencies that briefs come only from HR with a req ID.
• Read TAFEP's job advertisement page with whoever writes your ads, and add the 14 days to any start date that may need an EP or S Pass.

Before you buy anything

• Can they walk RAISE, COST, SIGN and POST HOLD without a product slide?
• Does the req lock the band, and what happens when someone changes it after approval?
• Can the requester be stopped from approving their own req?
• Who opens the queue when the director is away, and with what limits?

Red flags in a demo

• "One-click approval" that also posts the job everywhere.
• AI that suggests salary bands with no source you can check.
• Candidate scoring bundled into the approval step.
• Requisition history that cannot be exported.
• Leave cover "in phase two".

FAQ

Does a replacement hire really need approval if the seat is already in the budget?

Yes, a quick one. The HOD confirms the role should stay the same and finance confirms the cost still fits. Tier 1 can be signed in a day, and it is the moment to ask whether the job has changed since the last hire.

Who should raise the requisition, the HOD or HR?

The manager who needs the person raises it, because they can explain the work. HR owns the queue and the posting pack, finance costs it, and the director signs what is new or outside the plan.

Our company has fewer than 10 employees. Do we still need to advertise on MyCareersFuture?

MOM lists companies with fewer than 10 employees as exempt from the MyCareersFuture advertising requirement for EP and S Pass applications. MOM still expects fair hiring, and it encourages employers to advertise there anyway. A two-line req is still worth having so the band and the reason are written down.

Can AI write our job descriptions and ads from the requisition?

It can draft them, which saves time. A person still checks each draft against the approved req and TAFEP's guidance before it is published, since the ad goes out under your company's name.

Related runbooks

• Employee onboarding paperwork: the hire pack after an offer is accepted
• Employee onboarding software: buying an onboarding system vs building a workflow
• Purchase requisition approval: the same request, cost and sign pattern for assets
• Expense approval: written approval rules and one queue for claims
• Leave cover for SME workflows: backup design for the director and finance signers

Bring your last five hires to a consult

If hiring still starts with a corridor "ok, go ahead", agencies hear about roles before finance does, or nobody can say what band the last offer was approved at, bring your last five hires and your headcount plan to a free consult. We will map RAISE, COST, SIGN with you, write down who signs each tier and who covers when they are away, and tell you plainly whether a form, a Sheet and your payroll export can carry it. No feature tour first, and no invented case-study numbers.

Book a free consult

Sources

• TAFEP: Tripartite Guidelines on Fair Employment Practices (recruit and select on merit)
• TAFEP: Guide to writing fair job posts and advertisements (phrases to avoid, including work pass and quota wording)
• TAFEP, 18 May 2026: Fair recruitment practices for employers in Singapore: preparing for the Workplace Fairness Act (job analysis, ad vetting and approval, records kept at least one year)
• MOM: Fair Consideration Framework
• MOM: Consider all candidates fairly before you apply for an Employment Pass and for an S Pass (14 consecutive days on MyCareersFuture, salary range rule, new ad on changes, exemptions)
• MOM: S Pass quota and levy requirements (S$650 monthly levy since 1 September 2025; S Pass sub-quota by sector)
• MOM, 4 November 2025: Workplace Fairness (Dispute Resolution) Bill press release (aim for the Act to take effect in end-2027)
• MOM, 27 February 2026: Written answer to PQ on making workplaces happier (implementation in end-2027)
• CPF Board: How much CPF contributions to pay (rates from 1 January 2026) and Skills Development Levy
• Singapore Statutes Online: Personal Data Protection Act 2012, section 24 (protection of personal data)

← Back to Blog