These terms cover your use of reBe Labs public websites, launch-stage Studio surfaces, demos, written materials, and early reBe Intelligence interactions. They are written for an alpha-stage system whose direction is local-first, Thing-owned data and user-controlled boundaries. If you do not agree with these terms, do not use the launch surfaces.
reBe is in early access. Some parts are public narrative, some are working software, and some describe the direction of the architecture before the full product and support model are packaged. Use the launch surfaces as previews, learning tools, and fit-exploration surfaces, not as guaranteed production infrastructure.
The reBe direction is not a traditional cloud service where the platform collects your data and promises restraint. The goal is that your Thing owns its Corpus and chooses which device, Realm, team, organization, or network boundary can use it. Hosted launch surfaces may still receive messages, waitlist requests, Studio interactions, payment/account events, and diagnostics you intentionally submit.
Sovereignty is power, and power creates stewardship. As reBe becomes more local and more owned by the Thing, you become responsible for the choices that used to be hidden inside a platform account.
reBe Intelligence is meant to help structure questions, clarify needs, and route context to the right capability, flow, team, or human. During launch it may use a mix of local, Realm, and bounded external routes depending on the surface and what is available. Do not put sensitive or regulated information into a launch interaction unless you understand the route, boundary, and permissions involved.
Studio pieces, videos, notebooks, presentations, audio, and linked sites are educational and collaborative materials. They may include opinions, alpha design direction, and work in progress. External links are provided for context; their operators remain responsible for their own content, terms, and policies.
reBe content and early intelligence interactions are not legal, medical, financial, security, compliance, procurement, or professional advice. Use them to explore and structure your thinking, then involve qualified people for decisions with real-world consequences.
Launch-stage surfaces can change, break, move, or disappear. We may update these terms, revise public materials, change routes, or retire alpha features as the architecture matures. We will try to keep important changes understandable, but early access should be treated as evolving work.
To the fullest extent allowed by law, reBe Labs is not liable for indirect, incidental, special, consequential, or punitive damages, or for loss of data, profits, business, goodwill, or availability arising from launch-stage use. You are responsible for your own backups, recovery planning, and operational choices.
These launch terms are governed by the laws applicable to the reBe Labs operator, unless a written agreement says otherwise. Future commercial or organizational deployments may require separate agreements, support terms, data-processing terms, and jurisdiction-specific review.
Questions about these terms or data responsibility? Contact the reBe team.
Last updated: June 2026. This is launch-stage policy language and may change as reBe's local, Shell, Studio, and Realm surfaces mature.