Personal Information and Data Security Policy

Last updated: October 26, 2026 · In accordance with Japan’s APPI and real estate industry standards

1. Core security principles and account-free access

ELB uses an account-free ticket ID and encrypted passcode. You do not need to register an account or link a phone number, reducing the risk of credential-stuffing attacks.

2. Personal information and supporting documents collected

The system collects only the rental preferences and identity documents needed for eligibility screening, property applications to management companies, and lease procedures in Japan, including:

Applicant name and contact details (WeChat, email, phone, or LINE)
Residence status (visa), COE, and images of both sides of a passport or residence card
Proof of employment, income, or enrollment

3. Storage security and access controls

Identity documents and attachments are stored in isolated Cloudflare R2 object storage and protected by strict backend access controls. They are accessible only to the user with a valid ticket ID and passcode and the licensed real estate advisor assigned to the case. Unauthorized external requests are blocked.

4. Activity records and deletion requests

The system automatically records application status changes, data edits, and access. After a lease is completed or an application is cancelled, you may contact your advisor to archive or request deletion of the records.

5. Referral and traffic source information

To understand how visitors reach this site and record referral leads, we may store the following in your browser: the public landing page path for your first and later non-direct visits, page language, referring site domain, allowlisted UTM parameters (source, medium, campaign, content, term), and referral codes. We do not store the full referrer URL or query parameters outside the allowlist.

These source and referral records are stored in this browser’s localStorage with no automatic expiry; you can clear them at any time using the button below. Your browser may also clear them automatically. We keep up to five unique referral codes in order of first capture, with the first shown as the default candidate. All candidates are unverified leads and do not confirm a referral relationship or commission eligibility. No referral commissions are currently settled.

When you create any of the three types of Ticket, the source and referral information available at that time is saved with it as a snapshot. Later revisions do not overwrite that snapshot. On-site anonymous analytics queries only the last 90 days of events; older records are removed when subsequent events are written. Names, email addresses, identity document information, and passcodes are not used for anonymous analytics. Clearing source and referral records in your browser does not delete an existing Ticket. To request deletion of ticket data, contact the assigned advisor and follow the ticket deletion process.

6. General email inquiries

The general inquiry form sends your email address, question, preferred reply language and optional name and messaging details to an ELB advisor through our transactional email service, for this inquiry and follow-up. It creates no application ticket and accepts no identity-document attachments. Inquiry records remain in the receiving mailbox. Contact ELB to request correction or deletion.

To limit spam, we verify the security challenge and temporarily keep a hashed network identifier and submission count in KV. The count expires fifteen minutes after its last update; KV stores neither inquiry text nor the original IP address.