We use necessary cookies to keep you signed in. If you let us, we would also use analytics cookies, to count visits to our sales page, and marketing cookies, to measure our adverts. You can say no to both and still use everything. What we use.

Cookie settings

Choose which cookies we may use. You can change this at any time from the footer. Read what each one does.

Stayful Academy

Privacy

DRAFT - written by the build assistant, not yet reviewed by a solicitor. Check and complete the items in [square brackets] before launch.

Last updated: [LAST UPDATED DATE]

This notice explains what personal information Stayful Academy collects about you, why, who handles it for us, how long we keep it and what your rights are.

1. Who is responsible for your information

Stayful Academy is run by Stayful Ltd (company number 14791583), 20-22 Wenlock Road, London, England, N1 7GU. We decide how and why your personal information is used, which makes us the "data controller".

We are registered with the Information Commissioner's Office (ICO) under number ZA00016946040. For anything about your information, email info@stayful.co.uk.

2. What we collect

  • Your name and email address. Your email comes from your payment. Your name is there only if you add it to your account.
  • Your purchase record. What you bought, when, the amount, whether it was later refunded or disputed, and the reference numbers our payment provider gives us for the payment.
  • Your lesson progress. Which lessons you have completed and when.
  • Sign-in records. The time of each sign-in, the browser and device type your browser reports, and a scrambled ("hashed") marker made from your network address. We store the marker, not the address itself. We use these records to detect account sharing.
  • Your marketing preference. Whether you have said yes or no to marketing emails.
  • Account history. A note of changes made to your account by us, such as access being given or removed.
  • Messages you send us. For example, an email asking for help or a refund.

3. What we do not hold

We do not hold your card details. Your card number and billing address are typed into our payment provider's checkout page and stay with them. We receive only confirmation that you paid.

4. Why we use it, and what allows us to

  • To provide what you bought. We need your email, purchase record and progress to give you access, sign you in, show you where you are in a course, and answer you when you contact us. We do this because it is necessary for our contract with you.
  • To meet our tax and accounting duties. We keep records of sales because the law requires us to.
  • To keep the service secure and prevent account sharing. We use sign-in records for this. We do it because we have a legitimate interest in protecting the academy and the members who have paid for it. A person reviews any sign that an account is shared before we act on it. Nothing is decided by a computer alone.
  • Marketing, only if you opt in. We send marketing emails only if you have agreed to them. You can opt out at any time on your Account page, and opting out does not affect your access.

We do not sell your information. We do not use it for advertising, with one exception you control: if you accept marketing cookies on our public sales page, Meta is told that you visited that page (see "Cookies and tracking").

5. Who handles information for us

We use the companies below to run the academy. They handle your information on our behalf and for the jobs listed. We may change a provider in future. If we do, we will update this list.

  • Payments - Stripe. Stripe takes your card payment and holds your card and billing details.
  • Database and sign-in - Supabase. Supabase stores your account, purchase record and lesson progress, and checks your sign-in codes. The database is hosted in the EU (Ireland).
  • Website hosting - Vercel. Vercel runs this website, so it handles each request your browser makes.
  • Email sending - Resend. Resend delivers the emails we send you, such as your welcome email and sign-in codes.
  • Video hosting - Bunny. Bunny stores and plays the lesson videos, so it handles your browser's requests for video.

