CueStrideSign up free

Privacy policy

In force from 27 September 2026; this version from 15 November 2026, 10:49 UTC.

Who we are

CueStride is operated by Handz LTD, a company registered in Israel, at Jerusalem 14, Givat Shmuel, Israel. This policy covers this site, cuestride.com, and the app at app.cuestride.com. We decide how the personal data described here is used, except where this policy says a partner decides with us or on its own. Our Chief Security Officer is in charge of protecting personal information at Handz LTD. Questions and requests about this policy or your data go to them at privacy@cuestride.com.

In short

  • Screens need no account: a room's viewer link is all a screen needs. Screens, including this site's timers, carry no analytics and no advertising.
  • We use personal data to run CueStride, to learn how it is used, to advertise it, and, if you ask for it, to email you about it.
  • Where we ask for your agreement first, which we always do where the law requires it, analytics and advertising cookies, and our own count of visits to this site, are used only after you give it; elsewhere they are on until you turn them off. The places where we ask first are listed under Cookies and browser storage. Our banner tells you which of these applies where you are, and you can change your choice at any time with "Cookie settings", at the bottom of every page of this site and under "Privacy" in the app.
  • We do not sell personal data for money. Some US state laws count our advertising as "selling" or "sharing" personal data: you can opt out with "Your privacy choices", and we honour Global Privacy Control.
  • Marketing email goes only to people who asked for it, and every one has a link to unsubscribe.
  • Payments are handled by Paddle, and card details never reach our servers.
  • CueStride's servers are in the United States.

What we collect, and why

