Firebase + Twilio backend integration for a finished FlutterFlow app (iOS)

Scope of work (fixed) 1. Firebase setup — create/configure the project under my firm-owned account, enable Authentication and Firestore. 2. Database structure — create the collections per my spec: users (first name, last name, email, phone, consent, A-number, language, created date), a recipients subcollection, and an alerts collection. 3. Security rules — users can read/write only their own data; alerts written via Cloud Function only. Data minimization matters (see note below). 4. Wire the existing registration screen to save name / phone / email to users on submit (consent-based; the screen and consent UI already exist). 5. In-app account deletion — delete the user's Firestore data + Auth record (Apple requires this). 6. SOS engine — a Firebase Cloud Function that sends SMS via Twilio when SOS is pressed: text each saved recipient + notify the firm, include the user's captured GPS location as a map link, and log an alerts record. Wire the app's existing "Alert my people" button to call it and pass location. 7. Leads dashboard — a simple authenticated web page listing registered users (first name, last name, email, phone, sign-up date) with CSV export. List + export only; no CRM features needed. Out of scope: any UI/screen design, navigation, or content — all done. Encounter audio/video recording (v2). Android (later). What I provide • The finished FlutterFlow project (I'll grant access) • A detailed build spec (data model, cloud function outline, permissions, App Store requirements) • All content and branding • My Apple Developer + Firebase accounts (firm-owned)Required experience • Firebase: Firestore, Auth, Cloud Functions, security rules • Cloud Functions calling Twilio for SMS — this is the critical skill • Integrating a backend into an existing FlutterFlow project • Understanding of iOS constraints around messaging (see note) Critical technical note (please address in your proposal) Please confirm you understand that iOS cannot send SMS silently in the background, so the SOS messaging must be dispatched server-side (Cloud Function → Twilio), not from the app directly. Proposals that describe the app texting contacts directly will not be considered. About the users (please read) Users are often undocumented or mixed-status people. Data minimization, encryption, and transparent consent are requirements, not options. No covert or undisclosed data collection. I need someone who takes this seriously. To apply, include 1. Links to 1–2 apps where you integrated Firebase/Twilio (App Store links if possible) 2. A brief description of a Cloud Function you wrote that called an external API (Twilio or similar) 3. Your fixed-price quote and timeline for the scope above 4. Any questions about the spec