Principles.

The published list of refusals. What Aperture doesn't do, and why.

Each is backed by Terms of Service, Privacy Policy, or pricing canon. Quarterly re-verified where applicable.

  1. 01

    Facilitator-only architecture, no Aperture-collected participant data.

    Aperture-as-company doesn't collect or retain participant data for our own use. No analytics, no AI training inputs, no aggregation across facilitators. Facilitators may optionally collect participant names for their own session use, with informed consent. That data is facilitator-owned, visible only to them, never touched by Aperture for any other purpose, and deleted when the session is deleted.

    → Privacy § 1

  2. 02

    No AI training on saved selections.

    Subprocessors configured with training-off where the provider offers AI features, and named publicly on our subprocessor list. Quarterly re-verified.

    → Verification log

  3. 03

    Courts, not arbitration.

    If we screw up, you can sue Aperture in court. We don't bind buyers to arbitration.

    → ToS § 1.7

  4. 04

    No automated decision-making technology (no ADMT).

    Buyer-facing decisions are never made by algorithm without a human in the loop.

    → ToS § 1.13

  5. 05

    Narrow UGC license.

    We license only what's necessary to operate the service.

    → ToS § 1.9

  6. 06

    No data-broker status.

    We don't sell or share participant data.

    → ToS § 1.12

  7. 07

    Per session, never per participant.

    Flat-rate regardless of workshop size. Five participants or fifty, the work is the work.

    → Pricing

  8. 08

    Rate locked at signup.

    Continuous subscribers keep their original price for the life of the subscription. No mid-subscription bumps.

    → Pricing

  9. 09

    We don't A/B test the covenant.

    What's on the pricing page is what we offer, not what we're optimizing.

    → Pricing + Curation

  10. 10

    No customer data sold for advertising.

    Standard privacy commitment.

    → Privacy § 6

How we hold ourselves to this.

Subprocessors

We name every subprocessor publicly. Each is configured with training-off where applicable. Material changes are notified to customers via email and a posted update.

Full list →

Quarterly verification

Every 90 days, Aperture re-verifies subprocessor configurations: training-off status, DPA currency, role scope. Each verification is timestamped and logged.

Last verified 2026-05-22. Next due 2026-08-20.

Full log →