If you have an account. When you sign in, our sign-in provider, WorkOS, gives us your name, your email address, and the organization and role you belong to. We keep them, with the time of your last sign-in, to run your account. When an admin invites someone, the invitee's email address and role go to WorkOS, which sends the invitation. An organization's name, plan, and branding (its logo, whether the CueStride wordmark shows, and its screen theme) are kept with the account. The logo is published at a public address so the organization's screens can show it. An event's sponsors, as an admin enters them (each one's name, website, logo, and slides), are kept with the event; the images are published at public addresses, and the names are shown on the event's sponsor screens, so those screens can show them. Deleting the event deletes its sponsors and the images only it uses; an image another of the organization's events still uses stays while it is used. An image nothing uses any more is deleted a day later. An organization's speakers, as an admin enters them, are kept with the account: each one's name, and nothing else about the person but the card and the photo described below. The list lets the organization's rooms name the same speaker on their sessions. An admin can delete a speaker at any time, on any plan, and the list is deleted with the account. Each speaker also has a page of their own, at a private address that an admin copies and sends them. It shows the speaker's name and their sessions, each with its room, the room's event, and when it is on; to work that out, the page also receives the times of the room's other sessions those days, without their names or speakers. The address is kept with the speaker, so admins can copy it again, and making a new one ends the old one. A speaker's page carries no analytics and no advertising, and its address is not written to our logs. A speaker may add their own photo on their page; an admin cannot add one. Sending it is the speaker's consent, given on that page in a sentence that names the organization, to its showing next to their name wherever the organization lists their sessions: on its agendas, which anyone with the link can see, on attendees' phones, and on the crew's screens. Anyone who has seen it can keep a copy. We keep the photo with the speaker, with when that consent was given and the wording it was given to. The speaker's browser shrinks the photo and writes it again before it is sent, and our server takes it only without its metadata, such as where it was taken. The speaker can remove it on their page at any time, and so can an admin of the organization, on any plan: it is then deleted from our database at once, stops showing within five minutes, and leaves our backups within 30 days. It is deleted with the speaker and with the account. Each speaker may also have a card for whoever introduces them: an intro line, how to say their name, their pronouns, and whether they take questions, each line optional. An admin of the organization can write it, and the speaker can correct it on their page, which says above the card who sees it. We keep it with the speaker, with which of the two saved it last and when. The organization's moderator and operator pages show all of it, and so does the speaker's page; the room's backstage screen, which anyone with the room's screen link can open, and the event's, which anyone with the event's screen link can open, show only how to say the name and the pronouns. The speaker or an admin can clear any line at any time, on any plan: it is then deleted from our database at once and leaves our backups within 30 days. The card is deleted with the speaker and with the account. It never goes to our analytics or advertising partners, an API key cannot read it, and it is not written to our logs.

Billing. We keep the plan, its add-ons, the state of the subscription, each event pass bought with the plan the account had before it, so that a refund can undo it, and Paddle's ids for the customer, the subscription, and each pass's payment. Paddle is the merchant of record: it takes the payment and keeps the card, the billing address, and the invoice under its own privacy policy. We keep no card details. At checkout the admin's email address is passed to Paddle.

What you put into a room. The room's name, its timers, speakers, notes, labels, and messages, and the names and programme of an event. This can include other people's names, such as a speaker's. The people who hold a room's links see it: a screen sees the room's name, its timers, speakers, labels, and the messages on show, but never the notes; a controller sees everything. Where a session's speakers were picked from the organization's list, a screen also receives the random id our server gave each of them, which names no one by itself, and a backstage screen also receives each one's name, how to say it, and their pronouns, when their card holds them. A room also takes the time zone of the browser that created it. When an organization uses CueStride, it decides what goes into its rooms, and for that content we act on its behalf, as our terms describe. Room content never goes to our analytics or advertising partners.

Screens. A browser that opens a room keeps a random id, so the room's controller can tell its screens apart, rename them, and ask one to reload, flip, or go fullscreen. The id belongs to the browser, not to a person, unless someone names the screen; a name given to a screen is kept with the room. While a screen or controller is connected, the room's controllers see the list of connections, with the name of each signed-in member.

Paired screens. A TV or other display can be paired to an organization's account, by a code it shows, and then switched from the account's Screens tab. A paired screen keeps a random credential in a cookie (see Cookies and browser storage), of which we keep only a hash, with the name an admin gives the screen, what it shows, and when it was last connected. A paired screen belongs to the organization, not to a person; its record is deleted when it is unpaired or the account is deleted. A screen already open from a room's or an event's link can also be paired, when an admin chooses Pair for it in the Screens tab; if an admin denies it instead, we keep its browser's random id with the organization, so that browser is not offered again.

API keys. An organization's admins can make API keys, so that their own tools, such as a Stream Deck or a script, can read and run the organization's rooms. A key belongs to the organization, not to a person, and is kept with it. For each key we keep a hash of its secret, never the secret itself, and its last four characters, so admins can tell their keys apart; the label an admin gives it; the rooms it may reach and what it may do; whether it may be used in links; its expiry, if it has one; the member who made it; when it was made; when it was revoked; while its secret is being replaced, a hash of the old secret and when that stops working; when it was last used, to the hour; how many requests it made that day, by the UTC calendar; and the name at the start of the user agent of the program that last used it: its letters, digits, dots, hyphens, and underscores up to the first other character, such as curl from curl/8.4.0, or nothing when that name is longer than 24 characters or starts with csk_, in capital letters or not, as a key's secret does, and nothing else of the user agent. A later request whose user agent starts with no such name clears it. We keep that name only so admins can tell which program is using a key: they see it in the key's row in Account settings, with when the key was last used and its requests that day. When the member who made a key is deleted, the key keeps working and no longer names its maker. A key's record holds no IP address. While a key's stream is connected to a room, the room's controllers see it in Live connections, by the key's label, with the last command it sent, and our server holds the caller's IP address in memory for its limits on streams; it does the same for a refused request with a revoked or expired key, as for any request its limits count (see How long we keep it). Our server's log notes when a key is made, replaced, revoked, or turned off by a downgrade, by the key's id and the organization's; when all of an organization's keys are revoked at once, by the organization's id and how many; and each command or change a key sends, by its route and result, never with the key or an IP address.

CueStride in ChatGPT. If you use CueStride inside ChatGPT, ChatGPT sends us what the timer needs: a name for the timer, which ChatGPT writes from your conversation, its length and warning time, and the commands you give it, such as pause or add time, which may name the timer they are for. We keep the name with the timer, and anyone with its viewer link sees it, so don't ask for a name you wouldn't want its viewers to see. When ChatGPT asks us to create, check, or change a timer, OpenAI also sends an identifier it makes for you, which does not tell us who you are, and an anonymized id for the conversation. We use your identifier to keep each ChatGPT user within our limits on requests and new timers. For that, we keep it only in our server's memory, in scrambled (hashed) form, while one of those limits still counts it, which can be up to an hour for new timers, and drop it at our next clean-up after that, or when our server restarts, and we give it to no one. We also use the two ids together, so that a timer can be found again from the conversation that made it. When a timer is created in a conversation, we keep one scrambled form of both ids (a keyed hash) with the timer, which cannot be turned back into either id. We keep it only so that later requests from the same conversation, by the same ChatGPT user, can find and control that timer. We never keep either id itself, and we log neither the ids nor their scrambled forms. The keyed hash is deleted with the timer's room. ChatGPT may also send an anonymized id for your ChatGPT organization if there is one, your language and region setting, a description of the ChatGPT app or browser and the device you use (its user agent), and a rough location (city, region, country, time zone, and coordinates). We do not use, keep, or log any of them. Apart from these ids, we receive nothing from your ChatGPT account, such as your name or email. Like all traffic to CueStride, ChatGPT's requests pass through Cloudflare (see Who else handles data).

The timer's panel in ChatGPT runs on your device and connects to our server directly, to follow the timer and keep its clock right. So we also receive your IP address, as on any visit, and use and keep it only as "Your address and our logs" describes. We also receive what your browser or the ChatGPT app sends with every request, such as its user agent and language, which we do not use, keep, or log. Directly from our server, the panel also receives the room as every viewer screen does, including its timers, with each one's speaker and labels if they are set, but never its notes, and any message the room is showing to its viewers. The panel displays none of the speakers, labels, or messages, and none of them is in the results ChatGPT's model reads or in what the panel gives the model to read.

In the results ChatGPT's model reads, and in what the timer's panel gives the model to read, we send only the timer's name, whether it is running, the time left or the time past zero, its length, and the viewer link. A result may also include a one-line status, such as "Timer started.", or a short message, for example saying why a request failed, which may name the conversation's timers. A name given in the app to a timer or a room you use with ChatGPT can reach ChatGPT too, so don't give one you wouldn't want in your ChatGPT conversation. Through ChatGPT, the timer's panel also receives what it needs to show and run the timer: the room's name; its timers, with the ids we give them and each one's name, length, and countdown settings, but never its speaker, labels, or notes; which timer is loaded, whether it is running, and when it was started, paused, or will reach zero; our server's time; a revision number; and a reference that lets the panel control the timer, which works for whoever has it, until it is revoked. When a timer is created, we also send the panel a controller link for the person who set it up, which lets them run the room. The panel shows it as a button. The panel asks ChatGPT to keep the reference with the conversation, in a part ChatGPT does not show the model, so that the panel can resume the timer when it is shown again, and its controls send the reference to us through ChatGPT. We don't include the reference or the controller link in the results ChatGPT's model reads, but what we send the panel through ChatGPT, and what its controls send us, passes through OpenAI's systems. The results ChatGPT's model reads become part of your ChatGPT conversation; whether OpenAI keeps what we send the panel, or the reference the panel asks it to keep, with the conversation is up to OpenAI. If you share the conversation, the people you share it with may see this information too. Only the requests ChatGPT's model makes are tied to the conversation and to you, so someone else who continues a copy of the conversation in their own ChatGPT account cannot control the timer by asking ChatGPT. The panel's controls work with the reference instead, so anyone who has it, for example from a copy of the conversation that keeps it, can control the timer until the link labelled "chatgpt" is revoked. The controller link, if OpenAI keeps it, gives full control of the room. To cut off anyone who may have them, revoke the links labelled "chatgpt" and "controller" under Links. If you use that controller link yourself, create a new one first. What OpenAI does with your conversation is covered by OpenAI's privacy policy.

A timer you create in ChatGPT is a room without an account, kept and deleted as this policy describes for such rooms. Anyone you give its viewer link can watch it. When the timer is made, its panel also offers its controller link, which gives full control of the room. With that link you can cut ChatGPT off from the timer, by revoking the link labelled "chatgpt", or delete the timer. If you use it to add the timer to a CueStride account, the timer is kept like that account's other rooms, and ChatGPT can still start, pause, and reset it, and add or take away time, until you cut it off. The panel's links open our app, where this policy applies as it does to any visit.

How CueStride is used. With our analytics provider, PostHog, we record how the app is used, on its pages where you set up and run rooms and manage your account (the app's home page, a new room, the dashboard, Screens, Speakers, Sponsors, Account settings, and a room's controller and moderator pages). PostHog does not run on this site. We record which of those pages are viewed, and the actions you take there to run a show: today, creating a room, creating a timer, starting, pausing, or resetting a timer, and copying a screen's link. In a room made from our site's Try it live button, we also record each of the first steps its controller lists, once, as you do it: opening a screen, starting the timer, showing the message, and moving to the next timer. We may add more actions of the same kind, such as editing a timer, and we add each to this list in the next version of this policy. We may also count, from the room's controller page, how many screens are connected to a room, as a single number; the screens themselves still carry no analytics. We do not record clicks, scrolling, or errors on their own, and we make no recordings of your screen.

With each, your browser sends PostHog the address of the page, without the secret part of a room's link and without any query but campaign tags (such as utm_source), so never the id of an ad you clicked; the page that linked to it, cleaned the same way; your browser's user-agent string and, from it, the browser, its version, the operating system, and the device type and model; the browser's language; the screen and window size; the time zone; and random ids for your browser and your visit. It never sends the page's title, which can contain a room's name. Your browser sends this directly to PostHog in the United States, not through our servers, and PostHog works out an approximate location (such as country, region, city, and postal code) from your IP address and then discards the address, as we have set it to do. PostHog keeps its ids in your browser (see Cookies and browser storage), so that it can tell your visits apart and see which visits led to a sign-up. It reads no advertising cookie and records no advertising id, whatever your advertising choice. When you are signed in, we give PostHog your account's id and your organization's id, and PostHog keeps a profile of your account with the details above; it keeps profiles only for accounts. When you sign out, or your session ends without the Sign out button, later visits on that browser are not added to your account's profile: the id PostHog linked to your account is deleted or replaced before PostHog records anyone else's visit there. If your browser sends Do Not Track or Global Privacy Control, PostHog does not load at all. We never record what a room contains or what you type, and we send PostHog no name or email address. Screens are never measured: a room's viewer, agenda, and board, an event's agenda, any page that embeds them, and this site's timers; nor is a speaker's own page.

Counting visits to this site. Cloudflare, which carries all traffic to CueStride, also counts visits to this site's pages with its Web Analytics, except for visitors in the European Union. A small script from Cloudflare runs on each page of this site, other than its timers, and reports to Cloudflare the address of the page, without any query in it; the page that linked to it; the country you are visiting from; your browser, operating system, and device type; and how quickly the page loaded. It sets no cookie and keeps nothing on your device. Cloudflare shows us only totals, such as the number of visits and page views by page, country, or browser, never a single visit or your IP address. It does not run in the app, so no screen is ever counted.

We also count visits to this site's pages ourselves, with Counterscale, open-source software that we run on Cloudflare's network, so that we can see which sites and campaigns bring visitors here. It follows your analytics choice: where we ask for your agreement first, it counts a page only once you have given it, starting with the page where you give it; elsewhere it counts each page you open until you turn analytics off. A page your browser loads ahead of time is counted only once you open it, and one your browser kept in memory and shows again when you go back to it is not counted again. It never runs if your browser sends Do Not Track or Global Privacy Control, and never on this site's timers, on a timer embedded in another site, or in the app. For each page it counts, your browser sends our Counterscale the address of the page, without any query or the part after "#"; the address of the page that linked to it, if that page is on another site, without any query, or, if there is none, a source named in the page's own address: the value of the first of ref, referer, referrer, source, and utm_source that the address has, cut at any "?" and left out if it holds this site's address, such as newsletter from utm_source=newsletter, which is whatever the link to the page carried and can be any text; the campaign tags in the page's address (utm_source, utm_medium, utm_campaign, utm_term, and utm_content); and whether this is your browser's first, second, or a later page counted on this site that day. Nothing else from the page's query is sent. Cloudflare adds the country you are visiting from, which it works out from your IP address, and Counterscale records your browser's user-agent string and, from it, the browser, its version, and the device type and model. Counterscale does not record your IP address, sets no cookie, and keeps nothing in your browser's storage; to tell a first page of the day from a later one, it relies on your browser's ordinary cache (see Cookies and browser storage). Its dashboard shows us numbers, such as page views and visitors by page, linking site, campaign, country, browser, or device, not a list of visits; how long the records behind them are kept is under How long we keep it.

The page you signed up from. When you sign up from a page of this site, and your analytics choice allows it, your account keeps which page that was. We use it to learn which of our pages help people start. It is the page's address only, with no query. Your browser carries it to the app in a cookie while you sign in (see Cookies and browser storage). Our server then holds it in memory only, for up to a day, until your analytics choice in the app is known. Where we ask first, that is when you agree; elsewhere, it is when our banner has told you about analytics. It is never kept if you turn analytics off, or if your browser sends Do Not Track or Global Privacy Control. It is kept with your account and deleted with it.

Advertising. To advertise CueStride and measure our ads, we use two advertising platforms: Google Ads, and Meta's ads (on Facebook, Instagram, and Meta's other services). Each has a tag (a small piece of code) on this site, and our server sends each conversion reports. We add a platform to this list before we use it and, where your agreement is required, ask again before any data goes to it. No advertising runs in the European Economic Area (the EU, Iceland, Liechtenstein, and Norway), the United Kingdom, Gibraltar, Guernsey, Jersey, the Isle of Man, Switzerland, and Quebec, or wherever we cannot tell where you are, whatever you choose. Elsewhere, Google's tag runs on this site, cuestride.com, except its timers, and never in the app, unless you turn advertising off or your browser sends Global Privacy Control. It sets and reads cookies and identifiers on your device, among them the id of the Google ad you clicked, if any. It sends Google the address of each page you view here, the page that linked to it, your IP address, your browser's and device's details (such as its language and screen size), the time, the ad you clicked, if any, and that you clicked a "Sign up free" link, if you do.

