Draft — pending legal review. This English version is a translation; until the review is complete, the Portuguese version (Política de privacidade) prevails.

Privacy Policy

Version of

This policy explains, in plain language, how Sentinela handles personal data under the EU General Data Protection Regulation (GDPR, Regulation 2016/679), the UK GDPR, where applicable, and the Brazilian General Data Protection Law (Law 13,709/2018, the LGPD). Sentinela is operated by [COMPANY LEGAL NAME], CNPJ [CNPJ], headquartered at [ADDRESS], Brazil ("Sentinela", "we", "us").

Summary

  • Sentinela is a bug reporting tool: a widget our customers install on their websites and a dashboard at sentinela.click.
  • Reports sent through the widget belong to the customer who installed it. In that case we process the data on the customer’s behalf, following their instructions (we are a processor).
  • Data about your dashboard account, payments and visits to our website is processed by us for our own purposes (we are a controller).
  • Marketing cookies and ad pixels only run if you accept them. You can change your mind at any time.
  • We do not sell personal data.

1. Who decides about your data

Data protection law distinguishes two roles: the controller, who decides why and how data is used, and the processor, who handles data on the controller’s behalf.

When we are a processor

When someone sends a bug report through the widget installed on a customer’s site, the customer is the controller and Sentinela is the processor. The customer decides to install the widget, what to capture and how long to keep it, and must inform the users of their site about this processing. If you sent a report through a third-party site and want to exercise your rights, contact that site first; if you contact us, we will forward your request to them. Our processing on behalf of customers is governed by our Terms of Service and data processing terms (GDPR art. 28). [ATTACH OR LINK THE DATA PROCESSING AGREEMENT (DPA).]

When we are a controller

We are the controller of data about people who create an account and use the dashboard, billing data, the emails we send, data about visits to sentinela.click and data used to measure our ads.

2. What data we process

2.1 Reports sent through the widget (we are a processor)

  • Report content: title, description and, if the person chooses to provide it, the reporter’s email.
  • Image and video: a capture of the visible part of the page, with the annotations made; a short screen video (up to 15 seconds) when the plan allows; on phones and tablets, a page recording (replay) of up to 15 seconds in which typed fields are masked. Anything on screen at that moment may appear in these images.
  • Technical diagnostics: browser console messages, JavaScript errors and network requests (URL, method, status, duration and, on plans that enable it, the request content). Before anything leaves the browser, the widget replaces with ***REDACTED*** values whose names typically indicate sensitive data (password, token, API key, cookie, session, card, CVV, verification code and similar) and truncates long text.
  • Environment: browser and operating system (user agent), screen and window size, language, time zone, page and title, referring site (with tokens removed), light/dark theme, connection and loading metrics.
  • Signed-in user identification (only if the customer enables it): identifier, email and name of the user on the customer’s site, taken from the site’s session, from WordPress or provided by the site itself.
  • Visit counting: to apply the plan’s usage limit, we count visits per site using a cryptographic summary (hash) of the IP address, deleted within 1 day. The widget also stores technical markers in the browser (sessionStorage/localStorage) so the same visit isn’t counted twice.

2.2 Account and dashboard use (we are a controller)

  • Name, email and password (stored only as a hash by the authentication provider).
  • Language, country and time zone of the account (the country determines the billing currency).
  • Projects, invited members, configured integrations, tickets, comments and ratings of the AI analysis.
  • Technical access and security logs (date, time, IP and browser).

2.3 Payment

Plan, subscription history, invoices, coupons used and billing data (name, email, tax ID and address, when required). Card data is collected and stored by Stripe; we only receive information such as the card brand and last digits.

2.4 Website visits and ads

  • Visit source: campaign parameters (utm_*), ad click identifiers (gclid, gbraid, wbraid, fbclid, li_fat_id and similar), referring site and landing page.
  • At sign-up, we link that source to your account, together with the IP and browser used to sign up.
  • Your cookie choices: what was accepted, when, notice version, IP prefix and browser (to prove consent).
  • Events in your customer journey: sign-up, first report received, trial start, subscription, renewal and plan change (with amount).

