This document establishes the acceptable-use structure for the developing Rise ecosystem. Before production, it must be reviewed against the services actually offered, applicable law, product capabilities, account and community systems, infrastructure controls, enforcement procedures, and verified reporting channels.
Responsible use begins with clear boundaries.
This framework is intended to apply to public Rise websites and, when made operational under applicable terms, Rise products, services, accounts, APIs, community spaces, automation systems, artificial-intelligence capabilities, downloads, and shared platform infrastructure.
Individual products may establish additional requirements where their technical capabilities or risk profiles require more specific controls. More specific rules can supplement this baseline without eliminating broader security and lawful-use obligations.
Rise services are not a vehicle for unlawful activity.
Users must comply with applicable law and must not knowingly use Rise systems to facilitate conduct that is unlawful in the context in which the service is being used.
This includes attempts to use Rise infrastructure as a mechanism for fraud, theft, unauthorized access, unlawful distribution, rights violations, or other prohibited activity.
Production enforcement language must account for applicable jurisdictional requirements and the actual relationship between Rise and the affected user or organization.
Authorization is a boundary, not a suggestion.
Users must not attempt to access accounts, data, systems, administrative functions, infrastructure, credentials, secrets, or other resources unless they are authorized to do so.
Prohibited security-related activity may include:
- bypassing authentication, authorization, licensing, entitlement, rate-limit, or other access controls;
- probing or exploiting vulnerabilities without applicable authorization;
- obtaining, exposing, using, or distributing credentials, private keys, tokens, secrets, or protected information without permission;
- interfering with security monitoring, audit mechanisms, logs, or protective controls;
- accessing another user's or organization's resources without authorization; and
- intentionally introducing malicious code or attempting to compromise Rise or connected systems.
Legitimate security research requires an applicable authorization path. A future vulnerability-disclosure or security-research program should be governed by its own published scope when such a program is established.
Do not use the platform to damage systems or people.
Rise systems must not be intentionally used to distribute malware, disrupt services, damage infrastructure, facilitate unauthorized surveillance, conduct abusive attacks, or create material security risks for Rise, its users, or third parties.
Users must not intentionally overwhelm services, evade reasonable technical restrictions, abuse infrastructure resources, or interfere with another person's legitimate ability to use an applicable service.
Use content and systems with respect for applicable rights.
Users are responsible for ensuring they have appropriate rights or authorization for content, data, software, files, or other material they submit to or process through an applicable Rise service.
Rise services must not knowingly be used to infringe intellectual property, violate privacy or confidentiality obligations, unlawfully distribute protected material, or falsely claim ownership or authorization.
Product-specific terms may define additional responsibilities for user content, creator assets, software projects, shared files, or other materials handled by a particular product.
Do not use trust mechanisms to deceive or abuse.
Where Rise services provide accounts, messaging, support, community participation, notifications, or other communication capabilities, users must not use those systems for impersonation, fraud, deceptive identity practices, abusive harassment, spam, or unauthorized bulk communications.
Users must not misrepresent an affiliation with Rise or another person or organization in a manner that is materially deceptive.
Automation does not remove user responsibility.
Future Rise products may include artificial-intelligence, agent-based, workflow, voice, or other automation capabilities. Where such features are made available, users remain responsible for using them within applicable authorization, product, security, and legal boundaries.
Automated capabilities must not be intentionally used to bypass access controls, conduct prohibited activity at scale, conceal abusive behavior, compromise systems, or perform actions that the user would not otherwise be authorized to perform.
Product-specific AI or automation terms may establish additional restrictions, review requirements, usage limits, provider requirements, or safeguards based on the capabilities actually deployed.
Shared infrastructure needs reasonable use controls.
Public software services can depend on shared compute, storage, bandwidth, APIs, queues, third-party providers, and other finite resources. Users must not intentionally consume or manipulate those resources in a manner designed to disrupt the service, evade applicable limits, or materially degrade service for others.
Specific quotas, rate limits, plan allowances, AI usage limits, storage limits, or other product controls should be documented only when the corresponding services and commercial rules are operational.
Community spaces require their own operational standards.
Rise intends to support both forums and Discord-based community participation. Those spaces are not represented here as already operational.
When launched, community rules may address harassment, threats, spam, impersonation, malicious links, privacy violations, inappropriate content, product-space organization, reporting, moderation, suspensions, bans, appeals, and other conduct necessary to maintain useful professional spaces.
Community moderation should be role-based and auditable, with appropriate separation between community authority and unrelated billing, infrastructure, or security privileges.
Responses should be proportionate to the situation.
When operational services are governed by this policy, Rise may need to investigate suspected misuse and take reasonable action to protect users, systems, infrastructure, rights, or legal obligations.
Depending on the service, agreement, severity, urgency, and applicable law, responses could include warnings, limiting functionality, removing content, suspending access, terminating access, preserving relevant records, or escalating a matter through appropriate legal or security channels.
Final enforcement procedures, notice requirements, appeal mechanisms, and termination rights must align with the actual product terms and applicable law before production.
Acceptable use must evolve with the platform.
This framework may be updated as Rise introduces new products, service capabilities, community systems, integrations, automation, infrastructure, and operational controls.
Production versions should include appropriate effective-date or revision information, and material changes should be coordinated with the systems and terms they affect.
Security and abuse reports need verified destinations.
Rise intends to provide appropriate channels for security, abuse, community, and legal concerns as those operational functions are established. Specialized addresses or reporting workflows should be published only after they are configured, monitored, and verified.
Until then, the currently published Rise contact options can be used to begin routing a legitimate concern. Do not send passwords, authentication codes, private keys, payment-card details, exploit payloads, or unnecessary sensitive information through an initial general inquiry.