Outcome
What must a real user complete, and what evidence proves it?
Project brief
Bring enough context to define a responsible Jordan scope.
There is no intake form and no automated promise. Work through the questions below, then call or email Faith Forge Labs directly.
Enhanced pre-engagement review applies
This market is not automatically excluded, but the client and beneficial owners, payment route, banks and vendors, end users and end use, sanctions or export controls, and any required specialist advice must be verified before work is accepted.
People and place
Who is contracting, operating, approving, and using the system in or around Jordan?
Language
Current baseline: Arabic content and RTL delivery by agreement; delivery in English Who owns final content and native-language review?
Data
Current starting point: Jordan's Personal Data Protection Law and implementing practice require current review of purpose, consent or other authority, processors, transfers, rights, retention, security, and incidents. What data is actually necessary?
Commerce
Current starting point: JOD, sales tax, customer and service classification, invoicing, payment gateways, national identifiers, and hosting/provider restrictions need local professional review. Who confirms the final model?
Systems
What exists today, who owns access, and what must remain available during the change?
Timing
Jordan is normally seven hours ahead of Georgia. Who owns decisions, releases, incidents, and support outside the overlap?
Specialist review
Which questions need local legal, tax, sanctions, export, language, accessibility, security, or regulated-industry expertise?
Direct contact