3. Why we use it and on what legal basis

For each purpose, we list the legal basis under GDPR art. 6(1) and the corresponding basis under LGPD art. 7.

PurposeDataLegal basis
Receive, store and show reports to the customer; send them to the integrations the customer configuredWidget reports (2.1)Processing on behalf of the customer, who is the controller and determines the legal basis towards their users
Analyze reports with AI (summary, type, category)Widget reports (2.1)Processing on behalf of the customer (a feature of the service)
Create and maintain your account, provide dashboard access and supportAccount (2.2)Performance of a contract (GDPR art. 6(1)(b); LGPD art. 7, V)
Bill you, issue invoices and meet tax obligationsPayment (2.3)Performance of a contract (art. 6(1)(b)) and legal obligation (art. 6(1)(c); LGPD art. 7, II)
Send service emails (invitations, ticket notifications, billing, limits)Email and account dataPerformance of a contract (art. 6(1)(b))
Security, fraud prevention and prevention of plan-limit abuseAccess logs, IP hash, usageLegitimate interests (art. 6(1)(f); LGPD art. 7, IX) and log retention required by Brazilian law (Marco Civil da Internet)
Learn which campaigns bring us sign-ups and customers (first-party measurement, not shared)Visit and sign-up source (2.4)Legitimate interests (art. 6(1)(f)); where the ePrivacy rules of your country require consent for the related cookies, consent
Marketing cookies and pixels in the browser (Meta, Google, LinkedIn)Marketing cookiesConsent (art. 6(1)(a); LGPD art. 7, I)
Tell ad platforms about sign-ups, activations and trial startsHashed email, click identifiers, sign-up IP and browserConsent (art. 6(1)(a))
Tell ad platforms about paid subscriptions and renewals, to measure ad returnHashed email, click identifiers, sign-up IP and browser, amountConsent or, in its absence, legitimate interests (art. 6(1)(f)), with the right to object — see section 4. [LEGAL REVIEW: confirm whether consent is required for EU/UK visitors.]
Establish, exercise or defend legal claimsData needed for the caseLegitimate interests (art. 6(1)(f); LGPD art. 7, VI)

Where we rely on legitimate interests, we have balanced our interests against your rights; you can ask the DPO for details. Providing account and payment data is necessary to use the paid service; without it we cannot provide the service. We do not make decisions that produce legal or similarly significant effects based solely on automated processing (GDPR art. 22). The AI analysis of tickets only produces suggestions that the customer can review and change.

4. Ad measurement

We advertise Sentinela on Meta (Facebook and Instagram), Google and LinkedIn. To find out whether these ads bring customers, we do the following:

  • With your marketing consent (in the cookie notice), these platforms’ pixels run on our site and, from our server, we tell them when you sign up, start using the product or start the free trial.
  • For paid subscriptions (purchase, renewal and plan change), we may report the conversion to the platforms based on our legitimate interest in measuring the return on our ad spend, even without marketing consent. We carried out a legitimate interest assessment, available on request from the DPO.
  • We send the minimum: your email turned into a hash (SHA-256, a code that does not reveal the email), the ad click identifier, the sign-up IP and browser, the event type, the amount and the date. We never send the content of your projects or tickets.
  • Each platform uses this data to attribute the conversion to the ad and for the purposes described in its own policies, and may match it with your account on that platform, if you have one. For these purposes the platforms may act as independent controllers or as joint controllers with us (GDPR art. 26). [LEGAL REVIEW: confirm the arrangement with each platform.]
  • You can object: use the "Don’t use my data to measure ads" option in the dashboard, under account menu → Privacy (sentinela.click/conta/privacidade), or ask by email at [DPO EMAIL]. From then on we stop sending your conversions, with or without consent.

5. Who we share data with (sub-processors)

We use service providers (processors and sub-processors) that process data on our behalf and under our instructions, bound by data processing terms:

