Audit requests
Forms collect the minimum useful brief: name, company, website, market, service lane, budget posture, WhatsApp, and message.
Privacy
Digital Motivo uses a PDPL-aware intake posture: minimal fields, visible routes, and no private files before the right confidentiality path.
Handling board
Audit requests
Forms collect the minimum useful brief: name, company, website, market, service lane, budget posture, WhatsApp, and message.
local inbox
If no webhook is configured, submissions are written to a server-side local inbox JSONL file for operator review.
WhatsApp links open a buyer-controlled thread and may include a short route label so context is not lost.
retention
Lead records are kept only while the request is being reviewed, scoped, exported, or needed for active correspondence.
What we collect
Audit and contact forms are built to identify the buyer pressure, service lane, response route, and follow-up owner. They are not a place for confidential files.
Forms collect the minimum useful brief: name, company, website, market, service lane, budget posture, WhatsApp, and message.
If no webhook is configured, submissions are written to a server-side local inbox JSONL file for operator review.
WhatsApp links open a buyer-controlled thread and may include a short route label so context is not lost.
Lead records are kept only while the request is being reviewed, scoped, exported, or needed for active correspondence.
Send public URLs, screenshots, deadlines, and market context first. Private tender files, analytics exports, client lists, credentials, and legal material should wait for an NDA or agreed secure handoff.
No sensitive documents are required before scope fit.
NDA and SoW paths are available before private project material is shared.
Arabic public copy stays gated until native review signs off.
Analytics and attribution are planned around declared business purposes.
Contact