ZHENHUA GROUP(臻華)MARKET
Buy & Sell
Buy & sell under the ZHENHUA name — the Kandyan collection and Sell with ZHENHUA.
Live働 Part Time Jobs
Real part-time openings for students, all over Japan — browse freely, and apply directly with the employer. ZHENHUA is beside you at every step.

Part-time jobs listed
Regions across Japan
Listings checked
New verified opportunities will be published here soon.
Tell AI MASTER PRO a few details about yourself, and it prepares your complete application pack — a ready Japanese application message and a rirekisho summary. You send it in one tap, in your own name: employer replies and your interview date come straight to your Gmail. ZHENHUA can also help you apply by email.
A Japanese-style CV — handwritten or printed — with a proper ID photo. It is the first thing most employers ask for, so prepare yours before you start applying.
Your residence card, student ID, My Number and a Japanese bank account. Employers ask for these when you are hired, so keep them together and safe.
Greetings and polite phrases win jobs. Learn to introduce yourself, say which days and hours you can work, and thank the interviewer — basic keigo, not slang.
Student visa holders need permission to engage in activity other than that permitted (資格外活動許可) before starting any baito. The usual limit is 28 hours per week.
Interview and workplace phrases with audio — for konbini, restaurants, hotels and more. Practise before you apply.
Open SENSEI ProIn the app, open Baito Japanese from the side menu.
Curated from public job listings — apply directly with the employer. Checked 6 Nov 2026. ZHENHUA is not an employment agency and charges no fees.
Whatever the listing says, student-visa holders need the work permit (資格外活動許可) and the 28 h/week cap always applies.
Questions about a job or baito? Email us
Email usYour guided application assistant. Answer a few questions and AI MASTER PRO prepares your complete application pack — you send it yourself, in your own name, in one tap.
美 AURELUNE ATELIER
YOUR PERSONAL WORLD OF STYLE
Fashion is not just what you wear. It's how the world sees you.
AI Studio — Demo ModeIn this demo, styling is guided by the choices you pick, and the look images are curated AI-editorial visuals. True identity-preserving try-on arrives when the AI service is connected.
粧 AI Stylist Studio
Your face. Your style. Your world. Perfectly styled by AI.
AI Studio — Demo Mode
Honestly: this studio does not analyse your face with AI. You guide the styling yourself — pick your face shape, skin tone and undertone — and AURELUNE builds your look from professional styling rules. The look images are curated AI-editorial visuals for inspiration, never presented as photos of you. Real identity-preserving try-on will arrive when the AI service is connected — and if that ever means a photo would leave this device, you will be told before anything is sent.
Add a face photo, a full-body photo, or both — as many as you like. They are shown only here, on your device, and are never uploaded or stored.
This is guided analysis: you pick what fits you — nothing is auto-detected from your photo.
空 Weather & Occasion Intelligence
Tell AURELUNE where you are going — it reads the real forecast for that place and day, then plans an outfit that respects the weather, the occasion and your budget.
品 Shop the Look
Real pieces from ZHENHUA Market — the Kandyan bridal collection from Sri Lanka, listed under the ZHENHUA name. Buy and Quick View work exactly as they do in the Market.
These buttons open live searches in Google Maps and retailer sites. Live prices and stock are shown at the source — AURELUNE does not list store prices.
縫 Made-to-Measure Tailoring
Every garment in this catalogue is made to order — custom-sewn to your measurements by our family tailor, who can sew any women's garment you dream of: gowns, sarees, lungi and wrap styles, bridal wear and more, from world fashion. Nothing here is ready stock. Every design below is distinct — its own name, its own photograph. Choose a design, then pick your fabric and colour and add your measurements in the order form, and we confirm everything with you personally by email before a single stitch is sewn.
No designs match your search — try another word, or choose a different tier or garment type.
日 Daily Styling
One tap: today's real weather for your place, your chosen style, and one clear answer to “what should I wear today?”
箪 Personal Wardrobe
Photograph the clothes you already own. Your wardrobe photos are stored only in this browser, on this device — they are never uploaded anywhere.
Your wardrobe is empty — add a few pieces to start building outfits.
心 Your Collection
Saved on this device — your saved looks live in this browser only. The ZHENHUA login is not a sync account, so they will not follow you to another device.
装 Creative Services
Fashion design is one of DAIKI DELA's creative services, alongside the photography and graphic design of ZHENHUA's Creative Business: custom pieces, styling direction, and visual design for fashion. Tell us what you are dreaming of — every enquiry is answered personally.
Have fashion pieces to sell?
Sell with ZHENHUACreated by DAIKI DELA
市 Crypto Market
GLOBAL DIGITAL ASSET MONITORING
A professional market-monitoring dashboard — live watchlist, TradingView charts and market overview for the world's major digital assets. Information only: ZHENHUA does not trade, hold or exchange cryptocurrency.
Cryptocurrency prices are volatile. Market information is provided for educational and informational purposes only and is not financial advice.
Total Market Cap
—
24h Trading Volume
—
Bitcoin Dominance
—
Assets Tracked by Provider
—
Information only — not financial advice. ZHENHUA does not tell you what to buy or sell; these alerts show real market movements so you can decide for yourself.
Market condition today
—
Most active today · by 24h trading volume
Loading market data…
Top mover today
Loading market data…
Movement alerts · ±5% or more in 24h
Loading market data…
Your pinned-coin alerts
Loading market data…
Saved on this device only. Alerts are checked while this page is open — the site cannot message a closed phone. No push notifications, no account needed, and nothing leaves your device.
Advanced chart by TradingView · Candlesticks, intervals, volume and indicators are available inside the chart.
Loading market data…
Loading market data…
Widget by TradingView
Widget by TradingView
Visible only to the ZHENHUA GROUP owner. This dashboard uses keyless public data sources only — there are no API keys or credentials to manage, and none are ever shown here. Settings save on this device immediately, and to the HQ settings store (hq_settings) when Firestore rules allow it.
ZHENHUA CRYPTO MARKET is a monitoring dashboard. It does not execute trades, connect wallets, accept deposits or give buy/sell signals. Prices come from public market-data providers and may be delayed — always confirm a price with the venue you actually use before acting on it.
AI BRAIN LIVE • PLATFORM IN DEVELOPMENT
THINK / PLAN / EXECUTE / INNOVATE
BY ZHENHUA GROUP
ZHENOVEX AI is ZHENHUA GROUP's autonomous AI. At its centre, a Master Brain understands your goal, breaks it into steps and coordinates a team of specialist agents — so one request becomes a complete plan.
The ZHENOVEX Master Brain is live on this page. Describe a goal, or ask for a plan, and it will think it through with you.
Full plans can take around 10–30 seconds — the Brain works through the steps before it answers.
Master Brain — LIVE
Chat with it on this page.
Autonomous platform — IN DEVELOPMENT
The 10 specialist agents, the persistent task engine and the scheduler run in ZHENHUA's development environment; public task execution is not open yet. This chat gives answers and plans — it does not execute tasks.
One Master Brain, ten specialists. The Master plans and coordinates; every agent brings its own expertise.
音楽 DRAGONWOLF MUSIC — MUSIC LABEL
FROM KYOTO TO THE WORLD — ONE STAGE AT A TIME
DRAGONWOLF MUSIC is the music label of ZHENHUA GROUP(臻華), launched in November 2026. Home of DELA ON THE BEAT — the group's music production name, known for romantic dance remixes and original cover artwork — the label produces music from Kyoto to the world. Its first releases are now in preparation.
Music Label of ZHENHUA GROUP(臻華)
“Feel the roar. Run with the wolf.”
DRAGONWOLF MUSIC is the music label of ZHENHUA GROUP(臻華) — home of DELA ON THE BEAT, the group's music production name.
The dragon and the wolf — the emblem animals of ZHENHUA GROUP — give this label its name and its spirit.
Notes, lyrics, songs and videos from DRAGONWOLF MUSIC — posted by the label, played right here.
Loading the latest posts…
Digital instruments — synthesized live in your browser. Tap to play!
Music Label — Launched November 2026
Label launched November 2026 — first releases in preparation. No releases yet.
For enquiries, collaborations and production work with DRAGONWOLF MUSIC and DELA ON THE BEAT, email the ZHENHUA team — we reply personally.
Enquire — DRAGONWOLF MUSIC環 ZHENHUA GROUP(臻華)Ecosystem
ZHENHUA GROUP is growing into one global marketplace ecosystem. Two marketplaces are already live — ZHENHUA Market and ZHENHUA Crypto Market — and four new divisions are now launching: ZHENHUA Homes, ZHENHUA Tickets, ZHENHUA Automotive and ZHENHUA Gaming. Each new division opens honestly: partner applications first, verified listings only after approval — never invented listings.
Buy & Sell
Buy & sell under the ZHENHUA name — the Kandyan collection and Sell with ZHENHUA.
LiveDigital Asset Monitoring
Global digital asset monitoring — watchlist, TradingView charts and market overview. Information only, never trading.
LiveFind Your Home. Connect With Opportunity.
Find your home in Japan — apartments, rooms and student housing through licensed real estate partners.
LaunchingDiscover Events. Book Experiences.
Discover events and book experiences — concerts, festivals, anime, sports and more, from approved organizers.
LaunchingJapan Automotive. Global Opportunities.
Japan automotive, global opportunities — cars, motorcycles and parts from authorized dealers and export partners.
LaunchingPlay. Connect. Compete.
Play, connect, compete — game discovery, community, tournaments and gaming gear.
LaunchingThe same ZHENHUA account (Google or email sign-in) works across every division — browse, save favourites, send inquiries, register for events and join the gaming community. Browsing is always free; you sign in only when you use a feature.
Account roles: Customer · Seller · Property Partner · Event Organizer · Gaming Organizer · Administrator · Founder / Super Admin. Roles are never self-granted: partner, seller and organizer roles begin as an application on the division page, are approved by the owner, and are enforced by Firestore security rules on the server — not by hiding buttons.
Global search and advanced filtering, favourites and saved listings, inquiry management with unique reference IDs, notifications, verified badges based on actual verification, moderated reviews, report-a-listing, customer support, multilingual pages (English / Japanese / Sinhala), listing status management and an admin approval workflow. Each division keeps its own separate data — properties, vehicles, events, tickets, games and tournaments are never mixed into one collection.
家 ZHENHUA GROUP(臻華) — New Division
Find Your Home. Connect With Opportunity.
Now Launching — Partner Applications OpenZHENHUA HOMES connects people looking for a home in Japan — international students, foreign workers, families, people moving to Japan and Japanese residents — with authorized, licensed real estate partner companies. ZHENHUA does not act as a broker: partners handle viewings, contracts and every regulated step.
Legal note: ZHENHUA HOMES is a property discovery and referral platform only. ZHENHUA GROUP is not a licensed real estate broker, does not negotiate rental contracts, and does not collect brokerage fees. Only authorized, appropriately licensed real estate partners may perform regulated brokerage activities. Listings will show real availability only — ZHENHUA never fabricates properties.
Search and filters are live and run over this division's own listings data, which starts empty: an approved listing appears here only after verification — and the filter set grows with the first real listings in the next stage.
Every approved property listing will show: photographs, monthly rent, deposit and key money, management fees, initial move-in costs, location and distance to the nearest station, floor plan, available date, property conditions, and the partner agency's details — with an inquiry button that carries a unique reference ID.
01
Your inquiry receives a unique reference ID the moment you send it.
02
ZHENHUA forwards it to the responsible licensed real estate partner.
03
Viewings, contracts and all regulated brokerage are handled by the licensed partner only.
04
Referral status is tracked by ZHENHUA. A referral fee exists only where a written agreement with the partner says so — never assumed.
For licensed real estate companies. Applying does not grant any role or listing rights — the owner reviews and approves partners personally.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Looking for a home in Japan? Tell ZHENHUA what you need — your inquiry is forwarded to a licensed partner when one covers your area.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Submitting a form composes an email you send yourself, and the site also tries to save a copy for the owner in the ZHENHUA database (Firestore, hq_enquiries) so real demand can be counted and followed up. A reference ID is generated for every submission. Applications are requests only — approval is the owner's decision, and no role is ever granted automatically.
券 ZHENHUA GROUP(臻華) — New Division
Discover Events. Book Experiences.
Now Launching — Partner Applications OpenZHENHUA TICKETS brings concerts, music festivals, DJ events, cultural shows, anime and gaming events, sports, exhibitions and conferences into one discovery place — with events submitted by approved organizers and reviewed by ZHENHUA before anything is published.
Ticket sales are not open yet. No payment provider is configured, so no ticket can be bought on this site today, and ZHENHUA does not operate ticket resale. When sales open in a later stage, tickets will be issued only after verified payment — with a unique ticket ID and QR code, fees shown transparently, and published cancellation and refund conditions.
Search and filters are live and run over this division's own listings data, which starts empty: an approved listing appears here only after verification — and the filter set grows with the first real listings in the next stage.
Every approved event will show: date and venue, city and country, artists and performers, ticket categories and availability, full prices with any service fee shown separately, sales opening and closing dates, and the organizer's details. Every event is reviewed before publication.
Digital tickets with a unique ID and QR code, secure account storage, printable tickets and a mobile QR check-in scanner with duplicate-entry prevention are part of the ticketing stage — built only after an approved payment provider is configured and tested. Uploading event posters is not available yet: image uploads need the Firebase Storage upgrade, so organizer applications are text-only for now.
For event organizers. Applying does not grant an organizer role — the owner reviews and approves organizers personally, and every event is reviewed before publication.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Interested in an event category, or planning to attend events in Japan? Tell ZHENHUA — when approved events open, inquiries are answered first.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Submitting a form composes an email you send yourself, and the site also tries to save a copy for the owner in the ZHENHUA database (Firestore, hq_enquiries) so real demand can be counted and followed up. A reference ID is generated for every submission. Applications are requests only — approval is the owner's decision, and no role is ever granted automatically.
車 ZHENHUA GROUP(臻華) — New Division
Japan Automotive. Global Opportunities.
Now Launching — Partner Applications OpenZHENHUA AUTOMOTIVE connects buyers in Japan and around the world with authorized vehicle dealers and export partners — used and new cars, sports and luxury vehicles, SUVs, motorcycles, commercial vehicles, and parts and accessories.
How ZHENHUA AUTOMOTIVE works: this is an inquiry and discovery platform. ZHENHUA does not independently conduct regulated vehicle sales, brokerage or export operations — authorized dealers and licensed partners handle those steps. Any shipping figure connected with an export inquiry is an estimate only, never a confirmed quotation, and is given per inquiry rather than as an automated price. Fake listings and misleading condition claims are never accepted.
Search and filters are live and run over this division's own listings data, which starts empty: an approved listing appears here only after verification — and the filter set grows with the first real listings in the next stage.
Every approved vehicle listing will show: photographs, make and model, manufacturing year, mileage, engine information, transmission, fuel type, vehicle condition, inspection information where available, asking price, location and the seller's details — with an inquiry button on every listing.
Buying from outside Japan? Add your destination country in the inquiry form and ZHENHUA will connect you with partner exporters. A partner exporter directory will be published only when real partners are approved — it is not published yet.
01
Tell us the vehicle and your destination country.
02
A licensed partner exporter prepares the quotation — shipping shown clearly as an estimate.
03
Vehicle inspection information is shared where available before you commit.
04
The partner exporter handles shipping and export paperwork under its own licence.
For authorized dealers and sellers. Seller verification is part of approval — applying grants no listing rights, and vehicle photos can be added once image uploads are available (Firebase Storage upgrade).
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Looking for a vehicle in Japan, or importing from Japan? Tell ZHENHUA what you are looking for and where it should go.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Submitting a form composes an email you send yourself, and the site also tries to save a copy for the owner in the ZHENHUA database (Firestore, hq_enquiries) so real demand can be counted and followed up. A reference ID is generated for every submission. Applications are requests only — approval is the owner's decision, and no role is ever granted automatically.
遊 ZHENHUA GROUP(臻華) — New Division
Play. Connect. Compete.
Now Launching — Partner Applications OpenZHENHUA GAMING is the group's gaming platform: game discovery with official store links, gaming news, a moderated community, esports tournaments — community-run and official ZHENHUA tournaments — and a marketplace for gaming gear from approved sellers.
Fair-play rules: ZHENHUA GAMING never hosts game files — discovery links point to official stores only. Tournaments launch with no entry fees and no prize pools, until the legal requirements, publisher permissions and payment configuration are verified. Community content is moderated, with reporting — and official tournament records cannot be changed by unauthorized users.
Search and filters are live and run over this division's own listings data, which starts empty: an approved listing appears here only after verification — and the filter set grows with the first real listings in the next stage.
Game listings will show: description, platforms (PC / Android / iOS / console), system requirements and official download/store links. Tournament pages will show: game, organizer, registration period, rules, participant limits, match schedules, brackets, results and leaderboards.
A
PC, Android, iOS and console games — free-to-play, popular and new releases, with official links only.
B
Releases, updates, announcements and esports news, published by ZHENHUA.
C
Gamer profiles, teams and groups, discussions and reviews — with reporting and moderation.
D
Two systems: Community Tournaments by approved organizers, and Official ZHENHUA Tournaments run by the group. No entry fees or prize pools yet.
E
Gaming PCs, keyboards, mice, headsets, controllers and accessories from approved sellers.
F
A future home for original games developed and published by ZHENHUA GROUP. This is a future placeholder only: no game is released, and none will be shown as released until it truly is.
For tournament organizers and gaming-gear sellers. Applying grants no organizer or seller role — the owner approves organizers and sellers personally, and official tournament records stay under ZHENHUA control.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Want to join the community, enter a future tournament, or ask about gaming gear? Send an inquiry — community registrations open with the first approved tournaments.
Copy it, or send it by email — ZHENHUA GROUP will reply personally.
Submitting a form composes an email you send yourself, and the site also tries to save a copy for the owner in the ZHENHUA database (Firestore, hq_enquiries) so real demand can be counted and followed up. A reference ID is generated for every submission. Applications are requests only — approval is the owner's decision, and no role is ever granted automatically.

