relation-graph Membership Rights and Usage Boundaries

Last updated: April 18, 2026

This document explains the current membership, seat, credit, support, and on-site access rules for relation-graph Free, Pro, Team, and Enterprise offerings. It is not the full site-wide contract and it is not the full knowledge-content license text.

1. Document Role and Priority

To keep each document focused, please read them in this structure:

1. Terms of Service: governs accounts, ordering, payments, GraphPilot, public snapshots, liability limits, and governing law.
2. Privacy Policy: governs personal information, task data, attachments, logs, third-party processors, and cross-border transfers.
3. Knowledge Content License: governs the licensing boundaries for RG Template Vault, RG-Dev Skill, RG-Expert KB, GraphPilot outputs, and related protected knowledge content.
4. This document: explains the current site rules for membership plans, seats, credits, downloads, and support scope.

If there is any difference between public pages, orders, quotations, enterprise contracts, and project-specific statements, the usual priority is:

1. the final written contract or project-specific authorization confirmed by both sides;
2. the relevant order, quotation, or project statement;
3. the Knowledge Content License and the Terms of Service;
4. this document.

2. General Understanding of Plans

1. Free, Pro, Team, and Enterprise are the main plan levels currently offered on the site.
2. Unless a page expressly says otherwise, the Plan offerings on this site are one-time purchases and are not auto-renewing subscriptions.
3. At different times, each plan may include different example scope, credit amounts, support level, knowledge-content scope, public-page benefits, or enterprise-service boundaries. The actual scope is the one described on the purchase page or the applicable order at the time of purchase.
4. The core open-source relation-graph component itself remains available under its open-source license. The main value of paid plans is example access, knowledge content, GraphPilot capabilities, delivery efficiency, and support strength, rather than restricting the basic usability of the open-source component.

3. Seats and Account Rules

3.1 Individual Plans

1. Pro is generally intended for one account.
2. A single account should be used by one real person and may not be shared among multiple people.

3.2 Team and Enterprise

1. Team and Enterprise may use team-member collaboration and shared-pool models for some entitlements.
2. Team members should be assigned within the authorized team or shared pool. One account may not be used in place of multiple real users.
3. Credits, permissions, or service capabilities in a team shared pool may be allocated to authorized members based on site rules, back-office configuration, or order terms.
4. If staff changes, role changes, or organizational restructuring occurs, member assignments and shared-pool access may be adjusted under the then-current rules or manual handling process.

4. Credit Rules

1. At present, credits may only be used for online use of RG GraphPilot.
2. The default billing unit is one complete input/output interaction, and each complete interaction normally consumes 1 credit.
3. Team and Enterprise credits may operate through a team shared-pool model. If multiple pools or multiple credit sources are available, the system may consume the higher-level eligible credits first.
4. Credit records may remain stored long term, but whether they can actually be used depends on whether the account or team currently has an active eligible plan.
5. If your plan expires, becomes inactive, is suspended, or is adjusted, your remaining credits may become temporarily unavailable even if a balance still appears.
6. On renewal, credits may continue to accumulate and become available under the renewed validity rules. On upgrades, refunds, chargebacks, order cancellations, manual corrections, or special adjustments, credits may be reset, deducted, reversed, or recalculated.
7. If a refund or reversal happens, the credit amount associated with that plan may be clawed back, and the balance may become negative if necessary.

5. Downloads, Access, and Previously Authorized Content

1. For content that you have already downloaded or that you were expressly authorized to use through an order, plan, or project-specific authorization, the project-use license generally continues and may keep being used in your commercial project, internal system, or client-delivery project.
2. However, “continuing project-use rights” does not mean we automatically promise permanent online access to:
   • continuing on-site access;
   • permanent redownload convenience;
   • later updated versions;
   • newly released content;
   • continued online use of RG GraphPilot.
3. Continued access, new content, later updates, on-site downloads, online GraphPilot use, and other continuing fulfillment matters still depend on whether you have an active plan, active order, or other written authorization at that time.
4. If the site still allows some access, redownload ability, or history visibility after expiration, that is generally a convenience feature and does not create an additional permanent contractual obligation.

6. Support Boundaries

1. Team and Enterprise generally receive higher-priority human support.
2. The public promise of a “first human response within 24 hours” generally means an initial confirmation, reply, or start of handling. It does not mean the issue will necessarily be fixed or delivered within 24 hours.
3. Standard support usually covers:
   • use of the relation-graph component;
   • understanding, integrating, and adapting example code;
   • common questions related to graph display, graph editing, or GraphPilot usage;
   • collaboration items that were expressly promised within the purchased scope.
4. If a request clearly exceeds standard support, such as long-term embedded work, full outsourced development, delivery of a complex business system, or a large amount of business code unrelated to relation-graph, it will usually require support hours, project-specific development, or an enterprise contract.

7. How GraphPilot Relates to Membership Plans

1. The availability of online RG GraphPilot, credit amounts, upload scope, snapshot capability, session retention, and related limits may vary by plan level. The applicable page and order description control.
2. Private deployment of RG GraphPilot, local GraphPilot usage, enterprise knowledge-enhanced workflows, and enterprise AI integration capabilities are generally not automatic rights of ordinary plans and should be governed by Enterprise, project-specific authorization, or a separate contract.
3. Even if credits remain recorded on your account, you may still be unable to start new online GraphPilot tasks if no active eligible plan exists.

8. Prohibited Membership Usage

Members may not:

• share one account among multiple real users;
• resell, rent, lend, or transfer accounts, seats, credits, knowledge-content access, download rights, or shared-pool access to unauthorized third parties;
• consume site resources through automation, high-frequency scraping, API abuse, or circumvention;
• use authorized content to build a resource platform, knowledge product, or competing commercial substitute for relation-graph;
• repackage protected examples, knowledge content, or GraphPilot outputs into a new template library, knowledge base, training dataset, or outward-facing AI material pack.

9. Reference Pages

• Terms of Service: /terms
• Privacy Policy: /privacy-policy
• Knowledge Content License: /knowledge-content-license

If you need to confirm the scope for a specific order or enterprise project, rely on the relevant order, quotation, contract, and written confirmation between both sides.