Privacy infrastructure
Separating inspection, policy, transformation and recovery into explicit security boundaries.
Research & Engineering
Our technical work connects privacy architecture with structured decision research, while keeping implementation evidence separate from future goals.
Areas of work
We describe the technical direction publicly without exposing confidential implementation details or claiming results we have not qualified.
Separating inspection, policy, transformation and recovery into explicit security boundaries.
Studying Choice, Score and Noul decisions with typed outputs and meaningful probabilities.
Planning evaluation for Darija, Arabic and Latin scripts, mixed-language inputs and Moroccan context.
Comparing decision-focused approaches and measuring latency, memory and cost before claiming advantages.
Keeping sensitive processing and recovery within configured boundaries while controlling external destinations.
Tracking data provenance, grouped splits, calibration and experimental evidence to make future claims defensible.
Engineering philosophy
Model confidence is information.
Policy is authority.
A detector may classify data and express uncertainty. A privacy system decides what the application is allowed to do with that data, under explicit policy.
That separation keeps research progress from silently broadening access or weakening a processing boundary.
Explore PrivacyGuard architectureEvidence before scale
Claims about model quality, efficiency and reliability require more than a successful demonstration.
Track provenance and intended-use rights. Keep evaluation splits resistant to leakage.
Test typed decisions, uncertainty, boundary cases and context changes.
Evaluate Darija, scripts and mixed inputs separately. Do not infer support from an encoder.
Measure reliability, privacy boundaries and performance in the environment being claimed.
Let’s build what comes next
Contact us about research collaboration, technical partnerships or future engineering opportunities.