When you sign up, or buy for the first time, after clicking a Google ad, our server reports it to Google through its conversion service, if your advertising choice for your account, and in the browser you used, allows it: what happened (a sign-up, or a purchase with the amount paid and its currency; a sign-up carries no amount), when, the id of the ad click your browser kept from this site, an id for the report (for a purchase, the payment's id at Paddle; for a sign-up, a scrambled form of your account's id), and your email address in hashed form (scrambled, so that it cannot be read back). Google can use a hashed email to match a report to an account it already knows, but our Google Ads account has that matching (enhanced conversions) turned off, so the ad click's id is what ties the report to the ad. It sends no IP address or browser details, and we keep none of it. Renewals are not reported. We do not give Google, or any advertising platform, lists of our customers or subscribers. Google uses this to show you our ads on its services and elsewhere, based on your visit here, and to measure which ads lead to visits, sign-ups, and purchases. It may link your visit to the other devices on which you use its services.

For what Google's tag collects on this site, and for our conversion reports, Google and we are joint controllers in Europe. Under our arrangement with it, we are responsible for telling you about it (this policy) and for asking your agreement where it is required; Google is responsible for what it does with the data once it has it, under its own privacy policy (listed under Who else handles data), and for answering requests about that data. You can use your rights with us or with Google. You can also limit Google's ads in your settings with it, and through aboutads.info/choices in the United States and youronlinechoices.eu in Europe. Google explains how it uses data from sites that use its services at business.safety.google/privacy, and you can manage its ads in Google's Ads Settings.

