The Changelog 🎉

Keep up with the latest releases to Scanii.com with our change log 🚀

2026.3

Updated legal and data protection documents

We have revised our customer-facing legal documents so that they describe how Scanii actually works today and hold up to the due diligence our customers in the EU and UK are asked to perform. The Data Processing Addendum now uses the 2021 EU Standard Contractual Clauses (Module Two, or Module Three where you act as a processor for your own customers) with the UK International Data Transfer Addendum, relies primarily on our EU-U.S. Data Privacy Framework, UK Extension and Swiss-U.S. DPF certifications with the clauses as an automatic fallback, and includes a rewritten Annex I that states exactly what we retain, where, and for how long: file contents deleted on analysis, result records kept in your processing region for up to 400 days and deletable through the API, and only a small set of job metadata (identifiers, findings, timing and client information, never content type, size, checksum, file names, URLs or your custom metadata values) sent to our US control plane. It also adds an explicit return-and-deletion clause, a 30-day advance notice commitment for new sub-processors, and fields for your legal entity name. Existing signed DPAs remain in force; you can execute the new version from the same page.

The Terms of Service incorporate the DPA and the SLA by reference, so the availability commitment is now contractual for paid plans; add a plans, fees and renewal section that documents credits, automatic renewal, 30 days' notice of price changes and how mid-term plan changes affect your credit balance; correct the controller/processor roles to match the DPA; and describe termination and deletion consistently with it (downgrading to the free tier keeps your account, deleting the account starts deletion of your data within 30 days). The Privacy Policy has been rewritten in a conventional structure with the data we actually collect, our legal bases, a real retention schedule, an accurate cookie and analytics section, and the current list of sub-processors and service providers, which the DPA references. Our Website Terms of Use shrank to a page and now permit reuse of documentation code samples.

The Security Overview was updated alongside them to use the same wording as the DPA on regions, retention and the metadata that leaves your processing region, and to reflect our current backup rotation, log retention and container-based patching. If you have a signed DPA on file or an open security review with us, nothing changes for you today; if you would like to move to the new DPA, sign it from the DPA page and it replaces the earlier version. Questions to privacy@uvasoftware.com.

Better URL sanitization. Whenever we capture URLs, we now redact not only credentials but also query parameter values.

API Analysis result  deletion . You can now remove a processing result, its trace, or both, whenever you need to.

  • DELETE /v2.2/files/{id}      deletes a processing result
  • DELETE /v2.2/files/{id}/trace      deletes the processing trace for that result
  • The two are independent. Deleting a result leaves its trace readable, and deleting a trace leaves the result readable — to erase a scan entirely, call both.
  • Both return 204      when something was deleted and 404      when there was nothing to delete, so you always know whether your call removed anything. A repeated delete returns 404     , which is safe to treat as success.
  • Deletion requires an API key. Temporary authentication tokens — the short-lived credentials meant for browsers and other untrusted clients — cannot delete.

Deletion is permanent.

Performance and resilience improvements. We've rolled out a new content analysis architecture across all of our regions. Analysis now runs on its own autoscaling fleet instead of sharing capacity with the API, so heavy content no longer competes with request handling — in our highest-volume regions, 99th-percentile analysis times have roughly halved. It also runs through a durable pipeline, so analysis continues uninterrupted through deployments and infrastructure changes.

2026.2

We rolled out significant improvements to our search infrastructure, delivering 3x better search performance.

We've spent the last few months rebuilding our developer tooling from the ground up. Here's what's new:

Eight official SDKs, all current — We now ship official, open-source SDKs in Java, .NET, Go, Node/TypeScript, PHP, Rust, Ruby, and Python (Python coming soon). All eight follow the same three principles: zero runtime dependencies, always current with the latest API, and integration-only (no surprise retries or hidden concurrency). Every SDK is installable from its language's standard registry — Maven Central, NuGet, npm, Packagist, crates.io, RubyGems, and PyPI.

