Security

Your drawings are commercially sensitive.

A structural pack is competitive information — details, quantities, the decisions behind them. s.eye is built so that protecting it doesn't depend on anyone's good behaviour. The controls are in the database and the storage layer, not in a promise to be careful.

Free trial pack · No credit card
Public signups are currently waitlisted.
Access model

Operator-blind by construction.

s.eye staff cannot browse your reviews. There is no admin screen that lists customer packs, and no support back door in the application that quietly opens a finding, a drawing or an export. Keeping your work private does not rely on us choosing not to look — the application has no path that would let us.

How that is enforced.Row-level security scopes every table to the requesting member's organisation at the database layer: each policy checks organisation membership before a single row is returned, and the sensitive mutations are locked behind security-definer routines rather than a broad table grant. Drawings live in org-namespaced storage paths, private by default, reachable only through short-lived signed URLs minted per object on the server. The enforcement lives in the schema, applied to every query by the database itself — not in a staff policy document. This is a constraint on the application; it is not a claim that infrastructure access is impossible.
Data residency

Your data stored in Australia.

The production database and drawing storage run in the ap-southeast-2 (Sydney) region. Your packs are uploaded to, stored in and served from Australia — the system of record never moves.

One honest caveat, because precision matters here: during a review, sheet images are read by the AI models over an encrypted API connection, under the same no-training terms as everything else on this page. What lives permanently — the drawings, the register, the exports, the database — stays onshore, which keeps client confidentiality, professional-indemnity and public-sector data expectations simpler for an Australian practice.

Model training

No training on your packs.

No pack is ever used to train models.

The pack you upload is processed only to produce your review and your exports — it is never added to a training corpus.

Data lifecycle

What we hold, and how it leaves.

A short, honest account of what a review stores, how it is reached, and what happens when you remove it.

What we store

The pack and what it produces

The drawings you upload, rasterised one image per sheet; the supplementary parameters extracted from geotech reports and computations; and the findings and exports your review produces.

How access works

Per-object signed URLs

Every sheet image and source file is served through a signed URL minted for a single object, valid for 600 seconds. There is no public link to a drawing; the URL expires, and a fresh one is minted server-side only when a member of your organisation asks for it.

What deletion does

Deleting a review

Deleting a review removes the review record and its findings immediately, and deletes the uploaded drawings from storage. In the rare case a file removal fails it is logged and purged manually on written request — we never claim a file is gone until it is.

Account deletion

Access ends immediately; purge on request

Deleting your account revokes all access at once — your organisation and its reviews stop being reachable the moment it is deleted. A permanent purge of the stored data and uploaded files is performed on written request; email us and we complete it manually.

s.eye is a review-assistance tool. Findings are not engineering certification and must be verified by a qualified engineer.

Scope of the tool

What s.eye is not.

s.eye is a review-assistance tool, not an approval and not a substitute for engineering judgement. It reads the pack and drafts the register; the decisions about what is material, what is resolved and what gets issued stay with a qualified engineer. A finding is a prompt to check something — never a certification that it is correct. The signature on the drawings stays exactly where it belongs. We treat that boundary as a feature, not a limitation.

s.eye is a review-assistance tool. Findings are not engineering certification and must be verified by a qualified engineer.

Questions

Common questions

Who can see my pack?

Members of your organisation, and no one else. Access is scoped by row-level security at the database, so a query only ever returns rows for the caller's organisation. s.eye staff have no admin screen and no support back door in the application that would let them browse your reviews.

Where is my pack stored?

In the ap-southeast-2 (Sydney) region — the production database and drawing storage are onshore in Australia. During a review, sheet images are read by the AI models over an encrypted API under no-training terms; the stored pack, the register and every export stay in Sydney.

Is my pack used to train AI?

No pack is ever used to train models. The pack is processed to run your review and nothing else.

How do I delete everything?

Deleting a review removes its record and findings immediately and deletes the uploaded drawings from storage; if a file removal fails it is logged and purged manually on written request. Deleting your account revokes all access at once, and a permanent purge of the stored data and files follows on written request — email us and we complete it manually.

Do you have SOC 2 or ISO 27001?

Not yet — we hold no third-party security certification today. Rather than point at an audit we haven't completed, we publish how the system is actually built: org-scoped row-level security, private per-object storage and Australian data residency, described on this page. If a formal certification becomes a requirement for your practice, tell us.

Get started

Start free — no demo required.

Public signups are currently waitlisted — request access and we'll open your workspace. Free trial pack, no credit card.

Start free