Medevo · Last updated 25 July 2026
When you create an account we collect your name, phone number, date of birth, and governorate; if you sign in with Google we also receive your Google email address. (Phone sign-in uses a private internal identifier derived from your number, not a real email address.) When you build a CV we store the job title, skills, experience, education, languages, and the optional CV PDF you generate. When you post an ad we store the job title, description, category, area, salary range, and an optional tail image. When you post a marketplace listing we additionally store the business details you enter (see “Marketplace listings” below). We also collect a coarse device location (used only for "Jobs Near Me") and standard server logs (IP address, request time, error codes).
We use your data only to operate Medevo: matching you with relevant jobs, delivering the application and chat flow with employers, surfacing the alerts you've enabled, providing ad insights to owners on their own ads, and processing payments for ad boosts. Optional AI-powered assists — processed server-side via Google's Gemini API in the EU region — generate ad and CV improvement tips, suggested message drafts, a short CV summary shown to an employer you applied to, on-demand translation, and search relevance. Only the specific text needed for a given assist (for example the ad text you're improving, or your CV text when a summary or search embedding is generated) is sent to the AI provider to produce that result, and the result is cached. We do not sell your data and it is not used to train third-party models.
Ads carry only a city-level area (governorate + area name) and a coarse geohash used by "Jobs Near Me". The exact location and full address are stored on a private subdoc the applicant cannot read until the poster approves their application. Until that happens, neither side sees the other's precise location.
Your live CV is stored at cvs/[your-uid]/cv.pdf. When you apply to a job we freeze a snapshot at the time of application — the employer sees what you actually applied with, even if you edit your CV afterwards. Only the employer you applied to and you can read that snapshot.
If you list a pharmacy for sale or advertise for an investment partner, we store the business information you choose to enter: type and title, governorate and area, and the financial details you fill in — such as monthly income, monthly expenses, profit margin, asking price or capital required, share offered, value of stock, fixtures, outstanding debt, rent, remaining lease, floor area, and year established — plus your stated reason for selling or seeking a partner, and up to three photos of the premises. Everything you enter here is shown publicly on your listing to anyone browsing the Market tab, so only enter figures you are willing to disclose. Every financial field is optional. As with job ads, the exact pin and full address stay on a private subdoc that a buyer cannot read until you approve their application.
Some data never leaves your phone. If you start filling in a long form (post a job, post a listing, or the CV maker) and leave before publishing, we keep a local draft so your typing isn't lost — this can include a phone number or email if the form contained one. Drafts live in the app's private storage, expire after 7 days, are deleted the moment you publish, and you can clear one and stop being asked by choosing “Don't ask again” on the restore prompt. We also remember area names you type that aren't in our built-in list, so we can suggest them back to you next time. Neither is uploaded to our servers or shared with anyone. Uninstalling the app removes both.
You control four push channels independently in Profile → Notifications: application status updates, new messages, appointment reminders, and saved-search matches. Each channel can be flipped off without affecting the others. We never use push for marketing.
Ads, chat messages, and CVs are screened against a multi-language blocked-words list (English, Arabic, and Kurdish Sorani). Matches block the message or downgrade the ad to draft, and we log a moderation report for review. You can report any ad or message to us via the in-app Report flow.
Ad boosts (7 / 14 / 30 days) are paid one-time purchases via the platform store (Google Play or App Store). The store handles the payment — we receive only a confirmation and the SKU you bought. VIP membership (auto-apply) is currently disabled in this build and will be re-enabled when payments ship; we'll update this policy before it does.
You can request account deletion from Profile → Settings → Delete account. The deletion is scheduled 30 days out — you can cancel it during that window simply by signing back in. After 30 days, we remove your user doc, your CV, your saved jobs and saved searches, your viewer entries on private location subdocs, and your application and chat history. Applications you previously sent are anonymized but kept for the recipient's audit trail. If you can't access the app, you can request deletion by email instead — see Delete your account.
To keep the app stable and improve how it works, we use Firebase Crashlytics and Firebase Analytics. Crashlytics receives a stack trace and device info when the app crashes — no message bodies, no CV content, no personal information. Analytics records anonymous funnel events (e.g. an account was created, an ad was viewed, a search was run, a message was sent) tied to your Firebase user id; we never send names, phone numbers, emails, search terms, or message contents. Collection is disabled in debug builds.
Reach us at medevo.iq@gmail.com for anything not covered here.