pages.trustSecurity.heroEyebrow

pages.trustSecurity.heroHeadline

pages.trustSecurity.heroLede

00pages.trustSecurity.introEyebrow

pages.trustSecurity.introTitle

pages.trustSecurity.introBody

01pages.trustSecurity.q1Eyebrow

What data does StandIn process?

pages.trustSecurity.q1Body

That includes:
  • Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • User-authored wraps and declarations
  • Minimal user identifiers required for attribution and access control
That includes:
  • Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • User-authored wraps and declarations
  • Minimal user identifiers required for attribution and access control
  • Minimal user identifiers required for attribution and access control
  • Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

02pages.trustSecurity.q2Eyebrow

What data does StandIn process?

pages.trustSecurity.q2Body

That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control
That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

03pages.trustSecurity.q3Eyebrow

What data does StandIn process?

pages.trustSecurity.q3StorageLabel
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control
That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control

StandIn's compliance posture follows directly from its product design. The system only processes what people explicitly write and choose to publish. This is data minimization by architecture, not by policy configuration. There are no background syncs, no behavioral signals, no inferred data. What you write and publish enters the system. Everything else stays invisible. The FAQ below describes how that design maps to GDPR, data retention, and security controls.

04pages.trustSecurity.q4Eyebrow

What data does StandIn process?

StandIn processes only explicitly published wraps and declarations authored by users.

That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control

StandIn's compliance posture follows directly from its product design. The system only processes what people explicitly write and choose to publish. This is data minimization by architecture, not by policy configuration. There are no background syncs, no behavioral signals, no inferred data. What you write and publish enters the system. Everything else stays invisible. The FAQ below describes how that design maps to GDPR, data retention, and security controls.

05pages.trustSecurity.q5Eyebrow

What data does StandIn process?

StandIn processes only explicitly published wraps and declarations authored by users.

That includes:
  • Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • User-authored wraps and declarations
  • Minimal user identifiers required for attribution and access control
That includes:
  • Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • User-authored wraps and declarations
  • Minimal user identifiers required for attribution and access control
  • Minimal user identifiers required for attribution and access control
  • Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

06pages.trustSecurity.q6Eyebrow

What data does StandIn process?

The LLM does not have access to your systems.

That includes:
  1. 1StandIn retrieves already-stored, published data within your org boundary
  2. 2That bounded context is sent to the LLM
  3. 3The LLM generates a response
  4. 4The context is discarded
That includes:
  • Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • User-authored wraps and declarations
  • Minimal user identifiers required for attribution and access control
  • Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

07pages.trustSecurity.q7Eyebrow

What data does StandIn process?

StandIn processes only explicitly published wraps and declarations authored by users.

That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

08pages.trustSecurity.q8Eyebrow

What data does StandIn process?

  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

09pages.trustSecurity.q9Eyebrow

What data does StandIn process?

The LLM does not have access to your systems.

That includes:
  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control

If something is not intentionally written or explicitly connected, StandIn does not see it.

10pages.trustSecurity.q10Eyebrow

What data does StandIn process?

That includes:

  • —Read-only metadata from systems of record (for example issue titles, status, assignees, URLs)
  • —User-authored wraps and declarations
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control
  • —Minimal user identifiers required for attribution and access control
  • —Private messages or DMs

If something is not intentionally written or explicitly connected, StandIn does not see it.

11pages.trustSecurity.summaryEyebrow

What data does StandIn process?

The LLM does not have access to your systems.

pages.trustSecurity.ctaEyebrow