Overview

Forge provides hosted storage capabilities that let you store data in your app installation. These storage capabilities are classified as either persistent or cache (currently in EAP).

Each installation of your app is subject to the quotas and limits of Forge' hosted storage capabilities. See Storage quotas and Storage limits for more details.

Hosted storage capabilities

Use this for long-term storage until you need to delete or overwrite the data. Forge provides the following persistent storage capabilities:

• Key-value store: lets you store data in key-value pairs.
• Custom Entity Store: lets you store data based on custom data structures specific to your app's needs and query patterns.
• Forge SQL: lets you provision dedicated SQL database instances for each customer installation. You can then use these instances to store interrelated and complex datasets as required by your app.
• Object Store (EAP): lets you store and manage large items such as substantial data objects or media files. This feature is currently available as part of Forge's Early Access Program (EAP).

These capabilities encrypt and store data on disk, optimising them for durability and persistence at the expense of performance.

Data recovery for apps with hosted storage

When a customer reinstalls an app that uses Forge hosted storage, data from the previous installation is not automatically restored. Forge hosted storage retains data for 28 days after uninstallation.

To recover this data for a customer, app developers must:

• Get customer consent to restore data.

• Submit a recovery request within 21 days of uninstallation. This is to ensure the request is processed before the 28-day retention ends.

To submit a recovery request, raise a bug ticket on Developer Support. Use Re-linking reinstallation data as the summary, and include the following in your request:

• Customer details
• Site ID
• Installation ID

See Data lifecycle for Forge-hosted storage for related details.