For finance aggregators and broker networks

Give brokers a focused ID record workflow — with a CRM pathway in development.

SightVault is being built as a self-serve broker portal and a future back-end service that can connect to an aggregator or broker CRM. Brokers keep a retained sighting record and deletion history while raw ID images are held only for a short, defined period.

Open an aggregator discussion See the integration pathway

Self-serve broker portalBroker signup links plannedCRM/API pathway in development

Australian business, based in Australia. SightVault product servers are hosted in Australia.

Aggregator platform

Broker CRM

Broker portal

Retention and deletion records

One connected record pathway for broker networks

The network challenge

A consistent handling approach is difficult when every broker uses a different mix of systems.

Raw ID images may sit in email, CRM attachments, local folders, cloud drives and mobile devices. Aggregators need a practical option they can discuss with brokers without forcing every member to rebuild their whole application workflow.

Different broker habits

Each business may name, store, retrieve and delete raw files differently.

CRM copies and broker copies

Each system owner must control its own copy and decide when continued retention remains necessary.

Records need to outlast the image

Brokers still need a useful sighting record and deletion history after the photographic copy is removed.

What the network offer can include

Start with self-serve access. Add a connected pathway with the aggregator.

SightVault is intended to support individual broker adoption and a later CRM-connected workflow under a separately defined integration scope.

Self-serve broker workspaces

Brokers can upload ID files, create sighting records, search clients, manage the holding window and access retention and deletion logs.

Network signup links

Broker signup links are planned so an aggregator can direct members to the appropriate SightVault onboarding path.

CRM/API pathway

An integration pathway is in development for CRM platforms that want to send permitted files and record metadata to SightVault.

Permission-controlled broker access

Broker workspace owners can separate upload, raw-image, deletion, report and log permissions across their team.

Planned CRM/API pathway

A connected pathway for broker systems is in development

A CRM and API pathway is in development to support integration with broker systems.

Broker account and credentials

The broker creates a SightVault account and API credentials.

Broker workspace

CRM sends the agreed data

The CRM sends ID data to the broker’s SightVault workspace.

Aggregator or CRM

CRM controls its own copies

The CRM manages its own deletion of stored ID files.

CRM responsibility

SightVault manages the record workflow

SightVault manages the record, retention and deletion process inside the broker workspace.

SightVault workflow

Broker-facing experience

A portal that makes sense to brokers from day one

The portal is organised around practical actions: Upload ID, Search ID, Sighting Reports, Retention Log, Deletion Log, Users & Permissions and Settings. Select any software screen to open a larger view.

SightVault broker dashboard showing active ID files, sighting records and scheduled deletion activity

Workspace dashboard

Broker teams can see active raw files, retained sighting records, scheduled deletion activity and items needing attention.

Unassigned uploads

Broker teams can review uploaded files, confirm client details and complete assignment before the record moves forward.

Sighting reports

Retained reports and record evidence remain available after the raw image lifecycle has ended.

Potential value to an aggregator

A focused product discussion across product, compliance and broker support teams

A repeatable broker workflow

Offer members a dedicated place for temporary ID holding, sighting records and deletion history.

A staged rollout

Start self service broker portals, gather operational feedback and define the CRM pathway separate

Clear system boundaries

Document which platform holds each copy, which party removes it and what record remains.

Broker-controlled access

Workspace permissions support different roles for upload, raw ID access, manual deletion, reports and logs.

Important product boundary

A connected workflow does not replace each party’s responsibilities.

SightVault’s role is limited to its record and temporary-holding workflow. Each aggregator, CRM owner and broker remains responsible for the systems, copies and obligations it controls.

What SightVault createsSightVault creates ID sighting records and deletion evidence. It does not independently verify identity, conduct DVS/IDV checks, perform AML verification or guarantee compliance outcomes.

What remains with the brokerSightVault is not intended to replace a broker’s own legal, privacy, AML/CTF, responsible lending or lender-process obligations. It provides a secure record workflow and deletion evidence.

Aggregator FAQ

Questions for an early product discussion

The answers describe the planned direction. A real integration would require a separately agreed scope and technical review.

Is the CRM/API connection available now?

No. The pathway is in development. The current product direction includes a broker portal first and a connected CRM workflow developed with the relevant aggregator or CRM team.

What would the aggregator or CRM need to build?

The CRM owner would add its own front-end action and code to send permitted files and agreed metadata. It would also remain responsible for controlling and removing copies retained in its own systems.

What does SightVault do after transfer?

SightVault is intended to create the sighting record, hold the raw file for the configured period, allow earlier deletion by authorised users, automatically delete any remaining raw image within 14 days and keep the relevant records and logs.

Can individual brokers use SightVault without CRM work?

Yes. The self-serve broker portal is the first access model. Broker signup links are planned for network distribution.

What should be covered in an early discussion?

Broker workflow, CRM ownership, files and metadata to be transferred, access permissions, deletion responsibility, rollout group, support model and the evidence needed before implementation.

What is the target launch timing?

The current owner target to full launch is 5–8 weeks. Timing remains subject to completion, testing and review.

Start the conversation now

Open a discussion now about your front-end CRM and the SightVault backend pathway

Bring together the aggregator product, compliance, technology and broker-support contacts to assess fit and define the right next step.

5–8

weeks to targeted full launch

Integration timing would be planned separately with the aggregator or CRM team.

Aggregator and CRM enquiry

Open a product-fit discussion

Use this form for business and integration enquiries only. Do not include customer, applicant or ID document information.