Orbit

Trust & account safety

Clear permissions before clever behavior.

Trust starts by making the current boundary understandable: which account is connected, what Orbit receives, where the record lives, and what the product still cannot do.

Current checkpoint

Orbit can

Receive. Store. Show.

Orbit cannot

Reply. Publish. Guess.

These are product boundaries, not a security certification. Orbit will publish approved legal and security documentation before public launch.

Product boundaries

Safety you can inspect.

01

Credentials stay with their provider

Google and Instagram handle their own credentials. Orbit never asks for or stores either password.

02

Creator data remains tenant-scoped

Creator reads are scoped to the active workspace and connected account before any inbound record is returned.

03

The checkpoint is inbound-only

The current product receives and displays DMs and comments. It does not send replies or modify Instagram content.

04

Product state stays explicit

Preview controls are disabled and illustrative data is labeled. Future behavior does not masquerade as a live backend.

Know what Orbit is doing.

Connect one creator workspace and keep every capability inside a visible permission boundary.