Meta's tag, the Meta pixel, runs in the same places as Google's tag and under the same choice: on this site, except its timers, never in the app, never in the places where we ask first, and not once you turn advertising off or while your browser sends Global Privacy Control. It sets and reads cookies on your device, among them an id for your browser and the id of the Meta ad you clicked, if any. It sends Meta the address of each page you view here, the page that linked to it, your IP address, your browser's and device's details, the time, its cookies' ids, and that you clicked a "Sign up free" link, if you do. We have turned off its automatic events and its automatic advanced matching, so it does not read the buttons you press or anything you type on this site.

When you sign up, or buy for the first time, after clicking a Meta ad, our server reports it to Meta through its Conversions API, under the same conditions as our reports to Google: what happened (a sign-up, or a purchase with the amount paid and its currency), when, the id of the ad click the Meta pixel kept on this site, and its id for your browser when it kept one, your browser's details as it describes itself (its user agent), the app's address, an id for the report (for a purchase, the payment's id at Paddle; for a sign-up, a scrambled form of your account's id, the same id a report to Google for it would carry), and your email address in hashed form. If your browser also kept a Google ad click, the same sign-up or purchase is reported to Google too, as described above. Meta can use the hashed email to match the report to a Facebook or Instagram account it already knows. It sends no IP address, and we keep none of it. Renewals are not reported. Meta uses this to show you our ads on its services, based on your visit here, and to measure which ads lead to visits, sign-ups, and purchases.

