Legal

Privacy Policy

Last updated: 30 October 2026

This policy explains what personal data Agile Feedback handles, why, where it goes and how long we keep it. It covers our website, our dashboard and API, and the bug report widget that our customers add to their own websites.

1. Who we are

Agile Feedback is run by Agile Pixel Limited, a company registered in England and Wales with company number 08483922. Our registered office is 3 Whiteley Croft Rise, Otley, LS21 3NR, United Kingdom.

To contact us about privacy, use our contact form or email [email protected].

2. Our two roles

We are the controller for data about people who have an account with us, people who visit our website and people who contact us. We decide how that data is used.

We are a processor for bug reports. When you send a report through the widget on someone else’s website, that website’s owner is the controller. They chose to add the widget, decide which pages it runs on and decide where reports go. We handle reports for them and on their instructions.

If you have sent a report and want to know what happened to it, or want it deleted, please contact the owner of that website. If you contact us instead, we will pass your request on to them.

When a page with the widget loads

The visitor’s browser downloads the widget from our servers and checks its screenshot settings with us. Like any web request, this tells our server the visitor’s IP address and browser details. Our server keeps them in a session record that expires after 120 minutes and is then cleared out.

Nothing about the page itself leaves the browser until someone clicks the report button. The widget then starts copying the page for the screenshot, as described below, even if they close it without sending a report.

When someone sends a report

A report contains:

What the reporter types: a title and an optional description. The widget doesn’t ask for the reporter’s name or email address.
A screenshot with any annotations the reporter draws on it. A “quick issue” has no screenshot.
Attachments: up to 5 images the reporter chooses to add, of up to 10 MB each.
Page and browser details: the page address and title, the time, the browser’s user agent, language and platform, the number of processor cores and the device memory (where the browser shares them), the screen and window sizes, the pixel ratio and how long the screenshot took.
Recent console messages: the last 50 log, warning and error messages written to the browser console on that page, each cut to 1,000 characters. They can contain anything the website’s own code writes there.
A page fingerprint: a code worked out from the page’s structure (its tag and class names, not its text). It helps spot duplicate reports.
The reporter’s IP address and user agent, which our server records when the report arrives.

How screenshots are made

Usually the widget copies the page’s content and layout in the browser and sends that copy straight to our screenshot service. Password fields are masked in the copy. To draw the screenshot, the service may fetch the page’s images and fonts from their usual web addresses. It sends the image back to the browser and doesn’t keep the copy.

On a desktop computer, the reporter can choose an exact capture instead. Their browser then asks permission to share the tab and takes the screenshot itself.

Either way, a screenshot shows whatever was on the screen, which can include personal data.

The widget doesn’t set cookies or store anything on the website it runs on. Our Cookie Policy explains the hidden page it uses to send reports.

4. Where reports go

We store each report, with its screenshot and attachments, on our servers and show it in the website owner’s dashboard. The owner can also read reports, including console messages, through our API and MCP server using an API token. So can any tool the owner connects with that token.

We email the website owner when a new report arrives, with its title and description. Owners can turn these emails off.

We send each report to the tools the owner has chosen. Each tool receives:

Trello: a card with the title, description, page address and title, browser user agent and window size. The screenshot and attachments are uploaded to the card.
Jira: an issue with the same details. The screenshot and attachments are uploaded to the issue.
Asana: a task with the title, description, page address and title. The screenshot and attachments are uploaded to the task.
Slack: a message with the title, description, page address and title, browser user agent and window size. The screenshot and attachments are uploaded to the message’s thread.
Monday.com: an item with the title, description, page address and title, the time, the browser and operating system, language, platform, and window and screen sizes. The screenshot and attachments are uploaded to the item.
GitHub: an issue with the title, description, page address and title, browser user agent and window size. The screenshot and attachments are not uploaded to GitHub. The issue links to them on our servers instead, so anyone who can see the issue may be able to open them. On a public repository, that means anyone.

We don’t send console messages, the page fingerprint or the reporter’s IP address to these tools. The one exception is Monday.com: through our API or MCP server, a website owner can choose to copy other page details, including console messages, into columns on their board.

Once a report is in one of these tools, it is held under the owner’s account with that tool and that tool’s own privacy policy applies. Deleting a report from Agile Feedback doesn’t delete it there.

5. What we collect about account holders

