Collect
State the purpose, minimum fields, audience, notice, choice, and sensitive-data boundaries.
Privacy and data
Follow the Lebanon data from collection to deletion.
Lebanon's electronic-transactions and personal-data rules, sector duties, consent, processors, transfers, security, retention, rights, and enforcement practice require local legal review.
Use
Name ownership, access roles, processors, AI use, automated decisions, and data-quality checks.
Move
List hosting locations, vendors, transfers, subprocessors, backups, and remote access.
Keep
Set retention, deletion, account closure, legal holds, audit evidence, and recovery.
Respond
Assign rights requests, security events, breach decisions, escalation, and communications.
Analytics follows the same consent analysis.
The Lebanon microsite has its own GA4 property. That separation improves reporting; it does not remove any notice or consent duty that applies to the visitor. Advertising or profiling tags require a separate decision.
Next step
Turn the Lebanon context into a workable brief.
Good remote delivery depends on explicit ownership. Name the Lebanon users, data, vendors, languages, approvals, and release constraints before estimating the build.