Product

J-Cubed Agent OS

The private console J Cubed uses to run, watch and talk to its fleet of AI assistant agents.

Invitation only · no public sign-up

What it is

J Cubed builds AI assistants that do real operational work for a business — sorting an inbox, drafting content, tracking deliverables, chasing what has gone quiet. J-Cubed Agent OS is the control room for those assistants: one place to see what every agent is doing, review its output, correct it, and hand it new work.

It is used by J Cubed staff and by the clients whose agents we operate. Accounts are issued by us directly; there is no public registration.

The Chief of Staff agent

One agent in the fleet is a Chief of Staff. Its job is to protect its owner's attention: tell them what today actually looks like, warn them when two commitments collide, and stop meetings from being booked over the work that matters.

It cannot do any of that without seeing the calendar — which is the one reason Agent OS asks for Google Calendar access.

Connecting a Google Calendar

You click "Connect Google Calendar" in the Calendars section of Agent OS. Nothing is connected until you do.
Google asks for your consent on Google's own screen. You choose which account to connect. We never see your Google password.
Agent OS lists your calendars and shows a merged agenda — visible only to you.
The Chief of Staff reads that agenda to build your daily briefing, flag conflicts and check availability before proposing times.
You disconnect whenever you want, in one click. We revoke the token with Google and delete it.

What we ask for, and why

Read your calendars

calendar.readonly — lets the Chief of Staff list your calendars and read event times, titles and locations to build briefings and spot conflicts. Read-only: it cannot create, change or delete anything.

Know which account it is

openid and email — so the connected account can be labelled in the console and disconnected later. We store the address, nothing more.

We do not request access to Gmail, Drive, Contacts or any other Google service.

How your calendar data is handled

Events are read live from Google when a view or briefing needs them — not copied into a long-term events database.
The token that permits access is encrypted with AES-256-GCM before it touches disk, and the OAuth exchange happens entirely server-side.
Only you can see your calendar in Agent OS. Administrators cannot view another person's connections or events.
Your calendar data is never sold, never used for advertising, and never used to train models.

Full detail

The Agent OS Privacy Policy sets out exactly which fields we read, how they are stored and protected, how long they are kept, and how to revoke access. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions about Agent OS or about data we hold: hello@j3marketing.ai.