SnagFrog
Compare Guides Docs Privacy Terms Contact us

Privacy

Last updated 9 November 2026

On this page

  1. Who this is about
  2. Why SnagFrog is allowed to use this data
  3. Newsletter subscribers
  4. Roadmap voters
  5. Testimonials
  6. Outreach prospects
  7. Customers from Stripe or Polar
  8. Releases and changelogs
  9. Website audits
  10. Search and mention tools
  11. What SnagFrog keeps about developers
  12. Email
  13. AI assistants
  14. Tools a developer connects
  15. Posting to TikTok
  16. Posting to Instagram
  17. Posting to YouTube
  18. Google user data
  19. How data is protected
  20. Where data is stored
  21. Cookies
  22. Visitor counts
  23. How long data is kept
  24. Reports from before 9 November 2026
  25. If something goes wrong
  26. Children
  27. Your rights
  28. Changes

SnagFrog is a workspace for building, running and growing apps and games. It collects what it needs to do that, and nothing else. No ads, no trackers on the dashboard, and nothing is sold.

Bug reports, feedback and error tracking have moved to StareGlare, a separate product with its own privacy policy. SnagFrog no longer collects them.

SnagFrog is run by Gjorge Karakabakov. Questions or requests: hello@snagfrog.com.

Who this is about

  • Developers sign up, add their apps, and use SnagFrog to build, run and grow them.
  • The people developers reach through SnagFrog: newsletter subscribers, people who vote on a roadmap, people whose words are shown as testimonials, businesses contacted with Outreach, and the developer's own customers, read from their Stripe or Polar account. None of them need an account.

For the second group, the developer decides what happens with your data (in privacy-law terms they're the controller and SnagFrog processes the data on their behalf, under the Data Processing Agreement). To get a copy of your data, or to have it changed or deleted, ask the developer, or email me and I'll pass it on.

Why SnagFrog is allowed to use this data

European and UK law ask for a reason for each use of personal data. These are SnagFrog's.

  • A developer's email address and workspace, sign-in links, notifications, invites and the plan a workspace is on: needed to provide the service they signed up for (contract).
  • A one-way hash of your IP address, and of an email address a sign-in link, confirmation or invite is sent to, kept for up to a day: to stop spam and abuse of public forms and sign-in (a legitimate interest in keeping the service usable and safe).
  • Server logs: to find and fix faults (a legitimate interest in running a reliable service).
  • Website addresses a developer asks SnagFrog to audit, and the results: needed to provide the service they signed up for (contract).
  • Visit counts on three public pages, without cookies: to know whether those pages are read (a legitimate interest; nothing is stored on your device).
  • Subscribers, voters, testimonials, outreach prospects and customers: handled for the developer, who decides why they're collected and is responsible for the reason. SnagFrog acts on the developer's instructions.

Where the reason is a legitimate interest you can object, and I'll stop unless there's a compelling reason to continue.

Newsletter subscribers

A developer can collect newsletter signups on their app's public page or their own website. SnagFrog keeps your email address, where you signed up, your language and when you subscribed, confirmed or left. You get one email to confirm, and nothing more unless you do. Every newsletter has an unsubscribe link and a one-click unsubscribe header; using either stops further newsletters at once. Newsletters are sent through Resend. The developer can also remove you, and you can ask them or me to delete your address.

Roadmap voters

A developer can publish a roadmap where people vote and suggest ideas. To vote you give your email address, and SnagFrog sends one link to confirm it; a vote counts only once you do. SnagFrog keeps your address, your language, your votes and any idea you send, and a cookie that remembers the confirmed browser (see “Cookies”). When an item you voted for ships, you get one email saying so. Votes are never shown with your address. To have your votes and address deleted, ask the developer or email me.

Testimonials

A developer can ask someone whether a few words of theirs may be shown on the app's website. That person gets one email with a link (and, if they don't answer, at most one more after three days). Nothing is shown unless they say yes on that page; they choose the name, the title or company and the photo shown with it, and the same link withdraws their yes at any time, which takes the words down at once. If the words change after a yes, they come down until the person agrees again. A photo they add is public, because it is shown next to their words, and is deleted when they remove it or the testimonial is deleted.

Outreach prospects

