Rimba Courts · Read-only preview
Threads discovery — read-only reviewer preview
Rimba Courts is a padel venue operator in Indonesia. Our internal editorial workflow reads public Threads posts about padel to study how the community writes. This page describes the data shape and rules without embedding any third-party post. It has no controls of any kind: it makes no API calls, and there is nothing here to click.
The permissions this integration asks for
This first App Review requests only threads_keyword_search. Profile discovery is built but deferred to a later review.
threads_basic— required for all Threads API calls and already granted.threads_keyword_search—GET /keyword_search, public post discovery by keyword or topic tag. Documented limit: 2,200 queries per rolling 24 hours.threads_profile_discovery— not requested in the first filing. The built, permission-gatedGET /profile_lookupandGET /profile_postspaths for known public padel accounts remain blocked. Documented: public profiles with at least 100 followers, 1,000 requests per rolling 24 hours, and theownerfield is not returned.
We request no other discovery permission in this filing. There is no publish, reply, follow, message, delete, repost or media-download permission in this read-only acquisition path, and no such endpoint exists in its client.
What a search response contains
Field shape as documented by Meta for GET /keyword_search. No live call is made while the permission is under review.
{
"id": "<post-id>",
"text": "<public post text>",
"media_type": "TEXT_POST",
"permalink": "https://www.threads.com/@<user>/post/<shortcode>",
"timestamp": "2026-10-06T05:42:03+0000",
"username": "<public handle>",
"has_replies": false,
"is_quote_post": false,
"is_reply": false
}
We request text and metadata fields only. media_url is deliberately not in the field list, so no image or video is ever fetched or stored.
What a retained row looks like
This is a documented field-shape example, not a live or retained post. No third-party source text or identity is embedded in this public page:
id: <source-id> account: <public username, when available> permalink: <public source link, when available> text: <public post text, held only in private stores> media: none retained rights: UNKNOWN until separately evidenced provenance: <API search, public page, or operator public-post capture>
What we refuse — and what is never learned from
Not every public post is usable. These shapes are rejected automatically, with the reason recorded, and they are never used to study writing:
- Marketplace listings (someone selling gear) — rejected:
marketplace_listing_shape. - Booking or event templates (fields on lines, nobody talking) — rejected:
booking_or_event_template_shape. - News and official releases — rejected:
news_or_official_release_shape. - Video descriptions, venue blurbs and price lists — ineligible by kind, whatever surface they came from.
If a captured post contains a reply fragment from someone else in another language, that fragment is omitted from the analysed view. The source capture is still subject to the same retention and deletion path; no real fragment is reproduced on this page.
Controls on this surface: none
This preview is a description, not a console. It contains no form, no button, no input field and no action endpoint, and the pages are served with form-action 'none'.
- No publishing. No scheduling.
- No replies. No automated following. No messages.
- No deleting or editing of any Threads content. No reposts or quotes.
- No media download, no media re-upload, no media stored.
- No analytics, no tracking, no advertising use, no individual profiling.
Reading is also gated in software: the integration refuses to call search or profile endpoints until Meta has granted the permission and the grant has been verified, so nothing runs unapproved.
Retention and deletion
- Public post text and source metadata are retained for no more than 12 months from collection.
- After known source removal/private status or a Meta/user request, retained source data is deleted promptly and within 7 days after we receive notice. This integration does not automatically detect source removal.
- Only non-content deletion evidence is retained: hashed source key, reason, notice/deletion times and outcome.
- No media bytes are retained, so no copy of anyone's image or video exists to delete.
Read the full privacy policy. Questions: courtsrimba@gmail.com.