TownSq review: the resident app is the product; the contract is the problem

Who it is for

TownSq suits an association whose central problem is that its residents are not engaged — dues arrive late, nobody reads the notices, elections miss quorum. That is what it is built for, and where the evidence is strongest: the homeowner app is current on both platforms, wide rather than token, and the ballots it casts are described as legally binding. The rate card names a second profile plainly, management companies running portfolios; see the pricing rows in the fact box above.

It does not suit an association that needs a general ledger: community accounting is in neither published tier, and it is a separate product underneath. Nor does it suit a board that must answer a security questionnaire, or one whose counsel reads contracts before they are signed. Those are the two places this review turns hard, and neither is a close call.

What we evaluated, and how

This review rests entirely on published documentation read on 16 September 2026. No hands-on session was run and no demo account was requested, which is why ease of use is not scored. Every URL was hash-checked against a deliberately invalid path on the same host before it was treated as real.

Two findings correct our own earlier work. Comparing this product against Buildium, we reported that its terms of use and privacy policy could not be read, because both pages are bare containers for a consent-platform iframe that did not render. That was accurate about the page and wrong as a conclusion: the iframe has its own source address, and fetched directly it returns both documents in full. They are quoted throughout this review. We also reported that the support page published no hours and no response target; it publishes both today. Which changed — the page, or our reading of it — we cannot establish, so this review reports what the page says now and flags the earlier sentence for correction.

Core functionality

The most useful feature documentation this vendor publishes is its rate card, which is an unusual thing to be able to write. The feature pages are brochure copy, describing benefits without showing a single workflow. The rate card is tier-by-tier and specific, and it is where the real shape of the product shows.

The entry tier is the communication and community-management layer, and for a board whose job is communication it is close to complete. What is not there is governance and enforcement: architectural review, violations tracking, audit logs, package control, guest access and shift logs all sit at the middle tier or above, several of them separately purchasable per community. An association that wants covenant enforcement is upgrading or itemising, and should price the add-ons before comparing headline figures.

The release-notes archive corroborates that this is a maintained platform, and it is dated: an overhauled digital-voting flow, an automations engine, a notification hub, a pet registry, entry logs. The cadence is worth noting honestly — three posts carry 2026 dates against ten carrying 2025 — so the app stores tell a more active story than the release notes do.

Accounting and financial controls

This is the weakest documented area, for a structural reason rather than a missing page. Association accounting is not sold at any published price: the “fully integrated community accounting and management solution” appears only in the quote-only top tier, and the rate card labels it “Powered by C3” — a separate product. One marketing page asserts automated billing, payables and receivables, delinquency processing, banking integration, general ledgers and approved vendor invoices. Those are claims, and none is documented where a buyer can check it.

The public knowledge base makes the gap concrete. Its accounting articles are about the C3 product and read like documentation for installed desktop software: creating users, setting up budgets, maintaining mail-merge templates, resolving a Microsoft .NET prerequisite error when installing it. Whatever the ledger is, it is not the thing a board member opens on a phone. Nothing published evidences what this dimension actually measures: a bank reconciliation, an audit trail, separation of duties, dual approval on outbound money, reserve-fund handling, or an export a CPA will accept.

Resident experience

Here the product earns its reputation, on the kind of evidence we like: structured, dated, and declared under a platform’s rules rather than written by a marketing team. Both listings were refreshed within days of the evaluation date, and the iOS listing declares an unusually wide device surface — iPhone, iPad, Apple silicon Macs and visionOS — in three languages. The documented homeowner surface runs from payments and statements through to amenity booking, requests, package tracking and ballots; the store links are in the fact box above.

Two documented deductions keep it off the top of the scale. The first is what it costs a homeowner to pay: card payments carry a flat convenience fee plus a percentage, and eCheck payments carry a flat fee too — the rates are in the pricing rows of the fact box. No free path is offered in the app; the support page’s answer is to ask your management company about a cheque or a direct debit.

