Recall Third-Party SDK Sharing List
Hushan Hushan (Shenzhen) Technology Co., Ltd.
Last updated: August 1, 2026
Recall may use the following third-party services, frameworks, or SDKs for product features, security, payment, login, crash monitoring, system integration, and local processing. Actual integrations may differ by version, channel, platform, or region.
The App does not integrate advertising SDKs, does not display third-party ads, and does not collect, use, or share device identifiers for ad delivery, attribution, or personalized advertising.
This document applies to the macOS version of Recall. Downloads, updates, account services, payments, refunds, permission prompts, or system capabilities may be provided by the HSHS Tech website, the in-app email account service, Paddle checkout and customer portal, or the operating system, and may also be governed by their official terms, privacy policies, and on-screen notices.
Third-Party Services and Frameworks
| Service/Framework | Provider | Type | Purpose | Information Processed | Official Link |
|---|---|---|---|---|---|
| Paddle hosted payment service | Paddle.com Market Ltd. and its applicable affiliates | Hosted payment service | Complete purchases, cancellation, invoices, and payment-method management in the system browser | Email, customer ID, order, subscription, billing, and payment information; we do not store full card details | Privacy Policy |
| Sparkle open-source update framework | Sparkle Project | Open-source update framework | Check, download, and verify signed updates from the HSHS Tech update source | App version, update channel, and basic network connection information; anonymous system profiling is disabled | Documentation |
| KSCrash open-source crash-capture framework | KSCrash contributors | Open-source crash-capture framework | Locally capture Mach exceptions, fatal signals, C++ exceptions, and NSExceptions so Recall can allowlist-normalize and automatically report fatal crashes | The framework writes raw crash reports locally. It does not transmit data to KSCrash contributors; Recall sends only allowlist-normalized results to the HSHS Tech backend | Documentation |
Third-Party SDK Sharing List
This platform version currently does not integrate third-party SDKs that need to be listed in the third-party SDK table.
Local Processing and System Capabilities
| Capability/Component | Purpose | Information Processed | Processing Method | Frequency/Background Behavior |
|---|---|---|---|---|
| macOS Accessibility, display, and local workspace storage | Recognize displays and windows, store workspaces locally, and restore a layout after your confirmation | Display identifiers, app bundle IDs, window identifiers, titles, positions, sizes, match results, and local workspace files | Read through macOS system capabilities and processed in Recall's local database only when you save, update, preflight, or restore a workspace | Processed for user actions and display-connection changes; workspace content is not uploaded on a fixed schedule |
| KSCrash and Apple MetricKit local crash processing | Capture, normalize, deduplicate, and automatically replay fatal Recall crashes | App and system version, architecture, device, process and thread, exception or signal, module UUID and offset, redacted stack, time, and foreground state; KSCrash may include the account number at crash time, MetricKit is anonymous, and redacted logs covering two hours before and after may be attached only for a matching account | KSCrash is installed before AppKit/UI creation and leaves raw reports on-device; MetricKit diagnostics are delivered by macOS on a best-effort basis. Recall allowlist-normalizes and one-to-one deduplicates both sources before automatic delivery to the HSHS Tech backend. Tokens are not stored and no data is sent to KSCrash contributors | Processed only for supported fatal crashes or when macOS delivers a MetricKit diagnostic. Small-batch replay runs after restart and app activation; each of the three local queues is capped at 20 items. Hangs, deadlocks, and SIGTERM are not monitored |
Notes
Third-party SDKs process information under their own privacy policies. We evaluate the necessity of third-party services and require them to process data lawfully, properly, and only as necessary.
System capabilities, payment capabilities, login capabilities, and app-store capabilities may be provided by operating systems, device manufacturers, app stores, or payment platforms. Their official agreements and privacy policies govern their processing.
Local processing capabilities are mainly used to process files, photos, videos, audio, or app settings on your device. Unless a feature clearly states that network submission is required, we do not upload that content to our servers.
We periodically review SDK integrations based on product features, platform rules, and compliance requirements. For questions about third-party SDKs or information sharing, contact feedback@hshstech.com.