What is Globe?
Globe is a tool that helps you answer questions about a client's insurance cover. You type a question — like "Does this policy cover storm damage?" — and Globe reads the client's Policy Schedule and the insurer's Policy Wording to give you an answer.
Globe does not guess. If the answer isn't in the documents, it will tell you that instead of making something up.
Before you run a query
Three things need to be set up in Admin before Globe can answer questions about a client:
- Policy Wording uploaded — the insurer's standard terms document (e.g. Allianz Business Pack 2025). This goes in Admin → Wordings.
- Client added — the client's name, policy number, insurer, product, and inception date. This goes in Admin → Clients.
- Policy Schedule uploaded — the client's specific cover document. Search for the client in Admin → Schedules, then upload their PDF.
If any of these are missing, Globe will tell you when you try to run a query.
Running a query
- Search for the client — type their name or policy number in the Client search box. Click their name when it appears.
- Check the Policy Wording — Globe will automatically select the right wording based on the client's inception date. You can change this manually using the dropdown if needed.
- Type your question — be specific. Instead of "Is this covered?", try "Does this policy cover accidental damage to stock caused by a burst pipe?" Then click Submit Query or press Ctrl+Enter.
Reading the answer
Globe's answer is based only on the two documents loaded for that client. It will reference specific sections where it can.
After the answer appears, two buttons will show at the bottom:
- Open Policy Schedule — opens the client's uploaded schedule PDF so you can read it yourself.
- Open Policy Wording — opens the full wording document to verify the relevant clause.
Always verify important answers against the original documents before advising a client. If the answer involves a legal interpretation of the policy, confirm with the insurer or a qualified adviser.
Managing the library (Admin)
The Admin panel has three tabs:
- Wordings — upload, edit, or delete policy wording documents. Use the filter bar to find a specific insurer or product. You can edit the insurer name, product name, or effective date on any wording by clicking Edit on its card.
- Clients — add new clients with their policy details. Client records cannot be edited after creation yet (see roadmap).
- Schedules — upload a Policy Schedule for a client. Search for the client first, then upload their PDF. The document is encrypted the moment it arrives — it is never stored unencrypted.
Document versioning
Built Policy Wordings — multiple versions of the same wording can exist at the same time (e.g. Meridian Business Pack effective 1 Mar 2025 and 1 Mar 2026). Globe automatically picks the right version for each client based on their inception date. Staff can also override this manually.
Not built Policy Schedules — uploading a new schedule for a client replaces the previous one. There is no history. If you need to keep a copy of an old schedule, save it elsewhere before uploading the new one.
Privacy & security
Where data is stored: Client names, policy numbers, and policy wording text are stored in a secure database (Supabase) hosted in Sydney, Australia. This keeps client data on Australian soil in line with Australian Privacy Act requirements.
Policy Schedules: These contain sensitive client information, so they are treated differently. When you upload a schedule, it is encrypted immediately on the server before being saved to disk. The encryption key is separate from the file and stored independently. Even if someone accessed the server files directly, they could not read the document.
What reaches your screen: Globe never sends document content to your browser. The schedule is decrypted on the server, the AI generates an answer on the server, and only the text of that answer is sent back to you. When you click "Open Policy Schedule" or "Open Policy Wording", the file is decrypted on the server and streamed directly to your browser — it is not stored on your device.
Audit logging: Every query is recorded — who ran it, which client, and which documents were accessed. The question and answer text are not recorded.
What's not built yet
- Login screen — there are no individual staff accounts. Everyone uses the same shared access. This is planned.
- Admin vs. staff roles — all staff can currently access the Admin panel. There's no way to restrict this yet.
- Audit log viewer — the logs are being recorded but there's no screen to view them inside Globe.
- Client record editing — once a client is added, their details can't be changed through Globe. This requires database-level access.
- Schedule version history — as above, uploading a new schedule overwrites the old one.
- Schedule deletion via Globe — schedules can only be removed by an administrator at the database level.
- Multiple policies per client — each client can only have one active policy in the system at a time.
What's coming next
- Individual staff logins with separate admin and read-only roles
- Audit log viewer inside Globe for compliance and oversight
- Client record editing
- Schedule version history — keep a record of all uploaded schedules per client
- Support for multiple policies per client
Technical overview
Globe is built and hosted across three platforms. Here is what each one does.
-
Railway — hosts the Globe server. When you open the URL in your browser, Railway receives the request and forwards it to the server running inside a secure container. Railway also manages the custom domain and SSL certificate that makes the connection secure (the padlock in your browser).
-
Supabase (database) — stores all structured data: client records, policy details, wording document text, and the audit log. Supabase uses PostgreSQL, a widely used open-source database. Globe connects to it directly from the server — the database is never exposed to the browser.
-
Supabase (file storage) — stores the encrypted schedule files. When you upload a Policy Schedule, Globe encrypts it before it leaves the server, then stores the encrypted file in a private Supabase storage bucket. The original file is never written to disk unencrypted.
-
Anthropic (Claude API) — the AI that answers staff questions. When a query is submitted, the server sends the Policy Wording, the decrypted Policy Schedule, and the staff question to Claude. Claude reads the documents and returns an answer with a source citation. The API call happens entirely on the server — your Anthropic API key and document contents are never sent to the browser.
-
GitHub — stores the Globe source code and tracks every change. Railway watches the GitHub repository and automatically redeploys Globe whenever new code is pushed to the main branch.
All document encryption uses AES-256-GCM, a standard used by banks and government systems. Each document gets its own unique encryption key, which is itself encrypted using a master key stored only in Railway's environment variables — never in the database or source code.