Four questions, answered without you having to dig.

Who is this?

August SEO, LLC, a search agency in Spokane, Washington with a client roster across five verticals — manufacturing, private aviation, IT services, healthcare and auto glass. LocalSync is our own listing-management platform, built to replace the per-location subscriptions we were renting. We are the operator and we are also the first customer.

We are not a reseller, not a data broker, and not a marketplace. The contact address on this page is the same address that sent you the application.

What happens with the access?

Listing data — name, address, phone, hours, categories, photos, attributes — for locations we have written authorization to manage, under credentials the client owns and can revoke. Writes are scoped to those locations and nothing else.

We do not create accounts on a client's behalf, do not perform identity verification programmatically, and do not read or retain data about businesses we do not manage. Nothing retrieved through your API is resold, republished, or used to build a directory of our own.

What is the data-quality process?

This is the part most applicants our size cannot answer, so here it is in full.

1. One canonical record per location. Versioned, with an audit trail. Every directory is written from that record, never from another directory.
2. Normalization before comparison. Addresses, phone formats, hours and categories are normalized per directory taxonomy so a formatting difference is not mistaken for a data difference.
3. Plan before apply. Every change is computed as a reviewable diff. Name, address and phone edits stop at an approval gate and wait for a person.
4. Verify with a separate read. After a settle delay we re-read the record and compare. A success response is not treated as proof that anything changed.
5. Evidence retained 24 months. Request, response, read-back, screenshot, operator, timestamp.
6. Scheduled drift detection. The same verify pass runs on a schedule and raises a mismatch rather than silently overwriting.

Are we going to be a problem?

No, and the constraints are structural rather than promised. One session per directory. A deliberately low write ceiling, well under any published limit. Human-paced interaction. A global kill switch. Tier assignment driven by what your terms permit, not by what is technically reachable — where automation is prohibited, the directory is routed to manual work permanently and stays there.

CAPTCHAs are never bypassed, outsourced, or defeated. Hitting one enqueues a person. The full posture is on its own page.