0
Try it free
Trust & Security

Your data stays yours.

LucyIQ is built on a simple principle: your AI agent only knows what you give it. It answers only from your own uploaded documents and your own website content — Professional and above can optionally search the web, and say when they have. It doesn’t invent facts about your business, and it doesn’t pull answers from other customers’ data.

Private RAG, in practice

This is what “private RAG” (retrieval-augmented generation) means in practice:

A private knowledge base per agent

Each agent has its own private partition of our knowledge database, sealed off at the database level. Your documents are indexed only for your agents and are never shared across accounts.

Account isolation

Every client runs in their own separate workspace. One customer’s content is never visible to another.

Grounded answers, not guesses

Because the agent retrieves from your content before responding, it stays on-topic and avoids the “confident hallucinations” that make general-purpose chatbots risky for business use.

How your data is handled

What we store

The documents you upload, the website content you choose to index, your agent configuration, and conversation logs so you can review and improve your agents.

Where it’s processed

To generate a reply, the relevant snippets of your content are sent to our AI processing layer and to our enterprise-grade AI language model provider (named in the full sub-processor list we provide on request), purely to compose that single answer (and to generate the search embeddings that power retrieval). Content sent through the provider’s API is not used to train its models, under that provider’s API terms — this is distinct from consumer chatbot apps, which LucyIQ does not use.

Where it’s hosted

We are located in New Zealand. Your application and its self-hosted automation layer run on dedicated virtual servers in Asia-Pacific, operated by Hostinger. Your knowledge base’s vector database is hosted in Sydney, Australia (AWS ap-southeast-2) via Supabase. All traffic is served over encrypted HTTPS (TLS, HTTP/2 and HTTP/3).

Direct, in-house document ingestion

When you add a document, it goes straight from your dashboard into your own private knowledge base — indexed within the same infrastructure that hosts it. We recently removed an external cloud-drive step that files used to pass through, so today there are fewer systems in the pipeline and one less third party that ever touches your content. Indexing is event-driven, so new material is usually searchable within seconds.

Phone calls (Call Assist)

Call Assist is an optional add-on that shows your staff answers from your own documents while they are on a phone call. Nothing a caller says is turned into text until your staff member has told them an assistant is listening and confirmed in the call window that the caller agreed. The sound of a call is never stored. It is converted to text by our speech-to-text provider (under API terms that do not allow training on it) and discarded. No transcript of a call is kept, and there is no setting that keeps one: the text is deleted once the summary of the call has been written, and no later than when the call is filed. Our AI provider may hold the text it processes for up to 30 days before deleting it; it does not keep call audio, and it does not use this text to train its models. We do not identify anyone by their voice. Call Assist is not offered in the United States.

Retention & deletion

You can delete uploaded documents at any time from your dashboard. If a subscription lapses, the account enters a 30-day grace period (site stays accessible, reminder emails sent), then a 30-day locked period (login disabled, data retained) — data is permanently deleted 60 days after your last paid period ends if the subscription isn’t reactivated.

Platform security

✓
Encrypted in transit. Every connection uses TLS, with modern browsers negotiating strong AES-256-GCM encryption over the latest TLS 1.3 (HTTP/2 and HTTP/3).
✓
DDoS protection & edge filtering. All traffic passes through Cloudflare before reaching our servers, which absorbs attacks and masks their address.
✓
Bot protection on chat. Public chat requests are protected by Cloudflare Turnstile, which runs invisibly in the background to confirm a request comes from a genuine visitor rather than an automated bot. Turnstile shows no puzzles, sets no tracking cookies, and does not build an advertising profile of visitors across websites — it assesses a limited set of technical signals from the browser solely for this check. Signed-in users are never challenged. Its use is also subject to Cloudflare’s Privacy Policy.
✓
Database-enforced tenant isolation. Every knowledge-base search is constrained at the database layer itself (PostgreSQL row-level security) to your account’s own partition — isolation isn’t only application logic, it’s enforced by the database. The high-privilege key that can write to the store is never exposed to the browser.
✓
Short-lived, tenant-scoped chat access. The chat widget never holds a long-lived credential. Each chat session is issued a short-lived token (valid for minutes) scoped to a single account, so a token can’t be reused to reach another tenant’s data or linger indefinitely.
✓
Encrypted, off-site backups. Databases are backed up daily and files weekly to AES-256 encrypted, geographically-separate storage, so your configuration and knowledge base can be restored after any incident.
✓
Access control. Private/internal agents (for example staff training agents) sit behind authenticated login. Account owners assign granular, per-feature permissions to each team member, so people see only what they should.
✓
Passwordless sign-in. You and your team sign in with a secure, single-use link (or short code) sent to your email — there’s no password to create, remember, or reuse. With no stored password to phish, guess, or leak, it’s a more secure default than a traditional username and password. A password stays available as an optional fallback if you prefer one.
✓
Two-factor authentication. Administrative accounts support two-factor authentication (one-time authenticator codes and backup codes) for an extra layer of login security.
✓
Hardened web application. We set modern browser security headers — including HSTS (strict transport security), content-type sniffing protection, and clickjacking (frame) protection — to defend against common web attacks.
✓
Locked-down infrastructure access. Administrative access to our servers is limited to the people who run LucyIQ and uses cryptographic keys.
✓
Least-privilege access. Production systems are accessible only by our senior staff (CEO, Head – Software Engineering and Head – DevOps). There’s no shared password and no broad staff access to raw customer data.
✓
PCI scope reduction. Card payments are handled entirely by our payment processors’ (Stripe / PayPal) hosted payment fields — full card numbers never pass through or get stored on our servers.
✓
Isolated pre-production environment. Our staging environment sits behind its own authentication layer, is blocked from search-engine indexing, and uses logically separate caches from production, so we can test changes without affecting live traffic.
✓
Independent uptime monitoring. Platform availability is monitored externally, from multiple global regions simultaneously, so outages are detected the moment they happen — independently of our own infrastructure.
✓
Authenticated email. System email is sent through an authenticated relay with SPF, DKIM, and DMARC configured, protecting you from spoofing.

