Privacy Policy

Threadsort is a Chrome extension and related website that helps users sort and export publicly visible Threads profile posts. This Privacy Policy explains what information we collect, how we use it, when we share it, and the choices available to users.

1. What Threadsort does

Threadsort works on supported public Threads profile pages on desktop Chrome. It reads the visible page to extract post details such as text, publish time, and visible counters so the extension can sort posts and let the user export the ranked results.

Threadsort is an independent product. It is not affiliated with, endorsed by, or operated by Meta or Threads.

2. Information we collect

Information processed locally in the extension

• Supported page URL and profile handle
• Visible post data needed for sorting and export
• User-selected sort metric and scan depth
• Last scan result stored locally so the popup can reopen without losing state

Information stored for account, billing, and activation

• Email address used for activation or billing
• Subscription and entitlement status
• Manual comped access reason and expiry when access is granted outside checkout
• Billing provider customer and subscription identifiers
• Device entitlement session identifiers and expiry data
• Referral and affiliate summary data when the affiliate program is used

Information used only when a user chooses Google Sheets export

• Google OAuth access needed to create and write the spreadsheet created by Threadsort
• Visible export rows that the user explicitly sends to Google Sheets

Website analytics information

• Basic website usage and page view information collected through Google Analytics
• Standard browser, device, and referral metadata associated with those visits

Information we do not collect by default

• Private Threads content
• Browsing history outside the supported product flow
• Messages, passwords, payment card numbers, or unrelated website content
• Exported datasets on our servers unless a user explicitly sends them to support

3. Chrome permissions and why they are used

• activeTab: used after the user opens the extension to detect the current tab and confirm whether it is a supported Threads profile page
• storage: used to store local settings, cached scans, debug flags, and entitlement session data
• identity: used for Google Sheets OAuth when a Pro user chooses Google Sheets export
• identity.email: requested only when a user clicks Activate Pro, so the extension can try matching the Chrome profile email to an active subscription
• sheets.googleapis.com host access: requested only when a Pro user chooses Google Sheets export and the extension creates a spreadsheet on the user's behalf

4. How we use information

• Operate the extension and supported website pages
• Sort and export supported public Threads profile posts
• Enforce Free and Pro plan limits
• Activate paid access on a device after checkout
• Provide billing, account, and affiliate features
• Measure website traffic and onboarding usage on the marketing site
• Detect abuse, fraud, or misuse of the product
• Respond to support or legal requests

5. Legal basis and product posture

Threadsort is designed to process the minimum information needed to provide a local-first sorting and export workflow. We do not sell user data. We do not use scraped profile data to build a separate analytics database for resale.

6. Sharing and service providers

We may share limited information with service providers that help us operate the service.

• Vercel: hosts the Threadsort website and API routes
• Neon: stores account, subscription, session, and referral data
• Lemon Squeezy: handles checkout, subscription billing, customer portal, and affiliate infrastructure
• Google Analytics: measures website visits and high-level site usage
• Google Sheets API: used only when a user explicitly exports visible results to a new Google Sheet created by Threadsort

We may also disclose information if required by law, to enforce our terms, or to protect users, our service, or the public.

7. Data retention

• Local scan data remains in extension storage until replaced, cleared, or removed by the user
• Entitlement sessions are retained for the session period needed to keep a device activated
• Account, billing, and affiliate records are retained as needed for service operation, tax, accounting, fraud prevention, and legal compliance

8. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect account and billing data. No internet-based service can guarantee absolute security, so users should also protect their browser, email account, and devices.

9. International transfers

Depending on where users are located and which providers are used, information may be processed in countries other than the user’s home country.

10. Google API Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

11. Your choices

• Uninstall the extension at any time
• Clear local extension data through the browser
• Choose not to activate a paid plan through browser profile email
• Choose not to use Google Sheets export if you do not want to connect a Google account
• Contact us to request account-related access, correction, or deletion where applicable
• Use the billing portal to manage or cancel a subscription

12. Children

Threadsort is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

13. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the effective date on this page. Material changes may also be communicated through the product or website where appropriate.

14. Contact

For privacy questions or requests, contact threadsort@gmail.com or visit the support page.