Privacy policy

Last updated 14 October 2026

Who this covers

This policy covers the hosted Sniffington app and website at sniffington.com, which are operated by KMF Ventures LLC.

What we collect

  • Your account: the email address you sign in with, your password if you set one (stored only as a salted hash we can't read back), and, if you use Google sign-in, the name and profile picture Google shares with us.
  • What you give the app: brand names, descriptions and keywords you track, workspace settings, notes and statuses you add to mentions, and API keys you create (stored hashed).
  • What the app finds: public posts and videos that match your keywords, with the author name, link and text as they were public, and the AI check's note on each.
  • Basic technical logs from our host, such as IP address and request time, used to keep the service running and block abuse.

Roadmap ideas

If you suggest something on the roadmap page, we store the title, the description, your email address and the name you chose to give. We use the address to confirm the idea is yours and to reply about it; it is never shown. An idea stays hidden until you confirm it and we publish it, and only the title, the description and the name you gave are shown. Ideas you never confirm are deleted after 7 days, rejected ones after 30. To remove a published idea or your address, email hello@sniffington.com.

Affiliate program

If you follow an affiliate's link (an address with ?via= in it), we keep a cookie with their code for 30 days, so that if you sign up we can credit them. If you then sign up, we share your account id and email address with our affiliate system so it can pay them their commission, and when you pay, the amount of each payment. Affiliates see that a referral signed up or paid, never your email address or what you track. If you join the program yourself, we share your name and email address with it to set up your affiliate account.

Google sign-in

If you choose Google sign-in, we ask Google for your email address, name and profile picture. Nothing else: we don't read your Gmail, Drive, Calendar or contacts, and we don't ask for those permissions. We use that information to create your account and sign you in, and for nothing else.

Sniffington's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Separately, we search YouTube through the YouTube Data API for public videos; that uses our own API key and none of your Google data. By using those searches you are also bound by the YouTube Terms of Service and the Google Privacy Policy.

How we use it

  • To run the app: find mentions, rule out namesakes, send you the alerts and sign-in emails you ask for.
  • To bill you, through Polar, when you pay for a plan.
  • To fix problems and keep the service secure.

We don't sell your data, we don't show ads, and we don't use your workspace content to train AI models.

Cookies

Three kinds. Essential: the session cookie that keeps you signed in, and one cookie that remembers your cookie choice. They need no consent. Attribution: when you first arrive from another site or from a link with campaign tags, a cookie called sn_ft keeps the campaign tags, the page you landed on and the name of the site that sent you, for 90 days; if you arrive through a partner's link, a cookie called sn_via keeps the partner's code and a random click number for 30 days, and the visit is reported to our partner program. When you create an account, we store what sn_ft holds with it and tell our partner program which partner's link brought it, so we know which sites, campaigns and partners bring people. Analytics: only if you accept, we use PostHog to see which pages and features get used, on the public site and inside the app. In the app that is named events such as creating a brand or changing a mention's status, tied to an anonymous user id and your plan, never your email, never the text of your mentions, and there is no session recording. On the public site the events also include which free tool you used and how many results it gave, never what you typed. The campaign tags and landing page that sn_ft holds are added to these events, and when you create an account the app reports it with the same tags, so we can tell which campaigns bring sign-ups. If you run a brand check, your browser also keeps a random check number, with the counts from that check and not the brand you typed, for 30 days, so a sign-up can be tied to the check that came before it. Declining removes it. If you decline, nothing is sent to PostHog and it sets no cookie. We never use advertising cookies. PostHog respects Do Not Track, and we remove anything you type into a tool from the address before it is sent. You can change your choice at any time under Cookie settings in the footer, or Settings, then Account, in the app.

Who else handles your data

A small number of service providers process data on our behalf. By kind:

  • Cloud hosting, databases and the AI check: United States and EU (EU workspaces are stored in the EU).
  • TypeSafe, whose Jev model ranks the posts we find, for every workspace including EU ones: United States. It receives the text of each public post, the post author's public handle, display name, follower count and bio, your brand's one-line description and the keyword that matched. The author details are public information about the person who wrote the post, not about you. It does not receive your account details. TypeSafe's terms say it does not train its models on what we send.
  • Email delivery for sign-in and alert emails: United States.
  • Payments, through Polar as merchant of record: United States.
  • Social data providers that run the searches on the platforms we cover: mostly the United States, and some elsewhere.
  • Google, for Google sign-in and YouTube searches: United States.
  • Website analytics, only if you accept cookies: United States.

Keywords you track are sent to the data providers to run searches; your account details are not. Providers are bound by data-processing terms. For the names of the providers behind each group, email hello@sniffington.com.

Where it's stored

Workspaces are created in the United States or the EU, and you choose when you sign up. EU workspaces have their data storage in the EU. Email, the AI model that ranks posts and some search providers run in the United States.

How long we keep it

We keep your data while your account is open. Delete a workspace or ask us to delete your account and we remove your account and workspace data from our live systems. Payment records are kept by Polar and by us for as long as tax law requires.

Your choices

  • Ask for a copy of your data, a correction, or deletion by emailing hello@sniffington.com.
  • Disconnect an AI agent or revoke an API key any time under Integrations in the app.
  • You can remove Sniffington's access to your Google account at myaccount.google.com/permissions.

If you are in the EU or UK, you also have the rights GDPR gives you, including the right to complain to your data protection authority.

Changes

If we change this policy in a way that matters, we'll update the date above and tell signed-in users by email.

Contact

Questions about your data: hello@sniffington.com.