What is the difference between a data asset and a database?

A data asset is the dataset itself — the information content. A database is the structured container that organises the data — the schema, indexes, query architecture, and software infrastructure. The data asset is the substance; the database is the engineering. Two businesses with the same underlying data can have very different database value depending on the architecture.

What is a UK database right?

The UK database right is a sui generis intellectual property right under the Copyright and Rights in Databases Regulations 1997 (SI 1997/3032). It protects databases that show "substantial investment in obtaining, verifying, or presenting the contents". The right lasts 15 years from creation or substantial change, can be renewed by substantial change to the database, and is distinct from copyright in the database structure or IP in the underlying data.

How long does a UK database right last?

15 years from creation. Substantial change to the database — substantial investment in obtaining, verifying, or presenting new contents — resets the clock, providing a further 15 years of protection. Continuously maintained databases can have indefinite protection in 15-year increments.

Do US businesses have database rights?

No. The US does not have a sui generis database right equivalent. US database protection relies on copyright in the structure (where original creative expression exists), contract law (terms of use), and trade-secret protection. UK and EU businesses operating across the Atlantic need to plan for the asymmetry — the database right protection in the UK/EU does not extend to US operations.

How is a data asset valued in an acquisition?

Three methods are common. Cost approach — reproduction cost of building the dataset, less obsolescence; the dominant method for early-stage datasets. MPEEM — where the data is the primary cash-flow driver. RFR — where comparable data-licensing royalty rates exist. The choice depends on the data type, evidence availability, and audit defensibility requirements.

Can I capitalise data I have collected myself?

Generally no. Internally generated data assets fall under the IAS 38 paragraph 63 prohibition (alongside brands and customer lists) because the cost cannot be reliably distinguished from the cost of operating the business. The exception is where the data meets the strict IAS 38 paragraph 57 development-cost criteria, which is uncommon for general data accumulation. Acquired data, however, is recognised at fair value.

How does GDPR interact with data-asset valuation?

GDPR (UK GDPR and EU GDPR) imposes a lawful-basis requirement on processing personal data. A data asset whose lawful basis is consent that can be withdrawn at any time has a different useful-life profile than one whose lawful basis is contract or legitimate interest. The lawful-basis review is a standard step in M&A diligence and impacts the useful-life assessment for amortisation.

Can database rights be licensed?

Yes — database rights can be licensed under contract law, with the licensor retaining the underlying right and the licensee acquiring contractual permission to extract or re-utilise the database. Licence agreements over database rights are common in B2B data publishing and aggregator businesses. The licence itself is a separate intangible asset on the licensee's side.

Accounting Framework

Data Asset vs Database vs Data Rights

Data asset vs database vs data rights — what each is in intangible-asset terms, how UK database right works, and how SaaS founders value the data layer.

Three data-related intangibles sit close together in modern SaaS businesses and are routinely conflated: the data asset (the underlying data), the database (the structured container), and the database right (the UK/EU sui generis legal protection under SI 1997/3032 transposing EU Directive 96/9/EC). They are not the same. The taxonomy matters because the accounting recognition, the valuation method, and the legal protection differ across all three. A complete intangible-asset inventory identifies each layer separately.

Criteria	Data Asset	Database and Database Right
What it is	The dataset itself — the substance	Database: the structured container — schema, indexes, query architecture. Database right: UK/EU sui generis legal right over substantial-investment databases
Form	Information content	Database: software architecture and engineering. Database right: statutory legal right
Standard/legal reference	IAS 38 (intangible asset)	Database: IAS 38 / SIC-32. Database right: UK SI 1997/3032; EU Directive 96/9/EC
Geographic scope	Universal (subject to GDPR / privacy regime)	Database: universal. Database right: UK and EU only
Term	Indefinite (subject to refresh and obsolescence)	Database: 3-7 year software lifecycle. Database right: 15 years from creation or substantial change
Renewal	Continuous refresh extends useful life	Database: maintenance and re-architecture extend useful life. Database right: substantial change resets the 15-year clock
Internally generated recognition	Generally prohibited under IAS 38 paragraphs 63-67	Database: capitalisable from application-development stage under SIC-32. Database right: recognised where contractual/legal basis met
Acquired recognition	Fair value under IFRS 3 / ASC 805	Fair value under IFRS 3 / ASC 805
Typical valuation method	Cost approach, MPEEM, RFR	Database: cost approach (dominant). Database right: RFR, cost approach, income via competitive differential
What gives it value	Informational content, completeness, freshness	Database: architecture quality, query performance, scalability. Database right: legal exclusion right
Loss scenarios	Data corruption, breach, GDPR consent withdrawal	Database: technology obsolescence. Database right: 15-year expiry without substantial change
GDPR / privacy interaction	Direct — lawful basis required, data subject rights apply	Indirect for database; direct for database right (coexists with GDPR, does not displace it)
Tax treatment (UK)	Intangible Fixed Assets regime where capitalisable	Same — IFA regime for capitalised database costs and database right
IP-backed lending	Limited — depends on transferability and lawful basis	Database: limited — bespoke architecture difficult to collateralise. Database right: modest — recognised collateral in UK/EU

When to Use Each Approach

Data Asset

Inventory of acquired customer-behaviour, transactional, or operational data
Cost-approach valuation of internally accumulated datasets at point of acquisition
MPEEM application where data is the primary cash-flow driver
RFR where comparable data-licensing rates exist

Database and Database Right

Capitalisation of internally developed database engineering under SIC-32
Acquired database fair-value attribution in PPA
Sui generis database-right recognition where substantial investment is evidenced
Post-acquisition continuity planning for substantial-investment activity

Our Verdict

Most modern SaaS businesses hold all three intangibles but conflate them in fundraising and M&A narratives. The inventory should identify each separately: the dataset's informational value, the database's engineering value, and the database right's legal-exclusion value. All three are typically internally generated (prohibited from balance-sheet recognition) but recognised at fair value when acquired.

Related Glossary Terms

Learn More

View lesson →

Ready to Value Your Intangible Assets?

Use Opagio's valuation tools to apply these methods to your own business.

Try the Valuator Browse All Comparisons

Data Asset vs Database vs Data Rights

When to Use Each Approach

Data Asset

Database and Database Right

Our Verdict

Related Glossary Terms

Learn More

Related Comparisons

IFRS 3 vs ASC 805: PPA Standards Compared

IAS 38 vs ASC 350: Intangible Asset Standards

CHS Framework vs IFRS 3 Classification

Ready to Value Your Intangible Assets?