Service Terms

These terms cover the Harbor service — the accessibility widget, our API, scanning and the dashboard. If you are here about an audit engagement or about using this website, those are covered by the Terms of Service instead.

Last updated: 2026-08-21. This version is in force, and it is the version an account created on or after that date records agreement to.

What this is

The hosted terms that have to exist before a stranger can sign up. LICENSE covers the code a browser receives; this covers the service it talks to. PRIVACY.md covers what the widget's network request carries. Nothing here is meant to overlap with those, and where it repeats them it is because a customer reading only this file still needs the fact.

Two clauses in here are the reason it was written first rather than later: assignment on change of control (section 17) and aggregate research rights (section 11). Both are cheap to have on day one and expensive to add afterwards, because adding either later means asking every existing customer to agree again and getting a fraction of them back. Everything else in this document could have waited.

Where this is published, and why not at /terms. These terms are published at harboraccessibility.com/service-terms. /terms was already occupied when this document was written, by the terms covering the website itself and the audit engagements sold through it — a different agreement, for a different product, with published delivery commitments that another page on the site restates and links to. Replacing it would have deleted those. Two products, two agreements, two URLs, each pointing at the other.

1. Who we are, and what you are agreeing to

These terms are between Harbor Accessibility Co. ("Harbor", "we", "us") and the person or organisation that opens an account ("you").

Harbor Accessibility Co. is a single-member limited liability company organised under the laws of the Commonwealth of Pennsylvania, United States, with its registered office at 502 W 7th St STE 100, Erie, PA 16502. There is no "LLC" in the name and that is not an omission — Pennsylvania accepts "Co." as the entity designator.

They cover the Harbor service: the accessibility preferences widget, the site records and configuration our API serves to it, scanning, drafted fixes, the remediation log, the dashboard, and any paid plan. They apply from the moment you create an account, and they apply to the free plan exactly as they apply to a paid one.

One thing to know before the rest of it: today, only the Free plan can be opened. Nothing that takes a card is built. Every paid plan, price, renewal, refund and dunning rule described below is what will apply when those exist, not something you can buy this morning. It is written out now because these are the terms the first customer agrees to and both of the clauses that matter most (sections 11 and 17) have to be there from the beginning — but a document describing billing for plans nobody can buy invites you to wonder what else in it is aspirational, so: that is what, and this is the only place it happens.

Two documents sit alongside these terms and are part of your agreement with us:

Privacy — the privacy policy published at harboraccessibility.com/privacy, which is the document these terms incorporate. (PRIVACY.md in the widget's repository is its technical companion, describing the widget's network request in more detail than a site-wide policy can. Where the two differ in specificity that one is the more precise account of the widget; neither overrides the other.)
Licence (LICENSE) — the permission under which the widget's code runs in your visitors' browsers.

If this document and either of those conflict, tell us; one of them is wrong and we would rather fix it than argue about precedence.

2. What Harbor does not do, stated first

This section is deliberately at the top, and it is the same section that has led our README since before we sold anything.

Harbor does not make your website conformant with WCAG, compliant with the ADA, the European Accessibility Act, or any other law or standard, and we never claim that it does. No plan, no scan, no fix, and no amount of money buys that claim from us.
Harbor does not reduce your legal exposure, and we do not accept your legal obligation. Under the ADA and equivalent regimes elsewhere the obligation belongs to the business operating the website. No vendor can assume it, and a vendor telling you otherwise is selling you something they cannot deliver.
The widget is not remediation. It changes how a page is presented to one visitor, in one browser, who chose to change it. The underlying page is unchanged for everyone else, including for every visitor who never opens the panel. It adds no alt text, no headings, no ARIA and no keyboard handling to your page.
Our scans do not find every barrier. Automated checking finds a minority of real accessibility problems. A clean scan is not a clean site. We do not sample to WCAG-EM, we do not issue conformance verdicts, and a Harbor report is not an audit.
Our fixes are drafted, not certified. On the plans that include them we produce the best fix we can and you decide whether it is right. That approval is a real step and it is yours.
We do not replace an audit, expert review, or testing with disabled users.

