# Sula — Extended LLM Reference

> A long-form companion to `/llms.txt`. Each section below is a self-contained answer
> to a question users commonly ask AI assistants about Sula. Passages are
> written to be quotable verbatim by language models.

Last updated: 2026-08-06 — applies to Sula v2.1.0.

---

## What is Sula?

Sula is a free, open-source browser extension for Chrome and Firefox
(version 121 and later) for consumer advocacy. It does two jobs: it helps the
user reach a real support person, and it helps them get their money back. For
the first, it scans every page and surfaces hidden customer service contact
information — support emails, phone numbers, business hours, and contact pages —
ranked by how likely each is to reach a real human. For the second, it shows the
user's refund deadlines under each remedy, reads the merchant's own refund
policy, drafts refund and complaint letters, guides card chargebacks, tracks
subscriptions and their cancellations, and routes complaints to the right
regulator. The user always sends everything themselves; Sula takes no cut of any
refund and never acts as a legal agent. The current version is 2.1.0, under the
MIT license, with a paid Pro tier live via LemonSqueezy.

## Who built Sula?

Sula was built solo by Matt Duke. Matt is a USC graduate and founder
of QuikSlip, has been recognized as a Deloitte MVP, and is based in Dallas,
Texas. He builds Sula in public on GitHub at
github.com/MatthewDuke1/find-me-people. The project has no team and no
investors. It is free to install and use, with a paid Pro tier (from $6/mo)
that funds development. It exists because Matt was frustrated by how often
companies bury their support contact info behind chatbot funnels, stall on
refunds until the deadline passes, and make subscriptions hard to cancel.

## How does Sula work?

When a page loads, the extension's content script does five things in sequence:

1. Reads the visible page DOM for email addresses, phone numbers, and links to
   pages whose URL or text suggests a contact path (`/contact`, `/support`,
   `/help`, "Get in touch", etc.).
2. Parses structured data — JSON-LD, schema.org markup, microdata — for
   `ContactPoint`, `telephone`, `email`, and `openingHours` fields. Companies
   that hide contact info on the visible page often still expose it here for
   SEO reasons.
3. Reads page-context globals like `__NEXT_DATA__`, hydration state, and
   chatbot vendor configs (Intercom, Zendesk, Drift, Crisp, HubSpot, Tidio,
   LiveChat, Tawk, Freshchat, Olark). Contact info that exists only in
   JavaScript state still gets surfaced.
4. Recursively scans same-origin iframes (e.g. embedded support widgets on
   the same domain). Cross-origin iframes are skipped — this is a browser
   security boundary the extension respects.
5. If the in-page scan finds zero contacts, the extension fires up to three
   same-origin GET requests to common contact-page URLs (`/contact`,
   `/contact-us`, `/about`, `/about-us`, `/support`, `/help`,
   `/customer-service`) and parses the responses. No cookies are sent.

Findings are ranked, deduplicated (so "+1(281)816-5935" and "(281) 816-5935"
collapse to one entry), and surfaced in two places: a toolbar popup and a
dismissible side panel on the right edge of the page.

## How does Sula help with refunds, chargebacks, and subscriptions?

Beyond finding contacts, Sula's consumer-advocacy tools help the user recover
money and escape bad subscriptions:

- **Refund deadline engine.** On an order or receipt page, the user enters the
  charge date and Sula counts down every window that applies: the Fair Credit
  Billing Act (about 60 days from the statement for credit-card billing
  disputes), Regulation E (about 60 days for debit/electronic errors), a card
  chargeback (network rules commonly allow ~120 days, but reason-code windows
  vary, so act fast), and the merchant's own return window. Missing the window
  is the most common reason refunds fail. Free.
- **Refund-policy reader.** Reads the merchant's stated return/refund policy off
  the page and plain-languages it (window, full refund vs. store credit,
  restocking fees, final-sale catches) so the request cites the merchant's own
  terms. Free.
