Legal
Data processing agreement
This agreement covers the personal data ContextCapture.ai processes for its customers. It lists every subprocessor, the masking applied before upload, and the 90-day retention of captures.
Last updated:
Parties and roles
The customer is the workspace owner who installs the widget and is the controller of the personal data in reports. R. Dune Capital B.V., a private limited company (besloten vennootschap) registered in the Netherlands, registered with the Dutch Chamber of Commerce under number 95549765, at Driestedenweg 85, 1662 BH De Weere, the Netherlands, is the processor. This agreement applies from the day the customer creates a workspace and forms part of the terms of service.
What we process and why
- Subject matter: running the bug report widget, the report inbox and the delivery of reports to the destinations the customer connects.
- People concerned: the customer’s workspace members and the signed-in reporters who send reports from the customer’s website.
- Data: the reporter’s email address, the note they type, screenshots, the page address, browser and device details, console output, the selected element and, when the reporter records a flow, its steps and network request summaries.
- Duration: until the retention period below ends or the customer ends the subscription and asks for deletion.
Our commitments
- We process the data only to provide the service and on the customer’s documented instructions, which are the use of the service and requests sent to the support address below.
- Everyone with access to the data on our side is bound to confidentiality.
- We protect the data as described on the security page, including private storage of screenshots and recordings and checks of workspace access on every download.
- We tell the customer without undue delay after we become aware of a personal data breach that affects the customer’s data.
- We help the customer answer requests from the people concerned for access, correction and deletion.
- We give the customer the information needed to show that we meet this agreement, on reasonable request.
Masking before upload
The widget applies these defaults in the browser before anything is uploaded:
- In recorded steps, typed values in password and telephone fields, in fields the page marks as card or password autofill, and in fields whose name contains password, secret, token, ssn or pin are replaced by at most eight bullets, so the length is not leaked. The telephone and name rules apply to recorded steps only.
- Email-shaped values keep their first character and their domain (a****@example.com).
- Runs of 13 or more digits, spaces or dashes keep only the last four characters.
- Other typed text is cut to 80 characters.
- In the screenshot, password fields, fields the page marks with a card, one-time-code or password autofill value, and their placeholders are replaced or removed (eight bullets are shown), as are regions marked with the data-cc-mask attribute.
- Anything inside an element marked with the data-cc-mask attribute is blanked in the screenshot: text becomes bullets, images are hidden and the block is one flat colour.
- Ordinary inputs such as email, search and free text are not masked in the screenshot. Mark a region with data-cc-mask to hide it.
- On our servers, tokens, keys, credentials in web addresses and long random strings are removed from report text and recording metadata before delivery.
Retention and deletion
A capture (a report, its screenshot and its recording) is kept for 90 days and then deleted from the database and from file storage. The customer can ask for earlier deletion of the whole workspace by writing to [email protected]. When the agreement ends we delete the customer’s data, except what the law requires us to keep.
Subprocessors
The customer authorises us to use the subprocessors below. If we add or replace one, we update this list and the date at the top of this page before the new subprocessor receives customer data. The customer can object by writing to [email protected].
| Subprocessor | Purpose | Data processed |
|---|---|---|
| Supabase | Database, sign-in and file storage | Accounts, workspace membership, reports, screenshots and recordings |
| Fly.io | Application hosting (primary region Ashburn, Virginia, United States) | All traffic to the app and the report API, in transit and in memory |
| Cloudflare | Delivery of the widget script to your site | Request metadata such as IP address and user agent when a page loads the widget |
| Stripe | Subscription payments and invoices | Billing email, card details (held by Stripe, never by us) and subscription status |
| Mailgun | Transactional email: sign-in, invitations and report notifications | Recipient email address and the content of the notification |
| Anthropic | The optional AI report coach, which suggests improvements to a report before it is sent | The text the reporter has typed, the page address, the selected element and the reporter’s answers to clarifying questions, after secrets are removed |
| Plausible | Cookie-free analytics on the public marketing pages | Page address, referrer and coarse device data; private pages and report content are never sent |
Some subprocessors operate from the United States. Where personal data leaves the European Economic Area, we rely on the transfer safeguards each subprocessor publishes, such as standard contractual clauses.
Questions and related pages
Write to [email protected] with any question about these pages.