Privacy
Updated October 3, 2026.
Finding and saving GIFs
Search phrases are sent to our search service to find matching GIFs. Search results and search records may be cached by that service. GIFs can load from GifSnap and external media providers, which receive the network information needed to deliver them. Favorites and preferences can be stored in your browser. If you choose to sign in, Firebase provides account authentication.
Creating a GIF
The GIF creator processes the file you choose in your browser. Your input file and caption are not uploaded by the creator. We measure whether actions such as generating or downloading a GIF complete, without sending the file, its name or your caption to analytics.
GifSnap apps
GifSnap apps for iPhone and Android. Searches you type in the app, the GifSnap keyboard or iMessage are sent to GifSnap’s search service to find GIFs, just like searches on this website. When you copy, share or send a GIF, the app tells GifSnap which GIF was used, without any account or device identifier, so popular GIFs can rank higher. Your favorites, recent searches and the GIFs you make stay on your device. The GIF maker processes your videos and photos on your device; they are not uploaded. The GifSnap keyboard never stores or sends what you type into other apps — only the words you type into its own GIF search bar are sent. On iPhone, the keyboard needs Full Access to search GIFs online and copy them for you to paste. The apps don’t use advertising identifiers and don’t track you across apps or websites. On iPhone, GifSnap can show your favorites, GIFs you made and GIFs you viewed in Spotlight; this index stays on your device and can be turned off in Settings.
Website analytics
We use Google Analytics to understand visits, referral sources and actions such as searching, opening, copying and downloading GIFs. Analytics uses browser identifiers and cookies and can include device information and approximate location. Our analytics events omit search phrases, account details, file names and file contents. Search URLs and page titles are simplified, and individual GIF detail pages are grouped together.
We disable Google signals and advertising personalization in our analytics tag. Automatic search and form tracking are turned off; the site sends a limited set of events. We do not send Firebase account identifiers or email addresses to Google Analytics. On developer pages, we measure platform choices, code-copy success and demo actions without sending copied code or selected media URLs. These actions do not tell us whether you installed an SDK or deployed an app.
Your browser settings and content blockers can restrict analytics requests and cookies. See how Google uses information from sites that use its services.
You can turn off website analytics for this browser. This saves a local preference and reloads the page. It applies to future visits in this browser; it does not remove earlier analytics data. Clearing browser storage resets the preference. Other open tabs must be reloaded to apply it.
Checking this browser’s preference…
Service logs and browser storage
Server logs help us operate the site, diagnose errors and filter automated traffic. These are separate from website analytics. Browser storage also supports preferences, favorites and authentication; clearing it may reset those features.