Stardust End User License Agreement#

Version 2026-10-12.

This Agreement is between BitFlip LLC, a Nevada limited liability company ("BitFlip"), and you. Selecting Accept agreement confirms your acceptance. If you act for an organization, you must have authority to bind it.

Accept before downloading a license token or release package from Stardust. Installation and use require a valid Stardust license and this Agreement. Acceptance includes the binding arbitration terms in section 12. BitFlip records your acceptance, arbitration consent, agreement version and acceptance time.

1. Definitions#

• Software: Stardust's embedded database library, bindings, documentation, release packages and updates.
• License Token: the signed file that activates the Software for your account.
• Pre-Release: any alpha, beta or preview not declared generally available ("GA").
• Support Period: your purchased period of updates and support. Its end date is separate from token expiration.

Project means one identified application, product or service that uses Stardust, as named in your purchase record.

A Project includes its associated clients, interfaces and supporting components, including desktop, mobile and web clients, administrative interfaces, APIs, background workers and agents. Multiple components remain one Project when they operate as parts of the same application, product or service.

A Project includes all its development, testing, staging and production environments, supported platforms, feature editions, updates and successor versions. It may use multiple installations, processes, embedded Stardust instances, databases, replicas or shards without requiring additional project licenses solely because their number increases.

Separate applications, products or services are separate Projects when each uses Stardust to support distinct functionality and is independently offered or operated. Multiple interfaces to the same application or service do not create separate Projects. Shared code, repositories, branding, infrastructure or a Stardust deployment do not, by themselves, combine separate Projects or divide one Project.

A Project name identifies the licensed application, product or service. Renaming it does not transfer the license to a different Project.

2. License#

Payment and compliance with this Agreement grant a non-exclusive, non-transferable, non-sublicensable license:

Enterprise licenses follow their separate agreements. This Agreement applies only if the Enterprise agreement expressly incorporates it.

You may make copies for permitted installation, use, distribution and backup. Keep proprietary notices intact.

Hosted applications. You may operate an application or service that uses Stardust under the applicable license for your permitted use. As the person or organization operating Stardust, you must hold that license, accept this Agreement and supply your License Token. Users who only interact with your hosted application or service and do not receive or run a copy of Stardust do not need their own Stardust licenses, acceptance or tokens. Their number alone does not create additional Projects or require an Enterprise agreement.

Distributed applications. You may distribute the Software in object-code form within your applications, without your License Token or activation credentials. Each recipient person or organization running the embedded Software must obtain its own applicable Stardust license, accept the applicable agreement and supply its own License Token before use. This includes Community and non-commercial use. Distributing the same application to multiple recipients does not create additional Projects for its developer, but the developer's license does not cover those recipients.

Enterprise deployment rights. Community, Solo and Team licenses do not permit you to license the Software on behalf of third-party recipients or deploy it to them using your License Token or activation credentials. Deployment that allows recipients to run the Software without their own Stardust licenses, acceptance and tokens, including white-label or OEM deployment on that basis, requires a separate written Enterprise agreement with BitFlip expressly granting those rights. Contact enterprise@stardustdb.com to discuss deployment licensing.

Your license is perpetual for GA builds dated on or before your support end date, unless terminated under section 10. Later updates and support require optional renewal; renewal is not automatic. Alpha purchases also permit the Pre-Releases offered for that purchase.

3. Restrictions#

Except as expressly permitted, do not:

• Copy, modify, translate or create derivative works of the Software.
• Reverse engineer, decompile, disassemble or derive its source code.
• Alter or bypass license checks, tokens, signatures or other protections.
• Share, publish, sell, rent, lease, lend or transfer your license, credentials or account outside authorized users. Do not bundle credentials in distributed applications.
• Resell or repackage Stardust as a competing database.
• Violate applicable law, including export controls and sanctions.

Keep credentials private and report exposure promptly. Removing exposed credentials does not restore a revoked license. Mandatory legal rights and third-party permissions remain protected. BitFlip reserves all rights not granted.

4. Pre-release versions#

Pre-Releases are incomplete software for evaluation and development.

No stability, reliability or production-suitability guarantees apply. Database, file-format, ABI, API and behavior compatibility are not promised between Pre-Releases or with GA. Features may change or disappear without notice. Later builds may not read existing databases. No migration, upgrade path or data preservation is promised.

Production use is at your own risk. To the maximum extent permitted by law, BitFlip has no liability for that use, including data loss, corruption, downtime or incompatibility. Keep independent backups; recovery is not guaranteed. BitFlip has no obligation to fix Pre-Release errors or provide production support.

For alpha purchases, the included year of updates and support starts at GA, not purchase. Alpha tokens expire thirty days after download, or earlier during the refund window. Valid licenses permit replacement tokens, but do not guarantee availability of a particular build. Token expiration does not start the Support Period.

5. Payment and refunds#

Your purchase record states the tier, fees, currency and applicable project. Request a full refund within fourteen days of purchase at notices@stardustdb.com. Later refunds follow mandatory law. A full refund ends the affected license, support and updates; stop using its tokens.