臻華グループ
FROM JAPAN TO THE WORLD
BUILD BUSINESSES. CREATE OPPORTUNITIES. CONNECT THE WORLD.
An international multi-business company from Kyoto, Japan — founded by DAIKI DELA — holding AI products, creative services, a global marketplace and fashion under one name: the dragon and the wolf.
注目 Highlights
働
Real openings across 13 regions of Japan — 73 active verified listings, checked 7 Nov 2026.
Part Time Jobs品
Three real Kandyan bridal pieces, just listed — ¥42,000 to ¥60,000.
Explore Fashion語
38 interview & workplace phrases with audio — free in the SENSEI Pro app.
Open SENSEI Pro学
Starter sets and a first-weeks checklist — email us anytime.
Get SupportBased in Kyoto, Japan
One Company — Every Venture
SENSEI Pro — Free for the World
From Japan to the World
事業 Business Divisions — Active Today
ZHENHUA GROUP has three active business divisions today, plus two active services run directly by the group. Planned ventures are always labelled as planned — never presented as operating businesses.
AIプロダクト
Division 1 — Active. Intelligent products with a human heart: SENSEI Pro, AI MASTER PRO and AURELUNE ATELIER.
Active Divisionクリエイティブ事業
Division 2 — Active. Creative services for brands and local businesses — photography, design, fashion design and promotional content made in Kyoto.
Active Division音楽事業
Division 3 — Active. The music label of ZHENHUA GROUP(臻華) — home of DELA ON THE BEAT, the group's music production name.
Active Division市場と支援
Active group services — ZHENHUA Market (buy & sell) and ZHENHUA Global Support for people coming to Japan.
Active Services新 New Divisions — Now Launching
Four new divisions join the group as the ZHENHUA Ecosystem — launched honestly: partner, seller and organizer applications are open now, and verified listings follow only after approval. They are not yet active businesses, and nothing on their pages is presented as live trade.
ホームズ
Find Your Home. Connect With Opportunity. Property discovery in Japan through licensed real estate partners — referral only, never brokerage by ZHENHUA.
Launching — New Divisionチケット
Discover Events. Book Experiences. Events from approved organizers — ticket sales open only after a payment provider is configured and tested.
Launching — New Divisionオートモーティブ
Japan Automotive. Global Opportunities. Vehicles and parts from authorized dealers and export partners — inquiries only at launch.
Launching — New Divisionゲーミング
Play. Connect. Compete. Game discovery, community, tournaments and gaming gear — no entry fees, no prize pools, no hosted game files.
Launching — New Divisionエコシステム
All six marketplace businesses under one account — ZHENHUA Market, Crypto Market, Homes, Tickets, Automotive and Gaming.
Open the Hub私たちについて About the Group
ZHENHUA GROUP is a company from Kyoto — one name that holds everything its founder creates.
The name 臻華 (Zhenhua) carries a simple ambition: to bring things to their finest form. Everything under this name is made with that standard — whether it is built with artificial intelligence, crafted for a client's business, or a venture still to come.
The company has three active divisions today. AI Products — led by SENSEI Pro, our free Japanese learning app for learners around the world. Creative Business — creative services across photography, graphic design, fashion design and creative media. DRAGONWOLF MUSIC — our music label, home of DELA ON THE BEAT, the group's music production name. Alongside them, the group runs ZHENHUA Market and ZHENHUA Global Support as direct services. Our vision is global expansion by 2036 — and everything DAIKI DELA creates next will live under this same name.
From a studio in Kyoto, for the whole world.
ZHENHUA GROUP(臻華)is an independent group founded in Kyoto, Japan by a Sri Lankan creator. We work in education, part-time jobs, support for life in Japan, fashion and travel between Japan and Sri Lanka. ZHENHUA GROUP(臻華)is not affiliated with Shanghai Zhenhua Heavy Industries (ZPMC) or any other company with a similar name. Our name uses the characters 臻華.
「ZHENHUA GROUP(臻華)は、スリランカ出身の創設者が日本の京都で設立した独立したグループです。教育、アルバイト、日本での生活サポート、ファッション、日本とスリランカの旅行を手がけています。上海振華重工(ZPMC)など、同名・類似名の企業とは一切関係ありません。当グループの名称は『臻華』の文字を使用しています。」
人工知能
知 Active Division — AI Products
ZHENHUA GROUP builds AI products that feel human. Our first creation is already live: SENSEI Pro, a Japanese language learning app with a cute anime teacher who chats with learners like a friend, corrects their mistakes and remembers them from day to day.
It is free for everyone, everywhere — created by ZHENHUA GROUP and owned by DAIKI DELA, so that anyone in the world can learn Japanese.
Also in this division: AI MASTER PRO — a guided assistant on this site that prepares your baito application pack from your answers (you review and send it yourself; it does not submit anything automatically) — and AURELUNE ATELIER, our fashion styling studio, currently in clearly-labelled demo mode with real Open-Meteo weather.
AI BRAIN LIVE • PLATFORM IN DEVELOPMENT
ZHENHUA GROUP's Autonomous Artificial Intelligence Ecosystem
ZHENOVEX AI is an autonomous multi-agent AI platform now being built by ZHENHUA GROUP. At its centre is a central AI brain that plans tasks and coordinates specialist agents — research, development, business, creative, data and security — so they can work together on complex goals. The Master Brain is live now — chat with it on the ZHENOVEX AI page — while the full autonomous platform continues in development.
BY ZHENHUA GROUP
Chat with the Brain市場 Buy & Sell
The group's own marketplace — a place to buy and sell under the ZHENHUA name, from Kyoto to buyers everywhere. Start with a category:
MARKET




Pieces with a story — chosen in Kyoto, sent out to the world.
Curated in Kyoto.
Loved worldwide.
Hand-picked pieces and honest descriptions — and a person, not a checkout bot, at the other end of every order.
ファッション
Clothing, bags, watches and the finishing touches — style chosen with the ZHENHUA eye.
Explore AURELUNE Fashion
和雑貨
Goods from Japan — crafts, everyday items and pieces of Japanese life, sent from Kyoto to the world.
アート
Artwork, posters and photographic prints — including work from the ZHENHUA creative studio.
電子機器
Cameras, audio and everyday tech from Japan.
























