Your media is not uploaded to Transfa
The selected file is read into your browser and processed by a local worker. Previews, cleaned copies and ZIP creation happen on your device. There is no server endpoint for receiving media files.
Starting over or clearing a video releases the app’s file references. Closing the tab also releases the app’s working state. Files you downloaded or saved remain on your device. Your original file is never overwritten.
What the analytics count
We use a small service on the same host as Transfa. It adds up page loads, file-selection actions, successful or failed cleanup, download clicks, ZIP downloads, share-menu outcomes, media-mode changes and optional Instagram-result feedback.
Each count can have a fixed page category, format category, single/multiple batch category, touch/desktop category and broad referral category such as Google, Instagram, direct or referral. Campaign sources are reduced to the same fixed categories. We don’t send full URLs or query strings.
The same-host counters use no cookies, visitor IDs, fingerprinting, session recordings or personal profiles. That database stores daily totals, not raw event histories. We don’t store IP addresses, complete browser user agents, file names, file contents, photo tags, dimensions, duration, exact file sizes or error messages in analytics. Anonymous totals are retained for 180 days.
These are action counts, not unique visitors or unique people. Download clicks do not prove the file was saved, a closed share menu does not prove a particular destination received it, and optional success reports are not verified Instagram outcomes.
Optional Google Analytics and PostHog
If you choose Allow analytics, Google Analytics 4 and PostHog receive page views and fixed categories of tool actions, including the format group, touch/desktop group, single/multiple group and broad referral source. This helps us understand traffic and which steps people use. We do not send filenames, file contents, photo tags, exact dimensions, file sizes, video duration or free-text errors. Page addresses are limited to our public page paths; query strings, fragments and full referring URLs are not sent in our event properties.
Google Analytics may use first-party _ga cookies to recognize browsers, with a maximum lifetime of 180 days in our configuration. Advertising storage, advertising personalization and Google signals are disabled. Automatic enhanced measurement is disabled. Google may process request information such as IP addresses and browser information under its own policies. Google Analytics event data is set to two months and user data to fourteen months; aggregated reports can be retained longer.
PostHog receives explicit events through its EU ingestion endpoint. We use a random session identifier in session storage after consent, rather than a lasting visitor identifier. Person profile processing and IP geolocation are disabled for our events. We do not load its browser SDK, autocapture, heatmaps, surveys or session replay. Our PostHog Free plan provides one year of data retention. Request handling follows its policies.
Both providers necessarily receive a network connection when optional analytics run. Media processing stays local regardless of your choice. See Google’s privacy policy and PostHog’s privacy policy.
Change your choice anytime
Use Analytics settings in the footer to allow or reject optional analytics. We remember this choice in local storage for 180 days. Turning analytics off stops new events, clears our Google Analytics cookies and PostHog session identifier on this browser, and reloads the page to unload the Google tag. This does not delete data already received by providers.
Do Not Track or Global Privacy Control disables all our analytics even if you previously allowed them. You can block analytics requests and the file tools still work. If browser storage is unavailable, your choice applies to the current page only.
The optional “did the label disappear?” buttons count your answer without attaching it to a person or file. You can simply skip them.
Ordinary website requests and device sharing
The server necessarily handles your connection when you load the website. Normal hosting access logs may include connection information such as IP addresses and requested pages. Those logs are separate from the anonymous analytics counters. The analytics request endpoint does not write its own access log.
Fonts and images are served locally. The Google tag is loaded only after optional analytics consent. PostHog uses explicit event requests after that same consent; no advertising widget is loaded. Links to sources and social platforms open external sites whose privacy practices are their own.
Save / share opens your device’s native menu only when you tap it. If you choose another app, that app receives the cleaned file. Transfa doesn’t choose the destination or automatically post on your behalf.
Questions about limitations or test evidence? Read About Transfa and our testing.