Security and GDPR at Quack
Quack is built by Remuda Group AB in Lund, Sweden, and runs on Google Cloud. This page answers the questions schools and companies ask before they use it. The privacy policy has the full legal text.
Read the privacy policyWhere is my data stored?
Quack runs on Google Cloud and Firebase. The live database that carries every session, and the server functions, run in the EU (europe-west1, Belgium). Sign-in (Firebase Authentication) is processed in the United States, covered by Google's data-processing terms, the EU-U.S. Data Privacy Framework and EU Standard Contractual Clauses.
Do players need an account?
No. A player opens the join page, types the game PIN and picks a nickname. They are signed in anonymously, with no email address and no name. Their answers, reactions and comments are processed live during the session.
How long do you keep data?
Live session data (answers, reactions, comments, scores) is deleted shortly after the session ends. Saved session history and results are kept for up to 12 months, then deleted automatically. A host's account and decks are kept until the host deletes the account.
Who processes data for Quack?
A short list of sub-processors: Google Cloud and Firebase for hosting and databases, Gemini on Google's Vertex AI (EU multi-region) for the AI features, Stripe for payments, Resend for email, and PostHog (EU) for analytics you have agreed to. The full list is below.
Sub-processors
Each one does one job. The same list is in the privacy policy.
- Google Cloud / Firebase (Google Ireland Ltd. / Google LLC)
- Hosting, authentication, databases (Cloud Firestore and Realtime Database - the live database is in the EU, europe-west1), file storage, and serverless functions.
- Google - Gemini (Vertex AI, EU multi-region)
- Generating decks and slides from what you type, from the teaching material you upload (PDF, Word, PowerPoint or text - read in your browser, sent to the model for the length of the request, never stored by us), extracting a theme from a brand document you upload, and writing the post-session brief. For a brief, the session's answers and free-text responses are sent; participants are pseudonymous throughout and none of it is used to identify anyone. Model processing runs on Google's EU endpoint (Vertex AI, `eu` multi-region), so prompts, uploaded material and generated decks stay inside the EU.
- Stripe Payments Europe, Ltd.
- Payment processing, subscriptions and invoices. Stripe collects your billing details on its own hosted checkout - we never see or store your card number.
- Resend (Plus Five Five, Inc.)
- Sending account and transactional email (sign-up, sign-in codes, a deck shared with you, assignment invitations, and product updates you have not unsubscribed from). Receives the recipient address and the message.
- PostHog, Inc. (EU region)
- Privacy-friendly product analytics, hosted in the EU, loaded only if you accept analytics in the cookie banner. It receives an approximate location derived from your IP address (country, region, city), your browser, operating system and device, and which pages and features you use. If you are signed in to a host account it also receives your email address, display name, plan and sign-in method, and the organisation you belong to, so we can see how Quack works for a real account. Participants who join a session are measured in aggregate only - that someone joined, answered and finished - with no profile, no name and never their nickname. In the app for hosts it also records how pages are used (clicks, scrolling and what is on screen) so we can find and fix problems. Typed text and email addresses are hidden in these recordings, pages that show participants' names or answers are not recorded, and recordings are deleted after 30 days.
- Pexels GmbH
- Stock photo search in the deck editor. Searches are proxied through our servers, so Pexels receives the search term but not your identity; result thumbnails then load in your browser from their CDN.
- Apple Inc.
- “Sign in with Apple” - only if you choose that sign-in method.
- Meta Platforms (Facebook)
- “Continue with Facebook” login - only if you choose that sign-in method.
- Google - YouTube (YouTube Data API v3 and the embedded player)
- Playing a YouTube video a host has added to a slide or to a deck's waiting room. We look the video up from our servers to show its title and thumbnail in the editor; the video itself then plays in YouTube's own embedded player in the presenter's browser, which is when Google receives that viewer's request, sets its cookies and may show ads. Nothing is embedded on participants' phones.
- KLIPY (Kikliko, Inc.)
- GIF search in the deck editor, and delivery of a GIF a host has put on a slide. Searches go through our servers, so KLIPY receives the search term but not your identity. Unlike photos, a picked GIF is not copied to our servers - KLIPY's terms do not permit it - so it loads from their CDN: the host's browser, and every participant's phone that opens that deck, reveals its IP address to KLIPY (a US company). We send no user or device identifier with our requests, and ads are switched off for our integration. An organization's admins can turn GIF search off for all of their members.
Does Quack see card numbers?
No. Stripe collects billing details on its own hosted checkout page. Quack never sees or stores a card number.
Is analytics on by default?
No. Product analytics (PostHog, hosted in the EU) loads only after you accept analytics in the cookie banner. Without it, Quack processes only what it needs to run the service.
What happens to files I upload for AI?
When you make a deck from a PDF, Word, PowerPoint or text file, the file is read in your browser and its text is sent to Gemini on Vertex AI for the length of the request. Quack does not store the file.
How is data protected?
Every page and connection uses HTTPS, and Google Cloud encrypts the data it stores. Database rules let a host open and change only their own decks and sessions and the decks shared with them. Images uploaded to a deck can be opened by anyone with their direct link, so they can show on the big screen.
Can we use single sign-on?
Yes, on the Enterprise plan. Single sign-on uses SAML, so your staff sign in to Quack through the identity provider your organisation already uses.
How do I export or delete data?
In the app, Account settings → Download my data exports your profile, decks and session history as a file, and Delete account erases your account, decks, uploaded images and session history. You can delete one session's results from its results page. Players can email us with the session and their nickname.
Can we sign a data processing agreement?
Yes. Email hello@getquack.app and we will send our data processing agreement (DPA), with Remuda Group AB as the processor of the data your organisation puts into Quack.
How do I report a security problem?
Email hello@getquack.app with what you found and the steps to reproduce it. Please give us the chance to fix it before you publish anything.