Website privacy

Registration revision: 2026-10-10-pix-avulso.

Controller and scope

This notice describes data processing on the website, in the MasterFinder account, and in the backend used by the extension. Local operation and extension permissions are detailed in its dedicated privacy policy.

MasterFinder is provided by Caetano Hillesheim Sadosiuk, an individual in Brazil. Privacy requests and support questions may be sent to suporte@masterfindertool.com. The controller's Brazilian taxpayer number is not published on the website.

Data we process

To create and maintain an account, we process full name, email, Brazilian mobile number, credentials protected by Supabase Auth, phone and email verification, sessions, and acceptance records. During the temporary launch exception, the mobile number is stored without being sent to Twilio, phone_verified_at remains empty, and we separately record that confirmation was waived. Enter a number you can access because confirmation will be requested later. When the normal flow resumes, the code will be sent by text message (SMS/RCS) through Twilio Verify. WhatsApp remains disabled and reserved for future adoption, which will be disclosed before any message is sent. The phone number is not used for login, recovery, two-factor authentication, or subsequent messages, and may appear on more than one account. Email confirmation is optional and recommended; its absence does not prevent login, recovery, checkout, receipts, or financial communications.

For billing, MasterFinder keeps Stripe technical identifiers and subscription or Pix purchase and access status. For cards, we keep the brand, last four digits, country, funding classification, and a fingerprint protected by HMAC. For one-time Pix, we keep session and payment identifiers, amount, status, and the dates of the purchased month. We never receive or store the full card number or CVC.

The Brazilian CPF is collected when a payment method is added, validated, and transiently sent to Stripe as the Customer's tax identification. MasterFinder does not store or log the CPF in plain text; it only retains versioned HMACs for free-period eligibility. The billing address is collected by the Stripe component and remains with Stripe.

When confirmation is active, we record the requested channel without assuming the actual transport: an SMS request may be delivered as RCS. We do not store or log the OTP. During the temporary waiver, there is no Twilio request, SID, channel, or code; the phone number and its HMACs continue to protect trial eligibility.

We also maintain consent events, sanitized webhooks, an email queue, a pseudonymous financial ledger, operational switch status, and ephemeral pseudonymized identifiers for abuse limits. We do not use raw IP addresses as proof of consent.

When the extension completes a requested extraction, the backend receives the HTTPS source URL to build global mining statistics. In the MasterShop flow, this may include the product page, the Meta ad used as the source, or the product/ad pair that supplied context. In the ad-search flow initiated from a product, the direct MasterShop product URL is recorded separately. URLs are normalized and stored with a derived key, aggregate count, and first- and last-use dates, without a user_id, account link, or individual history identifying who performed each mining operation. The two flows keep independent counters.

When preparing a Meta search from a direct MasterShop link, that URL is sent to the MasterFinder backend after extraction to update the global counter, but it is not part of the payload sent to Google Gemini. In this flow, the model receives only the extracted product name and selected language. For MasterShop flow generations, public URLs or sanitized context may be sent to Gemini as described in the extension policy.

Purposes and legal grounds

Data is used to create and protect accounts, confirm and recover access, execute the subscription, grant or revoke account_access, prevent multiple trials, issue receipts, answer support, fulfill data-subject requests, maintain security and financial integrity, and produce aggregate mining statistics to understand use and guide MasterFinder improvements.

Processing follows the performance of the Terms and requested subscription, compliance with applicable duties, legitimate interests in security and fraud prevention, and separately recorded consent when required.

Free period and abuse prevention

There is at most one trial per account, supplied phone number, CPF, or card fingerprint. IP and device are not hard blocks. The temporary confirmation waiver does not remove the phone number from this rule. When a key has already participated in a trial, we do not charge or block the card for that reason; we only offer a direct subscription. Creating another account with the same phone number remains allowed, but does not grant another trial.

Anti-fraud claims are retained for as long as the trial program exists. After account deletion, they are detached from the account identity but are not released to originate another trial.

Cookies and local storage

We use only strictly necessary resources: HttpOnly, Secure, and SameSite cookies for PKCE, session, recovery, and the “Remember me” choice; and local storage for theme and language preferences. A persistent session has a maximum inactivity period of 30 days. A session without “Remember me” ends with the browser session.

There are no analytics, advertising pixels, behavioral advertising, or optional cookies. Stripe, Twilio, and Cloudflare Turnstile may use indispensable technical resources for payment and security checks under their own policies.

Providers

• Supabase: authentication, database, global mining aggregates, and scheduled tasks;
• Render: hosting and execution of the protected API used by the extension;
• Google Gemini API: generation of terms, categories, and search plans using the limited data described above; the direct MasterShop URL used to prepare a Meta search is not sent to the model;
• Stripe: card, one-time Pix, address, tax CPF where applicable, subscription, portal, and receipts;
• Twilio Verify and SMS/RCS delivery providers: receive the mobile number when confirmation is active to deliver and verify the code. During the temporary registration waiver, the number is not sent to Twilio; WhatsApp/Meta will only participate if that future channel is enabled and disclosed;
• Resend: transactional emails;
• Cloudflare Turnstile: automated abuse prevention for registration, resend, and recovery;
• Vercel and Vercel Blob: website hosting and file distribution;
• YouTube: privacy-enhanced player, loaded only after your action;
• Discord and WhatsApp: external channels opened only when you choose their links.

These providers may process technical data and operate infrastructure outside Brazil under their terms and applicable transfer mechanisms. We do not sell personal data or use it for personalized advertising.

Retention and deletion

• abandoned financial attempt: up to 24 hours;
• verification challenges: the raw destination is removed within 24 hours; Twilio and delivery providers apply their own technical retention;
• profile and sessions: deleted when the deletion request completes;
• minimum pseudonymous financial ledger: five years;
• anti-fraud claims: duration of the trial program;
• normalized URLs and global mining counters: indefinitely, without an account link or individual history and with separate MasterShop and Meta flow counters;
• support messages: for as long as necessary for service and related obligations;
• Stripe receipts and records: under Stripe's own retention and applicable duties.

Deletion requires password reauthentication and textual confirmation. It cancels the subscription, revokes sessions and access, and requests deletion of the Customer when technically possible. The process is irreversible and may take up to five minutes. A trial claim will not be released automatically.

Rights and contact

You may request confirmation, access, correction, information, objection, portability where applicable, or deletion at suporte@masterfindertool.com. Export requests are handled by support in this MVP; there is no automated tool. We may request minimum information to confirm identity and locate the account.

Local extension data can be removed through logout, reset, uninstallation, or clearing browser data. Because global mining aggregates do not identify the account or record the author of each extraction, deleting an account does not reduce those counters. Do not send passwords, tokens, cookies, full CPF, or card details in support messages.

Updates

This text is versioned. Material changes will be communicated, and existing users will need to accept updated policies before continuing to use protected features.