Last updated: October 14, 2026

Transparency Report

Effective May 24, 2026 Third Eye Cyborg, LLC Last updated September 1, 2026

1. Reporting cadence

We publish transparency reports as often as we reasonably can. We don't follow a fixed schedule, and each report says what period it covers.

The first edition under this cadence will cover the reporting period July 1, 2026 – December 31, 2026 and will be published in final form on or before March 31, 2027. The categories, methodology, escalation paths, and contact channels described in the sections below are in effect now and apply to every legal-process item, takedown notice, government request, and moderation action recorded from the publication date of this page forward, so that the first edition can be built directly from contemporaneous records.

2. First edition — interim status

This page is the interim first edition of the Transparency Report. The reporting period it covers (July 1, 2026 – December 31, 2026) has not yet closed as of the Last updated date shown above. No counts are reported here because the compliance ledger for this period is still open; any number published today would be a forecast rather than a measurement.

The final first edition, with the aggregated counts described in sections 3 – 8, will replace this notice on or before March 31, 2027. Until then, the methodology, categories, and contact channels below are authoritative and binding on our internal record-keeping.

3. Methodology

Counts in this report are aggregated from our internal compliance ledger, which records every legal-process item received by Third Eye Cyborg, LLC and every moderation action taken under our Acceptable Use Policy, DMCA Policy, DSA Notice and Action mechanism, and Child-Safety workflow. Each entry is timestamped, classified by request type, and reconciled against the originating record (notice, warrant, legal request identifier, or in-product report ID) before it is included.

Where a single underlying event generates multiple records (for example, a single warrant covering multiple accounts, or a single DMCA notice covering multiple URLs), we count one request per underlying instrument and one action per affected account or URL, and we identify that distinction in the relevant subsection.

Automated accounts, including Network Bots, are a tracked category in the compliance ledger. Bot-related notices, content actions, token revocations, and installation removals are aggregated with the relevant moderation or enforcement category and identified separately where reporting volume permits without compromising privacy.

4. Government and law-enforcement requests

The categories below cover the July 1, 2026 – December 31, 2026 reporting period. Sub-jurisdiction breakdowns are provided where the number of requests in a jurisdiction is large enough that doing so does not compromise the privacy of users or the integrity of ongoing investigations.

• US subpoenas received no counts yet and number complied with in whole or in part no counts yet.
• US court orders under 18 U.S.C. § 2703(d) received no counts yet and complied with no counts yet.
• US search warrants received no counts yet and complied with no counts yet.
• US National Security Letters and FISA process received no counts yet, reported within the bands permitted by 50 U.S.C. § 1874.
• Emergency disclosure requests under 18 U.S.C. § 2702(b)(8) received no counts yet and acted on no counts yet.
• Preservation requests under 18 U.S.C. § 2703(f) received no counts yet and honoured no counts yet.
• Non-US government requests received no counts yet, broken down by jurisdiction where volume permits.
• Number of users / accounts identified across all requests above: no counts yet.
• Percentage of requests that produced some user data: no counts yet.

5. Copyright takedowns (DMCA)

• 17 U.S.C. § 512(c) takedown notices received no counts yet.
• Notices acted on in whole or in part no counts yet, and notices rejected as facially invalid no counts yet.
• Counter-notices received under § 512(g) no counts yet and content restored no counts yet.
• Repeat-infringer terminations carried out under our published repeat-infringer policy no counts yet.

6. EU Digital Services Act notices

• Article 16 notices of illegal content received from recipients of the Service no counts yet.
• Notices received from trusted flaggers under Article 22 no counts yet.
• Statements of Reasons issued under Article 17, broken down by action type (content removal, visibility restriction, monetisation restriction, account suspension, account termination) no counts yet.
• Internal complaints lodged under Article 20 no counts yet and their outcomes — upheld no counts yet, reversed no counts yet, partially reversed no counts yet.
• Out-of-court dispute settlement proceedings under Article 21 in which we participated no counts yet.
• Median and 90th-percentile time to action for each category: no counts yet.
• Share of decisions in which automated systems were used: no counts yet.

7. Child-safety reports

• Child-safety / CSAE reports received through in-product reporting no counts yet.
• The current in-product workflow is authenticated, rate-limited, deduplicated, and queue-first. Child-safety report descriptions are omitted from the ordinary report record; only the category, target identifiers, and limited routing metadata are retained for review and accountability.
• Reports will include the number of child-safety removals. They'll include NCMEC report counts once our NCMEC reporting account is active.
• Accounts terminated for child-safety violations are reported only when a reviewer records that outcome.

8. Account-level and content-level enforcement

• Accounts actioned for Acceptable Use Policy violations, broken down by the most-cited violation categories no counts yet.
• Posts, books, chapters, Library videos, and other content units removed or restricted no counts yet.
• Appeals received no counts yet and the share that were granted in whole or in part: no counts yet.

Appeals marked as auto-denied represent submissions that reached their review due date without an operator decision in the configured SLA window.

This section also includes enforcement actions involving automated accounts and Network Bots where policy-violating automation impacted users, channels, or network governance.

9. Data minimisation and what we do not collect

We design our systems so that we do not retain data we do not need. As a result, certain figures other platforms publish are not meaningful for Ascended Social — for example, we do not run third-party behavioural advertising at all, so we have nothing to report under "ad-targeting categories shared". We do not sell personal information for money and do not share personal information for cross-context behavioural advertising as defined by the CCPA / CPRA, so the corresponding "sale" and "share" figures are structurally zero.

10. Related policies

For the legal framework that drives these figures, see the Law Enforcement Guidelines, the DMCA / Copyright Policy, the EU DSA Notices, the Child-Safety Statement, and the Acceptable Use Policy.

11. Contact

Questions about this report can be sent to legal@thirdeyecyborg.com. Researchers and civil-society organisations who would like the underlying methodology spreadsheet for a published period may request it from the same address.

Questions: legal@thirdeyecyborg.com