ProviderPurposeLocation
SupabaseDatabase, authentication, file storage (screenshots, videos, recordings) and server functions.[SUPABASE PROJECT REGION]
Cloudflare (R2 and CDN)Delivery of the widget script and of each project’s public configuration; bot protection (Turnstile) on sign-up and sign-in.Global network
[COOLIFY SERVER PROVIDER]Server that runs the dashboard (sentinela.click), on our own infrastructure managed with Coolify.[SERVER COUNTRY]
StripePayments, subscriptions, invoices and billing data. We never receive your full card number.USA and others
ResendTransactional emails (invitations, ticket notifications, billing, usage limits).USA
Anthropic (Claude)Automatic AI analysis of tickets: summary, type, category and suggestions.USA
Google (Tag Manager and Google Ads)Site tag management and ad measurement, as described in the ads section below.USA and others
Meta (Pixel and Conversions API)Ad measurement on Facebook and Instagram, as described in the ads section below.USA and others
LinkedIn (Insight Tag and Conversions API)Ad measurement on LinkedIn, as described in the ads section below.USA and others
GitHub and TrelloOnly when the customer connects the integration: ticket content is sent as an issue or card in their account.USA
Slack, Microsoft Teams and DiscordOnly when the customer adds a channel webhook: we send notifications with the title, project, priority, AI summary and ticket link, and the page address without query parameters. We never send the reporter’s name or email.USA
WhatsApp (official Meta API)Only when the customer connects their own Meta account: we send template notifications to the team phone numbers they registered and receive the button replies (mark as in progress or done). Messages are sent from the customer’s number. With the “My Evolution API” option (unofficial), messages go through the customer’s own Evolution server; the customer is the controller and is responsible for that provider.USA
Customer webhooksOnly when the customer registers a URL: ticket content is sent to the system they chose.Defined by the customer

When Meta, Google and LinkedIn receive ad measurement data, they also process it for their own purposes, under their own terms. We may also share data with authorities when required by law, and with a successor in the event of a merger or sale of the business, with the safeguards of this policy maintained. We will update this list before adding or replacing a sub-processor that handles customer report data. [LEGAL REVIEW: define the notice period and objection procedure for customers.]

For the Slack, Teams, Discord and WhatsApp integrations, the customer chooses and configures the destination. On WhatsApp, we process the phone numbers of team members registered by the customer only to send notifications and receive replies; the customer confirms that these people have agreed to receive the messages.

If the customer connects an AI tool to Sentinela via MCP, ticket data is sent to that tool at the customer’s request and under their responsibility; the customer chose it and is the controller of that data.

6. International transfers

Sentinela is operated from Brazil, and several of the providers above are located in, or process data in, the United States and other countries. When personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to countries without an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses (and the UK International Data Transfer Addendum, where applicable), on the EU–U.S. Data Privacy Framework for certified providers, or on other mechanisms under GDPR chapter V, together with supplementary measures where needed. Transfers out of Brazil follow LGPD art. 33 and ANPD Resolution CD/ANPD No. 19/2024. You can request a copy of the relevant safeguards from the DPO. [CONFIRM THE MECHANISM PROVIDER BY PROVIDER.]

7. How long we keep data

DataRetention
Widget reports (tickets and attachments)For the period of the customer’s plan (currently Starter 90 days, Pro 1 year, Business 5 years) or until the customer deletes them; deleted within [PERIOD] after the contract ends
IP hash for visit countingUp to 1 day
Account dataWhile the account exists; then within [PERIOD], except what the law requires us to keep
Dashboard access logs6 months (Brazilian Marco Civil da Internet, art. 15)
Invoices and tax data5 years, or the period required by tax law
Sign-up source and conversion eventsWhile the account exists
Cookie consent recordsFor as long as needed to prove consent [PERIOD]
CookiesAs listed in section 9

8. Your rights

Under the GDPR (arts. 15–22) and the LGPD (art. 18), you can ask at any time for:

  • confirmation that we process your data, and access to it;
  • correction of incomplete, inaccurate or outdated data;
  • erasure of your data, or restriction of its processing, where the law allows;
  • portability of the data you provided, in a structured, machine-readable format;
  • objection to processing based on legitimate interests (such as ad measurement) — and, at any time, to direct marketing;
  • withdrawal of consent, without affecting processing carried out before the withdrawal;
  • information about who we share your data with, and about the possibility of not consenting and its consequences;
  • not being subject to decisions based solely on automated processing, and review of such decisions.

