J-Cubed Agent OS

Privacy Policy

Last updated: 10 August 2026

This policy explains how J-Cubed Agent OS ("Agent OS", "we", "us") accesses, uses, stores and shares information — including data obtained through Google APIs — when you connect a Google account to it.

In one line: Agent OS reads your calendar so your AI Chief of Staff can see your schedule. It is read-only, it is never sold or used for advertising, and you can disconnect it at any time in one click.

1. Who we are

J-Cubed Agent OS is operated by J Cubed (J³), a marketing and automations studio. It is a private, invitation-only console used by J Cubed staff and clients to operate a fleet of AI assistant agents. Contact: hello@j3marketing.ai.

2. What Agent OS does

Agent OS is a web console for supervising AI assistant agents. One of those agents is a Chief of Staff, which prepares daily schedule briefings, surfaces deadline collisions, and checks availability before proposing meeting times. To do that, it needs to read the calendars of the people it supports — which is why Agent OS offers a "Connect Google Calendar" action.

Access to Agent OS requires an account issued by J Cubed. There is no public sign-up.

3. Google user data we access

We request the narrowest scopes that make the feature work:

Scope	Why we need it
`openid` `email`	To identify which Google account was connected, so it can be labelled in the console and disconnected later. We store the email address only.
`.../auth/calendar.readonly`	To list the calendars on the connected account and read their events, so the Chief of Staff can build schedule briefings, detect conflicts and check availability. This scope is read-only — it cannot create, modify or delete anything.

The specific fields we read

Calendar list: calendar id, name, time zone, access role, and whether it is your primary calendar.
Events: id, title, start and end time, all-day flag, location, organizer email, status, and Google Meet link.

We do not read attachments, attendee lists beyond the organizer, event descriptions, Gmail, Drive, Contacts, or any other Google service.

4. How we use it

To display a merged agenda inside the Agent OS "Calendars" view, to the person who connected the account.
To let the Chief of Staff agent summarise the day's schedule, flag deadline collisions and priority conflicts, and check availability before suggesting times.

That is the complete list. Calendar data is not used for any other purpose.

5. What we never do

We never sell, rent or trade Google user data.
We never use Google user data for advertising, retargeting or profiling.
We never transfer Google user data to data brokers, information resellers, or any third party for their own purposes.
We never allow humans to read your calendar data, except with your explicit consent, for security investigations, or where required by law.
We never use Google user data to train generalised AI or machine-learning models.

Agent OS's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. How the data is stored and protected

Refresh tokens are encrypted with AES-256-GCM before being written to disk. The encryption key is held in the server environment, never in the database.
Access tokens are held in server memory only and are never written to disk.
Data lives on a private, access-controlled server operated by J Cubed. The database is not publicly reachable.
All traffic between your browser, our server and Google is encrypted in transit over HTTPS/TLS.
The OAuth exchange happens server-side. Tokens are never exposed to the browser.
Per-user isolation is enforced: only the person who connected an account can see that connection or its events. This applies to administrators too — an Agent OS admin cannot view another user's calendar.

Calendar events and the AI agent

To produce briefings, event data is sent to the large-language-model provider that powers the Chief of Staff agent, strictly as the content of that request. It is processed to generate the response and is not used by us to train models.

7. Retention and deletion

We retain the encrypted refresh token and the connected email address for as long as the connection is active.
Calendar events are fetched live from Google on demand and are not stored in a long-term events database.
When you disconnect an account, we revoke the token with Google and delete the stored record immediately.
If you close your Agent OS account, all associated calendar connections are revoked and deleted.

8. How to revoke access

Either of these fully removes our access:

In Agent OS, open Calendars and choose Disconnect on the account. This revokes the token at Google and deletes it from our database.
Or visit myaccount.google.com/permissions, select Agent OS, and choose Remove access.

9. Other information we hold

Separately from Google data, Agent OS stores the account we issued you (email address and a hashed password) and standard server logs used for security and debugging. Logs do not contain calendar event content.

10. Children

Agent OS is a business tool and is not directed to anyone under 16.

11. Changes to this policy

If we materially change how we handle Google user data, we will update this page and revise the date above. Where the change requires it, we will ask you to re-consent.

12. Contact

Questions, access requests or deletion requests: hello@j3marketing.ai.