This project centres on a networking site that lets real-estate clients submit inquiries to one another while keeping their identities hidden from every other user. Only I, as the site administrator, need privileged access to see who submitted each inquiry so I can broker connections off-platform when appropriate. Core interaction Users land on a simple form, choose the property they’re interested in (or add one), enter the essential property details and their budget range, then hit “Send”. From the user’s viewpoint the process is entirely anonymous: no contact data, names, or e-mails are ever exposed publicly or to other members. On my side, an admin dashboard quietly logs the sender’s full profile, tags it to the inquiry and lets me filter, search, and export leads for follow-up. Key requirements • Networking site architecture, not a public marketplace • Supports only one visible action for regular users: submit anonymous inquiries • Mandatory fields in the form: Property details and Budget range • Admin-only dashboard with secure login, inquiry list, and identity reveal per record • Modern responsive UI so clients feel confident submitting information on mobile or desktop • Clean, well-commented code and database schema for future feature additions (e.g., messaging or profile viewing, which are out of scope for now) Suggested workflow After a brief kickoff call I’ll provide domain, hosting credentials, and any preferred branding. You’ll map out the data model, spin up the front end and back end (any stack you’re comfortable with—Laravel, Node, Django, or a no-code alternative—so long as it meets the privacy requirement), then deploy a password-protected staging URL for testing. I’ll verify that inquiries appear anonymous on the user side and fully attributed in the admin panel before sign-off. Acceptance criteria 1. A new user can complete and submit an inquiry in under two minutes. 2. The inquiry appears in the admin dashboard with the sender’s identity visible only to me. 3. No direct user-to-user contact information is ever displayed or exposed through the network traffic or page source. 4. Site passes basic penetration tests for data leakage. 5. Final deliverables: source code repository, brief setup/read-me, and production deployment. If this scope is clear, let’s move forward with a concise timeline and milestones so we can launch quickly. Two additional requirements: A: The website must prevent users from taking screenshots or screen recordings. B: Before viewing any property details, users must complete a multi-step confirmation process in which they explicitly agree not to forward, share, or distribute the documents and acknowledge that contractual penalties apply in case of a violation.