You may say your site uses Harbor. You may not say your site is "accessible", "WCAG conformant", "ADA compliant" or "certified" because it uses Harbor, and you may not attribute any such claim to us. We take this seriously enough to make it a term of the contract: see section 8.

3. Your account

One email address, one account, no password. You sign in by asking for a link and following it from your inbox. There is nothing else to steal, which is the point — we store no password, so we cannot lose one.

The consequence is stated plainly, because it is the whole security model: whoever controls your email address controls your Harbor account. Not a password, not a second factor — the mailbox. Protect it accordingly, and prefer an address more than one person at your organisation can reach if the account matters to your business.

If you lose access to that address, we have no other way to verify that you are you. We will not hand an account over on the strength of an assertion, an invoice or a friendly support conversation, because exactly the same evidence is available to anyone who wants to take your account from you.

There is one other way back in. If you have a site registered with us, ask and we will give you a token to publish as a DNS TXT record on that site's domain. Publishing it proves you control the domain, which is evidence nobody can talk their way past — it is the same control your account already implicitly rests on, and unlike a support conversation it cannot be charmed.

Where neither the mailbox nor the domain is available to you, there is no recovery. That sentence is unpleasant to write and it is the honest one: every alternative is a social-engineering path into somebody else's account.

Sign-in links expire in 15 minutes and may be opened at most five times. Do not forward one. The allowance exists because mail security systems open links before you do, not because a link is meant to be shared. Anyone who follows it is signed in as you.

Sessions last 30 days. Signing in on a shared machine and walking away hands the account over for a month.

One account is one owner. Multi-user accounts do not exist yet. If several people need access today they are sharing a mailbox, and you should assume the account is only as private as that mailbox is.

You must be old enough to enter a contract where you live, and if you are opening the account for an organisation you must be authorised to bind it.

4. Site keys

Every site you register gets a site key. It goes in a <script> tag on every page:

<script src="https://cdn.harboraccessibility.com/v1/s.js" data-account="site_..."></script>

A site key identifies a site. It authorises nothing. It is public by design: anyone who views source has it, and anyone can fetch that site's record and read the same configuration your visitors' browsers were already being served. This is not a leak and we do not treat it as one. Your account is protected by your session, never by the key.

Two things follow, and both are your side of the arrangement:

Do not treat a site key as a secret, and do not build anything of your own that depends on one being hard to guess. If a key ever appears to be doing the work of a credential, that is a bug on our side and we want to hear about it.
Install a key only on a site you own or are authorised to operate. Pasting someone else's key into your pages, or yours into theirs, breaches these terms.

Site keys count against your plan's site limit: 1 on Free and Starter, 3 on Source, 25 on Agency, 5 on Guided.

We do not yet offer self-serve deletion of a live site key, because deleting a key removes the widget from a live page and that deserves a confirmation path and a grace period, neither of which is built. Ask us and we will do it.

5. The service is a runtime dependency of your website, and you should know what that means

When you install Harbor, a script we serve loads on every page view of your site, and on each page view it asks our API for that site's record. That is what lets a fix we make reach every installed site on the next page load rather than whenever each site owner next redeploys. It also means we are in your critical path, and there is no version of that sentence that is not a real cost to you.

What we have built to keep the cost small, and what we hold ourselves to:

Stored preferences apply before first paint, with no network at all. A returning visitor's settings are read from their own browser; our API is not involved in applying them.
A failed request never switches the widget off. Our client treats only an explicit "inactive" answer from us as a definite no. A timeout, a 5xx, a DNS failure, a blocked request — all of them mean "carry on with what you had".
Our own errors are reported as our errors. When our storage fails we answer 503, never a 402 or 404, because those would switch off a paying customer's widget because we had a bad afternoon.
A first-time visitor to a site whose record we have never served will not see the widget while we are unreachable. That is the honest limit of everything above and we are not going to pretend otherwise.
The payload is not pinned by you. A mutable second stage is what buys automatic updates, and it is also what removes your ability to audit one fixed file. If that trade is wrong for your site, data-widget-src lets you pin the payload to a URL you control.

