Your data is part of your digital self.

The Principle

reBe is built around a different starting point: the most important data about a Thing should live with that Thing, under its control. Your Corpus, memories, questions, files, and local intelligence are not meant to become our platform assets.

What reBe Can See

When you visit this public website, we may process limited operational data:

• Site diagnostics: page requests, referrers, browser details, and basic server logs.
• Messages you send: email, waitlist, support, or Studio-related requests you choose to submit.
• Payment or account flows: handled only when you choose a hosted service or Studio Pass path.
• No sale of data: we do not sell personal data or use your private Corpus to train models.

What Belongs With Your Thing

In the reBe model, your Corpus, private notes, local AI interactions, Chronicles, imported files, and device-held memory are yours. When they run locally or in a Realm you control, they are not available to us unless you deliberately export, share, sync, back up, or send them.

Responsibility Comes With Power

Owning your digital self changes the risk model:

• If you lose a device without recovery, your local data may be gone.
• If you share a key, file, backup, or Realm invite, that choice has consequences.
• If you delegate memory to an agent, you must understand what boundary it can act inside.
• If you become responsible for another person's data, you inherit a duty of care.

Hosted Services

Some launch experiences still use hosted infrastructure: this website, Studio, account and payment flows, email, and operational logs. Those systems are narrower than your Corpus. They help us run the public service; they are not the place your private intelligence is supposed to live.

Your Choices

You can:

• Ask what hosted account, payment, or support data we hold about you.
• Request deletion of hosted records where deletion is legally and operationally possible.
• Export or move your local Corpus and Realm data when the relevant tools are available.
• Choose not to connect hosted services when local use is enough.

Data Retention

We keep operational logs and hosted service records only as long as needed for security, debugging, support, payment/account operations, and legal obligations. Local Corpus data under your control is not retained by us because it is not ours to retain.

Compliance

Data protection law still matters. reBe's architecture aims to reduce what we collect and clarify where responsibility sits, but this page is not a substitute for a formal legal notice in every jurisdiction. The launch policy will keep evolving as the product moves from public site to local app, Shell capability, and owned Realm.

Contact

Questions about privacy, responsibility, or data recovery? Contact the reBe team.