<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Quota Extension Feedback delay in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Quota-Extension-Feedback-delay/m-p/7155144#M18866</link>
    <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;we resubmitted our quota extension on May 10, 2025 after an initial rejection and applied the requested changes. We have not received an update since. We have read the updated extended-access criteria and understand reviews have become stricter.&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Are there current benchmarks for review timelines and sensible intervals for follow-ups?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Would additional materials help (for example MAUs, error budgets, security attestations)?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If our use case does not meet the new criteria, what compliant alternatives do you recommend in the interim (for example dev mode with export or deep links) until we scale?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Thanks for any guidance.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Sep 2025 20:04:38 GMT</pubDate>
    <dc:creator>sebass-tian</dc:creator>
    <dc:date>2025-09-29T20:04:38Z</dc:date>
    <item>
      <title>Quota Extension Feedback delay</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Quota-Extension-Feedback-delay/m-p/7155144#M18866</link>
      <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;we resubmitted our quota extension on May 10, 2025 after an initial rejection and applied the requested changes. We have not received an update since. We have read the updated extended-access criteria and understand reviews have become stricter.&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Are there current benchmarks for review timelines and sensible intervals for follow-ups?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Would additional materials help (for example MAUs, error budgets, security attestations)?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If our use case does not meet the new criteria, what compliant alternatives do you recommend in the interim (for example dev mode with export or deep links) until we scale?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Thanks for any guidance.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 20:04:38 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Quota-Extension-Feedback-delay/m-p/7155144#M18866</guid>
      <dc:creator>sebass-tian</dc:creator>
      <dc:date>2025-09-29T20:04:38Z</dc:date>
    </item>
  </channel>
</rss>

