DreamPark Developer Agreement
How attraction developers earn on the DreamPark Platform
How It Works
You build an Attraction. Businesses pay DreamPark for the minutes played on their headsets. Every month, part of that money is shared with developers, split by how much each developer's content was played.
Where the Money Comes From
Usage minutes are the source of every developer payout. Headset rentals and monthly plan fees are not shared.
Your Share
What Counts
- Billable minutes only: free trials, a business's own team, phones and test devices, and very short plays are not charged, so they don't earn usage money. You may see more minutes played than billable minutes.
- Real play only: play we identify as automated, fraudulent or artificially inflated is excluded.
Getting Paid
A monthly statement shows your minutes, your share and your payout. DreamPark will tell you when payouts open. From then, payouts are made in US dollars within 45 days of the end of each month, once your balance is at least $100 and a completed W-9 (or W-8BEN for international developers) is on file. Amounts below $100 carry over to the next month.
What You Need to Do
- Ship a working attraction that passes DreamPark's release review
- Keep it running: fix critical bugs within 72 hours, major bugs within 7 days
- Stay compatible: update for new Quest OS versions and DreamPark SDK releases within 30 days
The Full Terms
The plain-English summary above is for clarity, not a substitute for the actual terms. The terms below govern the DreamPark Developer Revenue Sharing Program.
1. Definitions
"DreamPark" means Dream Park Immersive, Inc. "Developer" means the person or legal entity named in the signature below.
"Attraction" means a content experience created by Developer and published to the Platform via the DreamPark SDK, including all updates, patches and derivative content. A Developer may publish multiple Attractions.
"Net Usage Revenue" means amounts DreamPark actually receives from businesses for metered play on their headsets in a calendar month (for example, a per-minute usage charge), less payment-processing fees, refunds, chargebacks and sales, use and value-added taxes. It excludes business monthly plan fees and amounts charged for hardware, rentals, shipping, deposits, booking fees and replacement or damage fees.
"Billable Minutes" means minutes of play on a business's headset, as measured by DreamPark's servers, that DreamPark charged that business for. Play that is not charged is not Billable Minutes, including free trials, a business's own team, phones and other non-headset devices, and plays under the minimum billable length. A session's Billable Minutes are split across the titles that were running during it, by the time each one ran, as recorded on DreamPark's servers. Billable Minutes that cannot be tied to a title are credited to no one.
"Usage Pool" means 50 percent (50%) of Net Usage Revenue for a calendar month.
2. Revenue Share
2.1 The Usage Split
For each calendar month, the Usage Pool is allocated among Developers pro rata by Billable Minutes: each Developer's share equals the combined Billable Minutes of its Attractions divided by the total Billable Minutes credited to all Attractions on the Platform in that month.
2.2 What Is Not Shared
Developer has no share of headset rentals, business monthly plan fees or any other DreamPark revenue. DreamPark retains the remainder of Net Usage Revenue.
2.3 Monthly Settlement
Allocation is computed once per calendar month after the month closes and credited to the Developer account that owns each Attraction. Each month is calculated independently. DreamPark never pays Developer from its own funds beyond the Usage Pool, and Developer is never liable for platform costs.
2.4 Corrections
If Billable Minutes are later found to be fraudulent or mis-measured, or revenue is refunded or charged back, DreamPark may adjust the affected month's allocation in a later statement. Amounts already paid out are not clawed back except in cases of fraud by Developer.
2.5 Earlier Months
If Developer signed an earlier version of these terms, that version keeps applying to Developer until the date in DreamPark's written notice, given at least 60 days ahead. If Developer first signs this version, it applies from signing. Months before these terms apply to Developer are calculated and paid under the terms in force during those months. Those earnings are not reduced by these terms.
3. Payment
Monthly statements itemize Billable Minutes, share of the Usage Pool and earnings by Attraction. Payouts are not open yet: earnings accrue until DreamPark gives notice that payouts have opened, and they are not lost or reduced by the wait. From then, payouts are made in US dollars within 45 days after the end of each month, subject to: (a) an accrued balance of at least $100; and (b) a completed W-9 or W-8BEN on file. Balances below the minimum carry over. Earnings accrued in DreamPoints under the previous entry-fee model remain cash-out eligible at the DreamEx Rate in effect when cashed out.
4. Conditions
Revenue sharing for an Attraction requires all of: (a) the Attraction has passed DreamPark's release review; (b) Developer is not in material breach of these terms or the SDK Use Agreement; (c) the Attraction meets ongoing quality and support standards under Section 5. If a condition lapses, DreamPark may suspend the Attraction (and its share of each pool) until cured.
5. Post-Release Obligations
While an Attraction is live, Developer shall: respond to critical (P0) bugs within 24 hours and fix within 72 hours; respond to major (P1) bugs within 48 hours and fix within 7 days; and provide compatibility updates within 30 days of new Quest OS or DreamPark SDK releases. An Attraction that is broken or unsupported may be removed until fixed and accrues no Billable Minutes while removed. Post-release support is part of the value exchange for revenue share, not separately compensated.
6. Reporting and Audit
DreamPark provides monthly statements within 45 days of month end. Developer may engage an independent CPA to audit the calculation of its share once per 12 months on 30 days' notice. If underpayment exceeds 5%, DreamPark pays the deficiency plus 1.5%/month interest and reimburses reasonable audit costs. Records are retained for 3 years.
7. Platform Changes
DreamPark retains sole discretion over pricing, packaging, usage rates, promotions, free trials and distribution. The 50% Usage Pool percentage and the allocation method in Section 2 will not be reduced or changed except with 60 days' advance notice.
8. Ownership and License
Developer retains all right, title, and interest in and to its Attractions. Developer grants DreamPark a worldwide, non-exclusive license to host, distribute, display, and operate the Attraction on the Platform, including for business customers and in promotional materials for the Platform, for the duration of participation in the Program.
9. Term and Termination
These terms apply for as long as Developer has an Attraction live on the Platform. Developer may unpublish an Attraction at any time; accrued earnings remain payable under Section 3. DreamPark may remove an Attraction for cause (material breach, quality failure, or abandonment per Section 5) or with 90 days' notice for convenience. Upon any termination, accrued unpaid amounts above the minimum threshold are paid out per Section 3.
10. Confidentiality
Non-public revenue data, minutes totals and financial details of the Program are confidential, surviving 3 years after termination. Developer may publicly share its own aggregate earnings.
11. Dispute Resolution
Good faith negotiation (30 days) → mediation in San Francisco → binding JAMS arbitration. Governed by California law. Either Party may seek injunctive relief.
12. General Provisions
These terms supplement the SDK Use Agreement and any signed development agreement. Existing arrangements governed by a signed agreement remain governed solely by that agreement. The Parties are independent contractors. No assignment by Developer without DreamPark consent. DreamPark may update these terms with 60 days' notice as described in Section 7; continued participation constitutes acceptance.
13. Signature
Typing a name and ticking the box to agree is a binding electronic signature. The person signing confirms they are at least 18 and have authority to bind the Developer they name.
A person under 18 cannot sign these terms. A parent or legal guardian must sign for them, and accepts these terms on their behalf.
Questions? Reach out to aidan@dreampark.app