Platform data use
This page explains how SocialCoDesk is designed to use data received through official platform connections.
Last updated: 18 October 2026Purpose and user control
SocialCoDesk requests platform data only to discover destinations the user manages, publish user-approved content, show supported results and maintain connection health. A user chooses the business profile and exact destinations before publishing.
Authentication data
Provider passwords are never collected. OAuth authorization codes are one-time values handled by the secure authorization service and are not displayed by callback pages. Long-lived provider secrets must remain server-side or in the operating-system credential vault, according to the connector design.
Sharing and selling
Platform data is not designed to be sold. It is shared only with infrastructure needed to deliver the user-requested connection, publishing or support operation, subject to the provider rules and applicable law.
Retention and disconnection
A disconnected destination should lose its locally stored grant reference, and an unreferenced grant should be revoked or removed where the provider supports it. Cached business and analytics records follow the product retention and deletion controls.
Current availability
The connector foundation is under development. Production data access remains subject to provider approval, secure broker deployment and real-account verification.