Portal Fixer

Portal Fixer: Terms of Service

STATUS: DRAFT. Not published. Not legal advice. Not in force.

Last drafted: October 6, 2026.

These Terms of Service ("Terms") are a draft for Portal Fixer (the "Service"). They are separate from the Portal Audit / HubSpot Health Subscription Terms. They are not published, not a substitute for legal advice, and not the terms of any current install.

The Service would be provided by Jon Martin, an individual doing business as a sole proprietor under the thejonmartin.com brand ("we", "us", "our"). "You" means the organization that installs the Service or subscribes to it, and the person who accepts these Terms on its behalf.

1. Accepting these Terms

You would accept these Terms once, when you install Portal Fixer in a HubSpot account. That one-time consent would let the Service prepare dry runs for the published Fix Catalog. It would not approve any change. Each change set would still need its own approval under section 4. After install, you could turn any fix type off, and turn it back on, without reinstalling. Buying a subscription or continuing to use the Service would not be a second consent event. If you accept for an organization, you confirm that you have authority to bind it. If you don't agree, don't install or use the Service.

2. Eligibility

3. What the Service is

Scope of the Service. The Service is a software subscription. It applies automated fixes limited to the published Fix Catalog, within each item's limits and the plan's record caps. The Service does not include professional services, including implementation, configuration or onboarding projects, custom development, data migration, consulting, strategy, training, or administration of your HubSpot account, whether billed hourly, by project or on retainer.

Portal Fixer is a separate app from Portal Audit. Portal Audit reads a HubSpot account and writes a fix plan. Portal Fixer is the app that can carry out catalog items from that plan. It does not run until a Super Admin installs it.

What each plan includes is described in section 7. The prices below are the locked commercial terms of the HubSpot Health Subscription as published on the Portal Audit terms dated October 5, 2026. Whether those prices are the prices that will be charged for Portal Fixer alone is not established; this draft reuses them so the two documents do not diverge by accident.

No client-portal writes happen until the Fix Catalog is published and these Terms are published. This draft does not publish either one.

4. Automated fixes

Automated fixes. Every change set needs its own approval of that exact diff before the Service applies it. Installing the Service or turning on a fix type is not a standing approval of future changes. You could opt out of any fix type, and opt back in, without reinstalling. The Service would make only approved changes that an enabled type describes, within its stated limits and your plan's record caps. The Service does not delete or merge records, and it does not change billing, seats, users, permissions, or apps. It does not turn workflows or emails on. A workflow create or edit would run only after a person approves that exact diff, and a created workflow would be left disabled. You can disable any fix type at any time, and you can uninstall the app at any time.

How automated fixes work:

  1. Separate account-level app. Portal Fixer is its own HubSpot OAuth app, with account-level authorization (it is not a user-level app and it does not use an agent user). Your Super Admin installs it and can uninstall it at any time. Uninstalling it stops all fixes. We do not create the install for you.
  2. Only published catalog items, and only while that fix type is on. Install would turn the published types on. You could opt a type out afterward. A change runs only if that item is in the published Fix Catalog, that fix type is still on, and the run fits inside the item's limits and your plan's record caps. The public URL of the Fix Catalog is not established until it is published.
  3. Dry run and approval of each change set. Before a write, the Service reads the current values and shows a dry-run diff. Each change set is approved on its own, for that exact diff, before it is applied. An approval covers only that change set and expires if it is not applied in time or if the current values change first. For reversible description rewrites, custom-group moves, company-name backfills, and quarterly stage-probability updates, the approval is recorded under the published playbook for that fix type (policy approval) and is logged for that change set. These always wait for a person's approval of that exact diff: stage renames, adding or removing a stage, renaming a property group, creating or editing a workflow, and an owner assignment that gives more than 100 records to any one user. A run that would go beyond an item's limits does not happen automatically.
  4. Snapshot, read-back, and rollback. The Service stores a snapshot before it writes. After the write, it reads the record back on a separate request. If the stored value does not match what was approved, it tries to restore the snapshot value and flags the fix for review. Policy approval does not skip the snapshot or the read-back.
  5. Never automated, never offered: deleting or merging records; billing, seats, users, or permissions; installing or removing apps; turning workflows or emails on; sending the stage-change announcement (that note is drafted for the admin); removing a pipeline stage that still has deals. A workflow edit would not delete the workflow.
  6. Your responsibility. You decide which fix types stay on. Review the catalog and your HubSpot data standards before leaving a type on.