We do not offer a service level agreement, and we are not going to invent one before we have operated long enough to know what we could keep. We will publish a status page and we will tell you about incidents that affected you.

No plan carries a service level agreement, including the paid ones, and none will until we have operated long enough to know what we could promise and then keep. If that changes, it will be published with the plan it belongs to rather than buried here.

We may change the service. Fixes, new checks and improvements to the widget ship continuously, and that is the arrangement you are buying. If we remove something you were relying on, or make a change that materially reduces what your plan includes, we will tell you before it takes effect and you may cancel and take a pro-rata refund of anything you have paid for time you will not get.

6. Plans, prices, and what you are paying for

The current plans are Free, Starter $9/month or $79/year, Source $49/month or $490/year, Agency $149/month or $1,490/year, Guided $499/month or $4,990/year, and quoted Engagements from $2,500. Prices are in US dollars and exclude any tax we are required to add.

Two rules govern what sits in which plan. They are commitments, not descriptions of a current arrangement:

The widget is never gated. Every control, every visitor, unlimited traffic, at every tier including Free. We do not hold widget features back to sell a plan and we do not intend to start.
Findings are never gated. You always see what is wrong with your site, in full. The Free plan limits how much of your site we look at; it never shows you a number and withholds the detail. Starting a scan needs an account because a crawl has to belong to somebody; seeing what it found never costs anything.

What money buys is remediation and scale: the drafted fix, the permanent version of the fix, the dated record of it, and doing all of that across more than one site.

The full entitlement matrix is published with the plans. If it and this document disagree about what a plan contains, the published matrix as it stood when you subscribed governs.

Taxes. Prices exclude sales tax, VAT, GST and equivalents. Where we are required to collect them we will add them at checkout.

Nothing is being collected today, because nothing can be bought today. Before the first paid plan opens we will register where we are required to and name those jurisdictions here. Pennsylvania taxes software sold as a service, so the first one is the state we are sitting in.

There is no payment processor. When there is, it will be named here and in the privacy policy's sub-processor list before it receives anybody's card details, along with anything in its terms we have to pass through to you.

7. Billing, renewal, cancellation, and what happens when a subscription ends

No card at signup. The free plan asks for an email address and a URL, and nothing else.

Subscriptions renew automatically — monthly plans monthly, annual plans annually — until you cancel. Annual is collected up front, in full.

You can cancel at any time, from the dashboard. Cancelling stops the next renewal. It does not end the current period: you keep the plan you paid for until the day it is paid through.

Refunds work like this:

Annual plans: full refund of the unused portion if you cancel within 30 days of the charge, and a pro-rata refund of the unused portion after that.
Monthly plans: we do not refund part of a month. You keep the month.
If we materially reduce what your plan includes, or we close your account for a reason that is not your breach, you get a pro-rata refund of time you paid for and will not receive.
Beyond that we use our judgement, and it tends to be generous — but this document should not be read as promising something specific that it does not.

If you are a consumer, your statutory rights come first and the paragraph above does not cut them down. In the EU and the UK a consumer buying a service at a distance ordinarily has 14 days to withdraw from it, and where you ask us to begin immediately you may be asked to acknowledge that the right ends once the service has been fully performed. This is written in the conditional because no paid plan exists yet; the exact wording gets checked against those rules before one does.

Downgrades take effect at the end of the period you have paid for, not immediately. If your new plan allows fewer sites than you have registered, you choose which sites stay inside the limit; if you have not chosen within 14 days, we keep the oldest and switch off the rest.

Upgrades take effect immediately, pro-rated against the remainder of the current period.

Failed payment. We retry, and we email you. If payment has not succeeded after 14 days of retries, the plan lapses to Free rather than the account being deleted.

Set out in detail, because a runtime dependency going away is the thing customers are right to worry about.

