Trust
Your records. Kept for you, and it says so on every screen.
Trust in Daiko is built into how the record works, not added as a setting. This page says what is true today, and marks plainly what is still under review.
Records kept by Daiko for Veridan Facility Services
- 01On every screen
At the foot of every screen, in the screen's language. No tier, setting or override removes it.
- 02On every document
Every page of a report, a printed badge sheet, the back of a visitor's wallet pass.
- 03Named from the record
The customer, never a vendor or occupier working inside the account. The link opens a page in nine languages saying where to ask.
Append-only
Nothing is edited in place. Ever.
Every action is an entry with who, when and why. A correction is a new entry that points at the old one, so the history stays whole. The database itself refuses a rewrite.
The same holds for prices, contracts and the law: a rate, a measure or a regulation at a date is versioned, never edited, so last year's report reads the same today.
- 06:11Raised from a sensor readingEdge gateway T4-B1, point CH2 suction pressure
- 06:41Priority P2 and Sunil Patil proposedDispatch agent, citing 3 records, model and version kept
- 06:43Proposal acceptedRekha Kulkarni, site manager
- 07:58Completed with 2 photos, cause: worn out with ageSunil Patil, on the phone offline; sent 08:20
- 08:35Cause corrected to: a part failedRekha Kulkarni. Reason: valve seal found split. Points at the 07:58 entry, which stays.
The AI and your records
The AI reads what you may read, and nothing it does is off the record.
Agents work inside the same rules as your people. They propose; a person decides anything with money, safety, the law or a contract in it. How autonomy is earned
The Assistant reads only through the routes the person asking could open, so it cannot tell anyone what they could not see themselves.
A sentence that cites no record, or cites one the agent did not read, is dropped and counted.
Inputs, tools, model and version, and the reason for each action are kept, so any run can be rebuilt from the record alone.
A cost, safety, legal or contractual consequence stops at a draft, however the agent is set up.
Autonomy is signed for by a named person after 200 decisions over 30 days at 95 per cent agreement, sampled one in twenty, and lost on one overruled action that mattered.
With the model off, unsure or slow, rules route the work and say why. Life-safety work always goes to a person.
Data residency
Hosted in your region, and only there.
Each region is a whole deployment of its own: sign-in, records, evidence, agents and metering. An account from one region is not found in another. Where the AI models that agents call are run is listed with our subprocessors: [AI PROCESSING LOCATION].
Hosted in Mumbai. Indian customers' accounts, profiles, evidence and usage record are held in India.
A region of its own, with its own sign-in. Available from [AVAILABILITY DATE].
Further regions are opened as whole deployments, never as a copy of another region's data.
A person who works in two regions holds two accounts. Their certificates still travel with them, because they present them rather than us looking them up.
The person comes first
You can see where you are known. Nobody else can join the dots.
One sign-in, many employers. Each employer keeps its own profile of you, and those profiles are never joined across customers. The link between them is visible to one person: you.
Profiles from two employers share no key. A person's record cannot be stitched together, by us or anyone.
Nothing confirms whether an email or phone already has an account. Every invitation gets the same answer.
Certificates are signed by their issuer and held by the person, so they travel without a lookup.
A domestic help's police verification is shown to a new household only when the worker agrees.
Your company signs in with Microsoft. Use the button below.
Continue with Microsoft Continue with GoogleSign-in
No passwords to leak. Your IT decides who is in.
- 01A one-time code
By email, or by text message or WhatsApp to a phone. It works once, for ten minutes.
- 02Google or Microsoft
For anyone whose address the provider proves. An invitation is taken up on the way in.
- 03Your own domain
Connect your Google Workspace or Microsoft Entra ID, and your domain signs in only through it. When IT disables a leaver, they are out of Daiko too.
- 04Our operators
Our staff sign in apart from every customer's people. They act on your account as themselves, on the record, and every look is logged.
Consent and privacy
Asked once, recorded exactly, never rewritten.
Consent text, purposes and retention periods are versioned data. Each consent records the exact wording and basis in force when it was given.
A camera kiosk photographs a visitor only with their consent, for security to compare.
Identity is sighted, not copied. No Aadhaar number is captured anywhere in the product.
A detection may keep one unblurred still, readable only by security heads, kept 30 days. Video never leaves the site.
A household's visitors and workers are visible to that household, and to a guard only for the entry in hand.
A walk-in queue counts tokens. It never records who stood in it.
When you ask this website for a demo
The Book a demo form keeps your name, work email, company, role, what you run, how many sites, your country, the note you add if any, which edition (India or United States) you read the site in, and when you sent it. To stop one sender flooding the form, it also keeps a one-way fingerprint of your network address for a day, never the address itself. Nothing else about you is kept: no cookies, no trackers, no analytics, and no fonts or scripts from anyone else. The site remembers your choice of edition and of motion in your own browser only.
We use it only to arrange your demo and follow it up. It is sent to Daiko's sales inbox by email and kept in Daiko's own database. It is never sent to a third party. It is deleted 180 days after you send it. To have it deleted sooner, write to [PRIVACY CONTACT EMAIL].
Our privacy notice and data processing terms are under review and will be published here. Until then, the product says who keeps the records and for whom, and does not describe who is responsible in law. [PRIVACY NOTICE] [DATA PROCESSING AGREEMENT]
Security practices
What we can show you, and what is still to come.
- Certification
- [CERTIFICATION]
- Independent penetration test
- [PEN TEST DATE]
- Subprocessors
- [SUBPROCESSOR LIST]
- Report a vulnerability
- [SECURITY CONTACT]
A code or invitation waits with its address sealed. The outbox holds no address in the clear.
Sign-in and recovery answer the same way whether or not an address is known, so it cannot be probed.
A logo is checked by its first bytes, not its name. SVG is never accepted, since it can carry script.
Passes and grants that outlast a visit are put to their owners for review; what nobody answers is suspended.
An agent proposes. Any command to a building system is issued by a person, under an attested policy.
Production checks its own configuration and will not start with a setting that is unsafe.
Bring your security team to the demo.
They can ask about any line on this page, and we will show it working in the product rather than on a slide.