Privacy & compliance

✓
Data ownership. You own your content. We act as a processor of it solely to provide the service.
✓
Sub-processors. We rely on a small set of reputable providers to operate the platform: Hostinger (infrastructure hosting for our application servers and our self-hosted automation layer — this automation layer is our own software running on our own servers, not a third-party processor), Cloudflare (DDoS protection, DNS, CDN, and Turnstile bot protection), Supabase (our vector database, for knowledge-base search), Amazon Web Services and Brevo (transactional email delivery). Card payments, once billing is live, will be processed by Stripe (card and subscription payments). Answers and search embeddings are generated by an enterprise-grade AI language model provider (named in the full sub-processor list we provide on request). We don’t sell your data to anyone.
✓
Privacy policy & DPA. Our privacy terms are set out in our Terms & Conditions. Need a Data Processing Agreement? Contact us at security@lucyiq.com.
✓
Data subject requests. In line with GDPR/CCPA-style data rights, you can request access to or erasure of your personal data at any time — contact security@lucyiq.com to make a request.
✓
Certifications. We don’t hold SOC 2 currently (see Where we are heading, below). We’re happy to complete a security questionnaire or walk security-conscious customers through our setup directly — just ask.

Accessibility

We want your chat agent to work for as many of your visitors as possible — including people who use a keyboard, a screen reader, or other assistive technology. We build and test our embeddable chat widget to follow the internationally recognised Web Content Accessibility Guidelines (WCAG 2.1, Level AA), and we treat accessibility as an ongoing commitment, not a one-off checkbox.

✓
Works with a keyboard alone. Every control can be reached and used from the keyboard, with a clear, high-contrast highlight showing where you are and a sensible focus order inside the chat window.
✓
Supports screen readers. Buttons and fields carry descriptive labels, the chat window is announced as a dialog, and new replies are read out as they arrive.
✓
Keeps text readable. Colours are checked and, where needed, adjusted automatically so messages, labels and links stay legible against whatever background they land on — in both light and dark mode.
✓
Respects visitor preferences. It follows the visitor’s own device setting for light/dark appearance and for reduced motion, and it translates its own controls into the visitor’s language.
✓
Is clear that it’s AI. A small, always-on caption lets visitors know they’re chatting with an AI assistant.
✓
Tested automatically. We check these behaviours with automated tests, including colour-contrast and keyboard-focus tests. If you or one of your visitors ever has trouble using the chat, or has an accessibility need we haven’t covered, email info@lucyiq.com and we’ll do our best to help.

Franchises and multi-location networks

The Franchise plan runs many locations under one franchisor account, with a data model built so a network can be run centrally without surveillance:

✓
Each location is isolated. A location’s knowledge is private to that location plus the one shared hub manual — never another location, never another franchise, never another network.
✓
The manual is for staff, not the public. The shared manual is answered to each location’s signed-in team only. A customer on a location’s public chat is never answered from it, unless head office marks an assistant as safe for customers.
✓
Head office sees patterns, not people. The franchisor’s console shows usage and the questions the manual doesn’t answer yet, as aggregates only — never a location’s individual conversations. Head office can also see whether each team member has signed in and how many conversations they had, never what was asked.
✓
Logging into a location is visible and audited. When head office logs into a location to help, it is recorded and shown to that location’s own admin. It is not silent access.
✓
Franchisees own their data on exit. A location that leaves the network keeps its own local knowledge and can continue on its own plan; the franchisor’s shared manual stays with the franchisor.

Where we’re headed

Security is an ongoing commitment, not a checkbox. As we grow, we’re continuing to invest in it — including formalising our internal security policies, rolling out two-factor authentication across all administrative access, and working toward independent security assessment (such as SOC 2 readiness). If your organisation has specific security or compliance requirements, we’d welcome the conversation — talking to security-conscious customers directly is how we prioritise this work.

Talk to us

Found a security issue?

We take vulnerability reports seriously. If you believe you’ve found a security issue in LucyIQ, email security@lucyiq.com with details — we’ll acknowledge your report and investigate promptly.

Questions?

Security or privacy question we haven’t answered? Email security@lucyiq.com and a human will get back to you.

Free trial

Try LucyIQ free on your own website

Give us your website and we’ll build you a working AI agent trained on it — in about a minute.

Free · about 60 seconds · no signup