The site key keeps working, on the plan you have dropped to. Lapsing from Starter to Free does not remove your widget; it removes the paid entitlements from your site's record.
If the account itself is closed or suspended, we switch the widget off by answering "inactive" for that site key. The script tag stays in your pages, the request still goes out on every page view, and it comes back a definite no. The widget then mounts nothing and your page renders exactly as it would without it.
A failed request is never that answer. If our API is unreachable, a returning visitor keeps the panel and their stored preferences still apply. We cannot switch you off by accident through our own outage; only an explicit answer does it.
You should remove the script tag. We keep answering it for as long as it points at us, and it is one request per page view that is now buying you nothing.
Permanent fixes stay yours. Where an approved fix was written into your own CMS — alt text in your media library, say — it is in your database, it survives cancellation, and it survives us. That is the intended outcome, not an oversight, and nothing in these terms lets us undo it.
Your remediation log and every patch we drafted stay exportable for 90 days after the account closes, after which we delete them. That is the same 90 days the privacy policy gives for deleting account data, deliberately, so there is one number rather than two.

8. Your site, your responsibility

You remain responsible for your website. For its content, its code, its accessibility and its legal compliance. Nothing we do transfers any of that to us, and section 2 is not decoration.

You approve every change. On plans that include drafted fixes, we produce the fix and you decide. We can describe what is on a page; only you know what the page is for — whether an image is decorative, illustrative, or carrying information the surrounding text does not. That question is why the approval step exists, and approving in bulk without reading defeats the point of the product you are buying.

What we will and will not apply on your behalf. This is a safety boundary rather than a feature limit:

Apply directly — only where a fix is mechanically decidable and reversible, such as writing approved alt text into a media-library field. You approved the text; we write it where it belongs.
Suggest only — anything that edits code. We hand you the patch. You apply it, or you do not.
Refuse, with an explanation — where the source is not yours to change, such as markup emitted by somebody else's plugin. We will name the plugin and tell you what to ask its author. We will not patch around it.

Where you give us credentials, or install a connector, so that we can write approved changes into your CMS, you are authorising exactly that and nothing wider. Keep a backup. We will try hard not to break your site and the boundary above is designed around that risk, but the site is yours and the last word on any change to it has to be yours too.

Acceptable use. You agree not to:

install a site key on a site you do not own or are not authorised to operate;
use Harbor for a site whose content is unlawful where it is published;
claim, or let anyone acting for you claim, that Harbor makes a site conformant, compliant or certified, or attribute such a claim to us (section 2);
resell or sublicense the service — except that the Agency plan exists for running client sites, and that is not resale;
present a site key as a credential, or probe for accounts, keys or email addresses that are not yours;
enumerate, scrape or systematically harvest our records, or generate traffic designed to do so;
copy, modify, self-host, decompile or reconstruct the widget's code beyond the permission in LICENSE;
start a scan against a site you do not own or are not authorised to operate;
interfere with the service, or with anyone else's use of it.

Your visitors are yours to inform. Installing Harbor means your visitors' browsers make a request to our API on every page view. Under GDPR and similar regimes that is a processing activity you are responsible for disclosing, and you should assume it belongs in your own privacy policy. PRIVACY.md gives you the facts to write that with. We would much rather you over-disclose than discover later that we let you under-disclose.

9. Your data, and who owns what

Your content stays yours. Your website, your pages, your images, your text, your CMS. Scanning it gives us no ownership of any of it.

We own the service. The widget, the API, our scanning and fix-generation software, the dashboard, and everything we build. Your subscription is a right to use it, not a transfer of it.

The fixes we draft for you are yours to use, keep and take with you. Alt text we drafted and you approved, patches we handed you, the export of your remediation log — all of it, on the site it was drafted for, and after you stop paying us. Portability is the inverse of our competitors' business model and it is deliberately on our side of the line.

To run the service you grant us the permission we need to run it: to fetch and analyse pages on the sites you register, to store the findings and the log, to generate and store drafted fixes, and — where you have approved a specific change and connected your CMS — to make that change. That permission lasts as long as your account does and exists for the purpose of providing the service to you. Section 11 is the one other thing we do with this data, and it is set out separately because it deserves to be read separately.

