PYLON Reversion Policy

Revision date: 2026-06-15 (v1.0.0) Audience: Filmmakers licensing Titles to PYLON Companion document: /legal/filmmaker-distribution-agreement

This Reversion Policy is a standalone restatement of the auto-reversion mechanics in the Filmmaker Distribution Agreement (the "Agreement"). It exists so a Creator can answer the question "under what circumstances do my rights come back to me?" without reading the full Agreement. In the event of any inconsistency between this Policy and the Agreement, the Agreement controls.

1. Why this policy exists

PYLON's deal with Creators is non-exclusive and time-bounded, but the deeper commitment we make is this: if PYLON stops actively working the Title, or stops paying for it, the Title comes back to the Creator automatically. No back-and-forth, no negotiation, no email chain.

This policy enforces that commitment. The triggers are checked by an automated cron in PYLON's API every day. If a trigger fires, an advance-warning email is sent 30 days before reversion takes effect. At the effective date, the Title is removed from the PYLON service and all rights snap back to the Creator.

2. Definitions used in this policy

The following terms have the meaning given in the Agreement (clause 3) and are repeated here for convenience:

• Title, a film licensed to PYLON under the Agreement.
• Active distribution, a Title is "actively distributed" if, in the trailing six-month window, either (a) it has been delivered to (or attempted in good faith to be delivered to) PYLON's owned FAST channel or a third-party FAST partner, OR (b) it has been served at least one premium SVOD view event recorded by PYLON's view-events pipeline.
• Premium view event, a watch event by an authenticated paying PYLON subscriber that crosses PYLON's qualifying-view threshold (excluding buffering, pre-roll skips, and the first 5 seconds of any session).
• Reversion Event, the occurrence of any auto-reversion trigger in this policy or any Creator-elected termination under clause 8 of the Agreement.

3. The three triggers

PYLON's auto-reversion cron checks each Title against three independent triggers. Any one of them, if satisfied and unrescued, causes the Title to revert.

3.1 Six-month inactivity (no FAST attempt)

If a Title has been published on PYLON for at least six (6) calendar months and PYLON has not attempted FAST distribution of the Title in the fifth month following publication, the Title auto-reverts.

The cron derives each Title's "month-5 expected FAST attribution" window from the Title's own publishedAt date and looks for at least one row in fast_revenue_title_attributions covering that month. A Title published on 2026-01-15 has a month-5 window of 2026-06; if no attribution row exists for that period by the time the cron runs in 2026-07, the Title is a six-month candidate.

This rule reflects PYLON's commitment to actively monetise the FAST tier. A Title that sits un-pitched for a full pre-revert month goes back to the Creator.

3.2 Twelve-month no-views

If a Title has been published on PYLON for at least twelve (12) calendar months and has received zero premium view events in the trailing 30 days, the Title auto-reverts.

The cron evaluates this rule independently of rule 3.1. A Title that has lost audience for a year goes back to the Creator.

3.3 Twelve-month nonpayment

If PYLON has failed to pay an undisputed Compensation amount of more than US$50 to the Creator for twelve (12) consecutive calendar months, all rights to all of the Creator's Titles revert to the Creator.

This rule is enforced through PYLON's payouts ledger and the monthly Creator statement workflow. "Undisputed" means an amount that PYLON has accrued and reported on a monthly statement and has not flagged as held pending investigation, dispute, regulatory or sanctions hold, or audit. A held amount does not run the clock.

[FOUNDER REVIEW · 2026-04-26] The auto-reversion cron at apps/api/src/cron/auto-reversion.ts enforces the 6-month no-FAST and 12-month no-premium-views rules but does NOT enforce the 12-month nonpayment rule described in §3.3. Today this clause is operationally a manual-claim path: a creator can invoke it via /studio/dmca (or by emailing [email protected]), and PYLON's payouts team verifies via the payouts_ledger table. Founder must decide before publication: (a) implement the cron rule and remove this notice, OR (b) reword §3.3 to describe the manual-claim mechanism explicitly. Do NOT publish without resolving.

4. Advance notice

At least 30 days before any auto-reversion under section 3 takes effect, PYLON sends the Creator a written advance-warning notice identifying:

• the Title (or in the case of section 3.3, all Titles affected);
• the rule under which reversion is pending;
• the date on which reversion is scheduled to take effect;
• a brief description of the cure (if any) PYLON is taking, or the cure the Creator may take.

The advance-warning notice is delivered as:

• an email to the Creator's primary email address on file in /studio profile; and
• an in-platform notification surfaced on /studio next sign-in.

PYLON's auto-reversion cron is configured to enqueue this advance notice automatically. The cron stamps a reversion_warning_sent_at timestamp on each Title to ensure idempotency, a second cron tick on the same day is a no-op. If the automated notice fails (e.g. due to a queue outage), the failure does not waive the Creator's reversion right; instead, the effective reversion date is extended by the number of days the notice was late.

A Creator may, in /studio, opt to receive an additional 60-day heads-up email; this is a courtesy and does not change the legal effective date.

5. Cure window

Between the advance-warning notice and the effective reversion date, PYLON may cure the underlying trigger:

• For section 3.1, by attempting in good faith to deliver the Title to a FAST partner during the warning window.
• For section 3.2, by serving qualifying premium view events during the warning window. PYLON does not guarantee any specific audience or marketing intervention, but a Title that re-enters the promoted-content surface and receives one or more premium views resets the clock.
• For section 3.3, by paying past-due Compensation in full, including any interest or remediation amount agreed with the Creator.

