---
title: Customizing storage used by the DaVinci module
description: PingOne Android iOS
component: orchsdks
page_id: orchsdks:davinci:customization/storage/index
canonical_url: https://developer.pingidentity.com/orchsdks/davinci/customization/storage/index.html
revdate: Tue, 25 Mar 2025 11:00:37 +0100
keywords: ["PingOne Advanced Identity Cloud", "PingAM", "Journeys", "Setup & Configuration", "Source Code", "Use Case", "SDK", "IdP"]
section_ids:
  next_steps: Next steps
---

# Customizing storage used by the DaVinci module

[icon: circle-check, set=far]PingOne [icon: android, set=fab]Android [icon: apple, set=fab]iOS

Depending on the authentication use case, you may need to store and retrieve ID tokens, access tokens, refresh tokens, or cookies.

Each token is serving a different use case, and as such how you handle them can be different.

The Orchestration SDKs employ identity best practices for storing data by default. However there are use cases where you might need to customize how the SDK stores data.

For example, you might be running on hardware that provides specialized security features, or perhaps target older hardware that cannot handle the latest algorithms.

For these cases, you can customize the provided storage solutions, or provide your own custom storage classes.

## Next steps

Learn how you can customize the provided storage solutions, or provide your own custom storage classes.

[icon: android, set=fab, size=3x]

#### [Android](customize-android-storage.html)

Customizing storage used by the DaVinci client for Android

[icon: apple, set=fab, size=3x]

#### [iOS](customize-ios-storage.html)

Customizing storage used by the DaVinci client for iOS