← Back to blog Data & Trust

Connecting your HRIS: what we actually need (and what we do not)

February 26, 2026 7 min read Farha editorial
🔗

IT and HR are right to ask hard questions before another tool touches employee data. Too many products grab fields “just in case.” We took the opposite approach: if it does not help get a safe, on-time delivery to the right person, we do not want it.

Fields you might share

Usually that means a name, birthday, hire date, and where the gift should land (office or home address). If you want, you can add dietary notes or allergies so kitchens know what to avoid. A phone number or email helps when the driver needs a quick handoff.

We do not need salary, bank info, or review scores to run celebrations. If someone asks for that for this use case, push back.

How this fits Jordan’s privacy law

Jordan’s Personal Data Protection Law No. 24 of 2023 is built around plain ideas: be clear about why you collect data, collect only what you need, and keep it secure. We keep records of how we process data, restrict internal access, and follow your instructions when someone asks to see, fix, or delete their information. The exact legal role (processor vs joint controller) depends on how you deploy Farha with your organisation, and we spell that out in contract, not in marketing fluff.