# Data retention Cell history is rich, but it does not run forever. Adrasis keeps per-cell change history for a finite window so storage stays predictable and review needs are still covered. This page tells you how long each surface keeps history and what to do when you need it longer. ## What gets retained, for how long | Surface | Retention | What it covers | | ------------------------ | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Rate history** | **3 months rolling** | Every change to a rate cell — base rates, derived rates, promotion-driven moves, partner inbounds. | | **Inventory history** | **3 months rolling** | Every change to a per-room, per-date inventory count — including booked, released, and channel-pushed updates. | | **Restriction history** | **3 months rolling** | Every change to stop-sale, CTA/CTD, min/max length-of-stay, advance-purchase windows. | | **Bookings & contracts** | **Indefinite** | Booking records and the contracts behind them are not subject to this 3-month window. They follow the contract lifecycle and your tax/accounting retention obligations. | The 3-month window is **rolling**: at the end of each calendar month, the oldest month rolls off. So on June 1st, the platform retains April 1 → May 31 (and as the month progresses, the new June entries land on top). You always have at least 60 days of cell history immediately searchable, and at most 90. ## Why three months Three months is the window where most operational review happens: * **Operator review** — *"who changed this rate last week?"* — same-day to a few weeks back. * **Partner reconciliation** — *"what was the cancellation policy on this booking date?"* — typically within the booking-to-stay gap (a month or two). * **Pricing investigations** — *"why did our average rate drop in the second half of last month?"* — covered by the most recent 30 days. Beyond that, the questions tend to shift from *"what changed in this cell"* to *"how is the platform configured today"* — answered by the live state, not by historical events. Three months also keeps storage cost predictable for every customer regardless of their event volume; it is the same window for every plan. ## What you keep forever The 3-month window applies to **per-cell change events**, not to the cells themselves or the underlying records: * **Current rate, inventory, and restriction values** — always live, never aged out. * **Bookings** — kept indefinitely (subject to your own data-retention policies). * **Contracts and rate plans** — kept indefinitely; their version history travels with the contract record. * **Properties, rooms, attributes, mappings** — kept indefinitely. * **Aggregated reporting** — long-term reporting (monthly performance, yearly comparisons) is built from rollups that survive the 3-month window. So when the cell-history timeline rolls off, you do not lose the cell — only the *trail* of micro-changes that produced its current value. ## Need it longer? Two options: 1. **Export before it ages out.** Cell history is available from the console export; moving the rolling window into your own reporting store is the safest path for customers who want a permanent record. The platform exposes a per-organization export that you can run on any cadence (daily, weekly, monthly). 2. **Extended retention add-on.** For customers with contractual or operational reasons to hold history longer, an extended retention plan is available — 12 months or 24 months. Extended retention does not change behaviour, only the window: every other surface in the platform behaves identically. Talk to your account manager to enable it; it is reflected in your service agreement. ## What this means in practice * The cell-history panel always shows you the most recent 60–90 days, depending on where you are in the month. * A reconciliation query that has to reach back further (say, a 6-month-old partner dispute) needs the export — the live console will not have it. * If your team relies on a specific lookback window, set a reminder to export at month-end, or move to extended retention. ## Where this is committed Retention is not a tunable preference — it is contractual. The exact wording lives in your service agreement; your account manager and the [Contracts](/console/contracts-and-onboarding/contracts.md) record carry it. Any change to the window for your organization goes through that contract layer, never through a console toggle. ## Where to next * **The cell-history surface itself** → [Cell history](/console/pricing-and-availability/cell-history.md) * **What contracts retain forever** → [Contracts](/console/contracts-and-onboarding/contracts.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://adrasis.gitbook.io/console/pricing-and-availability/data-retention.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.