Trust
Your records, and every agent’s reasoning, on the record.
An AI you cannot audit is an AI your security team will not sign off. In Daiko, every agent proposal, every person’s decision and every correction is an entry nobody can rewrite, and every screen says whose records they are. This page says what is true today, and marks plainly what is still under review.
Records kept by Daiko for Solvane 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 tenant 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 LKP-N-B1, point CH2 suction pressure
- 06:41Priority P2 and Tessa Brooks proposedDispatch agent, citing 3 records
- 06:43Proposal acceptedRafael Mendoza, chief engineer
- 07:58Completed with 2 photos, cause: worn out with ageTessa Brooks, on the phone offline; sent 08:20
- 08:35Cause corrected to: a part failedRafael Mendoza. Reason: valve seal found split. Points at the 07:58 entry, which stays.
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. US customers are hosted in the United States region, and their records, evidence and usage record stay there. When an agent calls a model, what it sends is processed by our AI provider: [AI PROCESSING LOCATION].
A region of its own, with its own sign-in, holding US customers' accounts, profiles, evidence and usage record in the United States. Available from [AVAILABILITY DATE].
Hosted in Mumbai, for Indian customers. Nothing of a US customer is held there.
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 household worker's verification, checked once by the property's office, is shown to another 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 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.
Each site chooses how a walk-in's identity is settled: the desk looks at the ID, the host vouches, or a camera kiosk takes it with consent. The front desk's own records keep no ID number and no image.
A detection may keep one unblurred still, readable only by security managers, kept 30 days. Video never leaves the site.
A household's visitors and workers are visible to that household, and to the front desk 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 of the site you read, the United States or India, 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]
The agents
Every agent reads what its user may read, and nothing more.
An agent is not a back door. The Assistant reads through the same permissions as the person asking, so it cannot tell a tenant what only the provider may see. Every proposal, act and answer is an entry on the record with what it read, and a person can overturn any of it.
How an agent earns autonomy, and loses itEvery sentence the Assistant writes points at the record it came from. If it cannot cite it, it does not say it.
An agent starts by proposing. Acting on its own needs a track record and a named person's signature, and one consequential override sends it back to proposing.
A person confirms one act in twenty that an agent took on its own.
Each agent uses the cheapest model that passes its test set, approved by a named person. A model that misses a life-safety case does not qualify.
A fire alarm, a gas smell or a blocked exit is never left to a model's judgment, and no cap ever pauses it.
Camera detectors run on a box at the site. What leaves is the detection, never the footage.
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, including what each agent may read, and we will show it working in the product rather than on a slide.