diff --git a/configuration/maestro-versions.md b/configuration/maestro-versions.md
index e58c97a..1bce7e9 100644
--- a/configuration/maestro-versions.md
+++ b/configuration/maestro-versions.md
@@ -38,3 +38,23 @@ dcd cloud ... --maestro-version 2.1.0
 # Always use the most recent version of Maestro available
 dcd cloud ... --maestro-version latest
 ```
+
+## Maestro Support Policy
+
+We will always aim to support the latest versions of Maestro and additionally continue to provide support for previous versions. Our policy for this is as follows:
+
+- We will always add support for new versions.
+- Once a new minor version has been released (i.e. 2.x.0), we'll mark all previous patches of the previous minor (i.e. 2.6.x) bar the latest as deprecated.
+- Once a minor version is five versions old, we'll mark it as deprecated.
+- Once a version reaches below 1% usage, we'll mark it as deprecated.
+- Deprecated versions are then removed after six weeks provided total usage is less than 0.5%.
+
+{% hint style="info" %}
+For example, Maestro 2.0.0 received 10 patch releases (2.0.1 -> 2.0.10) and we would provide support for all of them. Once Maestro 2.1.0 released, we would then remove support for 2.0.0 -> 2.0.9 and retain 2.0.10.
+
+Once Maestro 2.5.0 is released, we would then mark 2.0.10 as deprecated unless usage dropped below 1% before then.
+{% endhint %}
+
+We may change the default version from time to time and we will always provide at least 30 days of notice before changing the default version.
+
+We will also always aim to provide at least 30 days of warning before removing support for previous Maestro versions.
\ No newline at end of file
diff --git a/getting-started/devices-configuration.md b/getting-started/devices-configuration.md
index a319773..8bb136f 100644
--- a/getting-started/devices-configuration.md
+++ b/getting-started/devices-configuration.md
@@ -88,3 +88,46 @@ The flags above set the device for the whole upload. When only one flow needs a
 ### Running your suite across several devices
 
 To run every flow against several devices from a single `dcd cloud` invocation use a [device matrix](../configuration/device-matrix.md).
+
+## Device Support Policy
+
+We aim to provide a wide range of devices and OS versions so that you can test your apps as thoroughly as you need. However, due to storage constraints we can only provide access to certain devices and OS levels. Our policy on this is written below so you know what to expect. 
+
+If you need a device or OS that we don't currently offer, please feel free to reach out to support on [Discord](https://discord.gg/gm3mJwcNw8) or Slack (Enterprise customers only) or via email at [support@devicecloud.dev](mailto:support@devicecloud.dev) and we'll see what we can do.
+
+### iOS Support Policy
+
+We will always aim to have the following devices available as a baseline:
+
+- The latest even-numbered iPhone model & it's variations, i.e. iPhone 18, 18 Plus, 18 Pro & 18 Pro Max.
+- The previous two supported generations of iPhones, i.e. iPhone 16 & iPhone 14.
+- The latest generation of iPad Pro.
+Additionally we will aim to provide the latest odd-numbered iPhone in it's base configuration if there is a noticeable difference in dimensions however this may not always be possible.
+
+We will always aim to have the following iOS versions available as a baseline:
+
+- The latest version plus the previous two.
+- These should always be the latest point release.
+
+It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this.
+
+The default configuration will always be the latest even-numbered base iPhone we support running the previous version of iOS, i.e. iPhone 16 running iOS 26. Before we change the default, we will always provide a minimum of 30 days notice.
+
+Additionally when removing Device and OS support, we will always provide a minimum of 30 days notice.
+
+### Android Support Policy
+
+We will always aim to have the following devices available as a baseline:
+
+- The two latest Google Pixel models & all variations.
+- A generic-tablet model.
+
+We will always aim to have the following Android versions available as a baseline:
+- The latest version.
+- Any version still supported by Google Play Services.
+
+It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this.
+
+The default configuration will always be the latest base Pixel we support running the previous version of Android, i.e. Pixel 10 running Android 16/API 36. Before we change the default, we will always provide a minimum of 30 days notice.
+
+Additionally when removing Device and OS support, we will always provide a minimum of 30 days notice.