ThreadPresence (“we”, “the app”) is a brand support desk for Meta Threads. A support agent connects a brand’s Threads account, searches public posts by support-intent keywords, selects a customer thread, and publishes a reply as that brand. This policy describes what data we process so Meta App Review and end users can verify our use.
Who operates the app
ThreadPresence is operated by LnTech for App Review and brand support pilots. Contact: the app operator (LnTech). Live origin: https://thread-presence.vercel.app.
Data we process
- Threads OAuth tokens — access token issued by Meta/Threads after you authorize the app, used only to call official Threads Graph APIs on your behalf.
- Profile identifiers — Threads user id and username (`/me`) so the UI can show “Replying as brand @username”.
- Search results — public media returned by `keyword_search` for the keyword you enter. Shown in the support queue so an agent can choose a thread. Not stored in a warehouse or CRM in v1.
- Reply text you submit — sent to Threads via `reply_to_id` + `threads_publish`. Once published, the reply lives on Threads under Meta’s terms.
- Session cookie — an HTTP-only cookie (`tp_session`) holding the token and profile fields for the browser session. No separate user database in v1.
What we do not do
- We do not sell personal data.
- We do not run a listening warehouse, analytics dashboard, or bulk export of search results in v1.
- We do not auto-reply or send bulk spam. Every reply requires an explicit agent action.
- We do not use Threads data for advertising targeting outside the support desk flow.
Permissions (scopes)
The app requests: threads_basic, threads_keyword_search, threads_content_publish, threads_manage_replies. Each is used only for connect → search → reply-as-brand as described above.
Storage and retention
Session data lives in the signed cookie until you sign out, the token expires (~60 days for long-lived Threads tokens), or the cookie is cleared. Search results exist only in the browser for that request. Server logs on the host (Vercel) may briefly include request metadata per normal hosting practice; they are not used as a product feature.
Sharing
We share data with Meta/Threads when calling their APIs to search and publish. Hosting is on Vercel. We do not share Threads tokens with unrelated third parties.
Your choices
Disconnect anytime via Sign out in the app (clears the session cookie). For full data-deletion steps, see Data Deletion. You may also revoke the app in your Threads / Meta account settings.
Children
The app is intended for brand support agents and business users, not for children under 13 (or the age required by local law).
Changes
We may update this policy as the product evolves. The “Last updated” date at the top will change when we do.