Fintax uses cookies, local storage, pixels, tags, scripts, and similar technologies to operate the site, protect sessions, measure usage, understand conversions, and improve our services.
This policy explains the technology categories we use, why we use them, who may manage them, and how you can limit or disable them.
1. What cookies and similar technologies are
Cookies are small files stored on your device when you visit a website. Similar technologies, such as local storage, session storage, pixels, tags, web beacons, SDKs, and scripts, help remember preferences, authenticate sessions, measure interactions, detect errors, or record technical events.
2. Controller
The party responsible for information obtained through these technologies is Fintax. For questions or requests, contact us through WhatsApp +52 81 1015 3722, Instagram @fintaxmx, Facebook fintaxcontadores, Email servicio@fintax.mx.
3. Categories we use
We may use the following categories:
- Necessary or technical technologies for loading the site, browsing, login, security, fraud prevention, checkout state, and core features.
- Preference technologies that remember language, region, display, or browser choices.
- Analytics and performance technologies to measure traffic, pages, events, conversions, funnels, scroll depth, errors, performance, and aggregate usage.
- Security and anti-fraud technologies to detect unusual access, bots, abuse, spam, improper authentication, or suspicious transactions.
- Advertising and conversion measurement technologies to measure campaign results and improve Fintax-related advertising.
- Support and communication technologies that enable chat, tickets, messaging, and support integrations.
4. Third-party providers
Some technologies may be managed by external providers needed to operate the site or measure results. These may include authentication, payments, hosting, analytics, conversions, support, messaging, video calls, email, security, or infrastructure.
With optional measurement permission, the Meta pixel records public page views, WhatsApp contact clicks and confirmed consultations to measure Facebook and Instagram campaigns. Meta receives technical browser information and compatible public URLs and may use _fbp and _fbc cookies for attribution. Bookings use opaque event IDs; clicks do not include the phone, message or support reference. After a verified purchase, isolated measurement sends the amount, currency and an opaque order event ID without access to the confirmation content or private URL parameters. Navigation measurement does not load on administration, profile, sign-in or checkout pages. We do not configure advanced matching or automatic form detection. Consented pending events may be retained for up to 10 minutes for retry on return; opaque deduplication receipts, for up to 90 days. Withdrawing permission stops events and removes these site records and cookies.
Providers may include Clerk, Stripe, Vercel, Vercel Analytics, Google Analytics, Google Ads, OpenAI Ads, Google Workspace, Google Calendar, Google Meet, ManyChat, Twilio, Resend, Convex, and other technical providers, depending on what is enabled.
These third parties may process information under their own privacy, cookie, and security policies.
With measurement permission, the OpenAI pixel measures page views, submitted contact requests, scheduled consultations and WhatsApp widget clicks. Measurement uses a random pseudonymous identifier to improve matching; it is stored in this browser and removed when consent is withdrawn. When a contact request or consultation is successfully saved, the server may send OpenAI the normalized email as a SHA-256 hash, together with that identifier and available attribution references. The email and identifier are never sent in plain text. WhatsApp clicks do not include your email. The pixel's automatic advanced matching may also detect supported contact information and send its SHA-256 hash.
5. Specific purposes
We use these technologies to:
- Authenticate and maintain secure sessions.
- Remember browsing, language, or checkout preferences.
- Process payments, detect errors, and prevent fraud.
- Measure visits, interactions, conversions, forms, purchases, clicks, scroll, and funnels.
- Improve content, experience, performance, security, and support.
- Manage chat, tickets, messages, scheduling, and advisor handoff.
- Distinguish human traffic from automated or malicious traffic.
6. Duration
Duration depends on each technology. Session cookies are deleted when the browser closes; persistent cookies may remain for days, months, or the period configured by Fintax or the provider.
You can inspect specific cookies through your browser developer or privacy tools.
The OpenAI pixel may store __oppref for 30 days after recording an ad reference and __obref for 365 days after creation. Withdrawing measurement consent tells the pixel to delete both cookies.
With measurement consent, the browser stores a pseudonymous OpenAI identifier in local storage to recognize visits from that browser. It is removed when consent is withdrawn or site data is cleared.
7. Managing or disabling cookies
The cookie control lets you accept or reject optional measurement cookies and identifiers. Before choosing and after rejecting, Vercel Web Analytics continues measuring public visits in aggregate without analytics cookies. Google Analytics and Google Ads use Consent Mode: analytics and advertising storage and advertising user data remain denied; limited cookieless signals are sent for basic measurement and modeling. Personalized advertising stays off in all cases.
Vercel measurement excludes credentials, sensitive URL parameters and fragments. Without acceptance it retains only recognized campaign source and medium labels, such as google, chatgpt, cpc or paid; after acceptance it may retain compatible campaign labels. Events sent directly by Fintax to Google use public URLs without query parameters or fragments; limited conversion events do not include form, consultation or transaction identifiers. Google tags may also generate automatic signals containing technical browsing information according to Consent Mode and Analytics settings. First-party tracking measures visits, clicks, scroll, duration and known funnel stages before a choice and after rejection, using temporary identifiers held only in page memory. These basic events are not linked to your account and do not include form data; a full reload creates another session. Acceptance allows session and retry continuity across reloads, additional details and Google cookies. Rejection keeps OpenAI Ads and optional persistent identifiers disabled. Withdrawal removes persistence and discards pending detailed events; basic measurement continues. The pseudonymous OpenAI identifier is created only after acceptance and removed on withdrawal.
After accepting or rejecting, you can change or withdraw permission using the Cookies button on this page, accessible through the Cookies link in the site footer. Save preferences applies your selection: with Analytics enabled you allow optional measurement; with Analytics disabled basic measurement without analytics cookies remains active. Withdrawing a saved permission reloads the page to stop loading optional tools. If the browser blocks storage, the choice applies to the current page. You can also block or delete cookies through your browser settings. Disabling necessary technologies may affect login, checkout, security, support, preferences, or protected browsing.
8. Changes and contact
We may update this policy to reflect legal, technology, provider, or site functionality changes. The current version will be published on this page.
If you have questions about cookies or similar technologies at Fintax, contact us through WhatsApp +52 81 1015 3722, Instagram @fintaxmx, Facebook fintaxcontadores, Email servicio@fintax.mx.