Transparency

This page is a practical account of where Gatherly keeps data, what that data is, and how it can be deleted. It is meant to be readable without a lawyer. The Privacy Policy and Data Processing Agreement are the formal versions of the same facts.

Two kinds of data sit in Gatherly: your account (you are signing up with us) and your users’ feedback (you collect it through the widget; you control it, we host it).

Gatherly is a hosted web app. We do not run our own data center.

• Application hosting — Vercel runs the website, dashboard, APIs, and embed. On production, Vercel Web Analytics (cookieless) measures traffic on Gatherly’s own site.
• Database — Supabase (Postgres) stores accounts, projects, feedback, chats, reviews, and settings on servers in the EU (Ireland).
• Files — Supabase Storage, also in Ireland, holds bug-report images (JPEG/PNG), account avatars, and project icons.
• Authentication — Supabase Auth keeps sessions and hashed credentials. We do not store plaintext passwords. Google or GitHub hold the identity you authorize if you sign in with them.
• Payments — Stripe stores card details. We keep Stripe customer and subscription IDs, plan, and payment status, not full card numbers.
• Email — Resend delivers transactional mail (for example auth and invites).

Traffic to Gatherly uses HTTPS. Dashboard access is behind a signed-in session and project roles. Public widget APIs use your project public key; secret keys must stay on your server. Your database, files, and auth records in Supabase are stored in Ireland (EU). Other providers (Vercel, Stripe, Resend, Google, GitHub) may process data in the EU, the United States, or other regions they operate in. We use standard contractual clauses for those transfers where required.

We do not sell personal data. We do not use your users’ feedback content to train public AI models.

Your Gatherly account

• Email, name, avatar
• Auth identifiers (password hash or Google/GitHub ids)
• Plan, Stripe IDs, subscription status
• In-app notifications

Your project

• Name, slug, website URL, icon
• Public and secret API keys
• Widget appearance, copy, URL filters, feature flags
• Team members, roles, and pending invites
• Inbox workflow states and related settings

Feedback from people on your product

• Messages and type (general feedback, bug, idea, review, chat)
• Timestamps and the page URL where it was submitted
• Optional device metadata (browser, OS, screen size, user agent)
• Identity you send in a signed JWT, if you use one: user id, email, username, avatar URL, plan, Stripe customer id
• Bug screenshots (up to two JPEG/PNG images per report)
• Chat threads, messages, and reactions
• A per-project end-user profile built from identity claims (so the same person stays tied together in the inbox)
• Public feature-wall votes: an opaque cookie id and a hashed IP, not used for advertising

What appears in identity JWTs is your choice. If you put an email in the token, we store that email with the submission.

• Full payment card numbers (Stripe does)
• Plaintext passwords
• Advertising cookies, or analytics cookies on Gatherly itself (we do use cookieless Vercel Web Analytics on production for site traffic)
• Special-category data on purpose, do not send health records, card PANs, or similar through the widget

If you are a Gatherly customer

• One item — owners and admins can delete individual feedback, bug reports, and ideas from the inbox.
• Bulk delete — Project settings → Data (owners only). Delete general feedback, bugs, ideas, reviews, or chats: items older than 1, 3, 6, or 12 months; the oldest share of stored items when you are near the monthly response cap; or wipe a type, or everything in the project. A full wipe asks you to type the project name. This cannot be undone.
• Bug images — expire on the retention you set (default 30 days). Changing the setting applies to new uploads.
• A project — Project settings → Danger zone. That permanently removes the project and cascaded data: feedback, bugs, ideas, chats, reviews, feature wall, team access, keys, and files we stored for it. Type the project name to confirm. This cannot be undone.
• Your account — Account settings → Danger zone, after every project you own is deleted. That removes your profile, cancels Stripe, deletes your avatar, and signs you out. You are removed from projects you only joined as a member.

There is no in-app “download everything” export yet. You can read data in the dashboard and delete it from Project settings → Data. For a copy of your account data, email support@gatherly.sh.

If you are an end user of a product that uses Gatherly

Ask that product’s team. They control the inbox. We will help them delete or correct your data if they ask us. You can also email us at support@gatherly.sh and we will point the request to the right customer where we can.

We keep your users’ feedback until you delete it, you delete the project, or you close your account. We may also delete items older than the window for your current plan:

• Free and Starter — 1 year
• Growth — 3 years
• Scale — 5 years

We do not currently auto-delete on that schedule. We reserve the right to. If you switch to a lower plan, the shorter window applies. Bug images still expire on the retention you set (default 30 days). Billing records follow Danish accounting law (typically five years).

• Production rows and files for a deleted project or account are removed when the delete succeeds.
• Operational backups may still hold copies for a limited period, then they rotate out.
• Billing records may be kept as long as Danish accounting law requires (typically five years). Stripe may keep payment records under its own policy.
• Security and abuse logs may be kept longer when needed for fraud or disputes.

Privacy and deletion requests: support@gatherly.sh

Related pages: Privacy, DPA, Terms, Project data.