1. Agreement and eligibility
These Terms form an agreement between you and confirm contracting entity when you access the Magpy website or private beta. You must be authorized to accept them for yourself or the organization you represent and meet the verified minimum age for the service.
2. Private-beta status
The beta may be incomplete, change without notice, experience interruptions or contain errors. Features, integrations, limits and security controls shown in designs or roadmaps are not commitments unless expressly included in a signed agreement. The final terms should state whether beta data is suitable for production use and what service levels, if any, apply.
3. Accounts and access
You are responsible for accurate registration information, safeguarding credentials, controlling authorized users and promptly reporting suspected unauthorized access. Magpy may suspend access when reasonably necessary to protect the service, users or third parties.
4. Acceptable use
You may not use Magpy to violate law or third-party rights, distribute malware, gain unauthorized access, interfere with the service, bypass limits, conduct abusive automated activity, or build products whose prohibited use has been communicated to you. Add any sector, content and high-risk-AI restrictions required by the final product policy.
5. Customer data, generated code and intellectual property
You retain rights in content and product materials you submit, subject to the license Magpy needs to operate the service. The final agreement must clearly define ownership of generated code, platform components, templates, feedback, marketplace listings and derivative materials—especially where third-party or open-source components are involved.
You represent that you have the necessary rights to submit data and instructions to the service.
6. AI-assisted features
AI output may be incomplete, inaccurate or similar to output generated for others. You are responsible for reviewing generated specifications, code, content and actions before relying on or deploying them. Human approval controls reduce risk but do not replace your responsibility for the product you publish or operate.
7. Fees, subscriptions and marketplace terms
Before charging customers, define prices, billing cycles, taxes, refunds, credits, marketplace revenue share, payout timing and the treatment of third-party fees. No payment term shown in a design or roadmap applies unless published in an order form or product-specific terms.
8. Third-party services
Optional integrations and external model providers may have separate terms and availability. Magpy is not responsible for third-party services outside its control. You authorize Magpy to exchange relevant information with integrations you choose to enable.
9. Warranties, liability and indemnity
The final agreement needs jurisdiction-specific warranty disclaimers, liability caps, exclusions, indemnities and exceptions. These provisions should be drafted by counsel based on the actual beta, paid plans, data types and target customer profile.
10. Termination and data export
Define how either party may end the agreement, what happens to active subscriptions, how long customer data remains available for export and when it is deleted. Reserved rights to suspend should be balanced with notice and customer continuity where appropriate.
11. Governing law and disputes
Insert the selected governing law, venue and dispute process after confirming the contracting entity and launch markets: legal review required.
12. Contact
Questions about these Terms can be sent to legal@magpy.co or insert verified mailing address.