Cookie policy
Last updated: 9 October 2026
This policy explains what Gugab stores on your device, and why. Gugab is provided by SHOVVA LTD (“we”, “us”), 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. If you have a question about it, contact us at support@gugab.com.
The short version
- We store only what is essential to run the service. We use no advertising cookies, no analytics cookies, and nothing that follows you to other websites.
- Looking around this website stores no cookies on your device.
- Opening a quote that a business has sent you stores no cookies from us either.
- Logging in to the app sets sign-in cookies, because that is how the app knows it is you.
- Choosing a language before you log in sets one small cookie that remembers it.
What cookies are
Cookies are small text files that a website asks your browser to keep. Browsers can also keep other things for a website, such as saved copies of its files. This policy covers all of it, not only cookies.
What we store
Sign-in cookies
These are set when you log in or create an account. They hold a signed token that proves you are logged in, so you don’t have to give your password on every screen. Scripts on the page can’t read them.
- Who gets them: businesses logged in to the app. Website visitors and customers opening a quote do not.
- How long they last: until you log out, or 14 days after you logged in, whichever comes first.
- Type: essential. Without them the app can’t keep you logged in.
A quote you haven’t saved yet
While you write a quote in the app, what you have typed is kept in your browser, so it isn’t lost if your phone switches apps or you are logged out before you save it. It is offered back to you, and deleted when you save it, leave it on purpose or log out.
- Who gets it: businesses writing a quote in the app.
- How long it lasts: until you save or leave the quote, or log out, and never more than 7 days.
- Type: essential, for work you are doing.
The language you chose
If you choose a language on the app’s log-in or sign-up screen, a cookie called gugab_lang remembers it, so the screens stay in that language. It holds only the language’s code, and is set only when you choose one.
- Who gets it: people who choose a language before logging in.
- How long it lasts: one year, or until you clear this site’s data in your browser.
- Type: essential, for a setting you asked for.
Notifications, if you turn them on
If you turn on notifications in the app, your browser asks your permission and keeps your answer. If you say yes, we keep the address your browser’s push service gives us for that device, so we can send them; turning them off deletes it. If you choose “Not now” when the app offers them, it remembers that on your device for a month so it doesn’t ask again.
- Who gets it: businesses using the app who turn notifications on, or choose “Not now”.
- How long it lasts: until you turn notifications off; “Not now” for 30 days.
- Type: essential, for a setting you asked for.
App files saved for speed
When you open the app, your browser saves copies of the app’s own files (its styles, scripts and icons), so that it opens quickly and can be added to your home screen. Nothing about you, your account, your quotes or your customers is saved this way.
- Who gets them: anyone who opens the app, including its log-in page.
- How long they last: until the app is updated, or until you clear this site’s data in your browser.
- Type: essential to how the app works.
A security cookie from Cloudflare
Some traffic reaches us through Cloudflare, which protects the service and connects the web addresses of businesses that send quotes from their own domain. Cloudflare may set a cookie named __cf_bm to tell real visitors from automated traffic.
- Who gets it: visitors whose connection passes through Cloudflare, for example a customer opening a quote on a business’s own web address.
- How long it lasts: up to 30 minutes.
- Type: essential. It is used only for security.
Paying by card: Stripe
Card payments happen on Stripe’s own pages, not on ours. When a customer pays a deposit, or a business connects its Stripe account or manages its subscription, the browser goes to Stripe. Stripe sets its own cookies there, mainly to prevent fraud and to make the payment work. They are covered by Stripe’s cookie policy, and we can’t read them.
What we don’t use
- No analytics or statistics cookies.
- No advertising or social media cookies, and no tracking pixels on our pages.
- No tracking pixels or tracked links in the emails we send.
- No fonts, videos, maps or scripts loaded from other companies on our pages.
Why you don’t see a cookie banner
The law says a website must ask before it stores anything on your device, unless that thing is strictly necessary for a service you have asked for. In the UK the rule is in the Privacy and Electronic Communications Regulations, which work alongside the UK GDPR; in the EU it is in the ePrivacy rules, which work alongside the GDPR. Everything listed above is strictly necessary, so there is nothing to ask your consent for.
If we ever want to add something that isn’t essential, we will ask for your consent first, it will stay off until you agree, and this policy will be updated before it is switched on.
Your choices
- Logging out of the app removes the sign-in cookies straight away.
- You can block or delete cookies and saved site data in your browser’s settings. If you block the sign-in cookies you won’t be able to log in to the app. The website and customer quotes work without any cookies.
Cookies and personal data
The sign-in cookies identify your account, so they count as personal data. How we handle personal data, and the rights you have over it, are set out in our privacy policy.
Changes
We’ll update this policy whenever what we store changes, and show the date at the top.