Fun Fact Lab / Privacy
Privacy, explained clearly.
This website has no user accounts, no contact form and no newsletter. You can explore without submitting personal information.
Last updated:
What the site measures
We use Vercel Web Analytics for aggregate website usage, such as page views, referrers, browser/device information and approximate location (which may include country, region and city). It uses a temporary, privacy-preserving visitor identifier rather than an analytics cookie. We also record outbound video and channel clicks with a fixed destination identifier, platform and language. We do not send entered text, names, Instagram messages or account identifiers in those events. We do not use advertising pixels.
Your language preference
When you manually choose a language, the essential first-party cookie ffl_locale stores en, pt or es for up to one year. It is available across this website, uses SameSite=Lax and uses Secure on HTTPS. You can remove it in your browser settings. Without it, the homepage and /links use your browser’s language preference, with English as the fallback.
Hosting and external services
Our hosting provider processes the technical information needed to deliver and protect the site, which may include IP addresses and request logs. Vercel provides our analytics service. Videos are linked, not embedded: YouTube and Instagram receive a request when you choose to visit them and apply their own policies. Reference sites also apply their own policies.
Your requests and Meta data
This website does not receive Meta profile data and has no Meta login. Messages sent through Instagram remain on that platform. To ask about access, correction or deletion of data associated with an interaction, send a direct message to our verified Instagram profile for your language. See our data-deletion instructions for the steps. No technical deletion callback is currently provided.
Changes to this notice
If our data collection changes, this notice will be updated. A future Meta integration requires updated policies and an appropriate deletion callback before it is used.