Account & security

Data and privacy

What Inverity stores, and what happens to your media.

This page covers the practical questions teams ask before connecting a production library. For the formal terms, see the privacy policy at inverity.ai.

What Inverity holds

Your connector credentials, stored encrypted, and used only to access the assets you point Inverity at. See Tokens and permissions.

Your media, in order to process it. Optimization requires reading the asset and producing an optimized copy.

Your results. Original size, optimized size, savings, and the decision made per asset — this is what the dashboard shows you.

Your account and workspace records. Team members, roles, plan, and usage.

What Inverity does with your media

It optimizes it and writes the result back to your platform. That's the whole purpose, and the boundaries around it are the useful part:

  • Assets outside your watched locations are never read. Scope is the control you hold. See Choose what to optimize.
  • Nothing is deleted from your platform. There is no delete path.
  • Nothing is written back that failed the quality check. See How write-back works.

Controlling scope

The strongest privacy control available to you is scope. Inverity only reaches what you point it at, so:

  • Keep assets that must not be processed outside your watched locations.
  • Start with a single test folder before widening.
  • Review your watched locations when your library reorganizes — a folder that gets moved into a watched parent becomes in-scope.

Disconnecting and deletion

Removing a connector stops Inverity accessing that platform. Revoking the token in the platform itself makes the credential useless regardless — do both, and revoke first if you're responding to an incident.

Optimized assets stay in your platform. Disconnecting doesn't reverse past work, and it can't: the optimized files are yours and they live in your system.

For data deletion requests, or questions about retention periods, contact support@inverity.ai.

Questions from a security review

If you're being asked to complete a vendor security questionnaire or a DPA before connecting Inverity, email sales@inverity.ai — that's handled alongside Architect and procurement.

Regulated or rights-managed content

If your library contains regulated, licensed, or rights-managed material, treat the rollout the way you'd treat any other processor: scope it deliberately, start with a test collection, and involve whoever owns that policy internally before you widen. See DAM connectors.

Previous
Security