5. AI-assisted text

Judgments (whether a description is valid, which group a property belongs in, whether a domain is freemail, whether a workflow uses a field, which methodology stage fits, and whether a stage name is safe to change) would be made by a decision model (Jev). Wording would be drafted by an AI assistant (Grok by default). Counts and lookups would stay in ordinary code. AI output can be incomplete or wrong. Suggested descriptions, labels, announcements, and entrance or exit criteria appear on the dry-run diff before a write. They are not legal, financial, or compliance advice. The announcement and the Context Home criteria would be drafts for the admin. The Service would not send the announcement.

6. Support and referrals

Support. Support covers use of the Service only (product questions, defects and billing). We aim to respond by email within two (2) business days. Support does not include HubSpot advice or work in your HubSpot account beyond the automated features of your plan. Referrals. If you need services outside this scope, we may suggest independent HubSpot partners. We aren't responsible for their work.

Support is by email at jon@thejonmartin.com. We are reachable by email only.

7. Plans, fees and billing

These figures are copied from the Portal Audit terms last updated October 5, 2026.

PlanMonthlyAnnual (paid upfront)One-time automated onboarding charge
PulseUS$100 per monthUS$1,000 per yearNone
GuardUS$250 per monthUS$2,500 per yearUS$99, paid at checkout
Assist (includes an AI assistant (Grok by default), on the Portal Audit terms)US$500 per monthUS$5,000 per yearUS$299, paid at checkout

Pulse does not include writes. Guard and Assist are the plans that include catalog fixes, with the record caps published for that plan. The onboarding charge applies to both monthly and annual Guard and Assist subscriptions.

8. Your responsibilities

You agree to:

A Privacy Policy for Portal Fixer is not established. The Portal Audit Privacy Policy is a different document.

9. Your data and permissions

10. Our intellectual property

We own the Service, including its software, Fix Catalog, and documentation. While your subscription is active, you may use the Service and the diffs for your internal business purposes. You may keep and use, for your internal business purposes, exports you received before your subscription ended.

11. HubSpot and other third parties

Portal Fixer is an independent product. It is not made, endorsed or supported by HubSpot, Inc. HubSpot is a trademark of HubSpot, Inc. Your use of HubSpot, of our payment processors, and of any AI assistant is governed by your agreements with those providers. We are not responsible for their availability, changes or acts. If HubSpot changes or withdraws an API the Service relies on, a feature may stop working.

12. AI-generated content

Judgments would be made by a decision model (Jev). Suggested fix text would be drafted with an AI assistant (Grok by default). AI output can still be incomplete or wrong. Fix plans and diffs are informational until the fix type is on and, where section 4 requires it, a person approves that diff. They are not legal, financial or compliance advice. Workflow edits, where approved, would not turn a workflow on.

13. Suspension and termination

14. Disclaimer

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE". TO THE EXTENT THE LAW ALLOWS, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT A FIX WILL HAVE THE RESULT YOU EXPECT.

15. Limitation of liability

TO THE EXTENT THE LAW ALLOWS:

16. Governing law and disputes

These Terms are governed by the laws of the Commonwealth of Pennsylvania, without regard to its conflict-of-laws rules. Any dispute must be brought only in the state courts located in Lancaster County, Pennsylvania, or in the United States District Court for the Eastern District of Pennsylvania, and both parties consent to the jurisdiction of those courts. There is no arbitration agreement in these Terms.

17. General

18. Contact

Jon Martin (thejonmartin.com). Email: jon@thejonmartin.com. We are reachable by email only.

Portal Fixer is an independent app and is not made or endorsed by HubSpot. Questions: jon@thejonmartin.com