Privacy. What the widget sends us, what we keep and what we deliberately do not collect is in PRIVACY.md — including the fact that on each site-record fetch we record the site key and the host from the browser's Origin header, and nothing about the visitor.

Roles, sub-processors and transfers. For your account we are the controller. For the widget's site-record request you are the controller for the decision to install it and we are your processor for serving the configuration back — except for the install count we take from that same request, which is ours, for our own purposes, and makes us a controller for that narrow use. For page content we fetch once scanning is live, we are your processor. Which sub-processors we use, what each receives, and the transfer mechanism for each are published in the privacy policy and kept current there rather than frozen into this document. A data processing agreement is available on request — email legal@harboraccessibility.com.

10. Analytics, and what we count

Usage analytics is off unless you turn it on, and it is available on paid plans. When it is on, the widget reports which of its own controls a visitor used — from a fixed list of five event names, with no free-text field anywhere in the payload. It never sends a URL, a page title, a referrer, a screen size, or anything a visitor typed. The session id is random per tab, exists only in memory, and is discarded on ingest.

Separately, and regardless of that setting, we count installs. On each site-record fetch we record the site key and the host from the Origin header — example.com, never a path, never a full URL, never anything about the person visiting. It is how we know how many sites are running Harbor and how many are still running it next month. That is a fact about your website, not about your visitors.

11. Aggregate research data, and the annual report

This is one of the two clauses this document was written early to contain. It is short, it is not boilerplate, and it is worth reading properly.

Nobody has good public data on accessibility across the long tail of small business websites. The best available survey covers the top million home pages. The sites that actually get sued are not in it. We intend to publish an annual public report on what we find across the sites we scan, and to make the underlying aggregate dataset available for research, because the field needs it and we are in an unusual position to produce it.

You grant us a perpetual, worldwide, royalty-free licence to use the accessibility findings and remediation outcomes generated from your sites to produce and publish aggregate, de-identified research, datasets, statistics, benchmarks and reports. The licence survives the end of your subscription, for data collected while it was in effect.

The limits on that licence are part of it, not a courtesy:

Aggregate only. We publish counts, rates, distributions and trends across many sites. We do not publish per-site results.
De-identified. Before anything is published we remove what identifies a site or a person: domains, URLs, page titles, business names, your name, your email address, and any text taken verbatim from your pages that could be traced back to them.
We never name your site. Not in the report, not in the dataset, not in a case study, not in marketing — unless you have separately and specifically agreed in writing to be named.
No visitor data, ever. Visitors' preferences never leave their own browsers and cannot be in anything we publish.
Not a customer list. We will not publish, sell or license the dataset in any form that reveals who our customers are.
Small groups get suppressed. Where a breakdown would be narrow enough that a particular site could be recognised from it — a rare platform, a small sector, a single country with few sites in it — we suppress the cell rather than publish it.

If you would rather your sites were not included even on those terms, email us and we will exclude them.

That opt-out is real, and today we honour it by hand. Email privacy@harboraccessibility.com and your sites are excluded from the dataset; it becomes a switch in the dashboard when the dashboard grows one. It is promised at this size deliberately: honouring it manually costs nothing while there is no volume, and asking an existing base for a permission you forgot to take costs everything later.

12. Third parties, and the things we do not control

We depend on other people's services to run this: hosting and edge compute, email delivery for sign-in links, and payment processing. Their failures become our failures from where you are sitting, and we do not control them.

We also do not control your CMS, your hosting, your theme, your plugins, or any change anyone else makes to your site — including a change that undoes a fix you approved. Sites change; that is precisely why the product is continuous monitoring rather than a one-off audit.

13. Warranties, and the absence of them

We will provide the service with reasonable skill and care, and we will not knowingly ship something we believe is broken.

Beyond that: THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT A SCAN WILL FIND EVERY ACCESSIBILITY BARRIER, THAT ANY FIX WILL BE CORRECT OR COMPLETE, OR THAT USING HARBOR WILL RESULT IN CONFORMANCE WITH ANY STANDARD OR COMPLIANCE WITH ANY LAW.