Some of these providers may process information outside the UK. Where they do, appropriate safeguards are in place to protect it. [OWNER TO CONFIRM WITH EACH PROVIDER'S TERMS]

We may also share information where the law requires it, or with our professional advisers such as our accountant.

6. How long we keep it

  • Your account, lesson progress and sign-in records: until you delete your account. [OWNER TO CONFIRM: whether older sign-in records should be removed sooner]
  • Records of sales: kept for [6 years - OWNER/ACCOUNTANT TO CONFIRM] for tax purposes. If you delete your account, the sale record is kept in anonymised form: the amount, date and payment reference stay, and your name and email are removed from it.
  • Messages you send us: for as long as we need them to deal with your request and to keep a record of what was agreed.
  • Account history: if you delete your account, we keep a note that an account was deleted, without your name or email address.

7. Your rights and how to use them

You have the right to:

  • see the information we hold about you (access);
  • have it corrected if it is wrong (correction);
  • have it deleted (deletion);
  • ask us to limit how we use it (restriction);
  • object to us using it (objection);
  • receive it in a form you can take elsewhere (portability);
  • withdraw your consent, where we rely on consent, such as for marketing.

How to use them here:

  • Download your data: sign in and use the download option on your Account page.
  • Delete your account: sign in and use the delete option on your Account page. This removes your profile, progress, access and sign-in records straight away and cannot be undone.
  • Correct your name or change your marketing choice: on your Account page.
  • Anything else: email info@stayful.co.uk.

Some of these rights apply only in certain situations. If we cannot do what you ask, we will explain why.

8. Cookies and tracking

[DRAFT - generated from what the site really sets and loads. The owner and a solicitor must review the wording before launch.]

When you first visit a public page you are asked about cookies. Necessary cookies are always on. Analytics and marketing ones are off until you say yes, and only on our public sales page. Rejecting them is as easy as accepting them, and you can change your mind at any time with "Cookie settings" in the footer of any public page. If you are signed in, we load no analytics or marketing tracker at all.

Necessary (always on)

These make the site work. You cannot switch them off.

  • Sign-in cookie (sb-...-auth-token). Keeps you signed in. Without it the member area cannot work. The site's own page scripts can read it (our sign-in provider's library does not hide it from them). Set by us (through our sign-in provider, Supabase). Lasts: your browser keeps it for up to about thirteen months from when it was last renewed; it is renewed regularly (about once an hour) while you are using the site, and it is removed when you sign out. How long a sign-in stays valid is set by our sign-in provider, Supabase: see the sign-in length note below. Where: every page, once you have signed in.
  • Sign-in code-check cookies (sb-...-auth-token-code-verifier, sb-...-auth-token-flow-...-code-verifier, sb-...-auth-token-flows-code-verifier). Used while you sign in with an emailed code: a random value that lets the sign-in provider check that the sign-in finishes in the same browser it started in. Set as soon as you ask for a code, even if you then do not sign in. Set by us (through our sign-in provider, Supabase). Lasts: your browser keeps them for up to about thirteen months; they stay when you sign in and are removed when you sign out. Where: every page, once you have asked for a sign-in code.
  • Preview cookie (stayful_preview). Only for the site's administrator: remembers that they are looking at the site as a member would see it. Set by us. Lasts: 8 hours. Where: only for an administrator who switches the preview on.
  • Your cookie choice (stayful_consent). Remembers which kinds of cookie you accepted or rejected, so we do not ask on every page. Set by us. Lasts: about six months. Where: every page, once you have made a choice.
  • Error reports. When a page breaks, your browser sends us the error message, the address of the page without anything after a question mark, and where in the code it happened. Nothing you typed is added. As with every request your browser makes to this site, it attaches this site's own cookies (including the sign-in cookie, if you are signed in) to that request; the site ignores them for error reports and does not read, store or pass them on. Email addresses, long codes and anything after a question mark are removed automatically, but an error message can still hold words from the page, so reports are read only by the site's administrator and are never emailed. Set by us. Where: only when something breaks.
  • Lesson video players. Plays a lesson video for a signed-in member. It loads inside the lesson page, not on the public pages. Set by our video host (Bunny Stream, player.mediadelivery.net). Where: lesson pages for signed-in members, when the lesson has a video.

Analytics (off unless you accept)

These count visits so we can see how many people look at the sales page.

  • Page analytics (Vercel Web Analytics). Counts visits to the public sales page. It sets no cookie. Set by our hosting company (Vercel); the script is served from our own web address. Where: the public sales page only, only if you accepted analytics, only if it is switched on, never when you are signed in.

Marketing (off unless you accept)

These tell an advertising company that someone looked at the sales page.

  • Meta (Facebook) pixel. Tells Meta that a visitor looked at the sales page, so our adverts can be measured. Meta sets a cookie called _fbp (and may set _fbc when a visitor arrives from one of our adverts) that lasts up to about three months. Set by Meta Platforms, from connect.facebook.net. Lasts: up to about three months (_fbp, _fbc). Where: the public sales page only, only if you accepted marketing, only if a pixel ID is set, never when you are signed in.

How long a sign-in lasts. The sign-in cookie is set by our sign-in provider (Supabase) and your browser keeps it for up to about thirteen months from when it was last renewed. It is renewed regularly (about once an hour) while you are using the site; signing out removes it. The site itself sets no shorter limit. Any limit on how long a sign-in stays valid after you stop using the site is a setting of our sign-in provider. [OWNER TO CONFIRM: how long a sign-in should stay valid. The sign-in cookie is kept by the browser for up to about thirteen months and renewed regularly (about once an hour) while you are using the site, and the site sets no shorter limit of its own; any inactivity limit is a session setting in our sign-in provider's dashboard, which the site cannot read. Decide whether to set one, then say the real length here.]

[OWNER TO CONFIRM: whether the sales page tracking switches in Admin are on at launch. Until you switch them on and add a pixel ID, nothing in the analytics and marketing groups loads for anyone.]

This list is made from the same list the site checks itself against, so it changes when the site does.

[OWNER TO CONFIRM: if any lesson video is ever placed on YouTube or Vimeo instead of our video host, those services may set their own cookies - say so here, or do not use them]

9. Complaints

If you are unhappy with how we have used your information, please contact us first at info@stayful.co.uk so we can try to put it right. You also have the right to complain to the Information Commissioner's Office (ICO), the UK's data protection regulator, at ico.org.uk.

10. Changes to this notice

We will update this notice when what we collect, or who handles it for us, changes. The current version is always on this page, with the date it was last updated at the top. If a change is significant, we will email members.

Back to the home page