# Store Compliance

Submission quality reduces rejections and speeds review. Use these checklists before publishing to mobile or extension stores.

### Mobile Stores

#### Content & Privacy

* Accurate app descriptions and screenshots for each device class.
* Clear privacy policy URL with data collection details.

#### Technical

* Correct code signing and provisioning profiles.
* Version and build numbers incremented consistently.
* Runtime permissions minimized and justified.

#### Review

* Stable test accounts and credentials provided to reviewers.
* In-app purchase compliance where applicable.
* Crash-free sessions verified before submission.

### Extension Stores

#### Manifest

* Manifest v3 validates locally.
* Only required host permissions requested.
* Icons and localized text included.

#### Packaging

* Single zip bundle with correct structure.
* No remote code execution patterns.

#### Review

* Clear changelog and version history.
* Visible support and privacy links.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eitherway.ai/documentation/engineering/integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.