{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/zeroclaw.json", "name": "ZeroClaw", "score": 70.2, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.accounts" ], "slug": "zeroclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nanoclaw.json", "name": "NanoClaw", "score": 68.3, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.accounts" ], "slug": "nanoclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/hermes-agent.json", "name": "Hermes Agent", "score": 67.9, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory" ], "slug": "hermes-agent" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/openclaw.json", "name": "OpenClaw", "score": 67.1, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory" ], "slug": "openclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/ironclaw.json", "name": "IronClaw", "score": 66.7, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory" ], "slug": "ironclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nanobot.json", "name": "nanobot", "score": 62.4, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.accounts" ], "slug": "nanobot" } ], "tool": { "slug": "haven", "name": "Haven", "vendor": "Hello Haven, Inc.", "vendorUrl": "https://my.hellohaven.ai", "kind": "platform", "category": "personal-assistants", "summary": "Hosted personal AI assistant from Hello Haven, Inc. that a person reaches by phone call, text message, email, web or mobile app. It keeps a memory of the user and carries out tasks for them. In beta.", "url": "https://www.anchorterminal.com/tools/haven", "markdownUrl": "https://www.anchorterminal.com/tools/haven.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/haven.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/haven.json", "license": "Proprietary service under Hello Haven's Terms of Service", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "A person signs up at my.hellohaven.ai/gethaven with an invite code and signs in at app.hellohaven.ai, or reaches Haven from their own phone number or email address. The sign-in method was not read, because the app is behind a sign-in. No API key, OAuth app or other developer credential was found. The terms say Haven connects with the user's email, calendar, cloud storage, messaging and other services, and the privacy policy says authentication credentials for connected services are shared with those providers. Provider names, scopes and where tokens are stored were not found (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy).", "pricing": "free", "pricingNotes": "Free during beta with full access and no card, per the plans page. The FAQ says there are no usage limits, that prices are not set, and that users will get notice before charges begin. The terms mention subscription billing through a payment processor but no price is published (https://my.hellohaven.ai/plans; https://my.hellohaven.ai/faq, checked 2026-10-12).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the site, the plans page or the terms, and no API to carry one (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://my.hellohaven.ai/faq", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory" ], "tags": [ "hosted", "closed-source", "beta", "free", "phone", "sms", "email", "voice", "ios", "android", "status-page" ], "lastRelease": "2026-09-17", "graded": true, "anchor": { "graded": true, "score": 22.2, "grade": "F", "agentReady": false, "rank": 977, "ranked": true, "rankOf": 986, "categoryRank": 19, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 6, "maintenance": 35, "payments": 30, "reliability": 35, "schema": 4, "security": 13, "transparency": 51 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 35, "points": 7, "reason": "Read with the hosted lines. Statuspage site at status.hellohaven.ai with eight components (20). In the 90 days to 12 October 2026 the feed has one incident, phone and app voice down on 15 August 2026 from a billing issue with a provider, with no duration given. Voice is one of six channels, so we read it between minor and major (15 of 30). The FAQ says there are no usage limits and no rate limit was found (0). No overload or retry guidance (0). No SLA, and the terms say there are no guarantees of delivery, accuracy or uninterrupted service (0). The service is in beta (0)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 4, "points": 0.65, "reason": "Haven has no API, MCP server or developer documentation on the pages read, so most lines score absent. No machine-readable contract (0). /llms.txt answered 404 (0). The FAQ and home page describe what the assistant does in general terms, with no account of which actions it takes or when (4 of 20). No typed inputs (0). No examples or error documentation, and the one help article we opened from the sitemap showed a not-found page (0). No versioning or changelog (0)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 6, "points": 0.98, "reason": "No programmatic surface, so the lines are read against what an agent or its owner can do through the channels. Nothing sizes or filters replies (0 of 25, 0 of 20). No error documentation (0). No retry or idempotency guidance for tasks such as orders or sent messages (0). An account needs no setup beyond a call, text or email, and recurring tasks are set in plain language per the press release, with no SDK (6 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 13, "points": 2.28, "reason": "The sign-in method was not read, and no scopes, token storage or revocation for connected accounts were found. The privacy policy says credentials for connected services are shared with those providers and that the vendor's own keys sit in server-side environment variables (5 of 30). No read-only mode or approval control is documented. Outbound email is labelled as sent on the user's behalf and impersonation is forbidden (3 of 20). Haven reads mail and web pages, and no prompt-injection guidance was found beyond the home page's words safety tested (0 of 15). Memory can be browsed in the app, but no log of actions taken was found (2 of 15). Encryption in transit and at rest is claimed. No security.txt, disclosure policy, bounty or certification was found (3 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 30, "points": 3.75, "reason": "No machine payment protocol (0). The price today is published without a login (free in beta), and future prices are not set, which we read as public plan-only pricing (10). Free with no card (20). A person has to sign up with an invite code or phone the number, so no autonomous onboarding (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 35, "points": 3.06, "reason": "The public launch was announced on 17 September 2026, 25 days before this check, and we count it as the last dated release (30). No changelog or release notes were found, so no three dated entries in 90 days (0). A support form, a community site linked from the status page (not read) and status incidents that were answered and closed, with no changelog (5 of 15). No SDK and no registry entry (0). No package to assess, and app store version histories were not read (0)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 51, "points": 4.46, "note": "editorial 37, provenance 64", "reason": "Closed source under short terms that name the entity and governing law (15). The privacy policy lists what is collected and categories of recipients, keeps data while the account is active, and the data page gives deletion from backups within 30 days. The home page says Haven is never trained on the user, which neither legal document repeats, and the FAQ's vetted providers are unnamed (14 of 30). The FAQ promises notice before charging starts, while the terms allow suspension or change at any time with no notice period (3 of 20). Sub-processors are listed by category with the full list on request, and no data location is stated (5 of 20)." } ], "assessment": { "date": "2026-10-12", "basis": "public evidence", "confidence": "low", "notes": { "ergonomics": "No programmatic surface, so the lines are read against what an agent or its owner can do through the channels. Nothing sizes or filters replies (0 of 25, 0 of 20). No error documentation (0). No retry or idempotency guidance for tasks such as orders or sent messages (0). An account needs no setup beyond a call, text or email, and recurring tasks are set in plain language per the press release, with no SDK (6 of 15).", "maintenance": "The public launch was announced on 17 September 2026, 25 days before this check, and we count it as the last dated release (30). No changelog or release notes were found, so no three dated entries in 90 days (0). A support form, a community site linked from the status page (not read) and status incidents that were answered and closed, with no changelog (5 of 15). No SDK and no registry entry (0). No package to assess, and app store version histories were not read (0).", "payments": "No machine payment protocol (0). The price today is published without a login (free in beta), and future prices are not set, which we read as public plan-only pricing (10). Free with no card (20). A person has to sign up with an invite code or phone the number, so no autonomous onboarding (0).", "reliability": "Read with the hosted lines. Statuspage site at status.hellohaven.ai with eight components (20). In the 90 days to 12 October 2026 the feed has one incident, phone and app voice down on 15 August 2026 from a billing issue with a provider, with no duration given. Voice is one of six channels, so we read it between minor and major (15 of 30). The FAQ says there are no usage limits and no rate limit was found (0). No overload or retry guidance (0). No SLA, and the terms say there are no guarantees of delivery, accuracy or uninterrupted service (0). The service is in beta (0).", "schema": "Haven has no API, MCP server or developer documentation on the pages read, so most lines score absent. No machine-readable contract (0). /llms.txt answered 404 (0). The FAQ and home page describe what the assistant does in general terms, with no account of which actions it takes or when (4 of 20). No typed inputs (0). No examples or error documentation, and the one help article we opened from the sitemap showed a not-found page (0). No versioning or changelog (0).", "security": "The sign-in method was not read, and no scopes, token storage or revocation for connected accounts were found. The privacy policy says credentials for connected services are shared with those providers and that the vendor's own keys sit in server-side environment variables (5 of 30). No read-only mode or approval control is documented. Outbound email is labelled as sent on the user's behalf and impersonation is forbidden (3 of 20). Haven reads mail and web pages, and no prompt-injection guidance was found beyond the home page's words safety tested (0 of 15). Memory can be browsed in the app, but no log of actions taken was found (2 of 15). Encryption in transit and at rest is claimed. No security.txt, disclosure policy, bounty or certification was found (3 of 20).", "transparency": "Closed source under short terms that name the entity and governing law (15). The privacy policy lists what is collected and categories of recipients, keeps data while the account is active, and the data page gives deletion from backups within 30 days. The home page says Haven is never trained on the user, which neither legal document repeats, and the FAQ's vetted providers are unnamed (14 of 30). The FAQ promises notice before charging starts, while the terms allow suspension or change at any time with no notice period (3 of 20). Sub-processors are listed by category with the full list on request, and no data location is stated (5 of 20)." }, "sources": [ { "what": "press release of 17 September 2026, cited only for what it announces", "url": "https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html", "seen": "2026-10-12" }, { "what": "home page (channels, models shown, proactive claim)", "url": "https://my.hellohaven.ai", "seen": "2026-10-12" }, { "what": "plans page (free in beta, no card)", "url": "https://my.hellohaven.ai/plans", "seen": "2026-10-12" }, { "what": "FAQ (beta, cost, data)", "url": "https://my.hellohaven.ai/faq", "seen": "2026-10-12" }, { "what": "data page (memory controls, export, deletion)", "url": "https://my.hellohaven.ai/your-data", "seen": "2026-10-12" }, { "what": "terms of service, last updated 24 July 2026", "url": "https://my.hellohaven.ai/terms", "seen": "2026-10-12" }, { "what": "privacy policy, last updated 24 July 2026", "url": "https://my.hellohaven.ai/privacy", "seen": "2026-10-12" }, { "what": "support page (contact form only)", "url": "https://my.hellohaven.ai/support", "seen": "2026-10-12" }, { "what": "sitemap", "url": "https://my.hellohaven.ai/sitemap.xml", "seen": "2026-10-12" }, { "what": "status page components", "url": "https://status.hellohaven.ai/", "seen": "2026-10-12" }, { "what": "status incident feed, four entries from 21 May to 15 August 2026", "url": "https://status.hellohaven.ai/history.atom", "seen": "2026-10-12" }, { "what": "domain registration (RDAP)", "url": "https://rdap.identitydigital.services/rdap/domain/hellohaven.ai", "seen": "2026-10-12" }, { "what": "GitHub organisation, no public repositories", "url": "https://github.com/hellohavenai", "seen": "2026-10-12" } ], "openQuestions": [ "Kind is `platform`. Haven is a hosted consumer app reached by phone, text, email, web and mobile, with no API or MCP server, so no other kind fits. Graded as a hosted service.", "The lead's only address was a press release. The release links my.hellohaven.ai/meethaven, and every fact here other than the announcement comes from that site, its status page, RDAP and GitHub.", "The lead said Haven performs tasks through connected services. The terms confirm connections by type only. The 500 models and 100 integrations are the press release's figures and were not confirmed on the site.", "my.hellohaven.ai is drawn by script. A plain request returned an empty page for /meethaven and /plans, while our page reader received full text for the other pages. Wording quoted from those pages passed through that reader's summary and should be checked against the pages before publishing. No script bundle was read.", "unchecked: the app at app.hellohaven.ai (sign-in method, approval settings, the list of connectable accounts and their scopes, memory controls as built). It is behind a sign-in and we sent it nothing.", "unchecked: the incident history page on status.hellohaven.ai (script-drawn). The linked Atom feed was read in its place. Uptime figures were not read.", "unchecked: community.hellohaven.ai, the App Store and Google Play pages (version history, data safety labels), and the /press, /company, /contact, /gethaven and other blog pages.", "unchecked: whether content is used to train models. The home page says never, and the terms and privacy policy were silent as our reader reported them.", "Maintenance counts the launch of 17 September 2026 as the last dated release. With no changelog, a strict reading that wants a release note would give 0 on that line and a total of 5.", "Reliability reads the 15 August 2026 voice outage as between minor and major because no duration is given. Read as a major outage the line is 10, not 15.", "Slip, disclosed. The RDAP lookup at rdap.org redirected to rdap.identitydigital.services before that host's robots.txt was read. The answer is used for the registration date only.", "The interface cannot be read without an account and three scores (schema, ergonomics, security) rest mostly on absence. Under the batch 8 rule this listing may belong in held/." ] }, "negative": 0, "verdict": "Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.", "bestFor": "A consumer assistant for one person who wants to phone, text or email it and have it remember them.", "strengths": [ "Free during beta with no card and no usage limits, per the plans page and FAQ (checked 12 October 2026).", "One assistant on phone call, SMS, email, voice, web and mobile app, with a published phone number and email address.", "Statuspage site with eight components, including Phone Calls, SMS Chat and Scheduled Tasks \u0026 Reminders, and four dated incidents since May 2026.", "The data page says memory can be viewed, edited, exported and wiped in the app, with deleted data leaving backups within 30 days.", "The privacy policy names Hello Haven, Inc. with a street address in Park City, Utah, and was last updated on 24 July 2026." ], "weaknesses": [ "No approval setting or list of actions that need confirmation was found on the public pages. The terms say it sends emails, SMS and calls following the user's instructions.", "Connected accounts are described only by type (email, calendar, cloud storage, messaging). No provider names, scopes or token storage statement were found.", "Model providers and sub-processors are listed by category only. The policy says the list is available on request by email.", "No API, MCP server, developer docs, changelog, security.txt or disclosure policy was found. The press release says a developer platform is planned.", "Two voice outages (23 May and 15 August 2026) were caused by billing errors with a provider, per the status page.", "The terms allow the vendor to suspend, modify or terminate the service at any time, and say continued use accepts updated terms." ], "agentNotes": [ "Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).", "Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.", "Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.", "Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.", "Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 22.2 } ], "editorialScores": { "ergonomics": 6, "maintenance": 35, "payments": 30, "reliability": 35, "schema": 4, "security": 13, "transparency": 37 }, "provenanceScore": 64 }, "connect": {}, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/haven" }, "notable": [ "Hello Haven's press release of 17 September 2026 announces the public launch, a $15 million pre-seed round led by Mayfield, and a private beta opened the month before (https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html)", "The same release says Haven draws on more than 500 AI models and more than 100 app integrations. The site read today names no integration and no list of them was found (https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html)", "The release says a developer platform and a sign in with Haven feature are planned. Neither is available on the pages read (https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html)", "The status page records voice outages on 21 May, 23 May, 22 June and 15 August 2026. The 23 May and 15 August entries give a billing error with a provider as the cause (https://status.hellohaven.ai/history.atom)", "The home page says Haven is never trained on the user. The terms and privacy policy read today say nothing about training, and say content is sent to third-party AI model providers (https://my.hellohaven.ai; https://my.hellohaven.ai/terms)", "The terms and privacy policy both carry an effective date of 10 March 2025 and a last update of 24 July 2026 (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy)", "A GitHub organisation named Hello Haven AI links to my.hellohaven.ai and has no public repositories (https://github.com/hellohavenai)", "No security.txt and no llms.txt. Both paths on my.hellohaven.ai answered 404 on 12 October 2026" ], "area": "frameworks", "details": [ { "label": "Status", "value": "Beta. Public launch announced on 17 September 2026. The FAQ says this version is not always foolproof (https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html; https://my.hellohaven.ai/faq)" }, { "label": "Channels", "value": "Phone call and SMS on +1 (435) 412-3585, email to chat@hellohaven.ai (it can be copied on a thread), voice, the web app at app.hellohaven.ai, and iOS and Android apps (https://my.hellohaven.ai; https://my.hellohaven.ai/faq)" }, { "label": "Acts without asking", "value": "The home page describes proactive outreach before the user asks, and the status page has a Scheduled Tasks \u0026 Reminders component. The terms say Haven sends emails, SMS and phone calls on the user's behalf, following their instructions. The FAQ says it can shop, order food, book and cancel. No approval setting and no list of actions that need confirmation was found (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/faq)" }, { "label": "Accounts", "value": "Email, calendar, cloud storage, messaging and other services, by type only. No provider is named, and no scope or token storage statement was found. The privacy policy says the vendor's own keys for third-party services are held as server-side environment variables (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy)" }, { "label": "Memory", "value": "Persistent memory of people, preferences and facts, browsable under Memory in the app. A single memory can be corrected or forgotten, a topic cleared, the whole memory wiped or the account closed. Export in a machine-readable format. Deleted data leaves active systems at once and backups within 30 days, per the data page (https://my.hellohaven.ai/your-data)" }, { "label": "Where it runs", "value": "Hello Haven's servers. Hosting provider and data location are not stated. Chat messages, history, profile context and uploaded files go to third-party AI model providers, with speech, vector storage and communication services also listed by category. The home page shows GPT, Claude, Gemini and Llama among the models it routes to (https://my.hellohaven.ai/terms; https://my.hellohaven.ai)" }, { "label": "Outbound identity", "value": "Emails to other people name Hello Haven as the sender and note they were sent on the user's behalf. The terms forbid asking Haven to write or call as someone else (https://my.hellohaven.ai/terms)" }, { "label": "Cost", "value": "Free in beta, no card. Carrier message and data rates may apply. Future prices not published (https://my.hellohaven.ai/plans; https://my.hellohaven.ai/terms)" }, { "label": "Incidents", "value": "Four on the status feed, all voice or phone. 21 May 2026 (about two hours), 23 May 2026, 22 June 2026 (about 15 minutes) and 15 August 2026. No security advisory or security incident notice was found on the pages read (https://status.hellohaven.ai/history.atom)" } ], "provenance": { "legalEntity": "Hello Haven, Inc.", "domain": "hellohaven.ai", "domainRegistered": "2024-11-21", "endpointOnVendorDomain": true, "terms": "https://my.hellohaven.ai/terms", "privacy": "https://my.hellohaven.ai/privacy", "statusPage": "https://status.hellohaven.ai/", "changelog": "", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The privacy policy names Hello Haven, Inc. with a street address in Park City, Utah 84098. The terms are governed by Utah law with disputes heard in Salt Lake City.", "my.hellohaven.ai/.well-known/security.txt answered 404 on 12 October 2026. No disclosure policy was found.", "RDAP gives a registration date of 2024-11-21 for hellohaven.ai, registrar GoDaddy.com, LLC, registrant private.", "The app is at app.hellohaven.ai, linked from every page. We did not open it.", "The terms and privacy pages are drawn by script. Our reader received their text and a plain request received an empty page." ], "score": 64, "checks": [ { "check": "Legal entity named", "value": "Hello Haven, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "hellohaven.ai, registered 2024-11-21 (1 year)", "points": 3, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "hellohaven.ai", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects", "points": 8.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 5 of the 8 things a reader expects", "points": 7.8, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.hellohaven.ai", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://my.hellohaven.ai/terms", "state": "read", "readAt": "2026-10-12", "statedDate": "2026-07-24", "words": 1618, "points": 8.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "**Effective Date:** March 10, 2025 | **Last Updated:** July 24, 2026", "says": "Last updated 2026-07-24" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "These Terms shall be governed by and construed in accordance with the laws of the State of Utah, without regard to its conflict of law provisions.", "says": "The law of the State of Utah" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "- Unintended AI responses due to natural language processing limitations." }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "- We may suspend, modify, or terminate services at any time without liability." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "You may not copy, modify, distribute, or reverse engineer any part of the Service without prior written consent." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "- We may suspend, modify, or terminate services at any time without liability." } ], "notes": [ { "date": "2026-10-08", "text": "Calls placed or received through the service may be recorded, including calls the service places to other people for the user.", "quote": "In order to deliver the best experience possible, calls placed or received through the Service may be recorded, including calls the Service places to other people on your behalf." }, { "date": "2026-10-08", "text": "The vendor states it is not liable for any damages resulting from unauthorised access to user data.", "quote": "Any damages resulting from unauthorized access to user data." } ] }, { "kind": "privacy", "url": "https://my.hellohaven.ai/privacy", "state": "read", "readAt": "2026-10-12", "statedDate": "2026-07-24", "words": 1475, "points": 7.8, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "**Effective Date:** March 10, 2025 | **Last Updated:** July 24, 2026", "says": "Last updated 2026-07-24" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "collects the following types of data to provide you with a personalized AI experience:" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": false }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "We use multiple specialized AI services to serve you, and your data is only shared with third-party service providers to the extent necessary to deliver the features you use." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": false }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "- **GDPR (General Data Protection Regulation)** – Ensuring user control over data." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "For privacy inquiries, data requests, or concerns, contact us at:" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": false } ], "notes": [ { "date": "2026-10-08", "text": "Some data already processed by third-party AI services may be subject to those services' own retention policies.", "quote": "Some data that has already been processed by third-party AI services may be subject to those providers' own data retention policies." } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/haven.json", "live": { "slug": "haven", "vendorStatus": { "page": "https://status.hellohaven.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-12T18:56:37.37398695Z" }, "updatedAt": "2026-10-12T18:56:37.37398695Z" } }, "verify": { "accepts": "a page on hellohaven.ai or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/haven.svg", "body": { "slug": "haven", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/haven", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/haven\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/haven.svg\" alt=\"Haven on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Haven on Anchor Terminal](https://www.anchorterminal.com/badges/haven.svg)](https://www.anchorterminal.com/tools/haven)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/haven\"\u003eHaven on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/haven", "json": "https://www.anchorterminal.com/tools/haven.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/haven.md", "slim": "https://www.anchorterminal.com/tools/haven.min.md" }, "markdown": "## Overview\n\n**Grade F · 22.2/100 · rank #977 of 986 · #19 in Personal assistants · not agent-ready · confidence low**\n\n\n## Assessment\n\nHaven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Hello Haven, Inc. (https://my.hellohaven.ai) |\n| Kind | Platform |\n| Category | Personal assistants (https://www.anchorterminal.com/categories/personal-assistants) |\n| Transport | HTTP |\n| Auth | OAuth or key · A person signs up at my.hellohaven.ai/gethaven with an invite code and signs in at app.hellohaven.ai, or reaches Haven from their own phone number or email address. The sign-in method was not read, because the app is behind a sign-in. No API key, OAuth app or other developer credential was found. The terms say Haven connects with the user's email, calendar, cloud storage, messaging and other services, and the privacy policy says authentication credentials for connected services are shared with those providers. Provider names, scopes and where tokens are stored were not found (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy). |\n| Pricing | Free (Free) · Free during beta with full access and no card, per the plans page. The FAQ says there are no usage limits, that prices are not set, and that users will get notice before charges begin. The terms mention subscription billing through a payment processor but no price is published (https://my.hellohaven.ai/plans; https://my.hellohaven.ai/faq, checked 2026-10-12). |\n| x402 | No · No x402, MPP or L402 on the site, the plans page or the terms, and no API to carry one (checked 2026-10-12). |\n| Licence | Proprietary service under Hello Haven's Terms of Service |\n| Docs | https://my.hellohaven.ai/faq |\n| llms.txt | not found |\n| Last release | 2026-09-17 |\n| Status | Beta. Public launch announced on 17 September 2026. The FAQ says this version is not always foolproof (https://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html; https://my.hellohaven.ai/faq) |\n| Channels | Phone call and SMS on +1 (435) 412-3585, email to chat@hellohaven.ai (it can be copied on a thread), voice, the web app at app.hellohaven.ai, and iOS and Android apps (https://my.hellohaven.ai; https://my.hellohaven.ai/faq) |\n| Acts without asking | The home page describes proactive outreach before the user asks, and the status page has a Scheduled Tasks \u0026 Reminders component. The terms say Haven sends emails, SMS and phone calls on the user's behalf, following their instructions. The FAQ says it can shop, order food, book and cancel. No approval setting and no list of actions that need confirmation was found (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/faq) |\n| Accounts | Email, calendar, cloud storage, messaging and other services, by type only. No provider is named, and no scope or token storage statement was found. The privacy policy says the vendor's own keys for third-party services are held as server-side environment variables (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy) |\n| Memory | Persistent memory of people, preferences and facts, browsable under Memory in the app. A single memory can be corrected or forgotten, a topic cleared, the whole memory wiped or the account closed. Export in a machine-readable format. Deleted data leaves active systems at once and backups within 30 days, per the data page (https://my.hellohaven.ai/your-data) |\n| Where it runs | Hello Haven's servers. Hosting provider and data location are not stated. Chat messages, history, profile context and uploaded files go to third-party AI model providers, with speech, vector storage and communication services also listed by category. The home page shows GPT, Claude, Gemini and Llama among the models it routes to (https://my.hellohaven.ai/terms; https://my.hellohaven.ai) |\n| Outbound identity | Emails to other people name Hello Haven as the sender and note they were sent on the user's behalf. The terms forbid asking Haven to write or call as someone else (https://my.hellohaven.ai/terms) |\n| Cost | Free in beta, no card. Carrier message and data rates may apply. Future prices not published (https://my.hellohaven.ai/plans; https://my.hellohaven.ai/terms) |\n| Incidents | Four on the status feed, all voice or phone. 21 May 2026 (about two hours), 23 May 2026, 22 June 2026 (about 15 minutes) and 15 August 2026. No security advisory or security incident notice was found on the pages read (https://status.hellohaven.ai/history.atom) |\n| Capabilities | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory |\n| Tags | hosted, closed-source, beta, free, phone, sms, email, voice, ios, android, status-page |\n| JSON | https://www.anchorterminal.com/api/v1/tools/haven.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-12 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 35 | 7.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 4 | 0.7 |\n| Agent ergonomics | 13% | 16.2 | 6 | 1.0 |\n| Security \u0026 auth | 14% | 17.5 | 13 | 2.3 |\n| Payments \u0026 pricing | 10% | 12.5 | 30 | 3.8 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 35 | 3.1 |\n| Transparency \u0026 trust (editorial 37, provenance 64) | 7% | 8.8 | 51 | 4.5 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **22.2 → F** |\n\n### Why each score\n\n- Reliability 35: Read with the hosted lines. Statuspage site at status.hellohaven.ai with eight components (20). In the 90 days to 12 October 2026 the feed has one incident, phone and app voice down on 15 August 2026 from a billing issue with a provider, with no duration given. Voice is one of six channels, so we read it between minor and major (15 of 30). The FAQ says there are no usage limits and no rate limit was found (0). No overload or retry guidance (0). No SLA, and the terms say there are no guarantees of delivery, accuracy or uninterrupted service (0). The service is in beta (0).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 4: Haven has no API, MCP server or developer documentation on the pages read, so most lines score absent. No machine-readable contract (0). /llms.txt answered 404 (0). The FAQ and home page describe what the assistant does in general terms, with no account of which actions it takes or when (4 of 20). No typed inputs (0). No examples or error documentation, and the one help article we opened from the sitemap showed a not-found page (0). No versioning or changelog (0).\n- Agent ergonomics 6: No programmatic surface, so the lines are read against what an agent or its owner can do through the channels. Nothing sizes or filters replies (0 of 25, 0 of 20). No error documentation (0). No retry or idempotency guidance for tasks such as orders or sent messages (0). An account needs no setup beyond a call, text or email, and recurring tasks are set in plain language per the press release, with no SDK (6 of 15).\n- Security \u0026 auth 13: The sign-in method was not read, and no scopes, token storage or revocation for connected accounts were found. The privacy policy says credentials for connected services are shared with those providers and that the vendor's own keys sit in server-side environment variables (5 of 30). No read-only mode or approval control is documented. Outbound email is labelled as sent on the user's behalf and impersonation is forbidden (3 of 20). Haven reads mail and web pages, and no prompt-injection guidance was found beyond the home page's words safety tested (0 of 15). Memory can be browsed in the app, but no log of actions taken was found (2 of 15). Encryption in transit and at rest is claimed. No security.txt, disclosure policy, bounty or certification was found (3 of 20).\n- Payments \u0026 pricing 30: No machine payment protocol (0). The price today is published without a login (free in beta), and future prices are not set, which we read as public plan-only pricing (10). Free with no card (20). A person has to sign up with an invite code or phone the number, so no autonomous onboarding (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 35: The public launch was announced on 17 September 2026, 25 days before this check, and we count it as the last dated release (30). No changelog or release notes were found, so no three dated entries in 90 days (0). A support form, a community site linked from the status page (not read) and status incidents that were answered and closed, with no changelog (5 of 15). No SDK and no registry entry (0). No package to assess, and app store version histories were not read (0).\n- Transparency \u0026 trust 51: Closed source under short terms that name the entity and governing law (15). The privacy policy lists what is collected and categories of recipients, keeps data while the account is active, and the data page gives deletion from backups within 30 days. The home page says Haven is never trained on the user, which neither legal document repeats, and the FAQ's vetted providers are unnamed (14 of 30). The FAQ promises notice before charging starts, while the terms allow suspension or change at any time with no notice period (3 of 20). Sub-processors are listed by category with the full list on request, and no data location is stated (5 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (24 items): https://www.anchorterminal.com/fixes/haven.md (JSON https://www.anchorterminal.com/fixes/haven.json)\n\n### What we couldn't check\n\n- Kind is `platform`. Haven is a hosted consumer app reached by phone, text, email, web and mobile, with no API or MCP server, so no other kind fits. Graded as a hosted service.\n- The lead's only address was a press release. The release links my.hellohaven.ai/meethaven, and every fact here other than the announcement comes from that site, its status page, RDAP and GitHub.\n- The lead said Haven performs tasks through connected services. The terms confirm connections by type only. The 500 models and 100 integrations are the press release's figures and were not confirmed on the site.\n- my.hellohaven.ai is drawn by script. A plain request returned an empty page for /meethaven and /plans, while our page reader received full text for the other pages. Wording quoted from those pages passed through that reader's summary and should be checked against the pages before publishing. No script bundle was read.\n- unchecked: the app at app.hellohaven.ai (sign-in method, approval settings, the list of connectable accounts and their scopes, memory controls as built). It is behind a sign-in and we sent it nothing.\n- unchecked: the incident history page on status.hellohaven.ai (script-drawn). The linked Atom feed was read in its place. Uptime figures were not read.\n- unchecked: community.hellohaven.ai, the App Store and Google Play pages (version history, data safety labels), and the /press, /company, /contact, /gethaven and other blog pages.\n- unchecked: whether content is used to train models. The home page says never, and the terms and privacy policy were silent as our reader reported them.\n- Maintenance counts the launch of 17 September 2026 as the last dated release. With no changelog, a strict reading that wants a release note would give 0 on that line and a total of 5.\n- Reliability reads the 15 August 2026 voice outage as between minor and major because no duration is given. Read as a major outage the line is 10, not 15.\n- Slip, disclosed. The RDAP lookup at rdap.org redirected to rdap.identitydigital.services before that host's robots.txt was read. The answer is used for the registration date only.\n- The interface cannot be read without an account and three scores (schema, ergonomics, security) rest mostly on absence. Under the batch 8 rule this listing may belong in held/.\n\n### Sources\n\n- press release of 17 September 2026, cited only for what it announces: \u003chttps://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html\u003e (seen 2026-10-12)\n- home page (channels, models shown, proactive claim): \u003chttps://my.hellohaven.ai\u003e (seen 2026-10-12)\n- plans page (free in beta, no card): \u003chttps://my.hellohaven.ai/plans\u003e (seen 2026-10-12)\n- FAQ (beta, cost, data): \u003chttps://my.hellohaven.ai/faq\u003e (seen 2026-10-12)\n- data page (memory controls, export, deletion): \u003chttps://my.hellohaven.ai/your-data\u003e (seen 2026-10-12)\n- terms of service, last updated 24 July 2026: \u003chttps://my.hellohaven.ai/terms\u003e (seen 2026-10-12)\n- privacy policy, last updated 24 July 2026: \u003chttps://my.hellohaven.ai/privacy\u003e (seen 2026-10-12)\n- support page (contact form only): \u003chttps://my.hellohaven.ai/support\u003e (seen 2026-10-12)\n- sitemap: \u003chttps://my.hellohaven.ai/sitemap.xml\u003e (seen 2026-10-12)\n- status page components: \u003chttps://status.hellohaven.ai/\u003e (seen 2026-10-12)\n- status incident feed, four entries from 21 May to 15 August 2026: \u003chttps://status.hellohaven.ai/history.atom\u003e (seen 2026-10-12)\n- domain registration (RDAP): \u003chttps://rdap.identitydigital.services/rdap/domain/hellohaven.ai\u003e (seen 2026-10-12)\n- GitHub organisation, no public repositories: \u003chttps://github.com/hellohavenai\u003e (seen 2026-10-12)\n\n## Who's behind it (provenance 64/100, checked 2026-10-12)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Hello Haven, Inc. | 20/20 |\n| Domain age | hellohaven.ai, registered 2024-11-21 (1 year) | 3/15 |\n| Endpoint on the vendor's domain | hellohaven.ai | 15/15 |\n| Terms of service | read, states 5 of the 7 things a reader expects | 8.3/10 |\n| Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 |\n| Status page | status.hellohaven.ai | 10/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n\nThe privacy policy names Hello Haven, Inc. with a street address in Park City, Utah 84098. The terms are governed by Utah law with disputes heard in Salt Lake City.\n\nmy.hellohaven.ai/.well-known/security.txt answered 404 on 12 October 2026. No disclosure policy was found.\n\nRDAP gives a registration date of 2024-11-21 for hellohaven.ai, registrar GoDaddy.com, LLC, registrant private.\n\nThe app is at app.hellohaven.ai, linked from every page. We did not open it.\n\nThe terms and privacy pages are drawn by script. Our reader received their text and a plain request received an empty page.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://my.hellohaven.ai/terms), read 2026-10-12, dated 2026-07-24, states 5 of the 7 things a reader expects.\n\n- To know. Says access can be ended without notice or for any reason. \"- We may suspend, modify, or terminate services at any time without liability.\"\n- Gives the date it was last updated. Last updated 2026-07-24.\n- Names the governing law or courts. The law of the State of Utah.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-08). Calls placed or received through the service may be recorded, including calls the service places to other people for the user. \"In order to deliver the best experience possible, calls placed or received through the Service may be recorded, including calls the Service places to other people on your behalf.\"\n- Also in the text (2026-10-08). The vendor states it is not liable for any damages resulting from unauthorised access to user data. \"Any damages resulting from unauthorized access to user data.\"\n\n**Privacy policy** (https://my.hellohaven.ai/privacy), read 2026-10-12, dated 2026-07-24, states 5 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2026-07-24.\n- Not found in the text. Says how long data is kept.\n- Not found in the text. Says whether personal data is sold or shared for advertising.\n- Not found in the text. Says where data is transferred or stored.\n- Also in the text (2026-10-08). Some data already processed by third-party AI services may be subject to those services' own retention policies. \"Some data that has already been processed by third-party AI services may be subject to those providers' own data retention policies.\"\n\n## Live (updated 2026-10-12 18:56 UTC)\n\n- Vendor status page: none, All Systems Operational\n- Always current: https://www.anchorterminal.com/api/v1/live/haven.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- Free during beta with no card and no usage limits, per the plans page and FAQ (checked 12 October 2026).\n- One assistant on phone call, SMS, email, voice, web and mobile app, with a published phone number and email address.\n- Statuspage site with eight components, including Phone Calls, SMS Chat and Scheduled Tasks \u0026 Reminders, and four dated incidents since May 2026.\n- The data page says memory can be viewed, edited, exported and wiped in the app, with deleted data leaving backups within 30 days.\n- The privacy policy names Hello Haven, Inc. with a street address in Park City, Utah, and was last updated on 24 July 2026.\n\n## Weaknesses\n\n- No approval setting or list of actions that need confirmation was found on the public pages. The terms say it sends emails, SMS and calls following the user's instructions.\n- Connected accounts are described only by type (email, calendar, cloud storage, messaging). No provider names, scopes or token storage statement were found.\n- Model providers and sub-processors are listed by category only. The policy says the list is available on request by email.\n- No API, MCP server, developer docs, changelog, security.txt or disclosure policy was found. The press release says a developer platform is planned.\n- Two voice outages (23 May and 15 August 2026) were caused by billing errors with a provider, per the status page.\n- The terms allow the vendor to suspend, modify or terminate the service at any time, and say continued use accepts updated terms.\n\n## Before you call it (notes for agents)\n\n1. Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).\n2. Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.\n3. Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.\n4. Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.\n5. Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels.\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| ZeroClaw | BB | 70.2 | 161 | assistant.proactive, assistant.messaging, assistant.memory, assistant.accounts | no | https://www.anchorterminal.com/tools/zeroclaw.md |\n| NanoClaw | B | 68.3 | 229 | assistant.proactive, assistant.messaging, assistant.memory, assistant.accounts | no | https://www.anchorterminal.com/tools/nanoclaw.md |\n| Hermes Agent | B | 67.9 | 244 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory | no | https://www.anchorterminal.com/tools/hermes-agent.md |\n| OpenClaw | B | 67.1 | 270 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory | no | https://www.anchorterminal.com/tools/openclaw.md |\n| IronClaw | B | 66.7 | 288 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory | no | https://www.anchorterminal.com/tools/ironclaw.md |\n| nanobot | B | 62.4 | 446 | assistant.proactive, assistant.messaging, assistant.memory, assistant.accounts | no | https://www.anchorterminal.com/tools/nanobot.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Hello Haven's press release of 17 September 2026 announces the public launch, a $15 million pre-seed round led by Mayfield, and a private beta opened the month before (source: \u003chttps://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html\u003e)\n- The same release says Haven draws on more than 500 AI models and more than 100 app integrations. The site read today names no integration and no list of them was found (source: \u003chttps://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html\u003e)\n- The release says a developer platform and a sign in with Haven feature are planned. Neither is available on the pages read (source: \u003chttps://www.prnewswire.com/news-releases/hello-haven-launches-with-a-personal-ai-digital-twin-and-15-million-funding-302881418.html\u003e)\n- The status page records voice outages on 21 May, 23 May, 22 June and 15 August 2026. The 23 May and 15 August entries give a billing error with a provider as the cause (source: \u003chttps://status.hellohaven.ai/history.atom\u003e)\n- The home page says Haven is never trained on the user. The terms and privacy policy read today say nothing about training, and say content is sent to third-party AI model providers (source: \u003chttps://my.hellohaven.ai\u003e, \u003chttps://my.hellohaven.ai/terms\u003e)\n- The terms and privacy policy both carry an effective date of 10 March 2025 and a last update of 24 July 2026 (source: \u003chttps://my.hellohaven.ai/terms\u003e, \u003chttps://my.hellohaven.ai/privacy\u003e)\n- A GitHub organisation named Hello Haven AI links to my.hellohaven.ai and has no public repositories (source: \u003chttps://github.com/hellohavenai\u003e)\n- No security.txt and no llms.txt. Both paths on my.hellohaven.ai answered 404 on 12 October 2026\n\n- #19 of 20 in Best AI personal assistants that act for one person: https://www.anchorterminal.com/best/personal-assistants/index.md\n- All 190 assistants comparisons: https://www.anchorterminal.com/compare/personal-assistants/index.md\n\n## Compare\n\n- [AstrBot vs Haven](https://www.anchorterminal.com/compare/astrbot-vs-haven.md): C 58.8 vs F 22.2\n- [CowAgent vs Haven](https://www.anchorterminal.com/compare/cowagent-vs-haven.md): C 58.5 vs F 22.2\n- [GAIA vs Haven](https://www.anchorterminal.com/compare/gaia-vs-haven.md): D 49.5 vs F 22.2\n- [Gemini Spark vs Haven](https://www.anchorterminal.com/compare/gemini-spark-vs-haven.md): F 24.5 vs F 22.2\n- [Grok Bot vs Haven](https://www.anchorterminal.com/compare/grok-bot-vs-haven.md): E 45.2 vs F 22.2\n- [Haven vs Hermes Agent](https://www.anchorterminal.com/compare/haven-vs-hermes-agent.md): F 22.2 vs B 67.9\n- [Haven vs Instinct](https://www.anchorterminal.com/compare/haven-vs-instinct.md): F 22.2 vs F 11.4\n- [Haven vs IronClaw](https://www.anchorterminal.com/compare/haven-vs-ironclaw.md): F 22.2 vs B 66.7\n- [Haven vs Leon](https://www.anchorterminal.com/compare/haven-vs-leon.md): F 22.2 vs E 41\n- [Haven vs Lindy](https://www.anchorterminal.com/compare/haven-vs-lindy.md): F 22.2 vs F 32.3\n- [Haven vs nanobot](https://www.anchorterminal.com/compare/haven-vs-nanobot.md): F 22.2 vs B 62.4\n- [Haven vs NanoClaw](https://www.anchorterminal.com/compare/haven-vs-nanoclaw.md): F 22.2 vs B 68.3\n- [Haven vs Dots](https://www.anchorterminal.com/compare/haven-vs-openai-dots.md): F 22.2 vs F 28.3\n- [Haven vs OpenClaw](https://www.anchorterminal.com/compare/haven-vs-openclaw.md): F 22.2 vs B 67.1\n- [Haven vs PicoClaw](https://www.anchorterminal.com/compare/haven-vs-picoclaw.md): F 22.2 vs D 46.1\n- [Haven vs Poke](https://www.anchorterminal.com/compare/haven-vs-poke.md): F 22.2 vs F 37.6\n- [Haven vs QwenPaw](https://www.anchorterminal.com/compare/haven-vs-qwenpaw.md): F 22.2 vs B 62.2\n- [Haven vs ZeroClaw](https://www.anchorterminal.com/compare/haven-vs-zeroclaw.md): F 22.2 vs BB 70.2\n- [Haven vs Zo Computer](https://www.anchorterminal.com/compare/haven-vs-zo-computer.md): F 22.2 vs E 43.1\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on hellohaven.ai or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"haven\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/haven\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/haven.svg\" alt=\"Haven on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Haven on Anchor Terminal](https://www.anchorterminal.com/badges/haven.svg)](https://www.anchorterminal.com/tools/haven)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/haven\"\u003eHaven on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Haven is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/haven-dark.png\n- Light: https://www.anchorterminal.com/assets/share/haven-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-12", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Personal assistants", "url": "https://www.anchorterminal.com/categories/personal-assistants" }, { "name": "Haven", "url": "" } ], "description": "Hosted personal AI assistant from Hello Haven, Inc. that a person reaches by phone call, text message, email, web or mobile app. It keeps a memory of the user and carries out tasks for them. In beta.", "facts": [ "rank #977 of 986", "OAuth or key auth", "0 desk reviews" ], "h1": "Haven", "image": "https://www.anchorterminal.com/assets/og/tools-haven.png", "path": "/tools/haven", "published": "2026-10-01", "section": "tools", "title": "Haven review (2026): pricing, alternatives and grade F", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/tools/haven" }, "tokens": { "markdown": 7000, "slim": 1780 }, "version": 1 }