Privacy Policy
Your email is private. Your record is public.
How CADRAX handles what you tell The Ego Registry: what for, with whom, for how long and how you stay in charge of your data.
Controller: CADRAX TECNOLOGIA LTDA · CNPJ 68.531.899/0001-02
In short
Four things to know now
A public card you control
Public name or pseudonym, city, profiles and declarations appear on the records, with the title, the amount and the date of each purchase. You edit, hide or anonymise them in My Account.
Private, encrypted email
Your email never appears on the record. It, the accepted terms, the messages, the reports and the access logs are kept encrypted. We do not sell data.
Metrics only with your permission
Google Analytics, our own metrics and the count of who is watching now stay off until your yes and never turn on with Global Privacy Control active.
Download your data in My Account
The Download my data button hands you at once the file with what we keep about you. Other requests go to privacy@egoregistry.online.
Contents · 13 sections
- 1Who looks after your data
- 2What is public and what is private
- 3What we use it for and on which legal basis
- 4Who we share it with
- 5International transfer
- 6How long we keep it
- 7Your data rights
- 8Cookies and storage
- 9Security and incidents
- 10Application access logs
- 11Children and teenagers
- 12Automated decisions
- 13Changes to this policy
Section 1
Who looks after your data
The controller is CADRAX TECNOLOGIA LTDA, CNPJ 68.531.899/0001-02, established at Av. Cristóvão Colombo, 2144, Sala 408, Andar 3, Floresta, Porto Alegre - RS, CEP 90560-001. CADRAX is a small-scale processing agent and, as article 11 of Resolution CD/ANPD No. 2/2022 allows, handles directly, through privacy@egoregistry.online, the requests of data subjects and the communications of the Brazilian National Data Protection Authority (ANPD). This policy applies to The Ego Registry and is part of the Registry terms.
Section 2
What is public and what is private
Public on the record
- Public name or pseudonym, also on the certificates and images.
- City and public profiles of your card, in the categories that show them.
- The declaration of each record.
- Title, amount, date and time of each purchase and position in the queue.
- An authorised testimonial, with the public name of the chosen record.
You choose the name, the city and the profiles, and you may hide the card from a record or anonymise them all. Pages with a public identity may appear in search engines; without one, we ask search engines to stop indexing them.
Private, never shown
- The email of the purchase, kept encrypted.
- Card details, typed into the secure fields of Stripe, which never reach our servers.
- The accepted terms, the history of the order and the tax documents.
- The declared country of residence, the country your request came from, the billing country and state, and the country of the card issuer.
- Messages to support, cancellation requests and reports, encrypted.
- IP address and source port, kept only in the encrypted access logs; against abuse, the IP also becomes a daily code.
- Your communication and cookie preferences.
Section 3
What we use it for and on which legal basis
Each piece of data has a purpose and a basis in the Brazilian General Data Protection Law (LGPD). Without consent you buy normally: only news, usage metrics, testimonials and the notice of a request to the Registrar are left out.
Purchase email
Confirming the order, sending receipts and notices, opening My account and answering you.
Performance of the contract · LGPD art. 7, VSignature card and declarations
Publishing the record and generating its certificates and images.
Performance of the contract · LGPD art. 7, VOrder and payment
Charging, refunding, issuing the invoice and proving the purchase.
Contract, law and defence · LGPD art. 7, II, V and VICountry of the purchase
Checking that each purchase comes from a country we sell to, and proving the market of the sale to the tax authorities: the declared country of residence, the country the request came from, the billing country and state, and the country of the card issuer.
Legal obligation and legitimate interest · LGPD art. 7, II and IXAccess logs
Keeping for 6 months the date, time, IP and port of each sign-in and of each relevant action, as the Brazilian Internet Civil Framework requires.
Legal obligation · LGPD art. 7, IISecurity
Stopping bots, fraud and abuse with Turnstile verification, usage limits, the daily code of the IP and the block of new purchases of an email, when asked.
Legitimate interest · LGPD art. 7, IXOperation metrics
Counting purchases, refunds and failures of the service, without email, name or IP.
Legitimate interest · LGPD art. 7, IXSupport and cancellation
Receiving through the form or by email, answering and solving what you asked. It does not depend on consent.
Contract and procedures at your request · LGPD art. 7, VReports
Receiving the notification, deciding, telling whoever reported and whoever published, and reporting crimes to the authorities when the law requires.
Legal obligation and legitimate interest · LGPD art. 7, II and IXNotice of a request to the Registrar
Sending a single email if the name you asked for enters the catalog.
Consent · LGPD art. 7, ITestimonial
Publishing your story, with the date and the public name of the record you chose.
Consent · LGPD art. 7, INews and invitations
News, invitations and the digest of the agenda, at most 4 emails a week, always with an unsubscribe.
Consent · LGPD art. 7, IUsage metrics
Understanding how the site is used, with Google Analytics, the own metrics of the site and the count of who is watching now.
Consent · LGPD art. 7, ISection 4
Who we share it with
- Cloudflare, Inc. · United States
- Hosts the site and the database, sends the emails of the service, receives the messages sent to support@egoregistry.online and to privacy@egoregistry.online and protects the forms against bots. It acts as processor and, for the technical traffic data and the Turnstile signals, as controller (section 5).
- Amazon Web Services (AWS) · United States
- Provides the email delivery service and processes addresses, message content and technical sending and delivery data as processor.
- Google LLC · United States and other countries
- Only with your permission, receives as processor the Google Analytics metrics of the public pages and of the payment page, without personalised advertising (section 5).
- Stripe, Inc. · United States
- Processes the payments as controller of the data it collects, including to prevent fraud. It receives from us the email, the reference and the amount of the order, and the card data you type straight into its fields.
- Authorities
- Only by court order or when the law requires, as when reporting child sexual exploitation content.
Beyond these cases, we do not sell, rent or give away data, we use nobody’s personal data for targeted advertising and we build no advertising profiles.
Section 5
Data outside BrazilInternational transfer
The data we keep about you are processed outside Brazil, where the supplier is established. The United States has no adequacy decision of the ANPD, so below we say what goes, where, for how long and on which grounds. CADRAX remains responsible for the processing and for your requests.
Cloudflare, Inc. · United States
What it does. Hosts the site, the database, the files and the queues, sends the emails of the service, receives the messages of the support and protects the forms against bots (Turnstile).
Data. What you send to the site (email, kept encrypted; signature card and declarations; order data; support, cancellation and report messages), the access logs and technical connection data, such as the IP address.
Where. Mainly in the United States, where the site runs and the database lives. Technical network logs may be processed in other countries for a limited time, and your browser connects to the nearest Cloudflare data centre.
For how long. While the service operates, over an encrypted connection, and for the periods of section 6.
Grounds. Without this infrastructure we cannot answer what you ask before the purchase, perform the order, meet legal obligations or defend rights (LGPD, art. 33, IX, with art. 7, II, V and VI). The own metrics and the count of who is watching now only work with your permission, which also covers this transfer (art. 33, VIII).
Roles and safeguards. Cloudflare acts as processor under its Data Processing Addendum, which forbids using the data for marketing or advertising and provides for encryption and incident notice. For the technical traffic data and the Turnstile signals it is controller, under its own privacy policy.
Amazon Web Services (AWS) · United States
What it does. Sends the emails of the service. We do not use email open or click tracking.
Data. Email addresses, subject and message content, including order or support information when needed, and technical sending and delivery data.
Where. United States. The recipient’s email provider also receives the message to deliver it.
For how long. The delivery records we keep with this provider are retained for 30 days and contain no email addresses or message content. Message processing for sending, delivery and security follows the service terms; the 30-day period does not apply to all such processing.
Grounds. The purposes and bases remain those of section 3: necessary messages fulfil what you request, perform the order, meet legal obligations or defend rights (LGPD, art. 33, IX, with art. 7, II, V and VI). News and notices based on consent are sent only with your permission, which also covers this transfer (art. 33, VIII, with art. 7, I).
Role and safeguards. AWS acts as processor under the AWS Data Processing Addendum, with security measures, confidentiality and incident notice. The service may store and scan messages to prevent spam, phishing and other harmful content.
Google LLC · United States and other countriesOnly with your permission
What it does. Google Analytics, to measure the use of the public pages (catalog and editorials) and the purchases on the payment page.
Data. The page, the category, the campaign and, on a purchase, the code and the amount of the order, with the identifier of the Google Analytics cookie and device and browser data. Never your email, name or declaration. Google receives the IP address to estimate the approximate location and, it says, does not store it.
Where. In the United States and in other countries where Google keeps data centres.
For how long. Event and user data are kept 14 months, not renewed by new activity; aggregated reports may remain.
Grounds. Your specific and prominent consent, given in the cookie notice, which says the data leave Brazil (LGPD, art. 7, I, and art. 33, VIII). Withdrawing the permission in Cookie preferences stops the sending and erases the Google Analytics cookies of this browser.
Role and safeguards. Google acts as processor, under the Google Ads Data Processing Terms, and uses the data only to provide the service: data sharing with Google and Google Signals are off, and there is no personalised advertising.
Stripe, Inc. · United StatesIn the United States
Stripe, Inc. is a company in the United States and controller of the data it collects to process the payment and prevent fraud. The card data you type go straight to its fields and never reach our servers; it receives from us the email, the reference and the amount of the order. Sending these data to Stripe is a transfer to the United States, needed to perform the order (LGPD, art. 33, IX, with art. 7, V), and what Stripe does with them follows its privacy policy.
Through privacy@egoregistry.online you ask for more information on these transfers and exercise the rights of section 7, with an answer within 15 days.
Section 6
How long we keep it
When a period ends, the purge is automatic: the data are erased, or only the minimum to prove the history remains, such as dates, amounts and verification codes.
- Public page, signature card, declarations and history
- While the service operates, and for 12 months in a static archive after it closes; you can anonymise at any time
- Account email, preferences and followed rounds
- While the account exists
- Accepted terms of the order
- While the record is published and for 5 more years after it stops being shown (cancellation, reversal or closure of the service), or 5 years after the end of an order that ends without publication; afterwards, only the verification code and the accepted version
- Payment data and tax documents
- Until the period of the Brazilian tax law ends: 5 years counted from 1 January of the year after the tax of the order fell due, or while a dispute or proceeding is open
- Audit, moderation decisions and earlier versions of the signature card and of the declarations
- 5 years after the last related fact
- Access logs (IP, port, date and time)
- 6 months; backups are gone within 30 days
- Daily code derived from the IP
- Goes with what it protects: within minutes for usage limits, a day after the access link expires and together with the report or the request to the Registrar
- Support messages, cancellation requests and reports
- 90 days after the case closes
- Requests to the Registrar
- Requested name: 90 days after the decision, and an undecided request closes in 12 months; notice email: up to 7 days after the notice, or on refusal or closure
- Rejected or withdrawn testimonials
- 30 days
- Replaced certificates and images
- 30 days
- Access link and session
- Link: 15 minutes, single use; session: 24 hours without use or 7 days
- Email blocked from new purchases, on request
- While the block holds, kept only as a code
- Usage and operation metrics
- Google Analytics: 14 months, not renewed by new activity; own metrics of the site: up to 3 months; aggregated reports may remain
Section 7
Your data rights
Confirm, access and download
In My Account, Download my data hands you at once a file with what we keep about you, except the access logs, which you ask for separately (section 10), and a statement of origin, purposes, legal bases, criteria, periods and sharing.
Correct
The card and the declarations, in My Account, within the rules of each; the email and the rest, through the privacy channel.
Anonymise, block or erase
Whatever is unnecessary, excessive or processed against the law. Anonymise everything, in My Account, removes your identity from every record.
Portability
The file of Download my data comes in a format another service can read.
Erase what depends on consent
Testimonial, notice of a request, news and metrics.
Know who we share with
It is in sections 4 and 5, and we detail it through the channel if you ask.
Withdraw consent
News in My Account or through the link in each email, metrics in Cookie preferences, a testimonial withdrawn whenever you like and the notice of a request through the privacy channel.
Object and ask for human review
Against processing based on legitimate interest or an automated decision (section 12), through the privacy channel.
Other requests go to privacy@egoregistry.online, free of charge. Each message receives at once an automatic acknowledgement with the date of receipt and the deadline, opens a case in the support of the site itself and is answered within 15 days; account holders receive the answer by email only at the registered address. We accept requests from a representative with a power of attorney and from people without an account, such as someone named in a declaration, with the identification the request needs. If you prefer, we send the answer in print. When the law obliges us to keep a piece of data, such as the proof of a payment or the access logs, we explain which and for how long. You may also petition the ANPD and the consumer protection authorities.
Section 8
Cookies and storage in the browser
The essential ones make the site work. Usage metrics stay off until you allow them and never turn on with Global Privacy Control or Do Not Track active. On larger screens, the cookie notice offers Reject non-essential, Configure and Accept all with equal prominence. On small screens, it offers Configure and Accept all; open Configure to reject non-essential cookies. The preferences dialog keeps all three options.
EssentialAlways on
- __Host-egr-session
- Cookie that keeps My Account open · up to 7 days, ends after 24 hours without use
- __Host-egr-checkout
- Cookie that opens the page of your order without signing in · 7 days
- Cookie choice
- Keeps your choice in the local storage of this browser, with the date and the version of the notice · until you change it or the notice changes
- Tab storage
- Keeps the protocol of a cancellation request and the order just paid that the record page confirms, and avoids old versions of the page · while the tab is open
- Cloudflare security
- Cookies set by the Cloudflare network for security, when needed · period set by Cloudflare
- Card payments
- Device identifiers set by Stripe to prevent fraud · period set by Stripe
Usage metricsOff until your yes
- _ga and _ga_<ID>
- Google Analytics cookies · up to 2 years after the last measured visit, erased when you withdraw your permission
- __Host-egr-presence and ego-presence-selection
- Cookies that pick the sample and count how many sessions are watching now · up to 30 minutes
- Path, campaign and tab
- Link, in the storage of the tab, the steps of a visit and the source campaign and identify the tab in the count of who is watching · 30 minutes; the identifier of the tab, while it is open
- Measurement receipts
- Keep in local storage the codes of the orders and the source campaign, so the same purchase is never counted twice · 30 days
Your choice is kept only in this browser, and we ask again when the purposes, the providers or the destination countries change. With your permission, the metrics data go to Google and to Cloudflare, outside Brazil (section 5). Google Analytics only runs, with your permission, on the public pages and on the payment page, to measure purchases; never in My Account, contact, cancellation, report or access. The site does not fingerprint your browser; the Turnstile check reads technical signals of the browser only to stop bots, and, in card payments, Stripe sets device identifiers to prevent fraud.
Section 9
Security and incidents
Your email, the access logs, the messages to support, the reports, the accepted terms and the tax documents are encrypted with AES-GCM, and to find an email we use a code with a secret key (HMAC), without decrypting the database. The site uses HTTPS, bot checks and usage limits. Administrative accounts require two-step verification, and every look at private data is logged. If an incident may bring you relevant risk or harm, we notify the ANPD and the people affected within 3 working days (Resolution CD/ANPD No. 15/2024).
Section 10
Application access logs
The law obliges CADRAX to keep the access logs of the site for 6 months (Brazilian Internet Civil Framework, art. 15, and Decree 8,771/2016, art. 15-A). We keep only the acts that matter, not the browsing.
- When we log
- At each sign-in and each relevant action: asking for an access link, buying, declaring, editing the card, sending a message, a report or a request to the Registrar, cancelling and anonymising. Pages merely visited are not logged.
- What we keep
- Date and time in UTC, IP address, source port (the number a carrier uses to tell apart customers who share the same IP), transport protocol, the kind of action and the account, order or case linked to it.
- Legal basis
- Compliance with a legal obligation (LGPD, art. 7, II). These logs serve neither marketing nor metrics.
- Who looks
- They are encrypted and kept apart from the rest. Only the person responsible for the company looks at them, and every look is noted.
- When we hand them over
- Only by court order or when the law requires a crime to be reported to the authorities, such as child sexual exploitation content (Law 15,211/2025, art. 27).
- How long
- Erased right after they turn 6 months old; backups are gone within 30 days. We keep them longer only at the request of an authority, by court order, by a legal duty of preservation or for the defence of the company in proceedings. Being a legal obligation, they are not erased earlier on request.
- Where they are
- On the infrastructure of Cloudflare, outside Brazil (section 5).
- Your copy
- Ask privacy@egoregistry.online for your own logs; we hand them over once we confirm the account is yours.
Against abuse, we also use a daily code derived from the IP with a secret key, which does not keep the IP itself and is erased together with what it protects (section 6).
Section 11
Children and teenagers
The Ego Registry is not meant for children or teenagers. Purchasing is only for people aged 18 or older. You declare your age by ticking the confirmation on the order, and its text is kept in the accepted terms; to confirm your age, we ask for no document, date of birth or biometrics. We use nobody’s personal data for targeted advertising and build no advertising profiles.
If a purchase was made by a minor, the legal guardian asks support to annul it with the order number. We confirm through the email of the purchase or the payment details, without asking the family for documents, and refund the full amount to the card it was paid with; only if that refund is refused or fails do we send it by bank transfer to an account in the name of the payer. We remove the card and the declarations, close the account and, if asked, block new purchases from that email address. If the purchase still held the post, the post goes back to whoever held it before. Of the rest, we keep only what section 6 provides for any order, such as the financial and tax records, the accepted terms and the access logs, along with the reason for the annulment. Anyone may ask for new purchases from their own email address to be blocked.
Section 12
Automated decisions
Some limits and filters are automatic:
- Up to 20 orders a day per person.
- Up to 3 reservations expired per title a day; after that, a new reservation of that title only the next day.
- One exclusive reservation at a time; emails that refuse our messages cannot buy.
- An attention notice from $1,000.00, an extra confirmation of the amount from $10,000.00 and prior approval from $100,000.00.
- Filters that hold public names, declarations and links for human review, including mentions of gambling and adult content. The form refuses gambling, betting or sexual addresses, and a new or changed site waits for review before it shows.
- The risk analysis Stripe runs on each payment, under its own rules.
No final moderation is automatic: a person decides, and nothing goes offline by itself because of a report. You can ask for the review of any decision of ours through privacy@egoregistry.online (LGPD, art. 20); the analysis of Stripe is reviewed by Stripe itself.
Section 13
Changes to this policy
Each version has a number and a date, and a copy of the one in force at your purchase is kept on your order. We announce relevant changes on this site. What depends on consent only changes with your yes: if the purposes, the providers or the destination countries of the metrics change, we ask again.
Controller and privacy channel
Who answers for this policy
- Controller
- CADRAX TECNOLOGIA LTDA
- Channel for data subjects and the ANPD
- privacy@egoregistry.online
- CNPJ
- 68.531.899/0001-02
- Classification
- Small-scale processing agent (Resolution CD/ANPD No. 2/2022)
- Address
- Av. Cristóvão Colombo, 2144, Sala 408, Andar 3, Floresta, Porto Alegre - RS, CEP 90560-001
- General support
- support@egoregistry.online
This policy is part of the Registry terms. A copy of the version in force at your purchase is kept on your order.
Version 2026-10-26.1 · Oct 26, 2026