Your account: your name and email address, your password (we store only a secure hash of it), whether you have verified your email address, and your notification choices.
Google sign-in: if you sign in with Google, Google tells us your name and email address. We never see your Google password.
Sign-up answers: whether you signed up with an email address or with Google, which describes you best (an agency or freelancer, an in-house team, or something else), and, if you choose to tell us, how you heard about us. The first is required; how you heard about us is optional. If you sign up with Google, we ask these on a short page before your dashboard opens.
Where you first came from: when you sign up, we save on your account the first touch from your visit, described in section 6.
Your first delivered report: the date your account’s first report reached one of your tools. For accounts that had reports before we started recording this, we used the date their first delivered report was sent.
Elite interest: if you choose Tell me when it’s ready on the Elite plan, we record when you asked. If you aren’t signed in, we hold your request in your session and record it when you sign up or sign in. We use it to email you when Elite is ready, which we do ourselves rather than automatically, and to count how many people are waiting for it.
Passkeys: the public key of each passkey, the name you give it, the type of authenticator, and when it was added and last used. The private key never leaves your device or password manager.
Signed-in devices: while you are signed in, we keep a session record with your IP address, browser user agent and the time of your last activity. It powers the list of signed-in devices on Account › Security, where you can sign out other devices.
Security log: a record of important account events, with the IP address they came from. Examples are password changes, email address changes (with the old and new address), passkeys added or removed, devices signed out, API tokens created, tools disconnected, changes to sites, boards and reports, and plan changes.
Sites and tools: your sites’ names, the domains allowed to send reports, your settings and the destinations you choose. For each tool you connect, we hold its access tokens (encrypted), your account ID with that tool and basic details of the connection.
API tokens: each token’s name, permissions and when it was last used. We store only a hash of the token itself, so we can’t show it to you again.
Billing: your Stripe customer and subscription IDs, your plan, its status and when the current period ends. Stripe collects your card details, billing address and, if you give them, your VAT number and business name. We send Stripe your name, email address and account ID. Your invoices are fetched from Stripe to show on the Billing page.
Emails: we always send emails about your account’s security, such as email verification, password resets, and alerts when your password or email address changes or a passkey is added. New report, billing and failed delivery emails can be turned off on the Notification preferences page, or with the unsubscribe button your email app shows for them.
Contact form: your name, email address, subject and message. We receive them by email.

6. Visitors to our website

Like every website, our server receives your IP address and browser details with each request. We use them to deliver pages, keep the service secure and limit abuse, for example by limiting how often a sign-in can be tried from one address.

Where you first came from

When you arrive on our website without being signed in, we note the first touch of your visit:

the address of the first page you open, without its query string
any campaign tags in that address: utm_source, utm_medium, utm_campaign, utm_term and utm_content
if another website sent you, that website’s name and page path, without its query string

We keep this in your session on our server. It isn’t a separate cookie, it isn’t sent to Google, and it doesn’t depend on whether you accept analytics cookies. If you don’t sign up, it is thrown away when your session expires, after 120 minutes without activity. If you sign up, we save it on your account. We use it, with your sign-up answers, to count sign-ups, active accounts and paying accounts by type of customer and by where they came from, so we know which of our marketing works.

Google Analytics

We use Google Analytics only if you accept analytics cookies. Until you do, its script isn’t loaded at all and the events below aren’t sent. If you accept, it records which pages you view, your browser and device type and your approximate location. It also records these steps:

creating an account, and whether with an email address or Google
adding a site
connecting a tool, and which one
starting checkout, with the plan, billing cycle and price
buying a plan, with the plan, billing cycle, amount paid and a reference for the Stripe checkout (never your card or billing details)
your account’s first report reaching one of your tools

Google provides this to us as our processor. We have set Google Analytics to keep event data for 2 months and user data for 14 months. After that, only totals that don’t identify anyone are kept.

Our Cookie Policy lists every cookie and how to change your choice.

7. Why we use personal data

Data protection law requires a lawful basis for each use of personal data. Ours are:

Contract: to run your account, sign you in, store and deliver your reports, bill you and send emails about the service.
Legitimate interests: to keep the service secure, prevent spam and abuse, find and fix faults, answer enquiries and improve the service. We also use your sign-up answers, where you first came from and your first delivered report to learn which marketing brings customers who go on to use the service. We balance these interests against your rights.
Legal obligation: to keep tax and accounting records and to respond to lawful requests.
Consent: for analytics cookies, and for emailing you when Elite is ready if you asked us to. You can withdraw either at any time: use Cookie settings for analytics, or contact us to come off the Elite list.

For bug reports, the website owner is the controller, so the lawful basis is theirs.

We use these companies to run the service:

