← Back to homeTransparency

Know who processes what, and where.

UseGlic is built and operated by USE GLIC TECHNOLOGIES LIMITED. This page lists the current subprocessors and summarises the controls that shape the data path. Contractual terms, transfers and safeguards are confirmed in the applicable signed customer agreement.

Hosting and model routing

The workspaces run in the EU region.

UseGlic operates its workspace in the EU region by default. You can set your organisation's data region in workspace settings, and Enterprise or white-label deployments can pin a specific region for data-residency needs. In production, every model call goes to AWS Bedrock through UseGlic's model-routing layer; no other model providers are used and there is no fallback outside Bedrock. Where model inference and connected services process data depends on the regions and settings selected for your workspace, and some model routing can cross regions. UseGlic reviews the data path for each workflow before go-live.

Current subprocessors

Who processes what.

Updated 3 November 2026. Customer-facing notice is given before a new subprocessor is introduced; changes to this list are announced on this page. Connected tools such as Slack, Microsoft Teams, Gmail or Salesforce are configured on your own accounts and act under their own terms — they are not UseGlic subprocessors.

Provider	Service provided	Data used	Location
Amazon Web Services	Cloud hosting and agent runtime; model inference runs on AWS Bedrock routed through UseGlic's model-routing layer	Workspace data, prompts and outputs	EU region (Ireland) by default; workspace data region can be Europe, United States or Asia Pacific; some model routing can cross regions
Stripe and/or Razorpay	Subscription payments, invoices and payment records	Billing contact and payment metadata	Determined by the payment provider
Amazon SES	Transactional email delivery (verification, invitations, notifications)	Email address and message content	AWS
Cloudflare	Website and application edge delivery, TLS and bot protection	Web request data for sites served by UseGlic	Global edge network
Instantly (and previously Hunter)	Sourcing business contact details for business outreach	Professional names, work email addresses, roles and employers	Determined by the provider

Workspace controls

How data stays separated.

Tenant isolationTenant data is never shared across tenants. Workspaces use per-tenant roles and keys, and workspace roles determine who can request, inspect, manage and change settings.

Credential handlingNo raw provider keys or tokens are stored in code. Agent-specific credentials are provisioned through managed secret references, and the permissions an AI teammate receives are limited to what its connections grant.

Logging boundariesPrompts, outputs and document contents are not written to application logs. Audit records capture the user, agent, event type and action details for each recorded action, including approval decisions and policy decisions.

Network accessAgent network access is customer-configurable: agents can reach destinations unless a super admin blocks them. Review the current rules during setup; a default-deny allowlist is a separate configuration.

CookiesThe marketing website does not use advertising or analytics cookies. The Command Centre uses essential session cookies for login and security only.

CertificationsUseGlic does not currently hold a SOC 2 or ISO 27001 certification, and this page is not an audit report or certification statement.

Customer documents

Where the binding specifics live.

Retention periods, encryption specifics, transfers, safeguards and itemised processing terms are confirmed in the applicable signed customer agreement and its data-processing terms. For a review of the data path for a specific workflow, or to request the current subprocessor list, contact hello@useglic.com. Security inquiries and vulnerability reports go to security@useglic.com. See also the security overview, the security policy and the privacy policy.