Privacy policy
Effective October 29, 2026
Syncmoji is operated by Brandon McConnell. For privacy questions or requests, contact brandon@dreamthinkbuild.com.
Slack connections
You connect workspaces using Slack’s official authorization flow. Syncmoji requests access to custom emoji and workspace information (emoji:read and team:read), not Slack message or channel history. Syncmoji does not receive your Slack password.
Our authorization relay exchanges an authorization code with Slack and temporarily holds an encrypted workspace identifier and access/refresh credentials so your app can claim them using a single-use, verifier-protected ticket. Tickets expire after two minutes. A successful claim replaces the stored credential payload with a tombstone. Expired authorization records are removed by a daily cleanup, so unclaimed encrypted records may remain until that cleanup, approximately one additional day.
After authorization, credentials are stored in the device Keychain and shared only between Syncmoji and its Messages extension using their App Group. They use device-only, unlocked-device Keychain protection. Syncmoji does not create a separate Syncmoji user account.
Your emoji library
Workspace names/icons, emoji names and aliases, image URLs, downloaded artwork, pins, and recents are stored on your device and shared with the Messages extension. Emoji downloads and refreshes contact Slack directly. Our authorization and diagnostic services do not host a copy of your emoji library. Downloaded library files are excluded from iCloud backup; Keychain credentials are device-only.
When you choose to send or attach a sticker, Apple’s Messages service delivers that content. Recipients may retain it. Removing a workspace from Syncmoji does not delete stickers already sent or copies held by recipients.
Automatic technical diagnostics
When an import or sticker preparation fails, Syncmoji automatically sends a limited report to our diagnostic service. It includes a fresh random report identifier, report time, app build, attempt count, and technical failure categories, HTTP status codes, file byte counts, detected formats, animation-frame counts, and numeric error codes. Reports are capped at 200 failure entries.
These reports do not contain workspace/account identifiers or names, emoji names, image URLs, artwork, Slack credentials, device identifiers, private messages, or raw error descriptions. The random report identifier is not a persistent device or advertising identifier. Diagnostics are used to find and fix reliability problems, not for advertising or cross-app tracking.
Reports are stored privately for fourteen days and removed by a daily cleanup, which may add up to one daily interval. Pending reports on your device are bounded to twenty reports and expire after seven days. Because reports omit account identifiers, we may be unable to associate a specific report with you.
Service providers and network information
Slack provides workspace authorization and emoji services. Apple provides platform services, device security, Messages, and app distribution. Vercel hosts our authorization relay, diagnostic endpoint, private storage, and this website. Those services receive normal connection information, such as IP addresses and request metadata, as needed to serve requests, operate, and secure their systems. Provider records follow their respective retention and privacy practices.
See Slack’s privacy policy, Apple’s privacy policy, and Vercel’s privacy policy. Syncmoji contains no advertising or third-party advertising/analytics SDKs and does not sell your personal information.
Your choices and deletion
In Syncmoji or its Messages settings, select a workspace and choose Remove to delete its local connection, downloaded library, pins and recents from this device. To revoke a Slack installation, use Slack’s app-management controls. Removing one device’s local library does not revoke the bot for other installations or devices. You can also delete the app from your device; iOS controls app and Keychain data lifecycle. Contact us for privacy requests concerning our services.
Updates
We may update this policy when the app or its data practices change. The effective date above identifies the current version.