> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/squash/extras/privacy-policy.md). # Privacy Policy We value your privacy. The [Realmac Software Privacy Policy](https://docs.realmacsoftware.com/elements-docs/legal/privacy-policy) explains how we handle personal information for our software, website, purchases, support and mailing lists. It covers Squash as well as our other apps. The information below explains how Squash 4 processes images and handles its optional AI features. Squash processes your images entirely on your Mac. **Images never leave your Mac**, including when Squash generates descriptive filenames and descriptions. ### Image processing on your Mac Squash compresses, converts, resizes and applies visual edits on your Mac. These operations do not upload images to an image-processing service. Source metadata is removed by default. The [Metadata](/squash/quick-guide/nodes/metadata.md) section starts in **Remove All Metadata** mode. Choose **Keep All Metadata** to keep supported source metadata, or **Custom** to keep only some kinds, such as GPS location or camera information. Information you add in the Metadata section, such as a creator or copyright notice, is written into every exported image. The Metadata section can also set a location. Two optional parts of this use Apple's map services, and only when you use them: searching for a place on the map sends your search text and loads map tiles, and **Also fill in place names** sends the coordinates you set, to find the city and country. Apple handles these requests under its own privacy policy. Your images are never sent. ### Apple Intelligence Descriptive filenames, and descriptions written into image metadata, are generated by **Apple Intelligence** on your Mac. Squash does not use any cloud AI service, and there are no API keys to manage. The default Rename template uses Describe to request filenames. When it does, Squash describes images as soon as they are added, and during export. Remove Describe from the template if you don't want images described. Descriptions are generated during export only when the Metadata section's **Description** is set to **Apple Intelligence**, and never for images redacted with the Highlighter. Before describing an image, Squash makes a resized copy without original EXIF and GPS metadata. That copy is processed on your Mac and is not uploaded. See [AI Setup](/squash/quick-guide/ai.md) for more about descriptive filenames. ### Purchases, support and privacy requests For company data practices and your rights, refer to the [Realmac Software Privacy Policy](https://docs.realmacsoftware.com/elements-docs/legal/privacy-policy). For questions about Squash or requests concerning your personal information, email . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.realmacsoftware.com/squash/extras/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.