A developer can use Outreach to find businesses that may want their app and write to them. Claude, an AI model by Anthropic, searches the public web for suitable businesses and drafts the emails; the developer approves them before anything is sent. If you were found this way, SnagFrog keeps your company's name and website, your name and role if a public page gives them, a public business email address, why you seemed a fit and where that was found, the emails sent to you, and your reply.

  • The emails are sent from the developer's own Resend account and domain, in their name, not from SnagFrog. They are plain text, with no tracking.
  • Each one has an unsubscribe link and a one-click unsubscribe header. A reply or an unsubscribe stops the sequence, and an address that unsubscribed or bounced is never written to again from that workspace.
  • The developer is the sender and the controller. To object or have your data deleted, reply to the email, use the unsubscribe link, or email me and I'll pass it on.

Customers from Stripe or Polar

A developer can connect their own Stripe or Polar account with a read-only key, so SnagFrog can show their revenue. For each subscription SnagFrog reads and keeps the customer's name and email address, the plan, its monthly amount and status, and when it started, renews or was cancelled. Nothing is written back and no card details are read. The data is refreshed every few hours and deleted when the developer disconnects or deletes the app.

Releases and changelogs

A developer can publish a release: a version number and notes they write, shown on a public changelog page for their app. A developer can also show the changelog, roadmap or testimonials on their own website. That page then loads them from SnagFrog: no cookie is set and nothing is stored, and the request appears in the host's standard logs like any other.

Website audits

A developer can ask SnagFrog to audit a website for search engines and AI answers, once or on a weekly or monthly schedule. A separate audit service, run by SnagFrog on Fly.io in Frankfurt, then visits that site's public pages the way a search engine does, and may visit a few public pages of competing sites it finds by searching DuckDuckGo or Bing for the site's topics. It asks Google's PageSpeed Insights for speed measurements of the site's address. It is given the address, an internal reference, and on some plans the workspace's name to print on the report. It never receives anything else from the workspace.

An audit's results quote short pieces of the public pages it read, such as titles and headings. The results and the finished report (a web page and a PDF) are kept until the developer deletes the audit; deleting it removes them from SnagFrog's database and from the audit service. The audit's site address and date stay, so the month's allowance is counted correctly. When a whole workspace is deleted, its audit reports are removed from the audit service too; if that service is asleep at that moment, SnagFrog keeps asking until it confirms.

Search and mention tools

SnagFrog helps a developer see how their app is found: keyword research, search rankings, answers that AI assistants give about their topic, backlinks, and public posts that mention the app on Hacker News, Bluesky, Mastodon, Lobsters, Product Hunt and Reddit. This uses public data. Keywords, domain names, questions and the text of mentions found are sent to DataForSEO, a paid data provider, which also asks AI models for their answers and for how relevant a mention is. SnagFrog keeps the public posts it finds, with their author's public handle and link, until the developer deletes them or the app. SnagFrog never posts, votes or messages on those sites.

What SnagFrog keeps about developers

  • Your email address, used to sign in with a one-time link or with Google. Signing in with Google shares your name and email address with SnagFrog; only the email is used.
  • Your workspace: apps and their settings, Launchpad projects, designs and builds, releases, roadmaps, newsletters, testimonials, Outreach, website audits and their schedules, and scheduled posts.
  • API tokens, stored only as a one-way hash.
  • An activity log for the workspace's owners: who invited or removed a member, changed a role, created or revoked a token, connected a service, created or deleted an app or published a release, and when the plan changed, with the email address of whoever did it. It is kept for a year; when someone deletes their account their address is taken out of it.

Email

SnagFrog sends sign-in links, invites, notifications and digests to developers, and on a developer's behalf newsletter and voting confirmations, newsletters, testimonial requests and release notices. These go through Resend. Outreach emails go through the developer's own Resend account instead, and replies to them may come back through SnagFrog so the sequence stops. Email that reaches SnagFrog without matching anything is forwarded to my own inbox, hosted by Google (Gmail), so it isn't lost. Alerts about server errors go to the same inbox; they contain the address of the page that failed and a technical trace. Email you send to hello@snagfrog.com is passed to that inbox by ImprovMX, a forwarding service.

AI assistants

Developers can connect an AI assistant, such as Claude, to their workspace through SnagFrog's MCP server or API tokens, for example to build an app with Launchpad. Data the assistant reads is then sent to that AI provider under the developer's own account and the provider's terms.

SnagFrog itself sends data to AI models in two places: Outreach, which uses Anthropic's Claude to find prospects and draft emails (see “Outreach prospects”), and the search tools, which reach AI models through DataForSEO. It doesn't send newsletter subscribers, voters, customers or developers' account data to AI providers.

Tools a developer connects

