Privacy Policy

This policy describes Briskettle, the business behind GroomPrice, and the one-time digital tool access provided through the website.

Briskettle operates the website and is the controller of the personal data described in this policy. Contact and business details are available on the Contact page.

For privacy questions, contact hello@briskettle.com. Do not send payment-card details by email.

The app uses the following information for the stated purposes:

• A checkout session identifier and access token are used to verify a completed GroomPrice purchase and grant access in the purchasing browser.
• The buyer email returned by the hosted payment flow may be stored with the purchase record so the purchase can be identified and supported.
• Contact forms send your name, email address and message to Briskettle and store them as a contact-message record with a creation time. Product-feedback forms use the same route; fixed-option anonymous feedback is stored with placeholder contact details and the selected feedback message.
• The public case study uses fixed, read-only illustrative data. Its figures and any paid-workspace results depend on entered assumptions and are not guaranteed profit, market pricing or after-tax take-home pay.
• The payment provider processes the payment and any checkout information needed to complete it on its hosted checkout pages.

Support chat by Minisage loads automatically on website pages unless you have disabled it. Loading the script, stylesheet and configuration contacts the provider and exposes normal connection information such as your IP address and browser request information. Automatic loading is not consent to send a conversation or email.

Messages you submit are sent to the chat provider. If you choose Send to team, the widget sends your optional email, latest question and up to the last 40 conversation entries for human handoff. Do not enter passwords, payment-card details or sensitive personal information.

Live handoff stores a conversation identifier, bearer token, cursor and start time in tab session storage under ms-lite-live followed by the public tenant identifier. The inspected widget limits client live polling to two hours; that does not establish deletion from provider systems, and browser session restoration may retain tab storage.

Disable support chat and Use necessary storage only save an opt-out under briskettle.support-chat.disabled.v1 in local storage, attempt to remove the chat tab identifier and reload the page to stop browser requests. The opt-out has no coded expiry and remains until you re-enable chat or clear browser data. If the preference cannot be read, chat fails closed; if it cannot be saved or the identifier removed, an error and a chat-off URL reload are offered. That URL fallback is not a saved site-wide preference. Disabling does not delete an already-sent conversation from provider systems.

Our current chat settings enable AI answers using OpenAI gpt-4o-mini. Messages and recent conversation history are sent through MiniSage. Its published policy says it sends your message, recent history and our published answers to OpenAI through our own provider account. MiniSage describes masking certain contact and payment details in visitor messages; this does not make conversations anonymous. Do not include sensitive information.

Our selected MiniSage retention setting is 90 days. MiniSage’s published policy says visitor questions are kept for the selected period and human-handoff conversations are kept for 90 days after the last message. It says assistant reply text is not stored and older records are deleted by a scheduled job.

If you choose Send to team, your handoff is routed to Briskettle through our connected Telegram support bot or configured email fallback. The MiniSage retention setting does not determine how long OpenAI, Telegram, email services or recipients keep separate copies or records; their retention arrangements may differ. For questions about information you have sent, or to request access or deletion, contact hello@briskettle.com.

For privacy questions or requests about a conversation you submitted, contact hello@briskettle.com. Disabling browser chat does not itself request deletion from the provider.

Cloudflare Web Analytics is disabled for our website. Cloudflare continues to provide website delivery and security services. Optional browser performance measurement is separate from paid access and your requested workspace functions.

The light/dark control changes the website’s appearance without saving a preference. If you choose ‘Remember my preference’, the site saves your theme in this browser’s local storage under theme and records your explicit choice under briskettle-theme-remember. Turning this option off removes only the saved theme and its choice marker; paid access and workspace records are unchanged. Unsaved choices reset to your device’s theme when a page loads again. Earlier saved themes without an explicit choice are applied for that page load and their old theme keys are removed; choose ‘Remember my preference’ to save the theme again.

GroomPrice settings, jobs and job history are saved in this browser when storage is available, with a limit of 1,000 jobs. They are not cloud-synchronised. Export a workspace backup before clearing browser data. Recovering paid access does not restore this workspace.

The guided lesson uses session-storage keys groomprice.practice.progress.v2 and groomprice.practice.saved.v2 for progress and a saved-practice marker. They normally last for the tab session, although browser session restoration may retain them.

The cookie preferences notice stores only an acknowledgment under briskettle.privacy.choice.v1 in local storage when you save a choice. It has no coded expiry and remains until browser data is cleared. This closes the notice, does not consent to tracking, and does not store your theme unless you choose the optional theme preference. Reopen Cookie preferences in the footer to change the theme choice. Closing the notice for this visit does not save an acknowledgment.

The groomprice_access cookie recognises verified paid browser access. It is HTTP-only, uses SameSite=Lax and is Secure in production. Its browser maximum age is 365 days; this is not a guarantee of entitlement duration. Optional browser measurement is not required for paid access.

Payment and checkout information is shared with the payment provider only as needed to create and verify the transaction. The app does not sell personal data and does not add advertising or marketing trackers.

Purchase and access records are retained for as long as needed to provide paid browser access, support the transaction and meet applicable record-keeping requirements.

Depending on applicable law, you may have rights to access, correct, delete or restrict use of personal data, and to object or complain to a supervisory authority. Contact hello@briskettle.com first so your request can be assessed.

The paid-access token is set as an HTTP-only cookie and is not exposed to page JavaScript. No security measure is perfect, so do not share a browser with someone you do not trust after purchasing access.

This policy may be updated when the product, providers or legal information changes. The date above identifies the current information.