Privacy policy

This policy covers two groups of people:

• Customers: people who sign up for Featdock and use the dashboard. For your data, Featdock is the controller.
• End users: people who use a customer's site or app where Featdock widgets run. For their data, the customer is the controller and Featdock is a processor acting on the customer's instructions.

• Account details: your name, email address and team memberships.
• Project settings: allowed domains, theme, widgets and content you create.
• Billing details from Paddle: your plan, subscription status, country and invoices. Paddle processes your card; we never see full card numbers.
• Technical data when you use the dashboard: IP address, browser and error reports, used for security and fixing bugs.
• Messages you send us for support.

Depending on which widgets a customer uses and what they send us, Featdock processes the following about end users:

• A random visitor id stored in the browser's local storage, so widgets know whether someone is new or returning and which widgets they've dismissed.
• Identifiers and attributes the customer sends with identify(), such as a user id, plan or signup date.
• Events: custom events sent with track(), and widget events (shown, clicked, dismissed, completed, submitted) with the page URL and time.
• Submissions: survey answers, feature requests and votes.
• Bug reports: the description, a screenshot of the page as the user saw it, the URL, browser, operating system, viewport size and the last 20 console errors. Screenshots are stored in Cloudflare R2; we re-encode them and strip their metadata.
• Testimonials: the name, role, text, rating and avatar the person chooses to submit.
• Request data: IP address and user agent, used to check the request comes from an allowed domain and to rate-limit abuse.

If you are an end user and want to access or delete your data, contact the site you used. We'll help them respond.

• To run the service: show widgets, store submissions, and show customers their analytics.
• To keep it secure: check domains, rate-limit, and prevent spam and abuse.
• To send sign-in links, billing notices and the notifications you turn on.
• To provide support and fix errors.

We don't sell personal data, we don't use it for advertising, and we don't use one customer's end-user data for another customer.

The dashboard uses a secure, http-only cookie to keep you signed in. On customers' sites, the SDK uses local storage for the visitor id, a short event log for targeting, and which widgets were dismissed or completed. It doesn't set advertising or cross-site tracking cookies.

This website doesn't use analytics or advertising cookies.

We use these providers to run Featdock. Each only gets the data it needs for its job.

These providers may process data outside your country. Where the law requires it, we rely on safeguards such as standard contractual clauses.

We keep data while your account is open. When you delete a widget, a project or your account, we delete the related data, including end-user submissions and screenshots, except records we must keep by law, such as billing records.

Data is encrypted in transit. Every database query is scoped to one project, public keys only work from the domains you allow, uploads are size-limited and stored under random names, and passwords, if you set one, are hashed. No system is perfectly secure; if a breach affects your data, we'll tell you without undue delay.

Depending on where you live, you can ask to access, correct, delete or receive a copy of your personal data, and object to or restrict how we use it. Email [email protected] and we'll reply within 30 days. You can also complain to your local data protection authority.

Featdock isn't meant for children, and we don't knowingly collect data from anyone under 16 through the dashboard.

If we change this policy in a way that matters, we'll email account owners before it takes effect. Questions go to [email protected]. See also our terms of service.