A developer can connect their own accounts: Cloudflare or Netlify, where Launchpad deploys their sites; Stripe or Polar, to read revenue; Resend, to send Outreach email; X, to post; and Google, Bing, TikTok, Instagram and YouTube, described below. Launchpad backends run on PocketBase in the developer's own Fly.io account, and SnagFrog never holds their admin password. What SnagFrog sends to these accounts goes there on the developer's instruction, under that service's terms. The keys are stored encrypted.

Posting to TikTok

A developer can connect their own TikTok account to schedule videos and have SnagFrog publish them at the chosen time. They approve this on tiktok.com, and SnagFrog never sees their TikTok password. It asks TikTok for two permissions: user.info.basic, to show which account is connected, and video.publish, to publish the videos the developer scheduled. Nothing is published unless the developer scheduled it, or asked an AI assistant they connected to schedule it.

  • What SnagFrog gets from TikTok: the account's ID, username, display name and profile picture, who the account may post to, the longest video it may post, and the status of each post.
  • What SnagFrog keeps: that information, the access tokens (encrypted), and for each video the file, caption, audience, comment, duet and stitch settings, content disclosure settings and schedule.
  • What goes to TikTok: the video and those settings, when it is time to publish, to the developer's own account and under TikTok's terms and privacy policy.
  • How it is used: only to show the developer their account and to publish and track their videos. It isn't sold, used for advertising, or shared with anyone else, apart from the hosting providers listed below.
  • Removing it: disconnecting in the dashboard deletes the tokens and asks TikTok to revoke them; access can also be removed in TikTok's own settings. The video history stays until the developer deletes it. Deleting a video in SnagFrog removes SnagFrog's copy only; a video already published stays on TikTok until it is deleted there. Deleting the workspace or account removes everything SnagFrog holds.

Posting to Instagram

A developer can connect their own Instagram professional account (Business or Creator) to post the same videos as Reels, at the same time or on their own. They approve this on Instagram's own login page, and SnagFrog never sees their Instagram password. SnagFrog asks for two permissions, instagram_business_basic and instagram_business_content_publish, which it uses to show which account is connected and to publish the videos the developer scheduled. It reads no comments, messages or insights. Nothing is published unless the developer scheduled it, or asked an AI assistant they connected to schedule it.

  • What SnagFrog gets from Meta: an access token for the shared account, the account's ID, username, name, profile picture and account type, and for each post its status, its ID and its link on Instagram.
  • What SnagFrog keeps: that information, the access token (encrypted), and for each video the file, caption, whether it also shows in the profile grid, and schedule.
  • What goes to Meta: the caption and a private link to the video that expires within hours, which Instagram uses to fetch the video when it is time to publish, to the developer's own account and under Meta's terms and privacy policy.
  • How it is used: only to show the developer their account and to publish and track their videos. It isn't sold, used for advertising, or shared with anyone else, apart from the hosting providers listed below.
  • Removing it: disconnecting in the dashboard deletes the token; access can also be removed in Instagram's settings (Apps and websites). The video history stays until the developer deletes it. Deleting a video in SnagFrog removes SnagFrog's copy only; a Reel already published stays on Instagram until it is deleted there. Deleting the workspace or account removes everything SnagFrog holds. To ask for deletion by email, write to hello@snagfrog.com.

Posting to YouTube

A developer can connect their own YouTube channel to upload the same videos as Shorts, at the same time or on their own. SnagFrog uses the YouTube API Services for this; by connecting, the developer agrees to the YouTube Terms of Service, and Google's Privacy Policy applies. They approve this on Google's own sign-in page, and SnagFrog never sees their Google password. SnagFrog asks for two permissions, youtube.upload and youtube.readonly, which it uses to upload the videos the developer scheduled and to show which channel is connected. It reads no comments, analytics or other videos. Nothing is uploaded unless the developer scheduled it, or asked an AI assistant they connected to schedule it.

  • What SnagFrog gets from Google: a refresh token for the channel, the channel's ID, handle, name and picture, and for each upload its video ID.
  • What SnagFrog keeps: that information, the refresh token (encrypted), and for each video the file, title, caption, who can see it, and schedule.
  • What goes to Google: the video file, its title, the caption as its description, and who can see it, to the developer's own channel when it is time to upload.
  • How it is used: only to show the developer their channel and to upload and track their videos. See “Google user data” for who it is shared with and “How data is protected” for how it is kept safe.
  • Removing it: disconnecting in the dashboard deletes the token; access can also be removed on the Google security settings page. The video history stays until the developer deletes it. Deleting a video in SnagFrog removes SnagFrog's copy only; a Short already uploaded stays on YouTube until it is deleted there. Deleting the workspace or account removes everything SnagFrog holds.

Google user data

