Google Drive API policy compliance and approval requirements for Mlesmida’s optional, user-controlled, end-to-end encrypted backup and cross-device sync

Hi! Mlesmida is a local-first note/knowledge-map app (Web, Android). Optional sync of the user’s own app data between their devices to their own Drive via drive.file only; no developer-side storage; client-side E2E encryption; user-initiated, with versioned snapshots and restore. Does this fall under “Backup of user or app content from a developer’s app or project to Drive” (Drive API ToS and Workspace API policy)? If yes: which team handles express prior written consent, and what is the submission route for an independent developer without paid support? This is not an OAuth verification question.