Privacy Policy
Last updated: November 8, 2026
Local files stay on your device
Gifable’s free processing tools and browser-based template generators work locally. Selected images, GIFs, videos, logos and template text are read by your browser and are not uploaded to Gifable for processing. Local outputs are not stored in a Gifable gallery. Downloaded files remain under your control; closing the tab does not delete files you have saved to your device.
Accounts and essential cookies
You can use the free local tools without an account. If you register, we store information needed to run your account, such as your name, email address, authentication records and sessions. Sign-in uses essential cookies or similar session storage. If a third-party sign-in option is enabled and you choose it, that provider supplies the account information needed for authentication. We use these records to authenticate users, secure the service and provide account features.
Payments and credit records
Stripe handles card entry and payment processing under its own privacy policy. Gifable stores payment and billing references, plan or purchase details, payment status and credit transactions so that purchases can be reconciled and balances maintained. We do not receive the full card details entered on Stripe’s hosted payment form. Credit records can include grants, deductions, expiry dates and refunds. Payment and accounting records may need to be retained after account deletion when required for legal, tax or dispute purposes.
Online generation data and availability
Public AI generation is coming soon. A preview labelled as a fixed test sample does not call a live AI provider. Separately authorized real-provider testing can use the online processing described below. Unlike local file processing, submitting an online generation request sends your prompt, selected tool, format, usage mode and visibility setting to our servers. We associate the request with your account, keep job status, quota and credit records, and store the output using Cloudflare R2. When real GIF generation is explicitly enabled, Gifable sends your prompt and generation settings to LinkAPI (linkapi.ai), the API service used to request the configured image model. The current request contains the prompt, model identifier, requested dimensions, GIF format and result count. It does not include your Gifable account ID, email, credit balance or locally edited files. We associate the returned GIF and available usage metadata with your job on our servers. LinkAPI receives the prompt and handles it under its own service policies; private gallery visibility does not keep a prompt from the generation provider. We do not make a promise here about LinkAPI’s retention period or model-training practices. Do not assume that an online generation request stays on your device.
Temporary original GIF storage
For real-provider requests, Gifable temporarily stores the original returned GIF, before our watermark processing, in private Cloudflare R2 storage. This staging copy lets an interrupted job resume processing without making another generation request. It is separate from the finished output and is not served through the public gallery or download route. The service attempts to delete it after completion or terminal failure. Residual staging copies are subject to a storage lifecycle rule that makes them eligible for deletion after one day; lifecycle cleanup is asynchronous, so this is not a guarantee of deletion at an exact hour. This staging rule does not set the retention period for finished outputs, prompts, job or billing records, or copies held by the provider.
Public creations and private visibility
Generation results are public by default. A public gallery entry exposes the output, prompt, tool and creation time to other visitors. Free attempts produce public, watermarked results. An eligible paid account can select private visibility for a credit-funded generation; private results require the owner’s authenticated access through the service. Private visibility does not prevent processing by the infrastructure needed to provide the feature. Do not include secrets or sensitive personal data in prompts. Changing visibility or hiding a gallery entry cannot recall copies that others have already saved.
Reports, moderation and generation retention
When a signed-in user reports a public creation, we store the reported creation, reporter account and stated reason to investigate abuse. Reports can hide a creation from public view pending review; administrators can hide or remove content. Hidden or removed content may leave moderation, security, job or billing records needed to operate the service, handle disputes or meet legal duties. We do not promise a fixed automatic deletion period. You may request access, correction or deletion of your generation data. Removing public access is separate from erasing retained records and from deleting copies outside Gifable.
Analytics and technical data
When analytics is configured, we may use Google Analytics 4 or pageview analytics to measure visits and basic tool activity. Measurements can include the visited page, browser or device information and events such as a tool being used. Tool telemetry does not include the selected file, its contents, its filename, template text or logo. Analytics providers may use their own cookies and process network information under their policies. Hosting and security providers also receive technical request data, such as IP addresses and request times, to deliver and protect the website. Local file contents are not part of those requests.
How data is used and shared
Account and technical data are used to operate the service, protect it, maintain billing and understand usage. Hosting, authentication, payment and analytics providers process the information necessary for those roles. Provider processing can take place in other countries. We do not turn locally edited files into public content or give analytics services access to them through the tool workflow.
Retention, controls and deletion
We retain account and session data for as long as needed to provide and secure the account, and retain billing records when needed to meet legal obligations or resolve disputes. You may request access to, correction of or deletion of your account information. Deleting an account does not erase billing records that must be retained for legal obligations or disputes. You can control cookies in your browser and use provider privacy controls for analytics. Browser downloads and copies you share with others must be deleted separately; Gifable cannot recall them.
Scope and updates
This policy covers the local tools, account infrastructure and explicitly labelled online generation previews described above. Public availability and any authorized real-provider test are indicated in the relevant interface; disclosure of processing here does not mean the public AI service has launched. The date below identifies the current version of this policy.
See our Terms of Service and pricing page.