Market data and research subscriptions
Entitlement inventories, exchange declarations, user-level allocation and the contract terms that govern them.
Market data →Built for financial services
Your contracts say one thing.
Your consumption says another.
Nexus One connects every vendor contract to the services bought under it, the applications those services feed, and the people who actually use them — so duplicate entitlements, unmanaged renewals and out-of-profile allocations become visible before the invoice arrives.
traced
confident read
needs review
The gap
Spend controls stop at the approval. The leakage happens after it.
Your purchase workflow governs what gets bought. Almost nothing governs what happens next — and none of the following trips an approval step.
Entitlements nobody re-justifies
Licences stay allocated to people who have moved desk, changed role, or left. They renew because no one is asked to confirm they are still needed.
The same vendor, contracted twice
Regions and business units sign separately with entities that share a parent. Without resolved vendor identity, the overlap is invisible.
Terms that live only in the PDF
Geographic restrictions, derived-data rights, tiered pricing and notice periods sit in signed documents nobody reads until an audit.
Costs that move without explanation
Month-on-month changes get investigated by hand, weeks after the fact, from spreadsheets assembled out of several systems.
What Nexus One does
One connected model, from the signed page to the named user
Inventory tools hold vendors and contracts. Contract tools read clauses. Software tools map applications to users. Nexus One holds the whole chain in a single traversable graph, which is what makes the questions above answerable.
01 / GRAPH
Vendor → contract → service → application → person
Every record is a node with real edges between them. Start at a vendor and walk down to the individuals consuming it, or start at a person and walk back up to the agreement that permits it.
02 / CONTRACT TERMS
Extraction with the clause attached
Master agreements, schedules, order forms and side letters are classified, grouped into families and parsed into structured terms under the W3C ODRL schema. Each extracted field keeps a link to the sentence it came from and a confidence score.
03 / RULES
A control framework, not a dashboard
Deterministic checks run without a model call — expiry dates, duplicate assignments, required fields. Model-assisted checks handle the ones needing interpretation. Rules are saved, scheduled, versioned and re-run.
04 / REVIEW
Uncertain reads stop at a person
Anything below the confidence threshold enters a review queue rather than flowing downstream. Vendor matches, extracted terms and rule findings all carry an audit trail of who accepted what.
05 / RISK
The same graph answers a risk question
When a vendor appears in adverse media, the alert arrives attached to your exposure — the contracts it governs, the services and applications that depend on it, the people consuming them, and how much of the estate sits behind that one parent group. The monitoring is commodity. The linkage is not.
Clause extraction alone is close to commodity in 2026. The value here is what the extracted term is connected to. All four capabilities →
Where it applies
Built for market data — the hardest version of this problem
Agreements that span regions and legal entities, rights that are conditional rather than absolute, overlapping multi-year schedules, and vendor identities that fragment across a dozen names. Whichever category the spend sits in, that is the hard part.
Software, SaaS and technology services
The same graph applied to application licensing, renewals and departmental allocation — where the contract terms are simpler but the sprawl is wider.
Technology spend →Telecoms, professional services and wider indirect categories use the same data model. We would rather prove two domains properly than list six.
Deployment
It runs in your tenant. Your data does not leave it.
Nexus One deploys into your own Azure or AWS environment. Reasoning runs against a local model to limit exposure, updates are pulled by you rather than pushed to you, and your operational data stays inside the region you nominate.
- Single-tenant by design. Your graph, your environment, your access controls — not a shared multi-tenant database.
- Local model execution. Contract text and spend records are reasoned over inside your boundary.
- Client-pull updates. You decide when a new version lands. No vendor-side push into your estate.
- Your data is exportable. The graph, the extracted terms and the audit trail are yours, in your infrastructure, whatever happens to us.
Who we are
Two founders who have lived on the buying side of this problem.
Jonathan Spencer
CTO & co-founder
Architected data platforms and AI systems for financial institutions. Works on large-scale data engineering, machine learning, and building products that survive enterprise security review.
Jamie Johnston
CRO & co-founder
Commercial leader in financial services technology and data sales. Has advised banks, hedge funds and asset managers on vendor relationships and where the recoverable value in them actually sits.
Company details
Registered name
NEXUSONE AI PTE. LIMITED
Registered address
Marina Bay Financial Centre
10 Marina Boulevard, #39-010
Singapore 018983
Get in touch
Tell us what you are trying to get visibility of
A short note is enough to start — the rough scale and shape of the spend, the systems you use today, and what prompted you to look now. We will come back with a straight answer about whether Nexus One fits.
- Deployed inside your own Azure or AWS tenant.
- Security pack and DPA available before anything is shared.
- No marketing lists and no third-party trackers on this site.
Platform
A governed graph of everything you buy, and everyone who uses it
Nexus One ingests contracts, spend records, service inventories and user data, resolves them into one connected model, and runs a repeatable set of checks over it. Every finding traces back to the record — and the clause — it came from.
Layer 1 — identity
Vendors, before anything else
Nothing downstream is trustworthy while the same supplier exists five times under five spellings. Vendor resolution is the first thing Nexus One does and the thing everything else depends on.
Name normalisation and aliases
Raw vendor strings are normalised, "known as" names are mapped, and near-duplicates are surfaced for confirmation rather than merged silently.
Parent and child entities
Legal entities are rolled up to their parent, so spend concentrated across four subsidiaries reads as one relationship at negotiation time.
External reference identity
Optional PermID enrichment links internal records to an external identifier, with low-confidence matches routed to review and stale-data controls on lookups.
Layer 2 — contracts
Every term keeps its clause
Contract families are assembled automatically: master agreements with their schedules, order forms and side letters grouped under one governing document, with overlapping multi-year terms tracked side by side rather than overwriting each other.
- Classified on upload. Each file is typed as a master agreement, schedule, order form or side letter and matched to its parent.
- Structured to a standard. Rights and obligations are modelled as permissions, prohibitions, duties and constraints under the W3C ODRL schema — machine-readable, not free text.
- Source-linked. Every extracted field highlights the exact sentence it came from in the original document.
- Confidence-scored. A clean, direct read scores high; ambiguous language scores low and is marked for review before it flows anywhere.
Layer 3 — consumption
What was contracted, versus what is actually used
Contracts connect down to the services bought under them, the applications those services feed, and the individuals and cost centres consuming them. That chain is what turns an inventory into an answer.
Service catalogue
Category and data-content classification, delivery mechanism, latency, pricing and currency, geographic restrictions, and the governance and licensing fields attached to each line.
Application dependency
Which applications consume which services, and which applications depend on each other — so the impact of dropping or renegotiating a service is visible before the decision.
Named users and divisions
Service lines mapped to people, teams, divisions and cost codes, giving allocation and concentration rather than a single firm-wide total.
Interactive graph
Select, expand, focus and filter across vendors, contracts, services, applications, people and divisions. Start anywhere and traverse in either direction.
Layer 4 — controls
Rules you configure, not reports you receive
Checks are authored through a guided interface, saved, versioned, scheduled on ingest or overnight, and re-run. Deterministic validators handle anything that does not need judgement, so a date check never costs a model call. Model-assisted validators handle the rest.
| Group | Checks |
|---|---|
| Dates and renewals | Contract expiry, renewal warning windows, per-person licence expiry. |
| Value and taxonomy | Data-content taxonomy, geographic restriction compliance and completeness, contract versus summed service value, service price to contract value ratio, delivery mechanism taxonomy, regulatory data classification. |
| Data quality | Required fields present, service name and description quality, duplicate service names, duplicate service assignments per person, SLA field completeness, orphaned services, applications without a cost code, grammar and capitalisation. |
| Enrichment | Vendor catalogue taxonomy and description sync, vendor catalogue pricing checks, industry sector classification suggest-and-validate. |
Severity, scheduling and target entity are set per rule. Findings carry an audit trail of who reviewed and resolved them.
Layer 5 — reporting
What lands on a desk each month
User cost review
Period cost per person, active service lines, position against the median for their own cost centre, and month-on-month movement.
Cost movement bridge
Month-on-month change broken into added lines, dropped lines and price updates — so a rise is explained rather than investigated.
Out-of-profile detection
Services held by people whose role, department or location does not match the profile for that service, listed for manager review.
Substitute analysis
Where peers in the same taxonomy use a lower-cost equivalent, the alternative is surfaced with an estimated difference.
Peer comparison is between users inside your own cost centres. Nexus One does not publish or sell cross-firm pricing benchmarks.
Capabilities
Four capabilities, four questions
Each page below answers one question a specific person asks, states plainly what the capability does not do, and prints to a single-page PDF you can send on.
“A supplier is in the news. How exposed are we?”
Vendor risk and negative news
Adverse media alerts attached to the contracts, services, applications and users they actually affect, with concentration by parent group.
“How much are we spending with this group in total?”Vendor resolution and hierarchy
Name normalisation, alias handling, duplicate detection and parent-to-child rollup, with uncertain matches stopped at a person.
“Which of these numbers can I take to the board?”Data quality rules and controls
Configurable, scheduled, versioned checks with a severity-ordered review queue and an audit trail on every resolution.
“What are we buying, in categories I can compare?”Classification and taxonomy
Consistent classification of services and vendors by data content, delivery, latency, restriction and sector, reviewed rather than imposed.
These are capabilities. The domain pages — market data and technology spend — describe what they add up to for a specific buyer.
Capability — vendor risk
Know a vendor is in trouble before you renew with them
Adverse media alerts are a commodity. Knowing that the vendor in the headline sits behind eleven contracts, three critical applications and 140 users — and renews in nine weeks — is not.
The question it answers“A supplier is in the news this morning. How exposed are we, and what do we have to decide this week?”
- Monitors the vendors already in your graph, including parent groups and the subsidiaries that contract under them, so an alert on one legal entity surfaces exposure across all of them.
- Attaches the alert to your exposure. Contract value, renewal and notice dates, the services affected, the applications that depend on them and the people consuming them — all traversable from the alert itself.
- Shows concentration. How much of the estate sits behind a single parent group, which is the question a resilience committee asks and a vendor-by-vendor list cannot answer.
- Routes to a person. Alerts enter a review queue with an audit trail of who assessed and closed each one, rather than firing into an inbox.
What you get
A monitored vendor list drawn from your own estate, alerts linked to the contracts, services, applications and users they affect, and a concentration view by parent group — reviewable, attributable and exportable.
Sits with the vendor risk, resilience or COO function as often as with procurement. The graph is the same one used for spend; only the question changes.
Nexus One · thenexusone.ai · Know a vendor is in trouble before you renew with them
Why the timing matters
Third-party ICT risk stopped being discretionary
Since January 2025, EU financial entities have been required to maintain a register of their ICT third-party contractual arrangements, assess concentration risk before entering new arrangements, and ensure specific provisions appear in ICT contracts. The register is held at entity, sub-consolidated and consolidated level and submitted annually to the national competent authority. UK-only firms sit under the FCA and PRA outsourcing rules and the Critical Third Parties regime instead, and UK groups with EU-authorised entities are in scope for those entities.
Most of what those obligations ask for — provider identity and hierarchy, contract references and scope, service descriptions and locations, subcontractor relationships, criticality — is the same data Nexus One already holds in order to answer a spend question. Checking whether a required clause is actually present across a contract portfolio is a rule, not a project.
Nexus One · thenexusone.ai · Vendor risk
Capability — vendor resolution
One supplier, however many names it arrived under
Nothing downstream is trustworthy while the same supplier exists five times under five spellings. Vendor resolution is the first thing Nexus One does, and the thing every other answer depends on.
The question it answers“How much are we actually spending with this group, across every entity and every region?”
- Normalises raw vendor strings and maps trading names, abbreviations and ‘known as’ variants onto a single canonical record.
- Detects duplicates and near-matches and surfaces them for confirmation rather than merging them silently, so a wrong merge never propagates unnoticed.
- Resolves legal entities to their parent, so spend spread across four subsidiaries reads as one relationship at the point where you negotiate it.
- Links to an external identifier through optional PermID enrichment, with cached corporate hierarchy, stale-data controls and low-confidence matches routed to review.
- Tracks unresolved cases as issues with a workflow state, so a vendor with an open question can be blocked from downstream reporting until it is settled.
What you get
A canonical supplier list with parent and child relationships, spend and contract counts rolled up to group level, duplicate contracts and overlapping services surfaced as findings, and an audit trail on every match decision.
This is the layer that makes negotiation leverage, concentration risk and duplicate detection possible at all. It is also the least visible work in the product.
Nexus One · thenexusone.ai · One supplier, however many names it arrived under
Capability — data quality
Know which numbers you can take to the board, and which you cannot
A dashboard tells you what the data says. A control framework tells you whether the data is worth reading. Nexus One runs configurable, scheduled, versioned checks and shows you what failed.
The question it answers“Before I present this, what in it is incomplete, stale or contradictory?”
- Rules you author and own. Templates for dates and renewals, value and taxonomy, core completeness, and enrichment — each with a target entity, parameters, severity and schedule.
- Deterministic first. Anything not requiring judgement runs as coded logic, so an expiry check never costs a model call. Model-assisted validators handle only what needs interpretation.
- Scheduled on ingest or overnight, with last-run status, saved configurations, and backup and restore of the rule set.
- Findings, not noise. Alert counts roll up by vendor, contract, service and application, and each finding carries the record it came from and the person who resolved it.
What you get
A live issue count across the estate, a queue ordered by severity, a per-record view of what failed and why, and a rule set you can version, review and re-run on demand.
Usually the first thing that earns trust internally, because it is checkable. It is also the honest answer to ‘how do we know the AI got it right’.
Nexus One · thenexusone.ai · Know which numbers you can take to the board, and which you cannot
Capability — classification
Compare like with like, across a portfolio that was never labelled consistently
Peer comparison, substitute analysis and out-of-profile detection all rest on one thing: services classified consistently enough that two records can be judged against each other.
The question it answers“What are we actually buying, in categories I can compare across desks and regions?”
- Classifies services by category and data content, delivery mechanism, latency, pricing basis and currency, and geographic and regulatory restrictions.
- Classifies vendors by industry sector, with suggest-and-validate against reference data rather than a free-text field.
- Enriches from evidence. Proposals draw on public and licensed reference sources and on your own procurement documents, with your documents treated as the more authoritative where they disagree.
- Keeps the human in the loop. Every proposed classification is accepted or rejected by a person, and taxonomy drift is itself a rule that can be checked.
What you get
A consistently classified service catalogue, comparable across desks and regions, that makes peer benchmarking within your cost centres, substitute identification and out-of-profile detection possible.
The least glamorous capability and the one everything else depends on. Without it, ‘cheaper alternative’ and ‘out of profile’ have no meaning.
Nexus One · thenexusone.ai · Compare like with like, across a portfolio that was never labelled consistently
Market data
Where does your market data spend actually go?
Entitlements sit with people who have changed desk. The same exchange is contracted through four subsidiaries. Restrictions live in a PDF nobody opens until an audit. Nexus One was designed against this problem first.
Why this domain is hard
Market data is the worst case, which is why we started there.
Entitlements are per person
Cost attaches to named individuals and specific devices, not to a department line. Firm-level totals hide almost everything that matters.
Vendors fragment
One exchange group can appear as a dozen legal entities across regions. Without resolution, concentration and overlap are both invisible.
Rights are conditional
Geographic restrictions, display versus non-display use, derived-data creation and redistribution limits are all contractual conditions, not attributes.
Terms overlap
Initial terms, renewal terms and successive multi-year schedules run concurrently. Flattening them loses the history you need at renewal.
What it produces
Four questions, answerable on demand
Who holds what, and should they?
Every service line mapped to a named user, with their position against the median for their own cost centre and a flag where the service does not match their role, department or location.
What are we paying twice for?
Vendor entities resolved to their parent, contracts grouped by family, and duplicate service assignments across regions and business units surfaced as findings rather than left to be noticed.
What is coming up, and on what terms?
Expiry and renewal windows tracked from the extracted contract terms, with auto-renewal clauses and notice periods carried through from the signed document.
Why did the number move?
Month-on-month change split into added lines, dropped lines and price updates, at firm, cost-centre and individual level.
Sizing it honestly
We build the case at one-tenth of the upper bound
Published research puts procure-to-pay and post-signature leakage in a wide band of roughly two to eight per cent of contract value. We do not build business cases at the top of that range, or at the middle of it.
Our default target is 0.8 per cent of addressed spend — one-tenth of the upper bound — and every figure we put in front of you is derived at that level, against your own numbers, with the arithmetic shown.
- Your spend, not a benchmark. The recovery estimate is calculated from the extract you provide.
- Days saved every month from your reporting burden. The manual compilation cycle the reporting replaces, costed at your own blended rate rather than an industry average.
- Assumptions visible. Analyst count, hourly rate and addressed spend are inputs you can change, not numbers baked into a slide.
Leakage ranges cited from published industry research. We will share the sources and their limitations rather than presenting them as our own findings.
Alongside what you already run
The connective layer over your existing systems
Most firms of any size already run a market data inventory or expense management platform, often with a managed service attached. Nexus One sits on top of it and keeps working with it.
What it adds is the layer those systems were not built for: contract terms structured to a standard and traceable to their clause, linked through services and applications down to the individual, and checked continuously by rules you control.
Technology spend
The same model, applied to software and technology services
Application licensing, renewals and departmental allocation follow the same shape as market data: an agreement, the services bought under it, the systems they feed, and the people holding seats. The contract terms are simpler. The sprawl is wider.
What carries over
Nothing about the data model changes
A software vendor is a vendor. A licence agreement is a contract family. A subscription tier is a service. A seat is a person. The graph does not care which category the spend sits in, which is why the second domain cost us a taxonomy rather than a rebuild.
Renewal exposure
Auto-renewal clauses, notice periods and expiry dates extracted from the agreements themselves, with the source clause attached to each date.
Overlapping tools
Vendors resolved to parents and services classified by function, so two products doing the same job across two business units become one finding.
Seats nobody uses
Licences mapped to named holders and cost centres, with allocations that do not match a person's role or department flagged for review.
Where we focus
The contractual layer, in a controlled estate
In a regulated firm, procurement is centralised and the estate is locked down. Discovering unknown applications matters less than governing the ones you have already signed for.
That is where Nexus One works: what the agreement actually permits, which entity it covers, when it renews, and whether the allocation still matches the person holding it — all traceable back to the clause it came from.
WHERE WE FOCUS
The contractual layer
What the agreement permits, which legal entity it was signed with, what it obliges you to do, when it renews and on what notice — connected through the services and applications it covers to the individual holding the licence, inside an environment where the data does not leave your tenant.
A note on continuity
Your estate should not depend on our survival
In August 2026 a well-established SaaS management platform announced it was shutting down, giving customers four days to export their application inventory, spend records and contracts before the service ended. That is a structural risk in any multi-tenant model, and it is not one you can diligence your way out of.
Nexus One runs inside your own cloud tenant. The graph, the extracted contract terms and the audit trail live in your infrastructure, in a database you control. If we disappear tomorrow, your data does not go anywhere.
Security & deployment
Your contracts and your entitlement data never leave your environment
Nexus One is deployed as a single-tenant application inside your own Azure or AWS environment. This page is written for the people who will review it before a first meeting is agreed.
Architecture
How the deployment is structured
Single tenant, your cloud
The application and its graph database are deployed into your subscription, in the region you nominate. Your operational data is not pooled with any other client's.
Local model execution
Reasoning over contract text and spend records runs against a model inside your boundary. The rules engine uses deterministic logic and fuzzy matching first, so a large share of checks involve no model call at all.
Client-pull updates
New versions are pulled by you when you choose. There is no vendor-initiated push into your environment.
Role-based access
Read-only and administrative roles, with review and resolution actions attributed to the user who took them.
Secret handling
Configuration and credentials handled through platform-native secret management, with managed identity where the deployment pattern supports it.
Your own procurement files ranked first
Where internal documents and external reference material disagree, your signed documents are treated as the more authoritative source.
Vendor intelligence
Where reference data comes from
Service taxonomies, vendor descriptions and classification data are assembled from publicly available and licensed sources, and from the procurement documents you provide. Enrichment is delivered to your environment as a catalogue and taxonomy update.
- Your data is not the product. Client operational data is not used to build shared reference data, and is never exposed to another tenant.
- Enrichment is one-directional. Catalogue updates flow in. Your contracts, spend and user records do not flow out.
- Suggestions are reviewable. Enrichment proposes values; a person accepts or rejects them, and the decision is recorded.
Due diligence
What we can send your security team
A security pack, our data processing agreement and a completed due diligence questionnaire are available on request, before any data is exchanged. If your team works from its own questionnaire, send it over and we will complete that instead.
Contact
Tell us what you are trying to get visibility of
A short note is enough to start. We will come back to you with a straight answer about whether Nexus One fits what you are dealing with.
Get in touch
We would rather have a specific conversation than a generic one.
Useful things to include: the rough scale and shape of the spend, the systems you use today, and what prompted you to look now.
We use what you send here to reply to you and nothing else. No marketing lists, no third-party trackers on this site.
Blog & News
Notes from the team
What we are learning about procurement data, spend visibility, and applied AI in financial services.
Coming soon
We are preparing our first posts. In the meantime, follow Nexus One AI on LinkedIn for company news and updates, or get in touch directly.
Privacy
Privacy Policy
Effective from: 30 April 2026
Last updated: 30 April 2026
This Privacy Policy explains how NEXUSONE AI PTE. LIMITED (“Nexus One AI”, “we”, “us” or “our”) collects, uses, stores and protects personal information when you visit or interact with this website.
We respect your privacy and are committed to handling personal information responsibly and in accordance with applicable data protection laws, including the Singapore Personal Data Protection Act 2012 (PDPA), where applicable.
1. Information We Collect
Depending on how you interact with our website, we may collect the following types of personal information:
Information you provide to us
You may voluntarily provide personal information when you:
- contact us through the website;
- request information about Nexus One AI or our services;
- submit an enquiry or other communication;
- subscribe to communications or marketing materials; or
- otherwise communicate with us.
This information may include your name, job title, company, email address, telephone number and any other information you choose to provide.
Information collected automatically
When you visit our website, certain technical information may be collected automatically, including:
- IP address;
- browser type and version;
- device type;
- operating system;
- pages visited;
- referring website;
- approximate location derived from your IP address;
- date and time of visits; and
- information about how you interact with the website.
This information may be collected through cookies, analytics tools and similar technologies.
2. How We Use Personal Information
We may use personal information to:
- respond to enquiries and requests;
- provide information about Nexus One AI, our products and services;
- communicate with you;
- manage business relationships;
- improve and develop our website, products and services;
- understand how visitors use our website;
- monitor website security and prevent fraud or misuse;
- comply with applicable laws and regulatory requirements; and
- carry out other legitimate business purposes.
Where required by applicable law, we will obtain your consent before using your personal information for a particular purpose.
3. Marketing Communications
If you choose to receive marketing or other communications from us, we may use your contact information to send you information about Nexus One AI, our products, services, events and other business developments.
You may opt out of marketing communications at any time by using the unsubscribe mechanism provided in the communication or by contacting us directly.
We will not require you to provide personal information for marketing purposes as a condition of using this website.
4. Cookies and Similar Technologies
Our website may use cookies and similar technologies to enable functionality, understand website usage, improve performance and, where applicable, support marketing activities.
Cookies are small text files placed on your device when you visit a website.
We may use:
- Essential cookies, which are necessary for the website to operate;
- Analytics cookies, which help us understand how visitors use the website; and
- Preference or marketing cookies, where applicable, which may be used to remember preferences or support relevant communications and advertising.
You can control or disable cookies through your browser settings. Disabling certain cookies may affect the functionality of the website.
Where required by applicable law, we will obtain consent before placing non-essential cookies on your device.
5. Third-Party Services
We may use third-party providers to operate, analyse or support our website. These providers may process personal information on our behalf.
Examples may include providers of:
- website hosting;
- analytics;
- email and communications;
- security and fraud prevention;
- customer relationship management; and
- other website functionality.
We expect relevant third-party providers to handle personal information in accordance with applicable privacy and data protection requirements.
This website may also contain links to third-party websites. We are not responsible for the privacy practices or content of those websites. We recommend reviewing their privacy policies before providing them with personal information.
6. Disclosure of Personal Information
We may disclose personal information to:
- our employees, officers and authorised representatives;
- service providers and contractors who assist us in operating our business or website;
- professional advisers, including legal, accounting and financial advisers;
- regulators, government authorities or law enforcement agencies where required or permitted by law; and
- parties involved in a corporate transaction, such as a merger, acquisition, restructuring or sale of assets.
We do not sell personal information collected through this website.
7. International Transfers
Some of our service providers or business operations may be located outside Singapore. As a result, personal information may be transferred to or processed in other countries.
Where personal information is transferred outside Singapore, we will take reasonable steps to ensure that the information receives a standard of protection comparable to that required under applicable Singapore data protection law.
8. Retention of Personal Information
We retain personal information only for as long as reasonably necessary for the purposes for which it was collected, or as required by applicable law.
The appropriate retention period will depend on the nature of the information and the purpose for which it is used.
When personal information is no longer required, we will take reasonable steps to delete, anonymise or securely dispose of it.
9. Security
We take reasonable administrative, technical and organisational measures to protect personal information against unauthorised access, collection, use, disclosure, copying, modification, disposal or similar risks.
However, no website, transmission over the internet or electronic storage system can be guaranteed to be completely secure.
10. Your Rights and Choices
Subject to applicable law, you may have rights to:
- request access to personal information we hold about you;
- request information about how your personal information has been used or disclosed;
- request correction of inaccurate or incomplete personal information;
- withdraw consent to certain uses of your personal information; and
- make a complaint about how we handle your personal information.
Withdrawal of consent does not affect the lawfulness of processing carried out before consent was withdrawn.
We may need to verify your identity and the nature of your request before responding.
11. How to Contact Us
If you have a question, request or complaint concerning this Privacy Policy or our handling of personal information, please contact us:
NEXUSONE AI PTE. LIMITED
Marina Bay Financial Centre, 10 Marina Boulevard, #39-010, Singapore 018983
Email: jamie.j@thenexusone.ai
We will consider and respond to privacy-related enquiries within a reasonable period and in accordance with applicable law.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes to our business, website, technology or legal requirements.
The latest version will always be published on this website, together with the date it was last updated.
Your continued use of the website after an updated Privacy Policy has been published will constitute acknowledgement of the updated policy, to the extent permitted by applicable law.
© 2026 NEXUSONE AI PTE. LIMITED. All rights reserved.
Terms
Website Terms of Use
Effective from: 30 April 2026
Last updated: 30 April 2026
These Terms of Use (“Terms”) govern your use of the website operated by NEXUSONE AI PTE. LIMITED (“Nexus One AI”, “we”, “us” or “our”).
By accessing or using this website, you agree to these Terms. If you do not agree with them, please do not use the website.
1. About This Website
This website provides information about Nexus One AI, our business, products, services and areas of expertise.
The information on this website is provided for general informational purposes only and does not constitute professional, financial, legal, accounting, investment or other professional advice.
2. Use of the Website
You may use this website for lawful purposes and in accordance with these Terms.
You must not:
- use the website for any unlawful, fraudulent or malicious purpose;
- attempt to gain unauthorised access to the website or its systems;
- interfere with the operation, security or availability of the website;
- introduce viruses, malicious code or other harmful material;
- copy, reproduce, modify or distribute website content without our permission; or
- use automated systems to scrape, extract or collect content from the website without our prior written consent.
3. Intellectual Property
Unless otherwise stated, all content on this website, including text, graphics, logos, designs, images, software, trademarks and other materials, is owned by or licensed to Nexus One AI and is protected by applicable intellectual property laws.
You may view and use the website for your own legitimate informational purposes.
You must not reproduce, modify, distribute, publish, sell or commercially exploit website content without our prior written permission.
Nexus One AI, together with our logos, names and associated branding, are trademarks or business names of Nexus One AI or its licensors. No rights are granted to use them without our prior written consent.
4. Information on the Website
We aim to keep the information on this website accurate and up to date. However, we do not guarantee that all information is complete, accurate, current or free from errors.
We may change, update or remove content from the website at any time without notice.
Any descriptions of products, services, capabilities, performance or potential outcomes are provided for general information and do not constitute a guarantee of future results.
5. Third-Party Websites and Services
This website may contain links to websites, platforms or services operated by third parties.
These links are provided for convenience only. Nexus One AI does not control and is not responsible for the content, availability, security or practices of third-party websites or services.
Your use of third-party websites is subject to their own terms and policies.
6. Website Availability
We aim to keep the website available and functioning properly, but we do not guarantee that it will always be available, uninterrupted, secure or free from errors or defects.
We may suspend, withdraw or modify the website or any part of it without notice.
7. Limitation of Liability
To the maximum extent permitted by applicable law, Nexus One AI will not be liable for any loss or damage arising from or in connection with your use of, or inability to use, this website or reliance on information provided through the website.
This includes, without limitation, indirect or consequential loss, loss of profits, revenue, business opportunities, data or goodwill.
Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited under applicable law.
8. Privacy
Your use of this website may involve the collection and processing of personal information.
Our handling of personal information is described in our Privacy Policy.
9. Changes to These Terms
We may update these Terms from time to time.
Any updated version will be posted on this website with a revised “Last updated” date. Your continued use of the website after changes are posted constitutes acceptance of the updated Terms.
10. Governing Law
These Terms are governed by the laws of Singapore.
Any disputes arising out of or in connection with these Terms or your use of this website will be subject to the exclusive jurisdiction of the courts of Singapore.
11. Contact Us
If you have any questions about these Terms, please contact us at:
NEXUSONE AI PTE. LIMITED
Marina Bay Financial Centre, 10 Marina Boulevard, #39-010, Singapore 018983
Email: jamie.j@thenexusone.ai
© 2026 NEXUSONE AI PTE. LIMITED. All rights reserved.