Stripe handles payments and subscriptions and works out VAT.
Google provides sign-in with Google, if you use it, and Google Analytics, if you accept it. Google Workspace also hosts our email inbox, including messages sent through our contact form.
Postmark sends our emails.
20i hosts our website, database and file storage in a data centre in the UK.
Hetzner provides the server for our screenshot service, which we run ourselves, in a data centre in Nuremberg, Germany.
Cloudflare sits in front of our website and our screenshot service. It passes traffic on to them and helps protect them from attacks, so everything sent to them goes through it, including visitors’ IP addresses, reports and the page copies used for screenshots.

Reports also go to the tools that website owners connect, as described above. Those tools work for the website owner, not for us.

We may share data if the law requires it, or with a buyer if our business is sold, in which case we will tell you. We don’t sell personal data, and we don’t use it for advertising.

9. Data outside the UK

Our website, database and files are hosted in the UK. Some of the companies above process data elsewhere:

Hetzner runs our screenshot service’s server in Germany. UK law treats the European Economic Area as giving adequate protection, so no extra safeguards are needed.
Stripe, Google, Cloudflare and Postmark process data in the United States and other countries. For transfers to the United States, we rely on the UK Extension to the EU–US Data Privacy Framework (the “UK–US data bridge”) where the company is certified to it: Google, Cloudflare, Stripe and ActiveCampaign, which owns Postmark. Otherwise, and if the data bridge stops applying, we rely on the contractual safeguards in each company’s data processing terms, such as the standard contractual clauses with the ICO’s international data transfer addendum.

The tools that website owners connect may store reports in other countries. The owner chooses them.

10. How long we keep data

Account details: until you delete your account. This includes your sign-up answers, where you first came from, the date of your first delivered report and when you asked to hear about Elite.
First touch and Elite requests from visitors who don’t sign up or sign in: thrown away when the session expires, after 120 minutes without activity.
Reports: until the website owner deletes them. A deleted report is kept for 30 days in case it was deleted by mistake, then deleted for good with its screenshot and attachments.
Screenshots and attachments: deleted automatically one year after the report was sent. The rest of the report stays until it is deleted.
Connected tools: when you disconnect a tool, we delete its access tokens straight away.
Sessions: a session ends after 120 minutes without activity, or when you sign out. Old session records are cleared out regularly.
Security log: 90 days.
Billing: our billing record is deleted with your account. Stripe keeps payment and invoice records for as long as tax and accounting law requires.
Contact messages: they reach our inbox on Google Workspace by email, and we don’t store them in our app. Postmark, which delivers them, keeps a copy for 45 days. We keep them for up to two years after we last hear from you, then delete them.
Backups and server logs: our host backs up the website and database every day and keeps each backup for 30 days, so data you delete can stay in a backup for up to 30 days before it’s gone for good. Our server logs are deleted after 14 days.

When you delete your account

Deleting your account from Account › Your data deletes your account, sites, boards, reports, connected tools, API tokens and passkeys straight away. Their screenshots and attachments are deleted at the same time. Reports already sent to other tools stay there. Stripe keeps its billing records, as above. Security log entries stay until their 90 days are up.

11. Security

Our website and API use HTTPS.
We store passwords and API tokens only as hashes. Access tokens for connected tools are encrypted in our database.
Changing your email address, password or passkeys, signing out other devices and deleting your account all need a recent sign-in.
A new email address only takes effect once you confirm it from that address, and we email you about security changes to your account.

If you find a security problem, please tell us.

12. Your rights

Under UK data protection law, you have the right to:

get a copy of your personal data
have inaccurate data corrected
have your data deleted
restrict or object to how we use it
receive your data in a format you can take elsewhere
withdraw consent, such as for analytics cookies, at any time

How to use them

Download your data: Account › Your data gives you a file with your account details (including how you signed up, your sign-up answers, where you first came from, when your first report was delivered and when you asked to hear about Elite), sites and boards, reports (their titles, descriptions and status), connected tools and passkeys. It never includes tokens or keys. For a fuller copy, contact us.
Correct your details: change your name and email address on Account › Profile. To change your sign-up answers, contact us.
Delete your account: use Account › Your data.
Emails: choose which emails you get on the Notification preferences page.
Analytics: use Cookie settings at the bottom of our public pages.
Anything else: contact us. We reply within one month.

If you sent a report through the widget on someone else’s website, please contact that website’s owner first. See our two roles.

You can also complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113. We would appreciate the chance to put things right first.

13. Children

Accounts are only for people aged 18 or over. Website owners are responsible for reports sent from their own websites.

14. Changes to this policy

We update this policy when what we collect or how we use it changes. The date at the top shows when it last changed. If a change is significant, we will email account holders before it takes effect.

15. Contact us

Questions about your data? Use our contact form or email [email protected].

Agile Pixel Limited, 3 Whiteley Croft Rise, Otley, LS21 3NR, United Kingdom.