Common questions, answered honestly.
These come up in every prospect conversation. We answer them in plain language. If your question is not here, email us at hello@nansy.io.
Where does our data live?
Supabase Postgres in the EU region (Frankfurt) at the database layer; Vercel edge for the application layer. Storage (uploaded images, documents) on Supabase Storage. We can move database region on request — but the default is EU because Israeli boutique firms typically need data residency that is EU-compliant for cross-border matters.
What happens if Nansy fails or shuts down?
Every tenant has a one-click "Export everything" capability built into the dashboard (Module 8.5). The export includes: every blog post, contact, lead, schedule entry, audit log row, and signed document — as a structured ZIP (JSON + binary). You take it and run. We hold the data; we do not own the data.
Is the AI Secretary going to make up legal advice?
No. The AI Secretary cannot improvise legal content. It schedules, drafts replies inside templates, prepares documents from author-controlled templates only (per Module 25), and surfaces every action for partner approval before it sends. Bar Rule 8 advertising scanner runs on every publish path. Legal opinions, court filings, and contract drafting are explicitly out of scope.
How does the Bar Rule 8 ethics scanner work?
Every blog post, social caption, email campaign, and AI-prepared document is scanned for forbidden phrases (in Hebrew, Arabic, and English) before publish. Matches at "block" severity halt the publish; only ADMIN can override with a logged justification. The pattern set is firm-overridable, the audit trail is permanent.
Do you support Hebrew + Arabic + English natively?
Hebrew is the default. Arabic and English are first-class. Trilingual content is a primary data shape, not an afterthought — every blog post, practice area, partner bio, and CTA carries all three locales in the same row. RTL flow is the rendering default.
Can we use our own domain?
Yes. New tenants start at <slug>.nansy.io (e.g., nas.nansy.io). When you are ready to migrate to your own domain, we update the Tenant.customDomain column and the next request to that host renders your site. No code change, no redeployment on your side. The subdomain keeps working in parallel until you decide to redirect.
What if a partner leaves the firm?
Standard offboarding: revoke their TenantMembership row in the dashboard. Their session terminates on next request. Authored content (blog posts, drafts) stays attributed to them in the audit log; the firm can re-attribute or anonymize via the data-rights flow.
Is this GDPR / Israeli PPL Amendment 13 compliant?
Yes for the platform infrastructure. Cookie consent is opt-in (Amendment 13 default). Sub-processor inventory at /legal/subprocessors. DPIA tracking + DSR (data-subject-right) flow live in the dashboard. The compliance posture for YOUR firm depends on what content you publish and how you handle client matters — Nansy provides the rails; you operate them.
How much does it cost?
Pricing is at /pricing. Three tiers: Essential (smart portfolio site), Pro (adds the AI Secretary), Enterprise (managed customisation). 2026 onboarding cohort gets the early-stage rate; talk to us.
Is the platform pentested?
Engineering side is at the cleanest state we can produce internally — multiple smoke-audit waves with file:line evidence, regression-pin tests for visual + security contracts, fail-closed tenant resolution. External pentester engagement is scheduled for the post-handoff window (4–6 week lead time). The full RLS-gate posture is published at /security.
Still have questions?
Email us at hello@nansy.io with your firm size, primary practice areas, and what you wish was different about your current stack. We answer in one business day.
Get in touch