Staymulate — AI Disclosure
Version 1.0 first draft. Status: AWAITING LAWYER REVIEW.
Per s42 panel finding 7/11: "identifies as AI if asked" is insufficient. Disclosure must be PROACTIVE on first contact.
Plain-language summary
Some replies you receive on Staymulate are written or assisted by AI (artificial intelligence). Specifically:
| What | Who decides | Whether the human reviews before sending |
|---|---|---|
| Transcription of your voice message | Whisper (open-source AI) | No — direct transcription |
| Categorisation of photos you send (bill, food, damage, room) | Gemini (Google AI) | No — automated routing |
| Extraction of structured fields from a bill photo (vendor, amount, date) | Gemini | Yes — owner reviews before saving |
| Generation of social media captions for your property | Gemini | Yes — owner approves before posting |
| Generation of suggested replies to guest reviews | Gemini | Yes — owner approves before posting |
| Synthesis of your property's narrative voice from interview answers | Gemini | Yes — owner approves the DNA before it goes live |
| Routing of your message to the correct topic (maintenance, finance, purchase, emergency) | Phi-3 (open-source AI) running locally | No — automated |
| Drafting a panel review of a feature design | Gemini (11 expert agents) | Yes — Harpreet reads the consolidated review |
| Setting prices on your behalf | Not yet built — when shipped, will require owner approval | n/a |
When the disclosure is shown
The disclosure must be presented at these moments:
- First interaction with the Staymulate staff bot — when a staff member sends their very first message, the welcome reply must include a one-line AI disclosure: "Some replies you receive here are written by AI. You can ask me 'are you a bot?' at any time and I will tell you the truth."
- First interaction with the Staymulate guest bot — when a guest sends their first message (typically the welcome flow), the welcome reply must include the same one-line disclosure.
- First interaction with the owner-facing webapp — the onboarding wizard must include a checkbox: "I understand that Staymulate uses AI to process my property data, and that I am a joint controller for AI-derived inferences. I have read the AI Disclosure: [link]." This box is not pre-ticked.
- Every automated message that Staymulate sends without owner review — must include the footer: "Sent by Staymulate AI on behalf of [Property Name]. Reply STOP to opt out." (Not just "AI" alone — the line must name Staymulate as the originator.)
- Every owner-approved message that was AI-drafted but human-approved — must include a less prominent indicator: "Drafted with AI assistance, approved by [Property Owner Name]."
- The Privacy Policy + Data Processing Agreement — both must reference this disclosure document.
"Are you a bot?" — the verification answer
Per Foundation Brief Section 5: "Every agent identifies itself as AI if directly asked — non-negotiable."
When a user sends any message that includes any of the following (case-insensitive substring match):
- "are you a bot"
- "are you ai"
- "are you human"
- "are you a real person"
- "is this a robot"
- "kya tum bot ho" (Hindi)
- equivalents in other supported languages
The reply MUST be: "Yes, I am Staymulate's AI assistant. I help with [scope]. The owner of this property is [name] and they review or approve any decision that affects you. You can ask to speak directly with the owner at any time by replying OWNER."
This reply is non-overridable. No prompt engineering, no test mode, no business logic can suppress it.
---
What this disclosure does NOT do
This disclosure does not:
- Replace the owner's responsibility for the content of AI-generated messages sent in their name. The owner is the controller for the property's reputation.
- Replace the requirement for explicit consent before AI processing of sensitive personal data (health, biometric, etc).
- Cover AI features that are not yet built — when a new AI feature is added, this document must be updated in the same commit.
---
Source AI vendors
For full transparency, the AI components that touch user data:
| Component | Vendor | Hosted where | What it sees |
|---|---|---|---|
| Whisper transcription | Open-source (run locally on Staymulate infrastructure) | India (currently dev) | Voice messages from staff, owners, guests |
| Gemini API (1.5 Flash thinking) | Multi-region | Photos, structured field extraction, content generation, panel reviews | |
| Phi-3 Mini intent classification | Microsoft (run locally via Ollama) | India (currently dev) | Text snippets for routing |
| Anthropic Claude | Anthropic | US | Used for build sessions only — never receives live property data per Foundation Brief D-31 |
Cross-border data transfer to Google for Gemini API calls is the most material risk and is addressed in the per-market addenda (especially Indonesia UU PDP and Canada provincial laws).
---
Where this document is linked from
disclaimer.md(the one-page summary references this for the AI disclosure detail)terms_of_service.md§3 "AI use disclosure"privacy_policy.md§5 "Automated decision-making"data_processing_agreement.md§4 "Joint controller activities"- The onboarding webapp consent screen
- The staff bot welcome message
- The guest bot welcome message
- The footer of every automated message Staymulate sends without owner review
---
Version 1.0, awaiting lawyer review.