“Google user data” here means what SnagFrog receives from a developer's Google account when they choose to connect it: their name and email address when they sign in with Google, their Search Console and Google Analytics reports, and their YouTube channel's profile, refresh token and video IDs. SnagFrog's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

  • What it is used for: only to show the developer their own data in their workspace and, for YouTube, to upload the videos they scheduled. It isn't sold, used for advertising, used to train AI models, or used to build profiles of anyone.
  • Who can see it: the members of the workspace it was connected to, and an AI assistant only if a member connects one to that workspace and asks it to read the data on their behalf. Nobody else.
  • Who it is shared with: no one, except the service providers that store and run SnagFrog for me, only as far as they need to do that, under their data processing terms: Fly.io (the database, in Frankfurt), Netlify (the server code, in Frankfurt) and Cloudflare (stored files, such as a video waiting to be uploaded, in the United States). YouTube videos go to Google itself, to the developer's own channel. Google user data is never transferred to anyone else, unless the law requires it, it is needed to protect someone's safety or to investigate abuse, or SnagFrog is merged or sold, in which case this policy keeps applying to it and developers are told first.
  • People: I don't read it, except with the developer's permission (for example to help with a problem they report), for security, or when the law requires it.
  • Deleting it: disconnecting a Google service in the dashboard deletes its token, and deleting the workspace or account deletes all of it. You can also revoke SnagFrog on the Google security settings page, or email me to have it deleted.

