About ReleaseDesk
ReleaseDesk is a Chrome extension for preparing app-store publishing information on Apple, Google Play and selected Meta developer websites. It never submits or publishes applications for you.
Data stored on your device
Project names, app descriptions, store listing drafts, selected publishing platforms, preferences and checklist progress are stored in Chrome extension local storage. In this version ReleaseDesk does not provide developer-hosted project synchronization or live accounts. Locally exported JSON backups are unencrypted and should be kept private.
Developer-console website access
After you explicitly request a scan and grant access to a supported site, ReleaseDesk examines limited page route information, eligible field labels and field availability. It does not copy existing form answers into your project. Filling supported empty text fields requires your selection and approval. Any data you save yourself on an app-store website is handled by that store operator.
Optional AI and third parties
Offline drafting assistance does not contact a model provider. Connected AI requires a separately running local gateway on your device. A preliminary model/cost planning request sends lengths of your text, draft type and model preferences to the gateway. After separate approval, your app name and typed description are sent through that gateway to the chosen AI provider, potentially OpenAI, Anthropic/Claude, or DeepSeek if explicitly enabled. These providers process text under their own terms. ReleaseDesk does not automatically send developer-console form answers to AI providers.
Advertising, analytics and sharing
This extension does not run advertisements, developer-operated analytics, central project databases or cloud sync in the current version, nor sell user data for advertising. Chrome stores local workspace data. Apple, Google and Meta process data you submit on their official sites. If you opt into connected AI, your local gateway and selected provider process the draft text you approve.
Data retention and choices
Chrome retains local project records until you erase them or remove the extension. You can manually export an unencrypted backup. Local gateway pairing tokens are kept in trusted Chrome session storage and may be cleared by disconnecting the gateway. Providers and gateway operators may separately retain information according to their own policies.
Permissions
sidePanel presents the interface. storage saves local work. activeTab and scripting support user-requested website inspection and approved blank-field autofill. Optional site origins provide scoped access only after you choose a feature requiring them, including the local gateway at 127.0.0.1.
Chrome Web Store Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data accessed through Chrome permissions is used only to provide or improve the user-requested publishing-preparation function and permitted supporting operations, not for advertising, data brokerage or credit assessment. Human access to user data is prohibited except where permitted by applicable law, security requirements or explicit user consent.
Changes and contact
We will update this notice before materially changing data collection, sharing or features such as hosted accounts, billing or analytics. Contact [email protected] with questions or privacy requests.