Language

Legal

TalkDock Privacy Policy

Effective date: June 1, 2026.

This Privacy Policy explains how Markas Studio handles information related to TalkDock public pages, support workflows, administrator-submitted bug reports, TalkDock Free, and TalkDock Pro.

Terms of UseSupportDocumentation
This policy is designed to be transparent about external services, administrator control, optional diagnostics, Pro licensing, local analytics, and offline lead capture.

1. Who we are and what this policy covers

Markas Studio provides TalkDock software, public product information, documentation, and support resources. In this policy, we, us, and our refer to Markas Studio. You refers to visitors, customers, site administrators, reviewers, and people who interact with TalkDock-related services.

This policy covers information processed through TalkDock public pages, support communications, administrator-submitted bug reports, TalkDock Free behavior, TalkDock Pro licensing, Pro local analytics, and Pro offline lead capture. It does not automatically replace the privacy policy of a website that installs TalkDock.

2. Public pages and ordinary website access

When you access public TalkDock pages, standard website hosting, security, and logging systems may process basic technical information such as IP address, user agent, access time, requested URL, referrer, and security log data where applicable.

If you contact support or submit a business inquiry, we process the information you choose to provide, such as name, email address, site URL, company name, message content, and related context.

  • Purpose: operate pages, secure systems, respond to requests, prevent abuse, maintain records, and improve documentation.
  • We do not sell personal information.
  • We do not use administrator bug reports for unrelated advertising.

3. Free plugin frontend behavior and WhatsApp links

The free TalkDock frontend displays a browser link to the configured WhatsApp destination. TalkDock does not make a server-side request to WhatsApp merely because the button is displayed.

When a visitor clicks the WhatsApp link, the visitor’s browser may open WhatsApp, WhatsApp Web, or another Meta-controlled flow depending on the device and browser configuration. That interaction is governed by WhatsApp or Meta terms and privacy policies.

  • The site administrator controls the WhatsApp URL.
  • Prefilled message text, if enabled, is appended to the WhatsApp URL as a text parameter.
  • The free frontend script emits a local browser custom event on click; it does not by itself send that event to Markas Studio.

4. Administrator-submitted Report-a-Bug data

The free plugin includes an administrator-only Report-a-Bug modal. A report is sent only after the administrator intentionally clicks Send. Before submission, the administrator can review the report fields and choose whether to include optional diagnostics.

Reports may be sent to the Markas Studio bug receiver at https://projects.markas.cloud/wp-json/markas/v1/plugin-bug and are also recorded in a bounded local log on the customer site. If the receiver cannot be reached, the local record remains and the user is told that remote dispatch did not succeed.

  • Possible report data: submitted time, subject, message, optional reply-to email, optional screenshots, optional diagnostics, dispatch status, and receiver reference number if returned.
  • Screenshot limits: maximum 3 images, PNG/JPEG/GIF/WebP only, 5 MB per image, and 8 MB combined raw attachment payload.
  • Optional diagnostics can include plugin version, WordPress version, PHP version, MySQL version, active theme name/version, locale, multisite flag, and memory limit.
  • Diagnostics do not automatically include user accounts, full plugin list, license inventory, admin email, or site URL as JSON fields unless the administrator types relevant information into the report.
  • Local report history is capped to 50 entries; the modal lists up to 20 recent entries. Attachment binary is stripped from the local log and only attachment metadata is retained there.

5. TalkDock Pro license processing

TalkDock Pro communicates with the Markas license API to activate, refresh, heartbeat, or deactivate a Pro license. License checks are required to unlock premium features and to confirm whether the license is active, grace, expired, invalid, or inactive.

License requests may include the license key, normalized site URL, plugin slug, plugin version, WordPress version, PHP version, environment hash, server token, request ID, and related license status information. Local license state is stored in a protected signed envelope and may use a local site secret.

  • API host: https://projects.markas.cloud.
  • API path: /wp-json/talkdock-pro/api/v1.
  • A transient server error may allow a limited grace state; expired or invalid licenses do not unlock premium features.
  • Deactivating a license removes local license state and clears the scheduled Pro heartbeat.

