The Admin Password Is Not a Handshake: Digital Custody Rules for US–Cameroon Coalitions
Photo by Photo by Ninthgrid on Unsplash on Unsplash
A term sheet can run to twenty pages and still say nothing about the one asset every partner touches daily: the group chat. In practice, a great deal of US–Cameroon collaboration is administered through a WhatsApp group with a dozen members, a Google Drive assembled by whoever had the fastest connection that month, and a Facebook page that a volunteer opened in 2021 using a personal email address. None of that appears in the agreement. All of it decides whether the partnership can function next quarter.
The problem is not that these tools are informal. Informality is often what makes cross-Atlantic work possible at low cost. The problem is that informal infrastructure acquires formal consequences. It holds beneficiary lists, price negotiations, photographs of children, minutes of decisions, and the receipts a US funder will eventually request. When the coordinator moves to Douala, changes her number, or simply stops answering, the partnership can lose its institutional memory in a single afternoon.
The remedy is not to ban the tools. It is to write down, in plain clauses, who holds the keys and what happens when hands change.
Why the group chat outlives the agreement
A memorandum of understanding typically runs for twelve or twenty-four months. A WhatsApp group, once created, has no expiry. Its members drift, its administrators accumulate, and its archive grows until it is either migrated or abandoned. US partners often assume the Cameroon-based organization maintains the digital record; the Cameroon-based organization often assumes the US funder, which set up the drive, keeps the backup. Each side is being reasonable, and each side is wrong.
Term sheets that address this usually do so with a single unenforceable sentence about "shared information." That sentence is not a governance rule. A governance rule names a role, a platform, a custodian, and a fallback.
Clause one: designate an administrator of record
The first clause should identify, by position rather than by name, the individual responsible for each platform the partnership uses. A typical set might read: the program coordinator administers the primary WhatsApp group; the finance officer administers the shared drive folder containing budgets and receipts; the communications lead administers the public social accounts.
Two details matter more than the list itself. First, each platform should have at least two administrators, one based in each country, so that a single absence does not lock the partnership out. Second, the agreement should state that administrator status is a duty of the role, not a personal privilege, and that it transfers automatically when the role transfers.
Where a platform permits it, add a named institutional account rather than a personal one. A group created under an organizational email address can be reassigned; a group created under an individual's phone number often cannot.
Clause two: separate the account from the person
This is the clause partners most often resist, and the one that saves the most trouble. Personal phone numbers in Cameroon are frequently the de facto login for messaging platforms, mobile money, and cloud storage. When a staff member departs, the institution may find that its own records left with them.
The term sheet can require that partnership accounts, wherever technically feasible, be registered to an organizational address or a dedicated partnership number that the governing body controls. Where a personal account must be used for practical reasons, the clause should record the arrangement, set a review date, and require that partnership content be exported to a shared repository on a fixed schedule, monthly is reasonable, so the account itself is never the only copy.
Clause three: write the handover protocol before you need it
Succession language should specify what actually changes hands: administrator rights, the recovery email and phone number, device passcodes where partnership-issued devices exist, the folder structure, and an index of where things live. It should also set a timeline, commonly five to ten business days for administrative access and thirty days for a complete archive transfer.
A useful companion is a short digital asset register, updated at each quarterly review, listing every platform, its administrator of record, its backup administrator, and the location of its archive. The register costs an hour to maintain and can prevent a year of reconstruction.
Clause four: state privacy expectations plainly
Group chats blur the line between professional coordination and personal conversation, and photographs of community members circulate easily. US partners bring expectations shaped by state privacy statutes and their own institutional review processes; Cameroonian partners operate within a legal framework that continues to develop, anchored in Law No. 2010/012 on cybersecurity and cybercriminality, alongside sector-specific rules. Neither side should assume the other's defaults.
The agreement need not resolve every legal question. It should, however, establish three commitments: no publication of identifiable images or personal data without documented consent; no forwarding of partnership content to third parties outside the agreed membership; and a designated contact for privacy questions on each side. Where US federal funding is involved, cross-reference the applicable data handling requirements rather than paraphrasing them.
Clause five: archive for the exit, not just for the audit
Closeout is where digital neglect becomes expensive. A US funder that has disbursed funds over three years may need to demonstrate what was spent, on what, and with whose agreement. A Cameroonian organization that intends to continue the work needs the relationships, not only the receipts.
The term sheet should specify an archive format, a schedule for export, and a custodian on each side. Plain folders, descriptive file names, and a single PDF of key decisions will outlast any platform migration. Include a clause confirming that on closeout, the Cameroon-based partner retains an unrestricted copy of all non-restricted records, and that the US partner retains only what its own compliance obligations require.
A short checklist for the drafting table
Before signature, confirm that the term sheet answers five questions: who administers each platform, what happens when that person leaves, where the backup lives, what may not be shared, and who holds the archive at the end. Partners who can answer all five in a single paragraph have done most of the work that digital governance requires.
The tools will keep changing. The obligation to name a custodian will not.