CloserDesk

Privacy policy

Last updated 9 October 2026

Who we are

CloserDesk is run by Bhavishya Raghav, based in India. Contact: hello@closerdesk.me. This policy explains what we do with personal data, including data we receive from Google when a venue connects its Gmail account.

Google user data

When a venue connects its Gmail account, CloserDesk requests two permissions:

What we keep: for each enquiry, the sender's name and email address, the subject line, the time it arrived, the dates and guest numbers it mentions, and the replies we sent. We don't keep the text of incoming emails; we store only a fingerprint (checksum) of it, to avoid answering the same message twice.

Once, when a venue starts, we read the sender and time (never the text) of up to 400 of its inbox conversations from the year before, to measure how quickly it used to reply. Only the totals are kept.

How it's used: only to provide the enquiry service to the venue that connected the account: drafting and sending replies, and producing the venue's monthly Enquiry Record. The text of an enquiry is passed to our AI model provider only to draft that reply.

What we never do: sell Google user data, use it for advertising, use it to build or train general AI models, or let anyone read it except where the venue asks us to (for support), where it's needed for security, or where the law requires it.

CloserDesk's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting: a venue can revoke access at any time at myaccount.google.com/permissions, or by asking us. When an agreement ends, we delete the venue's Gmail access tokens and its enquiry data within 30 days, unless the law requires us to keep a record.

Microsoft user data

When a venue connects a Microsoft 365 or Outlook.com mailbox, CloserDesk asks Microsoft for permission to read and write mail (Mail.ReadWrite: to see new messages and to write reply drafts in the venue's own mailbox), to send mail (Mail.Send: replies the venue has approved, from its own address), and to read the mailbox's own address (User.Read). We treat it exactly as we treat Google user data above: the same things kept, the same uses, and the same things we never do.

Disconnecting: a venue can remove CloserDesk at any time at myapplications.microsoft.com (Microsoft 365) or account.live.com/consent/Manage (Outlook.com), or by asking us. When an agreement ends, we delete the venue's Microsoft access tokens with its other data, as above.

Businesses we contact

What we hold: the business's name, website, and the business email address and contact name published on its website, in public directories or on LinkedIn, plus notes of our emails and replies.

Why, and our lawful basis: to offer our service to businesses it may help. Our lawful basis is legitimate interests (UK GDPR Article 6(1)(f)). We only write to business addresses, and every email tells you how to stop hearing from us.

How long we keep it: 12 months after our last contact. If you ask us to stop, we keep only your email address on a do-not-contact list, so we never write again.

The answers map on our homepage

If you type a website into the answers map, CloserDesk reads that website's public pages to check them against the questions couples ask. Nothing you type is stored. Bhavishya is told which website was read, so he can offer to go through the result with you.

People who ask for a call

If you use the form on our homepage, we receive the name, venue, email address and time you give, by email. We use them only to arrange the call, and keep them as we keep the details of businesses we contact.

Our clients

What we hold: contact details for the people at the venue who use CloserDesk, contracts, invoices and our emails with you.

Why, and our lawful basis: to provide the service and get paid (contract, Article 6(1)(b)), and to keep financial records (legal obligation, Article 6(1)(c)).

How long we keep it: for the length of our agreement, then as long as tax and accounting law requires.

Couples who enquire at a venue

For enquiries we handle on a venue's behalf, the venue is in charge of the data and its own privacy notice applies. We act only on the venue's instructions, under a written data processing agreement.

What we hold for a venue about its couples: their names and email addresses, the dates and guest numbers they ask about, and their answers on their own page (a date to hold, a viewing time). Once a couple books: the payments the venue records, the final details they add (guest numbers, timings, suppliers and dietary needs, which can say something about health or religion, so they are shown only to that venue), and a signed copy of the venue's agreement with when it was signed and the internet address and browser it was signed from. For an open day: the name, email address and wedding date each person gives when they sign up or arrive.

A couple who replies "no thanks" hears nothing more about open days or free dates. We never take or hold payments: a deposit is paid on the venue's own page. When a venue's agreement with us ends, its couples' data is deleted within 30 days, as above.

Who we share it with

Only the services we use to run the business: Google and Microsoft (email), Notion (our records of the businesses we contact), Skydo (receiving payments), and our database, hosting and AI providers, which are listed in each client agreement. We never sell personal data.

Transfers outside the UK

We're based in India, and some of our providers are in the United States or the EU. We rely on each provider's own UK transfer terms, and on the ICO's International Data Transfer Agreement with our clients.

Your rights

You can ask to see the data we hold about you, correct it, delete it, or object to our using it. Email hello@closerdesk.me and we'll reply within one month. If you're unhappy with our answer, you can complain to the Information Commissioner's Office at ico.org.uk.