Legal
Privacy policy
Last updated November 4, 2026
Who is responsible
The controller of the personal data described here is Dyego Maas Tecnologia e Inovação Ltda., CNPJ 60.611.422/0001-25, Rua Frei José, 478, torre 1, apto. 801, Salto, Blumenau, SC, 89031-040, Brazil.
As a small processing agent, we are exempt from appointing a person in charge (ANPD Resolution 2/2022, art. 11). Our channel for data subjects and the ANPD is spec-ultra@dyegomaas.com.br.
What this policy covers
This policy covers visitors of specultra.dev; buyers; administrators of Business licences; licensees, including those of licences granted without payment; and people named on a licence who have not signed in yet. It describes what we process about each group, where it comes from, why, on what legal basis, with whom it is shared and for how long it is kept.
Your choice about analytics
The site measures its own use with PostHog and Google Analytics, and measures through Google Analytics which ads lead to a purchase. On your first visit a banner offers Accept and Reject with equal prominence, and your answer decides what is captured:
- Before you answer: neither PostHog nor Google Analytics is loaded, nothing is sent to analytics and nothing is written in your browser for analytics.
- After Accept: PostHog stores in your browser, in a cookie and in local and session storage (
ph_…), a pseudonymous identifier that links your visits to each other. It does not carry your name, and it becomes linked to your purchase if you buy. PostHog captures:- page views and the events listed below;
- a recording of the session, with every form field masked, without the browser console log;
- heatmaps of clicks, mouse movement and scrolling;
- page performance metrics (web vitals);
- clicks that have no effect on the page ("dead clicks").
Paddle's checkout, which opens over the site's page in a frame hosted by Paddle, is never recorded.
The sign-in, account, licence administration and purchase confirmation pages are recorded with all their text hidden, and the clicks captured there carry neither the text of the elements nor what you copy, so the e-mails, serials and other people's data they show do not reach PostHog.
Google Analytics is loaded and stores its own cookies in your browser (
_ga,_ga_…and_gcl_…), with a pseudonymous identifier that links your visits to each other. It receives:- page views, with the page address, the referrer address and the page title;
- the purchase completed in Paddle's checkout, with its value before tax and its currency, without the transaction identifier;
- interactions it measures on its own, such as scrolling and clicks on links that leave the site.
On the sign-in, account, licence administration and purchase confirmation pages, the address that reaches Google loses the licence identifier and the transaction identifier, and the page title is replaced by the address without identifiers. Google does not use this data to personalise ads, and Google signals, which would match your visits to your Google account, stay off.
- After Reject: neither PostHog nor Google Analytics is loaded, nothing is sent to analytics and nothing is written in your browser for analytics; we keep only your choice (
su_consent_2, in local storage). If they were already loaded, new capture stops, and the site deletes the cookies they had written.
You can change your answer at any time: the "Privacy choices" control in the footer of every page reopens the banner.
The events the site records are:
| Event | When | What it carries |
|---|---|---|
consent_changed | you answer or change your answer | the answer |
rival_selected | you pick a tool in the comparison section | the tool picked |
checkout_started | you press a purchase button | licence type, number of seats, currency, language |
checkout_returned | you return from the payment page | only the language and currency |
Every event also carries the page language and currency. The events we define include no name, no e-mail and no Paddle transaction identifier, and the page addresses that reach PostHog lose the licence identifier and the transaction identifier. PostHog also receives with each event technical data such as browser, system, language, time zone, screen size, page and referrer address, and campaign parameters.
If you accepted analytics and start a purchase, the site attaches your analytics identifier to the Paddle transaction, in its custom_data. This links your visits to the purchase you made, so we can learn which pages lead to a sale. If you rejected analytics, no identifier is attached.
Analytics data is sent through a path on the site's own domain (/ingest) and forwarded to PostHog Cloud in the United States. After Accept, PostHog may derive an approximate location (country and city) from the IP address of each request and discards the address without storing it; after Reject, it receives nothing more from the site.
Google Analytics data goes straight from your browser to Google, in the United States and other countries where Google keeps facilities. Google uses the IP address of each request to derive an approximate location and does not store it. Google processes this data as our processor; when we use it to measure in Google Ads which ads lead to a purchase, Google also processes that conversion data as a controller, under its data protection terms (https://business.safety.google/privacy/).
Session recordings and heatmaps happen only after Accept, and only in PostHog.
Cookies and browser storage
| Name | What it is for | Kept for | When |
|---|---|---|---|
NEXT_LOCALE | the language you chose, when it differs from your browser's | until you close the browser (session cookie) | only when you switch language, strictly necessary |
su_cur | the currency shown (brl, eur or usd), recalculated from the connection's country on every page; it stores neither the country nor the IP | 1 year from the last write | from your first visit, strictly necessary |
su_consent_2 (local storage) | your answer to the banner: 1 accepted, 0 rejected | until you clear the site's data in your browser | once you answer, strictly necessary |
PostHog cookie and local and session storage keys (ph_…) | the analytics identifier and the state of the analytics session | cookie: 1 year; local storage: until removed by the site or the browser; session storage: until you close the tab | only after Accept |
Google Analytics (_ga and _ga_…) and Google Ads (_gcl_…) cookies | the analytics identifier, the session state and the link between a purchase and the ad that brought it | _ga and _ga_…: 2 years; _gcl_…: 90 days | only after Accept |
Sign-in cookies: Clerk's __session and __client_uat, and Cloudflare's _cfuvid, which Clerk uses | keep you signed in and protect sign-in | while the sign-in session lasts, up to 7 days | only on the sign-in, account and licence administration pages, strictly necessary |
__Host-su_account | remember across the site's pages that you are signed in: it holds only your first name, your initials and whether you hold a licence, administer one or neither; no e-mail, identifier or token | 30 days from the last account page you opened; removed when you sign out | after you sign in, strictly necessary |
On every page, the site's server looks up the country associated with your IP address, through Netlify's geolocation, to choose the currency shown; when it opens the checkout, it looks the country up again. The site does not keep the country: it keeps only the resulting currency, in the su_cur cookie.
On sign-in, Clerk's bot protection and Cloudflare's challenge (Turnstile) may read technical signals from your browser and connection, only to protect sign-in. Paddle's checkout may set its own cookies inside its frame; see Paddle's privacy policy. Rejecting analytics does not switch off this necessary storage.
What we process, why and on what basis
| Data | Why | Legal basis |
|---|---|---|
| IP address and browser data in each request | to serve the site, protect it from abuse and pick the currency of your country | our legitimate interest in running a secure site (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Analytics after Accept | to understand how the site is used, which pages lead to a purchase and which ads brought it | your consent (LGPD art. 7, I; GDPR art. 6(1)(a)); you can withdraw it from the footer |
| Purchase data: at Paddle, name, e-mail, country, amount, currency and receipt, which we consult in its dashboard; in the site's database, only the buyer's e-mail, the transaction identifier, the modality and the number of seats. The confirmation page reads the total and currency from Paddle to show them and does not keep them. | to create and deliver the licence, handle refunds and answer you | performance of the contract (LGPD art. 7, V; GDPR art. 6(1)(b)); for a buyer acting for a company, our legitimate interest in performing the contract with it (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Licensee: e-mail, serial, Clerk account identifier and the dates of assignment and of each certificate. It comes from checkout (Individual), from the administrator who names them (Business) or from us (Concession). | to invite, issue and renew certificates, manage seats and resolve a serial found in an artifact | performance of the contract where the licensee is party to it (LGPD art. 7, V; GDPR art. 6(1)(b)); where an organization names them, and when resolving serials, our and the organization's legitimate interest in delivering and protecting the licence (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Administrator: e-mail and Clerk account identifier | to administer the seats and identify the licence to its licensees | performance of the contract with the buying organization and our legitimate interest (LGPD art. 7, V and IX; GDPR art. 6(1)(b) and (f)) |
| Sign-in data held by Clerk: e-mail, sign-in method (e-mail code, Google or GitHub) and account identifier | to know who signs in and tie a licensee or an administrator to their seats | performance of the contract (LGPD art. 7, V; GDPR art. 6(1)(b)) |
| Renewal access record: full IP address, date and time, and serial of each renewal request | to keep the application access records the law requires | legal obligation (LGPD art. 7, II; Marco Civil da Internet, Law 12.965/2014, art. 15); for data subjects protected by the GDPR, our legitimate interest in meeting that duty of Brazilian law, to which we are subject, and in protecting the licence (GDPR art. 6(1)(f)), with a right to object |
| Renewal prefix record: the /24 (IPv4) or /48 (IPv6) prefix of the address, the date and the serial | to tell whether one certificate is being renewed from several networks | our legitimate interest in protecting the licence (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| E-mail and plan of interest sent through the launch notice form | to send you one launch notice | your consent (LGPD art. 7, I; GDPR art. 6(1)(a)); you can withdraw it by writing to us |
| Messages you send us | to answer them | performance of the contract or legitimate interest, depending on the subject |
To obtain a certificate you need a named seat and an account that confirms that seat's e-mail; without this data we cannot issue the certificate. Analytics and the launch notice are optional.
The system automatically checks whether the licence and seat allow a certificate to be issued or renewed, and a confirmed refund may end the licence. Network prefixes help investigate possible sharing, and using several networks does not by itself trigger an automatic block. If a refusal looks wrong, write to spec-ultra@dyegomaas.com.br so we can review it. We do not sell this data or use it for advertising.
The launch notice form
While the licence is not on sale, the site offers a form to tell you when it is. The form asks for your e-mail and, optionally, your plan of interest (Individual, or Business with a number of seats). It is collected through Netlify Forms, with Netlify acting as our processor, and sent only to the site's own domain; no analytics event carries your e-mail. With each submission, Netlify also records the IP address, the browser's user agent and the page the form was sent from. We use this data only to send you one launch notice. We keep it until that notice is sent or you ask to be removed, whichever comes first; to be removed, write to spec-ultra@dyegomaas.com.br. The legal basis is your consent (LGPD art. 7, I; GDPR art. 6(1)(a)), which you can withdraw the same way.
Payment
Paddle.com is our reseller and the merchant of record for every purchase: it sells you the licence, charges the payment, collects and remits the tax, and issues the receipt and the invoice. You buy from the Paddle entity identified at checkout and on your receipt, under the Paddle terms that apply to your location. Payment happens in Paddle's checkout, an overlay hosted by Paddle that opens over the site's page. The site never receives or stores your card data. Paddle processes the data you give at checkout as an independent controller for payment, tax, invoicing and fraud prevention, and makes the purchase data listed above available to us; its privacy policy identifies the entities involved (https://www.paddle.com/legal/privacy).
The transaction the site creates in Paddle carries the currency and, in its custom_data, the licence type, the number of seats and the language and, if you accepted analytics, your analytics identifier. After payment, Paddle sends you back to the confirmation page on the site itself, which reads the transaction from Paddle by its identifier; the site keeps that transaction identifier. Paddle also notifies the site of each completed purchase and each refund, and the site reads the buyer's e-mail from Paddle to create the licence.
The licence certificate and the watermark
The certificate installed on a licensee's machine carries their e-mail and serial. The serial, without the e-mail, is written as a declared watermark in the artifacts the licensee generates. Anyone holding such an artifact sees only the serial; we link it to the licensee through our record, and anyone holding the certificate or other information can make that link too; we treat that link as personal data. That record lives in the site's own database, hosted by Neon, and is not published. For each licence it holds the modality, the number of seats, the origin (purchase, Concession or course), the status, the Paddle transaction reference when there was a purchase, the organization name for a Concession, and the dates of planned end, end of updates and ending; the administrator's e-mail, on a Business licence; for each seat, the e-mail and serial of whoever holds it and of whoever held it before, with the start and end date of each assignment; the Clerk account identifier of each administrator and licensee after their first sign-in; and each certificate issued, of which it keeps the type, the dates, the signing key identifier and a fingerprint (hash), never the certificate itself. It also keeps the identifier and type of each notice received from Paddle, so it is not processed twice.
A licensee obtains the certificate through the Spec Ultra installer, after signing in to the site with Clerk. The site offers no download of the certificate and sends none by e-mail.
We receive the buyer's e-mail from Paddle. On a Business licence, licensees' e-mails come from the administrator who names them; on a Concession, from us. Clerk gives us the account identifier and the e-mail verification. The administrator sees, on the Your account page, the e-mail and assignment date of each seat of the licence they administer, and does not see the renewal records. Someone holding seats in more than one licence sees, when obtaining the certificate, each organization's name or, until there is one, its administrator's e-mail. When a named person has no account yet, Clerk receives that person's e-mail and tries to send them an invitation on our behalf. Only we see the network prefixes of renewals. If you administer a licence, name only people who should receive access and tell them about this policy.
The plugin renews the certificate by sending it to the site; renewal goes to the site alone, never through Clerk. When the site verifies the certificate's signature and receives a valid IP address from the hosting service, it writes two records, including when it refuses renewal because the seat changed or the licence ended:
- An access record, with the full IP address, the date and time and the serial of each request. It exists to meet, for renewal, the duty in article 15 of the Marco Civil da Internet (Law 12.965/2014) to keep application access records. It is shown in no panel, is handed to third parties only under a court order, and is deleted by the daily routine after 183 days.
- A prefix record, with the /24 (IPv4) or /48 (IPv6) prefix of the address and the serial, once per UTC day, with no time or request count. It helps investigate whether one certificate is renewed from several networks; several networks alone do not prove copying, since VPNs, travel and mobile networks also change the address. It is the only renewal record our management panel shows, and it is deleted by the daily routine after 90 days.
Who processes data for us
| Provider | What it does | Where |
|---|---|---|
| Paddle.com | reseller and merchant of record: checkout, payment, tax, receipt, invoice and fraud prevention, as an independent controller; receives your name, e-mail, country and payment data | the Paddle entity identified at checkout and on your receipt |
| PostHog | analytics, as described above | United States |
| Google (Google Analytics and Google Ads) | analytics and ad measurement, as described above; processor in Google Analytics and controller of the conversion data in Google Ads | United States and other countries where Google keeps facilities |
| Netlify | hosting and delivery of the site; keeps access logs with your IP address and uses it to find your country, only to choose the currency shown and charged; receives and stores the submissions of the launch notice form | United States |
| Neon | the site's database: licences, seats, administrator e-mails, current and former licensee e-mails and serials, Clerk account identifiers, issued certificates (hash only), Paddle notices and the two renewal records | United States (AWS US East 2, Ohio) |
| Clerk | sign-in to the site: verifies who signs in, holds the e-mail and sign-in method of each account and sends the invitation to sign in to a licensee or administrator named on a licence; holds no licence data | United States (Google Cloud, with Cloudflare as a sub-processor) |
| Google (Google Workspace Gmail) | answering messages | United States and other countries where Google keeps facilities |
International transfers
We are in Brazil; Paddle sells through the entity identified at checkout and on your receipt, and the other providers process the data in the United States, Google also in other countries where it keeps facilities. Each transfer rests on:
| Provider | GDPR and UK GDPR | LGPD |
|---|---|---|
| Netlify | the EU-U.S. Data Privacy Framework (DPF) and its UK extension; should the DPF stop applying, the European Commission's standard contractual clauses and the UK IDTA | performance of the contract (art. 33, IX, with art. 7, V) |
| Neon (Databricks, Inc.), on AWS us-east-2 | the DPF, its UK extension and the Swiss DPF; as a fallback, the standard contractual clauses with the UK addendum | performance of the contract (art. 33, IX, with art. 7, V) |
| Clerk | the DPF, its UK extension and the Swiss DPF; where the DPF cannot be relied on, the standard contractual clauses with the UK addendum | performance of the contract (art. 33, IX, with art. 7, V) |
| PostHog | the standard contractual clauses (module 2) with the UK addendum; PostHog also takes part in the DPF | your specific consent to the transfer, given prominently (art. 33, VIII), when you Accept on the banner |
| Google (Google Analytics and Google Ads) | Google's data processing terms, with the DPF or the standard contractual clauses | your specific consent to the transfer, given prominently (art. 33, VIII), when you Accept on the banner |
| Google (Google Workspace Gmail) | Google's data processing addendum, with the DPF or the standard contractual clauses | performance of the contract (art. 33, IX, with art. 7, V), with the Brazilian standard contractual clauses Google's addendum provides |
| Paddle | the data you give at checkout goes straight to Paddle, as an independent controller; its privacy policy describes the safeguards for the transfers it makes | performance of the contract (art. 33, IX, with art. 7, V), for what the site sends Paddle when it creates the transaction |
You may request information about these safeguards and a copy of the applicable clauses at spec-ultra@dyegomaas.com.br.
How long we keep data
| Data | Kept for |
|---|---|
| PostHog events | up to 7 years from each event, the period of the PostHog plan |
| Google Analytics events | 2 months from each event, the period set on the property |
| Session recordings | 30 days |
| Request logs at Netlify | up to 7 days, depending on the plan |
| Payment, tax and invoicing data at Paddle | the period Paddle sets under its own privacy policy and legal duties, which can outlast our relationship |
| Record of a licence in the site's database: licence, seats, administrator, licensees, serials, originating purchase, status and issued certificates | while the licence is active |
| E-mail and Clerk account link of someone who left a seat or of an ended licence | deleted by the daily routine 6 months after leaving or ending; the serial and dates stay, unlinked from a person |
| Submissions of the launch notice form: e-mail and plan of interest | until the launch notice is sent or you ask to be removed, whichever comes first |
| Renewal access record: full IP address, date and time, and serial | deleted by the daily routine after 183 days |
| Renewal prefix record: /24 or /48 prefix, date and serial | deleted by the daily routine after 90 days |
| Sign-in account at Clerk | deleted by the same routine, 6 months after the person no longer holds a seat or administers an active licence |
| Messages | 5 years from the last message, the claim period of the Brazilian Consumer Protection Code (art. 27) |
We keep only what each purpose needs. When a period ends, the data is deleted or made anonymous, except where a law or an open dispute requires us to keep it.
Your rights
Under the LGPD and the GDPR you may ask us: to confirm whether we process your data and give you access to it, with the source of each item; to correct incomplete, inaccurate or outdated data; to anonymize, block or delete data that is unnecessary, excessive or unlawfully processed; for portability; to delete data processed on your consent, subject to lawful retention; to tell you with whom we share it and about the option of not consenting and its consequences; and to withdraw consent, which does not affect earlier processing. Under the GDPR you may also ask us to restrict processing.
Right to object. Where we rely on our legitimate interest, you may object at any time, on grounds relating to your situation; we stop unless we have compelling legitimate grounds or need the data for a legal claim. Under the LGPD, you may object to processing that breaches the law.
To exercise these rights, write to spec-ultra@dyegomaas.com.br, also through a representative. Requests are free, and we may ask you to confirm your identity. We answer confirmation and access at once in simplified form, or with a full statement within 15 days, as the LGPD sets (art. 19). Other requests we answer within one month, the GDPR period, which we extend only where it allows, telling you within that month. To correct the e-mail on a licence, write to us: changing your sign-in e-mail does not change the certificate.
You may also complain to a data protection authority: in Brazil, the Autoridade Nacional de Proteção de Dados (ANPD); in the European Economic Area, the authority of the country where you live or work; in the United Kingdom, the Information Commissioner's Office.
Some data cannot be deleted while a law requires us to keep it, such as tax records of a purchase. In that case we keep only what the law requires and tell you so.
Security
The site runs over HTTPS and holds no card data. The personal data it keeps are the launch notice form submissions, held by Netlify Forms, and the analytics data described above, plus, in its own database at Neon, the record of licences and the two renewal records. Certificates are signed on the site's server with a private key kept as a secret of the hosting environment; no table and no log holds that key or a certificate. Access to data is limited to the people and providers who need it for the purposes described: the administrator sees the seats of the licence they administer, and the renewal access record is shown in no panel.
Children
The site and the licence are meant for professionals and are not directed at people under 18. We do not knowingly collect data from them.
Changes to this policy
We may change this policy. The date at the top shows the last change. When a change affects what we do with data you already gave us, we will tell you by e-mail if we have your address.
Contact
Privacy questions: spec-ultra@dyegomaas.com.br.