Operator and scope
Social Apps Hub is operated by the individual behind DailyDiscountsHQ, not by a registered company represented on this website. Contact the operator at enquiry@dailydiscountshq.com about the workspace or your information.
The workspace is based on a self-hosted Postiz application and is currently used for operator-managed testing. It is not open for public registration. Visiting the DailyDiscountsHQ website does not connect a social account; the website Privacy Policy covers those visits separately.
Information the workspace processes
Workspace accounts. The application processes a login email, authentication information, a workspace identifier, and session information to control access. An application login is separate from a social-platform login.
Authorized social connections. For personal LinkedIn access, the configured permissions are openid, profile, and w_member_social. LinkedIn provides an account identifier, display name, and profile picture where available. The application receives an access token and expiry information; a refresh token is processed only if the platform issues one.
Publishing information. The workspace stores content and media supplied for drafts or scheduled posts, scheduling settings, publishing status, platform post identifiers, and relevant error information. It does not receive a LinkedIn password: LinkedIn handles the platform sign-in and authorization.
How information is used
The information is used to identify the authorized account, display its connection, prepare content, carry out publishing actions selected by the user, and diagnose failed actions. Access tokens allow the server to make the authorized platform requests.
Authorizing a connection does not itself publish a post. A user must choose a publishing action. The current setup does not offer paid-ad campaign management or approved company-Page publishing. LinkedIn data is not collected for resale or advertising profiles through this testing workspace.
Where data goes
The application server and its database store workspace and connection records; media is stored in the operator-controlled application environment. Content selected for publishing is transmitted to LinkedIn or the relevant authorized platform. Once published, that platform handles the content under its own terms and the account’s visibility settings.
The current test environment runs locally rather than on this public website. Email requests are handled through the operator’s email service. Operational records and backups may be retained within the application environment. Access is limited to the operator and any explicitly authorized workspace participants.
Storage, expiry, and removal
Tokens and connection records are stored on the application side, not in the public website files. Token validity is determined by the social platform; the user may need to reconnect after expiry or revocation.
Data is retained while needed for the authorized testing and publishing workflow, troubleshooting, or applicable obligations. The current application uses soft deletion for channel removal: marking a connection as removed does not immediately erase its database record, tokens, post history, or backups.
For removal beyond the workspace controls, send a deletion request to the operator. The operator will review the request, remove information that is no longer needed, and explain any lawful retention requirement. There is no verified automatic purge schedule in this test setup.
Revoke access or request deletion
You can revoke Social Apps Hub’s authorization in LinkedIn’s account settings for permitted services. Removing the workspace connection and revoking LinkedIn authorization are separate steps. Revocation stops the relevant platform access but does not by itself erase the workspace’s stored history or already published LinkedIn posts.
To request access, correction, or deletion of your workspace information, email enquiry@dailydiscountshq.com with the account or workspace concerned. Do not include a password or token. The operator may request proportionate information to confirm ownership before acting. Manage already published posts through the relevant platform.
Sessions and future changes
Unlike the static public website, the publishing workspace uses authentication/session information to keep authorized users signed in. The current LinkedIn connection test does not require third-party advertising trackers.
Public registration, new providers, external AI processing, additional analytics, or a change of legal operator would require this notice and the actual controls to be reviewed before those changes are offered. This notice does not claim platform approval or replace the platform’s own privacy terms.