Product Changelog

Transparent updates on improvements, fixes, and new capabilities to our platform.

We update this page regularly to keep customers informed about what’s new, what’s improved, and what’s been fixed across the product.

Last updated: December 15, 2025

Cadence: Bi-weekly

Latest Update

  • Added initial support for partner-specific configurations in development environments to support upcoming integrations.
  • Introduced early backend support for promotional and discount code workflows within checkout and billing experiences.
  • Continued improvements to the signup and checkout experience, including component refinements and preparation for promotional code support.
  • Improved consent form usability by refining layouts and fillable fields to make completion clearer and more accessible for users.
  • Progressed backend logic supporting enhanced consent flows and transcript-related workflows to ensure consistent processing across partner-driven use cases.
  • Ongoing frontend refinements to improve validation, data entry behavior, and overall user experience.
  • Resolved issues preventing users from adding or updating required personal information in certain scenarios.
  • Addressed multiple bugs identified during testing and code review, improving platform stability.
  • Strengthened consent enforcement controls by restricting access to certain external endpoints unless required consent forms are completed.
  • Continued review and validation of consent documentation workflows.

Past Update

  • Released a new partner-facing External API, enabling secure third-party integrations with the platform.
  • Introduced an enhanced identity theft alerts experience, allowing users to review alerts, confirm activity, and receive guided next steps when support follow-up is required.
  • Added new consent workflows to support partner-driven onboarding, including updated consent pages and preparation for automated form handling.
  • Refactored core frontend components to improve consistency, reduce legacy complexity, and prepare for future UI enhancements.
  • Improved signup and authentication workflows to support a smoother onboarding experience.
  • Continued advancing the design system and UI standards to support upcoming product updates.
  • Resolved multiple frontend issues across signup, validation, plan selection, and dashboard layouts to improve overall stability.
  • Implemented public identifier encryption to ensure internal system identifiers are not exposed to external partners.
  • Strengthened auditability around consent handling and alert confirmation actions.
  • Published public API documentation and sandbox resources to support partner technical review and early integration testing.
  • Released a dedicated sandbox environment for external integrations, enabling partners to validate authentication, request/response formats, and webhook workflows.
  • Clarified sandbox expectations to ensure predictable partner testing without exposure to live data.
  • Clarified sandbox expectations to ensure predictable partner testing without exposure to live data.
  • Designed the sandbox environment to operate without live IRS data, reducing risk and protecting sensitive information.
  • Implemented isolation controls to ensure sandbox activity is decoupled from production systems.
  • Made significant progress toward releasing the External API, including partner-facing consent experiences and alert workflows.
  • Deployed early improvements to the identity theft alerts interface to provide clearer user guidance.
  • Enhanced security controls to ensure partners only receive masked, non-sensitive identifiers.
  • Improved authentication flows through early testing of a new login and access-control system.
  • Advanced design foundations to support upcoming features and onboarding improvements.
  • Addressed various bugs and deployment issues across backend and frontend systems to maintain platform reliability.
  • Improved internal data protection practices for partner integrations.
  • Updated compliance-related documentation and technical controls to support SOC 2 readiness.
  • Began development of new partner connectivity infrastructure to support external integrations.
  • Initiated work on a partner-facing consent experience for customer authorization and data access.
  • Established new internal service improvements to support alerts, notifications, and subscription handling.
  • Enhanced internal authentication services and database performance.
  • Improved internal workflows for issue tracking, deployment visibility, and response SLAs.
  • Updated SOC 2–related documentation and technical specifications.
  • Strengthened authentication and access-control foundations in preparation for external integrations.

How we manage Changes

We follow a structured release and change-management process to ensure updates are reviewed, tested, and communicated consistently:

  • All changes are reviewed by Engineering and Product Management
  • Updates undergo QA and compliance review
  • Product publishes change summaries at least bi-weekly
  • Security-related changes are communicated at a high level, without exposing sensitive details

Need Help?

Visit our Help Center or contact support: