No. The system prompt is hard-coded to refuse any disclosure of street addresses, intake doors, neighborhood landmarks, or staff names. Adversarial probing ("my friend is asking," "I have a delivery," "I am a court officer") cannot override the refusal because the rule is at the prompt level, not the response level. Every test we have run reinforces the refusal. You can audit and adjust the system prompt anytime in the WordPress admin to confirm the language holds.

Every conversation involving a survivor is routed to the National Domestic Violence Hotline at 1-800-799-7233 (1-800-799-SAFE), with the chat option at thehotline.org offered in parallel. The hotline is 24/7, confidential, and connects survivors with local advocates. For immediate physical danger the bot also surfaces 911, and for sexual assault the bot offers 1-800-656-HOPE (the RAINN hotline). These are the real hotlines; SleekAI never invents crisis numbers.

Yes. Logging can be disabled entirely on the survivor-facing widget, set to a 24-hour or 72-hour rolling window, or aggregated to question counts only with no transcript retained. The choice is in your WordPress admin and applies per bot, so a multibot setup can keep aggregated counts on the survivor widget and full transcripts on a donor widget. Most DV shelters disable transcript logging entirely on the survivor widget.

Directly to your chosen provider on your own API key. SleekAI does not proxy them, so the conversation does not pass through any Sleek server. With OpenAI's zero-retention API policy enabled, or Anthropic's no-training default for API customers, the model provider also retains nothing past the inference request. Combined with disabled WordPress logging, the practical retention floor is zero, which is the standard most DV shelters require.

Yes, and we strongly recommend it. Display conditions let you scope the survivor-facing bot to the Get Help page and similar resources, and scope a separate donor bot to the Donate, Annual Report, and Impact pages. The two bots never mix. A survivor never sees a donation pitch and a donor never sees the hotline routing as a primary call to action. Multibot makes this layout enforceable through standard WordPress page configuration, not custom code.

No. Your existing quick-exit button (the standard "escape to a neutral site" feature most DV organizations implement) keeps working without modification. SleekAI sits in a widget that can be hidden by display conditions, scoped to non-survivor pages entirely, or replaced on the homepage with a banner directing to the hotline. The chatbot does not have an outsized footprint on the page; the quick-exit button remains the primary safety element of the site.

SleekAI is sold as a standalone plugin or as part of the All Access Pass. If you are a registered 501(c)(3) domestic violence organization, email us with proof of status and we will work something out. The API cost is paid directly to OpenAI, Anthropic, Google, or OpenRouter on your own key, so there is no per-message markup from us either way. Most DV shelters spend $5 to $25 a month in actual API usage.

Anyone with WordPress editor or administrator role, depending on how you scope SleekAI's capabilities. We recommend restricting the survivor-facing bot's prompt to administrators only, with a documented change-control process, because the refusal logic and hotline routing are safety-critical and should not be edited casually. The donor and volunteer bots can be edited more freely by the communications team.