That last item is not a lawyer's reflex. It is the same statement as section 2, and we would make it with or without a liability clause to hang it on.

Nothing here excludes liability that cannot lawfully be excluded — including for death or personal injury caused by negligence, for fraud, and for anything else your local consumer law protects.

Where you are a consumer, the law where you live may give you rights this document cannot take away — statutory warranties, remedies where a service is not performed with reasonable care, and in the EU and UK the withdrawal right in section 7. Where anything here conflicts with those, they win and the rest of this document still stands.

14. Liability

Our total liability to you, for everything arising out of these terms or the service, in any 12-month period, is capped at the greater of what you paid us in the 12 months before the claim and $500. On a free account that is $500.

The floor is the part worth explaining rather than just stating. A cap of "one year's fees" evaluates to zero for every free-tier customer, and a zero cap is the kind courts strike as illusory — in several jurisdictions taking the surrounding clause down with it. A $500 floor costs nothing until something goes wrong, and it makes the clause survivable.

Neither of us is liable to the other for indirect or consequential loss, lost profits, lost revenue, lost business, loss of data, or the cost of substitute services.

We would rather state the shape of this plainly than bury it: on a $9 plan we are not underwriting your legal exposure, and no accessibility vendor at any price is doing that for you either. If your risk is large enough that somebody needs to carry it, what you need is an audit firm, insurance and counsel — in some combination, and probably all three.

A cap is not the control that solves the realistic worst case. That case is a bad source patch breaking a customer's site, which is not subscription-sized in either direction. What solves it is the boundary in section 8 — direct-apply only where a fix is mechanically decidable and reversible, suggest-only for anything that edits code — and, behind that, insurance. Both matter more than the number above, and the number above is not a substitute for either.

15. Indemnity

You will cover us against claims brought by someone else that arise from your website, your content, your use of Harbor in breach of these terms, or any claim about accessibility or compliance that you — or anyone acting for you — made about your site.

We will cover you against a third-party claim that the Harbor software itself infringes their intellectual property rights.

Both are conditional on the party being indemnified telling the other promptly, letting them run the defence, and not settling without their agreement.

16. Suspension and termination

You can close your account at any time. Export what you want first; section 7 says how long we keep it afterwards.

We can suspend or close an account for breach of these terms, for non-payment after the dunning period, or where we are legally required to. Unless the breach is serious or we have no choice, we will tell you what is wrong and give you a reasonable chance to fix it first.

If we close your account, your widget stops. We answer "inactive" for the site key and it mounts nothing. Your pages still render — they render as they did before you installed us. Anything already written into your own CMS stays there.

We may discontinue the service entirely. If we do, we will give at least 180 days' notice — ninety is the convention for software you can export and walk away from, and this is a script that loads on every page view of your site — refund the unused portion of anything prepaid, and keep exports available for the whole notice period. Because the widget is a runtime dependency of your pages, we will also keep serving a final entitlement response that switches it off cleanly rather than letting the hostname simply stop answering. A broken request is not how anyone should find out.

17. Change of control, and what happens to your account

This is the second of the two clauses this document was written early to contain.

If Harbor Accessibility Co. is merged, acquired, reorganised, or sells all or part of its business or assets, your account, your subscription, this agreement and the data associated with your account transfer to the acquirer as part of that transaction. You agree to that transfer now, and we do not need to ask you again at the time.

What transfers: your account and contact details, your site records and site keys, your subscription and billing relationship, your scan history, your remediation log and drafted fixes, and this agreement itself.

Being plain about why the clause is here: the customer base is the principal asset of a business like this one. If a buyer cannot lawfully take on the customer relationship, there is nothing to buy. Every company in this position has this clause; the difference is whether they tell you what it is for.

The commitments that come with it are also terms:

The acquirer takes on these terms as they stand. Your plan, your price for the period you have paid, and everything promised to you here binds them from the moment of transfer.
We will tell you. By email to your account address and on the dashboard, without undue delay after the transfer takes effect, and you then have 30 days to export your data and close the account. Notice afterwards rather than beforehand is deliberate: an obligation to warn an entire customer base before a deal closes collides with the confidentiality every deal has, and a clause that made this relationship awkward to convey would be working against the reason it exists. The privacy policy says this in the same words, and if you ever find those two paragraphs disagreeing, the disagreement is the bug.
If the acquirer wants to change these terms, or how your data is handled, that is a change under section 18 — advance notice, and you can cancel and take a pro-rata refund rather than accept it.
The limits in section 11 travel with the data. An acquirer receives the same licence on the same terms, and cannot use it to publish, sell or identify individual customer sites.

You may not transfer your own account to someone else without asking us, though we will not be unreasonable about it — a business that changes hands should usually keep its Harbor account.

If you are an individual rather than a company, the transfer of your personal data as part of a change of control is ordinarily lawful, and it is disclosed here and in the privacy policy rather than left to be discovered. The notice and the 30-day window above apply to you in exactly the same way.

18. Changes to these terms

We will change these terms. The service is new and some of what is written above will turn out to be wrong.

How you will hear about it:

Every change: the "Last updated" date at the top changes and the new version is published at harboraccessibility.com/service-terms. We keep every previous version and will send you any of them on request — your account records the dated version you agreed to, so there is always a specific document to ask for.
Any change that materially affects your rights, your price, or how we use your data: email to your account address at least 30 days before it takes effect. Not a banner you might miss.
If you do not accept a material change, cancel before it takes effect and we will refund the unused portion of anything prepaid. Continuing to use Harbor after the effective date means you accept it.

Two exceptions, stated so they are not a surprise: changes we have to make immediately for legal or security reasons take effect when we make them, and we will explain why afterwards.

Sections 11 and 17 are the two we will not quietly widen by amendment. If we ever needed to broaden either — publish more than aggregate data, or hand over more than these terms allow — that is a new agreement, and we would have to ask you rather than tell you.

19. Law, disputes, and notices

These terms are governed by the laws of the Commonwealth of Pennsylvania, United States, without regard to its conflict-of-laws rules, and the state and federal courts located in Pennsylvania have exclusive jurisdiction over any dispute arising out of them. Not a named county: the only Pennsylvania address on file is a registered office, and tying a forum clause to a registered agent's street is the kind of detail that looks careless later. Our IP assignment chooses Pennsylvania too, so the two instruments agree without anyone having to decide twice.

If you are a consumer, nothing above deprives you of the protection of the mandatory law of the country you live in, or of a right to bring a claim in your local courts where that law gives you one.

Before either of us sues, we talk. Email legal@harboraccessibility.com with what is wrong and what you want, and we have 30 days to resolve it informally. After that, the courts named above.

There is no arbitration clause and no class-action waiver, and that is a choice rather than an oversight — the conventional answer here is the opposite one. Mass arbitration is a real and asymmetric risk for a consumer-priced product; consumer arbitration filing fees fall mostly on the company, so a $9-a-month dispute costs us four figures to defend either way; and a class-action waiver reads badly on a company whose entire position is that it does not hide things.

Notices to us: Harbor Accessibility Co., 502 W 7th St STE 100, Erie, PA 16502, United States, and by email to legal@harboraccessibility.com. A notice that reached us by only one of those two still counts; we are not going to argue about the envelope.

Notices to you go to the email address on your account. Keeping it current is your side of that; if the address stops working we have no other way to reach you (see section 3).

The rest of it. If part of these terms turns out to be unenforceable, the rest still stands. If we do not enforce something immediately, we have not given it up. These terms, the privacy policy published at harboraccessibility.com/privacy, and LICENSE are the whole agreement between us about the service and replace anything said before. Nobody other than you and us has rights under them.

Where this document names a file or a section of the software, the name is meant to be checked rather than taken on trust. If these terms and the code ever disagree, the code is what is happening and the terms are the bug — tell us at legal@harboraccessibility.com and we will fix whichever one is wrong.