AYE Market is deliberately built on a small set of infrastructure services rather than a patchwork of SDKs. Here is the complete list — if a service isn't on this page, the app doesn't use it.
Google Firebase (core infrastructure)
Firebase is Google's application platform and forms AYE Market's entire backend. Data processed by Firebase is governed by Google's Firebase Privacy documentation.
| Firebase service | What it processes | Why |
|---|---|---|
| Authentication | Email address, phone number, or Google account identity; password hashes; sign-in metadata | Creating and securing your account |
| Cloud Firestore | Profiles, listings, chats, job posts, applications, reviews, reports, payment requests, privacy requests | The app's database |
| Cloud Storage | Listing photos, profile/cover photos, chat images, CVs, verification documents, payment receipts | File storage with per-path access rules |
| Cloud Messaging (FCM) | A per-device push token | Delivering push notifications |
| Cloud Functions | Server-side processing of the data above | Payment approval effects, notifications, moderation automation, account deletion cascade |
Google & Facebook Sign-In
Optional sign-in methods. If you choose one, that provider shares your name, email address, and profile photo with the app to create your account. If you sign up with email or phone instead, neither is ever involved. Governed by Google's Privacy Policy and Meta's Privacy Policy respectively.
Google Play Billing
Google Play's in-app purchase infrastructure is integrated in the app. Today, Premium purchases run through our manual payment flow instead (receipt upload + admin review) — Play Billing processes no payment data for AYE Market unless/until that path is used, in which case Google handles the transaction under its own terms.
WhatsApp, phone & SMS deep links
The Call, WhatsApp, and SMS buttons on listings simply open your device's own dialer, WhatsApp app, or messaging app with the seller's shared number (and, for WhatsApp, a pre-filled greeting mentioning the listing). AYE Market:
- never sees, stores, or transmits the content of those calls or messages;
- never accesses your contacts, call log, or SMS inbox;
- shows those buttons only when a seller has chosen to share their number and enabled those channels.
Your use of WhatsApp is governed by WhatsApp's Privacy Policy; calls and SMS by your carrier's terms.
Maps & location
Listing locations use Tigray's administrative hierarchy (region → zone → wereda → tabiya) from the app's own location database, plus optional GPS from your device (with your permission) for nearby search and map pins. Map tiles are rendered via the map component embedded in the app; no location history is shared with any advertising or analytics service.
What we deliberately do NOT use
- No third-party analytics SDKs (no Google Analytics for Firebase, no Mixpanel, etc.) — usage measurement is limited to first-party counters like listing view counts.
- No crash-reporting SDKs currently (no Crashlytics/Sentry). If one is added to improve stability, this page and the Privacy Policy will be updated first.
- No advertising networks or tracking SDKs — the app contains no third-party ads.
- No advertising or tracking social SDKs — Facebook Login is used only as an optional sign-in method (see above); no Facebook/Meta ads or tracking pixel is present anywhere in the app.
- No data brokers — we never share data with data resellers.
This website
These pages are statically hosted. The Account Deletion and Privacy Rights pages load the Firebase Authentication and Firestore web SDKs (from Google's CDN) so you can sign in and submit requests — the same Firebase project the app itself uses, under the same security rules. The optional Google Fonts preconnect on some pages loads font files from Google's CDN.