Privacy Policy
Last Updated: November 16, 2026 Effective: November 16, 2026
This page outlines our policies with regard to the collection, use, and disclosure of Personal Information for visitors who have decided to use our Services.
If you choose to use our Services, then you agree to the collection and use of information in relation with this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy.
The terms used in this Privacy Policy have the same meanings as in our Terms of Service, which is accessible at https://decka.dev/terms, unless otherwise defined in this Privacy Policy.
Information Collection and Use
For a better experience while using our Service, we may require you to provide us with certain personally identifiable information, including but not limited to your name, phone number, and postal address. The information that we collect will be used to contact or identify you.
Information you provide to us directly
We may ask for certain information when you register for the Services or interact with us (such as a username, your first and last names, birthdate, phone number, profession, postal/physical and e-mail address).
We also collect any messages you send us through the Services (such as user feedback, search queries and prompts), and may collect information you provide in User Content you post to the Service (such as text, images, and lottie files you upload to use in your slides). We use this information to operate, maintain, improve and provide the features and functionality of the Service to you, to correspond with you, and to address any issues you raise about the Service.
When you browse presentation templates, we derive preference signals from the tags on templates returned by your searches and from the templates you open. We store the interaction type, tag identifiers, and timestamp — not the raw template search text — to personalize the order in which templates appear. Opening a template contributes more to this ordering than a search.
If you use one of our free tools before you have an account, such as the team generator, and then sign up to keep what it made, we hold what you entered into the tool for up to 7 days, so that we can make it again in your new account. It is then deleted, whether or not you signed up. When something you chose before signing up is made in your account, we note for the same 7 days which workspace it was made in, so that it is made only once.
When you sign up, we keep the page you signed up from (for example, a lesson, a template or one of our tools) and, if you tell us or it is clear from how you started, what you mainly use Decka for, such as teaching or events. We use them to suggest where to start, and keep them for as long as your account exists. If you accept Decka's optional analytics, we also add both to your account's analytics in PostHog, so we can see how people who start in different ways get on.
Decka Studio. When you make an activity in Decka Studio, we keep the whole conversation with its project: your messages and Studio's replies, your answers to its questions, the pictures you upload, and the places you point to on its preview, each with a picture of what the preview showed. We keep with them the plan, the activity's files, the screenshots Studio takes as it checks the activity, and every version it saves. Everyone in the project's workspace can open the project in Studio, and an AI app that one of them connects to Decka can read the project's first request word for word, its plan, the answers given to Studio's questions and the activity's files. We also note when you last had a Studio project open, so that we can decide whether to email you about it, and delete that note once no such email is due. What Studio sends to AI models is described in Information processed by AI-assisted features, and how long a project is kept in Data retention.
If you don't provide your personal information to us, you may not be able to access or use our Service or your experience of using our Service may not be as enjoyable.
Information from third-party services
When you sign in to the Service using a third-party authentication provider, such as Google or Microsoft, we receive the information that you authorize the provider to share with us, including your name, email address, and profile image. When you connect the Service to a third-party application or integration, we receive the information that the integration provides in the course of its operation. When you make a payment through the Service, our payment processor collects your payment details and shares limited transaction information with us. We do not store full payment card information on our systems.
Browser extensions and presentation add-ins
Parts of the Service are delivered through browser extensions and presentation add-ins — currently the Decka for Google Slides Chrome extension and the Decka for PowerPoint add-in. These components extend the Service into a presentation tool you already use. When you install one of them and connect it to your Decka account, the following applies in addition to the rest of this Privacy Policy.
What the Google Slides extension reads. To attach an activity to the intended slide and keep the presenter overlay synchronized, the extension reads the active Google Slides page URL and tab title, the presentation identifier and title, the identifier of the currently selected slide, and whether the presentation is in editing or presentation mode. Through the Google Drive API it checks the current file's type and whether the connected account can edit it. Through the Google Slides API it also reads limited structural metadata: presentation page size, slide and page-element object identifiers, and page-element description fields used to find Decka-owned placeholders. It does not read the body text, speaker notes, existing image content, or other content of non-Decka slide elements. That is a property of what the extension is for, not a limit we happen to observe: to attach an activity and keep the overlay in place it only ever has to find Decka's own elements, so that is all it looks at. Importing a presentation is a different feature with a different and unavoidable need — see Importing a presentation you already have below. The PowerPoint add-in uses its host APIs for comparable Decka binding and placeholder behavior; its marketplace disclosure describes the permissions granted by that host.
What the extension or add-in writes. When you bind an activity to a slide, the extension or add-in inserts a Decka-owned activity placeholder onto that slide so the activity is visible in your presentation flow. Depending on the activity, this may include a shape, label, or QR-code image. When you unbind an activity or remove its placeholder, the integration identifies and removes only Decka-owned elements. It does not modify slide content unrelated to Decka activities.
Decka account authentication. The Chrome extension accesses cookies associated with Decka's production domain, decka.dev, to reuse, renew, and clear the Decka website session. Decka access and refresh credentials are kept in those Decka-domain cookies, not copied into Chrome extension storage. When a Decka access credential expires, the extension sends the refresh credential to Decka's authentication endpoint over HTTPS to obtain a replacement.
Google authorization and local extension storage. The extension requests only Google's file-specific drive.file permission. When the current presentation has not previously been shared with Decka, the extension shows a permission card; Google account connection and authorization for that specific file begin only when you click it. Each additional presentation requires the same file-specific authorization, while previously authorized presentations remain available through the connected account. The Google OAuth access token, optional refresh token, granted scope, token expiry, and consent state are stored in Chrome's local extension storage. The extension sends the access token to Google over HTTPS when it calls the Google Drive or Google Slides APIs. It sends the OAuth authorization code, and later the refresh token when renewal is needed, to Decka's authenticated token-exchange endpoints; Decka performs the corresponding exchange with Google because the OAuth client secret cannot be included in the extension. Chrome extension storage also contains the configured Decka service URL, presentation/slide-to-activity bindings, references used to find Decka-owned placeholder and QR elements, and limited interface and keepalive state.
State synchronized with Decka. To make bindings available after the extension panel or browser restarts, the extension synchronizes presentation and activity metadata with Decka. This metadata may include the Google presentation identifier and derived presentation title, slide identifier, Decka activity identifier, activity title and type, selected background reference, and update time. Decka stores this server-side state under the authenticated account or workspace. The extension does not send the body content of unrelated Google Slides elements as part of this synchronization. Importing a presentation, described below, is a separate feature and is not part of it.
Activities, uploads, and the presenter overlay. Activity content created in the extension — such as titles, prompts, poll options, quiz questions and answers, Q&A descriptions, reaction settings, and other activity configuration — is sent to and stored by Decka. Custom background images selected in the extension are uploaded to Decka and may contain embedded file metadata as described in Files and media you upload below. When an activity is presented, the extension loads a sandboxed Decka presenter page in an iframe over the Google Slides page. The iframe runs under Decka's web origin and connects to Decka to receive the activity configuration and live participant data needed for presentation, including display names or anonymous labels, answers, open-text responses, Q&A questions, quiz results, reactions, drawings, join/leave state, and aggregate counts. The remote page does not receive access to Chrome extension APIs.
Network and usage data. Requests from the extension and presenter page provide the network and device information described in Log Data, including IP address and approximate location derived from it. If you explicitly accept Decka's optional analytics, we send product-usage events to PostHog, such as creating, deleting, starting, pausing, resetting, or ending an activity. Those events may include the Decka user and workspace identifiers, activity and presentation identifiers, request path and method, timestamps, participant or response counts, and operational exception messages and stack traces. The account's current analytics choice is applied to authenticated extension requests; a client-supplied analytics identifier cannot enable collection. The submitted extension package contains no PostHog or Sentry SDK, and the embedded presenter does not receive browser analytics or error-reporting SDK configuration.
Decka also uses Sentry for operational error diagnosis on its servers and on ordinary Decka web pages. Before an error report leaves our systems, we remove request query strings and bodies, recursively filter credential-bearing fields (including authorization, cookie, embed-token, and presenter-token values), and remove query strings and fragments from structured URL fields and URLs embedded in event text. We also suppress browser error reporting entirely on the extension's embedded presenter and on credential-bearing OAuth callback pages. Error reports may still contain the scrubbed exception message and stack trace, request path and method, browser or runtime information, and a timestamp. We use these records only to secure, diagnose, and maintain the Service. The extension is not used to collect a history of unrelated websites, raw pointer positions, navigation-keystroke contents, or console logs.
Chrome Web Store Limited Use. User data obtained through the Chrome extension is used only to provide and improve its disclosed single purpose: creating, binding, and presenting interactive Decka activities in Google Slides. We do not sell extension user data or use or transfer it for advertising, data brokerage, unrelated secondary purposes, creditworthiness, or lending. We transfer it only as needed to provide the user-requested features through our disclosed service providers, support user-directed sharing, maintain security and prevent abuse, or comply with law. Our handling of extension user data otherwise follows the Chrome Web Store User Data Policy's Limited Use requirements.
Limited use of Google API data. Our 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. In particular, information received from Google APIs through the Services is used only to provide and improve user-facing features of the Services; is not transferred to third parties for advertising, machine learning, or any purpose unrelated to the user-facing features you signed up for; and is not used to train any general-purpose AI model, consistent with the broader commitment in How we use your information below. Google authorization data is processed locally by the extension, by your browser when you import a presentation, and by authenticated Decka and Google endpoints as needed to provide those features, and is transmitted over HTTPS. When you import a presentation from Google Drive, the short-lived access token authorising that one file is sent to Decka only so that Decka can request the export from Google; it is used for that request and discarded, and is never stored or logged. We do not permit human access to Google API data except where necessary for support or debugging at your request, to investigate suspected violations of our Terms of Use, or as required by law.
Disconnecting an extension or add-in. You can sign out of the extension or add-in at any time from its panel. Signing out ends the Decka session but does not by itself revoke Google authorization or delete server-side presentations, activities, participant submissions, uploads, or synchronized bindings. Choosing the extension's option to switch Google accounts removes the Google OAuth credentials stored by the extension before a new authorization begins. You can also revoke the Service's access to your Google account at https://myaccount.google.com/permissions or to your Microsoft account at https://account.microsoft.com/privacy. Uninstalling the Chrome extension removes its local extension storage; server-side information remains subject to the deletion and retention terms below. Importing a presentation leaves nothing to disconnect: that authorization covers only the single file you picked, Decka keeps no Google credential from it, and the imported deck is an ordinary Decka deck you can delete like any other.
Decka in Canva
Canva identity and your activity library. When you open the Decka app in Canva, Canva supplies a signed token containing app, user, and team identifiers. We verify that token and derive an identifier for a private Canva activity workspace. Canva does not supply your email address through this flow, and you can use that workspace without creating a separate Decka email-and-password account. We store the identity-to-workspace association and the activities, uploads, and participant responses needed to provide the integration.
Connecting an existing Decka account is optional. If you choose to connect one, we require authentication to both Canva and Decka and verify the Decka account's email status. We store the linked Decka user identifier, verified email address, and workspace identifier. Connecting accounts does not merge or transfer their activity libraries: you can switch between the Canva library and your Decka library. A signed-in Decka user can open Canva libraries linked to that account from the Canva setup page. Disconnecting the accounts removes the link without deleting either library.
Design access and saved elements. The app inserts Decka-owned elements containing a frame identifier and dimensions, and can update the selected Decka element when you request an independent activity copy. Decka stores the frame's activity selection separately in your workspace. This flow does not read the text, images, notes, or other content of unrelated Canva design elements. Saved designs contain no Decka sign-in credentials. Duplicating a Decka element shares its activity and results until you explicitly create an independent copy. Sharing a design does not give another user permission to control your workspace.
Browser connections and local storage. To configure or control an activity outside the native Canva panel, we use a short-lived connection link and ask you to confirm the connection. Device-bound credentials are saved in the relevant browser's storage when permitted; the server stores a hash of the device secret. The native panel, browser setup page, and embedded slide may have separate storage, so a slide can require its own confirmation. Credentials and one-time connection secrets are not saved in Canva elements or public activity links. We also save non-secret identifiers for unfinished insertion or copy operations in tab-scoped browser storage so a reload or lost response does not create duplicate activities. These recovery records can survive signing out, contain no activity content or credentials, and are used only after the same account authenticates again.
Activity content and AI features. Content you create or upload and audience responses are processed as described elsewhere in this policy. Optional AI generation and activity insights process the prompts, activity context, or submitted responses used by that feature under Information processed by AI-assisted features. The Canva identity connection does not itself send your Canva design content to an AI model.
Signing out and uninstalling. Signing out revokes the relevant browser session; it does not delete your activities. When Canva sends a verified app-uninstall event, we revoke the associated Canva device sessions and pending connection links and schedule deletion of that Canva workspace's content through our account-deletion process. Your separately linked Decka workspace and its content are not deleted by Canva uninstall. Retention exceptions and backups follow Data retention below. You can also request deletion using the contact details in this policy.
Importing a presentation you already have
Separately from the extensions above, the Decka dashboard can import a presentation you already have — a PowerPoint .pptx file from your device, or a presentation from your Google Drive. You do not need the Chrome extension for this, and it is not part of it.
Why this reads more than the extension does. The Google Slides extension deliberately does not read your slide content, and that remains true of it. Importing is the opposite case: copying a presentation into Decka means reading the presentation, and there is no version of "import my deck" that does not involve reading the deck. So when you import one, we read the file in full — slide text, speaker notes, images, layout, fonts, colors, and shapes — and reproduce it as an editable Decka deck.
What happens to it. The imported presentation becomes your own Decka deck. It is stored and treated exactly like a deck you created in Decka, under Your content and Files and media you upload below, including their retention and deletion terms. Images embedded in the file are stored as deck assets and may carry embedded file metadata as described in Files and media you upload. We do not use imported content to train any general-purpose AI model.
Importing from Google Drive. When you choose to import from Google Slides, Google's own file picker opens and you select one presentation. That selection is the permission. Decka requests only Google's file-specific drive.file permission, which grants access to files you hand it through that picker and to nothing else — Decka cannot list, search, browse, or open anything in your Drive that you did not pick, and each presentation you import is authorized separately. Decka receives a short-lived Google access token, sends it to Google once to export that one presentation, and does not store, log, or reuse it. There is no long-lived refresh token in this flow, and Decka holds no standing access to your Google account. Your original presentation in Google Drive is not modified.
Importing a file from your device. A .pptx file you upload is transmitted to Decka over HTTPS and handled as described in Files and media you upload below.
Information about participants in sessions you didn't host
Some Decka features let people join an interactive session — a poll, a quiz, a word cloud, a Q&A, a drawing activity, an audience game — without first creating a Decka account. We refer to those people as "Participants." If you are a Participant joining a session that someone else created, this section describes the information we receive about you in that role.
When you join a session, we may receive:
- A display name that you choose, or, where the session permits, an anonymous label;
- Your responses — the answers, votes, drawings, photos, words, reactions, and other contributions you make in that session;
- Session timing data — when you joined, how long you stayed, and (for activities that depend on it) how quickly you responded to a prompt;
- Technical information sent by your browser to load and run the session, including your IP address, approximate geolocation derived from that IP address, browser type, and device identifiers — used for security, abuse prevention, and fault diagnosis;
- An email address, but only if you ask us to send you a copy of the results at the end of an activity, or to email you how to make an activity like the one you took part in. You can take part in a session without giving one, and nothing else in this section requires one. Because that address is handled differently from everything above, each of those requests has its own subsection below.
In most cases, the host of the session — the Decka account holder who created it, or the workspace they use Decka through — controls the personal information you provide as a Participant. We act on that host's instructions when we process Participant data and when we make it available to them through the Service. If you have questions about how a particular host uses the data they collect from you through Decka, please contact the host directly. Where we are processing Participant data on a host's behalf, we will pass your privacy-rights requests through to them.
We may use Participant data on our own behalf for limited operational purposes that apply to the Service as a whole — for example, to detect abuse, investigate security incidents, prevent fraud, and meet our legal obligations.
We retain Participant data only as long as needed for the host to use it through the Service, plus a short additional period to handle disputes or service issues. We do not enable persistent identification of Participants across sessions hosted by different organizers.
If you ask us to email you a copy of the results
At the end of an activity you took part in, Decka may offer to email you a copy of the results. If you accept, you type an email address. Alongside it we record which activity sessions in that meeting the copy should cover, and whether you ticked the box asking for additional communications from us. We do not ask for your name, and the address is not used to link what you did in one organizer's session to what you did in another's.
Decka is the controller for that address — the host is not. This is the one piece of Participant information in this section that does not belong to the person running the session. The host never sees it, cannot export it, and it does not appear in anything we make available to them, so a request about it goes to us at legal@decka.dev rather than to them. We use the address to send you one email with the results of the sessions you took part in, and to respond to you if that send fails or you contact us about it.
That email contains a link to a page showing the same results. There is no sign-in on that page, so the link itself is the whole key to it: treat it as private, and do not forward it to anyone you would not show your own answers to. The link stops working 90 days after you asked for the report.
How long we keep it. We erase the address 7 days after your report has been delivered. If the report is never delivered — the send fails permanently, or you asked for a copy of a session you then took no part in — the address is erased 30 days after you gave it to us, so a failed send cannot turn into indefinite storage. The address-free record behind the link (which sessions the copy covers, and the choice you made about additional communications) is kept for 90 days, the lifetime of the link itself, and is then deleted with it.
Additional communications are optional and separate. The box asking whether we may send you occasional additional communications from Decka starts unticked, and your copy of the results is sent whether or not you tick it. If you do tick it, we add your address to the Feature updates and marketing topic described under Email we send you, and how we measure it below; every message we then send carries a one-click unsubscribe link, and using it takes effect immediately and does not affect the results email you asked for. If your request reaches us from an IP address in Canada, we treat the box as declined whatever you ticked, because Canada's anti-spam law requires consent given expressly for that purpose.
If you ask us how to make an activity like it
While you wait between questions in some sessions, Decka may offer to email you how to make an activity like the one you are taking part in. If you ask, you type an email address and we send you one email: how to make that kind of activity, and what else you can make with Decka. It names the kind of activity, never the host's title or questions. As with the results copy, Decka is the controller for that address, the host never sees it, and a request about it goes to us at legal@decka.dev.
We use the address only to send that email, and we do not keep it. It is held only until the email is sent, and is then deleted. When many people in one session ask at once, the emails go out in turns, so that can take hours. This address is separate from any address you gave for a copy of the results: neither request reads the other's.
Limits on requests. So that nobody can use this to send mail to someone who did not ask, we limit how many requests one device, one network and one address can make. Those counts are kept under keyed one-way fingerprints of the IP address and the email address, never the values themselves, for at most 24 hours, and are used only to prevent abuse.
Additional communications work exactly as they do for the results copy: the box starts unticked, your email is sent whether or not you tick it, and only if you tick it do we keep your address, for the Feature updates and marketing topic, with a one-click unsubscribe in every message. Requests from an IP address in Canada are treated as declined, as above.
If you play an activity made in Decka Studio
An activity made in Decka Studio runs in a room of its own, which a phone joins by the room's code or QR code. Your phone sends the room only what the activity asks of you: your taps, choices and numbers, anything you type, up to 500 characters for each answer, and, in a room that asks for one, a name of up to 40 characters. The room accepts no photo or file, and an activity cannot use your phone's camera or microphone. A name is refused, and typed words are removed, if they match a list of words we hold back. Some activities also ask an AI model for words or pictures as they run, as described in Information processed by AI-assisted features.
Classroom rooms. A room is a classroom room when the person in its workspace who made the activity, or the host who starts the room, has told us they use Decka for teaching, when the activity was made from a classroom template, or when Decka has labelled it a classroom activity. If we cannot tell, the room is a classroom room. In a classroom room:
- the phone never asks for a name, and a name sent anyway is not kept;
- before the activity sees anything a player types, an automated system from Typesafe AI checks it, by its text alone. Text it flags is removed; text it is unsure of, or could not check, waits for the host, and so does everything else typed unless the host switched that review off;
- the record the room leaves keeps counts and scores, and no words, unless the activity takes typed answers and the host chose Keep typed answers when starting it. While an activity that takes typed answers keeps numbers only, a public link to the deck does not show its room's screen.
Other rooms. In any other room, the phone asks for a name. When the host has switched moderation on, what players type is checked by Typesafe AI's system too, by its text alone: text it flags is removed, and text it is unsure of waits for the host. The record the room leaves keeps what the activity drew at its end, which can include players' names and what they typed.
What the room keeps. While it runs, the room holds the game: who has joined, what each phone sent and what the activity made of it. It deletes all of that soon after it ends, as Data retention says, and leaves the workspace that ran it one record: when it ran and who started it, how many took part, the AI credits it used, and the summary the activity drew at its end, kept as the rules above say. That record appears in the activity's report to the people who can edit the activity in that workspace. A practice run's record keeps no summary. Whoever made the activity, if it came from another workspace or from Decka's library, sees nothing of the rooms it runs in.
Your phone. The join page sets one strictly necessary cookie, described in our Cookie Policy, so that your phone keeps its seat after a reload; each room is given only a one-way fingerprint of it, different in every room.
Reporting an activity. The Report link above the activity tells Decka that something is wrong with it, and sends no words. So that each phone's report counts once however often it is sent, we keep a keyed one-way fingerprint of the identifier in your phone's cookie and of the network the report came from, never the address itself, and use them only to count reports and stop abuse.
Squadrillion game answers
For the free Squadrillion game and team games, we count accepted canonical answers to improve answer recognition and evaluate future scoring. We count one accepted answer per person, prompt and game, and use hash-based records to avoid counting retries. These frequency records do not include player names, account identifiers, email addresses, IP addresses, private game links or report links. Aggregate counts and duplicate-prevention records do not expire automatically; keeping them prevents delayed retries from being counted again.
To investigate valid answers that may have been rejected, we also keep a limited sample of rejected or unchecked answer text for private administrator review. We keep at most three distinct candidates per person, prompt and game, normally for 14 days, with a configured maximum of 30 days. Expired text is excluded from review and deleted by scheduled cleanup. We filter common contact details, obvious secrets and control characters before collecting this sample, and exclude answers explicitly refused by contextual safety checks. A word-list match alone does not remove an answer from private review: it may be part of a legitimate cultural name. If a safety check could not finish, the private sample may include inappropriate text. These checks cannot recognize every kind of personal information: please do not enter personal details in game answers.
The review sample is not shared on public score pages, with the host or other players, or in game reports. An administrator may approve a verified canonical answer or alias for future games only after a contextual safety check; approval does not expose the rejected text as a public submission or change an existing score. Administrative review decisions retain an audit record. The administrator's identity and review note are removed after 24 months; the canonical decision and hash-based retry record remain so future judgments and retries stay consistent.
Draw the Suspect mugshots
Draw the Suspect is a party game in which one player's face is the suspect: a few witnesses describe it, everyone else sketches it from what they hear, and the face is revealed at the end of the case. When a host plays it with photos, each Participant may take a photo of their own face (a "mugshot") when they join. Taking one is optional: a Participant who skips it still plays, and is never the suspect.
What we keep. The Participant's phone sends a smaller copy of the photo and a thumbnail of it, which we store with the session. Our servers refuse a mugshot that still carries the details a camera embeds in a photo, such as its location, the time and the device. A Participant can take theirs again until they have been a suspect, and the earlier one is deleted.
Who sees a mugshot. Thumbnails are shown on the host's screens, and on screens the host has set up to present the session, while players join; the host can remove any of them there, which deletes it, and that Participant is then never the suspect. When the players guess who the suspect was, each guesser's phone shows the thumbnails of the six faces in their line-up. The suspect's mugshot is shown in full to each witness only while they press and hold to look, for at most 3 seconds of holding in all, through links that each work once and expire within seconds; and on the host's screens once the case is revealed, for the rest of the session. A Participant's own phone can always show their own mugshot. A mugshot is never shown to anyone who only watches the session through its link, and never put in an email.
The host's report. After the game, the host's report shows the mugshots and the sketches drawn of them to the host and anyone who can edit the activity in their workspace. Mugshots and sketches are deleted within a day after 90 days from when the first image of their session was stored, and when the activity is deleted. After that, the report shows names and the witnesses' statements only.
AI witnesses. A host can choose AI witnesses instead of witness players. For each case whose suspect is a Participant's mugshot, that mugshot is then sent to Anthropic, the AI model provider that writes the case's three witness statements; if the request fails, it may be sent again for the same case. The statements may describe only what anyone can see (hair, glasses, headwear, accessories, expression, clothing and its colours, and the background), never a person's age, ethnicity or race, religion, gender identity, body, disability or health, or attractiveness, and never a name. Before anyone reads them, the statements, but not the photo, are checked by a second automated system, from Typesafe AI. We keep the statements with the case, in the host's report, and nothing else of the request. We do not authorize Anthropic to train its general-purpose models on the photo. A practice run never sends a photo to an AI.
Teaching. When the person who makes a Draw the Suspect has told us they use Decka for teaching, or starts from its classroom template, mugshots start switched off, and the game plays with illustrated suspects from our case bank instead. The host can switch them on.
The free Daily line-up. Draw the Suspect's free page, the Daily line-up, uses no photos and sends nothing to an AI: its suspects are illustrations from our case bank, and the sketches drawn there stay in the browser they were drawn in. So that you can play without an account, it keeps a day's progress and your streak in one strictly necessary cookie, described in our Cookie Policy, which holds the day's picks, when each was made, and the streak, but no identifier, and is kept for 90 days after your last play.
Mic Drop answers
Mic Drop is a party game in which Participants write funny answers to prompts and the room votes on them, with no names shown until the votes are in.
The family-friendly filter. A host can switch on a filter, which starts on when the person who makes the game has told us they use Decka for teaching. With it on, each answer a Participant writes is checked by an automated system from Typesafe AI before it is shown on the big screen. The check sends the answer's text alone, never a name. An answer that system flags, or is unsure of, is shown only to the Participant who wrote it, and a prepared line takes its place on stage. A practice run is never checked. Answers are kept with the session like other responses, and an answer the host hides is left out of every report.
The free Daily duel. Mic Drop's free page, the Daily duel, gives everyone the same prompt each day: you can write one line, and judge pairs of other players' lines and lines we wrote in advance.
- Before anyone else sees your line, Typesafe AI's automated system checks it. A line it flags, or is unsure of, stays yours alone.
- So that you can play without an account, writing a line sets one strictly necessary cookie, described in our Cookie Policy, which holds a random identifier we issue and nothing about you. It lets the page show you your lines and results next time, keeps your own lines out of the pairs you judge, and moves your lines to your account if you sign in.
- Each line has a private link to its result. Whoever holds the link can read that one line's result, and do nothing else.
- If you are signed in when you write a line, or sign in or create an account on that device afterwards, we email you the line's result once it is final, unless you switch that off on the page. We erase the address once that email has gone, or once we have given up sending it.
- We delete every line, the record of who wrote it and every pair judged 90 days after the prompt's day, and keep only that day's prompt and its counts. The cookie and the result links expire with the lines.
Log Data
Whenever your browser requests the Service, our hosting and security infrastructure receives operational Log Data needed to deliver and protect that request. This may include your Internet Protocol ("IP") address, approximate location derived from it, browser or user-agent information, request path, and request timestamp. Route pageviews, page-leave events, time spent, and how fast pages load and respond are optional product analytics and are collected only while you have a current explicit Accept choice for analytics. We do not use the extension to collect a general history of unrelated websites.
If you gave that Accept on or after October 19, 2026, PostHog may also make a masked recording of how you use the Decka dashboard, so we can see where getting started is hard. A recording keeps the layout of each page and where you move, click and scroll. Every piece of text on the page is masked, what you type is never captured, and images, video and drawing areas are left out. Pages your audience uses (joining a session, answering, the live and big screens, the results reports sent to them, and public decks), presenting, the Insights reports on your dashboard, Decka Studio's pages, and the presentation add-ins are never recorded. An Accept given before that date does not allow recording.
A private history of how you use Decka
If your Decka account was created on or after October 19, 2026, Decka keeps its own record of how you use the Service while you are signed in: the pages and dialogs you open, the buttons you press, how long a screen stayed in view, the kind of page you signed up from, and the identifiers and types of the activities involved, each with the time it happened. It never holds anything you typed, the content of your presentations or activities, or anything your audience submitted. We use it only to understand where getting started is hard, and to improve it.
Each entry is deleted automatically 180 days after it was recorded. The record never leaves Decka: it is not sent to PostHog or any other analytics provider, and it is not shared with or sold to anyone. It is included when you ask for a copy of your data, and deleted when you delete your account.
It is on by default for those accounts. You can turn it off at any time under Settings → Privacy, and turning it off also deletes the history kept so far. A browser that sends a Global Privacy Control signal is treated as having turned it off for what you do in that browser. Accounts created before October 19, 2026 are not recorded.
Cookies
Cookies are small files or values that a website stores in your browser.
Our Services use strictly necessary cookies to persist authentication, protect authorization flows, provide billing, remember your cookie choice, and keep your lines and progress in our free games, Mic Drop's free Daily duel and Draw the Suspect's free Daily line-up. Optional analytics cookies are off by default and are used only after you click Accept. You can refuse optional cookies without losing core Service access. Blocking strictly necessary cookies in browser settings may prevent authentication, billing, or other requested features from working.
For more general information on cookies, please read "What Are Cookies".
Email we send you, and how we measure it
Decka sends two kinds of email, and they follow different rules.
Transactional email is email you receive because of something you or someone else did in the Service: a sign-in code, a password reset, a workspace invitation, a receipt, a report for an activity you presented, the copy of the results a Participant asked us for, and the email a Participant asked for about making an activity like the one they took part in. We send it whether or not you have opted in to anything, because it is the thing that was asked for.
We may also send necessary account, security or service-interruption notices to affected customers. These notices do not require marketing opt-in and do not include promotions or ordinary feature announcements.
Getting-started email. After you create an activity, we may send you up to three short emails about using it, such as how to run it with an audience. Like the welcome email when you sign up, they are sent because of what you did in your account, so they do not depend on the marketing topic below. You can turn them off under Settings → Email preferences, or from any of them.
They come from the mailbox of a member of our team, which Google Workspace hosts and delivers for us, and we keep Google's identifiers for each one with our record of the send. If you reply to one, your reply reaches that person, and we note that you replied and send you no more of them. So that they arrive in your morning, we save with your account the time zone your signed-in browser reports, such as Europe/Paris, and keep it for as long as your account exists. Until we have one, they are planned for the time of day you created the activity. We also keep, for as long as your account exists, which of these emails your account was set up to receive, so that none is ever sent to you twice.
Marketing email — product announcements, tips, offers, and other promotional updates — goes only to addresses that have opted in to the Feature updates and marketing topic. Every checkbox that offers that topic starts unticked, and we do not subscribe you as a side effect of creating an account or signing in through Google or Microsoft. Every marketing message carries our physical mailing address and a one-click unsubscribe link, and if you have an account you can change the topic at any time under Settings → Email preferences. Requests reaching us from an IP address in Canada are treated as opted out regardless of the checkbox, in line with the express-consent standard in Canada's anti-spam law.
For newsletters and product updates, we may select recipients by subscription tier, recorded product use, and country. We maintain a daily audience snapshot for these selections and check current identity and permission before delivery. We record changes to your marketing preference, including when and how you chose it and the wording version, so we can verify permission before sending newsletters. Permission for occasional product news is not treated as permission for broader offers and promotions; those require the broader choice in Settings. We keep this preference history and account-attributed product-use milestones while your account exists and remove them, including audience snapshot records, with your account. We keep a country code, its source, and the time it was observed with your account. Where no more reliable country information is available, we use the country estimated by our hosting provider from a signed-in request's IP address; this record does not contain the IP address itself and is not proof of residence. This country record is removed when your account is closed. Country estimates never opt you into marketing or override an unsubscribe.
Newsletter buttons and links measure aggregate clicks for that newsletter and destination. They do not identify the recipient, set an attribution cookie, or add an open-tracking pixel. Email scanners and repeated clicks can affect these totals, so they are not a count of unique people.
How we measure our own email. For the lifecycle messages we send as part of a campaign, we record whether the message was opened and whether its links were clicked. An open is measured by a single-pixel image loaded from our own servers when your mail client displays the message; a click is measured by sending the link through our own redirect before it takes you where it says it goes. Both carry an identifier for the message, not for you — your address never appears in those URLs, they are served by Decka rather than by an advertising network, they are not used to build a profile of you, and none of it is shared with any presenting workspace. If you would rather not be measured this way, most mail clients can be set not to load remote images, and unsubscribing stops the messages altogether. A click also sets the short-lived first-party cookie described in our Cookie Policy, which exists to connect a visit to the message that prompted it. The getting-started emails carry no such image, so whether they were opened is not measured. For them, the record of each send also notes when you first visited Decka from it and when an activity of yours, or one you started, first ran with an audience, and we keep with your account, for as long as it exists, which of them you visited Decka from and when you first did, so we can tell which of them help.
We also keep day-bucketed totals — how many messages went out, how many were opened, how many clicks came back, and how many visits followed — which carry no email address and no account identifier.
How we use your information
We use the information we collect for the following purposes:
- to provide, operate, maintain, and improve the Service;
- to authenticate users and protect the security of accounts;
- to process payments and send transactional communications;
- to send the email you asked us for, to send marketing email where you have opted in to it, and to measure whether our own messages and pages work;
- to respond to your inquiries and provide customer support;
- to personalize your experience and remember your preferences;
- to analyze usage trends so that we can improve the Service;
- to detect, investigate, and prevent fraudulent or unauthorized activity; and
- to comply with our legal obligations and to enforce our Terms of Service.
We do not use your User Content to train general-purpose AI models, whether our own or those of third parties.
Service Providers
We may employ third-party companies and individuals due to the following reasons:
- To facilitate our Services;
- To provide the Services on our behalf;
- To perform Services-related services; or
- To assist us in analyzing how our Service is used.
These third parties may have access to your Personal Information to be able to perform the tasks assigned to them on our behalf. They are obligated not to disclose or use the information for any other purpose.
Sharing your content
Several features in our Services exist so that you can share your work with other people. When you choose to share, the form of sharing you choose determines who can access the content and what they can do with it. This section explains what happens to information when you exercise those sharing features, and how that information moves between you, other users, and, in some cases, third parties.
Content you publish via join codes, public links, or embeds
Some features such as, but not limited to, interactive activities, participant-joinable sessions, shareable view-only links, and embeds, are designed so that any person who holds the code, link, or embed can access the associated content without an account or invitation from you.
A start link that works without signing in. If you turn on "Start without signing in" for an activity, anyone who holds its start link can start, run and end that activity and see its live screen, including the responses and results it shows, without a Decka account. They cannot edit, export or delete it, or open its results history. Treat the link like a key: you can turn it off, or replace it with a new link, at any time. We keep a record of the link with your account (when it was made, when it expires, when it was last used and how often, and when it was turned off), and nothing about whoever uses it. The record is deleted with the activity or with your account.
When you generate a join code or enable a public link, you should assume that the content behind it may be viewed by anyone the code or link is forwarded to, indexed by tools that scrape public URLs, or captured by recipients (for example, via screenshots, recordings, downloads, or browser caches). Once you have made content accessible in this way, we cannot retract it from places where it has already been viewed, captured, or redistributed.
Content you share with specific recipients
Where the Service supports sharing with named individuals (for example, by inviting collaborators by email, granting workspace access, or adding co-editors to a presentation), those recipients may view, edit, comment on, copy, duplicate, or export the shared item according to the role you grant them, and will see your full name as the inviter. When you invite a recipient by email, that address becomes associated with the shared item for the purpose of access control. Recipients you invite may further share the item with others if the role you grant them permits it. Removing a recipient or revoking a link prevents further access through our Services, but does not affect copies, exports, or derivatives the recipient may already hold.
Content visible within a workspace or organization
If you use the Services as part of a workspace, team, or organization, the administrator of that workspace may have access to the content, files, and activity created within it, including content created by you, regardless of whether you marked it as private. Workspace administrators may also be able to manage, transfer, export, or delete that content, suspend or reassign accounts, and apply retention or audit policies. We act on the instructions of the administrator with respect to workspace content. If you are unsure whether your account is part of a workspace, please contact your administrator before sharing anything personal through it.
Automatic and default sharing within your workspace
Some workspaces, teams, or organizations may configure the Service so that presentations, activities, or other items you create are automatically shared with a defined group, such as members of your team or workspace, at the moment of creation, without a separate action on your part. These settings may be controlled by you, by your workspace administrator, or by both. When automatic sharing is in effect, items you create may be visible to other members of the configured group as soon as they are saved, including drafts and works in progress. Changing the default later applies only to items created after the change and does not retroactively unshare items that were already shared. Before relying on a workspace, please review the automatic sharing settings that apply to your account.
Activities you submit to Decka's library from Decka Studio
When you submit an activity you made in Decka Studio to Decka's library, Decka's staff review it. They see who submitted it, the activity's files, its cover, the results of Decka's checks and which workspaces hold a copy of it, and they can play it with test players. They do not see the conversation you built it in or the pictures you uploaded. Once Decka approves it, other Decka users can find it in the library and run it in their own sessions, and its cover and the pictures that explain it can be opened by anyone who has their address, without signing in.
Its credit line reads "[the activity's title] created by [your first and last name]" while Show my name on activities Decka approves is on under Settings → Privacy, which it is unless you switch it off, and "Created by the Decka community" while it is off. If Decka changes your activity, the line also says it was edited by Decka. It never shows your email address or your workspace. We email you when Decka approves your activity, asks for changes (with our reviewer's note), turns it down, withdraws it from the library or changes it.
Files and media you upload
When you upload images, animations (including Lottie files), fonts, audio, video, documents, or other media to the Service, those files are stored so that the slides, activities, or presentations containing them can be rendered. If the slide, activity, or presentation containing a file is shared, the underlying file is shared with it, including any metadata embedded in the file by the device or application that created it (such as EXIF location data, original filenames, or author tags). We do not strip embedded metadata from uploaded files. If a file contains information you do not wish to disclose, please remove that information before uploading.
Gift photos are the exception. When a Participant photographs a gift in a White Elephant, Yankee Swap or Dirty Santa game, their phone makes a smaller copy of the photo before sending it, without the details the camera embedded in it, such as its location, the time and the device. Our servers refuse a gift photo that still carries those details.
Participant identity, reactions, and contributions
Features that allow people to join a presentation, react in real time, answer prompts, leave feedback, or otherwise contribute will display the contributor's chosen display name (or, where applicable, anonymous label), their reactions, and their responses to the host and to other participants of the same session, in accordance with the configuration of that session. Aggregate counts (for example, totals of a given reaction) and timing information (for example, when a participant joined or left) may be visible to the session's host or organizer. If you join a session as a participant, you should treat any name, response, or reaction you provide as visible to the host and, depending on the session, to other participants. A gift photo is shown on the host's screens, on the phones of the people taking part in that session, and on screens the host has set up to present the session. It is not shown to anyone who only watches the session through its link. If the host has chosen to approve photos first, a photo is seen only by the person who took it and the host until the host shows it.
Exported and downloaded content
When you, or someone with whom you have shared content, export a presentation to formats such as .pptx, image, PDF, or video, or when you download embedded media, the resulting file is no longer governed by our Services. Once exported, the file may be stored, edited, redistributed, or uploaded elsewhere by the holder, and our access controls and revocation tools cannot reach it.
The practical limits of revocation
Across all of the sharing flows above, once a piece of your content has been viewed, copied, exported, screenshotted, recorded, downloaded, indexed, or otherwise captured by another person or system, we cannot guarantee its removal from those locations. Deleting content from your account, revoking a link, removing a collaborator, disconnecting an integration, or closing a session prevents further access through our Services going forward; it does not undo access that has already occurred. Please choose what you publish, and who you invite, with that limit in mind.
Information processed by AI-assisted features
If you use AI-assisted features of the Service (for example, generation, summarization, suggestions, or translation), the prompts you submit and the content you provide as context, including text, files, and uploaded media, are processed by the model serving that feature in order to return a result. We may retain prompts and outputs to operate, debug, monitor for abuse, and improve the feature. Where we use third-party model providers to deliver these features, prompts and content are transmitted to those providers under contractual restrictions; we do not authorize them to train their general-purpose models on your content. If you do not wish to submit a piece of information to an AI-assisted feature, do not include it in a prompt or attach it to one.
Building in Decka Studio. Studio builds with an AI model from Anthropic. Each time it works on a project, the model receives the conversation so far, with every picture you uploaded or pointed to, and the plan, the activity's files and the screenshots Studio takes. Studio takes those screenshots in a browser that Cloudflare runs for us, which is served the activity by Decka and can reach nothing else, with made-up test players; a second turn of Anthropic's model reviews them, with your first request. Before Studio takes in a message or an answer of yours, an automated system from Typesafe AI checks its text. When Studio paints a picture, its description, and any picture of yours it works from, goes to Google's Gemini; Typesafe AI's system checks the description first, and Anthropic's model then looks at the picture to check it for writing. A cover Studio paints without being asked is described from the project's plan, or, before there is one, from your first message. When you submit an activity to Decka's library, Studio prepares it with Anthropic's model, which receives the activity's files and screenshots, never your conversation, and paints its pictures with Gemini.
Building with your own AI app. You can also build in Studio from an AI app of your own that you connect to Decka. Decka sees none of your conversation with that app, only what it sends: the activity's files, and its requests to check, try out, look at, paint for or submit the activity. The files are kept with the project like Studio's own, and each request is handled as Studio's would be, including the review of its screenshots unless the app asks for none; the screenshots and the review go back to the app. Decka keeps a record of each request, with what it sent, as Data retention says.
Live AI in an activity made in Studio. Some activities made in Studio ask an AI model for words or pictures while they run. The host is told so before starting one, with what it costs, and can run it without live AI; a practice run never uses it. Each request sends the activity's own instructions and whatever it passes along with them, which can include what players typed and, in a room that asks for names, their names: for words, to a model Cerebras, Anthropic or Groq runs; for pictures, to Google's Gemini; and for a yes-or-no question about what players typed, to Typesafe AI's system. In a classroom room, or when the host has switched moderation on, Typesafe AI's system checks a request for a picture before it is painted, and the words a model wrote before the activity uses them. Decka keeps a request, and any picture made for it, only as long as the room.
Data retention
We retain your personal information for as long as your account remains active and for as long as is necessary to provide the Services to you. The specifics depend on the category of data.
What we keep until you delete it. Presentations, activities you have opened or edited, templates, drafts you have interacted with, uploaded images, fonts, audio, video, and drawings are retained until you (or your workspace administrator) delete them. We do not run an automatic sweep that removes work you've created. A Decka Studio project, with its whole conversation, its pictures and its files, is kept until the person who made it deletes it or its workspace is deleted, and a project you made in a shared workspace stays with that workspace when you leave it or delete your account. The record each Studio room leaves its workspace is also kept until the workspace is deleted.
What ages out automatically. A small number of categories are removed on a scheduled basis:
- Abandoned drafts — presentations or activities you created but never opened or edited — are cleaned up after 90 days from creation.
- Participant submissions on completed sessions (poll responses, reactions, word-cloud entries, drawings, Q&A submissions, quiz answers) are retained for 3 years from the end of the session.
- Squadrillion answer-review samples expire normally after 14 days, with a configured maximum of 30 days; expired text cannot be read in the review page and is removed by scheduled cleanup. Accepted-answer aggregates and hash-based duplicate-prevention records remain as described above.
- Gift photos are deleted within a day after 90 days from when the first photo of their game was stored. After that, the game's results show the gifts' names only.
- Draw the Suspect mugshots and sketches are deleted within a day after 90 days from when the first image of their session was stored, and when the activity is deleted. After that, the host's report shows names and the witnesses' statements only.
- Mic Drop Daily duel lines, with the record of who wrote each and every pair judged, are deleted 90 days after the prompt's day; only that day's prompt and its counts are kept. An address a result was emailed to is erased once that email has gone.
- Template-personalization signals derived from template searches and opens are scheduled for automatic deletion after 90 days from the interaction. Raw template search text is not stored in this dataset.
- A participant's report address — an address someone gave us so we would email them a copy of a session's results — is erased 7 days after that report is delivered, or 30 days from the moment it was given if the report is never delivered; the address-free record behind the report link is kept for 90 days, the lifetime of the link, and is then deleted. Decka is the controller for this data and the presenting workspace never receives it.
- Marketing send records — which campaign message reached which address, and how that send settled — are kept for 24 months, the same window as our security audit logs, because that record is the compliance trail for the message itself. We delete them sooner when you delete your account or ask us to erase your data.
- First-party email and landing counters — day-bucketed totals carrying no address and no account identifier — are kept for 3 years.
- The private history of how you use Decka, kept for accounts created on or after October 19, 2026, is deleted entry by entry 180 days after each was recorded, and all at once if you turn it off or delete your account.
- A Decka Studio room deletes who joined it and everything they sent, with any picture an AI made for it, about a minute after it ends, with a configured maximum of 24 hours. A room nobody ends ends by itself no later than 12 hours after it started, with a configured maximum of 7 days.
- A Decka Studio project you delete leaves Studio at once, and nothing new can be made from it. The slides and activities already made from it keep working for 60 days; the project and its conversation are then deleted within a day, and its pictures and files by the daily clean-up once 7 days have passed since nothing at Decka used them. If Decka approved a version of it for its library, that version stays in the library, as it does when its workspace is deleted. A note that the project was deleted, and by whom, stays until its workspace is deleted, so a slide that used it can say it was deleted; closing your account removes your name from it.
- Reports of a Decka Studio activity — the keyed fingerprints that make each report count once — are deleted once they are 30 days old, the next time any report reaches us.
- Decka Studio usage records — which build rounds a workspace ran, who ran each and for which project, and what it cost — are deleted 400 days after the round closed. What Studio credits were bought, granted and refunded is kept with our billing records.
- The record of a request from an AI app you build with in Decka Studio, with what the app sent, is deleted 7 days after the request finished. The files it wrote stay with the project.
- A deleted workspace's or project's Decka Studio pictures and files are deleted by a daily clean-up once 7 days have passed since nothing at Decka used them. What an activity approved for Decka's library uses stays with it.
- A Participant's request for how to make an activity — the address is deleted when that one email is sent, and the keyed fingerprints that limit requests are kept for at most 24 hours.
- What you entered into one of our tools before signing up, and which workspace it was then made in, is deleted 7 days after you used the tool.
- A deleted account's identifier, kept so that nothing that reaches us late can recreate the account's data, is deleted 31 days after the deletion is complete, by the next daily clean-up.
- Security audit logs are retained for 24 months.
- Backups roll off after 30 days.
What we keep after account closure. When you close your account, your sign-in identity and any data we are not specifically required to keep are deleted. We retain a small set of records as required to comply with our legal obligations, defend against legal claims, satisfy tax and accounting requirements, and enforce our agreements — most notably, the consent records that show which version of these terms you agreed to, and our billing records. Decka keeps a one-way hash of the email address that started a free Studio trial, after the account is deleted, only to stop the same person taking repeat free trials. An activity you made in Decka Studio that Decka approved for its library stays in the library, and in the decks that use it, after you leave its workspace, close your account or delete its project, and after its workspace is deleted; closing your account removes your name from it.
While a request to delete your account is being completed, we pause the getting-started, marketing and other campaign emails queued for you. Transactional email, such as the report for a session you presented, may still arrive. Once the deletion is complete, which can take about a day, we also keep a record that holds only its identifier for 31 days, so that nothing that reaches us late can recreate what was deleted. It is removed by the next daily clean-up after that.
While an account-deletion request is pending reconciliation, the underlying template-personalization pins and interaction records may remain temporarily, and new personalization writes are blocked. Once deletion is finalized, those records are deleted. The only template-personalization deletion marker that remains is a domain-separated pseudonymous hash used as a tombstone to reject delayed authenticated writes. It is retained for a short access-token safety window of at least 24 hours and then purged by the next scheduled retention sweep.
You may request deletion of your information at any time by deleting your account from your dashboard settings or by contacting us at legal@decka.dev.
International transfers
We may transfer, store, and process your information in countries other than the country in which you reside, including the United States and the European Union. Where the law of the jurisdiction from which the information originates requires specific safeguards for international transfers, we rely on lawful transfer mechanisms recognized by that jurisdiction. These mechanisms may include the Standard Contractual Clauses approved by the European Commission. By using the Service, you acknowledge that your information may be processed in this manner.
Your rights and choices
Depending on where you reside, you may have certain rights with respect to your personal information. These may include:
- the right to access the personal information we hold about you;
- the right to request correction of inaccurate or incomplete information;
- the right to request deletion of your information;
- the right to receive a portable copy of your information in a machine-readable format;
- the right to object to or restrict certain types of processing;
- the right to withdraw consent where we rely on consent to process your information; and
- the right to lodge a complaint with the data protection authority of your jurisdiction.
To exercise any of these rights, please contact us at legal@decka.dev. We may need to verify your identity before responding to your request, and we will respond within the time required by applicable law.
Security
We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security.
Links to Other Sites
Our Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the Privacy Policy of these services or sites. We have no control over, and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.
Underage Privacy
Our Services do not address anyone under the age of 18. We do not knowingly collect personal identifiable information from children under 18. In the case we discover that a child or underaged person (under 18) has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us on legal@decka.dev so that we will be able to do necessary actions.
Changes to This Privacy Policy
We may update our Privacy Policy from time to time. Thus, we advise you to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately, after they are posted on this page.
Contact Us
If you have any questions or suggestions about our Privacy Policy, please contact us at legal@decka.dev.