For what the Meta pixel collects on this site and for our reports to Meta, Meta and we are joint controllers in Europe for collecting the data and sending it to Meta, under Meta's controller addendum; Meta alone decides what it does with the data once it has it, under its own privacy policy (listed under Who else handles data), and answers requests about that data. You can use your rights with us or with Meta. You can see and disconnect what sites send Meta in your activity off Meta technologies, and manage Meta's ads in its ad preferences.

Emails. Service emails go to everyone with an account: sign-in codes and invitations (sent by WorkOS), receipts and other emails about a payment, such as a failed renewal (sent by Paddle), and messages about your account, your plan, and changes to our terms or this policy (sent by Brevo, without tracking of opens or clicks). As of the date of this version, we do not use Brevo yet: we send no marketing email, this site has no form to subscribe, and CueStride sends you no email of its own; a message about your account or a change to our terms or this policy is one we write to you by hand. The only emails our own server sends are the alerts to us described below, and they never go to you. What this policy says about Brevo applies from when we start using it, and we will update this page before then.

Alerts to us. When a payment needs our attention, for example a refund Paddle could not complete, our server emails us about it. Each alert has the account's internal ID, the subscription's ID if there is one, and a note on what needs doing. Depending on the alert, it can also have the payment's ID, the plan before and after a change (as price IDs), the renewal or paid-until date, and a short reason. Nothing else about you is included, never your name or email address. These emails are sent through Resend and go only to our own inbox, never to you.

Marketing email (news, tips, and offers about CueStride) goes only to people who asked for it: by ticking a box, never ticked in advance, after the first sign-in or in your profile in the app, or by subscribing on this site and confirming by email. The form on this site sends your address to our server, which passes it to Brevo. For marketing email we keep your email address, your name, when and where you subscribed, and whether you are subscribed. Brevo records when each email is delivered. A second box, also never ticked in advance, lets us see when you open our marketing email and which of its links you click, with the IP address and device of the open or click; without it, our marketing email to you carries no open or click tracking. Every marketing email says who sends it and how to reach us, and has a link to unsubscribe, a link to stop the tracking, and a link to stop us giving your address to the advertising platforms, which holds for every record we have under that address until you allow it again.

The unsubscribe link in a marketing email stops marketing email until you subscribe again; it does not stop service emails. Many mail apps also show an unsubscribe button on our service emails. If you use it, or mark one of those emails as spam, Brevo stops sending you our messages about your account, your plan, and changes to our terms or this policy, until you ask us to start them again.

Naming customers. As our terms allow, we may name an organization as a CueStride customer and show its logo. We never publish a person's name this way.

Your address and our logs. Your IP address is used to apply limits that protect the service from abuse. It is held only in the server's memory, while your connection is open or a limit still counts it, and forgotten at our next clean-up after that, or when our server restarts; it is never written to our database or our logs. PostHog and the advertising platforms receive it, as described above, when your choices allow it; PostHog discards it once it has worked out the location, as we have set it to do. Our own count of visits to this site receives it as any request to Cloudflare does, and records only the country Cloudflare works out from it, never the address. Our logs record each request's method, path, status, and duration, and account events such as a sign-in with the account's id. They hold no IP addresses and none of the secrets in links.

No law requires you to give us personal data. Without an email address you cannot have an account; without your agreement we send you no marketing email and, where the law requires your agreement, use no analytics or advertising cookies and do not count your visits to this site ourselves.