To exercise your rights, email [DPO EMAIL] from the address linked to your account. We may ask you to confirm your identity. We reply within one month (GDPR) and, for requests under the LGPD, within 15 days. If the request concerns a report sent through one of our customers’ sites, we will forward it to the customer, who is the controller.

You also have the right to lodge a complaint with a supervisory authority — in particular in the EU/EEA country where you live or work or where the alleged infringement took place, with the UK Information Commissioner’s Office (ico.org.uk), or with Brazil’s National Data Protection Authority (ANPD, gov.br/anpd).

9. Cookies

Cookies are small files a website stores in your browser. Strictly necessary cookies make the site work and cannot be turned off. First-party measurement cookies stay with us and tell us where our sign-ups come from. Marketing cookies are only enabled if you accept them.

CookiePurposeCategoryDurationSet by
sb-*-auth-tokenKeeps you signed in to the dashboard (Supabase Auth session).Strictly necessaryUntil you sign out or the session expires (max. 400 days)Sentinela (first party)
snt_consentStores your cookie choices so we don’t ask again.Strictly necessary6 monthsSentinela (first party)
NEXT_LOCALERemembers the language you chose for the site (Portuguese or English).Strictly necessary1 yearSentinela (first party)
sentinela_cupomKeeps the campaign coupon received through a link until you subscribe.Strictly necessary7 daysSentinela (first party)
sentinela_trello_connectSecurely completes the Trello connection when you start it.Strictly necessary30 minutesSentinela (first party)
snt_vidRandom browser identifier, to know which visit a sign-up came from.First-party measurement1 yearSentinela (first party)
snt_touchSource of the first and last visit (utm_* parameters, ad click identifier, referring site and landing page).First-party measurement90 daysSentinela (first party)
_fbcMeta ad click identifier (fbclid), used to measure ad results.Marketing90 daysMeta (read by Sentinela)
_fbpBrowser identifier used by the Meta Pixel to measure ads.Marketing90 daysMeta
_gcl_au, _gcl_awGoogle Ads conversion measurement.Marketing90 daysGoogle
li_fat_id, li_sugr, bcookie, lidc, UserMatchHistory, AnalyticsSyncHistoryLinkedIn ad and conversion measurement (Insight Tag).MarketingFrom 1 day to 1 year, depending on the cookieLinkedIn

The widget installed on customers’ sites does not use its own cookies; it stores technical markers in the browser storage (sessionStorage/localStorage) to count visits and remember notices already shown.

10. Security

  • Connections are always encrypted (HTTPS), with per-account access control and isolation between customers in the database.
  • Sensitive data is masked in the browser itself, before the report is sent.
  • Integration keys and secrets are stored encrypted and outside the code.
  • Internal access is restricted to those who need it, for support and operations.

No system is completely immune to incidents. If a personal data breach occurs that is likely to result in a risk to your rights, we will notify the competent authorities (within 72 hours where the GDPR requires) and, where required, the people affected. When we act as a processor, we will notify the customer without undue delay.

11. Children

The Sentinela dashboard is a professional service for people aged 18 or over and is not directed at children. On customers’ sites, it is up to the customer to assess whether the widget is suitable for their audience.

12. Changes to this policy

We may update this policy. The version date is at the top of the page. We will announce relevant changes by email or in the dashboard before they take effect.

13. Contact, data protection officer and representatives

Data protection officer: [DATA PROTECTION OFFICER NAME]
Email: [DPO EMAIL]
[COMPANY LEGAL NAME] — CNPJ [CNPJ] — [ADDRESS]
EU representative: [EU REPRESENTATIVE (GDPR ART. 27), IF REQUIRED]
UK representative: [UK REPRESENTATIVE (UK GDPR ART. 27), IF REQUIRED]