How our systems guard payroll, national IDs and money

A Ministry of Youth & Sports club keeps its members’ records, payments, payroll and accounts in a system we built. This page lists what stops the wrong person from seeing or changing them.

Who can see it, who changed it, who approved it

  • Who sees what

    • Permissions per role, down to each action
    • Each user limited to their own branch and data
    • National IDs, salaries and contact details masked by role
    • An access matrix management can review
  • Accountability

    • An Audit Log of every create, change and delete
    • The value before and after, kept for every change
    • Who did it and when, on every record
  • Money

    • A second approval on refunds, transfers and payments
    • Every payment taken inside a treasury session
    • Every payment posts its own journal entry
    • Double-entry books with period closing and a trial balance
  • AI with guard rails

    • The assistant reads the database and never writes to it
    • Each query checked against the asking user’s permissions
    • Every query it runs is logged
  • Separation

    • A separate application and database for each client
    • Hosted on our servers or on yours
  • Operations & contracts

    • Private source control for every project
    • Backups and monitoring on the systems we host
    • An NDA signed before we see your data

What happens to one payment

In the ERP we built for a Ministry club, a payment is taken inside a treasury session, posts to the ledger by itself, and leaves a record of who took it, when, and what changed. A refund or a transfer waits for a second approval before it happens.

Approval workflows in an ERP built by AL-Arcade

What people ask before they send a brief

Can you handle sensitive and government data?

Yes. A club affiliated with the Ministry of Youth & Sports keeps its members’ personal records, payments, payroll and accounts in our system, behind role permissions, an Audit Log and approval chains.

Can the AI assistant see salaries?

Only if the person asking can. The assistant reads and never writes, every query is checked against that user’s permissions, and every query is logged.

Is our data shared with other clients?

No. Each client runs on its own application and its own database.

Can we host the system on our own servers?

Yes. We can host and run it for you, or deploy it to your own servers.

Do you sign an NDA?

Yes. We sign it before we see your data or documents.

Who can see what inside the system?

Exactly what their role allows. Permissions are set per role and per user, and every change lands in the Audit Log.