Short-term access, long-term clutter
Teams may need an ID image during an active lender or application process, but not as an indefinite file copy.
Built for finance and mortgage brokers
Temporary ID holding. Permanent sighting records.
SightVault is being built to help broker teams move raw ID images out of scattered inboxes, devices and folders, create a structured sighting record, and keep clear retention and deletion logs.
12-day defaultConfigurable raw ID holding window
14-day maximumRaw images deleted sooner when no longer needed
Records retainedSighting, retention and deletion information remains
Australian business, based in Australia. SightVault product servers are hosted in Australia.
5–8 weeksCurrent target to full launch. Timing remains subject to completion and review.
The business problem
Raw ID files are useful for a short period. They should not become the permanent record.
Finance applications often move photographic ID through email, CRM platforms, cloud storage, local folders and mobile devices. That makes it harder to control access, know what is still needed and document when raw files were removed.
Scattered records
A separate sighting record can preserve the visible document details and handling context after the image is removed.
Deletion activity is hard to evidence
Manual and scheduled deletion logs give authorised teams a searchable record of what was received and when it was deleted.
How SightVault is intended to work
From upload to retained records and deletion history
The workflow keeps the raw image separate from the business record that remains after deletion.
01
Upload ID documents for a client
Add the permitted licence, passport or other supported photo ID images for the client.
02
Read the visible fields
The system reads visible document fields and prepares the information for a sighting record.
03
Create the retained record
A retained ID sighting record is created with the document, processing and retention information.
04
Keep the image briefly
The raw ID image remains available for a limited time while it is needed for the application or lender process.
05
Delete the raw image
The image is deleted after the set retention period, or earlier when an authorised user removes it manually.
06
Keep the business history
The system keeps the sighting record, retention details and deletion log.
Core product workflow
One focused place for upload, search, records and deletion history
The broker portal is designed around the tasks staff need to complete, without turning raw ID images into permanent file storage. Select any software screen to open a larger view.
Upload and extraction
Add one client or a batch of files
Use the client mobile, client ID or application reference to organise a record. Where the identifier is already included in the file name, SightVault can use it to group the uploaded files.
Single and bulk workflowsAdd one client at a time or group multiple files by mobile number.
AI-assisted field readingRead visible name, date, document number, expiry, issue location, address and document side where available.
Files organised for searchDisplay names can combine the client name, mobile and document side so records are easier to retrieve.
Unassigned uploadsReview and assign uploaded files
Search and retrieve
How do I find a client’s ID later?
Files are automatically renamed using the client name, mobile or reference, so the team can retrieve the record using details it already knows.
- Search by client name.
- Search by client ID or application reference.
- Search by mobile number.
- If the raw ID is still within the holding period, authorised users can access it.
- The sighting record and logs remain available after the raw image is deleted.
View raw IDAccess the raw image while it remains active
Retained sighting record
Keep the details and handling history, not the raw image
The sighting record captures the key identification details, processing information and retention history required after the original image is removed.
The record is retained after the raw ID image has been deleted.
- Report date and staff user
- Document type
- Client, ID Details application reference
- Sighting method and time
- AI extraction status
- Retention reason and due date
- Source file names
- Deletion status and timestamp
Sighting recordRetained record details and handling history
Retention and deletion logs
Temporary raw-file handling with a retained record history
- Raw ID images are held temporarily for application or lender use.
- A default retention period applies, such as the 12-day workspace default.
- Authorised users can delete ID images earlier when they are no longer required.
- If not removed manually, the system deletes the raw image after the retention period.
- A deletion log is retained showing when the file was removed.
The system maintains a complete record history, including:
- upload and processing events;
- report creation;
- the retention period; and
- deletion status, whether manual or automatic.
This record remains available after the raw ID image has been removed.
Sighting reportsRetained reports and record evidence
Team permissions
Configure access around the way your team works
- Control who can view raw ID images.
- Control who can access sighting records.
- Control who can delete files.
- Restrict some users to reports and logs only.
- Configure team roles based on your workflow.
Manual reviewReview exceptions and records needing attention
Important product boundary
A record workflow — not a substitute for the broker’s own obligations.
SightVault is designed to create structured records and deletion evidence while responsibility for customer identification and business processes remains with the broker.
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.
Handling photographic ID documents
Separate temporary ID handling from long-term record keeping.
Recent AML/CTF reforms and privacy guidance have changed how photographic ID documents are handled. Businesses may still collect ID documents to identify a customer, but retaining copies of those documents is not always required.
ID images should be removed when they are no longer reasonably needed for the purpose for which they were collected. Instead of keeping the image, businesses need to retain evidence of how identification was completed.
SightVault is designed to support this workflow by separating temporary ID handling from long-term record keeping.
Document sightedKeep the type of ID that was sighted.
Review detailsKeep when it was reviewed and how it was checked.
Reference informationKeep the relevant reference details in the retained record.
Initial markets
Broker-first, with wider professional use cases
The first product focus is finance and mortgage broking and finance aggregator networks. Accountants, lawyers and conveyancers, real estate professionals and dealers in precious metals can use the same SightVault workflow at launch; a separate workflow or additional software development is not required for those sectors.
Finance and mortgage brokers
Brokerages, commercial and asset finance teams that collect ID for applications and lender processes.
Finance aggregators
Networks seeking a consistent broker workflow, a future CRM pathway and retained record visibility.
Accountants
Professional practices can use the same upload, sighting-record, temporary-holding and deletion-log workflow.
Lawyers and conveyancers
Legal and property practices can use the same SightVault workflow for relevant customer ID handling.
Real estate professionals
Property businesses can use the same workflow where photographic ID is collected for a genuine business purpose.
Dealers in precious metals
Dealers can use the same workflow where customer ID is collected for a genuine business purpose.
Aggregator and CRM/API pathway in development
Monthly pricing
Simple plans for individual brokers and growing teams
Each plan includes a monthly record quota. Additional records are charged only after the included quota is used.
1 User
$59per month
100records per month
Register interest
2–3 Users
$99per month
300records per month
Register interest
4–10 Users
$199per month
1,000records per month
Register interest
10+ Users / Enterprise
Contact Sales
10+ usersenterprise discussion
Contact Sales
Additional usage$0.25 per additional recordafter the included monthly quota
Plans are not available for purchase until product launch
Frequently asked questions
Practical answers for broker teams
The answers below describe the planned product workflow and current owner-supplied settings.
How do I find a client’s ID later?
Files can be organised using the client name, client ID or application reference and mobile number. Search using any of those details. If the raw ID remains inside the holding period, an authorised user can access it; the sighting record and logs remain after deletion.
What happens to the uploaded file name?
The system is intended to use the client name, client ID or mobile from the upload details or file name, then show a clear display name including the document type and front, back or passport page.
What is included in the sighting record?
The record can include visible document details, sighting method and date, the user who uploaded it, AI extraction status, retention reason, deletion due date, source files and deletion status. Passport fields are included where applicable.
How long is the raw ID image kept?
The current workspace default is 12 days from upload, with no setting above 14 days. An authorised user can delete the raw image earlier when it is no longer needed.
What remains after the raw image is deleted?
The retained sighting record, register entry, retention information, deletion log and relevant activity history remain. The raw image and its thumbnail are removed from active product storage.
Can I restrict staff access?
Yes. Planned permissions separate upload, raw-image access, manual deletion, sighting-record access, log exports, user management and workspace settings.
Does SightVault decide whether a person or document is valid?
No. SightVault reads visible document fields and creates a record from the business upload workflow. It does not establish whether the person or document is valid. The business remains responsible for its own customer-identification and review process.
Launch target
Be ready when SightVault opens.
The current target to full launch is 5–8 weeks. Register for product updates or contact us about a broker, business or aggregator use case.
5–8
weeks to targeted full launch
Target timing is not a guarantee and remains subject to completion, testing and review.
Stay informed
Launch updates and business enquiries
Register for product updates or send a business enquiry. Do not include customer, applicant, ID document, account or loan-application information.