On valid cure, the auto-reversion does not fire. PYLON shall confirm the cure to the Creator in writing within 7 days. The clock for the underlying trigger restarts (e.g. a cured section 3.1 trigger restarts a fresh 6-month window).

A Creator may at any time during the cure window elect to forgo cure and accept reversion by replying in writing, useful where the Creator wishes to license elsewhere immediately. PYLON shall give effect to that election within 14 days.

6. Exclusions (when the clock does NOT run)

The auto-reversion clocks in section 3 are paused during:

6.1 Force majeure

Any period during which PYLON is prevented from distributing the Title by an event beyond its reasonable control, including natural disaster, war, terrorism, strike, internet or vendor outage of significant duration, or governmental action. PYLON shall give written notice of the force-majeure event and shall resume distribution promptly when the event ends.

6.2 Legal hold

Any period during which the Title is subject to:

• a DMCA takedown pending counter-notice or court action;
• a sanctions or export-control hold;
• a court-ordered or law-enforcement-requested takedown;
• a regulator-mandated content review.

PYLON shall notify the Creator in writing of the legal hold and the basis for it (subject to any non-disclosure obligations imposed by authority).

6.3 Mutual pause

Any period of mutual pause agreed in writing between the Parties. Examples: Creator requests a temporary takedown for festival exclusivity; Creator and PYLON jointly pause distribution pending an authorised re-master delivery.

6.4 Repeat-infringer suspension

If the Creator is suspended under PYLON's repeat-infringer policy (pylon.video/dmca), the auto-reversion clock is paused until the suspension is resolved. This protects against a suspended Creator gaming the reversion path. After resolution, the clock resumes from where it left off.

7. What happens at reversion

On the effective reversion date:

7.1 Rights snap back

All rights granted to PYLON under clause 4 of the Agreement automatically revert to the Creator. PYLON has no continuing licence in the Title (subject to clause 7.3 below).

7.2 Removal from distribution

Within 30 days of the effective reversion date, PYLON shall:

• (a) remove the Title from the PYLON web, mobile, and connected- device applications;
• (b) revoke and recall the Title from any FAST partner surface;
• (c) cease creating new marketing clips of the Title;
• (d) revoke sub-licences to PYLON's hosting, CDN, FAST, and operational vendors holding the Title;
• (e) confirm deletion of the Title's master from PYLON storage, except for back-ups retained per PYLON's published retention schedule (which expire automatically per the Privacy Policy).

7.3 Existing marketing assets

Marketing clips, key art, and metadata distributed before the reversion may persist on third-party social platforms outside PYLON's operational control (e.g. an Instagram clip already shared by a fan). PYLON has no obligation to recall third-party copies, but PYLON shall:

• (a) not actively promote, boost, or re-share the existing marketing clip post-reversion;
• (b) take down any PYLON-owned copy of the Title from PYLON-owned surfaces; and
• (c) cooperate with reasonable Creator requests for take-down of PYLON-controlled copies on third-party platforms (e.g. PYLON's own Instagram).

7.4 Final payment

Any earned but unpaid Compensation continues to accrue and is paid in the next monthly payout cycle following the reversion, subject to the $25 minimum threshold and the reporting / dispute process in clause 11 of the Agreement.

7.5 Mutual release

On consummation of reversion (i.e. removal complete and final payment made), the Parties release each other from claims arising from the Agreement with respect to the reverted Title, except for claims that survive under clause 21 of the Agreement (which include indemnification, confidentiality, audit rights for the relevant period, and dispute resolution).

8. How to verify the cron fired correctly

Creators concerned about reversion timing can:

• Check /studio for the in-platform reversion notification.
• Inspect the email log in /studio/notifications (which records every cron-fired email keyed to the Creator).
• Request a copy of the audit-log entries (PYLON's auto-reversion cron writes an audit_log row keyed actorId='system:cron.reversion' for every reversion action).

If the Creator believes the cron fired in error (e.g. PYLON did deliver to FAST in month 5 but the attribution row is missing), contact [email protected] within 30 days of the reversion notice. PYLON shall reinstate the Title where the error is confirmed; the underlying clock restarts.

9. Reversion vs editorial removal

This policy concerns auto-reversion, which transfers all rights back to the Creator. It does not concern editorial removal, in which PYLON exercises its discretion under clause 17 of the Agreement (the Editorial Guardrail) to remove or restrict a Title without returning rights, typically because the Title has been found to violate PRD §11.7 or the AI-content policy.

Editorial removal:

• pauses the auto-reversion clock under section 6 of this policy (i.e. the Title does not auto-revert during editorial review);
• entitles the Creator to a written explanation and an appeal under the editorial-review process;
• does not entitle the Creator to damages, compensation, or specific performance.

If editorial review concludes that a Title cannot be reinstated, PYLON shall offer the Creator a mutual termination of the Agreement with respect to that Title, and any remaining Creator-side rights not granted to PYLON revert to the Creator. PYLON retains no continuing licence.

10. Document version control and updates

PYLON may update this policy from time to time. Material changes require:

• 60 days' advance email notice to all active Creators;
• preservation of the prior version at docs/legal/archive/reversion-policy-vN.md;
• a version-history entry below.

A Creator who objects to a material update may exercise the 90-day exit right under clause 8 of the Agreement during the 60-day notice window.

Contact

• Filmmaker support: [email protected]
• Legal: [email protected]

Version history