Privacy Policy

Threadmap

Last updated: September 9, 2026

1. Overview

Threadmap ("we", "our", or "us") turns photos into cross-stitch patterns. This policy explains how we handle information when you use the app.

Your photos are processed on your device. We use Amplitude to understand how people use Threadmap and RevenueCat to manage purchases and subscriptions. You do not need to create a Threadmap account. We do not sell your personal information or use your data for targeted advertising.

2. Photos, patterns, and face processing

Photos and patterns. Photo-to-pattern conversion happens on your device. We do not upload your photos, generated patterns, or pattern names to Amplitude or RevenueCat. Saved patterns are stored locally and may include a name, stitch grid, thread colors, thumbnail, and a copy of the cropped source image.

Face processing. For photos containing people, Threadmap uses Apple's on-device Vision framework to locate face rectangles. This helps preserve recognizable faces when reducing the photo to a stitch grid and limited color palette. Threadmap does not identify people, create facial identity templates, or use Face ID data. Face rectangles and derived processing weights are used in memory during conversion and refinement; they are not saved as face-detection data with a pattern or sent to analytics providers. A source photo or pattern you save may itself depict a face.

Exports and sharing. If you choose to export or share an image or PDF, the content is provided to the app, service, or recipient you select. Their privacy practices apply to that content. Device backups are governed by your Apple settings and Apple's privacy practices.

3. Usage analytics — Amplitude

Threadmap sends selected app events to Amplitude to help us understand feature use, improve onboarding, find conversion problems, and measure save, export, and subscription flows.

These events can include:

• App sessions and event timestamps, app version and build number.
• Choices you make from the app's predefined onboarding options: goals, pain points, agreement or disagreement with swipe cards, pattern styles, and bundled demo photos. Changes and deselections are included.
• Whether a conversion uses a personal photo, a bundled sample, or an existing saved pattern; conversion and refinement outcomes; processing durations; cache use; and general failure or cancellation categories.
• Save and PDF export attempts and outcomes, and share completion or cancellation when the operating system reports an outcome.
• Paywall presentations and dismissals, purchase and restore outcomes, and whether a restore recovered access.
• A randomly generated installation identifier and random identifiers that connect events within a session, onboarding journey, conversion, or action.

The installation identifier lets us associate events from the same app installation across sessions. It is not your name, email address, Apple ID, advertising identifier, or RevenueCat customer identifier. These records are pseudonymous, not fully anonymous, because events can be associated with the same installation.