Why we may use it

  • To provide what you signed up for or asked for: your account, your rooms (including timers you make in ChatGPT, and the keyed hash of ChatGPT's ids for you and the conversation, which lets you find and control them from that conversation), your organization's API keys (each key, its label, its rooms and rights, its expiry, and the member who made it), your plan and its billing, and the service emails that come with them.
  • Our legitimate interest in keeping CueStride secure and running: the limits against abuse (including the ChatGPT identifier, and the IP address our server holds in memory for an API key's stream), our logs, and our backups. This includes what an API key records of its use (when it was last used, its requests that day, and the program that last used it), which admins see in the key's row so they can spot a key that is misused or stolen, and what our server's log notes about keys, which we use to find misuse.
  • Analytics (our analytics with PostHog in the app, our own count of visits to this site with Counterscale, and the page of this site you signed up from): your consent where we ask for it first, which we always do where the law requires it; elsewhere, our legitimate interest in understanding how CueStride is used or, where the law there relies on consent instead, your consent given by leaving it on after our banner tells you about it, which you can withdraw at any time with "Cookie settings".
  • Advertising (Google's tag, the Meta pixel, and their cookies on this site, and the conversions we report to Google and Meta): none in the places where we ask first, since it never runs there, whatever you choose; elsewhere, where it runs until you turn it off, our legitimate interest in advertising CueStride or, where the law there relies on consent instead, your consent given by leaving it on after our banner tells you about it, which you can withdraw at any time with "Cookie settings" or Global Privacy Control.
  • Counting visits to this site with Cloudflare's Web Analytics, which uses no cookie and does not run for visitors in the European Union: our legitimate interest in knowing which of this site's pages are visited and how quickly they load.
  • Marketing email, and tracking its opens and clicks: your consent, each asked for separately.
  • Our legitimate interest in showing which organizations use CueStride: naming customers.
  • Our legal obligations, such as keeping accounting records and being able to show the consents you gave us.

We make no decision about you that has legal or similarly significant effects by automated means alone. The advertising platforms do use data about you to choose which ads to show you, which is a form of profiling; you can refuse it as described under Your rights. We do not use personal data to train language models, and we do not sell it for that.

Cookies and browser storage

The app, at app.cuestride.com, sets these cookies it needs to work. All are HttpOnly and SameSite=Lax, and Secure over https:

  • __Host-cs_session keeps you signed in, for 30 days, renewed while you use the app.
  • __Host-cs_state and __Host-cs_redirect protect a sign-in and remember where it returns, for 10 minutes.
  • cs_pass_ followed by a room's id lets a screen into a room with a password, for 30 days, and stops working when the password changes.
  • __Host-cs_screen keeps a TV or display paired to an organization's account, for a year, renewed while the screen is in use; before pairing, it ties the screen to the code it shows. Unpairing the screen ends it.

The app also keeps these in your browser's storage, on your device only: the screen's random id (cuestride.device); the rooms you made without an account, with their controller links (cuestride-device-rooms); your choices of theme, sound, and screen flip (cuestride-theme, cuestride.sound, and cuestride.viewer.flip); on a new room's controller, which of its first steps you have done there and whether you hid them (cuestride.start.and the room's id); on a paired screen, what it last showed, so it shows it again at once after a power cut (cuestride.screen); and, on an event's attendee page, a random id our server gave your phone, so the page counts it once among the people reading it (cuestride.attendee).

A cookie on cuestride.com and the app, cs_consent, keeps the choices you make, for up to a year, and our server records each one. Where you have not chosen, the default for the place you are visiting from applies each time, and is not kept; for your account, it follows where your latest visit while signed in came from (the country, and in Canada the province, where they can be told), which we keep with the account to apply that default, including to the conversions we report to Google and Meta. We ask for your agreement first in the European Economic Area (the EU, Iceland, Liechtenstein, and Norway), the United Kingdom, Gibraltar, Guernsey, Jersey, the Isle of Man, Switzerland, and Quebec, and wherever we cannot tell where you are, including Canada when we cannot tell the province; we always do where the law requires it. There, analytics is used only once you give it, and advertising is not used at all; elsewhere, both are used until you turn them off:

  • Analytics, in the app only: PostHog's cookie, named ph_<project key>_posthog, on the cuestride.com domain, for up to a year, holding random ids for your browser and your visit, your account's id once you sign in on that browser, and the addresses of the first app page you opened there and of the page that linked to it, without the part after "#" and shortened if long, with a room's name, a room id, or an ad click id in the first one's query masked; the same, with more of PostHog's settings such as your organization's id, in your browser's local storage; and entries in the tab's session storage, some holding the page that linked to the visit and others telling the app's tabs apart, all deleted when you close the tab. Turning analytics off in the app stops PostHog and at once deletes its cookie, its local storage, and the session entries with the page that linked to the visit; the entries that tell tabs apart go when you close the tab.
  • Analytics, when you sign up from this site: the app's __Host-cs_from, for 10 minutes while you sign in, holding the address of the page you signed up from. It is set only when your analytics choice allows it, and deleted when the sign-in ends.
  • Analytics, on this site only: our own count of visits (see Counting visits to this site, above) sets no cookie and keeps nothing in your browser's storage. Its answer to each page it counts stays in your browser's ordinary cache, as other parts of web pages do, and holds a date that says which day it is and whether one, two, or more of this site's pages have been counted in your browser that day; your browser sends that date back with the next page counted, and Counterscale uses the cache for nothing else. Turning analytics off stops it being sent, and clearing your browser's cache removes it.
  • Advertising, set on this site only: Google's cookies, holding ids that let Google recognise your browser. Some are set on cuestride.com, each for up to 90 days, among them_gcl_aw and _gcl_gb, which hold the id of the Google ad you clicked; your browser also sends them to the app, whose server reads that id only to report a sign-up or purchase as described above. Others are Google's own cookies, on its own domains (such as google.com and doubleclick.net), which last up to 24 months.
  • Advertising, set on this site only: the Meta pixel's cookies on cuestride.com, each for up to 90 days: _fbp, an id for your browser, and _fbc, which holds the id of the Meta ad you clicked. Your browser also sends them to the app, whose server reads them only to report a sign-up or purchase to Meta as described above. If you are signed in to Facebook or Instagram in the same browser, Meta's own cookies on its domains are sent to Meta with the pixel's requests too.

Cloudflare's count of visits to this site (see Counting visits to this site, above) sets no cookie and keeps nothing in your browser.

"Cookie settings" and "Your privacy choices", at the bottom of every page of this site and under "Privacy" in the app, let you turn analytics and advertising on or off at any time. The sign-in pages of WorkOS and the checkout of Paddle may set cookies of their own, under their policies.

Who else handles data

These providers handle data for us, only to provide their service to us, under agreements that bind them to it:

  • WorkOS: sign-in, sign-in codes, and invitations, with names, email addresses, and memberships.
  • Cloudflare: carries all traffic to CueStride, runs its domain names, stores the database's backups, counts visits to this site (Web Analytics), runs our own count of visits to this site (Counterscale) and keeps its records, and forwards email sent to our addresses.
  • Hetzner: the servers that run CueStride and hold its database.
  • PostHog: our analytics.
  • Brevo (Sendinblue SAS, France): our service and marketing email, once we use it (see Emails).
  • Resend: email delivery for our internal billing alerts (see Alerts to us).
  • Zoho: our email, including what you send to our addresses (such as support and privacy requests) and the alerts to us.

These receive data as controllers in their own right, under their own privacy policies:

  • Paddle, our merchant of record, for payments (its privacy policy).
  • The advertising platforms, for what they do with the data their tags and our reports send them: Google, Meta.
  • OpenAI, when you use CueStride in ChatGPT: it is not our processor; it decides what it does with your conversation, including what we send back, under its own privacy policy.

Brevo also uses some data as a controller for purposes of its own: to keep its service free of abuse, spam, and fraud, and for its own statistics. We disclose personal data where the law requires us to.

Selling and sharing, under US state laws

We do not sell personal data for money. When your advertising choice allows it, some US state laws, such as California's, treat what Google's tag and the Meta pixel collect on this site and the conversions we report as "selling" personal data or "sharing" it for targeted advertising. What goes to Google and Meta this way: identifiers (cookie ids, ad click ids, IP addresses, hashed email addresses, and browser and device details), the pages you view on this site, and commercial information (that you signed up or bought, with the amount paid). To opt out, use "Your privacy choices" at the bottom of every page of this site or under "Privacy" in the app, or turn on Global Privacy Control in your browser: we treat it as an opt-out for that browser and, if you are signed in, for your account, and the page shows that we have. We do not knowingly sell or share the personal data of anyone under 16.

Where it is kept

CueStride runs on servers in the United States, and its backups are stored with Cloudflare, which we ask to keep them in North America. Cloudflare carries traffic, counts visits to this site, and runs our own count of them and keeps its records, on its network of data centres around the world. PostHog keeps our analytics in the United States. Brevo keeps our email data in the European Union, in France, Germany, and Belgium, and its support staff in the United States and India may reach it. Resend keeps our billing alerts, and its logs of sending them, in the United States. Email sent to our addresses, including these alerts, passes through Cloudflare, which forwards it without storing its content, and Zoho keeps our mailbox in the United States. The advertising platforms process data in the United States and the other countries where they operate. If you are outside the United States, your data is transferred there. For data from the European Economic Area, the United Kingdom, and Switzerland, we rely on the EU-US Data Privacy Framework, with its UK and Swiss parts, for providers certified under it, which the European Commission and the UK and Swiss governments have found to protect data adequately; for other providers and countries, we rely on the European Commission's standard contractual clauses, with the UK's addendum. From Israel, we transfer data abroad as Israel's rules on transfers from databases abroad allow. You can ask us for a copy of these safeguards at privacy@cuestride.com.

How long we keep it

  • A room made without an account: deleted after 90 days without activity.
  • Your account, and the rooms and settings of your organization: while the account exists. When you ask us to delete it, we do so within 30 days, together with its analytics profile and any contact at Brevo, apart from the records below that show your consent and that you unsubscribed; the backups let go of it within 30 days after that.
  • A room you delete: gone from the database within about 15 minutes.
  • A code a screen shows to be paired: two minutes. A paired screen: until it is unpaired or the account is deleted. A screen's browser an admin denied pairing: until the account is deleted.
  • An API key: deleted 30 days after it is revoked or expires, whichever comes first; a key that reaches one room is deleted with that room, and every key with the account. The hash of a secret being replaced: until the new secret is first used, or for 24 hours.
  • Backups: a continuous copy kept for 30 days, and nightly copies kept for up to 30 days, so deleted data leaves them within 30 days.
  • Billing records: the plan changes and Paddle's ids, for as long as we must keep accounting records.
  • Alerts to us: Resend keeps them for 30 days, and its backups for up to 7 days after that; if we stop using Resend, it deletes anything left within 90 days; we keep them in our mailbox until the matter is resolved and then for up to 12 months, after which we delete them. Both apply even if the account has been deleted, since the alerts hold only IDs, plan details and dates, never your name or email address.
  • Your IP address: in memory only, while your connection is open or a limit still counts it, and until our next clean-up after that, or until our server restarts. Logs: until they are rotated out, by size.
  • The id of a phone reading an event's attendee page: on our server, in memory only, for two and a half minutes after the page last checked for changes, or until our server restarts; on the phone, until its browser's storage is cleared.
  • The ChatGPT identifier, for our limits: in memory only, in hashed form, for as long as one of our limits still counts it (up to an hour, for the limit on creating new timers), and then until our next clean-up. A server restart deletes it sooner.
  • The keyed hash of ChatGPT's ids for you and for a conversation: with each timer made in that conversation, until the timer's room is deleted.
  • Analytics: PostHog keeps events for the period its plan sets, at most seven years, and we cannot make it shorter. It keeps your account's profile until we delete it. When your account is deleted, or sooner if you ask, we delete the profile and the events linked to it.
  • Counts of visits to this site: Cloudflare keeps them for the period its Web Analytics service sets. They are totals, and we see no single visit in them.
  • Our own count of visits to this site: the record of each page counted, with the details listed under Counting visits to this site and its time, for three months, after which Cloudflare deletes it. It does not hold your IP address.
  • Advertising cookies: those on cuestride.com, up to 90 days on your device, unless you clear them; Google's own cookies, up to 24 months. Turning advertising off in a browser sets Google's tag there to not use them and stops the Meta pixel, and we report nothing from that browser; turned off while you are signed in, it is off for your account too, in every browser. The cookies stay on your device until they expire or you clear them. Google and Meta keep what they receive under their own policies.
  • Your marketing subscription: while you are subscribed, with Brevo's records of each email's delivery, opens, and clicks. When you unsubscribe, your address stays on Brevo's list of addresses we must not write to, for as long as you stay unsubscribed.
  • Records of the consents you gave, for cookies and for email, and of their withdrawal: up to seven years, as long as a claim about them could be brought.

Your rights

You can ask for a copy of your personal data, for it to be corrected or deleted, for its use to be restricted, or for it in a form you can take elsewhere. You can withdraw any consent you gave, at any time, without affecting what was done before you withdrew it: for cookies with "Cookie settings", and for marketing email with the unsubscribe link in any of them. In the US states whose laws give these rights, you can also ask what we collected, sold, or shared about you in the last 12 months, and we will not treat you differently for using your rights.

You can object at any time to our use of your data for marketing, including marketing email and the advertising and profiling described above, and to any use we base on our legitimate interests, such as our analytics. Once you object to marketing, we stop using your data for it.

Write to privacy@cuestride.com from the address on your account or subscription, or, if you have neither, tell us how to find your data, and we answer within 30 days. If we turn down a request, you can appeal by replying to our answer; we decide an appeal within 45 days and, if we turn it down, tell you how to complain to your state's attorney general. You can also complain to the Privacy Protection Authority in Israel, or to the data protection authority where you live.

Security

Every connection to CueStride is encrypted. The secrets in room links and in API keys, and the passwords of rooms, are stored only as hashes (an API key also keeps its last four characters, so it can be told apart), and never sent to our analytics or advertising partners; card details are never stored. No system is perfect: if a breach puts your data at risk, we tell you as the law requires. Only the people who run CueStride can reach its servers and its data.

Children

Accounts are for people aged 18 or over, and CueStride, including in ChatGPT, is not meant for children. We do not knowingly collect a child's personal data, advertise to children, or give their data to advertising platforms.

Other services

CueStride links to services that have their own privacy policies, such as the sign-in pages of WorkOS, the checkout of Paddle, and the advertising platforms. This policy does not cover what they do with data on their own services. The pages Brevo shows when you confirm or manage a subscription are run for us, and this policy covers them.

Changes to this policy

We update this page when what we do changes, and we tell account holders of a material change by email before it applies. When we change where we ask for your agreement first, we publish a new version of this page before the change and, where it turns something on by default, tell account holders in the places affected by email before it applies. The first date at the top of this page is when this policy came into force. The second shows when this wording was published.

Contact

privacy@cuestride.com, or by post to Handz LTD, Jerusalem 14, Givat Shmuel, Israel.