Your Work Is Personal.
Know Where It Goes.
A plain-language guide to Globster’s access, memory, files, background work, approvals, and data controls.
Assurance in Progress
We are working toward SOC 2 and ISO 27001. These are planned milestones, not certifications or audit reports already held by Globster.
Audit preparation in progress
Certification work in progress
You Choose What to Connect.
Globster works with the apps, accounts, and tools configured for your agent. A connected account’s permissions and provider scopes determine what it can access. Connecting an app does not grant access to every account or every action.
Explore connected appsUseful Context Can Carry Forward.
Saved memory and conversation history are different. Your Globster agent can use saved facts about people, projects, and preferences in later work. Review, correct, or remove saved memories as things change. Removing a saved memory does not delete the independent conversation history.
Understand agent memoryA Workspace for the Work You Share.
Each Globster agent has its own workspace for source files and deliverables. Upload the material you want it to work with and review the files it creates. Runtime isolation and configured permissions define the environment around that work.
Read about isolationConnect Accounts. Keep Secrets out of Chat.
Use provider authorization or the platform’s credential controls instead of pasting passwords and API keys into messages. Managed connections and custom credential slots use scoped access; how a credential is consumed depends on the integration.
How credentials are handledMake Review Part of the Process.
Configure which actions need your approval. When approval is required, the agent pauses for your decision. Not every action asks first by default: your approval policy and connected account permissions matter.
Explore approval controlsOngoing Work Should Have a Clear Purpose.
An agent can work through a longer task and revisit work through configured routines. A goal defines an outcome; a routine must be configured and activated to return on a schedule. Review the work, access, and schedule you give it.
How routines workHosted Agents. Connected Providers.
Globster uses Microsoft Azure as its cloud foundation and NVIDIA OpenShell for the hosted runtime boundary. Your selected model and connected services also take part in the work. Ask us about data-handling requirements for your specific setup before sharing sensitive material.
Explore the runtime boundaryAsk Us About Your Data.
For questions about retention, deletion, model-provider data use, or an organization’s requirements, contact the team. We’ll help clarify the applicable setup and terms. This page does not promise a universal retention period or model-training policy.
Contact supportYour Privacy Settings Are within Reach.
Use Privacy choices or Cookie Settings on this website to review your analytics and advertising preferences. The privacy policy explains the applicable handling of personal information.
Read the privacy policyBuilding toward Enterprise Assurance
SOC 2 and ISO 27001 work is in progress and marked Coming Soon. Globster does not yet claim completed certification or an issued SOC 2 report. Enterprise identity, data residency, retention and deletion controls, model-training commitments, and service levels are planned; confirm availability and terms with us before rollout. Runtime controls do not make an agent immune to every security risk.
Discuss your requirementsSomething You Want to Understand Better?
Tell us what matters to you or your team. We’ll help you find a clear answer.
support@globster.ai