Privacy.

This policy applies to the Shrinkray iOS app, Photos Share and Action extensions, and Messages extension. Shrinkray is provided by Here Comes Supper, a DBA of Beat Breakdown LLC.

Shrinkray reads the photos and videos you select, creates optimized copies, and prepares them for sharing on your iPhone or iPad. It does not upload media bytes, thumbnails, filenames, library identifiers, message or recipient context, location, or extracted media metadata to Here Comes Supper or PostHog.

When Apple needs to retrieve an iCloud-only Photos item for a selection, that retrieval is handled by Apple and initiated by your use of Photos. Shrinkray’s compression and output preparation still happen on your device. Files opened from Files or passed into a sharing extension are copied for processing; the source file is not edited.

With your permission, the main app and Messages extension can use Apple’s Photos framework to show and read selected library items. You can instead use Apple’s private Photos picker, which lets you choose items without granting Shrinkray full library access. The Share and Action extensions process attachments that another app passes to them and do not request full Photos library access.

Shrinkray does not send a message or publish a post on your behalf. You choose when to use Apple’s share sheet, Messages composer, or another destination, and you remain in control of the final handoff.

The app and its extensions use shared local App Group storage to pass temporary job files and small pieces of extension recovery state between the app, Share and Action extensions, and Messages. Media jobs are stored in short-lived directories and are excluded from device backup.

Shrinkray removes job files after a completed handoff, cancellation, or cleanup. Abandoned jobs become eligible for removal after the three-hour cache lifetime and are removed when cleanup runs. A short-lived Messages recovery record expires after ten minutes. Shared app settings and a Boolean verified-Pro entitlement cache may remain in the shared storage so extensions can use the same settings and purchase status.

For one output, Shrinkray can hand the optimized file to the Messages composer. When multiple outputs need to be copied, the Messages extension writes the encoded media bytes to the iOS general pasteboard as local-only items with a ten-minute expiration. You must paste them into Messages yourself; Shrinkray does not send them automatically.

The system pasteboard is controlled by iOS and may be visible to other apps on the same device subject to iOS paste permissions until it expires or is replaced. Shrinkray does not put a URL to its private cache on the pasteboard.

Shrinkray uses PostHog to understand product use and reliability when the production analytics configuration is present. It may send app lifecycle events and product events such as onboarding, screen selections, optimization starts, coarse counts and settings, optimization results, cancellations, and blocked actions. It may also send standard technical context supplied by the SDK, such as a random app-install identifier, app version and build, device model or type, operating-system name and version, locale, time zone, screen dimensions, and network connection type.

These events are designed to exclude media bytes, thumbnails, filenames, Photos identifiers, recipient or message content, location, and extracted media metadata. Shrinkray does not use PostHog’s identify feature to connect events to your name, email address, Apple Account, or another known person. PostHog processes this information as a service provider. Learn more in PostHog’s privacy policy.

PostHog automatic error tracking is enabled in the configured physical-device build. Shrinkray also reports certain handled import and optimization failures. Before an error report is sent, Shrinkray removes raw exception values, local paths, raw error messages, source filenames, package details, and other mechanism metadata that could reveal private media context. It retains limited technical information, such as the operation, error domain, numeric code, error type, exception fingerprint, stack information, and debug identifiers, to help diagnose failures.

Session replay, automatic screen capture, automatic element-interaction capture, push-notification capture, rage-click capture, and PostHog exception steps are disabled. Error tracking is not the same as collecting your media: Shrinkray does not attach your selected media or its thumbnails to these reports.

Shrinkray offers a one-time, non-consumable Pro entitlement through Apple’s StoreKit and App Store. Apple processes payment and purchase history. Shrinkray receives product information and verified entitlement status so it can unlock Pro features or restore a purchase, and it shares the verified status with its extensions through the App Group cache.

Payment details and Apple Account information are handled by Apple. Shrinkray does not send them to PostHog.

Shrinkray relies on Apple for Photos, the private Photos picker, Files and Messages handoffs, StoreKit purchases, and iOS pasteboard services. It relies on PostHog for the limited analytics and sanitized error information described above. Shrinkray does not include advertising SDKs or a cloud media-processing service.

You choose whether to grant Photos access, which items to select, and whether to use a share destination. You can review or revoke Photos access in iOS Settings, or use the private Photos picker when available. You can avoid the multi-item clipboard handoff by using another sharing path.

Deleting Shrinkray and its extensions removes their local app data and cached job files from the device. Pasteboard items expire after the period described above or when the pasteboard is replaced. Records controlled by Apple, including App Store purchase history and any Apple-managed Photos or iCloud data, remain subject to Apple’s controls and policies.

For questions about Shrinkray or this privacy policy, email support.shrinkray@herecomessupper.com.

If Shrinkray’s privacy practices change, this page will be updated and the effective date above will be revised.