Privacy
Updated November 17, 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. Authorized administrators may inspect the existing search cache for troubleshooting. Cache records are not a complete log of individual search submissions. 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. If you paste a public TikTok or Instagram Reel link, that link is sent to GifSnap’s video import service to fetch and prepare a temporary clip. No social-account login or cookies are used. Direct video and GIF links are fetched by your browser from their host, which receives the request’s network information. Files you choose from your device stay in your browser. If you choose to submit the finished GIF for publication, that GIF, including any caption, is uploaded as described below. 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 unless you choose to submit a GIF for publication. The GIF maker processes your videos and photos on your device. 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.
Publishing a GIF
If you choose to submit a GIF, the finished GIF, its title and its search tags are uploaded to GifSnap for review. Approved GIFs and their titles may be visible to others, including in search, and others may save or share them. GifSnap stores a pseudonymous publishing identifier to let the same device or browser check or remove its submission and to limit abuse. Approved GIFs include a pseudonymous creator code so people can block that creator. We use network information to help protect the service.
Removing a submitted GIF
To remove a GIF, open its publishing status on the same device or browser and choose Remove. You can also email support@gifsnap.com with the GIF link or submission ID to request help. Clearing browser data may remove access to the browser's publishing key and submission list.
Removal takes the GIF out of search and deletes its GIF file, preview, title, tags and reports from the active publishing service. A minimal record, including its status and pseudonymous publishing identifier, may remain to support the service and prevent abuse. We keep the two most recent successful daily recovery snapshots; a removed GIF may remain in them until they are replaced, normally after two successful daily backups. Copies may remain longer if backups are interrupted. Removing a GIF from GifSnap cannot remove copies other people have already saved.
Website GIF activity
When you copy a catalog GIF or its link, complete the website’s share action, or start a download, your browser sends GifSnap the public GIF identifier and the action type. GifSnap records the report with its time to show recent activity and improve popularity rankings. The report contains no account, device, chat or recipient identifier and does not confirm that anyone received a message. This reporting is separate from Google Analytics. The website analytics opt-out below also stops new website GIF activity reports.
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…
Contacting us
If you request a custom GIF quote or contact us about an integration, we send your email address, request type and message, along with any platform or app link you provide, to our team’s Google-hosted inbox so we can respond. The form is processed by GifSnap and Google Apps Script. We don’t send the form’s contents to website analytics or subscribe you to marketing. Please don’t include secrets or private customer information. We retain the correspondence to handle your request; you can reply to ask us to delete it. Short-lived request identifiers and one-way fingerprints help prevent duplicate messages and abuse.
Developer accounts and API credits
The developer workspace uses Firebase to verify your sign-in. It stores your account identifier, a protected hash of your verified email to prevent repeated starter-credit claims, project details you enter, hashed API keys, daily request and error counts, and credit-ledger records. Keys are shown in full only when created. The billing ledger stores keyed request fingerprints for retry protection rather than raw searches; searches still reach the search service described above.
When card top-ups become available, the payment provider will process card details and provide payment and adjustment references. GifSnap does not receive card numbers or security codes. Credit and payment records are retained for reconciliation and support. Project website details are developer-provided claims. To request account closure or discuss record deletion, contact us through support; some payment records may need to be retained. See how API credits work.
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.