Zema is an Ethiopian and Eritrean community platform, initially serving users in the United Kingdom. The application provides marketplace listings, messaging, and a dating channel.
Depending on how you use Zema, the application may receive your email address, name, date of birth, profile details, home city, country, listings, posts, prices, descriptions, photos, dating profile information, preferences, prompts, messages, reports, blocking or safety-related information, and information included in a support request. If you choose to add a trusted contact to a dating profile, the application stores that contact's name and email address.
The codebase does not verify whether Zema collects IP addresses, browser or device information, usage information, cookies, or similar technologies. These practices are [NEEDS CONFIRMATION].
Information is used in the application to create and manage profiles, display marketplace listings, provide the dating channel, enable messaging and matching, process likes, support blocking and reporting, review dating profiles, send trusted-contact notifications when configured, and process subscription checkout and subscription status. The application may also use information to operate and secure these features. Any additional purposes are [NEEDS CONFIRMATION].
Marketplace listings can be read publicly in the application, and listing photos are stored in a public Supabase Storage bucket. Dating profiles are loaded for signed-in users and are intended to appear after review. Dating profiles may contain a display name, photos, city, bio, faith, languages, preferences, and prompt answers. Messages are loaded for the users participating in the relevant conversation. Zema cannot control what another user copies or shares outside the application.
Users can like dating profiles and can block or report profiles, listings, and conversations. The application is designed so blocking is mutual: the affected users should not see each other's profile or message each other. Reports are submitted to the application and can be accessed through the administrative reporting tools. The exact review, investigation, and retention process for reports is [NEEDS CONFIRMATION].
When a user starts a new dating conversation and has a trusted contact email, the application records a notification and may send a one-time email through the configured email service. The email says that the user started chatting with a new match and does not include conversation details. Delivery is not guaranteed, and this feature is not an emergency service or a guarantee of personal safety.
Zema uses Supabase for authentication, database access, and storage, including dating photos and marketplace photos. The application uses authentication and database access policies to control access to some information. The codebase does not verify all security measures or provide a guarantee of security. Any additional protection practices are [NEEDS CONFIRMATION].
Zema uses Stripe for subscription checkout. The checkout route sends the user's email and Zema account identifier to Stripe and receives a checkout URL; the codebase does not show Zema storing full payment card details directly. Zema may use Resend for trusted-contact emails when a Resend API key is configured. Other third-party providers or sharing practices are [NEEDS CONFIRMATION].
The codebase does not define complete retention periods or an account deletion process. Those details are [NEEDS CONFIRMATION]. Requests about deletion should be sent to [Support Email].
The specific privacy rights available to Zema users and the process for exercising them are [NEEDS CONFIRMATION]. For privacy questions or requests, contact [Support Email].
The dating setup requires a date of birth on file and displays an 18+ only requirement. Whether the wider Zema service is intended for or available to children under 18 is [NEEDS CONFIRMATION].
How Zema will notify users about changes to this Privacy Policy is [NEEDS CONFIRMATION]. Zema's legal entity name, registration number, physical address, and privacy contact are [NEEDS CONFIRMATION]. The current privacy contact placeholder is [Support Email].