Legal
Privacy Policy
This draft explains the information handled by the current rahoyahaan product. It is based on the code paths inspected and should be reviewed against production configuration and applicable law.
Last updated: 16 November 2026
Information collected
When you sign in with Google, rahoyahaan receives account information made available by Google, including your name, email address, and profile image. Authentication uses Google as the identity provider. Phone number is optional and may be added to your account.
If you create or edit a profile, rahoyahaan may process profile fields such as age, profession, biography, preferred localities, budget, move-in date, gender, lifestyle preferences, visibility settings, and contact preferences. If you publish a listing, the service processes the information you enter, including accommodation details, address, pricing, availability, rules, and photographs.
The service also stores marketplace activity needed to operate the features you use, such as inquiries and their status, saved listings, reports, notifications, and information about listing image uploads. Technical request data may be processed by the hosting, database, storage, and rate-limiting services used to run the application.
How information is used
- Authenticate accounts and maintain sign-in sessions.
- Create and display profiles, listings, and search results according to visibility and publication settings.
- Route inquiries, apply contact-sharing choices, and show notifications.
- Let users manage listings and profiles, save listings, and report concerns.
- Protect the service through rate limits, moderation workflows, and operational troubleshooting.
rahoyahaan does not document analytics or advertising tracking in the reviewed application code. Production deployments and third-party infrastructure should be checked before treating this as a complete list.
What other users can see
Published listings and profiles enabled for discovery may be visible to other visitors. Profile visibility controls determine which profile fields are shown. Information entered in a listing may be public, so review it before publishing. Private account details are not intended to be displayed as public listing data.
Phone numbers and fallback contact details are optional. WhatsApp contact sharing is controlled through the product's inquiry and consent flow; do not assume that any contact detail is confidential after you choose to share it.
Storage and service providers
Application records are stored through the configured PostgreSQL database. Listing and profile images are uploaded to configured S3-compatible object storage. Google provides sign-in. These providers process information as needed to provide their services; the exact provider terms and production configuration should be confirmed by the business.
Retention and account deactivation
The application does not publish a general retention schedule. Account deactivation changes the account status, pauses published listings, and ends current database sessions; it is not the same as erasing the account or all related records. Some information may remain in the database, backups, reports, or operational records according to system behavior and any applicable retention obligations.
Data deletion timelines and backup handling have not been established in the reviewed code. They require a documented business process before a specific deletion promise is made.
Your choices and requests
You can edit profile visibility and contact preferences, remove or pause listings where available, and deactivate your account from the profile area. A dedicated privacy-request contact channel is not currently published. The operator should establish and publish a reliable route for access, correction, deletion, or other legally applicable requests.
Security and children's privacy
The application uses authenticated sessions, access checks, upload validation, and rate limiting in relevant workflows. No online service can guarantee absolute security; avoid putting sensitive information in public profiles, listings, or inquiry messages.
The reviewed product does not state an age eligibility rule or document a specific process for children's data. The business should set an appropriate age policy and publish it after legal review.
Policy updates
This policy may be updated when the product's data practices change. Material changes should be reflected here with a revised date and communicated through an appropriate channel.