How data is protected

  • In transit: every connection to SnagFrog, and from SnagFrog to its providers and to Google, TikTok and Meta, is encrypted with HTTPS (TLS).
  • Tokens and keys: the access and refresh tokens for Google, TikTok and Instagram, and the keys of other connected tools, are encrypted in the database with AES-256-GCM. The encryption key is kept apart from the database, so a copy of the database alone doesn't reveal them.
  • At rest: the database and stored files sit on encrypted disks at the providers above.
  • Access: each workspace's data can only be read by its own members, which SnagFrog checks on every request. Files are private and only shown through links that expire. Only I can administer the servers and the database.
  • Keeping it small: SnagFrog asks Google for the narrowest permissions that do the job (read-only for Search Console and Analytics; uploading and reading the channel's profile for YouTube) and keeps only what is listed above.

Where data is stored

  • Fly.io: runs the database and sign-in (PocketBase) in Frankfurt, Germany, and the website audit service, which holds audit reports.
  • Cloudflare (R2): stores files, such as scheduled videos and testimonial photos, in the United States.
  • Supabase: held the database until October 2026, in Frankfurt. A read-only copy is kept there until the move is complete, then deleted.
  • Netlify: hosts the website and runs the server code in Frankfurt. Like any host it keeps standard request logs for a limited time.
  • Resend: sends and receives email, in the United States.
  • Anthropic: Claude finds Outreach prospects and drafts their emails, in the United States. It receives the app's description and public details about each prospect.
  • DataForSEO: receives keywords, domain names, questions and the text of public mentions for the search tools, and returns search data and AI models' answers.
  • X and twitterapi.io: if you connect X, SnagFrog posts through X's own API, and reads public profiles, posts and their numbers through twitterapi.io.
  • Google (PageSpeed Insights): receives the address of a website being audited and returns speed measurements.
  • Google (Search Console, Analytics): if you connect them, SnagFrog reads your site's search data (searches, pages, impressions, clicks, positions) and your Google Analytics reports (visitors, pages, sources, countries, devices) with read-only access. Analytics reports are kept for up to 7 days and refreshed every 10 minutes while you look at them. You can disconnect at any time, which revokes that access.
  • Microsoft (Bing Webmaster Tools): if you connect it, SnagFrog reads your site's Bing search data (searches, impressions, clicks, positions) with your API key. You can disconnect at any time, and delete the key in Bing Webmaster Tools.
  • TikTok: if you connect it, receives the videos you schedule and their settings, and returns your basic profile and each post's status. See “Posting to TikTok”.
  • Meta (Instagram): if you connect it, receives the captions and videos you schedule as Reels, and returns your Instagram account's basic profile and each post's status. See “Posting to Instagram”.
  • Google (YouTube): if you connect it, receives the videos you schedule as Shorts with their titles and captions, and returns your channel's basic profile and each upload's ID. See “Posting to YouTube”.
  • Keywords Everywhere (Open PageRank): receives the domain names of audited websites, of apps' websites and of the competitors you list, and returns how strongly other sites link to each. Nothing else is sent.
  • ImprovMX: forwards email sent to hello@snagfrog.com to my inbox.
  • Google (Gmail): hosts that inbox.
  • Polar: handles payments for paid plans as the merchant of record. Card details go to Polar and its payment processor, never to SnagFrog; SnagFrog only learns the plan, its status and your billing email.
  • Google Analytics: counts visits to the public pages. Google processes that data on its own servers, including in the United States. See below.

See “How data is protected” for how this data is kept safe.

Data leaving Europe. The database stays in Frankfurt; stored files are kept with Cloudflare in the United States. Email passes through Resend in the United States, Google processes visit counts and the forwarded mail above there too, and SnagFrog itself is run from outside the European Union. Supabase, Netlify, Resend, Fly.io, Cloudflare, Anthropic, Polar, Google, Microsoft and Meta are companies based in the United States, so their staff there may be able to reach data they hold in Europe, and a request to the site passes through whichever of Netlify's network locations is nearest to you on its way to Frankfurt. Those transfers rely on the safeguards in each provider's data processing terms, such as the European Commission's Standard Contractual Clauses. You can ask me for details.

Cookies

The dashboard sets a sign-in cookie so you stay signed in. Asking for a sign-in link sets one for an hour, so the link opens straight away in the browser that asked for it, and signing in with Google sets one for a few minutes to remember which page to return to. Picking a light or dark theme sets one that remembers it for a year, and the dashboard keeps a few of your own choices (a dismissed hint, a folded sidebar) in your browser's storage. Confirming your email on an app's roadmap sets a cookie for a year so later votes from that browser count straight away; it holds a random code, not your address, and is only sent to that app's pages. Nothing else sets cookies. Google Analytics runs without cookies (see below). There's no advertising on any page.

Visitor counts

The home page, this page and the terms count visits with Google Analytics: which of those pages were opened and where visitors came from. It runs with storage switched off, so it sets no cookies, keeps nothing in your browser and can't tell that two visits came from the same person. Google receives your IP address to estimate a rough location and, by its own account, doesn't store it. Advertising features and Google Signals are switched off, and there's no session recording. Page addresses are sent without query strings and invite links are redacted, so sign-in and invite tokens never reach Google. The sign-in page, invite pages, apps' public pages and the dashboard don't load it at all, and it's switched off as soon as you navigate into them.

How long data is kept

  • Subscribers, voters, testimonials and Outreach prospects stay until the developer deletes them, the app, or their account, or until someone asks for theirs to be deleted. Someone who unsubscribes is kept as unsubscribed, so they aren't written to again.
  • A roadmap voter who never confirms their email address is deleted after 7 days.
  • Customers read from Stripe or Polar stay until the developer disconnects the account or deletes the app.
  • Releases, website audits and their reports stay until the developer deletes them or their account.
  • Scheduled and posted videos (TikTok, Instagram and YouTube) stay until the developer deletes them or their account. A video added but never saved on a post is deleted within about a day.
  • A workspace that has had no plan for 90 days, after its trial or subscription ended, has its apps and everything in them deleted. Its members are emailed at least 14 days before.
  • A workspace's activity log is kept for a year.
  • Files that were uploaded but never used are deleted within about a day.
  • The hashed IP and email addresses used for rate limits are deleted within a day.
  • Developers can delete their account and everything in it under Account in the dashboard. It happens immediately, and also removes their email address from anything left in a workspace they shared. You can also email me.
  • Backups and email logs kept by the hosting and email providers expire on those providers' schedules after that.

Reports from before 9 November 2026

Bug reports, messages, files and captured errors that SnagFrog collected before 9 November 2026 are still stored, but no longer shown or added to. They are kept until the workspace deletes its apps or the 90-day rule above removes them. To ask about yours, or to have it deleted sooner, email hello@snagfrog.com.

If something goes wrong

If there's a security incident that affects your data, developers are emailed without undue delay with what happened and what's being done. Developers are responsible for telling the people whose data they hold; I'll give them what they need to do that.

Children

SnagFrog isn't meant for children, and developers must be old enough to enter a contract. A developer who lets younger people subscribe to a newsletter or vote on a roadmap is responsible for doing that lawfully.

Your rights

You can ask for a copy of your data (in a form you can take elsewhere), a correction, or deletion. SnagFrog makes no decisions about you by automated means. If you're in the EU or UK you also have the right to object, to restrict processing and to complain to your data protection authority. Where a developer controls your data, ask them, or email me and I'll pass it on. Email hello@snagfrog.com; I answer within 30 days.

Changes

If this page changes in a way that matters, the date at the top changes and developers get an email.

SnagFrog by Karakabakov · Also made here: Orbit X — grow on X Privacy · Terms · DPA