Terms of Service

Membase is operated by Unibase (“we”, “us”). These terms are an agreement between you and us. If you are using Membase for an organization, you are confirming you may accept these terms for it.

You need an account to use the hosted service. Keep its credentials to yourself: anything done with them is treated as done by you. Tell us at support@unibase.com if you believe someone else has reached your account.

You must be old enough to enter a contract where you live. One person, one account; organizations get an account per member rather than a shared login.

What you put into Membase — notes, documents, captured conversations, anything a container holds — remains yours. We do not claim ownership of it.

We need a narrow permission to run the service: to store your content, process it so search and retrieval work, and show it back to you and to the agents you authorize. That permission exists to operate Membase for you and for nothing else. It ends when you delete the content or close the account.

These are the controls, and they are not conditional on anything:

• Read and correct. Every fact Membase holds can be opened and edited.
• Export. Take a full copy out at any time.
• Delete. Remove a memory, a container, or the account.
• Scope. Access is per container, so an agent can be given one project without being given the rest. Revoking it takes effect immediately.

Do not use Membase to:

• break the law, or help someone else do it;
• store or distribute material you have no right to, including someone else's personal data you were not permitted to collect;
• attack the service or anything it connects to — probing for weaknesses without our written agreement included;
• work around limits, quotas or access controls, or let someone reach through your account whom you would not give access to directly;
• resell access to the hosted service as if it were your own.

Reporting a security problem you found is welcome and is not a breach of these terms, provided you tell us before you tell anyone else and do not take or damage data that is not yours.

API keys identify your account. Treat them as credentials, keep them out of client-side code and public repositories, and rotate them if they leak.

We may apply rate limits to keep the service usable for everyone, and may change them. Breaking changes to the API are announced before they take effect, not after.

An agent you connect acts with the access you gave it. Give it the containers it needs and no more — the scoping exists for that reason.

Nothing today. Membase is not charging for any feature at the moment, and no payment method is required to use it.

If that changes, we will say which features are paid, what they cost, and from when, before any charge is made — and you will be able to decline and keep using whatever remains free. Nothing you already stored becomes inaccessible because a price was introduced: export stays available regardless.

We work to keep Membase running, but we do not promise it is never unavailable. Maintenance, outages and failures of services we depend on all happen.

The product changes. Features are added, and occasionally removed; when something you rely on is being removed we will say so in advance and in the changelog, with enough notice to export or adjust.

You can stop at any time: delete your account in the web app. Export first if you want a copy — deletion is meant to be real, so we cannot retrieve it afterwards.

We may suspend or close an account that breaches section 4, or where we are required to. Except where the law or an active investigation prevents it, we will tell you why and give you a chance to export first.

Membase is provided as it is. Retrieval is a search over what you stored: it can return the wrong passage, and an answer built from your memory can be wrong. Check anything that matters before acting on it — particularly before acting on something an agent produced from it.

To the extent the law allows, we are not liable for indirect or consequential loss, lost profits, or lost data where you had the means to export and did not. Nothing here limits liability that cannot be limited.

We may update these terms. The date at the top says when they last changed. If a change materially reduces your rights we will tell account holders before it takes effect, rather than relying on you to re-read this page.

Questions about these terms, or anything else, go to support@unibase.com.

The Chrome extension privacy policy is published separately and covers that extension only. A policy covering the web app, the desktop app and the API is not yet published; ask us and we will send what applies before you sign up.