Use case
An ASO tool that keeps your data local: what stays on your Mac
LocalASO stores boards, listings, rank history and settings in a local database on your Mac, and the app has no analytics, telemetry or tracking. Data still leaves the Mac in four documented cases, and a security-minded team should read them before adopting any tool.
Updated
Who this is for
Your company or client contracts limit where product plans and keyword strategy can go. You want ASO research without a cloud account holding your unreleased listings.
The problems you probably have
- Cloud accounts hold strategy. A web ASO tool stores your keywords and competitors on its servers.
- Unclear data flows. Vendor pages rarely list every destination.
- AI and privacy. AI features can send listing text to a provider.
- Credentials. An App Store Connect key must be handled carefully.
What stays local and what does not
| Item | Where it goes |
|---|---|
| Boards, listings, rank history, settings | Local database on your Mac |
| App Store Connect key and Anthropic key | Encrypted with the macOS Keychain; the Apple key is used only to sign requests that go straight to Apple |
| Rank checks and listing reads | Apple's public iTunes Search and Lookup APIs |
| AI text and phrase generation | The AI provider you choose; Ollama runs offline on your Mac |
| Draft upload | App Store Connect, only if you add a key |
| License checks | LocalASO's license server: your key, a salted hash of your Mac and the Mac's name |
Details are in the privacy and data docs, and the AI provider setup shows how to choose one.
A privacy-first setup
- Install the signed and notarized app and activate the key.
- Pick an AI. If your policy forbids sending text to a cloud provider, use Ollama on your Mac. Read the provider's own terms for any other.
- Skip the App Store Connect key at first. LocalASO works without an Apple account by reading the public listing; a key adds the real keyword field, all localizations and uploads.
- If you add a key, upload only drafts. LocalASO never submits for review.
- Back up the local database as part of your normal Mac backups.
Offline work is supported: the license re-checks about every 7 days online and keeps working offline up to 60 days after the last successful check.
What this does not guarantee
- Not a security audit. Check the code signing and your own policies.
- No shared workspace. Local data also means no team sync.
- Apple still sees the public searches the app makes.
- The AI provider you pick has its own data policy.
Questions to ask your security contact
Which AI provider will you allow? Can a Mac with this app reach Apple's public search endpoints and the license server? Where do backups of the local database go? Who holds the App Store Connect key, and is the App Manager role the minimum you are willing to grant? Answering these four before installation prevents most surprises, and the docs describe each data flow in plain language.
Next step
Read the privacy policy and the FAQ, then download the free app or see pricing. For other setups, see budget-conscious developers and side-project apps.
Do this for every country, in minutes