sdlc.cc / customer setup

Put privacy controls in front of every AI chat.

One operator screen for browser users and desktop users. Policies store metadata only; prompt content never appears here.

1. Connect your gateway

Use the operator bearer issued with your private appliance or hosted tenant. The bearer stays only in this page's memory — never written to localStorage.

0. Pilot activation

After connecting, run one guided activation: upsert the organization, ensure an observe policy for the cohort, issue a managed client key (scrub + policy:read), and download managed config plus content-free evidence and rollback records.

Managed configuration (Chrome/Edge storage.managed)

Copy this key now.

Evidence and rollback records never include the plaintext key or admin bearer. Checkout redirects are not entitlement.

1. TenantIQ connector

Issue a document:scan key and download the non-secret connector pack TenantIQ loads after Graph extraction. sdlc.cc never receives SharePoint paths or mailbox IDs — only extracted text. Contract: docs/TENANTIQ_CONNECTOR.md.

Copy this document:scan key now into TenantIQ secrets (SDLC_DOCUMENT_SCAN_KEY).

2. Organization

Give this installation an owner and a deployment mode.

3. Privacy policy

These detectors are enforced by the gateway for Browser Guard and Desktop Guard scrub requests. Choose whether Browser Guard auto-sends scrubbed text, holds for a second confirmation, or blocks. Optionally record content-free reports when someone tries to send matching data. Select a saved policy to update it without creating a competing policy.

4. Access keys

Issue one tenant key for each Browser Guard, Desktop Guard, add-in, connector, or API installation. Use M365 connector (document:scan) only for TenantIQ SharePoint/mailbox extractors — never for Browser Guard. The secret appears once and is never stored in this console.

Copy this key now.

After you close or refresh this page, only its safe prefix remains visible.

5. Usage and rollout

Review counts and statuses without exposing message content. Detection reports appear only for policies that opted in.

—requests (7 days)
—cost (USD micros)
—saved policies

Detection attempt reports

6. Rollout

Move one cohort at a time from observation to enforcement. The stage shown is what the gateway would actually apply to that cohort right now, resolved the same way the gateway resolves it.

Install checklist

  1. Save the organization and issue a separate tenant key for each installation. Copy it into Browser Guard, Desktop Guard, or the supported add-in once; it cannot be recovered here.
  2. Set the browser extension endpoint to this gateway and distribute it through Chrome/Edge management.
  3. For native ChatGPT, Claude, Gemini, and other desktop apps, open the Desktop Guard secure composer — hosted or private appliance — and copy only its clean output.
  4. Run a redaction test, then switch from observe to redact when the team is comfortable.
  5. For SharePoint or mailbox analysis, run TenantIQ connector above: store the document:scan key in TenantIQ and load the connector pack — do not put Graph IDs into sdlc.cc.
  6. Invite operators only after rotating the admin bearer. This MVP uses a single operator token; SSO/SCIM is a full-product milestone.