Trust & security
Autonomous does not mean uncontrolled
You decide what Eli can see, what it can change and what must wait for approval. Execution should stay bounded, reversible and visible. This page states only what is true today. If a claim is not here, we do not make it.
Where your data lives
Core data hosted in the European Union
Eli's core customer database is hosted in Frankfurt. AI checks may send a buyer question and relevant public context to the selected model provider under that provider's terms. We do not claim that every provider request stays in the EU.
Data minimization and controls
We collect the data needed to do the work: your site, what AI says about it, and the outcomes you choose to track. We sign a Data Processing Agreement on request. To export or delete your workspace data, email get@hireeli.io from the address on your account and we confirm the request.
No personal-visitor tracking
Our site tag never stores a raw IP or personal identifier. It records a salted daily hash so repeat visits are not linked across days, and reports only aggregate AI-referred visits plus visits to conversion pages you configure. Those page visits are directional and are never called revenue. Until a visitor accepts analytics the tag measures nothing and shows nothing; it only reports that it is installed. It never changes your pages' own code or what search engines read, and removing it, or Stop everything in Eli, ends everything it shows.
How your data is protected
Isolated per customer
Database row-level security scopes every protected table to your workspace. Customer isolation is enforced in the database rather than relying only on application checks.
Connections are encrypted
When you connect a site or search service, credentials are encrypted with AES-256-GCM before storage and decrypted only in memory to do the work. Stored values are ciphertext rather than plaintext credentials.
Access you control
Every connection uses a key you create and can revoke: a WordPress application password, a read-only Search Console user, a Bing API key, or a Slack webhook. Revoking it removes Eli's future access. We ask for the least access that does the job, and read-only access wherever possible.
Third-party sends stay human
Eli may apply bounded changes to a site connection you explicitly own. Anything sent to another site or person stays a one-click human action. The engine drafts; a human makes the final send. That is a safety boundary, not just a feature.
Which third parties process data?
AI model providers
To measure AI answers, Eli sends the buyer question and relevant public context about your company to OpenAI, Anthropic, Google and Perplexity through their APIs. Web search results are retrieved through Serper. Eli does not send visitor identities, credentials or CRM records to model providers.
Infrastructure
The application runs on Vercel in the Frankfurt region and the core database is hosted by Supabase in Frankfurt. Payments are processed by Stripe; Eli does not store card numbers.
How are website changes approved and recorded?
Approval is the default
No draft reaches a public URL without a human approval. Automatic publishing of low-risk changes to your own site is a separate switch you turn on yourself, with weekly and monthly caps, and you can turn it off at any time.
Every change leaves a receipt
After a change is published, Eli fetches the exact public URL and checks the approved content is there before calling it live. The approval, the published content and the later measurement are stored as separate records.
Actions through AI tools need explicit confirmation
When you use Eli from an AI assistant, a change is shown as a full before-and-after preview first and proceeds only on an explicit confirmation. Each such action is written to an audit log and counted against a daily cap.
How we handle AI Search honestly
We measure, we do not invent
Every number in your dashboard comes from something we actually observed: real AI answers, your own console data, real visits. Where we estimate, we label it an estimate and show the assumption. We never present a modeled number as measured revenue.
Safe website work
Eli uses honest comparisons, visible methods, checked sources and clear limits. It does not use tactics that could put your search presence at risk.
Certifications and roadmap
SOC 2: on the roadmap
We are not yet SOC 2 certified and we will not claim otherwise. If you are evaluating Eli for a security review, contact us and we will share our current security posture in detail and our timeline. We begin the formal process when a customer's security review calls for it.
Single sign-on
Google sign-in is available today. SSO/SAML for teams is available on request as you scale.
Status
Live service status is at /status. If something is degraded, you will see it there.
Have a security question or need a DPA? get@hireeli.io
See live service status