Tokens issued during the refund window expire no later than its end. Valid licenses permit replacement tokens afterward. You pay applicable taxes, except taxes on BitFlip's income.

6. Ownership#

BitFlip and its licensors own the Software and its intellectual property. You own your applications and data. Using Stardust's public APIs does not make your application a prohibited derivative work.

BitFlip may use voluntarily supplied feedback without payment or obligation. You need not provide feedback or disclose confidential code or data.

You must stand by every issue report, support request and other submission made by you or on your behalf. You remain responsible regardless of how it is created or sent, including through employees, contractors, AI agents or automated tools. Review submissions before sending them, distinguish observations from assumptions, and correct material errors when discovered.

7. Third-party components#

Third-party licenses govern their components and prevail over conflicting terms here. This Agreement does not restrict permissions they grant.

8. Warranties#

To the maximum extent permitted by law, the Software is provided "as is" and "as available," with all faults. BitFlip disclaims express, implied and statutory warranties, including merchantability, fitness, title, non-infringement and accuracy. Uninterrupted operation, error-free operation and protection against data loss are not warranted.

9. Liability#

To the maximum extent permitted by law, BitFlip excludes liability for indirect, incidental, special, consequential, exemplary or punitive damages. This includes lost data, profits, revenue, goodwill and business interruption, however caused, even if BitFlip was warned. Total liability for all claims related to an affected license is capped at the total amount paid for that license, collectively across claims.

Nothing here excludes fraud or other liability that law prohibits excluding. Mandatory consumer warranties, rights and remedies remain protected throughout this Agreement.

10. Termination#

BitFlip may terminate for a material breach not corrected within thirty days after notice, or immediately for a section 3 breach.

BitFlip may end technical support and issue-reporting access for abuse of those channels, with notice to your account contact. Abuse includes threats, harassment, spam, fabricated evidence, and repeated low-effort reports that disregard reporting requirements after notice. Good-faith reports and honest criticism remain permitted.

Your license, updates and replacement-token rights continue unless separately terminated under this Agreement. Refunds remain governed by section 5. Mandatory rights and remedies remain protected.

Public exposure of your token or activation credentials, including in a repository or distributed application, permits immediate revocation of the affected license, tokens, support and updates. BitFlip will notify your account contact.

After termination, stop using the Software and delete its copies. BitFlip may revoke tokens. Sections 3, 6, 8, 9, 10, 12, 13 and 14 survive.

11. Agreement changes#

New versions apply to downloads after you accept them. Your accepted version continues to govern Software previously obtained under it.

12. Governing law and disputes#

Nevada law governs, except where mandatory law requires otherwise.

Before arbitration, either party must send written notice describing the dispute and requested remedy. Both parties must attempt good-faith resolution for thirty days after receipt. This does not delay urgent relief, small claims or legally required deadlines.

You and BitFlip agree to binding arbitration instead of a court trial, subject to the exceptions below. The American Arbitration Association (AAA) administers proceedings before one neutral arbitrator. Consumer disputes follow AAA Consumer Rules; other disputes follow Commercial Rules. Federal arbitration law governs where applicable; otherwise Nevada arbitration law applies.

The location is Clark County, Nevada, subject to mandatory consumer protections and AAA rules. Remote or document-only proceedings are allowed under those rules.

Business parties share administrative and arbitrator costs equally, subject to law and the award. Consumer costs follow AAA's Consumer fee schedule; BitFlip pays the business portion. Each party pays its own attorneys unless law or an authorized award provides otherwise. Sanctions or fee reassignment for harassment or patently frivolous claims require authority under applicable rules and law.

Proceedings must be individual. Both parties waive class actions and class arbitration to the extent permitted by law. Non-waivable representative remedies remain protected. A claim with an unenforceable waiver proceeds in court; other arbitrable claims remain in arbitration.

Eligible small claims and temporary court relief remain available. Court proceedings concerning arbitration or non-arbitrable disputes use Clark County state courts or the federal court with jurisdiction there, subject to mandatory consumer rights to local proceedings and residence-law protections.

13. Personal information#

BitFlip does not sell personal information or use it for targeted advertising. Use is limited to necessary account, sign-in, licensing, support and payment operations, financial due diligence and anonymous metrics. Due diligence includes payment verification, fraud prevention and required financial records.

Anonymous metrics must not identify you or permit reconstruction of your identity. Sharing is limited to providers needed for these purposes and legally required disclosures. These terms do not authorize unrelated collection of application data.

14. General and notices#

This Agreement is the entire agreement about the Software. Invalid provisions do not invalidate the remainder. You may not assign this Agreement without BitFlip's written consent. Failure to enforce a provision is not a waiver.

Send ordinary contractual notices, disputes and privacy questions to notices@stardustdb.com. BitFlip uses your account email; keep it current. Notices take effect on receipt. BitFlip acknowledges dispute notices; delayed acknowledgment does not invalidate receipt. Email does not replace legal process or legally required notice methods, address disclosures or electronic-consent rights.