When you use SnagFrog to keep a newsletter, run a roadmap, show testimonials, write to prospects or read your customers from Stripe or Polar, you decide what happens with those people's data and SnagFrog handles it for you. This page is the agreement that covers it. It is part of the Terms and applies to every workspace; there is nothing to sign.
1. Who and what this covers
This agreement is between Gjorge Karakabakov, who runs SnagFrog (“SnagFrog”, “I”), and the person or company that holds a SnagFrog workspace (“you”). Contact: hello@snagfrog.com.
It covers the personal data that your workspace processes through SnagFrog about other people (“workspace data”), as listed in section 2. For that data you are the controller and SnagFrog is your processor. If you are a processor for someone else, SnagFrog is your sub-processor and you pass on their instructions.
It doesn't cover your own account data (your email address, plan and sign-in records), or the website audits and search tools you run, which read public web pages. SnagFrog is the controller of those, as the privacy policy describes. Nor does it cover the sites and PocketBase backends Launchpad deploys to your own Cloudflare, Netlify and Fly.io accounts: SnagFrog doesn't host them or hold their users' data.
2. What is processed
- Purpose: keeping your newsletter's subscribers and sending your newsletters; taking and confirming votes and ideas on your roadmap and telling voters when an item ships; asking people for permission to show their words and showing them once they agree; finding business prospects, drafting emails to them and sending those emails from your own email account; reading your customers and subscriptions from your Stripe or Polar account to show your revenue.
- How long: for as long as you have a workspace, plus the periods in section 10.
- Whose data: your newsletter subscribers; people who vote or suggest ideas on your roadmap; people whose words you show as testimonials; the businesses and their contacts you find or add in Outreach; your customers in Stripe or Polar.
- What data: email addresses, with confirmation and unsubscribe dates and language; votes and ideas; a testimonial's words, name, title or company and photo, and the person's answer; a prospect's company, website, name and role, public business email address, why they fit and where that was found, the emails sent and their reply; a customer's name, email address, plan, monthly amount, status and dates.
- Sensitive data: none intended. The Terms forbid using SnagFrog to collect passwords, payment card details, health data or similar. Free text, such as an idea or a reply, can still contain whatever its writer chooses to include.
3. Your instructions
SnagFrog processes workspace data only on your instructions. Your instructions are: these terms, how you set up your workspace, and what you and your teammates do in the dashboard, through the API, or through an AI assistant you connect.
If I believe an instruction breaks data protection law, I'll tell you and may pause that processing. If a law requires SnagFrog to process workspace data in another way, I'll tell you first unless that law forbids it.
4. Confidentiality
Only people who need access to run the service have it, and they are bound to keep it confidential. Today that is one person.
5. Security
SnagFrog applies the measures listed at the end of this page and keeps them at least as protective as they are now. You're responsible for who you invite to your workspace, for your API tokens, and for what you connect.
6. Companies SnagFrog relies on
You authorise SnagFrog to use these sub-processors for workspace data:
- Fly.io: runs the database (PocketBase), in Frankfurt, Germany.
- Cloudflare (R2): stores files, such as 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 site and runs the server code in Frankfurt, and keeps standard request logs for a limited time.
- Resend: sends and receives email (confirmations, newsletters, testimonial requests, release notices, and replies to Outreach emails), in the United States.
- Anthropic: Claude finds Outreach prospects on the public web and drafts the emails to them, in the United States. It receives your app's description and each prospect's company, website, name and role.
- Google (Gmail): only for email that reaches SnagFrog without matching anything, which is forwarded to my inbox so it isn't lost.
Each is bound by its own data protection terms, and SnagFrog remains responsible to you for what they do with workspace data. Before adding or replacing one, I'll update this list and email workspace owners at least 30 days ahead. If you object on reasonable data protection grounds and we can't resolve it, you may cancel and get a refund for the unused part of a period you paid for.
Some companies are not on the list because they never receive workspace data: Polar handles SnagFrog's own payments as the merchant of record and sees only your billing details; Google Analytics counts visits to three public pages without cookies; and DataForSEO, Keywords Everywhere and Google's PageSpeed Insights receive only keywords, domain names, website addresses and public posts for the search tools and website audits.
Services you connect yourself (Stripe or Polar for your revenue, the Resend account Outreach sends from, Cloudflare, Netlify, X, TikTok, Instagram, YouTube, Google, Bing, an AI assistant) aren't SnagFrog's sub-processors. They receive or hold data on your instruction, under your own agreement with them.
7. Data leaving Europe
The database stays in the European Union. Files are stored with Cloudflare in the United States, email passes through Resend there, Outreach prospects' details go to Anthropic there, and stray mail reaches a Gmail inbox. Fly.io, Cloudflare, Supabase, Netlify, Resend, Anthropic and Google are companies based in the United States, so their staff there may be able to reach workspace data they hold in Europe, and a request to the site passes through whichever of Netlify's network locations is nearest to the sender on its way to Frankfurt. Those transfers rely on the safeguards in those providers' own data processing terms, such as the European Commission's Standard Contractual Clauses.
SnagFrog itself is run from outside the European Union, and I access workspace data from there to operate and support the service. Where that is a transfer of workspace data from the European Economic Area, the United Kingdom or Switzerland to a country without an adequacy decision, the Standard Contractual Clauses apply between you and SnagFrog and are part of this agreement. These are the clauses approved by the European Commission's Implementing Decision (EU) 2021/914 of 4 June 2021 (the “Clauses”).
- Which module: Module Two (controller to processor) where you are the controller, and Module Three (processor to processor) where you are a processor for someone else. You are the “data exporter” and SnagFrog is the “data importer”.
- Clause 7 (others joining the Clauses later): does not apply.
- Clause 9(a) (sub-processors): Option 2, general written authorisation, with the 30 days' notice in section 6.
- Clause 11 (an independent dispute resolution body): the optional wording does not apply.
- Clause 17 (governing law): the law of Ireland.
- Clause 18(b) (courts): the courts of Ireland.
- Annex I.A (the parties): you, with the details on your SnagFrog account, and SnagFrog as named in section 1. Agreeing to the Terms counts as both of us signing the Clauses.
- Annex I.B (the transfer): as described in section 2; continuous for as long as you use SnagFrog; kept for the periods in section 10.
- Annex I.C (supervisory authority): the data protection authority that supervises you, or, if you are outside the European Economic Area, the one where your representative is or where most of the people concerned live.
- Annex II (security): the security measures at the end of this page.
- Annex III (sub-processors): the list in section 6.
United Kingdom. For workspace data covered by UK data protection law, the Clauses apply as amended by the UK Information Commissioner's International Data Transfer Addendum (version B1.0), which is part of this agreement too. Its tables are filled in with the details above, and either of us may end it as its Table 4 allows.
Switzerland. For workspace data covered by Swiss data protection law, the Clauses apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, the Swiss Federal Data Protection and Information Commissioner as the supervisory authority, and people in Switzerland able to bring claims where they live.
8. Requests from the people concerned
If someone contacts SnagFrog about their workspace data, I pass the request to you and don't answer it for you, beyond telling them it has been passed on.
You can remove subscribers and testimonials in the dashboard, and delete roadmap items and whole apps at any time. Every newsletter and Outreach email has an unsubscribe link that works on its own. For anything you can't do in the dashboard, such as deleting one prospect or one voter, or a copy of one person's data, email me and it's done within 30 days.
9. If there is a breach
If SnagFrog becomes aware of a breach of security affecting your workspace data, I'll email workspace owners without undue delay, and within 72 hours where feasible. The email will say what happened, which data and roughly how many people are affected as far as known, what is being done, and how to reach me. I'll keep you updated as more is known.
10. Deletion and copies
- You can delete subscribers, testimonials, apps or your whole account at any time, and anything else on request (section 8). Deletion from the live systems is immediate and includes stored files.
- Disconnecting Stripe or Polar deletes the customers read from it.
- For a copy of one person's data or of a whole workspace, email me and you'll have it within 30 days.
- When a trial ends without a subscription, or a subscription ends, the workspace's apps and everything in them are kept for 90 days and then deleted. Members are emailed at least 14 days before. The workspace and your account stay.
- Backups kept by the hosting provider expire on the provider's schedule after that.
11. Checking that this is kept
On request I'll give you the information reasonably needed to show that SnagFrog keeps to this agreement. If that isn't enough for an obligation you have, you may audit once a year, on 30 days' notice, during working hours, at your own cost and without access to other customers' data.
12. Help with your own obligations
I'll give you reasonable help with data protection impact assessments and with consulting a regulator, where these concern SnagFrog's processing and you can't do them from what is already published here.
13. How this fits with the Terms
The liability limits in the Terms apply to this agreement, except where the law doesn't allow them to. If this agreement and the Terms disagree about workspace data, this agreement wins. If the Standard Contractual Clauses apply and disagree with either, the Clauses win.
Report data from before 9 November 2026
Bug reports, feedback and error tracking moved to StareGlare, a separate product. Reports, messages, files and captured errors SnagFrog collected for you before 9 November 2026 are still stored under this agreement, but no longer shown or added to. They are kept until you delete the apps they belong to or the 90-day rule in section 10 removes them. To ask about them, email hello@snagfrog.com.
Security measures
Each line describes what the service does today.
- In transit: HTTPS everywhere.
- At rest: the database and file storage are encrypted by the hosting provider. The keys and tokens of the services you connect are also encrypted by SnagFrog itself.
- Separation between workspaces: enforced on every request and in the database's access rules, and checked by automated tests on every change.
- Files: private unless you publish them, such as a testimonial's photo. Your team reaches private files only through links that expire.
- Sign-in: a one-time email link or Google; no passwords. Session cookies can't be read by page scripts. API tokens are stored only as a one-way hash and stop working when the person who made them leaves.
- Roles: owners and members. Invites, roles and renaming the workspace are for owners only.
- Activity log: changes to members, roles, tokens, connections and apps, published releases and plan changes are recorded with who made them, readable by owners, kept for a year, and cannot be edited or deleted through the service.
- Abuse limits: every public form and endpoint that accepts data or sends email is rate-limited, using a one-way hash of the IP address (or of the email address a message goes to) and never the address itself.
- Uploads: file types are restricted by the storage itself, and uploaded content is never shown as a web page.
- Scripts: a content security policy stops injected scripts from running.
- Outgoing requests: requests to websites, such as audits, Outreach and backend health checks, can't reach private network addresses.
- Less data to begin with: confirm and unsubscribe secrets are stored only as a hash or a signature, an address that unsubscribed or bounced is kept only to block it, and Outreach emails carry no tracking.
- Changes to the service: type checks, unit tests and database permission tests run on every change, and each release is checked on a draft before it goes live.
SnagFrog is run by one person and has not had an independent security audit or certification. Found a problem? See security.txt.
Changes
If this agreement changes in a way that matters, the date at the top changes and workspace owners get an email at least 30 days before it takes effect.