Skip to content

Koraku RealtyReal estate & privacy-first AI

Contact

Koraku Realty · Tokyo

In development

Privacy-first AI workflows for Japanese real estate.

PrivaGate AI is being developed to help real estate teams use Claude with permission-aware retrieval, local disclosure controls, and human-reviewed document workflows.

How it works
Real estate services

Planned privacy boundary

  1. LocalCustomer-controlled environment

    1. 01 Local documents
    2. 02 Authorization
    3. 03 Disclosure controls

  2. ExternalAPI boundary

    1. 04 Approved context → Claude API

    Requests that fail policy checks are not intended to cross this boundary.

  3. LocalBack inside the customer environment

    1. 05 Local validation and authorized restoration

  4. ReviewHuman accountability

    1. 06 Human review
Target architecture. In development.

PrivaGate AI · In development

A shared privacy and authorization foundation.

The planned local control layer between Japanese SME document workflows and the Claude API. EstateVault is the first industry module built on top of it.

How it works Platform overview

Real estate services · Current business

Real estate operations in Tokyo.

  • Investment consulting
  • Rental property management
  • Property search support
  • Property sales

Real estate services Company

The workflow problem

Document-intensive work needs more than a chat window.

Koraku Realty operates in document-intensive workflows where confidentiality, access permissions, and multilingual communication are everyday concerns. PrivaGate AI is being developed from these practical needs.

  • Confidential documentsLeasing, sales, and property-management files hold tenant, owner, and financial details.
  • Access permissionsNot every user may see every document. Retrieval has to follow role and scope.
  • Contextual identification riskRemoving names is not enough. Context, token shape, and other fields can re-identify a person or transaction.
  • Multilingual workJapanese and English summaries of the same source material need citations back to the source clause.
  • Human accountabilityA licensed professional confirms the result. The system never auto-issues a regulatory document.

Target architecture · In development

From a real estate question to a controlled answer.

  1. Local 01

    Local ingestion & authorization

    The local layer confirms user identity, role, and document access before any retrieval happens. Only the minimum set of authorized documents is returned.

  2. Local 02

    Local disclosure controls

    Sensitive fields are redacted or replaced with reversible tokens. Originals, tokens, and restoration keys stay inside the customer environment. The minimized payload is checked against the configured disclosure policy.

  3. External 03

    Claude API processing

    Claude is the planned cloud reasoning engine. Only policy-approved, minimized context is sent through the official Claude API.

  4. Local 04

    Local validation & review

    Responses are checked for structure, source support, and disclosure risks. Restoration of original values is a separate authorization step. A licensed professional confirms the result.

Requests that fail policy checks are not intended to cross the external API boundary. This describes design intent only. Concrete data handling depends on the deployment and the service contract.

Read the full architecture and data flow or the security and privacy approach.

See the disclosure flow on synthetic data.

Concept illustration Synthetic data Browser-only

Illustrative example — not a live product response. No Claude request is made.

  1. A Tokenization (local)
  2. B Policy check (local)
  3. C Restoration (separately authorized; not performed here)

Synthetic source

Tenant name:  Yuki Tanaka-SYNTH
Contact:      tenant-001@example.invalid
Address:      1-1-1 SYNTHETIC_ADDRESS_001
Income:       JPY 6,200,000 / year (synthetic)
Co-signer:    SYNTHETIC_REF_42

Minimized context tokenized, not yet approved

Tenant name:  NAME:TENANT_001
Contact:      EMAIL:EMAIL_001
Address:      ADDRESS:ADDR_001
Income:       FINANCIAL:INC_001
Co-signer:    IDENTIFIER:REF_001

Policy result illustrative

  • Allowed Address (tokenized)
  • Blocked Income-to-rent ratio: not authorized for cloud context

Rental application received. Income-to-rent ratio and identity references are sensitive and are not sent without explicit authorization.

Open the interactive concept

Why a real estate company

Built from document-intensive operations.

Koraku Realty operates in document-intensive workflows where confidentiality, access permissions, and multilingual communication are everyday concerns. PrivaGate AI is being developed from these practical needs, with EstateVault as the first industry module.

In the real estate business today

  • Leasing and sales
  • Property management
  • Multilingual communication with counterparties

Planned in PrivaGate AI

  • Permission-aware retrieval
  • Local disclosure controls
  • Human-reviewed output, reusable beyond real estate

Read the company and product origin story.

Development stages

What exists today, and what is planned.

  1. NowArchitecture & evaluation design
  2. NextMinimal permission-aware gateway and synthetic-data evaluation
  3. ThenEstateVault validation in internal workflows
  4. LaterPlanned expansion marketsProfessional offices, dental clinics, pharmacies. Planned only; none is a customer or a deployed module.

No dates or completion percentages are published.

Contact

Interested in becoming a design partner?

Useful information is general: the kind of documents your team handles, who may see them, which steps need a human reviewer, and which languages are involved. Describe the workflow in general terms.

Please notePlease do not send confidential documents or personal data of third parties.

Request a workflow conversation