Parity

Privacy policy

Effective date: April 29, 2026

This policy covers the Parity Figma plugin (the "plugin") and the website at parityplugin.design (the "site"). It explains what we collect, why we collect it, and how it flows between the plugin, our servers, and the third parties we rely on to run the product.

Who we are

Parity is a solo-developed product. Contact: support@parityplugin.design.

What we collect

From the plugin

  • Figma user identifier. A short opaque string assigned by Figma. We use it to count audits per person and to associate a Stripe customer with your Figma account.
  • Audit inputs. When you submit a URL or an image for audit, we process that content on our servers long enough to produce a review. We do not retain the source URL, image, or extracted page data after the audit finishes.
  • Audit outputs. The review findings we return to you. After the audit completes, the plugin saves a copy of the findings to your review history. Review history is stored locally on your device by Figma's plugin storage — it is not uploaded to Parity's servers. You can delete entries at any time from the History screen.
  • Usage counters. How many audits you've run in the current month, and when the counter resets. This is how the free tier's monthly quota is enforced.
  • Product telemetry. Coarse events like "plugin opened", "audit completed", "paywall shown", and which screen the user was on when a paywall triggered. These events never include audit content or the URL/image you submitted.

From the site

  • Request metadata. Standard HTTP data like IP, user-agent, and referrer, held by our hosting provider for a limited window to mitigate abuse. We do not use this data for advertising or cross-site tracking.
  • Checkout data. When you start a checkout or open the billing portal, your Figma user identifier is sent to Stripe as the customer reference so Stripe can link the subscription back to your Figma account.

What we don't collect or keep

  • We don't collect or store the content you submit for audit beyond the audit lifecycle. URLs, uploaded images, and the extracted page data we capture to run the review are held only for the duration of the audit and then discarded. Your review history lives on your device, not on our servers.
  • We don't use your submissions to train AI models. Audit content is not retained by Parity for training, fine- tuning, or evaluation. See the section below for how Anthropic handles the same content on its side.
  • We don't use advertising cookies, retargeting pixels, or third-party analytics trackers beyond those explicitly listed below.
  • We don't collect content from your Figma files except the specific frame you export for an audit.
  • We don't collect or store your Figma authentication tokens — the plugin runs inside Figma's sandbox and authenticates via Figma's provided APIs.

How audit content flows through Anthropic Claude

Parity's review engine is powered by Claude, operated by Anthropic PBC. When you run an audit, the Figma frame (or image, or URL screenshot) and the DOM / metadata we extract are sent to Anthropic's Claude API over HTTPS so the model can generate findings. This is the only way Parity can produce a review.

Once content reaches Anthropic, it is subject to Anthropic's handling terms for the Claude API, not ours. That means:

  • Anthropic may retain the request briefly to operate the service, detect abuse, and improve reliability. Retention periods, logging, and regional processing are defined by Anthropic and can change over time.
  • Parity uses Anthropic's paid API offering, which under Anthropic's current published terms does not use customer content to train generally-available models. We rely on Anthropic's published terms for this commitment — you should read them directly if the specifics matter to you.
  • If you submit content to Parity, that content becomes subject to Anthropic's data-handling practices for Claude in addition to ours. If you can't or don't want to send specific content to Anthropic, don't submit it to Parity.

The authoritative references for how Anthropic treats this data are Anthropic's Privacy Policy and the Anthropic Commercial Terms. We'll update this section if our relationship with Anthropic or the model we use materially changes.

Who we share data with

  • Anthropic PBC (Claude API). — the AI provider that generates audit findings. See the section above for exactly what flows through Anthropic and how it's handled.
  • Stripe, Inc. — payments and subscription management. Stripe receives your Figma user identifier, email address (if provided at checkout), payment information, and billing details necessary to process the transaction.
  • Google Cloud (Cloud Run) and Supabase. — hosting and database. The Parity audit service runs on Google Cloud Run in us-central1 (Iowa). Usage counters and billing associations are stored in a Supabase Postgres database hosted on AWS in us-east-2 (East US, Ohio). Review history is not stored on either — it stays on your device.
  • PostHog, Inc. — product analytics. Receives the telemetry events described above (event names, tier, source type, error codes — no audit content). Configured with US-region ingest.
  • Sentry (Functional Software, Inc.). — server-side error monitoring. Receives stack traces and sanitized request context when a backend error occurs. Request bodies (which may contain audit content) and user identifiers are stripped before events are sent.
  • Vercel. — hosting for this website. Receives standard HTTP request metadata.

We don't sell your data to anyone, and we don't share it with advertisers or data brokers.

How long we keep data

  • Audit source content (URLs, uploaded images): deleted shortly after the audit finishes.
  • Review history (on your device): the plugin keeps recent audit findings in Figma's local plugin storage on your machine. You control retention — delete an entry from the History screen and it is removed. Parity's servers never receive these entries.
  • Usage counters: we retain rolling monthly counters for quota enforcement and anti-abuse, typically thirteen months.
  • Billing records: retained as required by tax and accounting law, typically seven years.
  • Telemetry events: retained by PostHog per our configured retention window (initial setting: twelve months).

Your rights

You can email support@parityplugin.design to:

  • Request a copy of the data we hold about you.
  • Ask us to delete your account and associated data, except billing records we're legally required to retain.
  • Cancel your subscription, which you can also do yourself from the Account page.
  • Ask any other question about how your data is handled.

Children

Parity is a professional design tool and is not directed at children under 13. We don't knowingly collect data from children; if you believe we have, please contact us and we'll delete it.

International users

Our infrastructure is located in the United States. If you use Parity from outside the US you consent to your data being processed in the US, subject to applicable law.

Changes to this policy

We'll update the "effective date" above when we revise this policy. Meaningful changes will be announced through the plugin, via email to active subscribers, or both.