Skip to content
InvoSort

Last updated: August 24, 2026.

Cookie Policy

InvoSort uses cookies and local storage to run the app, protect accounts, remember preferences, understand site performance, and measure advertising where you allow it.

Necessary

Necessary cookies and local storage support login sessions, account security, protected pages, interface preferences, and checkout or billing flows. Short-lived necessary page state may also remember the email submitted for pending verification and resend timing while you complete signup. This state is not used for analytics or marketing. Necessary storage is always enabled because the service cannot operate correctly without it.

A random pseudonymous consent-context identifier and decision sequence are also kept in first-party necessary storage. They serialize versioned choices across same-origin tabs and let a pending choice or withdrawal resume safely after a reload. They contain no name, email, network address, Google click identifier, or invoice data and are not used for analytics or advertising.

Analytics

Analytics storage helps us understand visits, page performance, consented signup-page views and submissions, selected product interactions, and product interest. Browser funnel events, Vercel Analytics, Vercel Speed Insights, and analytics storage run only after you allow analytics. Because public-page URLs may contain campaign identifiers, DataFast and Google measurement tags run only when you allow both analytics and advertising measurement and the server has acknowledged those choices.

Advertising measurement

Advertising-measurement storage supports campaign and conversion measurement, including Google Ads where applicable. First-touch campaign data is captured only after the server records your choice and is limited to recognized campaign fields, the landing path without its query or fragment, and the referring site origin rather than its full URL. For a consented Google-ad click that leads to trial activation, InvoSort may share the pseudonymous GCLID, trial-activation time, and a random stable pseudonymous transaction ID with Google. This flow does not send name, email, phone, postal address, or invoice contents. Google Consent Mode is denied until the relevant choice is durably acknowledged, and advertising personalization remains denied. When consented Google tags load, ordinary web requests can also make network information such as the device IP address available to Google; InvoSort does not add an end-user IP address to the separate server-side trial-conversion upload. See Google's information-use explanation.

Changing your choice

Your choice is stored locally and as a minimal, versioned, server-timestamped consent receipt. You can reopen the preference panel from this page or from legal/footer links. Withdrawing advertising-measurement consent immediately denies browser signals and stops new tracking. If the server is temporarily unavailable, the pending withdrawal remains in browser storage and is retried on a later page load, online event, or visible session until acknowledged. Acknowledgement clears device-held first-touch campaign data and its attribution identifier, blocks conversion work not yet committed for immediate provider dispatch, and is idempotent. Work already committed by the final database dispatch authorization is limited to receipt persistence and status polling. Withdrawing analytics consent stops new browser funnel and analytics events. Previously recorded operational records may be retained for security, reliability, and lawful recordkeeping. If you clear browser storage, InvoSort may ask for your preference again.