> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/salesforce-b2c-link-cartridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/salesforce-b2c-link-cartridge/1.0-2/operations-and-maintenance.md).
# Operations and maintenance
## Data storage
Outside of Commerce Cloud, Digital River API stores Customer, Order, and SKU data across three areas:
| | SOC Compliant | PCI Compliant |
| ---------------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------- |
| CPG Payments | 
| 
|
| Commerce engine for Global Commerce (GC) | 
| 
|
| Payments Service (PC) | |  |
The location is Elastic Search, Oracle, and Cassandra, and the duration is a maximum of 10 years for Customer Data and Order Data except for the EU “Right to be forgotten” GDPR requirements, which we support.
## Availability
Services should always be available.
If services are not available, orders and payments cannot be processed.
A provided Business Manager extension cartridge will give real-time status on available services by sending a static request and evaluating the response code sent back to SFCC.
DigitalRiver.js and Digital River API are available globally. Digital River API is available via all three of Digital River’s data centers – Virginia, Oregon, and Ireland. Our load balancers handle fallback.
Digital River’s general availability goal is to respond in 800 ms or less within the Digital River network. The roundtrip response time, which includes external networks, may vary (as expected).
Monitoring with Zabbix is in place, and the Digital River Operations team has logging and notifications in place; Digital River customer-facing teams have access to that data.
## Failover/Recovery process
If there is a service disruption, it will impact the ecommerce experience in the following ways:
1. Payment Methods will not render in the cart during checkout.
2. Tax calculations will not return to the cart.
3. Overall customers will be unable to transact on the ecommerce store, which is leveraging Digital River for tax, payments, and risk.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.digitalriver.com/salesforce-b2c-link-cartridge/1.0-2/operations-and-maintenance.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.