6. TalkDock Pro offline leads

If Pro business hours and offline lead capture are enabled, visitors may submit a local offline lead form outside open hours. This data is stored on the website where TalkDock is installed, not automatically in Markas Studio public content pages.

The website owner controls whether the offline form is enabled and whether a new lead email is sent to the WordPress admin email address.

  • Lead fields: name, email address, message, created time, and page URL.
  • Local storage is capped to the most recent 100 leads.
  • Administrators can review, export CSV, delete one lead, or delete all leads.
  • Site owners should disclose offline lead handling in their own privacy policy.

7. TalkDock Pro analytics, agents, avatars, greetings, and consent

Pro click analytics are stored locally in WordPress and kept to the most recent 90 days. Click tracking includes abuse-prevention controls. Per-agent click totals may be stored when agent routing is used.

Administrator sessions are excluded from public-content telemetry before any row is written, so admins can test pages, Pro CTAs, free-download buttons, popups, and outbound links without polluting analytics.

Optional Google Analytics and Meta Pixel events fire only if the site already loads gtag or fbq and the administrator enables the corresponding Pro setting. TalkDock Pro does not install those analytics platforms by itself.

If administrators configure agent avatar URLs from external hosts, visitor browsers may request those images from the chosen host. Greeting bubbles and consent prompts use administrator-controlled text and frontend behavior on the customer site.

  • Local click data: date, total count, and per-agent counts.
  • Optional GA data depends on the site’s existing Google Analytics setup and configured event name/category.
  • Optional Meta Pixel data depends on the site’s existing fbq setup and configured event name.
  • Consent prompt text should be reviewed by the site owner for regional privacy and messaging requirements.

8. Sharing, retention, and security

We may share information with trusted service providers that help us host websites, secure systems, process support communications, store support records, operate license infrastructure, or maintain technical systems. Providers may process information only for permitted operational purposes and subject to appropriate confidentiality or security obligations.

We retain information only as long as reasonably necessary for support, security, operational records, dispute prevention, legal obligations, product reliability, or abuse prevention. No website, plugin, network, or storage system can be guaranteed completely secure, but reasonable administrative, technical, and organizational safeguards are used according to the nature of the information.

9. Your choices and site-owner responsibilities

Where applicable, you may request access, correction, deletion, or clarification regarding personal information submitted through support or bug-report workflows. We may need to verify the request and may retain limited records where required for security, legal, operational, or dispute-prevention purposes.

If you install TalkDock on your own website, you remain responsible for your own privacy notices, cookie disclosures, contact-channel disclosures, analytics disclosures, WhatsApp disclosures, offline lead notices, and data-processing obligations.

  • Review reports before sending them.
  • Redact screenshots before upload.
  • Use your own privacy policy to explain your WhatsApp, analytics, email, CRM, hosting, and lead-processing practices.
  • Keep WordPress, themes, plugins, PHP, and server software updated.

10. Children, international access, and changes

TalkDock public pages and plugin support workflows are intended for website owners, administrators, businesses, and reviewers. They are not directed to children.

Because websites, license systems, and support systems may be accessed internationally, information may be processed in jurisdictions different from your own. We will update this policy when practices, services, or legal requirements materially change.

Pro for teams that want every chat to count

Turn a simple WhatsApp button into a guided sales path.

Start with the official free TalkDock plugin on WordPress.org, then upgrade when you want business hours, agent routing, page targeting, click analytics, greeting bubbles, consent prompts, and offline lead capture in one clean flow.

  • Capture after-hours leads
  • Route chats to the right agent
  • See what drives clicks
Save IDR 150,000Usually IDR 299,000IDR 149,000per yearNo hard redirect: checkout opens in a focused Lynk popup window. If your browser blocks it, you can continue safely in this tab.
Need the free plugin first? Download TalkDock Free from WordPress.org.Download free plugin
TalkDock is maintained by Markas Studio. Free plugin 1.1.6, Pro add-on 1.1.6. Content version %content_version%.