Skip to content

SocialDesk — Privacy Policy

Effective date: August 28, 2026 · Version 1.0

1. What SocialDesk is

SocialDesk is a desktop application that runs locally on a single user’s computer. It has no server component and no hosted service. It is used by one person — the operator of clfaigateway.dev — to monitor public discussions on Threads relevant to that product and to publish and reply from their own connected accounts.

There is no sign-up, no user base, and no multi-tenant infrastructure. Each installation is independent and stores its data only on that machine.

2. Data accessed through the Threads API

With the permissions the user grants, SocialDesk accesses:

  • Profile information (threads_basic) — the connected account’s ID and username, used to identify which account an action belongs to.
  • Public post content (threads_keyword_search) — public Threads posts matching keywords the user configures. Returned fields: post ID, text, author username, permalink, timestamp, and media type.
  • Publishing (threads_content_publish) — creates posts and replies from the connected account, only when the user explicitly approves each one.

SocialDesk does not access private accounts, direct messages, follower lists, or any content not returned by the public keyword search endpoint.

3. Where data is stored

All data is stored in a local SQLite database file on the user’s own computer. Access tokens are encrypted at rest using the operating system’s credential store (Keychain on macOS, DPAPI on Windows).

No data is transmitted to any SocialDesk server, because none exists. No analytics, no telemetry, no crash reporting.

4. Third-party processing of Threads content

Text from public posts retrieved via keyword search is sent to a large language model to score topical relevance and to draft reply suggestions for the user to review and edit.

  • Requests are routed through the operator’s own API gateway at clfaigateway.dev, which forwards them to upstream model providers.
  • Only the post text is sent. Usernames, permalinks, and post IDs are not included in these requests.
  • Prompts and responses are not stored by the gateway and are not used to train models.
  • The gateway’s own privacy policy applies to this processing: https://clfaigateway.dev/privacy

Users who prefer not to send post text to any external service can point SocialDesk at a locally hosted model instead; the endpoint is configurable.

5. What we never do

  • We do not sell, rent, or share Threads data with any third party.
  • We do not use Threads data to train machine learning models.
  • We do not build advertising profiles.
  • We do not aggregate data across users — there is only one user.
  • We do not post, reply, or like automatically. Every published action is individually reviewed and approved by the user.

6. Retention and deletion

Retrieved posts are kept locally so the tool does not resurface items the user already reviewed. The user can delete any record, or the entire database file, at any time — deletion is immediate and permanent.

To revoke SocialDesk’s access to a Threads account, remove the app under Settings → Website permissions on Threads. Once revoked, the app can no longer retrieve any data for that account.

To request deletion of data associated with your account, contact us at the address in section 8, or use the automated endpoint at https://clfaigateway.dev/delete. Requests are processed within 30 days.

7. Children

SocialDesk is not directed at anyone under 13 and does not knowingly process their data.

8. Contact

Privacy questions and deletion requests: [email protected]

9. Changes

Material changes to this policy will be reflected in the effective date above.