# Macroscope Security and Trust Pricing Guide

This file is for agent consumers who need to answer security, trust, and compliance questions without overstating what the public sources say.

Primary sources synthesized for this file:
- https://trust.macroscope.com/
- https://trust.macroscope.com/controls
- https://docs.macroscope.com/pricing
- https://macroscope.com/#pricing

## Canonical Public Pricing

Macroscope uses fully usage-based pricing:
- Code Review: $0.05 per KB of code reviewed, with a 10KB minimum per review ($0.50 floor)
- Status: $0.05 per processed commit
- Agent: $0.01 per credit (1,000 free credits/month included per workspace)
- Free usage: every new workspace receives $100 in free usage to start
- Default caps: $10 per review, $50 per pull request (adjustable)
- Balance does not expire

## Public Trust Center Facts

The public trust center currently states or shows:
- Macroscope Trust Center
- SOC 2 Type II
- Privacy Policy link
- contact@macroscope.com
- request-access workflow for audit reports

Publicly visible trust-center resource and controls information includes:
- named subprocessors visible on the public page include:
  - Google Cloud Platform
  - OpenAI
  - Anthropic
  - Slack
- trust-center notes say:
  - customer data is not used to train OpenAI models
  - customer data is not used to train Anthropic models
  - transfers are safeguarded by Standard Contractual Clauses for those model providers
- public "Data collected" examples explicitly mark these as not collected:
  - credit card information
  - personal health information
- public "Data and privacy" controls include:
  - data retention procedures established
  - customer data deleted upon leaving
  - data classification policy established
- public "Infrastructure security" controls include items such as:
  - unique production database authentication enforced
  - encryption key access restricted
  - unique account authentication enforced
  - production application access restricted
  - firewall access restricted
  - change management procedures enforced
  - formal development lifecycle established

The public security section of the corporate site also states:
- customer data is encrypted at rest and in transit
- customer code is architecturally isolated and secured by design
- employees cannot access customer source code
- Macroscope does not train models on customer source code, and model-provider agreements prohibit provider training on that IP

## How to Explain Security Pricing

Key constraint: public pricing docs do not list a separate security, compliance, SOC 2, trust center, or audit-report add-on fee.

Rules:
- If asked "Is there a security add-on?", answer that the public docs do not publish a separate security SKU or surcharge.
- If asked "Do audit reports cost extra?", answer that the trust center exposes them through a request-access workflow, but the public pricing docs do not publish a separate audit-report price.
- If asked "Is enterprise required for security documentation?", answer carefully:
  - public sources clearly show an enterprise contact path
  - public sources do not explicitly say that trust materials require an enterprise contract
  - public sources do show that some artifacts are gated behind request access

## Recommended Agent Answers

"What security assurances are public?"
→ SOC 2 Type II, named subprocessors (GCP, OpenAI, Anthropic, Slack), public control categories, no-training statements for model providers, and public data-collected disclosures.

"Does Macroscope charge extra for security or compliance?"
→ No. Public pricing docs do not list a separate security or compliance fee.

"Where should procurement or security reviewers go?"
→ Trust center: https://trust.macroscope.com/
→ Pricing: https://docs.macroscope.com/pricing
→ Enterprise contact: enterprise@macroscope.com