ThisModern.dev Public policy

OttoNominous / Threads application

Privacy
Policy

Effective August 28, 2026Last updated August 28, 2026

This policy explains what information the OttoNominous application receives through Meta’s Threads API, why it is used, how it is protected, and how to request deletion.

On this pageOperatorInformationHow it is usedSharingRetentionSecurityYour choicesChildrenChangesContact
01

Who operates this application

OttoNominous is an automated Threads publishing and engagement application operated by ThisModern.dev, an independent digital practice based in Georgia, United States. References to “we,” “us,” or “the application” in this policy refer to ThisModern.dev and the OttoNominous application.

02

Information we receive

The application receives only information needed to operate the authorized Threads account and the features described here.

Account and authorization information

  • Threads app-scoped user ID, username, display name, profile biography, and verification status.
  • OAuth access tokens and the permissions granted to the application.

Content and interaction information

  • Posts created through the application, including text, topic tags, media IDs, permalinks, and timestamps.
  • Public replies and mentions involving the authorized account, including public usernames, text, post IDs, timestamps, and permalinks.
  • Public profile and post information returned by Threads discovery or search features when those features are authorized.

Performance information

  • Post and profile insights made available by Threads, including views, likes, replies, reposts, quotes, shares, clicks, and follower counts.
  • Derived analytics such as engagement rates, performance comparisons, content categories, and strategy adjustments.

We do not intentionally collect private Threads messages, payment information, precise location, government identifiers, or data from a device’s address book.

03

How information is used

Information is used to:

  • Authenticate the authorized Threads account.
  • Create, publish, retrieve, and manage Threads posts and replies.
  • Prevent duplicate posts or duplicate responses.
  • Measure views and engagement and prepare performance reports.
  • Improve topic selection, writing strategy, timing, and relevance using aggregate performance data.
  • Detect errors, enforce rate limits, protect credentials, and maintain application security.
  • Respond to support, privacy, and deletion requests.

The application does not use Threads information for credit decisions, employment decisions, insurance decisions, surveillance, facial recognition, or targeted advertising.

04

How information is shared

We do not sell personal information. We do not rent Threads data or provide it to data brokers.

Information may be processed by:

  • Meta and Threads, as necessary to authenticate the account and provide API functionality.
  • Infrastructure providers used to host the application, store operational records, and secure network traffic.
  • Service providers acting on our instructions, when required to operate or secure the application and subject to appropriate confidentiality obligations.
  • Authorities or other parties when disclosure is required by law, necessary to protect rights and safety, or needed to investigate abuse.

Public posts and replies remain public according to the visibility settings and policies of Threads.

05

Data retention

  • OAuth tokens are retained while the account remains connected or until they expire, are replaced, or are revoked.
  • Post, reply, and performance records are retained while needed to operate the application and evaluate its performance.
  • When an account is disconnected or a valid deletion request is received, associated account-level records are deleted or de-identified within 30 days, unless retention is required by law or necessary for security and fraud prevention.
  • Temporary backups may persist for up to an additional 30 days before routine deletion.
  • Aggregated or de-identified statistics that no longer identify an account or person may be retained.
06

Security

We use reasonable administrative and technical safeguards appropriate to the information processed. These include encrypted HTTPS transport, restricted credential storage, least-privilege API permissions, access controls, rate limiting, and logs designed to avoid exposing secrets.

No method of electronic storage or transmission is completely secure. We cannot guarantee absolute security, but we will investigate material incidents and provide notifications when legally required.

07

Your choices and data deletion

You may revoke the application’s Threads access through your Threads account’s website permissions or connected-app settings. Revocation prevents future API access but may not automatically remove operational records already stored by the application.

To request access, correction, or deletion, email otto@thismodern.dev with the subject “OttoNominous data request” and include the relevant Threads username. We may request reasonable verification before acting.

For step-by-step deletion instructions, visit the OttoNominous data-deletion page.

08

Children’s privacy

The application is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information to the application, contact us so it can be reviewed and removed.

09

Changes to this policy

We may update this policy as the application, Threads API, or legal requirements change. The “Last updated” date will identify the current version. Material changes will be described on this page or through another reasonable notice.

10

Contact

Questions about this policy or the application can be sent to:

OttoNominous privacyotto@thismodern.dev
© 2026 ThisModern.devData deletionReturn home ↑