How to read this page
This document is designed to work with the other QuickBooking legal pages instead of repeating the same information everywhere.
1. Purpose
QuickBooking seeks to limit the use of these technologies to what is necessary for operation, security and the features actually used.
QuickBooking currently does not use analytics tools intended to track user behavior for statistical or marketing purposes.
2. QuickBooking publisher
QuickBooking is operated by DOGOOLLE LTD, Carlyle House, Lower Ground Floor, 235 Vauxhall Bridge Road, London SW1V 1EJ, United Kingdom. Company Number: 16357520.
Contact: support@dogoolle.com.
3. What is a cookie?
A cookie is a small piece of information stored or read on your device when you visit a website or use an online service.
Similar technologies may also be used, including browser local storage, session storage or technical identifiers needed for an application to operate.
In this policy, the term cookie may also refer to these technologies where they perform a comparable function.
4. Why does QuickBooking use cookies?
QuickBooking may use cookies or similar technologies where they are needed to maintain a user session, secure dashboard access, remember certain technical preferences, operate the booking form, operate certain integrations, enable certain payment operations, and prevent errors or abuse.
QuickBooking does not seek to place cookies that are unnecessary for service operation.
5. Strictly necessary cookies
Some cookies are essential for QuickBooking to operate. They may be used to authenticate a user, maintain a session, protect forms, secure requests and temporarily remember certain information needed for the booking journey.
Where these cookies are strictly necessary to provide the requested service, they may be used without prior consent, subject to applicable law.
6. QuickBooking dashboard
The dashboard for Customers and administrators may use cookies or technical storage needed for login, authentication, security, session maintenance and certain interface preferences.
These technologies allow the dashboard to work correctly. Disabling them may prevent access or cause malfunctions.
7. Public QuickBooking widget
QuickBooking may be integrated into an Organizer website using the WordPress plugin, a JavaScript widget, an iframe or other publishing methods offered by QuickBooking.
The widget should use only technologies necessary for features actually enabled. Technologies used may therefore vary depending on the Booking Event configuration.
8. Hosted pages
Some Booking Events may be published on pages hosted by the EventMasterSuite environment.
These pages may use cookies or technologies strictly necessary for QuickBooking operation and the features enabled by the Organizer.
Where non-essential technologies are added to a hosted page, applicable consent rules must be respected.
9. Stripe payments
When Candidate Payments is enabled, QuickBooking uses Stripe for payment processing.
Stripe may use its own cookies or similar technologies needed to secure payments, prevent fraud, operate Stripe Checkout or payment components and authenticate certain operations.
Technologies used by Stripe are subject to Stripe applicable policies and terms. The presence of Stripe cookies depends on actual use of payment features. If no Stripe component is loaded on a page, this integration in QuickBooking alone does not mean that a Stripe cookie is automatically placed on that page.
10. Chatwoot support
QuickBooking uses Chatwoot for customer support. Support is intended for QuickBooking Customers and their authorized administrative users.
Chatwoot may use cookies or storage necessary for the conversation to work when it is actually loaded.
In QuickBooking, the support interface may be designed to load only when the user requests access to support. People making a booking are not intended to use QuickBooking support for Customers.
11. Postmark emails
QuickBooking uses Postmark for certain transactional communications. Postmark mainly acts server-side for sending emails.
Use of Postmark by QuickBooking therefore does not mean that a Postmark cookie is automatically placed on the browser of a person using the booking form.
Any tracking technologies associated with emails should be assessed separately according to the configuration actually used.
12. Twilio SMS
QuickBooking uses Twilio for certain communication and SMS features. These processing operations are mainly performed server-side.
Use of Twilio to send an SMS therefore does not mean that a Twilio cookie is automatically placed on the recipient browser.
Twilio should appear in a page cookie inventory only if a component actually loaded on that page uses a corresponding technology.
13. Analytics
QuickBooking currently does not use any analytics service intended to track user behavior for statistical or marketing purposes.
QuickBooking therefore currently does not, on its own initiative, use services such as Google Analytics or Meta Pixel in the framework described by this policy.
If QuickBooking later introduces non-essential analytics or marketing technologies, this Cookie Policy and consent mechanisms will be updated where required.
14. Organizer website
When an Organizer embeds QuickBooking on its own website, that website may use other cookies that are not controlled by QuickBooking.
For example, the Organizer may use an analytics tool, advertising tool, marketing pixel, embedded videos, social network tools or other WordPress plugins.
These technologies are the Organizer responsibility when added by the Organizer. The cookie policy of the Organizer website should inform visitors about technologies actually used on that site.
15. Organizer responsibility
The Organizer must ensure that its own website complies with rules applicable to cookies and other trackers it uses.
This includes, where necessary, providing clear information, identifying purposes, obtaining consent before placing non-essential cookies and allowing consent withdrawal.
QuickBooking cannot determine which plugins, marketing tools or external scripts are installed on the Customer website.
16. Consent
Cookies strictly necessary to provide a service explicitly requested may be used without prior consent where applicable regulation allows it.
Non-essential technologies may require prior consent. Depending on how they work, this may include non-exempt analytics, advertising, profiling, marketing or certain third-party content.
Where consent is required, refusal must be as accessible as acceptance and consent must be withdrawable.
17. Cookie management
Depending on the page used, cookies may be managed from the consent mechanism on the site, from browser settings or from settings offered by the relevant third-party service.
Deleting certain strictly necessary cookies may prevent QuickBooking from working correctly.
18. Cookie duration
The retention period depends on the cookie function. Some cookies are deleted when the browser is closed. Others may be kept for a limited period to perform a necessary function.
QuickBooking does not wish to keep cookies beyond the time needed for their purpose.
A technical inventory of cookies actually used may specify for each one its name, provider, purpose, duration and category.
19. Third-party cookies
Third-party services may change the cookies or technologies they use. Where QuickBooking actually loads a third-party service on a page, the provider policies may provide additional information about its technologies.
The main services that may be concerned depending on enabled features are Stripe and Chatwoot.
Postmark and Twilio mainly operate server-side and should not automatically be considered as placing cookies on QuickBooking pages.
20. Cookie inventory
QuickBooking maintains or may maintain an inventory of cookies and storage actually used by its interfaces.
This inventory should reflect the real technical behavior of the platform. It should not present as active cookies belonging to services that are not loaded.
The inventory may evolve when QuickBooking or its providers modify their technologies.
21. Changes to this policy
This Cookie Policy may be updated when QuickBooking evolves, a new service is integrated, a cookie is added or removed, or applicable rules evolve.
The last updated date appears at the top of the document.
Where a new technology requires consent, the appropriate mechanism must be implemented before or when it is activated according to applicable requirements.
22. Additional documents
This Cookie Policy should be read together with the QuickBooking Privacy Policy, the QuickBooking Terms of Service and the Data Processing Agreement (DPA) where applicable.
When a Booking Event is published on an Organizer website, the Organizer privacy policy and cookie policy may also apply.
23. Contact
For any question about QuickBooking use of cookies: DOGOOLLE LTD, Carlyle House, Lower Ground Floor, 235 Vauxhall Bridge Road, London SW1V 1EJ, United Kingdom. Company Number: 16357520. Email: support@dogoolle.com.
Legal validation
These documents are operational templates for QuickBooking. Final review by a GDPR/privacy lawyer is recommended, especially for the DPA, legal bases and retention periods.