How we use your information

• When you book a walk-through, we keep your name, school, email, what you use for bookings now and the time you chose, so we can hold the walk-through.
• We measure how this site is used ourselves, without cookies, so we can see which pages help schools. We set a cookie that recognises your browser on a later visit only if you say yes to analytics cookies.
• We do not sell your details or pass them to anyone to sell you things.
• If you booked a course with a sailing school that uses Keely, your school decides how your details are used. Section 09 explains.
• If you work for a school that connects Google to Keely, section 10 says exactly what Keely reads from Google, what it sends, how long it keeps it and how to disconnect.

This website is run by Grow Fast Ltd, a company registered in England and Wales with number 16534124. Our registered office is 27 Old Gloucester Street, London WC1N 3AX. Keely is a trading name of Grow Fast Ltd.

For the information you give us on this website, we decide what is collected and why. In data protection law that makes us the controller.

• Walk-through booking: your name, your school's name, your email, what you use for bookings now, and the time you pick. Your phone number and website too, if you give them.
• Where we met: if you came from a code at a show or event, the event's name.
• Emails, chats and messages: your email address, what you wrote to us, and our notes of what we talked about.
• Site measurement: on every visit: the pages you visit and how you use them, the kind of device and browser you use, and your approximate town and network, worked out from your IP address without keeping the address. Not your name. How we measure our website, at the end of this page, sets out exactly what we record.
• Your cookie choice: whether you said yes or no to analytics and advert cookies, and when, kept in your browser so we do not ask you again on every page.

We use your booking details to arrange the walk-through, send you the calendar invite and the reminder, and reply to what you ask. If you ask for a written quote afterwards, we use them for that too. The law calls this our legitimate interest: you asked us to get in touch.

We use site measurement to see which pages help schools and which do not. That is our legitimate interest in understanding and improving our website, and it uses no cookies. The cookie that recognises your browser when you come back is set only with your consent, and you can change your answer at any time from Cookie settings at the bottom of every page. Our cookie policy lists what the site keeps in your browser.

A small number of companies handle information for us: the company that hosts this site, the service that sends our email, the service we use for video calls, and Google for our calendar. They may only use it to do that job for us. Ask us and we will send you the full, dated list.

We measure the site ourselves, on the same servers as the site. No analytics or advertising company receives what you do here.

When a school connects its Google accounts to Keely, Google is also a processor for those features: it provides the data Keely reads and receives what Keely sends, on the school's instruction. Section 10 sets out what that is.

We never sell your details, and we do not give them to anyone so they can sell you something.

We keep your details on servers in the UK or the EEA. Some of the companies we use, Google among them, may handle them in the United States.

When your details leave the UK, the move is covered by the UK–US data bridge or by contract terms approved for UK data. Ask us and we will tell you which one applies.

If your school does not become a customer, we delete your walk-through details two years after we last spoke. If it does, we keep them for as long as your school uses Keely, then follow the deletion timetable in our terms.

We keep site measurement for no more than 25 months, and parts of it for less. How we measure our website, below, gives each period.

You can ask us for a copy of what we hold about you, ask us to correct it or delete it, and object to or limit how we use it. Email hello@keelyapp.com, or write to us at the address in section 11. We reply within one month.

If you are unhappy with how we have handled your information, you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113. We would like the chance to put it right first.

Sailing schools use Keely to run their bookings, forms and records. When you book a course with one of them, the school decides what it collects and why. The school is the controller; we handle your details on its instructions, under a written data processing agreement.

Medical notes are shown only to the school's office and the instructor on your course. Card details are typed into Stripe's payment fields. Neither we nor your school see or store them.

To see, correct or delete what a school holds about you, ask the school first. If you cannot reach them, write to us and we will pass your request on.

This section is for schools that use Keely and the people who work for them. It covers the Google accounts a school, or a person at a school, can choose to connect to Keely. This website itself sends nothing to Google Analytics or Google Ads.

