Problem
Currently, the SDK allows us to update the refund data consent via Adapty().updateCollectingRefundDataConsent(bool), but there is no way to retrieve the current state of this consent from the SDK (e.g., via getProfile()).
When implementing an Opt-out policy for the "Refund Saver" feature, I need to show a toggle in the App Settings. Since I cannot fetch the current status from Adapty, I cannot accurately reflect whether the user has already opted out or is still opted in, leading to a confusing UI/UX.
The solution you'd like
I would like to see the collectingRefundDataConsent (or a similar naming) property added to the AdaptyProfile object or a getter method in the Adapty class.
Example usage:
final profile = await Adapty().getProfile();
bool isConsentGiven = profile.collectingRefundDataConsent; // This is currently missing
Alternatives I have considered
I considered persisting this state locally using shared_preferences. However, this is prone to errors if the user clears app data or uses multiple devices, as the local state might get out of sync with the actual state stored on Adapty's servers.
Additional context
This is particularly important for compliance with Apple's refund consumption data requirements, where providing a clear "withdraw consent" UI is necessary if an opt-out mechanism is used.
Problem
Currently, the SDK allows us to update the refund data consent via
Adapty().updateCollectingRefundDataConsent(bool), but there is no way to retrieve the current state of this consent from the SDK (e.g., viagetProfile()).When implementing an Opt-out policy for the "Refund Saver" feature, I need to show a toggle in the App Settings. Since I cannot fetch the current status from Adapty, I cannot accurately reflect whether the user has already opted out or is still opted in, leading to a confusing UI/UX.
The solution you'd like
I would like to see the
collectingRefundDataConsent(or a similar naming) property added to theAdaptyProfileobject or a getter method in theAdaptyclass.Example usage:
Alternatives I have considered
I considered persisting this state locally using
shared_preferences. However, this is prone to errors if the user clears app data or uses multiple devices, as the local state might get out of sync with the actual state stored on Adapty's servers.Additional context
This is particularly important for compliance with Apple's refund consumption data requirements, where providing a clear "withdraw consent" UI is necessary if an opt-out mechanism is used.