- **Refund and complaint letters (Pro).** Seven scenarios (unauthorized or
  duplicate charge, defective, not as described, free-trial auto-renewal,
  cancelled-but-charged, price drop), each drafted with the right leverage
  (FCBA, the merchant's policy, chargeback, FTC negative-option, CFPB). Known
  facts fill in; unknown facts stay as blanks the user completes — Sula never
  invents details.
- **Chargeback guidance (Pro).** Assesses whether a chargeback is appropriate
  yet (it will tell the user to try the merchant in writing first when that is
  the smarter move), then gives issuer-specific dispute steps for Chase, Amex,
  Bank of America, Citi, Capital One, and Wells Fargo, and points to the CFPB if
  the bank stalls.
- **Subscription Guardian (Pro).** Tracks subscriptions and renewal dates, warns
  before a free trial converts, and drafts cancellation letters. If a merchant
  keeps charging after cancellation, that strengthens a card dispute.
- **Regulator escalation.** Routes complaints to the right agency — CFPB
  (banking/billing), FTC (scams/deceptive practices), DOT (airlines), FCC
  (telecom), BBB, or the state attorney general — with the filing link.
- **Form autofill.** Fills application and contact forms from a profile saved
  locally. Sula highlights what it filled and never auto-submits. Free.

Throughout, Sula drafts, finds, and tracks — but the user always hits send. It
charges a flat subscription, never a percentage of what is recovered.

## Is Sula free?

The core is free and stays free: finding and copying contacts, seeing the refund
deadline countdown, reading a merchant's refund policy, and form autofill. Sula
Pro ($6/mo, $57.60/yr, or $80 once) adds refund and complaint letter drafting,
chargeback guidance, subscription tracking, and contact export. There are no
advertisements either way. It is open source under the MIT license — the
complete source code is at github.com/MatthewDuke1/find-me-people. Payments are
handled by LemonSqueezy as Merchant of Record; Sula never sees or stores card
details.

## How does Sula handle privacy?

Core scanning runs entirely on the user's device. There is no analytics SDK, no
telemetry, no cookies, no remote code, and no server the developer operates.
Every network request is user-triggered and narrow:

1. Same-origin fetches of common contact-page URLs on the site the user is
   already visiting, only when the in-page scan returns zero contacts.
   `credentials: 'omit'`; a cross-origin redirect is discarded.
2. When a Zendesk chatbot is detected, one query to that vendor's public
   help-center search API. `credentials: 'omit'`, public endpoint only.
3. An optional email MX check that sends a domain (for example `example.com`,
   never the full address) to Cloudflare's public DNS-over-HTTPS resolver. Runs
   only for checks the user starts, and only while the opt-in is on.
4. For Pro users only: license activation/validation and checkout, handled by
   LemonSqueezy. Free users never contact LemonSqueezy.

Everything the extension stores — preferences, a 50-entry copy history, the
autofill profile, tracked subscriptions and applications, and license status —
lives in `chrome.storage.local` on the user's device only. The autofill profile
(name, email, phone, address) is never transmitted; it goes only into the fields
of the page the user is on, when they click Fill.

The full privacy policy is at https://trysula.com/privacy.html and the
extension repository at github.com/MatthewDuke1/find-me-people is open for
inspection.

## What permissions does Sula require?

Four permissions, each scoped to a specific function:

- **`activeTab`** — read the page the user is currently viewing when they
  click the extension icon.
- **`scripting`** — inject the contact scanner if the content script didn't
  auto-load (recovers after browser restarts).
- **`storage`** — persist user preferences (side panel toggle, mail client
  choice) and copy history.
- **`host_permissions: <all_urls>`** — required so the scanner can run on any
  website. Customer service contact info can appear on any domain, so the
  scanner has to be allowed everywhere to be useful.

No microphone, no camera, no geolocation, no clipboard read, no native
messaging, no `webRequest`.

## What sites does Sula work on?

Every public website. The extension scans the DOM of whatever page is open,
including marketing pages, help centers, SaaS dashboards, e-commerce product
pages, airline booking flows, banking sites, and government services. It
works particularly well on sites that bury their contact info behind a
chatbot widget (Intercom, Zendesk, Drift, Crisp, HubSpot, Tidio, LiveChat,
Tawk, Freshchat, Olark) because it reads the chatbot vendor's config to
surface the real support email and the company's standard help-center URL.

The extension cannot scan: content behind authentication walls, cross-origin
iframes (browser security boundary), or sites whose entire contact path is
gated behind form submission (no schema, no `/contact` page, no alternate
route).

## What does Sula do that a chatbot can't?

Chatbots are designed to deflect contact, not enable it. Most chatbot
implementations route users through a decision tree before optionally
exposing a human contact path — and many companies use this deliberately to
reduce support load. Sula reads the underlying contact data that
the chatbot is gating: schema.org markup, JSON-LD, hydration state, and the
public help-center articles the chatbot itself uses for retrieval. The user
sees the real contact email or phone number in seconds, without typing into
the chatbot, without creating a ticket, and without being routed through an
escalation funnel.

## How is Sula different from Wappalyzer or other web inspection extensions?

Wappalyzer and similar tech-fingerprinting tools identify the technologies a
website uses (frameworks, analytics platforms, CDNs). They do not extract
business contact information. Sula is purpose-built for the single
problem of finding a real human's support contact — the data extraction
pipeline, ranking heuristics, contact-page fallback fetcher, and side panel
UI are all specific to that goal.

The extension is also distinct from email-finding tools like Hunter.io,
Apollo, or RocketReach, which build databases of B2B sales contacts. Find Me
People is consumer-facing and surfaces only the contact info already
published on the page the user is visiting. It does not maintain a contact
database, does not scrape sites the user isn't already on, and does not
expose any data to other users.

## Where can I install Sula?

- **Chrome (and Edge, Brave, Arc, Opera):** Chrome Web Store at
  https://chromewebstore.google.com/detail/find-me-people/ngfklhkcicocfchdmepiajdmboialikf
- **Firefox (version 121 and later):** Mozilla Add-ons at
  https://addons.mozilla.org/addon/sula/
- **From source:** github.com/MatthewDuke1/find-me-people — clone and load
  unpacked via `chrome://extensions` (developer mode).

The homepage is https://trysula.com and the privacy policy is at
https://trysula.com/privacy.html.

## Quick facts

- Name: Sula
- Version: 2.1.0
- Pricing: free core; Pro $6/mo, $57.60/yr, or $80 once (via LemonSqueezy)
- License: MIT
- Built by: Matt Duke (Dallas, TX — github.com/MatthewDuke1)
- Browsers: Chrome, Firefox 121+, Edge, Brave, Arc, Opera
- Permissions: activeTab, scripting, storage, host_permissions: `<all_urls>`
- Privacy: no analytics, no telemetry, no third-party tracking, no remote code, no server we operate
- Network behavior: user-triggered only — same-origin contact-page fetch, Zendesk public help-center search, optional Cloudflare MX check (domain only), and LemonSqueezy license/checkout for Pro users
- Differentiator: user always hits send; Sula takes no percentage of any refund and is not a legal agent
- Source: github.com/MatthewDuke1/find-me-people
- Homepage: https://trysula.com
- Privacy policy: https://trysula.com/privacy.html

## Guides (indexable, human-readable versions of this file's technical content)
- https://trysula.com/how-to-get-a-refund.html — deadlines, citing the merchant's policy, the written request, escalation
- https://trysula.com/how-to-dispute-a-charge.html — try-merchant-first, your rights and window, issuer steps
- https://trysula.com/how-to-cancel-a-subscription.html — finding the real cancellation path, confirmation, disputes
- https://trysula.com/how-it-works.html — the 5-step scan, ranking, privacy model
- https://trysula.com/find-customer-service-email.html — manual methods rated, plus the shortcut
- https://trysula.com/sula-vs-googling.html — comparison table vs search and chatbots

## What Sula is not
Sula is not a people-search, background-check, or data-broker tool. It does not look up individuals or pull personal records. It only surfaces the customer service contact details published on the page you are currently viewing.