Keely reads nothing from Google until someone signs in with Google and agrees on Google's own permission screen. Each connection asks only for what it needs, and each can be disconnected at any time. When a school connects Google, we handle the data on the school's behalf, under our agreement with the school.

What Keely accesses, and why

Google Analytics, through Connect Google (in Keely: Analytics → Settings). Permission: analytics.readonly, read only.

• What Keely reads: the Google Analytics accounts and properties you can see, so you can pick one. Then, for the property you pick, its purchase report: each purchase's order reference, date and value, and the campaign, channel and source Google Analytics credited it to. To check the property is set up correctly, Keely also reads its attribution settings and whether it is linked to BigQuery. Keely never changes anything in Google Analytics.
• Why: to show the school, order by order, whether Google Analytics and Keely agree about which advert brought each sale (Google vs Keely, on the Ads page and on each order).

Google Ads, through Connect Google (Analytics → Settings). Permission: adwords.

• What Keely reads: the Google Ads accounts you can reach (name, currency and time zone), so you can pick one; campaign, ad group, ad and keyword names, with their daily cost, clicks, impressions and conversions; which campaign, ad and keyword a click came from, so a visit can be tied to its advert; and the account's conversion actions, conversion settings, time zone and upload reports.
• What Keely changes: only for Send sales Google missed. When the school presses Create it for me, Keely creates one conversion action, called “Keely: sales Google missed”. Once the school has switched sending on, Keely lowers or removes the value of a sale it sent if that sale is later refunded. Keely never creates, edits, pauses or deletes campaigns, ads, keywords, budgets or bids.
• Why: to show advertising cost, profit and which adverts bring sales in the school's reports, and to set up and run Send sales Google missed.

Sending sales to Google Ads, through Allow Keely to send sales (Analytics → Settings → Send sales Google missed). Permission: datamanager.

• What Keely sends: the Google Ads sales Google didn't count, then a check on whether Google accepted each one. Each sale carries its order reference, value, currency and time, the Google click reference if the visit had one, and a scrambled (SHA-256 hashed) copy of the customer's email address and phone number. Never their name or address. Keely doesn't read customer lists or audiences from Google.
• When: only for a sale whose customer agreed to marketing cookies, checked again just before it is sent, and only when Google Analytics shows Google didn't already count it.
• Why: so Google Ads can count sales its own tag missed, for the school's own advertising.

Google Calendar, through Connect Google Calendar, which each person at a school can choose to do for their own calendar (in Keely: your account → Calendar). Permissions: calendar.calendarlist.readonly, calendar.freebusy and calendar.events.owned.

• Your calendar list: each calendar's name and time zone, and your access to it, so you can choose which calendars count as busy and which one bookings go in. Nothing inside the calendars.
• Your busy times: for the calendars you tick, only when each busy time starts and ends. Never what the meeting is, who is in it or where it is. Keely checks every 10 minutes, and again at the moment someone books.
• Adding bookings: when someone books time with you on the school's booking page, Keely adds the booking to the calendar you chose (only a calendar you own), moves it if the booking moves and removes it if the booking is cancelled. The entry shows what was booked, the customer's name and email, when and where, any answers they gave when booking, and a link to the booking in Keely. If the school's booking page is set up that way, the customer is added as a guest and the entry carries a video-call link.
• Keeping Keely's entries right: Keely asks Google to tell it when events in that calendar change. It reads only each change's id, status and times, and ignores, without storing it, any change that isn't to one of Keely's own entries, so staff can see in Keely when a booking was moved or deleted in Google. Keely never reads, changes or deletes your other events.
• Busy times only: if you untick the permission to add events on Google's screen, Keely reads your busy times and never writes to your calendar.
• Why: so the school's booking pages never offer a time when you are already busy, and the bookings made with you appear in your own calendar.

How Keely uses it