📓 See the full lineup at https://docs.scanii.com/article/146-language-clients

v2.2 API surface across all SDKs — Every official SDK now supports the v2.2 API, including the new trace endpoint for inspecting processing events on a per-result basis (preview), and synchronous URL submission via the location        parameter on POST /files        .

Refreshed scanii-cli         — Our local mock server has been updated to support the full v2.2 surface. If you use scanii-cli         for local or CI testing (and you should — it's the same tool we use), pull the latest image from ghcr.io/scanii/scanii-cli:latest        .

New setup-cli-action         for GitHub Actions — We've published an official GitHub Action that handles cross-platform installation and startup of scanii-cli         in your CI pipeline. One line in your workflow, works uniformly on ubuntu/macos/windows runners.

- uses: scanii/setup-cli-action@v1

API versioning policy, documented — We've also published a clear policy on how the Scanii API evolves and how SDKs handle version transitions. Short version: old majors stay supported indefinitely, additive changes ship anytime, and breaking changes only happen at new majors.

📓 Read it at https://docs.scanii.com/article/170-api-versioning-policy

2026.1

Introducing the Scanii Trust Center

We're making it easier than ever for your security and compliance teams to evaluate Scanii. Here's what's new:

  • Trust Center at trust.scanii.com — A dedicated portal where you can review our security posture, request compliance documents, and access the information you need during vendor evaluation — all in one place.
  • Redesigned security page — Our security page has been restructured around the questions buyers actually ask during due diligence: data handling, encryption, infrastructure, and compliance posture. Every claim has been reviewed against our privacy policy and security overview for accuracy.
  • SOC 2 compliance in progress — We've partnered with Drata to formalize our compliance program and are actively working toward SOC 2 certification. More details to come as we progress through the audit process.
  • Updated security overview — Our security overview documentation has been refreshed to reflect current practices, including our metadata hashing approach, updated encryption details, and revised data handling disclosures.

2025.4

You can now search for user supplied metadata

Now available in the US1 region, you can tag your resources with custom metadata and search by those values to find exactly what you need. Whether you're tracking customer IDs, project codes, environment markers, or team assignments, your metadata stays private—we hash the data so your original values are never stored in the search index.

Keep in mind that searches must match exact values (no partial matches), but that precision is exactly what makes it powerful. If organizing and retrieving resources has been a pain point, this should help.

See our search guide for details

Unsafe Image engine now supports PDF files

Our engine can now identify unsafe images stored inside PDF files expanding on our already long list of support image types.

To learn more read our engine support article


2025.2

All new administrative UI

Greetings, everyone. We are pleased to announce the release of version 4 of our administrative UI at www.scanii.com. This update addresses long-standing requests from our users, including:

  1. Introduction of a new analytics engine and dashboard, enabling visualization of up to 12 months of historical data with single data point fidelity. We also provide comparison time ranges to give you a better sense of your usage over time and all new filtering so you can visualize your usage by actor/key or region.
  2. All new time picker giving you both relative and absolute data picking ability.
  3. All new search that is faster and searches across more dimensions of your data.
  4. The UI is now responsive, so you can access scanii on the go from your favorite mobile device.
  5. Improved integration with Stripe, our payment processor
  6. Revamped security event tracking and SIEM integration

2025.1

New Region Announcement: CA1 in Canada

We’re excited to announce the launch of Scanii’s newest processing region, CA1, running on AWS ca-central-1 in Canada!

This expansion is driven by customer demand and reinforces our commitment to data sovereignty, providing organizations operating in Canada with greater control over their data. With this new region, Scanii continues to offer secure, scalable, and efficient content scanning, now with enhanced regional support for compliance and performance needs.

This is part of our ongoing effort to bring Scanii closer to our users worldwide—expect more to come!


📍 New Region: CA1 (Canada) with endpoint https://api-ca1.scanii.com

📓 Unsafe image detection is not currently available in this region due to a provider limitation

🚀 Available Now to all customers!


For more details visit: https://docs.scanii.com/article/161-endpoints-and-regions

2024.2

  • We launched our all-new command line interface which includes a built-in test server that closely mimics our production endpoint and can be used to local (or continuous) integration testing.

Here's what it looks when you start up the test server:

The CLI is open source (APL) and available from here: https://github.com/uvasoftware/scanii-cli

2023.6

2023.3

  • All of our global endpoints now support TLS v1.3 along with TLS v1.2
    • To find out how TLS v1.3 helps protect our customers, please reference this article
    • An exact Cypher list can be found here
  • New v4 UX
    • We are beginning the rollout of our all new web portal interface, expect things to look better and more modern
    • We are starting with public pages first and will move on to the logged in experience in the coming weeks
  • Improvements to our AI model use for unsafe language detection improves detection of violent, explicit and suggestive content

2023.1

  • We rolled out a series of performance improvements significantly improving the p99 response times for our API across all regions
  • We updated our Privacy Policy, it now better complies with the California Consumer Privacy Act
  • Our terms have also been revised to better comply with EU regulations 

2022.2

  • Improvements to unsafe language detection engine, lowering overall FP 
  • New versions of our dotnet, php and java clients revving up dependencies and addressing some usability quirks

2022.1

  • All new documentation site and in-application contextual search 📗

2020.3

  • New version of S3/Lambda client v1.5.0

2020.2

  • New version of Java client v3.8.0
    • You can now target one of our 2 new regions; AP2 and EU2
  • New version of DotNet client v3.3.1
    • You can now target one of our 2 new regions; AP2 and EU2
    • NSFW image detection improvements
      • 2x improvement in accuracy of our NSFW engine under certain circumstances
      • Expanded ipv6 support across all global regions
    • New version of our PHP client v3.2.0
      • You can now target one of our 2 new regions; AP2 and EU2
      • We now test against MacOS, Linux and Windows
      • Support for PHP 7.3 and above
      • Accounts API (beta) support
      • Model refactor (breaking change warning)
      • Improved debug logging (thanks @tomworks ) #9
      • Upgraded phpunit to 9.x #8
    • New version of S3/Lambda client v1.3.
    • Added support for parallel deploys, you can now deploy multiple independent versions of scanii-lambda by simply giving it different application names.
    • Bumped node runtime to latest v12x

2019.4


Two new regions: AP2 in Singapore and EU2 in London

    • Singapore / Singapore - api-ap2.scanii.com
    • London / United Kingdom - api-eu2.scanii.com

This release marks our fifth API endpoint and furthers our commitment to not only support the data sovereignty of our users but also ensure the quickest API responses as we continue to expand our presence across the globe.

Customers using our latency routed endpoint (api.scanii.com) traffic will begin to flow to the closest region automatically, otherwise, setting your endpoint to your preferred location will ensure your files are processed solely from the region of your choice.

A full list of available regions/domains can be found here .


We are dropping support for TLS 1.0 and 1.1 in March of 2020


In order to ensure that we’re meeting our compliance requirements and providing our customers with the highest possible level of security, we are going to be dropping support for TLS protocol version 1.0 and 1.1 along with weak cyphers on March 1st 2020.

For a specific list of protocol and cyphers being added/removed please reference this chart - we will be moving from bundle 2016-08 to TLS-1-2-2017-01.

If your API client already supports TLS 1.2, there is nothing for you to do, otherwise, you should consider upgrading your dependencies (or runtime) to a newer version.

If you have any questions or concerns, please contact support at support@uvasoftware.com .


New version of our SAM-packaged AWS Lambda client v1.3.0

  • Added support for parallel deploys, you can now deploy multiple independent versions of scanii-lambda by simply giving it different application names.
  • Bumped node runtime to latest v12x
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us