Your Next Treasure
Starts Here
ZHENHUA Market 市場
No items match your search — try a different word or category.
近日公開
How to read this Market: items marked SAMPLE are display examples only — they are not for sale and their prices are illustrative. Unmarked items are genuine listings sold by ZHENHUA GROUP. Ordering is by personal order request by email — there is no online checkout or card payment on this site.
Sell with ZHENHUAHow ordering works: Choose an item and tap Buy — the order form opens right here on this page. Sending it creates an order request to ZHENHUA GROUP by email. We confirm payment and delivery with you personally — there is no online checkout and no card payment on this site.
出品 Sell Yours
Have an item to sell? Tell us about it below. Your details are composed into a listing request you can send to ZHENHUA GROUP by email — we review every item personally before it goes on sale.
Copy it, or send it by email to ZHENHUA GROUP. We will reply to review your item and arrange the listing.
学生 For Students in Japan
Just arrived in Japan? These starter sets cover what a student needs first — a room to sleep in, a kitchen to cook in, and the everyday things in between. Nothing here is a fixed listing: send an enquiry and we will tell you honestly what we can put together for you, often including good pre-loved pieces from graduating students.
室
ルーム
Futon, blanket, pillow, hangers and a desk lamp — everything you need for a good first night's sleep in your new room.
食
キッチン
Rice cooker, kettle, frying pan, plates and chopsticks — cook your own meals from day one and keep your food budget under control.
学
学習
Desk, chair, power strip and a Wi-Fi router — a proper corner of your own for study, homework and online classes.
冬
冬支度
A warm coat, gloves and winter layers — Japan's winter is colder than it looks, so be ready before it arrives.
暮
毎日
Bicycle, umbrella, raincoat and a backpack — the everyday kit for getting around your new city like a local.
Leaving Japan? Sell your items to ZHENHUA — graduating students can sell furniture, appliances and bikes to us, and new students buy them for less.
Sell with ZHENHUA支援 Global Support
Going to a new country is a big step. ZHENHUA Global Support offers friendly support and guidance for foreigners heading abroad — starting with Japan, the country we call home, and growing from there.
Our home country — support for coming to Japan is open now:
More countries — coming soon. ZHENHUA Global Support starts in Japan and grows from here, one country at a time, as the company expands.
Finding a baito (part-time job) is one of the hardest parts of student life in Japan — so here is honest, practical help: how to get ready, and where students actually find work. This is free community guidance from ZHENHUA — we are not an employment agency, and we never charge students for job help.
A Japanese-style CV — handwritten or printed — with a proper ID photo. It is the first thing most employers ask for, so prepare yours before you start applying.
Your residence card, student ID, My Number and a Japanese bank account. Employers ask for these when you are hired, so keep them together and safe.
Greetings and polite phrases win jobs. Learn to introduce yourself, say which days and hours you can work, and thank the interviewer — basic keigo, not slang.
Student visa holders need permission to engage in activity other than that permitted (資格外活動許可) before starting any baito. The usual limit is 28 hours per week.
Interview and workplace phrases with audio — for konbini, restaurants, hotels and more. Practise before you apply.
Open SENSEI ProIn the app, open Baito Japanese from the side menu.
Japan's free public employment offices. Many offer support for foreign job seekers — bring your residence card and ask what is available near your school or home.
Universities and language schools keep job boards and career support desks for their own students — often with employers who already hire international students.
Townwork, Indeed and Baitoru list thousands of part-time jobs. Search by station, hours and Japanese level — and look for listings marked 外国人歓迎 (foreigners welcome).
Restaurants, convenience stores, hotels and kitchens around Kyoto often hire students. Look for 求人 posters in shop windows — it is fine to walk in politely and ask.
Many baito change hands when a senior student graduates or moves away. Ask seniors at your school and in your community — a personal introduction beats a cold application.
The short version of settling in — the things to sort out first when you arrive in Japan as a student.
Get connected in your first days — you will need a Japanese phone number for school, baito applications and almost everything else.
Register your address at city hall within 14 days of moving in. This one visit unlocks almost everything else on this list.
Open one early; you will need it for wages and bills. Many students start with Japan Post Bank (Yucho).
Your My Number notification arrives after you register your address. Keep it safe — employers and banks will ask for it.
Enrol at city hall when you register — students in Japan must be covered, and the insurance card keeps medical care affordable.
With your work permit, students can work up to 28 hours a week. See Part-Time Job Support above for getting ready and where to look.
A Japanese CV (rirekisho) with a proper photo helps you start faster — keep copies ready to hand when a shop is hiring.
Japanese opens every door — jobs, friends and daily life. Study free with SENSEI Pro, ZHENHUA's own learning app, before and after you arrive.
Open SENSEI Pro — it's free →The language opens every door. Study Japanese free with SENSEI Pro — chat with Sakura-chan, master kanji and practise real conversation before you arrive, and keep learning after you land.
Open SENSEI Pro — it's free →Thinking of studying in Japan? We share guidance on preparing for the move — learning the language first, getting ready for school life, and knowing what to expect when you arrive.
Everyday guidance for building a life in Japan — finding your footing in a new city, understanding daily customs, and settling in with confidence, from people who live here.
You do not have to do it alone. Email the ZHENHUA team at zhenhuateam@gmail.com — learners and newcomers from around the world write to us about Japanese and life in Japan, and we reply personally.
Email the team →ZHENHUA Global Support is friendly guidance and community support — not a licensed visa or immigration agency. For official visa and residency procedures, always follow the guidance of the Japanese authorities or a licensed specialist.
撮影
業 Active Division — Creative Business
ZHENHUA GROUP's creative studio serves local businesses and brands — photography, graphic design and promotional content with the same cinematic eye behind everything we make. From social Stories that stop the scroll, to posters and menus that fill seats.
依頼 Start a Project
Planning a shoot, a poster, a menu or a full brand refresh? Tell us below — your details are composed into an enquiry message you can send to ZHENHUA GROUP by email, and we reply personally.
Copy the message, or send it by email. ZHENHUA GROUP will reply to talk through your project.
一 The Company Itself — One Name
ZHENHUA GROUP is not a single product or a single service — it is the company itself. Every venture, every product and every creation of DAIKI DELA is shared and held under this one name: the AI products, the creative business, and everything still to come — one company, one standard, one signature.
From Japan to the World
メディア部門 — THE MEDIA DIVISION
The sound of the company. Under the name DELA ON THE BEAT, DAIKI DELA creates music remixes — romantic dance remixes with their own cover artwork — one more creation held under the ZHENHUA name.
Email the ZHENHUA Team製品 The AI Product
A free Japanese language study app for the whole world. Chat with Sakura-chan, your anime sensei, master kanji stroke by stroke, test yourself at every JLPT level — then walk through a living anime Japan and use your Japanese for real.
Structured study across every JLPT level, N5 to N1 — vocabulary, grammar and reading in one place.
Both kana systems with writing practice — the foundation every learner starts with.
Kanji packed by level, with an animated sensei showing the correct stroke order for every character.
Word learning with My Word Book, Smart Review (SRS), and Ask Sensei — type any word and get a full lesson.
Sensei Chat with Sakura-chan — message your anime teacher, get mistakes corrected, and explore a whole-Japan map world where you talk to people on the road.
38 interview and workplace phrases with audio — for konbini, restaurants, hotels, cleaning and warehouse work.
Timed mock exams with instant review — so you walk into the real JLPT ready.
Learn in your own language — 13 interface languages including English, Japanese and Myanmar. Profiles are created on-device with no login needed to study.
Getting started: open the app, create your profile (name + avatar, saved on your phone only), and start with kana or your JLPT level. The Community section (Chat · Moments · Friends) uses Google sign-in. New features arrive in waves — anything still in development is labelled inside the app.
Created by ZHENHUA GROUP · Owned by DAIKI DELA
展望 Global Vision
2036
Our vision is global expansion by 2036: ZHENHUA products, creative work and support reaching people far beyond Japan — built step by step, honestly, under one name. What is live today is listed on this page as live; what is planned is labelled planned.
Build Businesses. Create Opportunities. Connect the World.
連絡 Contact
Every message is answered personally by the ZHENHUA team in Kyoto. Choose the channel that suits you — browsing never needs an account; login is only needed to buy, sell and enquire.
zhenhuateam@gmail.com — email the ZHENHUA team; we reply personally.
Add on LINE and message directly.
Privacy enquiries and data-deletion requests: email us at zhenhuateam@gmail.com with the subject “Privacy” — we reply personally. See the Privacy Policy below for exactly what is collected and why.
Company information is shown in English. It is also available in 日本語 and සිංහල — switch the site language to read it in that language.
規約 Privacy, Terms & Data
This policy is shown in English. The full policy is available in English, 日本語 and සිංහල — switch the site language to one of those to read it in that language.
ZHENHUA GROUP is run from Kyoto, Japan by DAIKI DELA. This policy describes what this website actually does with data, checked against the site's real behaviour. Browsing is always free and never needs an account.
Login is needed only to use features: Market Buy, the Sell-with-ZHENHUA form, Creative enquiries and AI MASTER PRO send. Accounts are handled by Firebase Authentication (Google, project zhenhuagroup). What is stored there: your name, your email address, your profile photo if your provider supplies one, and which sign-in provider you used (Google, or email & password). Your password is handled by Firebase / Google — this site never sees or stores it.
When you order from ZHENHUA Market, send a Sell request, make a Creative enquiry or send a job-support enquiry, or submit a ZHENHUA Ecosystem partner application or division inquiry (Homes, Tickets, Automotive or Gaming), the site composes an email in your own email app, addressed to zhenhuateam@gmail.com, and you send it yourself; ZHENHUA receives it by email. The AI MASTER PRO application pack works the same way: it is prepared on this page and you send it yourself. From 7 Nov 2026 the site also saves a copy of the details you entered (your name, contact, and what you asked about) in ZHENHUA's own database (Firestore, collection hq_enquiries) so ZHENHUA can count and follow up real requests; those records can be read only by the owner, and saving takes effect once the database rules for that collection are switched on (see the QA report). The messages themselves live in your own mailbox or in the app you used to contact us (such as LINE), under that service's own privacy terms. There is no online checkout and no payment is taken on this site.
Notifications are opt-in. If you tap “Turn on notifications”, Firebase Cloud Messaging creates a device token, which is stored in Firestore in a collection called push_tokens, together with your browser's user-agent string and a timestamp. No name or email is attached to the token, and the site's security rules do not allow browsers to read tokens back. You can turn notifications off for this browser in “Privacy & My Data” (account menu) or in your browser settings.
Google Analytics 4 (property G-CNW81KD2C8) counts anonymous visit statistics: pages viewed, approximate country / region and device type. ZHENHUA sets no advertising trackers. You control this in “Privacy choices” (footer) or “Privacy & My Data”: if you turn anonymous analytics off, the analytics code does not load on this device at all. Browsing and logging in work exactly the same either way, and this choice is never bundled into login.
When you chat with the AI Assistant, your messages are sent to our AI service (a Cloudflare Worker), which passes them to Google's Gemini AI to generate the reply. The chat history is kept only in this tab's memory and is never stored by this site. The AI runs on a free tier, and on free tiers Google may use submitted prompts to improve its products — so please do not put personal details (names, addresses, phone numbers) into AI chats.
Studio photos are processed on your device only: they exist only as previews in this page's memory, are never uploaded to any server, and are never saved in browser storage. Wardrobe photos and saved looks are stored only in your own browser's local storage, on your own device. The Studio is in demo mode — no external AI is connected. If a real external AI is connected in the future, you will be told before any photo is sent anywhere.
Firebase Authentication storage (keeps you signed in on this device); zhAnalytics (your analytics choice); zhxNewsSeen (which What's New item you last saw); and, for AURELUNE, aurelune_wardrobe, aurelune_saved_looks and aurelune_last_city (your wardrobe, saved looks and last weather city — this device only). The weather feature sends only the city name you type to Open-Meteo; no account data is sent with it.
Your account details are kept while your account exists. A push token stops being usable when you turn notifications off for this browser, revoke notification permission in your browser, or delete your account — the Privacy & My Data dashboard tries to delete this browser's token and reports honestly if the server copy cannot be deleted from the browser. Analytics data is held by Google under Google Analytics' own retention settings. Messages you sent us stay in the chat app where you sent them.
When signed in, open “Privacy & My Data” from the account menu to see the account data this site shows for you, download a JSON copy of the data held on this device for you, turn analytics on or off, turn off notifications for this browser, and delete your account. Deleting your account deletes your Firebase Authentication account. It cannot delete emails or messages you already sent to us — those are outside this site's control.
This site is made for a general audience and is not directed at young children. If you are not old enough to agree to these terms where you live, please use the site together with a parent or guardian.
Email us at zhenhuateam@gmail.com with the word “Privacy”, or message us on LINE via the link in the Contact section — we reply personally.
This policy is provided in good faith and is pending professional legal review.
ZHENHUA GROUPは、DAIKI DELAが日本・京都から運営しています。本ポリシーは、このウェブサイトが実際に行っているデータの取り扱いを、サイトの実際の動作と照合して説明するものです。閲覧は常時無料で、アカウントは不要です。
ログインが必要なのは、機能を「使う」ときだけです:マーケットの購入、Sellフォーム、クリエイティブのお問い合わせ、AI MASTER PROの送信。アカウントはFirebase Authentication(Google、プロジェクト:zhenhuagroup)が管理します。保存されるのは、氏名、メールアドレス、プロバイダから提供される場合はプロフィール写真、そして利用したログイン方法(Google、またはメールアドレスとパスワード)です。パスワードはFirebase / Googleが管理し、このサイトがパスワードを見たり保存したりすることはありません。
ZHENHUA Marketの注文、Sellリクエスト、クリエイティブのお問い合わせ、求職サポートのお問い合わせ、ZHENHUAエコシステム(ホームズ/チケット/オートモーティブ/ゲーミング)のパートナー申請や各部門へのお問い合わせでは、サイトは、宛先zhenhuateam@gmail.comのメールをあなた自身のメールアプリで作成し、送信はあなた自身が行います。ZHENHUAはそれをメールで受け取ります。AI MASTER PROの応募パックも同様で、このページ上で作成され、送信はあなた自身が行います。2026年11月7日からは、入力した内容(氏名、連絡先、お問い合わせ内容)のコピーが、実際の依頼の集計とフォローのためにZHENHUA自身のデータベース(Firestoreの「hq_enquiries」コレクション)にも保存されます。この記録を読めるのはオーナーのみで、保存はそのコレクションのデータベースルールが有効になってから開始します(QAレポート参照)。メッセージ自体は、このサイトではなく、あなたのメールボックスや、連絡に使ったアプリ(LINEなど)の中に、そのサービスのプライバシー条件のもとで残ります。このサイトにはオンライン決済はなく、支払いを受け取ることもありません。
通知は任意です。「通知をオンにする」をタップすると、Firebase Cloud Messagingがデバイストークンを作成し、Firestoreの「push_tokens」コレクションに、ブラウザのユーザーエージェント文字列とタイムスタンプとともに保存されます。トークンに氏名やメールアドレスは紐づいておらず、サイトのセキュリティルールにより、ブラウザからトークンを読み取ることはできません。このブラウザの通知は、アカウントメニューの「プライバシーとあなたのデータ」またはブラウザ設定からオフにできます。
Google Analytics 4(プロパティ G-CNW81KD2C8)が匿名の訪問統計(閲覧ページ、おおよその国・地域、デバイスタイプ)を集計します。ZHENHUAは広告トラッカーを設定しません。この設定はフッターの「プライバシー設定」または「プライバシーとあなたのデータ」で管理できます。匿名の解析をオフにすると、この端末では解析コード自体が読み込まれません。閲覧もログインもどちらの場合でも同じように使え、この選択がログインに含まれることはありません。
AIアシスタントでチャットすると、メッセージは当社のAIサービス(Cloudflare Worker)に送られ、返信生成のためにGoogleのGemini AIへ渡されます。チャット履歴はこのタブのメモリ内にのみ保持され、このサイトに保存されることはありません。AIは無料枠で動作しており、無料枠ではGoogleが送信されたプロンプトを自社製品の改善に使用する場合があります。そのため、AIチャットには個人情報(氏名、住所、電話番号)を入力しないでください。
スタジオの写真はあなたの端末上でのみ処理されます。このページのメモリ内のプレビューとしてのみ存在し、サーバーへアップロードされることはなく、ブラウザのストレージに保存されることもありません。ワードローブの写真と保存したルックは、あなたの端末のブラウザのローカルストレージにのみ保存されます。スタジオはデモモードで、外部AIは接続されていません。将来、本物の外部AIを接続する場合は、写真がどこかへ送信される前に、必ずそのことをお知らせします。
Firebase Authenticationのストレージ(この端末でログイン状態を保持)、「zhAnalytics」(解析の選択)、「zhxNewsSeen」(最後に見たWhat's New)、そしてAURELUNE用の「aurelune_wardrobe」「aurelune_saved_looks」「aurelune_last_city」(ワードローブ、保存したルック、最後の天気の都市 — いずれもこの端末のみ)。天気機能は、入力した都市名のみをOpen-Meteoに送信します。アカウントデータは一緒に送信されません。
アカウント情報は、アカウントが存在する間保持されます。プッシュトークンは、このブラウザの通知をオフにする、ブラウザで通知許可を取り消す、またはアカウントを削除すると使えなくなります。「プライバシーとあなたのデータ」ダッシュボードはこのブラウザのトークンの削除を試み、サーバー側のコピーをブラウザから削除できない場合はその旨を正直に表示します。解析データはGoogle Analytics自身の保持設定のもとでGoogleが保持します。送信済みのメッセージは、送信したチャットアプリの中に残ります。
ログイン中は、アカウントメニューの「プライバシーとあなたのデータ」から、アカウントデータの確認、この端末に保持されたあなたのデータのJSONダウンロード、解析のオン/オフ、このブラウザの通知オフ、アカウントの削除ができます。アカウントを削除すると、Firebase Authenticationのアカウントが削除されます。送信済みのメールやメッセージは、このサイトの管理外のため削除できません。
このサイトは一般向けであり、小さなお子様を対象としたものではありません。お住まいの地域で本規約に同意できる年齢に達していない場合は、保護者の方と一緒にご利用ください。
「Privacy」と添えて、zhenhuateam@gmail.comへメールをお送りいただくか、お問い合わせセクションのリンクからLINEでメッセージをお送りください。担当者が直接返信します。
本ポリシーは誠意をもって提供するものであり、専門家による法的レビューは今後の課題です。
ZHENHUA GROUP එක Kyoto, ජපානයේ සිට DAIKI DELA විසින් පවත්වාගෙන යනු ලැබේ. මෙම ප්රතිපත්තිය, මෙම වෙබ් අඩවිය දත්ත සමඟ ඇත්තටම කරන්නේ කුමක්ද යන්න, අඩවියේ සැබෑ හැසිරීම සමඟ පරීක්ෂා කර විස්තර කරයි. බ්රවුස් කිරීම සැමවිටම නොමිලේ වන අතර ගිණුමක් කිසිවිට අවශ්ය නැත.
ලොග් වීම අවශ්ය වන්නේ විශේෂාංග භාවිතා කිරීමට පමණි: Market Buy, Sell පෝරමය, Creative විමසීම් සහ AI MASTER PRO යැවීම. ගිණුම් Firebase Authentication (Google, project zhenhuagroup) මගින් හසුරුවනු ලැබේ. එහි ගබඩා වන්නේ: ඔබේ නම, ඔබේ ඊමේල් ලිපිනය, ඔබේ සැපයුම්කරු ලබා දෙන්නේ නම් පැතිකඩ ඡායාරූපය, සහ ඔබ භාවිතා කළ ලොග් වීමේ සැපයුම්කරු (Google, හෝ ඊමේල් සහ මුරපදය). ඔබේ මුරපදය Firebase / Google විසින් හසුරුවනු ලැබේ — මෙම අඩවිය ඔබේ මුරපදය කිසිවිට නොදකින අතර ගබඩා නොකරයි.
ඔබ ZHENHUA Market එකෙන් ඇණවුම් කරන විට, Sell ඉල්ලීමක්, Creative විමසීමක් හෝ රැකියා සහාය විමසීමක් හෝ ZHENHUA Ecosystem හවුල්කරු අයදුම්පතක් හෝ අංශ විමසීමක් (Homes, Tickets, Automotive හෝ Gaming) යවන විට, අඩවිය zhenhuateam@gmail.com වෙත යොමු කළ ඊමේල් එකක් ඔබේම ඊමේල් යෙදුමේ සකසන අතර, ඔබම එය යවනු ලැබේ; ZHENHUA එය ඊමේල් හරහා ලබා ගනී. AI MASTER PRO අයදුම් පැකේජයත් එසේමයි: එය මෙම පිටුවේදීම සකසනු ලබන අතර ඔබම එය යවනු ලැබේ. 2026 නොවැම්බර් 7 සිට, ඔබ ඇතුළත් කළ තොරතුරු වල පිටපතක් (ඔබේ නම, සම්බන්ධතා තොරතුරු සහ ඔබ විමසූ දේ) සැබෑ ඉල්ලීම් ගණන් කිරීමට සහ ඒවාට පිළිතුරු දීමට ZHENHUA හිම දත්ත ගබඩාවේද (Firestore, hq_enquiries එකතුව) සුරැකේ; එම වාර්තා කියවිය හැක්කේ හිමිකරුට පමණක් වන අතර, එම එකතුව සඳහා දත්ත ගබඩා නීති ක්රියාත්මක කළ පසු සුරැකීම ආරම්භ වේ (QA වාර්තාව බලන්න). පණිවිඩ තිබෙන්නේ මෙම අඩවියේ නොව, ඔබේම ඊමේල් ගිණුමේ හෝ ඔබ අප හා සම්බන්ධ වීමට භාවිතා කළ යෙදුමේ (LINE වැනි), එම සේවාවේම පෞද්ගලිකත්ව නියමයන් යටතේය. මෙම අඩවියේ online ගෙවීමක් නැත, ගෙවීම් කිසිවක් අඩවිය හරහා ලබා නොගනී.
දැනුම්දීම් අත්යවශ්ය නොවේ. ඔබ “දැනුම්දීම් ක්රියාත්මක කරන්න” ඔබතොත්, Firebase Cloud Messaging උපාංග ටෝකනයක් සාදන අතර, එය ඔබේ බ්රවුසරයේ user-agent තන්තුව සහ වේලා මුද්රාවක් සමඟ Firestore හි push_tokens එකතුවේ ගබඩා වේ. ටෝකනයට නමක් හෝ ඊමේල් එකක් සම්බන්ධ නොවේ, අඩවියේ ආරක්ෂක නීති බ්රවුසර වලට ටෝකන නැවත කියවීමට ඉඩ නොදේ. ගිණුම් මෙනුවේ “Privacy & My Data” හරහා හෝ ඔබේ බ්රවුසර් සැකසුම් වලින් මෙම බ්රවුසරය සඳහා දැනුම්දීම් අක්රිය කළ හැක.
Google Analytics 4 (G-CNW81KD2C8) නිර්නාමික සංචාර සංඛ්යාලේඛන ගණනය කරයි: බලන ලද පිටු, දළ වශයෙන් රට/ප්රදේශය සහ උපාංග වර්ගය. ZHENHUA දැන්වීම් ට්රැකර් සකසන්නේ නැත. මෙය “Privacy choices” (footer) හෝ “Privacy & My Data” හරහා ඔබ පාලනය කරයි: ඔබ නිර්නාමික විශ්ලේෂණ අක්රිය කළහොත්, මෙම උපාංගයේ විශ්ලේෂණ කේතය කිසිසේත්ම පූරණය නොවේ. බ්රවුස් කිරීම සහ ලොග් වීම දෙකම ඕනෑම ආකාරයකින් එකසේ ක්රියා කරයි, මෙම තේරීම කිසිවිට ලොග් වීමට බැඳී නැත.
ඔබ AI සහායකයා සමඟ කතාබස් කරන විට, ඔබේ පණිවිඩ අපගේ AI සේවාවට (Cloudflare Worker) යවනු ලබන අතර, පිළිතුර උත්පාදනය කිරීම සඳහා එය Google හි Gemini AI වෙත යොමු කරයි. කතාබස් ඉතිහාසය මෙම ටැබයේ මතකයේ පමණක් තබා ගන්නා අතර, මෙම අඩවිය එය කිසිවිට ගබඩා නොකරයි. AI එක නොමිලේ මට්ටමකින් ක්රියාත්මක වන අතර, නොමිලේ මට්ටම් වලදී Google සිය නිෂ්පාදන වැඩිදියුණු කිරීමට යොමු කළ ප්රොම්ප්ට් භාවිතා කළ හැක — එබැවින් කරුණාකර AI කතාබස් තුළට පුද්ගලික තොරතුරු (නම්, ලිපින, දුරකථන අංක) දාන්න එපා.
Studio ඡායාරූප සකසනු ලබන්නේ ඔබේ උපාංගයේම පමණි: ඒවා මෙම පිටුවේ මතකයේ පෙරදසුන් ලෙස පමණක් පවතින අතර, කිසිම සර්වර් එකකට කිසිවිට උඩුගත නොවන අතර බ්රවුසර් ගබඩාවේ කිසිවිට සුරැකෙන්නේද නැත. Wardrobe ඡායාරූප සහ සුරකින ලද looks ගබඩා වන්නේ ඔබේම උපාංගයේ, ඔබේම බ්රවුසරයේ local storage එකේ පමණි. Studio එක demo ප්රකාරයේය — බාහිර AI එකක් සම්බන්ධ වී නැත. අනාගතයේදී සැබෑ බාහිර AI එකක් සම්බන්ධ කළහොත්, ඡායාරූපයක් කොහේ හෝ යැවීමට පෙර ඔබට ඒ බව දැනුම් දෙනු ලැබේ.
Firebase Authentication ගබඩාව (මෙම උපාංගයේ ඔබව ලොග් වී තබා ගැනීමට); zhAnalytics (ඔබේ විශ්ලේෂණ තේරීම); zhxNewsSeen (ඔබ අන්තිමට දුටු What's New අයිතමය); සහ AURELUNE සඳහා aurelune_wardrobe, aurelune_saved_looks සහ aurelune_last_city (ඔබේ wardrobe එක, සුරකින ලද looks සහ අන්තිම කාලගුණ නගරය — මෙම උපාංගයේ පමණි). කාලගුණ විශේෂාංගය Open-Meteo වෙත යවන්නේ ඔබ ටයිප් කරන නගරයේ නම පමණි; ගිණුම් දත්ත ඒ සමඟ යවනු නොලැබේ.
ඔබේ ගිණුම පවතින තුරු ගිණුම් තොරතුරු තබා ගනු ලැබේ. Push ටෝකනයක්, ඔබ මෙම බ්රවුසරය සඳහා දැනුම්දීම් අක්රිය කළ විට, බ්රවුසරයේ දැනුම්දීම් අවසරය ඉවත් කළ විට, හෝ ඔබේ ගිණුම මකා දැමූ විට භාවිතයට ගත නොහැකි වේ — Privacy & My Data dashboard එක මෙම බ්රවුසරයේ ටෝකනය මැකීමට උත්සාහ කරන අතර, සර්වර් පිටපත බ්රවුසරයෙන් මැකිය නොහැකි නම් ඒ බව අවංකව වාර්තා කරයි. විශ්ලේෂණ දත්ත Google විසින් Google Analytics හිම රඳවා ගැනීමේ සැකසුම් යටතේ තබා ගනු ලැබේ. ඔබ යවන ලද පණිවිඩ, ඔබ ඒවා යවන ලද කතාබස් යෙදුමේම පවතී.
ලොග් වී සිටින විට, ගිණුම් මෙනුවෙන් “Privacy & My Data” විවෘත කර මෙම අඩවිය ඔබ සඳහා පෙන්වන ගිණුම් දත්ත බැලීමට, මෙම උපාංගයේ ඔබ සඳහා තබා ඇති දත්ත වල JSON පිටපතක් බාගත කිරීමට, විශ්ලේෂණ ක්රියාත්මක හෝ අක්රිය කිරීමට, මෙම බ්රවුසරය සඳහා දැනුම්දීම් අක්රිය කිරීමට, සහ ඔබේ ගිණුම මැකීමට හැකිය. ඔබේ ගිණුම මැකීමෙන් ඔබේ Firebase Authentication ගිණුම මැකේ. ඔබ දැනටමත් අපට යවා ඇති ඊමේල් හෝ පණිවිඩ මැකීමට එයට නොහැකිය — ඒවා මෙම අඩවියේ පාලනයෙන් බැහැරය.
මෙම අඩවිය සාමාන්ය ප්රේක්ෂකයින් සඳහා වන අතර කුඩා ළමුන් ඉලක්ක කර නැත. ඔබ ජීවත් වන ස්ථානයේ මෙම නියමයන්ට එකඟ විය හැකි වයසේ නොමැති නම්, කරුණාකර දෙමාපියෙකු හෝ භාරකරුවෙකු සමඟ අඩවිය භාවිතා කරන්න.
“Privacy” යන වචනය සමඟ zhenhuateam@gmail.com වෙත අපට ඊමේල් එකක් එවන්න, හෝ Contact අංශයේ ඇති ලින්ක් එකෙන් LINE හරහා පණිවිඩයක් එවන්න — අපි පෞද්ගලිකවම පිළිතුරු දෙමු.
මෙම ප්රතිපත්තිය යහපත් විශ්වාසයෙන් සපයනු ලබන අතර, වෘත්තීය නෛතික සමාලෝචනයක් තවමත් අපේක්ෂිතය.
These terms are shown in English. They are also available in 日本語 and සිංහල — switch the site language to read them in that language.
ZHENHUA GROUP provides this website, SENSEI Pro links, ZHENHUA Market order requests, the Jobs in Japan information board and creative-service enquiries. Market orders are requests only: placing an order composes an email for you to send to zhenhuateam@gmail.com, and this site stores no order database — no contract or payment exists until ZHENHUA confirms personally with you, and there is no online checkout or payment on this site. The jobs board is information sharing, not employment placement; ZHENHUA GROUP is not a licensed employment agency, and employment terms are agreed between you and the employer. The AI Assistant's replies are generated by Google Gemini via our AI service and can be wrong — please check important details with us directly, and do not share personal information in AI chats. Accounts are provided by Firebase Authentication; you are responsible for keeping your sign-in details safe, and you may delete your account at any time from “Privacy & My Data” in the account menu. Content is provided honestly and may change as listings and products change. These terms are pending professional legal review.
ZHENHUA GROUPは、このウェブサイト、SENSEI Proへのリンク、ZHENHUA Marketの注文リクエスト、日本の求人情報ボード、クリエイティブサービスのお問い合わせを提供します。マーケットの注文はリクエストのみです。注文すると、zhenhuateam@gmail.com宛にあなたが送信するためのメールが作成されます。このサイトは注文データベースを保存せず、ZHENHUAがあなたと直接確認するまで契約や支払いは発生しません。このサイトにはオンライン決済はありません。求人ボードは情報提供であり、職業紹介ではありません。ZHENHUA GROUPは有料職業紹介事業者ではなく、雇用条件はあなたと雇用主の間で合意されます。AIアシスタントの返信は、当社のAIサービスを通じてGoogle Geminiが生成するもので、誤りを含む場合があります。重要な内容は直接お問い合わせのうえご確認ください。また、AIチャットには個人情報を入力しないでください。アカウントはFirebase Authenticationが提供します。ログイン情報の管理はご自身の責任となります。アカウントは、アカウントメニューの「プライバシーとあなたのデータ」からいつでも削除できます。コンテンツは誠実に提供しますが、掲載内容や商品の変更に伴い変更される場合があります。本規約は専門家による法的レビューが今後の課題です。
ZHENHUA GROUP මෙම වෙබ් අඩවිය, SENSEI Pro ලින්ක්, ZHENHUA Market ඇණවුම් ඉල්ලීම්, Jobs in Japan තොරතුරු පුවරුව සහ creative-service විමසීම් සපයයි. Market ඇණවුම් ඉල්ලීම් පමණි: ඇණවුමක් දැමීමෙන් ඔබ zhenhuateam@gmail.com වෙත යැවීමට ඊමේල් එකක් සකසනු ලබන අතර, මෙම අඩවිය කිසිම ඇණවුම් දත්ත ගබඩාවක් ගබඩා නොකරයි — ZHENHUA ඔබ සමඟ පෞද්ගලිකව තහවුරු කරන තුරු කිසිම ගිවිසුමක් හෝ ගෙවීමක් නැත, මෙම අඩවියේ online ගෙවීමක්ද නැත. රැකියා පුවරුව තොරතුරු බෙදාගැනීමක් මිස රැකියා ස්ථානගත කිරීමක් නොවේ; ZHENHUA GROUP බලපත්රලාභී රැකියා ආයතනයක් නොවන අතර, රැකියා නියමයන් එකඟ වන්නේ ඔබ සහ සේවායෝජකයා අතරය. AI සහායකයාගේ පිළිතුරු අපගේ AI සේවාව හරහා Google Gemini විසින් උත්පාදනය කරනු ලබන අතර ඒවා වැරදි විය හැක — වැදගත් විස්තර අප සමඟ සෘජුවම පරීක්ෂා කරන්න, AI කතාබස් තුළ පුද්ගලික තොරතුරු බෙදා නොගන්න. ගිණුම් Firebase Authentication විසින් සපයනු ලැබේ; ඔබේ ලොග් වීමේ තොරතුරු ආරක්ෂා කර ගැනීම ඔබේ වගකීම වන අතර, ගිණුම් මෙනුවේ “Privacy & My Data” හරහා ඕනෑම විටෙක ඔබේ ගිණුම මැකිය හැක. අන්තර්ගතය අවංකව සපයනු ලබන අතර ලැයිස්තු සහ නිෂ්පාදන වෙනස් වන විට වෙනස් විය හැක. මෙම නියමයන් සඳහා වෘත්තීය නෛතික සමාලෝචනයක් තවමත් අපේක්ෂිතය.
This summary is shown in English. It is also available in 日本語 and සිංහල — switch the site language to read it in that language.
Analytics: if anonymous analytics is on in your Privacy choices, Google Analytics sets cookies to count visits. If it is off, the analytics code never loads on this device and this site sets no analytics cookies. Sign-in: Firebase Authentication uses browser storage (local storage / IndexedDB) to keep you signed in on this device — this is required for login to work and is separate from analytics. Site storage: this site stores a small amount of data in your browser's local storage — your analytics choice, which What's New item you have seen, and AURELUNE wardrobe photos, saved looks and last weather city (this device only — see the Privacy Policy). No advertising trackers are set by ZHENHUA GROUP. You can clear cookies and site storage in your browser settings at any time; you will be signed out and saved looks will be removed from this device.
アクセス解析:プライバシー設定で匿名の解析がオンの場合、Google Analyticsは訪問を集計するためにCookieを設定します。オフの場合、この端末では解析コード自体が読み込まれず、このサイトによる解析Cookieは設定されません。ログイン:Firebase Authenticationは、この端末でログイン状態を保持するためにブラウザのストレージ(ローカルストレージ / IndexedDB)を使用します。これはログインの動作に必要で、解析とは別です。サイトのストレージ:このサイトは、解析の選択、最後に見たWhat's New、AURELUNEのワードローブ写真・保存したルック・最後の天気の都市を、ブラウザのローカルストレージに少量保存します(いずれもこの端末のみ。詳細はプライバシーポリシーをご覧ください)。ZHENHUA GROUPは広告トラッカーを設定しません。Cookieとサイトストレージはブラウザ設定からいつでも消去できます。その場合、ログアウトし、保存したルックはこの端末から削除されます。
විශ්ලේෂණ: ඔබේ Privacy choices වල නිර්නාමික විශ්ලේෂණ ක්රියාත්මක නම්, Google Analytics සංචාර ගණනය කිරීමට කුකීස් සකසයි. අක්රිය නම්, මෙම උපාංගයේ විශ්ලේෂණ කේතය කිසිවිට පූරණය නොවන අතර මෙම අඩවිය විසින් විශ්ලේෂණ කුකීස් සකසනු නොලැබේ. ලොග් වීම: Firebase Authentication මෙම උපාංගයේ ඔබව ලොග් වී තබා ගැනීමට බ්රවුසර් ගබඩාව (local storage / IndexedDB) භාවිතා කරයි — මෙය ලොග් වීම ක්රියා කිරීමට අවශ්ය අතර විශ්ලේෂණ වලින් වෙන්ව පවතී. අඩවි ගබඩාව: මෙම අඩවිය ඔබේ බ්රවුසරයේ local storage හි කුඩා දත්ත ප්රමාණයක් ගබඩා කරයි — ඔබේ විශ්ලේෂණ තේරීම, ඔබ දුටු What's New අයිතමය, සහ AURELUNE wardrobe ඡායාරූප, සුරකින ලද looks සහ අන්තිම කාලගුණ නගරය (මෙම උපාංගයේ පමණි; පෞද්ගලිකත්ව ප්රතිපත්තිය බලන්න). ZHENHUA GROUP දැන්වීම් ට්රැකර් සකසන්නේ නැත. ඔබට ඕනෑම විටෙක ඔබේ බ්රවුසර් සැකසුම් වලින් කුකීස් සහ අඩවි ගබඩාව මැකිය හැක; එවිට ඔබ ලොග් අවුට් වන අතර සුරකින ලද looks මෙම උපාංගයෙන් ඉවත් වේ.
品質 Quality & Transparency
What was fixed in this overhaul, how it was checked, and what honestly remains. Nothing untested is marked as passed.
| Area | Issue found (severity) | Fix implemented | Test | Result | Remaining action |
|---|---|---|---|---|---|
| Corporate structure | “Three divisions” vs “two living divisions” contradiction (High) | One structure everywhere: 2 active divisions + group services + clearly-labelled future ventures | Full-page text review | PASS | — |
| Navigation | Missing SENSEI Pro / Divisions / Contact destinations (Medium) | Full 11-destination nav per brief; every link points to a real section or view | Link-by-link click check in build audit | PASS | — |
| Brand & SEO | No canonical / OG / structured data (Medium) | Official palette (#0B0B0D · #C6A45C · #BFC3C8 · #F5F3EE), canonical, OG/Twitter cards, Organization JSON-LD, slogan “From Japan to the World” | Source inspection | PASS | sitemap.xml / robots.txt live on the Firebase host, outside this page file |
| Marketplace | Samples mixed with real items; no availability/seller info (High) | Samples labelled display-only with Buy removed; real items show availability + “Sold by ZHENHUA GROUP”; search + category filters kept | Filter & card render check | PASS | Online payment not integrated — orders stay personal via email by design |
| Jobs board | Only region filter; no search/wage/time filters or legal notice (High) | Search + category + wage + time filters added; per-listing “last verified” date; stale listings (>60 days) auto-hidden; full legal notice added | Filter logic wired to the single JOB_POSTINGS source | PASS | Daily re-verification of listings continues as a separate routine |
| SENSEI Pro | Feature list incomplete vs verified app (Medium) | Verified features only: JLPT N5–N1, kana, vocabulary, kanji, grammar, conversation, Baito Japanese, mock exams, 13 languages | Checked against live app feature set | PASS | In-development features stay labelled inside the app |
| Login & forms | Duplicate submissions possible (Medium) | Submit buttons lock while a message is being composed; validation via native form checks; forms compose a message — no fake “submitted” success anywhere | Code review of all four form flows | PASS | Live Google/email sign-in, password reset and logout must be re-tested on the production Firebase host after deploy — NOT TESTED in this page build |
| Privacy & legal | No Privacy / Terms / Cookie pages (High) | Privacy Policy, Terms and Cookie & Data sections added, linked from the footer | Content review | PASS | Professional legal review (APPI/GDPR) still required |
| LINE updates | Users asked for app/website details via LINE (Medium) | LINE contact button added (personal add-friend link) | Link check | PASS | Automatic push of user/app data to LINE needs a LINE Official Account + Messaging API — cannot be done from the add-friend link alone |
| Security | Frontend config review (Medium) | No private credentials in this page; Firebase web config is a public client identifier by design — access is governed by Firebase rules on the server side | Source scan | PASS | Firestore/Storage rules review happens in the Firebase console, outside this page |
| Jobs Statistics | Hero stats rested on “–” placeholders; Highlights jobs line was hardcoded stale copy (“checked 5 Nov 2026”) (High) | Stats computed at page load from the active JOB_POSTINGS set (stale >60 days and expired listings excluded); placeholders removed — the resting value is always the real number; stats hide and “New verified opportunities will be published here soon.” shows when no active listings exist; Highlights jobs line and board note now computed from the same data in EN/JA/SI | Source + render-logic review against the 73 postings / 13 regions in the single data array | PASS | Daily re-verification of listings continues as a separate routine |
| Marketplace — empty state | Default view could show “No items match your search” while the three real Kandyan listings exist (High) | Filter state reset on load (All categories, empty search, empty state hidden); the empty message now appears only when a visitor's own search/filter matches nothing; featured Highlights card and Marketplace read the same MARKET_ITEMS array — the Highlights price line is computed from the real items at runtime | Render-logic review: default view lists all 9 entries (3 real + 6 labelled samples); search/filter paths re-checked | PASS | — |
| Daily Pay Jobs | Category titled “HAND CASH JOBS” with an over-promising tagline (Medium) | Renamed “DAILY PAY & SHORT-TERM JOBS” (EN/JA/SI); descriptor now states payment method and timing follow each employer's actual terms and reminds students of work-permission + 28-hour rules; every pay-type card shows a Payment line (method + timing) derived from its verified payType, alongside employer, location, wage, source and verified date; the cash/daily split is always computed, never hardcoded | Source review of JOB_LABELS and card renderer | PASS | Only postings whose source page states cash-in-hand or daily/weekly pay carry the badge — all others show no pay claim |
| Job Filters | No listing ID, employment type, status or expiry handling; no sort control (Medium) | Every card now shows a stable listing ID (ZHJ-001… by board order), a Part-time type label and Active/Expired status; the four postings with verified closing dates carry an expires field (8–10 Nov 2026) — past that date they render badged Expired with Apply disabled and drop out of the active statistics; “Recently updated” sort (newest verified first) added beside the existing search + region + category + wage + time filters | Filter/sort logic review against JOB_POSTINGS | PASS | Expiry behaviour activates automatically on the stated dates |
| Firebase Rules | Backend audit requested (High) | Firestore rules source-reviewed: strict field whitelists, admin-only moderation, default-deny catch-all — no change needed and none made. Job and product listings live in this page's data arrays by design (not Firestore collections) and were not migrated. The Firebase web apiKey in the page is a public client identifier, not a secret | Rules source review (owner audit, 6 Nov 2026) | PASS | Owner-side Firebase console review still recommended |
| Firebase Storage | Storage rules written but no bucket exists yet (Medium) | No change possible from this page — rules deploy only after the Firebase Blaze upgrade creates the bucket | Configuration check | NOT CONFIGURED | Blaze upgrade (owner's billing step) required first |
| Privacy Pages | Must stay reachable and accurate (Medium) | Privacy Policy, Terms of Service and Cookie & Data sections reviewed against the site's actual data use (Firebase Auth, GA4, email/LINE message channels, on-device AURELUNE photos) and remain linked from the footer | Content review + footer link check | PASS | Professional legal review (APPI/GDPR) still required — flagged in the policy text itself |
| Forms | Validation, duplicate submissions, fake success (Medium) | All four forms (contact/creative enquiry, Market buy, Sell, Ecosystem) validate required fields natively, lock their submit button while composing, and only ever present a composed message for the visitor to send — no fake “submitted” state | Code review of all form flows | PASS | Production Google/email sign-in + password reset re-test: NOT TESTED (needs a live sign-in) |
| Email Links | Order/enquiry routing (Low) | All email actions use the single ZHENHUA_ORDER destination configured at the top of the Market script — one place to update | Source check of every email href/composer | PASS | Routes to the official ZHENHUA team email, zhenhuateam@gmail.com |
| Mobile Layout | Phone-width overflow / tap targets (Medium) | Jobs stats, filter tools and cards reflow at phone width; new sort control joins the existing wrapping filter row | Build audit at desktop + phone widths | PASS | — |
| SEO | Indexing quality (Low) | Canonical, Open Graph, JSON-LD, descriptive alt text already in place from the overhaul; no duplicate titles introduced by this fix round | Source inspection | PASS | sitemap.xml / robots.txt live on the Firebase host, outside this page file |
| ZHENHUA AI Assistant | Visitors had no in-page way to ask about the company, its divisions, SENSEI Pro, the Jobs board, the Market, Global Support, AURELUNE ATELIER or DELA ON THE BEAT (New) | Floating “AI Assistant” button opens a black & gold chat panel on every view; it talks to the same Sakura AI backend the SENSEI Pro app uses (POST {messages, mode:“zhenhua”, lang}) and replies in the visitor's language. On any backend error or the shared daily free quota, the panel shows an honest busy/unavailable state with the site's email and LINE links — never a pre-written answer. Chat history is kept in page memory only, with a privacy note in the panel; no API key or secret in the page. ZHENHUA AI MASTER PRO on the Jobs page is untouched | Panel open/close, send flow, exact request shape and both reply rendering and the error/unavailable state exercised in the build environment against a stubbed fetch stand-in — no live backend call made | PASS | Live AI replies: NOT TESTED — the shared free daily quota was deliberately not spent during the build; first live check happens in production use |
| Site languages — 14 | Switcher offered only EN / JA / SI while the audience spans many more first languages (New) | Switcher is now a 14-language menu listing native names (English, 日本語, සිංහල, မြန်မာ, Tiếng Việt, 简体中文, 한국어, Bahasa Indonesia, नेपाली, हिन्दी, ไทย, Filipino, Português, Español). All UI strings translated with the same i18n keys — the full 284-key main dictionary per language, plus job-board labels, enquiry modal titles and login strings; proper nouns (ZHENHUA GROUP, SENSEI Pro, AURELUNE ATELIER, DAIKI DELA), prices, job data and URLs unchanged; selection applies through the same setLang mechanism as before. Long-form dynamic content that was never translated beyond EN/JA/SI keeps the existing English-fallback pattern | Dictionary parity check (284/284 keys in every language, {placeholders} intact) + switcher exercised across languages in the build audit | PASS | Native-speaker review of the 11 new translations recommended |
| Highlights jobs line — JA/SI | JA/SI versions still showed the old jobs count/date after the English line was corrected to 73 listings / 7 Nov 2026 (Medium) | Japanese entry now reads 73件・2026年11月7日確認 and the Sinhala entry 73 listings / 2026 නොවැම්බර් 7, same sentence structure as before; a What's New item (7 Nov 2026, “73 verified part-time jobs are live”) added in EN/JA/SI at the top of the What's New list | Source check of the hl1D entries and the WHATS_NEW array | PASS | — |
| Privacy — data audit (7 Nov 2026) | Policy text had to match where each data type actually lives (High) | Full source audit of every data flow. Where each data type actually lives: accounts → Firebase Authentication only (name, email, profile photo, provider); Market orders / Sell requests / Creative enquiries / AI MASTER PRO sends → composed as email messages in the visitor's own app, stored in NO database by this site; push subscriptions → Firestore push_tokens {targets, ua, updatedAt}, opt-in only, no client reads; visit statistics → Google Analytics 4 (G-CNW81KD2C8), anonymous; AI Assistant messages → sent to the AI service (Cloudflare Worker → Google Gemini) to generate replies, history in tab memory only; AURELUNE photos → on the visitor's device only (see photo row below); site preferences → this browser's local storage (zhAnalytics, zhxNewsSeen, aurelune_wardrobe, aurelune_saved_looks, aurelune_last_city). There is no Firebase Storage bucket, no online checkout and no server database of enquiries, and the policy now says exactly that | Line-by-line source review of the auth, forms, push, analytics, AI and fashion code paths | PASS | — |
| Privacy Policy rewrite (7 Nov 2026) | Previous policy was shorter than the site's real data use and its cookie text did not match any consent behaviour (High) | Privacy Policy rewritten itemised — accounts, email-composed enquiries (not stored), push tokens, GA4 analytics, AI Assistant messages (incl. the free-tier note that Google may use prompts to improve its products), AURELUNE on-device photos, browser storage, retention, visitor controls, children, and only contact routes that really exist (the official email zhenhuateam@gmail.com, the LINE link) — in English, Japanese and Sinhala following the site's language switcher; other languages see the English text with a clear note. Terms and Cookie sections given the same accuracy pass. No compliance is claimed anywhere; the policy keeps the honest “pending professional legal review” line | Content review against the data audit row above; language versions follow the switcher | PASS | Professional legal review still required — flagged in the policy text itself |
| Privacy & My Data dashboard (7 Nov 2026) | Signed-in users had no in-site way to see, download or delete their data (New) | “Privacy & My Data” added to the account menu: real account name / email / connected provider / sign-in state read from Firebase, notifications state for this browser, and the analytics toggle. Actions: Download my data (JSON of account basics + this device's local preferences, with the honest note that enquiries/orders are not stored by the site); Turn off notifications for this browser (invalidates this browser's FCM token and attempts to delete its push_tokens document, reporting the real outcome of each step); Delete my account (two-step confirmation, re-authentication via the existing Google / email-password providers when Firebase requires it, honest per-step result — never a fake “everything deleted”) | Analytics toggle exercised live in the Privacy choices dialog (the same shared control the dashboard uses, incl. persistence across reload); dashboard code, download generation and delete flow source-reviewed. Signed-in dashboard actions could not be exercised in the build harness — Firebase is unreachable from the sandbox and no test account was used | PASS | Live account deletion against production Auth: NOT TESTED — code path source-reviewed only; first real exercise is the owner's own deletion test if ever wanted |
| Analytics consent (7 Nov 2026) | GA4 loaded for every visitor with no way to opt out (High) | Site-wide “Anonymous usage analytics” choice (footer “Privacy choices” + dashboard toggle), stored in localStorage (zhAnalytics), separate from login and never bundled into it. When off, the GA4 script is not loaded at all on this device and Google's disable flag is set; the site and login work fully either way | Toggle exercised live in the build harness — switched off in the Privacy choices dialog and still off after a full page reload (choice persisted in localStorage); the head gate that loads GA4 only when the stored choice is “on” source-verified | PASS | — |
| AURELUNE photo verification (7 Nov 2026) | Privacy claim “photos never leave the device” had to be proven in code, not just written (High) | Verified in the actual fashion code: Studio photos exist only as in-memory object URLs (URL.createObjectURL) — never uploaded, never written to storage. Wardrobe photos are downscaled on a canvas and stored only in this browser's localStorage (aurelune_wardrobe). The fashion view's only network calls are Open-Meteo weather/geocoding (city name + coordinates only — no photo data). No code path sends photo data anywhere; none had to be removed. On-page consent and demo wording strengthened: if a real external AI is connected in the future, users will be told BEFORE any photo is sent | Full source audit of every fetch / upload / storage call in the fashion view | PASS | — |
| Security audit — secrets & keys scan (7 Nov 2026) | Exposed credentials would compromise the whole system (High) | No private credential found, and none was present to remove. The only key-like strings in the page are the Firebase web config — a public client identifier, not a secret: access is governed by Firebase's server-side rules, not by hiding it — and the FCM VAPID key, which is the public half of a keypair and public by design. The AI service's API key exists only on the Cloudflare Worker backend and was never in this page; there is no password, private key, service-account material or bearer token anywhere in the file | Pattern scan of the full page source (API-key shapes, private-key blocks, service accounts, tokens) with manual review of every match | PASS | Nothing to rotate. If the Worker key ever needs rotation, it happens on the Worker — it must never be placed in this page |
| Security audit — rendering & injection (7 Nov 2026) | Any unescaped rendering of user or AI content is a cross-site scripting hole (High) | Every one of the page's innerHTML sinks was audited: the Market grid, Jobs board, AURELUNE (collection, look render, saved looks, wardrobe, weather) and AI MASTER PRO (wizard + application pack) all render data through an escape function, and the auth button escapes the account name/photo URL. The ZHENHUA AI Assistant renders both the visitor's messages and the AI's replies with textContent only — AI replies are never inserted as HTML. Form results (order, Sell, enquiry, enquiry modal) are written into <pre> elements via textContent, and What's New renders via textContent. The page contains no eval, no Function constructor, no document.write and no insertAdjacentHTML. The only unescaped insertions are the site's own authored dictionary strings (data-i18n, one AI MASTER PRO step line), which contain no user or AI data | Line-by-line audit of all 38 innerHTML assignments in the source, plus sink-pattern scan | PASS | Standing rule for future code: render as text, or escape — never insert user/AI content as HTML |
| Form validation hardening (7 Nov 2026) | Form inputs had required checks but no length caps (Medium) | Length caps added to every input, sized to its purpose: Market order (name/contact/country 100, address 500, note 1,000), Sell (name/contact/item 100, description 2,000), Creative enquiry (name 100, contact 200, message 2,000), AI MASTER PRO steps (name 100, email 254, phone 30, city 100, hours 10, time note 100), login + re-authentication (email 254, password 128), AI Assistant message 2,000, Jobs/Market search and the AURELUNE city field 100. Order quantity is capped at 99 and asking price at ¥99,999,999 via native min/max, enforced by the reportValidity() checks every submit already runs — behaviour for legitimate users is unchanged | Attribute review of every form in the page + handler review (all submit flows still validate before composing) | PASS | Live production exercise happens in normal use — no destructive or fake testing was run against production, per the brief |
| Security Center (7 Nov 2026) | The owner had no single place showing the site's real security state (New) | An owner-only “Security Center” panel added to the account menu: it stays hidden unless the signed-in email matches the owner address used by the Team Review page and by the rules' isAdmin() check, the open handler re-checks before opening, and it closes on sign-out. Inside: 16 evidence-based statuses (Secure / Warning / Not Tested / Not Applicable — deliberately no percentage score and no “100% secure” claim anywhere), an incident-response plan (defacement, compromised account, suspected data exposure) and a backup & recovery plan, all written for this exact setup — Firebase Hosting rollback, the project backups folder, rules redeploys — with no tooling that does not exist. This page-level gate is visibility only; real enforcement stays in the Firestore rules | Gate logic source-reviewed end to end (hidden default, email match, re-check on open, close on sign-out); panel content reviewed line by line against the ground truth of what is actually deployed | PASS | Live admin visibility: NOT TESTED — it needs the owner's real sign-in on the production host; no test account was used and no fake sign-in was staged |
| Firestore rules review (7 Nov 2026) | Backend rules had to be re-verified for this security round (High) | Review of record of the deployed rules source (firestore.rules, deployed 7 Nov 2026). Findings: the file closes with a default-deny catch-all (allow read, write: if false); push_tokens accepts only the exact {targets, ua, updatedAt} shape with size caps and denies all client reads, lists and deletes; community_messages, community_moments and their comments, members, study_stats, banned, stories, follows, friend_requests and videos each carry strict key whitelists, type/size checks and uid-ownership checks; content creates are gated by notBanned(); study_stats are readable by the admin only; isAdmin() requires the owner's exact Gmail and a verified email. Conclusion: the rules match the intended design — no change needed and none made; rules live outside this page and this build did not modify them | Full read of the rules source of record, collection by collection, against the site's actual data use | PASS | This is a review of record, not a live probe — the page cannot read the deployed rules. Re-verify in the Firebase console after any future rules deploy |
| Security headers — recommended set (7 Nov 2026) | The hosting layer sends no hardening headers yet (Medium) | Recommended set for the owner to apply in firebase.json → hosting → headers (source “**”) — headers cannot be set from inside this page. X-Content-Type-Options: nosniff · Referrer-Policy: strict-origin-when-cross-origin · X-Frame-Options: SAMEORIGIN · Permissions-Policy: camera=(), microphone=(), geolocation=(self), payment=(), usb=() · Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' https://www.gstatic.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https://lh3.googleusercontent.com https://www.google-analytics.com; connect-src 'self' https://firestore.googleapis.com https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://fcmregistrations.googleapis.com https://www.google-analytics.com https://region1.google-analytics.com https://www.googletagmanager.com https://sakura-ai.kazuojapanesesl.workers.dev https://api.open-meteo.com https://geocoding-api.open-meteo.com; frame-src https://zhenhuagroup.firebaseapp.com https://accounts.google.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'. Notes: the origins are exactly the ones this page really uses (Firebase SDK + Auth + Firestore + FCM, GA4, Google Fonts, the AI Worker, Open-Meteo, Google profile photos); 'unsafe-inline' is required by this single-file page, whose code is inline by design — removing it would need a nonce-based restructure. Apply the CSP first as Content-Security-Policy-Report-Only, use the whole site (login, push opt-in, AI Assistant, analytics, AURELUNE weather), then switch to enforcing once reports are clean | Origin inventory taken from the page's actual script/link/API usage; header set cannot be applied or verified from inside the page | NOT TESTED | Owner applies the set in the Firebase hosting config and redeploys hosting, then verifies the response headers on the live site |
| Backup, recovery & incident response (7 Nov 2026) | Backups existed but no written recovery or incident procedure (Medium) | Written plans added to the Security Center: where backups live (dated index.html copies in the project backups folder, plus Firebase Hosting's release history), hosting rollback and redeploy recovery steps, and incident steps for defacement, a compromised account and suspected data exposure — real steps for this setup only. Honest gaps kept visible: Firestore managed backups / point-in-time recovery are not configured, and no automated security alerting exists (GA4 and the Team Review dashboard are manual) | Content review against the actual infrastructure — no fictional tooling, no invented retention or SLA claims | PASS | Restore drill: NOT TESTED — backups exist, but no restore has ever been performed; the first drill should follow the written steps in the Security Center |
| Account deletion — carried status (7 Nov 2026) | Status from the Privacy round had to be carried honestly, not upgraded by silence (Medium) | No change this round. Account deletion remains implemented in Privacy & My Data (two-step confirmation, re-authentication when Firebase requires it, honest per-step results) and remains unexercised against production — the status shown in the Security Center is Not Tested, matching this row | Status reconciliation between the Privacy round's QA row and the new Security Center board | NOT TESTED | Only the owner can close this — by deleting a real (e.g. throwaway) account in production, or accepting the code-reviewed state |
| Monitoring & alerting (7 Nov 2026) | No automated alerting exists for security events (Low) | Recorded honestly rather than papered over: there is no automated security alerting. Visit statistics (GA4) and the Team Review dashboard are checked manually, and the Security Center states this as a Warning | Configuration review of the whole stack (page, hosting, rules, Worker) | NOT CONFIGURED | If wanted later, alerting is a Firebase/Google console-side setup (e.g. billing and abuse alerts) — it cannot be created from inside this page |
| Payments / Storage / Cloud Functions (7 Nov 2026) | Security scope had to state plainly what does not exist (Info) | Nothing to secure in-page, and nothing was invented: there is no checkout or card handling anywhere on the site (Stripe awaits the owner's own signup/KYC); there is no Firebase Storage bucket (the Blaze plan is not enabled); there are no Cloud Functions or custom claims. The future rules are written into the Security Center: reputable payment provider only, never store raw card data, verify payment webhooks server-side; any future Storage bucket gets deny-by-default rules before first use | Full-stack configuration review against the ground truth for this build | NOT APPLICABLE | Revisit this row when payments or the Blaze upgrade actually land |
| CEO Control Center — gate (7 Nov 2026) | The owner needed one private headquarters for the whole group (New) | A “CEO Control Center” added to the account menu using the exact Security Center gate pattern: the button stays hidden unless the signed-in email matches the owner address used by the Team Review page and the rules' isAdmin() check, the open handler re-checks before opening, and it closes on sign-out. Landing: “WELCOME TO ZHENHUA GROUP HEADQUARTERS / FOUNDER / OWNER / CEO — DAIKI DELA / FROM JAPAN TO THE WORLD”, in the brand palette (Obsidian Black #0B0B0D / Royal Gold #C6A45C / Platinum Silver #BFC3C8 / Ivory White #F5F3EE). Twelve modules: Executive Overview, Divisions, Finance & Accounting, HR, Sales & Marketplace, Customers, Partners, Approval Center, Reports & Analytics, Security Center (opens the existing panel — not duplicated), Strategy & Planning, Company Settings. This page-level gate is visibility only; enforcement is in the Firestore rules | Gate logic source-reviewed end to end (hidden default, email match, re-check on open, close on sign-out); module render checked in the build harness with no signed-in user (panel never opens) | PASS | Live owner visibility: NOT TESTED — needs the owner's real sign-in on the production host; no test account exists and no fake sign-in was staged |
| HQ data model & Firestore rules — TO DEPLOY (7 Nov 2026) | HQ modules need real collections; this build must not change rules itself (High) | Collections designed (all prefixed hq_): hq_divisions (division records), hq_finance (revenue/expense records), hq_budgets (budgets), hq_employees (HR records — records only, never auth accounts), hq_tasks (statuses: Not Started / In Progress / Under Review / Completed / Blocked, with due dates so overdue is computed), hq_approvals, hq_partners, hq_enquiries (stored Market orders / Sell requests / Creative enquiries / job-support enquiries), hq_announcements, hq_messages, hq_meetings, hq_documents (metadata only), hq_goals, hq_settings (single doc), hq_audit (who / what / when / which record / success — passwords, tokens and secrets are never written to it). Rules May must deploy (firestore.rules, mirroring the existing isAdmin()): for every hq_* collection except hq_enquiries — allow read, write: if isAdmin(); For hq_enquiries — allow create: if signed-in AND the document has exactly the keys {type, name, contact, summary, uid, email, status, createdAt} with type in {market_order, sell_request, creative_enquiry, job_support} and string size caps (name ≤ 120, contact ≤ 120, summary ≤ 600); allow read, update, delete: if isAdmin(); Role assignment is owner-only: no rule may read a role from a client-writable field, so nobody can self-promote from the frontend or through Firestore fields. Until these rules are deployed, the existing deny-by-default catch-all blocks every HQ read and write, and the Control Center labels its data state “pending rules” instead of showing invented numbers | Data model and rules text reviewed against the brief and the deployed rules' existing patterns (isAdmin, field whitelists, size caps, default-deny) | NOT TESTED — pending rules deployment | May: add the rules above to firestore.rules and deploy, then re-test each module signed in as the owner. No HQ feature that depends on these rules is claimed as working before that deploy |
| Org chart & HR (7 Nov 2026) | Hierarchy had to be real, with no invented people (High) | HR module shows L1 Founder/Owner/CEO — DAIKI DELA → L2 Executive Management → L3 Department Managers ×7 (Technology, Marketplace, Finance, HR, Marketing, Operations, Customer Support) → L4 Employees → L5 External Users. All seven manager posts start VACANT and stay visibly VACANT until the owner appoints someone by adding a real HR record; the module reads appointments from hq_employees and never invents a name. No fake employee accounts were created — HR records are database records only and create no sign-in accounts. The 9 roles are listed with department-scoped access notes (Finance access does not grant HR access; external users never see internal modules) | Source review of the HR renderer against the brief; vacancy state is the default with zero records | PASS | Live appointment flow: NOT TESTED — depends on the hq_employees rules above being deployed |
| Finance & Accounting (7 Nov 2026) | Finance had to start from the truth: nothing recorded (High) | Finance opens EMPTY: recorded revenue ¥0, no records, no balances, no P&L figures — the P&L is computed only from records the owner adds to hq_finance, and budgets only from hq_budgets. The owner can add revenue/expense records (amount, category, date, note, status) and budgets. Approved records are locked: they cannot be edited — the only path is the controlled correction flow, which files a linked correction record (original id + reason) that the owner then approves or rejects in the Approval Center, keeping the full audit history in hq_audit. Nothing in the module annualises, estimates or annual-revenue-projects any figure | Source review: totals are pure sums over loaded records; with zero records every total renders ¥0 and the empty state shows | PASS | Saving records: NOT TESTED — writes are blocked until the HQ rules are deployed; a record added before then is kept only in this tab's memory and is badged “Not saved — pending rules”, never presented as stored |
| Approval Center (7 Nov 2026) | Approvals needed a tamper-resistant shape (Medium) | 8 categories: Budget & Spending, Hiring, New Project, Partnership, Marketing Campaign, Equipment Purchase, Content & Media, Other. Every request carries requester, department, description, cost, justification, date and status (Pending / Approved / Rejected / More Information Required / Cancelled). Self-approval is blocked in the logic: when the requester email equals the signed-in email, the decision buttons are disabled and the row states why — nobody can approve their own request. Each decision records decision-maker, date/time and reason | Source review of the decision handler, including the self-approval guard and the decision fields written | PASS | Live multi-account approval flow: NOT TESTED — no second account exists to request as; also depends on the hq_approvals rules |
| Stored enquiries (7 Nov 2026) | Dashboards could not count demand because enquiries were stored nowhere (Medium) | The Market order, Sell, Creative enquiry and job-support (enquiry modal) flows are unchanged for the user — same forms, same composed email message. In parallel, the page now also tries to save a record of each sent enquiry to hq_enquiries (type, name, contact, summary, sender uid/email, status “new”), and those records feed the Customers module and the Executive Overview counts — real records only. Privacy Policy §2 (EN/JA/SI) and the Security Center were updated to describe this honestly | Source review of the capture hook (fires on the same submit/click as the existing flows, reads the composed message, never blocks or alters the email behaviour, fails silently) | PASS | Actual saving: NOT TESTED — Firestore will deny the write until the hq_enquiries create rule above is deployed; until then enquiries behave exactly as before (email only, stored nowhere) |
| Document Center & Communication Center (7 Nov 2026) | Records without fake uploads or fake messages (Medium) | Document Center (inside Company Settings): categories Contracts, Finance, HR, Legal, Marketing, Operations, Company — metadata records only (title, category, permission level, version label, activity), stored in hq_documents. File uploads are NOT offered: they are gated on Firebase Storage, which needs the Blaze plan, and the module labels them “uploads pending storage setup”. CEO Communication Center (inside Executive Overview): announcements, internal message records and meeting notes from hq_announcements / hq_messages / hq_meetings, with unread counts computed from read flags on real records only — with zero records, unread is 0 | Source review; no upload control exists anywhere in the module, and unread counts are sums over loaded records | PASS | Saving metadata/announcements: NOT TESTED — pending the HQ rules deployment |
| Reports & Analytics (7 Nov 2026) | Reports had to reflect records, not vibes (Medium) | Daily / weekly / monthly views computed only from the loaded real records (enquiries received, finance in/out from hq_finance, approvals decided, tasks completed), with a Download button that exports exactly what is shown as a text report. The module states plainly that website traffic (GA4) is not revenue and is never mixed into these figures | Source review of the aggregation (date-window filters over loaded records only) and the export (Blob download of the rendered report) | PASS | With the rules undeployed the report honestly shows zeroes/empty — live figures: NOT TESTED until records exist |
| HQ languages (7 Nov 2026) | New UI strings needed the site's language pattern (Low) | Control Center strings are provided in English, Japanese and Sinhala, and every other language falls back per-string to English — the same fallback rule the main dictionary uses — so no label is ever blank. The existing 284-key dictionary was not touched, so its 14-language parity is unchanged | Source review of the HQ string table and its fallback function | PASS | — |
| ZHENHUA CRYPTO MARKET — new section (7 Nov 2026) | Brief asked for a professional crypto market monitoring dashboard inside the existing site, without rebuilding anything (New) | New “CRYPTO MARKET” nav destination opens a dedicated view (Jobs/Fashion view pattern — all existing sections, login, CEO HQ, Security Center, AI Assistant, AURELUNE, Jobs board and Market untouched). Institutional black/gold/platinum styling, ticker tape, market statistics strip, watchlist sidebar, TradingView Advanced Chart, Top Gainers/Losers, Coins Heatmap and Cryptocurrency Market widgets, USD/JPY/EUR/LKR display, and the exact volatility / not-financial-advice notice from the brief. It is a monitoring dashboard only: no trading, no wallet connection, no deposits, no buy/sell signals anywhere in the code | Source review of the new view, its view-switching registration (ZHENHUA_VIEWS) and mutual-close behaviour with the Jobs/Fashion/AI views; build audit at desktop + phone widths | PASS | Live data behaviour on the production origin: NOT TESTED in this page build — first live check happens in production use (endpoints were verified from the build environment, see data row below) |
| Crypto data — no fake prices (7 Nov 2026) | Every figure had to come from a real keyless public source, with honest failure states (High) | Watchlist, statistics, gainers/losers and coverage counts come only from the CoinGecko free public API (no key exists and none is embedded): /coins/markets pages of 50 (top 250 by market cap, clearly labelled as a monitored selection — never claimed to be every coin), /search for catalogue search, /global for totals. Responses are cached in memory for at least 60 seconds to respect the free rate limit; HTTP 429 and network failures render an explicit “unavailable / rate-limited” state with a Retry button — no placeholder prices exist anywhere. Endpoints verified live from the build environment (HTTP 200, CORS open) before wiring. “Data: CoinGecko · Updated <time>” is shown on the section, and the data is labelled delayed, never “real-time” | Endpoint checks (CoinGecko markets/search/global) + source review of the fetch/cache/error paths | PASS | If CoinGecko changes its free terms, the section degrades to the honest unavailable state rather than inventing data; a future paid key would be added server-side, never in this page |
| Crypto charts — TradingView (7 Nov 2026) | Official widgets only, branding preserved, coin selection must drive the chart (Medium) | Advanced Chart, Ticker Tape, Crypto Coins Heatmap and Cryptocurrency Market (screener) widgets load lazily — only when the Crypto Market view is first opened — from TradingView's official embed CDN (s3.tradingview.com), dark theme, with TradingView attribution kept. Selecting a watchlist coin re-mounts the Advanced Chart on the matching pair (e.g. BINANCE:BTCUSDT; USDT itself maps to KRAKEN:USDTUSD); the chart's own symbol search stays enabled for pairs the mapping cannot cover, and the pair in use is printed above the chart. Widgets are never initialised while the view is closed, keeping Android performance intact | Widget script URLs verified (all HTTP 200) + source review of the lazy-mount and symbol-mapping logic | PASS | Widget rendering inside the production page: NOT TESTED in this build — the audit sandbox cannot guarantee third-party iframe rendering; verify once on the live site |
| Crypto currency display (7 Nov 2026) | USD / JPY / EUR / LKR display with honest conversion labelling (Medium) | CoinGecko quotes are USD. Display conversion uses keyless reference rates: Frankfurter (European Central Bank reference rates) for JPY and EUR, and the ExchangeRate-API open endpoint for LKR (the ECB does not publish an LKR rate — verified: Frankfurter returns no LKR). Whenever a non-USD currency is selected, the page labels prices as converted and names the rate source and rate date; the TradingView market widget is re-mounted in the same display currency. If an FX source fails, the affected currency simply stays unavailable rather than converting at an invented rate | Both FX endpoints verified live from the build environment (HTTP 200, CORS open; LKR present only in the ExchangeRate-API response) + source review | PASS | Reference rates are daily rates, not dealing rates — the section says converted prices are for orientation |
| Crypto owner controls (7 Nov 2026) | Owner-only market configuration without exposing any credentials (Medium) | An Owner Controls panel inside the Crypto Market view is rendered only when the signed-in email is the owner address (same gate as the Security Center / CEO HQ; it stays hidden for everyone else). It configures pinned assets, the default display currency and chart interval, the two data providers on/off, and which panels (ticker tape, heatmap, market widget) show. There are no API credentials in this system at all — both providers are keyless — so nothing secret can leak. Saving writes to this device's local storage immediately and also attempts the HQ Firestore store (hq_settings / crypto_market); the panel reports honestly which of the two succeeded | Source review of the gate (owner email match), the save paths and the status reporting | PASS | Firestore persistence: NOT TESTED — until the HQ rules (see the hq_settings row above) are deployed, saves land on-device only and the panel says so; signed-in owner flow to be re-tested after the rules deploy |
| Crypto section languages (7 Nov 2026) | New UI strings needed the site's language pattern (Low) | All Crypto Market strings are provided in English, Japanese and Sinhala, with per-string English fallback for the other 11 languages — the same precedent as the CEO Control Center. The existing 284-key main dictionary was not touched, so its 14-language parity is unchanged | Source review of the section string table and fallback function | PASS | — |
| Security headers — CSP additions for Crypto Market (7 Nov 2026) | The enforcing-CSP switch must not break the new section (Medium) | Add these exact origins to the recommended CSP in firebase.json BEFORE switching from Report-Only to enforcing — script-src: add https://s3.tradingview.com · frame-src: add https://www.tradingview.com · connect-src: add https://api.coingecko.com https://api.frankfurter.dev https://open.er-api.com · img-src: add https://coin-images.coingecko.com (coin logos served by the data provider). Nothing inside the page weakens the policy; the widgets and APIs above are the only new origins the section uses | Origin inventory taken from the section's actual script/API/image usage; header change itself cannot be applied or verified from inside this page | NOT TESTED | Owner/May: extend the firebase.json CSP with the origins above while still in Report-Only, confirm clean reports on the Crypto Market view, then switch to enforcing |
| Crypto Market side button & nav visibility (7 Nov 2026) | Owner reported the CRYPTO MARKET section was not visible to him on the site and asked for a normally-visible side button (Medium) | Added an always-visible vertical edge tab fixed to the left edge of the screen (obsidian black + royal gold, “📈 CRYPTO MARKET”, vertically centred, slim on phones) that opens the Crypto Market view, and a gold pill highlight on the existing CRYPTO MARKET nav item so the destination stands out in the desktop nav and in the wrapped mobile nav rows alike. The tab sits on the opposite edge from the AI Assistant button and chat panel (bottom-right) and clear of the What's New bell in the header, so it never overlaps them; it hides itself while the Crypto Market view is open, where the view's own Back button takes over. The tab carries the same data-open-crypto attribute as the nav item, so both entry points run through the single delegated open handler into openCrypto() — the lazy TradingView initialisation and the CoinGecko load fire exactly once (cmInit guard) from either path, with the honest loading / unavailable states unchanged. The tab label is localised EN/JA/SI with English fallback for the other 11 languages, following the section's established pattern. The Marketplace reveal fix (observer change, listings decoupling, scroll-margins) was not touched | Source review of the tab markup/CSS, the shared open handler and the applyI18n label hook; build audit at desktop + phone widths, including a regression check that Marketplace listings still render immediately | PASS | Live widget/data behaviour on the production origin remains as noted in the Crypto Market rows above — the open path itself is unchanged; only a second, always-visible entry point was added |
| ECOSYSTEM STAGE 1 — architecture audit & shared framework (7 Nov 2026) | Brief §1/§14: expand the EXISTING site into a global marketplace ecosystem in stages, reusing architecture, without rebuilding, deleting divisions, removing Crypto Market, breaking auth or duplicating nav/accounts (New) | Architecture reused (audit of record): single-file static page on Firebase Hosting; the Jobs/Fashion/Crypto SPA-view pattern (hidden <main> per view, ZHENHUA_VIEWS registry, mutual close, hash routes, pushState Back handling); Firebase Auth (Google + Email/Password) as the ONE account system — reused, not duplicated; Firestore with the isAdmin() owner gate; the modal/form system (native validation, composed email message, no fake success); the hq_enquiries capture pattern; the CEO Control Center module system; the EN/JA/SI + English-fallback string-table pattern (Crypto/HQ precedent) so the 284-key main dictionary and its 14-language parity are untouched. Stage 1 built: ONE reusable division framework — shared search / category chips / filter selects / listings grid / detail panel / application + inquiry forms, parameterised per division from config (categories, filters, brand, reference-ID prefix). Risks identified and designed around: no Cloud Functions and no Firebase Storage exist (uploads impossible until Blaze), no payment provider exists, Firestore rules deny unknown enquiry types until extended, and the four new views must mutually close with Jobs/Fashion/AI/Crypto views (openers that use pushState fire no hashchange, so the ecosystem script also closes on those opener clicks) | Source review of the framework, view registry and mutual-close paths; build audit at desktop + phone widths | PASS | Stages 2–5 (below) are separate later builds, sequenced exactly as the brief's §14 strategy |
| Ecosystem hub & routes (7 Nov 2026) | Four new divisions needed one discoverable home without duplicate navigation (New) | ONE new nav item — “Ecosystem” — opens the hub view (#ecosystem) presenting all six marketplace businesses: ZHENHUA Market (Live), ZHENHUA Crypto Market (Live), Homes / Tickets / Automotive / Gaming (Launching), with the shared-account explanation and the 7-role model. Hash routes follow the existing pattern: #ecosystem, #homes, #tickets, #automotive, #gaming — direct links and browser Back work like #jobs/#crypto. The four divisions also appear in Business Divisions, labelled “Launching — New Division” (the section's structure text still truthfully counts only the two ACTIVE divisions). No nav item, account system or division was duplicated; Crypto Market and its side tab are untouched | Source review of nav, hub and route registration; build audit navigation checks at desktop + phone widths | PASS | Production-origin route check happens in the publish pass + owner's phone check |
| ZHENHUA HOMES — Stage 1 shell (7 Nov 2026) | Brief §3: Japan property discovery division (New) | Landing page with brand + tagline “FIND YOUR HOME. CONNECT WITH OPPORTUNITY.”, purpose and target customers, 9 categories, working search + filter shell (prefecture, monthly rent, furnished, foreigners welcome — the full brief filter set, incl. room size/bedrooms/station distance/deposit/key money/guarantor/move-in, lands with the first listings in Stage 2), the exact listing-detail field set, the 4-step referral flow, partner application + property inquiry forms with generated reference IDs (ZH-HOME-YYYY-XXXXXX). VISIBLE legal framing: discovery & referral only — ZHENHUA is not a licensed real estate broker (no 宅建 licence claimed), does not negotiate contracts or collect brokerage fees; only licensed partners broker. Listings source ECO_LISTINGS.homes starts EMPTY: the page shows the truthful launching empty state and no property, price or availability is invented | Source review; empty-state and form-compose behaviour checked in the build audit | PASS | Stage 2 (separate build): homes_properties collection + partner listing submission/approval, full filter set, referral-status + commission recording under written agreements |
| ZHENHUA TICKETS — Stage 1 shell (7 Nov 2026) | Brief §4: events & ticketing marketplace (New) | Landing page with tagline “DISCOVER EVENTS. BOOK EXPERIENCES.”, 10 event categories, search + filter shell (country, city, ticket type), listing-detail field set, the five planned ticket categories (General Admission / VIP / Gold / Premium / Reserved), organizer application + event inquiry forms (ZH-TKT reference IDs). VISIBLE honesty: “Ticket sales are not open yet” — no payment provider is configured, so nothing can be bought; no resale anywhere. Digital tickets (unique ID + QR), QR check-in with duplicate-entry prevention, refunds and organizer sales dashboards are documented as the ticketing stage's architecture, NOT presented as working. Poster uploads marked NOT AVAILABLE YET (no Firebase Storage until Blaze). ECO_LISTINGS.tickets starts empty | Source review; empty-state and form behaviour checked in the build audit | PASS | Stage 4 (separate build, AFTER Stripe is configured by the owner and tested): tickets_events + tickets_issued collections, payment-state verification, QR issue + check-in. Do not publish purchasing as live before that |
| ZHENHUA AUTOMOTIVE — Stage 1 shell (7 Nov 2026) | Brief §5: global vehicle marketplace (New) | Landing page with tagline “JAPAN AUTOMOTIVE. GLOBAL OPPORTUNITIES.”, 9 vehicle categories, search + filter shell (brand, fuel, transmission — year/price/mileage/condition filters land with listings in Stage 3), listing-detail field set, Japan export discovery (destination country captured in the inquiry form; 4-step partner export process), dealer/seller application + vehicle inquiry forms (ZH-AUTO reference IDs). VISIBLE framing: inquiries only; ZHENHUA does not independently conduct regulated sales/brokerage/export; shipping figures are estimates, never quotations, and are given per inquiry — no automated shipping prices are invented or shown. ECO_LISTINGS.automotive starts empty | Source review; empty-state and form behaviour checked in the build audit | PASS | Stage 3 (separate build): automotive_vehicles collection, verified seller listings, partner exporter directory once real partners are approved |
| ZHENHUA GAMING — Stage 1 shell (7 Nov 2026) | Brief §6: global gaming platform (New) | Landing page with tagline “PLAY. CONNECT. COMPETE.”, platform categories (PC / Android / iOS / Console / Free-to-Play / New Releases / Gaming Gear / Tournaments), search + filter shell, listing/tournament detail field sets, and all six sections as framework blocks: Game Discovery (official store links only — no hosted game files, ever), Gaming News, Community (moderated, with reporting), Esports Tournaments (BOTH systems: Community Tournaments by approved organizers + Official ZHENHUA Tournaments; no entry fees and no prize pools until legal requirements, publisher permissions and payments are verified), Gaming Marketplace (approved sellers), and ZHENHUA Game Studio as a CLEARLY-LABELLED future placeholder — no game is shown as released. Organizer/seller application + gaming inquiry forms (ZH-GAME reference IDs). ECO_LISTINGS.gaming starts empty | Source review; empty-state and form behaviour checked in the build audit | PASS | Stage 5 (separate build): gaming_games + gaming_tournaments collections, community wiring to the existing members system, organizer dashboard |
| Ecosystem enquiry types & Firestore rules — TO DEPLOY (7 Nov 2026) | Division applications/inquiries must reach the owner and be countable, using the site's one capture collection (High) | Forms compose an email exactly like the existing flows AND attempt the hq_enquiries save with these EXACT new types: homes_partner_application, homes_inquiry, tickets_organizer_application, tickets_inquiry, automotive_seller_application, automotive_inquiry, gaming_organizer_application, gaming_inquiry. Document shape is identical to the existing types — exactly the keys {type, name, contact, summary, uid, email, status, createdAt}, name ≤ 120, contact ≤ 120, summary ≤ 600 (the page slices to those caps), status “new”, plus the generated reference ID inside the summary text. Rule May must deploy: extend the hq_enquiries create rule's type whitelist with the 8 types above (same signed-in + exact-keys + size-cap conditions; read/update/delete stay isAdmin()-only). Until that deploy, Firestore's deny-by-default blocks these saves SILENTLY BY DESIGN and the email carries every submission — the same behaviour the original four types had before their rule landed. Privacy Policy §2 (EN/JA/SI) now names these flows | Source review of the capture code against the existing saveEnquiry shape and caps | NOT TESTED — pending rules extension | May: add the 8 types to the hq_enquiries create whitelist in firestore.rules, deploy, then submit one test application per division signed-in and confirm it lands in the CEO applications queue |
| Ecosystem role model & data structures — Stages 2–5 (7 Nov 2026) | Brief §7/§8: one account, seven roles, separate data models per division (High) | Roles (enforced by Firestore rules, never by the frontend; nobody can self-grant): customer (default for any signed-in user — browse, favourites, inquiries, event registration, community), seller, property_partner, event_organizer, gaming_organizer (each granted ONLY by an owner-approved application), admin (assigned division moderation), founder/super admin (the owner's isAdmin() identity). Rule shape May deploys per role: a single owner-writable collection eco_roles {uid → role, division, approvedBy, approvedAt} with allow read: if request.auth.uid == uid || isAdmin(); allow write: if isAdmin(); — role checks in other collections read this doc server-side, so no client-writable field can elevate a user. Collections per division (separate, never one generic collection): homes_properties {partnerUid, category, rent, deposit, keyMoney, fees, prefecture, city, stationMinutes, floorPlan, availableFrom, status: draft/pending/approved/rejected, createdAt} — public read only if status == “approved”, create only by property_partner role holders, update own drafts, approve isAdmin-only · tickets_events {organizerUid, category, venue, city, country, startsAt, ticketTypes[{name, price, qty}], salesOpen/Close, status: pending/approved/rejected} + tickets_issued {eventId, buyerUid, ticketType, paymentStatus, qrId, usedAt} — created ONLY after verified payment (server-verified in the ticketing stage; no client create), check-in update admin/organizer-of-event only, usedAt write-once prevents duplicate entry · automotive_vehicles {sellerUid, category, make, model, year, mileage, fuel, transmission, price, location, status} — same approval pattern as properties · gaming_games {title, platforms, storeLinks (official only), status} + gaming_tournaments {organizerUid, kind: community/official, game, registration window, rules, limit, schedule, results, status} — official-kind create isAdmin-only, results writable only by the owning organizer or admin · eco_favourites {uid, division, listingId} — owner-of-record read/write only. Stage 1 creates NONE of these collections; they are specified here so later stages deploy rules before UI | Data model and rule shapes reviewed against the brief and the deployed rules' existing patterns (isAdmin, field whitelists, uid ownership, default-deny) | NOT TESTED — specified, not deployed | Deploy each collection's rules WITH its stage build (Stages 2–5), never before the UI that needs it is tested |
| CEO Control Center — ecosystem modules (7 Nov 2026) | Brief §10/§9: divisions integrated into the CEO Control Center with honest figures (New) | Six modules added to the existing Control Center (same owner gate): Homes Management, Tickets Management, Automotive Management, Gaming Management — each showing real stored application/inquiry counts from hq_enquiries, approved-listings = 0 (true in Stage 1), the division's legal frame and its next-stage collection — plus a combined Partner & Organizer Applications queue (all four application types, real records only) and an Ecosystem Revenue panel marked NOT CONFIGURED: verified ecosystem revenue ¥0, the brief's per-division revenue sources listed as potential only, the rule that commission requires an approved written agreement AND a verified transaction/referral, and company/partner/organizer funds kept separate. The Customers module's type map now includes the 8 ecosystem types. No metric, listing or revenue figure is invented anywhere — with no records, every module shows zero/empty states | Source review of the six renderers against the loaded-data-only pattern of the existing modules; gate unchanged (owner email + isAdmin rules) | PASS | Live data in the modules: NOT TESTED until the hq_enquiries rule extension above is deployed and real applications arrive |
| Ecosystem languages (7 Nov 2026) | Brief §12: reuse the existing language system (Low) | All hub + division strings (navigation, taglines, legal frames, categories, filters, forms, empty states) are provided in English, Japanese and Sinhala in the ecosystem string table, following the Crypto/HQ precedent; the other 11 languages fall back per-string to English for the NEW sections only. The existing 284-key main dictionary was not touched, so its 14-language parity is unchanged | Source review of the string table (every key present in en/ja/si) and the fallback function | PASS | Native-speaker review of the new JA/SI division copy recommended |
| Payments, uploads & external keys — ecosystem (7 Nov 2026) | Brief §13/§16: state plainly what Stage 1 does NOT have (Info) | Requires payment-provider configuration: ALL ticket purchasing, QR ticket issue/check-in, commissions, featured-listing payments and payouts — Stripe awaits the OWNER's own signup/KYC; nothing payment-shaped is presented as working. Requires the Blaze upgrade + Firebase Storage: listing photos, event posters, vehicle images — every upload-dependent feature is labelled NOT AVAILABLE YET and no fake upload control exists. Requires partner agreements: Homes referral fees, Automotive exporter directory, featured placements. Requires legal authorisation: real-estate brokerage (partners' 宅建 licences), regulated vehicle sales/export (partners' licences), ticket resale (not offered), tournament entry fees/prize pools (publisher permissions + Japanese prize-competition law). Requires external API keys: none in Stage 1 — no new external origin is introduced, so the CSP recommended set needs NO additions for this stage | Configuration review of the whole stack against the build | NOT CONFIGURED | Owner: Stripe signup + Blaze upgrade unlock Stages 3–4 features; May deploys rules per stage as specified above |
| Ecosystem regression & mobile (7 Nov 2026) | Brief §15: existing production routes must not break (High) | Regression scope checked in source + build audit: Homepage, About, Business Divisions (new launching block added — nothing removed), AI Products, SENSEI Pro links, Crypto Market incl. side tab + #crypto route, Global Marketplace incl. the reveal fix (untouched), Fashion/AURELUNE, Creative Services, Global Support, Jobs board, Contact, CEO HQ, Security Center, Privacy, AI Assistant, push/What's New (ONE new entry added, EN/JA/SI, announcing the ecosystem), login model. Ecosystem views mutually close with Jobs/Fashion/AI/Crypto views in both directions. Mobile: division toolbars, chips, filter grids, category grids, hub grid and forms all reflow to a single column; no sideways scroll introduced | Build audit at desktop + phone widths; source review of every touched integration point | PASS | Production-origin verification (live data, signed-in flows) happens in May's publish pass + the owner's phone check, as with every round |
| Showcase slideshows — six sliders (7 Nov 2026) | Owner instruction (7 Nov 2026): add slides to every Ecosystem page and the Market so visitors can SEE each division (New) | ONE shared slideshow component (obsidian/gold, crossfade, ~5s auto-advance, diamond dots, prev/next arrows, touch swipe, pause on hover and on touch-hold, autoplay OFF under prefers-reduced-motion, hidden slides removed from tab order) placed at the top of SIX views: Ecosystem hub, ZHENHUA HOMES, ZHENHUA TICKETS, ZHENHUA AUTOMOTIVE, ZHENHUA GAMING and the Market section. Each division slider has 3 slides: (1) the owner-commissioned atmospheric showcase photo for that division (bundled locally as assets/slide-homes.jpg / slide-tickets.jpg / slide-automotive.jpg / slide-gaming.jpg — captioned as the division's WORLD, never as a property/event/vehicle/game for sale), (2) a branded title slide (dragon-wolf crest, the division's real name and its exact existing tagline string), (3) a categories + CTA slide whose category chips render from the SAME CATS data as the page itself and whose two buttons scroll to — and focus — the division's OWN existing application and inquiry forms (same forms, same submit path, nothing duplicated). The hub slider uses the site's existing Kyoto night hero image, the group brand slide (FROM JAPAN TO THE WORLD / BUILD BUSINESSES. CREATE OPPORTUNITIES. CONNECT THE WORLD.) and a slide listing all six businesses with their real Live/Launching status. Sliders lazy-initialise: ecosystem sliders only when their view first opens (openEco hook, like the Crypto widgets), the Market slider on first scroll into view (IntersectionObserver). All divisions remain LAUNCHING with zero listings and their legal lines untouched; no prices appear anywhere except the Market slider's real listings. New strings (photo captions, hub brand/six-business lines, slider aria labels) added to the ecosystem string table in EN/JA/SI; the other 11 languages fall back to English exactly as the division pages already do | Source review of the shared engine, all six slider markups and the lazy-init hooks; build audit at desktop + phone widths (slides render, no sideways overflow); duplicate-ID scan of the new markup (no new element IDs introduced); inline-script parse check | PASS | Touch-swipe feel and auto-advance timing on a physical phone: NOT TESTED — covered by the owner's phone check after publish, as with every round |
| Market slideshow — real listings only (7 Nov 2026) | Market slider must show the real listings exactly as listed — no invented items or prices (High) | The Market slider's three slides are the three REAL Kandyan listings with their own photos (assets/item-kandyan.jpg / item-kandyan2.jpg / item-osari.jpg), names and prices copied exactly from MARKET_ITEMS: “Kandyan Bridal Saree — Cream” ¥60,000, “Kandyan Bridal Saree — Gold” ¥51,000, “Kandyan Osari” ¥42,000. Each slide's button finds that item's own rendered card in the listings grid by its exact name, scrolls to it and flashes a gold outline — the Buy / Quick View actions stay on the card itself, unchanged. Sample items are NOT in the slider | Source comparison of slide captions against the MARKET_ITEMS entries (name, price, photo) and of the card-matching logic against the grid renderer | PASS | If a Kandyan item is ever renamed or repriced in MARKET_ITEMS, its slide caption must be updated in the same edit — the two are deliberately separate copies so the slider can never silently invent a price |
| Slideshow languages & regression (7 Nov 2026) | Slide text must follow the site's language system; nothing existing may break (High) | Slide captions, taglines, category chips and CTA labels reuse the ecosystem string table via the existing data-eco mechanism, so EN/JA/SI switch live with the page and slider arrow/dot aria-labels are re-localised on language change; brand names and the group slogan stay in their official English form in every language, as elsewhere on the site. Regression scope: all forms, the HQ enquiry capture, legal framing, LAUNCHING states, view routing and mutual close are untouched — the only existing-code changes are one renderCats hook (fills the slide-3 chips from the same data), one openEco line (lazy slider init) and the new CSS/JS blocks | Source review of every touched integration point; JA/SI spot-check of the new string keys in all three tables (every key present in en/ja/si); build audit navigation checks | PASS | Native-speaker review of the new JA/SI slide captions recommended, as with the Stage 1 division copy |
| TradingView trade view stopped working — fix (8 Nov 2026) | Owner reported the Crypto Market trade view (TradingView chart) had stopped working (High) | Root cause found in TradingView's own current embed script (s3.tradingview.com, Last-Modified 6 Nov 2026): its widgets now build their iframes on https://www.tradingview-widget.com, which the production enforcing CSP does not list in frame-src (only https://www.tradingview.com is listed — verified live in the zhenhuagroup.web.app response headers on 8 Nov 2026), and the scripts' built-in CSP fallback host (s.tradingview.com) is not listed either, so every JS-embed widget rendered as a silent blank. Fix inside the page: (1) the main Advanced Chart no longer uses the JS embed — updateChart() now mounts a direct iframe to https://www.tradingview.com/widgetembed/ (HTTP 200, no frame-ancestors block, verified 8 Nov 2026) with the selected pair, the owner's default interval, Asia/Tokyo, dark theme, symbol search, date ranges and side toolbar — the one TradingView host the CSP already allows; (2) the ticker tape, heatmap and screener JS embeds get a 12-second load watchdog (mountTV onFail): if no widget iframe appears, the tape hides and the panels show an honest blocked message (EN/JA/SI) with an “Open on TradingView” link instead of a blank box. CoinGecko data, watchlist, settings and owner controls untouched | Live checks from the build environment: TradingView embed script source read (widgetHost = www.tradingview-widget.com + its CSP-fallback code), production CSP headers read, widgetembed URL checked (200); source review of the new updateChart/mountTV code; build audit at desktop + phone widths with the Crypto Market view opened by probe | PASS | Owner/May (production hardening, outside this page): also add https://www.tradingview-widget.com and https://s.tradingview.com to frame-src in firebase.json so the remaining JS-embed widgets (tape, heatmap, screener) render natively on the production origin too; until then they degrade to the honest blocked state there, while the main chart works via widgetembed |
最新情報 Latest Updates
CEO Control Center — a private headquarters for the owner inside the account menu: twelve modules (Executive Overview, Divisions, Finance, HR, Sales & Marketplace, Customers, Partners, Approvals, Reports, Security, Strategy, Settings). Finance starts honestly empty (¥0 recorded), all seven department-manager posts show VACANT, and enquiries now also save an owner-only record so real demand can be counted. HQ database rules are written in the QA report and pending deployment — until then the Control Center labels its data state instead of inventing numbers
Security & cyber-defense upgrade — a full in-page security audit (secrets scan, rendering and form-validation hardening), an owner-only Security Center with evidence-based statuses plus incident-response and backup plans, and a recommended security-header set documented in the QA report for the hosting configuration
Privacy & Security upgrade — Privacy Policy rewritten in English, Japanese and Sinhala to match exactly what the site does; new “Privacy & My Data” dashboard (download your data, delete your account); anonymous analytics is now your choice in “Privacy choices”
Website production upgrade — one corporate structure, full navigation, jobs search & filters, Privacy / Terms pages and this QA report
First real Market listings live — the Kandyan bridal collection (¥42,000–¥60,000) — and the Part Time Jobs page launched with the verified baito board
SENSEI Pro gets a real 3D Japan Map and Ask Sensei lessons
Ask about ZHENHUA GROUP — the company and its divisions, SENSEI Pro, part-time jobs, ZHENHUA Market, Global Support, AURELUNE ATELIER and DELA ON THE BEAT. It replies in your language.
The AI assistant is busy or unavailable right now.
Please message us directly instead — we reply personally:
Privacy: your messages are sent to our AI service, which uses Google Gemini, just to generate the reply. The chat stays in this tab only and is never stored by this site. The AI runs on a free tier, and on free tiers Google may use prompts to improve its products — please don't share personal details here. Full details: Privacy Policy.