Keely uses Google user data only to provide and improve the features the school and its staff can see in Keely: the Google vs Keely comparison, advertising cost and profit reports, the How they found you card on each order, alerts about tracking problems, Send sales Google missed, and booking pages that know when staff are busy. We don't use it for anything else.

We do not:

• sell Google user data, or give it to data brokers or information resellers;
• use it to serve, target or measure advertising for anyone other than the school's own Google Ads account, or to build profiles of people;
• use it to decide anyone's creditworthiness or for lending;
• use it to develop, improve or train generalised artificial intelligence or machine learning models;
• combine one school's Google data with another school's, or show it to another school.

Limited Use

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

Who can see it

• People at the school who can see Analytics in Keely see the Google Analytics and Google Ads figures. A person's busy times are used to work out which times to offer. Nobody at the school sees what they are for, because Keely never has that.
• Keely staff, only when the school asks us for help and agrees to it, when we need to look into a security problem or abuse, or when the law requires it. Otherwise our staff don't read it.
• Google, which provides the data and receives what Keely sends to Google Ads and adds to a calendar, on the school's or the person's instruction.
• Our hosting provider, Amazon Web Services, which stores it for us in London and may not use it for anything else.

We don't share Google user data with anyone else, except as part of a merger or sale of our business (with this section still applying, and schools told first), or when the law requires it.

How it's stored and protected

• Google's sign-in tokens are stored encrypted (AES-256-GCM), and are only ever sent to Google.
• Everything passing between Keely and Google, and between your browser and Keely, is encrypted in transit (HTTPS).
• Data is stored on Amazon Web Services servers in London. The nightly backups are encrypted and kept in London too.
• Access to production systems is limited to the few Keely engineers who need it, each with their own account.

How long it's kept, and how to remove it

• Google Analytics: the first read covers the last 60 days. After that, Keely re-reads the last 14 days each morning, and keeps the rows while the property is connected. Disconnect Google (Analytics → Settings) deletes Keely's copy of the Google Analytics rows straight away. Choosing another property deletes the old property's rows.
• Google Ads: Disconnect Google stops Keely reading straight away. Cost and campaign figures already copied stay in the school's reports, because they describe past advertising. They are deleted on the same timetable as the rest of the school's data, as agreed in its contract, or sooner if the school asks.
• Sending sales: Disconnect Google stops sending straight away. On each order Keely keeps a record of what it sent and when: the value, Google's reference for the request, and which kinds of identifier went (for example email and phone), never the identifiers themselves. The Google click reference is deleted as soon as the sale has gone to Google, and in any case within 90 days.
• Google Calendar: busy times are kept from now to 120 days ahead and replaced each time Keely checks, so past ones drop out. Disconnecting (your account → Calendar) deletes your busy times, your calendar list and Keely's copy of the sign-in straight away. You can choose to remove Keely's upcoming bookings from your calendar as well; otherwise they stay as they are and Keely stops updating them. Your bookings stay in Keely. Keely keeps a note of which Google account was connected for 30 days, then deletes it. If you stop working for every school that uses Keely, your calendar is disconnected for you.
• At Google: when you disconnect, Keely asks Google to cancel its access straight away. Google's permission covers every Keely connection made with the same Google account, so if that account is still connected to Keely for something else (another school, or your own calendar), Keely deletes its copy, leaves the others working and tells you. You can remove Keely's access from your Google Account at any time at myaccount.google.com/permissions.
• Backups: each nightly backup is kept for 35 days, and is gone from storage completely within 70 days.
• To ask us to delete any Google data we hold for a school, email hello@keelyapp.com from an address at that school.

When we change this page, we change the date at the top. If a change affects how we use details you have already given us, we email you first. If we change how Keely uses Google user data, we tell schools in Keely before the change takes effect, and ask for permission again where Google's rules require it.

Email: hello@keelyapp.com. Post: Grow Fast Ltd, 27 Old Gloucester Street, London WC1N 3AX.