Data ownership

Built so you can leave.

A platform should earn the right to keep your business. It should not trap it.

Beaver gives operators a Live console export of the core operating data created inside the platform.

Your business stays yours.

Boab carrying a stack of folders labelled ideas, plans, projects and results.

The principle

Lock in should not be the retention strategy.

Software companies sometimes make leaving difficult because it makes staying easier. We think that is backwards.

If Beaver is useful, operators should stay because the platform works for them. Not because their customer records are stuck inside it.

  • We would rather give you a reason to stay than a reason you cannot leave.

What can be exported

The operating record.

Live The console supports full export of players, orders, entries, draws and audit logs.

That is not a decorative "download CSV" button representing one table. It is the core operating data that describes what happened on the platform.

Export operating data
  • PlayersExport
  • OrdersExport
  • EntriesExport
  • DrawsExport
  • Audit logExport

Your data. Your file. Taken from the console, not requested from a supplier.

Illustration of the export list. The five data sets shown are the ones the console exports today.

  • Players

    Take the customer relationship with you.

    Player exports matter because the customer relationship is the asset the operator is building. The platform should not turn that relationship into somebody else's moat.

  • Orders and entries

    Keep the commercial record.

    Who bought, what they entered, which competition each entry belonged to and how the operating record was constructed. That history matters for migration, analysis and dispute handling.

  • Draws

    Keep the result record too.

    A competition business should retain the record of how historic competitions concluded, rather than losing it simply because the platform changes.

  • Audit logs

    Take the evidence.

    Audit records are part of the exportable operating data, so the history of sensitive administrative actions does not have to disappear with the platform.

    The history belongs with the business that created it.

What about the API?

Not ready to sell.

Beaver contains API tokens and webhook architecture as Built capabilities. The public REST API is currently broken and is not part of the commercial proposition. So we do not say:

  • Open API
  • Connect any CRM
  • Real time third party data access

We will, once that capability is fixed and verified.

Export is live. Public API is not.

Migration

Data ownership matters most when you need to move.

The ability to export operating data is one half of platform mobility. The other half is understanding how that data maps into the next system. A Beaver migration conversation covers:

  • Customer records
  • Orders and entries
  • Historic draws
  • Consent state and account status
  • Operational history
  • Domain and storefront cutover

We do not promise perfect automated migration from every competitor. Those paths have to be built and tested first.

Privacy and deletion

Ownership does not remove responsibility.

The product contains Built workflows for data export and deletion handling at player level.

Operators still need to understand their own obligations around retention, deletion and lawful processing. More in the Trust Centre.

Your data

Take it with you.

If Beaver deserves to keep the operator, the product should prove it every month.