Legal
Privacy policy
Last updated November 17, 2026
What we store, why we store it, who else handles it, and how to reach us. We aim to say only what is true of the product today.
Who we are
SnapFeedback provides embeddable feedback widgets and a dashboard to collect and read the answers. It is operated by NAN DESENVOLVIMENTO WEB, CNPJ 41.755.673/0001-39, Recife/PE, Brasil. In this policy, "we" and "us" mean NAN DESENVOLVIMENTO WEB.
This policy covers the website at snapfeedback.app, the dashboard at app.snapfeedback.app, the widget script and the hosted survey pages.
Questions about this policy or your data go to privacy@snapfeedback.app.
Two groups of people
- Account holders sign up, build widgets and read responses in the dashboard.
- Visitors are the people who see a widget on an account holder's site, or open a hosted survey link, and may leave an answer.
What we store about account holders
- Account details: your email address, your name and company name if you add them, your password stored only as a one-way hash, and whether your email is verified.
- Sign-in sessions: each time you sign in, we keep a session record with the IP address and device information (the browser's User-Agent) the sign-in came from, plus an approximate location (city and country) taken from Cloudflare's request data. The account security page shows your sessions by device and approximate location, and you can end any of them there. We keep a session record while it is active. Signing out or ending a session deletes the record, and a session that has expired is no longer accepted.
- Your configuration: projects, widgets and their questions, allowed domains, colors, and the logos you upload, which we keep in Cloudflare storage.
- API keys: we keep only a one-way hash of each key and a short prefix to help you recognize it. The key itself is shown once, when you create it.
- Subscription records: if you pay, your Paddle customer and subscription identifiers, plan, billing interval, price, currency, status and period dates. Your payment card details are entered with Paddle and never reach our servers.
What we store about visitors
When a visitor submits a widget, we store the answers, the widget they answered and the time. We also store whether the answer came from an embedded widget or a hosted link, and the address of the page the widget was on.
We do not store the visitor's IP address or User-Agent with a response. Responses carry neither. To limit abuse, our rate limiting looks at the visitor's IP address for the length of a request window. It does not write the address to our database.
If the account holder's site calls identify(), we also store the visitor id and the attributes the site passes in, but only when that visitor submits a response. That information is chosen by the account holder, and we only hold what their site sends.
We count widget views as a daily total per widget. That count holds no visitor identifier, IP address, User-Agent or page address.
The widget remembers when it was last shown to a visitor, and whether they answered, in the visitor's browser storage (localStorage), so a widget does not reappear too often. The widget does not set cookies.
Responsibility for visitor data
The account holder decides what a widget asks and whether to identify visitors. The account holder is responsible for telling their visitors what they collect and for having a lawful reason to collect it. We store and process that data on their behalf to provide the service.
Cookies
The dashboard sets a sign-in session cookie to keep you signed in. The widget and the marketing site do not set cookies. We do not run third-party analytics or advertising trackers on the website or in the dashboard.
Who else handles your data
These companies process data for us to run the service.
- Cloudflare hosts the website, dashboard, widget and API, and provides our database, file storage, rate limiting and email. Cloudflare runs a global network, so data can be processed in more than one country. Requests to our services pass through Cloudflare, which sees the IP address of the request and may keep request and error logs as part of running the service.
- Paddle takes payments for paid plans and is the merchant of record. We share your email address and name with Paddle to create your customer record. Paddle handles your payment details, invoices and tax under its own terms and privacy notice.
We do not sell personal data.
Email we send
We send transactional email only: verifying your address, resetting your password, and confirming changes to your email address, sent from hello@snapfeedback.app.
Keeping and deleting data
- We keep your account data while your account exists. If you cancel a paid plan, you move to Free and your widgets and responses stay.
- Deleting a project in the dashboard deletes its widgets, their responses, its visitors and its stored logo.
- There is no delete account button yet. To delete your account, email privacy@snapfeedback.app from the address on the account. Deleting an account also deletes its projects, widgets, responses, sessions, API keys and subscription record.
- Paddle keeps the transaction records it is required to keep as merchant of record. We cannot delete those.
- You can export your responses as CSV before you leave.
Your rights
Depending on where you live, you may have the right to see the data we hold about you, correct it, export it, delete it, or object to how we use it. Email privacy@snapfeedback.app and we will help. If you are a visitor who answered a widget, the account holder who runs that widget is usually the best first contact, since they decide what the widget collects. We can help with a request you send to us.
Changes to this policy
If we change how we handle data, we will update this page and its date. For a material change, we will also email account holders.