Privacy policy

Information the portal handles

• Business and website information: website addresses, business purpose, audience, brand voice and content preferences entered by the owner.
• Content and activity: post titles, copy, image briefs, generated or uploaded images, external image URLs, drafts, approvals, Trash records, planned times and workspace activity.
• Connected accounts: account or Page names and identifiers, selected publishing destinations, authorization tokens and expiry information returned after you grant access to Meta or LinkedIn.
• Generation and publishing records: AI request results and usage information, delivery status, platform post identifiers, links and errors needed to operate the workflow and avoid accidental duplicate posts.
• Technical information: necessary session and authorization cookies. Hosting infrastructure may also process request information such as IP addresses, browser details and server logs for delivery, security and troubleshooting.

Social account passwords are entered on the relevant platform’s own authorization page. The portal does not ask you to enter your Meta or LinkedIn password into its forms.

How information is used

Information is used to maintain the private workspace, generate requested content, show drafts and previews, record approval, connect authorized accounts, publish approved posts when instructed, display delivery results and troubleshoot failures. Connected-account access is used for the available publishing workflow; this release does not provide an inbox that reads private messages or an address-book import feature.

AI generation and service providers

When you request AI generation, relevant brand details, prompts and draft text are sent to OpenAI for text generation. Image briefs are sent for image generation. The portal saves the resulting content and available usage information. Avoid including passwords, access tokens or unnecessary personal information in prompts.

The deployed Hostinger edition stores workspace records, private image bytes, generation history and publishing records in its configured MySQL database. Hostinger provides application hosting. Meta and LinkedIn process account authorization and publishing requests. An external image host receives a request when its image URL is loaded or imported.

Providers apply their own terms and privacy practices and may process information in different countries. See the OpenAI Privacy Policy, Meta Privacy Policy and LinkedIn Privacy Policy for their information.

Social publishing and visibility

Connecting an account does not itself publish content. The owner selects a destination and approves the post before using the publishing controls. When publishing, the portal sends the approved content and the selected image to the relevant social platform. The platform determines visibility and any subsequent use of the published content under its settings and policies.

For Instagram publishing, the portal can create a signed image link valid for 15 minutes so Meta can fetch that image. Ordinary portal image endpoints remain protected. Published images and posts may remain available on the social platform after the temporary link expires.

Cookies and security

The portal uses an HTTP-only signed owner-session cookie with a maximum 12-hour lifetime. Its OAuth state cookies expire after ten minutes and help validate account connections. Cookies use secure transport on the configured HTTPS deployment. This release does not add advertising pixels or marketing analytics cookies to the portal.

Stored social authorization tokens are encrypted using AES-256-GCM with a server-configured key. API credentials are kept in server runtime configuration. Access controls and authorization checks protect private workspace and image endpoints. These measures reduce risk but do not guarantee that any system is completely secure.

Retention, disconnection and deletion

Workspace content, images, activity and delivery records remain stored until the administrator removes them or processes an appropriate deletion request. Moving a post to Trash retains it for restoration; it is not permanent erasure. Generated or uploaded images may remain stored even if a draft is abandoned.

Disconnecting a social destination removes its saved connection from the portal. You can also revoke the application’s access in the social platform’s settings. Disconnecting does not automatically erase past drafts, publishing history or posts already published on that platform.

You may request access, correction or deletion by contacting us. We may verify that you are authorized to make the request before acting. Relevant copies in backups, security logs or third-party systems may follow separate retention processes. See the data-deletion instructions for details.

Contact and updates

For privacy questions or requests, email admin@dmarketeer.com.sg. Please do not include passwords or authorization tokens.

We may update this policy when the portal’s features or data handling change. The effective date above identifies this version.