MAKH Social
MAKH Social
This demo policy explains how MAKH Social handles user, workspace, generated content, media, and social platform data while the product is being prepared for platform app review.
MAKH Social stores account details you provide, workspace details, social handle metadata, generated content, media assets you upload, approval notes, schedules, publish records, and interaction records synced or entered for your workspace.
When platform OAuth is enabled, MAKH Social requests only the permissions needed for the selected feature, such as reading connected profile metadata, preparing publish actions, reading comments or engagement, and sending replies you explicitly approve.
MAKH Social does not ask for or store social media passwords. Users connect accounts through each platform's official authorization flow.
Data is used to operate the dashboard, generate and organize content, show approvals and schedules, display interaction history, and prepare platform-specific publishing workflows.
Workspace records are retained while the account remains active. Users can delete individual records in the product, disconnect social handles, or request full workspace deletion.
Session cookies are HTTP-only. Platform tokens, once token exchange is enabled, must be stored encrypted and scoped to the connected workspace.
The demo environment may use hosting, database, payment, and AI providers to run the service. Production subprocessors should be listed before public launch.
For privacy or data requests, contact the MAKH Social operator with the account email and workspace name. A verified owner request is required before deleting workspace data.