This policy explains what Kiray collects, why, who it is shared with, and how to get it deleted. It describes the mobile app and the service behind it.
What we collect
Information you give us
| Data | When | Why |
|---|---|---|
| Full name | Registration | Identifies you to people you contact about a listing |
| Phone number | Registration or phone sign-in | Sign-in, and verification before you may publish a listing |
| Email address | Optional, at registration | Sign-in and account recovery |
| Password | Registration | Stored only as a one-way hash; we cannot read it |
| Profile photo, bio, city | Optional, any time | Shown on your public profile and your listings |
| Listing content and photos | When you publish | Displayed publicly in search results and on the listing page |
| Messages | When you contact another user | Delivering the conversation |
| Reviews, reports, bookings, moving orders | When you use those features | Operating the feature |
Identity verification documents
If you choose to verify your identity, we store the images you submit — which may include an identity document and a selfie — and the resulting status. These are sensitive, are used only to confirm you are a real person, and are not shown to other users. Verification is optional; you can use Kiray without it, though some features require a verified phone number.
Collected automatically
- Approximate and precise location, only while the app is open and only if you grant permission — to show nearby rentals and to place a listing on the map. You can refuse and still search by city, sub-city and woreda.
- Device notification token, with platform, app version and a device identifier, so we can send you push notifications.
- Usage events — which screens and listings you open, what you search for, and how long you spend on a listing — used to rank and recommend listings.
- Advertising identifier, used by Google AdMob to serve ads.
- Technical logs, including IP address, needed to operate the service and to enforce rate limits and abuse controls.
- Crash reports, when the app fails: the error and where in the code it happened, your device model and OS version, the app version, and a short trail of the screens you visited and requests the app made just beforehand. If you are signed in, your account identifier is attached so we can follow up if you contact us. Passwords, one-time codes and authentication tokens are stripped out before a report leaves your device. We do not record your screen.
Camera, photos and location permissions
The app requests the camera and photo library only to attach images to a listing or your profile, and location only for the purposes above. Denying any of these leaves the rest of the app working.
Who we share it with
We do not sell personal information. We share it only with the providers needed to run the service:
| Provider | What it receives | Why |
|---|---|---|
| Convex | Account, listing, message and activity data | Database |
| DigitalOcean Spaces | Uploaded images | Image storage and delivery |
| Google Maps Platform | Coordinates and place queries | Maps, geocoding and address lookup |
| Google Gemini | A listing's area and nearby landmarks | Generating a written description of the area. No account or contact details are sent. |
| Google Sign-In / Apple Sign-In | Your provider account identifier | Optional social sign-in |
| SMS provider (AfroMessage or httpSMS) | Your phone number and a one-time code | Phone verification |
| Firebase Cloud Messaging | Your notification token | Push notification delivery |
| Google AdMob | Advertising identifier | Advertising |
| Sentry | Crash reports: the error and code location, device model and OS, app version, and your account identifier if you are signed in | Detecting and diagnosing crashes. Credentials and one-time codes are removed before sending, and your screen is not recorded. |
Your name, profile photo, bio and listings are public by design. Your exact address is not shown on a public listing page to people who are not signed in.
How long we keep it
- Account and listing data: until you delete your account.
- One-time verification codes: minutes — they expire and are destroyed once used or after a small number of wrong attempts.
- Sign-in tokens: until they expire or you sign out.
- Messages: retained so both sides keep their conversation history.
Deleting your account
You can request deletion from inside the app, under Settings. We confirm the request with a one-time code sent to you, then remove your account and personal data. Some records may be retained where the law requires it, or in de-identified form that is no longer linked to you.
Security
Passwords are stored only as one-way hashes. Traffic between the app and our servers is encrypted in transit. Verification codes are stored hashed and are compared in constant time. No system is perfectly secure, and we cannot guarantee absolute security.
Children
Kiray is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has given us data, contact us and we will delete it.
Your rights
You can access and correct most of your information in the app, and request deletion as described above. For anything else, contact us.
Changes
If this policy changes materially we will update the date at the top of this page and, where appropriate, tell you in the app.