If Roiva went away: what you keep

Your AI ROI record shouldn't depend on any vendor, Roiva included. If Roiva stopped running, you'd keep what you had already taken out of it. Its pages, its API and its export button would go with it. This page lists what each copy holds, so you can decide what to keep on your side and how often.

Two copies you can hold

• The reporting tables, every night. On a plan that includes API access, Roiva builds its figures as Parquet files at 07:00 UTC each night. Your warehouse loads them, or Roiva writes them to an S3 bucket you own. They're typed tables with a published schema, so once they're in your warehouse you query them without Roiva. They hold the reported figures and the evidence behind them, not the whole account. See Roiva's figures in Power BI and your data warehouse.
• The full-account export, weekly or when you ask for it. On every plan, an Owner or Admin can download one ZIP of CSVs holding the account's record as the table below lists it, with the uploaded documents and the records synced from each connection. Roiva deletes a downloaded export from its side after seven days. On a plan that includes API access, Roiva can also write the same export to your S3 bucket every Sunday, once an Owner or Admin turns that on for the bucket. Without that, the copy you hold is the last one you downloaded. See Your data: exports and deletion.

A copy counts only once it's on your side: in your warehouse, in your bucket or in your files. A Power BI report that reads the tables from Roiva's address keeps only what its last refresh imported.

What each one holds

Part of the record	Reporting tables (nightly)	Full-account export (weekly, or when you ask)
Initiatives: stage, owner, business case	Yes	Yes, with notes, activity and pauses
Sample initiatives, which hold made-up figures for a demonstration	No	Yes, marked in the "Sample data" column of initiatives/initiatives.csv
Costs, and where each came from	Yes	Yes, with allocation rules, the bills they split and the records synced from each connection
Value entries	Approved entries only	Every status, drafts and rejected entries included
The formula behind each calculated figure: its key, and the version and expression it was computed with	Yes	Yes, with every version Roiva has kept of each formula
The inputs frozen with each figure	Yes, whole, and split one row per input for a calculated figure	Yes, whole
Metric readings and baselines, with how each baseline was arrived at	The ones an approved figure used	All of them
Assumptions	The figure each approved entry used, with the date it took effect	Every dated figure the account has set
Approvals: who decided, when, at which step, and why	Yes	Yes, with each initiative's approvers and delegations
Locked and reopened months	Yes	Yes, with journals
Budgets, every version	Yes, with budget against spend	Yes
Portfolio decisions, with the figures each was taken on	Yes	Yes
Measurement charters, every version, and the charter each value entry was counted under	No	Yes
The audit log	No	Yes, every row
Supporting documents	Which documents each approved figure cites. An SOW's or a contract's title is left out	The uploaded files, and the address of any document held as a link

A calculated figure keeps the expression it was computed with and the value of each input it used, so it can be checked without Roiva. A synced figure keeps what the sync counted, and a typed-in figure keeps who entered it and who approved it. In the reporting tables, reported_totals holds Roiva's own totals for every quarter and year: cash value, freed capacity and cost, kept apart. Rebuilding them from reported_value and costs over the same dates, the way Reporting tables describes, gives them to the cent. Roiva won't publish a build where it doesn't.

What neither one holds

• A formula's changes from before Roiva kept versions. Until then a formula was edited in place. Each figure from that time still records the expression it was computed with, but an expression replaced before any figure used it isn't kept.
• Roiva's shared library. Default formulas, assumptions and metric definitions belong to Roiva. The value of any default a figure used is frozen in that figure's inputs. A formula your initiative took from the library is a copy, and it's in the export.
• Credentials and conversations. Integration secrets, access tokens and Assistant chats are never in either copy.
• What Roiva drafted initiatives from. Answers to the pre-signup assessment, and the runs in which Roiva read your documents to suggest initiatives, aren't exported. The initiatives they produced are, and so are the documents.
• Roiva's software. You keep the record and the arithmetic, not the product: there's no Roiva to run your copy in.

If you lose access, and Roiva is still here

If nobody in your organization can sign in any more, because every member was removed or the only Owner left, write to security@roiva.ai. Roiva staff can generate the same full-account export for you. The request and every download are recorded in your account's audit log with the reason given, every Owner is emailed, and the file is deleted from Roiva after 30 days.

Keeping a complete copy

1. Turn on the reporting tables and load them into your warehouse every night, or have Roiva write them to your own bucket.
2. Turn on the weekly full-account export for that bucket, or download the export on a schedule of your own, such as each quarter's close, and keep it with your finance records. It covers what the tables leave out: entries not yet approved, the audit log, the documents themselves.

Next

• Reporting tables lists every table and column.
• What makes a figure auditable covers versions, frozen inputs and approval.