The second is the tracking declaration. The iOS listing states that identifiers may be used to track homeowners across apps and websites owned by other companies, and that an email address may be linked to identity for the developer’s advertising or marketing. The Android declaration goes further, listing data shared with third parties that includes name, address, phone number, payment information, approximate location, photos, files, and emails and other in-app messages. The privacy policy agrees this may constitute a “sale” or a “share” under California law. None of that is unusual for a consumer app. It is unusual for the system an association compels its owners to use to pay their dues.

Security, permissions and data ownership

There is nothing to read, and not because we looked in the wrong place: /security, /trust, /status, /dpa, /subprocessors, /sla, /compliance and /soc2 are all byte-identical to this site’s 404 page, which does return a genuine 404. No status page, no service-level agreement, no subprocessor list, no attestation of any kind. Neither “multi-factor” nor “two-factor” appears anywhere on the site or in any of the three legal documents.

The master agreement, updated in April 2026, is not silent on security so much as pointed. It disclaims any warranty that its security measures will be sufficient to prevent third-party access to customer data, and the breach-notification duty it creates runs from the customer to the vendor rather than the other way. Backups are retained at the vendor’s discretion and stated to be for the vendor’s own purposes; recovery for the customer is a chargeable extra. The licence the customer grants over its own content is perpetual, irrevocable and sublicensable, and expressly extends to developing new products. At termination the obligations run one way, and nothing requires the vendor to give the association its data back.

The homeowner-facing terms do the same to residents and add to it: the same perpetual, irrevocable licence over what a homeowner puts in, plus a statement that it may be used to train the product’s AI features, with the resulting vectorised data owned by the vendor.

Two things are positive, and the score reflects them: the Android declaration states that data is encrypted in transit and that deletion can be requested, and audit logs are a real feature — on the middle tier and above, so the entry-tier association does not have them. Asked by an insurer whether its resident platform is audited, whether it enforces multi-factor authentication, or what becomes of owner data if the association leaves, a board can answer none of the three from anything the vendor publishes.

Pricing and contract terms

The transparency is real and should be credited. A board can select its unit band, read its own monthly price and each add-on’s price beside it, and read the master agreement in full, without speaking to anyone. Most of this category does not allow that, and the homeowner payment fees are published too, if on the support page rather than the pricing page.

Three deductions. Published is not purchasable: every call to action on the rate card routes to a demo request, including the buttons labelled “Choose Plan”. And the total is not knowable for an association that needs accounting — the published figure is the price of the communication product, not of the platform.

Third and most important, the exit terms. Terminating early for any reason makes the minimum monthly fees for the whole remaining initial term immediately due, payable within fifteen days: acceleration, being invoiced for months you will not use, rather than forfeiture of what you have already paid. The agreement renews automatically unless either party gives thirty days’ notice, and the vendor may terminate for any reason at any time on seven days’ written notice, with no matching right for the association. A board commits to a term it must serve and the vendor may leave in a week; that is worth counsel’s time before signature.

Support and onboarding

The support page is better than we previously reported, and now among the more forthcoming in this category: weekday hours in a named time zone, a stated typical same-day response, a phone number, an email address, a support form that routes by line of business, and a link to a public knowledge base.

The knowledge base is where the honest reckoning is. Its own sitemap lists thirty-nine topic articles. Three are for TownSq Community — registering an account, making a payment, setting up an automatic payment. The other thirty-six cover business accounting, resale processing, print-and-mail and the C3 desktop product. A board member with an administrative question has no public documentation at all.

The page’s framing matters too. It opens by telling the reader that the vendor is not their management company, and many of its answers end by sending the resident back to that company. That is a sensible division of labour where there is one; a self-managed board buying the entry tier is that management company, and should plan for the questions to land on it. Onboarding is not addressed in the agreement at all, and the “personalized implementation team and plan” appears only in the quote-only tier.

Alternatives worth a look

The head-to-head against the accounting-first alternative is TownSq vs Buildium, which is also where the two contracts are read side by side.

If the association is self-managed and the published price is why this product is on the list, the two competitors that publish a price and do include a ledger are compared in PayHOA vs EasyHOA, and our PayHOA review is the page to read against this one. The trade is close to exact: that product has the ledger and no app; this one has the app and no ledger at a published price.

Corrections

None yet. Corrections are logged here with the date and what changed.