Rimba Courts · Internal operations
Privacy policy
This policy explains how Rimba Courts handles data in its internal operations tools: the Rimba Ops Automation tool, which uses Google account data when Rimba Courts authorizes it to access the venue's operational mailbox, and the read-only Threads discovery integration, which reads public Threads posts about padel after Meta grants the required permissions.
Gmail: what we access
With the mailbox owner's approval, the Ops Automation tool requests only the Gmail read-only permission. It looks for Rimba-owned operational and booking report emails and reads the report attachments needed for internal venue reporting and reconciliation. It may use message metadata such as sender, subject, and date to identify those reports.
Gmail: what we do not do
- We do not request Gmail send, edit, or delete access.
- We do not send messages, alter mailbox content, or delete emails through this tool.
- We do not sell Google user data or use it for advertising.
Gmail: use, storage, and sharing
The tool uses the accessed information for Rimba Courts operational purposes only. It checks the metadata of candidate report emails and saves selected Rimba-owned report attachments and derived operational records in Rimba-controlled systems for internal reporting and reconciliation. It does not intentionally retain unrelated email or unrelated attachments.
Access to the retrieved operational data is limited to authorized Rimba operations personnel. Data may be processed by infrastructure providers that support these internal systems, but it is not sold or shared for advertising. Operational records are retained as needed for internal accounting and recordkeeping; questions about access or deletion can be sent to the contact below.
Threads: public posts we read
Rimba Courts has collected publicly available Threads posts about padel from public pages and operator-supplied public-post captures. After a verified Meta grant, the read-only integration may also use the documented Threads API keyword search; the built public-profile path remains blocked until separately granted. We do not log in as another user or bypass platform restrictions.
Threads: what we retain
We retain the text of a public post and, when available, its public username, permalink, timestamp and collection provenance. We do not download, store or re-publish any image or video from those posts: media URLs are excluded from API fields we request, and no third-party media bytes are retained. Authorization to use a third party's content is recorded separately, and content without a recorded rights basis is not published.
Threads: how the text is used
Retained public post text is used for editorial pattern analysis and retrieval — studying how Indonesian padel communities write (rhythm, hooks, question shapes, line breaks, emoji placement, code-switching) so that drafts for Rimba Courts' own account sound like the community rather than like a machine. It is not used to train or fine-tune machine-learning models, and it is not used for advertising, retargeting, individual profiling or sale to third parties. We do not post, reply to, follow or message anyone automatically through this integration; drafts are approved by a person and the publishing path is separate and human-gated.
Threads: retention and deletion
- Public post text and source metadata are retained for no more than 12 months from collection, with earlier deletion when required. Our scheduled retention sweep and source-specific deletion path remove local retained copies, including source text in derived records.
- If we learn that a source post was removed or made private, or receive a Meta or user deletion request, we delete its retained source data promptly and within 7 days after we receive notice. The integration does not automatically detect source removal; please contact us if you know a source was removed or made private.
- Only non-content deletion evidence is retained: a hashed source key, reason, notice time, deletion time and outcome, without the post text or permalink.
- No media bytes are retained, so there are no images or videos to delete.
Questions or access concerns
For questions about these tools or their data use, contact courtsrimba@gmail.com. The mailbox owner can also revoke the tool's Google authorization in their Google Account settings; Threads permissions can be revoked by the Threads account holder in their Threads settings.