Privacy Policy

Last updated: August 2026

Orb2 is self-hosted software. It runs entirely on hardware you control. Your conversations, files, camera, microphone, and connected-account data are processed on your instance and are never received by the author. Two small, optional convenience relays are the only Orb2-operated services, described below — each is minimal, purpose-bound, and can be switched off.

1. Who this covers

Orb2 ("the software") is an open-source, single-user AI assistant published by Martin Nicolas Ausilio (the "author"). You install and operate your own instance. You are the data controller for everything your instance processes.

2. What data the software handles

Your conversations, files, and settings — stored locally in your instance (on your machine), never sent to the author.
Connected accounts — if you choose to connect Google or Microsoft, the software requests OAuth access tokens so it can act on your behalf. Tokens and any retrieved content stay on your instance.
Model inference — by default the AI model runs locally on your hardware. If you configure a remote/cloud model endpoint yourself, your prompts are sent to that endpoint under your own terms.

3. Connected accounts & scopes

Connecting an account is optional and initiated by you. The software requests only the scopes needed for the features you enable, for example:

Google — Drive (read your files), Calendar (read your events), and, where you enable it, Gmail. Used to display and act on your content inside your own instance.
Microsoft — OneDrive (files), Outlook mail, and Calendar, via Microsoft Graph, for the same purpose.

The software uses this access solely to provide the features you request within your instance. It is never used for advertising, profiling, sold, or shared with third parties.

Google Limited Use disclosure. Orb2's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide user-facing features within your own self-hosted instance, is not transferred to others except as necessary to provide those features at your direction, is not used for advertising, and is not read by humans except with your consent or as required for security/legal reasons.

4. Optional Orb2-operated relays

Two narrow convenience services run at orb2.app so a fresh install works out of the box. Both are optional:

Sign-in email relay — if you haven't configured your own SMTP, your instance sends the relay an email address and a one-time sign-in code, used solely to deliver that one email (via the Resend email service) and not stored by the relay. Opt out by configuring your own SMTP or setting ORB2_OTP_RELAY_URL="".
Device-address relay — if you enable a *.device.orb2.app hostname, your instance sends the relay a random device id and your box's LAN IP address so DNS can point the name at your box and a certificate can be issued. The relay holds only DNS records; the private key for your certificate never leaves your instance. Off unless you enroll.

5. Where your data lives

On your instance. Outside the two relays above (which see only what's listed), your data is never received by the author. Connected-account tokens are stored in your instance's local store and used only to make API requests from your instance directly to the provider.

6. Revoking access & deletion

Disconnect any account from Orb2's Settings at any time — the stored token is deleted from your instance.
Revoke access from the provider directly: Google account permissions · Microsoft app access.
Delete your instance's data by removing its local storage/volumes.

7. Children

Orb2 is not directed to children under 13 and should not be used by them.

8. Changes

This policy may be updated; the "last updated" date will change accordingly. Material changes will be noted on this page and in the GitHub repository.

9. Contact

Questions: open an issue at github.com/MrQbit/0rb.