SeedEnv
Terms of Service
Last Updated: October 6, 2026
Welcome to SeedEnv ("Company," "we," "our," or "us"). These Terms of Service ("Terms") govern your access to and use of the SeedEnv website, applications, APIs, and related services (collectively, the "Platform").
By registering for an account, accessing, or using the Platform, you agree to be bound by these Terms. If you do not agree, do not use the Platform.
1. The SeedEnv Platform
SeedEnv provides a specialized two-sided marketplace connecting software creators and teams ("Developers") with community members and QA specialists ("Testers") for structured beta testing, feature validation, and user feedback campaigns ("Campaigns").
SeedEnv acts as a facilitator and platform provider. SeedEnv is not an employer, contractor, agent, or representative of either Developers or Testers.
2. Eligibility & Account Registration
- Age Requirement: You must be at least 18 years old (or the legal age of majority in your jurisdiction) to create an account.
- Account Integrity: You agree to provide accurate, current, and complete information during registration. You may not maintain multiple accounts, impersonate another entity, or use automated systems (bots/scrapers) to register or interact with the Platform.
- Account Security: You are responsible for safeguarding your credentials and for all activities that occur under your account. Notify us immediately if you suspect unauthorized access.
- Member Connections & Private Messages: Use follows and message requests respectfully. No harassment, spam, impersonation or unsolicited payment demands. A new contact may send one request; further messages require the recipient's acceptance. You may decline, block or report a conversation from Messages, and disable new requests in Account Message privacy. Following a developer can optionally enable email updates; tester follows do not send email. Direct messages do not amend an assignment's recorded directions or payment terms and must not be used to bypass SeedEnv review or funding protections.
3. Developer Terms & Obligations
- Campaign Rules & Instructions: Developers are solely responsible for setting clear test criteria, device/environment requirements, instructions, and review benchmarks.
- Versioned Directions: An active cohort's existing step titles and directions may be edited without changing rewards, funded places, proof types or payment terms. SeedEnv retains prior versions with the developer account and save time. Each accepted assignment is linked to the instruction version in effect at acceptance, and its submission remains reviewed against that version. Updated directions apply to new assignments only; existing testers are not required to satisfy later changes. Existing testers see an update notice while their assigned steps remain unchanged. For cohorts predating versioning, the initial archive records the directions available when versioning was introduced, not a reconstruction of earlier edits.
- App Safety & Compliance: Software, builds, URLs, and test packages provided to Testers must be lawful, free from malicious code, spyware, or harmful payloads, and compliant with all third-party platform rules (e.g., Apple App Store, Google Play Store).
- Funding & Reviews: Developers must pre-fund or commit campaign rewards as required by the Platform. Campaign submissions must be reviewed in good faith and in a timely manner. Arbitrary rejections or bad-faith refusals to approve valid proof of completion violate these Terms and may result in immediate suspension.
4. Tester Terms & Obligations
- Independent Status: Testers participate in campaigns as independent third parties. Participation does not create an employment, partnership, or joint-venture relationship with SeedEnv or any Developer.
- Completion Standards: Work must follow the campaign instructions disclosed before participation, including required steps, eligible devices, accurate evidence, and any stated duration or continuous participation requirement. Where a campaign requires 14 continuous days opted in, a single screenshot or an early submission does not by itself prove that period was completed. Honest negative feedback is not grounds for denial when it meets the published requirements; developers may not impose new undisclosed standards after work begins.
- Authenticity of Feedback: All feedback, bug reports, logs, and completion proofs must be genuine, accurate, and produced by you on qualifying hardware/software. The use of emulators (unless explicitly permitted), fake screenshots, duplicate submissions, or synthetic AI-generated feedback is strictly prohibited.
- Confidentiality: Pre-release software, unannounced features, and proprietary campaign details shared through SeedEnv are strictly confidential. You agree not to distribute, leak, screenshot, stream, or publicly discuss any beta build without express written consent from the Developer.
5. Rewards, Fees, and Payouts
- Reward Eligibility: Testers are only eligible for campaign rewards, bounties, or incentives upon meeting all verified requirements set by the Developer and approved under SeedEnv platform standards.
- Denied Work & Manual Reward Hold: A developer denial automatically opens a manual review case. The unpaid reward allocated to that submission remains held in the campaign, is not available for tester cash-out or developer refund/reuse, and does not automatically approve while review is pending. The denial is provisional, not an automatic forfeiture. SeedEnv reviews the disclosed instructions, evidence, developer reason, and any required participation period, and records a decision either approving the work and authorizing its reward or confirming the denial and releasing the unused place. Contact terimus@seedenv.com with relevant evidence. No fixed resolution time is guaranteed. This hold does not freeze unrelated earnings or reverse funds already paid. Stripe payout-readiness and funding-reconciliation requirements still apply to approved payments.
- Review Window & Auto-Approval: Developers have 48 hours from the time a Tester submits proof to approve it, request manual review of a denial, or request a revision. If a submission receives no review decision within 48 hours and is not held for denial or fraud review, SeedEnv automatically approves it and authorizes the posted reward from the funded reward pool, subject to payment-provider readiness. A revision request pauses this window until the Tester resubmits, which starts a new 48-hour window. A denied-proof case does not auto-approve while manual review is pending. Automatic approval does not limit SeedEnv's rights under Fraud & Chargebacks.
- Platform Fees: SeedEnv may charge platform fees, processing fees, or commissions on campaign transactions. Any applicable fees will be disclosed prior to checkout or funding.
- Developer Promotions & Referrals: Discounts reduce only SeedEnv platform servicing fees, never tester rewards, payment processing, balance top-ups or Clippers agreements. The first funded cohort receives a one-time full platform-fee waiver; cancellation or refund after funding does not reset eligibility. Link one inviter permanently before your first funded cohort. Future referral credits require at least $50 in actual funded tester escrow, not a reusable balance top-up. A 50% credit remains pending until at least half the qualifying cohort has genuinely started or submitted testing; it then vests for 90 days. New credits stack multiplicatively, with a maximum 75% discount; excess credits remain unused. Credits reserved for a pending payment cannot be spent elsewhere. Source-cohort cancellation, refund or dispute revokes the credit; actual servicing-fee savings already redeemed are recovered from the referrer's funding balance and recorded for operator review. This recovery may create funding debt, but never reduces tester rewards. Already-issued legacy codes retain their non-expiring, up-to-100% stacking terms. Public promotions and permanent account fee waivers retain their stated terms. Credits are not cash, transferable balances or refundable rewards. No self-referrals, circular referrals, multiple accounts or fabricated activity. A TestFlight join link is bound to its original SeedEnv developer and cannot be reused by another account without verified support intervention. Signup, payment-method setup, unpaid checkout and preview alone do not earn a vested credit.
- Prepaid Balance: Custom campaigns are funded from a prepaid SeedEnv balance. Developers add funds through Stripe Checkout; each top-up charges exactly the amount credited to the balance, with no surcharge, card processing or top-up fee, and is itemized on a receipt. Each time the Developer accepts a tester, that tester's reward and the platform fee (20% of rewards, with a $15.00 minimum per campaign taken on the first acceptance) are deducted from the balance; each amount is shown before acceptance and itemized on a receipt. If the balance is insufficient, the tester is not accepted unless the Developer has enabled auto-reload, in which case the Developer authorizes SeedEnv to charge the saved payment method for the selected reload amount (or the shortfall, if larger). The balance does not earn interest, is not a deposit account, and can be used only for SeedEnv campaigns.
- Balance Refunds: The Developer may request a refund of the available balance at any time from Billing. Refunds are returned to the payment methods that funded the balance, most recent top-up first. Amounts that cannot be refunded automatically remain in the balance, and SeedEnv will assist through support.
- Refunds: When a campaign is ended by the Developer or reaches its expiry, SeedEnv automatically returns unused funds. For custom campaigns, the reward and platform fee for each unused paid place are credited back to the Developer's prepaid balance. For bundles, unused tester rewards are refunded to the original payment method. For bundles, the fixed platform fee is refunded only if no tester started the campaign, except as stated in the Google Play 14-Day retention guarantee. Testers already working when a campaign ends may still submit, and approved work is paid from the held funds. Rewards already approved or paid to testers cannot be refunded. Questions: terimus@seedenv.com.
- Google Play 14-Day Retention Guarantee: For the Google Play 14-Day Closed Test bundle, if fewer than 12 SeedEnv testers remain opted in to the Developer's closed testing track for 14 continuous days during the cohort window, SeedEnv will refund the full bundle price, including the platform fee, to the original payment method. Requests must be made within 30 days after the cohort window ends and are verified against the Developer's Play Console tester data. The guarantee covers tester retention only; Google decides production access independently and SeedEnv does not guarantee approval, ranking, or store listing outcomes. The guarantee does not apply if the Developer removes testers, pauses or unpublishes the test track, or ships a build that testers cannot install.
- Fraud & Chargebacks: SeedEnv reserves the right to withhold, freeze, or reverse pending payouts, rewards, or wallet balances if fraudulent activity, manipulated submissions, or abusive payment chargebacks are detected.
- Taxes: Users are solely responsible for determining and paying any applicable income, sales, or local taxes arising from payments or rewards received.
6. Intellectual Property
- SeedEnv IP: All branding, interfaces, code, designs, and content provided directly by SeedEnv remain the exclusive property of SeedEnv.
- Developer IP: Developers retain full ownership of their software, applications, assets, and trade secrets.
- Feedback License: By submitting feedback, issue reports, logs, or suggestions to a Campaign, Testers grant the respective Developer a non-exclusive, perpetual, worldwide, royalty-free license to use, incorporate, and implement that feedback into their products without further compensation beyond agreed campaign rewards.
Clippers Creator Agreements
Clippers is a separate paid-content collaboration area. Creators retain ownership of their videos. Upon successful payment, the developer receives a non-exclusive, 90-day organic repost license to the approved video. This specific license overrides the general feedback license for Clippers videos. Paid advertising, boosting, whitelisting, raw footage, and ownership transfer are excluded and require a separate agreement.
Each agreement records a fixed creator fee, revision limit, delivery deadline, publication platform, and minimum period the post must remain public. The developer pre-funds the fee and disclosed platform charge through Stripe. This marketplace payment flow is not represented as legal escrow. Draft approval alone does not release payment; publication evidence and verification are required, followed by developer confirmation that the published video matches the approved draft.
Developer review and payment release are due within 72 hours of submission, included revisions within three days of a revision request, and publication within seven days of draft approval. Creators must provide honest content, required sponsorship disclosure, and appropriate rights to music and other media. Views, conversions, and follower growth are not guaranteed. Deadlines and post-retention breaches require human dispute review; no automatic refund, payout forfeiture, or clawback is performed.
Either party may raise an agreement dispute for administrator review. Unreleased funds and further work are frozen during review. Developers may cancel before creator upload starts; later refunds require administrator review. Already initiated or completed transfers require payment-provider reconciliation and are not automatically reversed. Stripe charges, transfers, and bank payouts can have different settlement times. Creators should not start work until the agreement is marked funded.
Review watermarks are interface overlays, not burned-in file watermarks or copy protection. Drafts may not be reused without the agreed license. Social API verification establishes account ownership and selected post metadata, not visual identity, permanent availability, or compliance certification. Developers remain responsible for reviewing the actual public content. SeedEnv does not automatically publish to social accounts.
7. Prohibited Conduct
You agree not to:
- Exploit, reverse-engineer, decompile, or tamper with the Platform or other users' beta builds.
- Sybil attack or game the platform using automated tools, scripts, or multiple accounts.
- Harass, threaten, or abuse other users or SeedEnv staff.
- Circumvent the platform by attempting to solicit off-platform payments to avoid platform fees.
8. Suspension & Termination
We reserve the right to suspend or terminate your account and access to the Platform at our sole discretion, without prior notice, for conduct that violates these Terms, harms other users, or exposes SeedEnv to legal liability.
9. Disclaimers & Limitation of Liability
- As-Is Service: The Platform is provided "as is" and "as available" without warranties of any kind, whether express or implied.
- Pre-Release Software Risk: You acknowledge that beta software tested via the Platform is experimental and may contain bugs, crashes, or data-loss risks. SeedEnv is not liable for any system instability, device damage, or data loss resulting from installing third-party developer builds.
- Limitation of Liability: To the maximum extent permitted by applicable law, SeedEnv shall not be liable for any indirect, incidental, punitive, or consequential damages, or any loss of profits, data, or goodwill arising out of or related to your use of the Platform.
10. Governing Law & Dispute Resolution
These Terms shall be governed by and construed in accordance with the laws of the State of Florida, United States, without regard to its conflict of law principles. Any legal action or proceeding arising under these Terms shall be brought exclusively in the state or federal courts located in Florida.
11. Contact Information
If you have questions about these Terms, please contact us at:
Email: terimus@seedenv.com