Privacy

Finn Dudek, trading as kaumstudios, Müllerstrasse 138d, 13353 Berlin, Germany. Email: contact@kaumstudios.com. Finn Dudek operates this website and manages enquiries. This notice explains processing when you visit kaumstudios.com or contact us.

Cloudflare provides hosting, content delivery and protection against abusive traffic. To deliver a page, its infrastructure receives your IP address, request time, requested address, browser information and technical connection data. Request and error information may be recorded to diagnose faults and protect the service. Our interest in operating a secure, reliable website is the basis for this processing under Article 6(1)(f) GDPR.

Application contact-event logs record technical status and a request identifier rather than the message text or sender email address. Infrastructure logs can nevertheless contain connection and request data. Operational records are kept for the period needed to investigate faults or abuse and then removed under the applicable provider retention schedule. Records needed for a specific security incident or legal obligation may be retained for that purpose.

We use Sanity to manage website content and deliver images, and Mux to deliver videos and video thumbnail images. Your browser connects to these services when the relevant media is loaded. They receive the IP address and technical request information needed to return the asset, such as its address, request time and browser information. A video thumbnail also creates a request to Mux, even before playback starts.

The purpose is to present our portfolio and deliver media efficiently, based on Article 6(1)(f) GDPR and our interest in showing our work through a functioning website. Technical delivery records are retained according to the providers’ operational and security requirements, rather than as a separate marketing profile created by us.

We offer selected videos through YouTube, a Google service. For users in the European Economic Area, Google Ireland Limited is responsible for Google’s processing under its privacy policy. We use the privacy-enhanced player at youtube-nocookie.com. No YouTube player or thumbnail is requested until you choose “Load YouTube video”.

After activation, Google receives your IP address, our website’s origin, browser and device information, and information about playback and interactions. Cookies or similar storage may be used once the player is loaded. Privacy-enhanced mode does not mean that no personal data is processed. Google describes its purposes, account-related processing, retention periods and international transfers in its privacy policy: https://policies.google.com/privacy.

Our activation of the optional player is based on your consent under Article 6(1)(a) GDPR and, where device storage or access requires consent, § 25(1) TDDDG. You can withdraw activation for that player by choosing “Close YouTube”, which removes it and stops further requests from that embedded player. Withdrawal does not undo processing that has already occurred or delete data held by Google. We do not remember your choice across page reloads. The rest of the website works without loading YouTube; the separate “Watch on YouTube” link opens YouTube’s own website.

We offer selected TikTok videos to illustrate our projects. For users in the European Economic Area, TikTok Technology Limited (Ireland) and TikTok Information Technologies UK Limited are the joint controllers identified in TikTok’s privacy policy. We do not request TikTok players, thumbnails or scripts until you choose “Load TikTok video”.

After activation, TikTok receives your IP address, our website’s origin, browser and device information, and playback and interaction data. TikTok may use cookies or similar technologies and associate this activity with information it already holds about you, including account information. TikTok describes its own purposes, retention and international processing in its privacy policy: https://www.tiktok.com/legal/page/eea/privacy-policy/en. Processing may take place outside the European Economic Area.

Our activation of the optional player is based on your consent under Article 6(1)(a) GDPR and, where required for device storage or access, § 25(1) TDDDG. “Close TikTok” removes the player and stops further requests from that embedded player. This does not undo prior processing or delete data held by TikTok. We do not remember your choice across page reloads. You can use the rest of the website without loading TikTok; “Watch on TikTok” opens TikTok’s own website.

If you email contact@kaumstudios.com, we process your address, name, message, attachments and any other information you provide to respond and discuss your project. We use Google Workspace for receiving, sending and storing this correspondence.

For enquiries about a contract with you personally, the basis is Article 6(1)(b) GDPR. For communications with a company’s representatives or other business contacts, the basis is Article 6(1)(f) GDPR and our interest in responding to business enquiries. Information required by tax or commercial law is retained under Article 6(1)(c) GDPR.

Providing information is voluntary. We need a reply address and enough information about your enquiry to respond; without these we may be unable to help. Please avoid sending sensitive personal information that is unnecessary for your project.

The contact form processes the details you enter, including your name, email address, company or project information, selected services and message. Cloudflare Email Service delivers the enquiry to our Google Workspace inbox. The website does not maintain a separate database of enquiry messages.

To protect the form from automated abuse, Cloudflare Turnstile loads when you open it. Cloudflare receives technical signals including your IP address, browser information, TLS connection characteristics and the site origin. We also send the IP address with the server-side verification request. We use this processing to protect the requested contact service under Article 6(1)(f) GDPR.

Cloudflare acts as a processor when protecting our form and as a separate controller when using signals to improve its bot detection. Its Turnstile privacy notice explains that additional processing and how to exercise rights with Cloudflare. You can contact us by ordinary email instead of using the form.

We normally delete an unsuccessful enquiry six months after it is closed, unless it is subject to a statutory retention obligation or is still needed to establish, exercise or defend a legal claim. This is not a blanket deletion rule for business records.

Qualifying commercial and business correspondence is generally retained for six years, accounting vouchers and invoices for eight years, and books and annual accounts for ten years, where the relevant statutory duties apply. These periods generally run from the end of the relevant calendar year; tax proceedings or other legal circumstances can extend them. We restrict further use of records kept only to meet such duties.

Deletion from our working mailbox does not mean every provider backup disappears immediately. Google’s data-processing terms provide for deletion from its systems after an applicable deletion instruction as soon as reasonably practicable, subject to a maximum of 180 days and legal exceptions. Any applicable recovery, archive or legal-hold settings must also be respected.

When you successfully unlock password-protected work, the website sets the cookie __Host-ks_content_access to remember that access for up to 30 days. It is a secure, HttpOnly cookie in production, with SameSite=Lax. Its purpose is access control, not advertising. You can remove it through your browser settings and then unlock the work again.

Animation quality adapts to rendering performance while the page is open. The resulting quality settings are held only in memory for the current page lifetime; the website does not store them in cookies or local storage for later visits, or send them to an analytics service.

Storage and access on your device are governed separately by § 25 TDDDG. Strictly necessary access-control storage can fall within its exception for a service you expressly request. Non-essential storage requires consent; a legitimate interest under the GDPR alone does not replace that requirement.

On the public website, we use Plausible Analytics, provided by Plausible Insights OÜ in Estonia, to understand which pages are useful and where visits come from. Analytics is disabled on our maintenance page, local development and preview environments.

Plausible processes page addresses, referral sources and campaign parameters, browser and operating-system information, device type, approximate location and engagement measurements such as time and scroll depth. It does not set analytics cookies or store persistent visitor identifiers in your browser. We remove unrelated query parameters and URL fragments before transmitting page addresses and remove query parameters and fragments from referrers. We also count when the contact form is opened, an enquiry is started, an enquiry is successfully submitted, an email link is clicked or our email address is copied. These events contain fixed action names and page context, not contact-form contents, names, email addresses, selected services, budgets or submission identifiers. We use pageviews and these events to understand navigation paths and where visitors leave before sending an enquiry. Automatic form, download and general outbound-link tracking remain disabled.

Like other web requests, analytics requests contain an IP address and User-Agent. Plausible uses these temporarily to derive approximate location and a daily identifier using a rotating salt. According to Plausible, the raw IP address and User-Agent are not stored; salts are deleted every 24 hours. The identifier is specific to the website and does not link visitors across days or other websites. Event and session records are used to produce aggregate statistics.

The purpose is to measure use of our portfolio and improve its content, based on our legitimate interest under Article 6(1)(f) GDPR. Plausible processes and stores visitor analytics within the European Union on EU-owned infrastructure under its data-processing agreement. Analytics records are retained for historical reporting while the service is used, subject to our deletion instructions and the provider’s account and subscription deletion rules. For further information, see https://plausible.io/data-policy and https://plausible.io/dpa. You may object to processing based on our legitimate interest by contacting us.

Pirsch and Google Analytics are not integrated into the website application. Cloudflare hosting and security statistics are separate from Plausible. We do not use enquiries to subscribe you to marketing emails.

Links to external websites, including social platforms, take you to services operated by others. Their processing is governed by their own notices. We will update this notice when relevant processing changes.

We use Sentry, provided by Functional Software, Inc. in the United States, to detect and fix technical errors and performance problems in the website. Our organisation uses Sentry’s European Union data-storage region. Monitoring is enabled for the production website; local development and preview environments are excluded. Browser monitoring is inactive on the maintenance page, although unexpected production-server failures may still be reported.

Our error-reporting configuration sends technical exception types, fixed diagnostic categories and recognised framework error codes, JavaScript stack locations, event timestamps and deployment/release information. Error reports also include the capture type, browser or server context, broad source categories such as our application, external scripts or browser extensions, whether a stack trace is available, route groups such as /services or /work/[slug], coarse browser family and mobile/desktop classification, and a fixed marker distinguishing our application code from unmarked scripts. We derive diagnostic labels in memory and do not transmit original arbitrary error messages, external script addresses or browser-extension identifiers. Stack locations retain only our deployed application JavaScript file locations and line/column positions; arbitrary function names and source-context text are removed. Before sending an error event, we also remove form contents, request bodies, cookies, request headers, full page addresses, URL query parameters, visitor identifiers and browsing breadcrumbs. We also sample 20% of browser performance traces to measure page loading, navigation, responsiveness, layout stability, resource timings and long tasks or animation frames where supported. For these sampled traces, we also record fixed section and loading-stage labels, graphics-preparation durations and outcomes, rendering-fallback and graphics-context-loss categories, and brief summaries of animation-frame delays and long tasks while a section is visible. We take at most one visible measurement window of up to eight seconds per section category for each sampled navigation, ending it earlier if the section leaves view, the tab is hidden or navigation starts. Within these windows, native-video playback measurements can include time until a frame is available, buffering counts and duration, and changes in dropped and total frame counts where supported. We limit these diagnostics to 48 records per sampled navigation. These diagnostics exclude video addresses, DOM text and selectors, and do not record image frames or continuous interaction histories. These performance records contain numeric measurements, timestamps, deployment information, coarse browser family and mobile/desktop classification, route groups such as /services or /work/[slug], and short-lived technical trace identifiers. They exclude full page and resource addresses, URL parameters, form data, DOM element details and the original User-Agent string. Network-request tracing and links between successive traces are disabled. Session Replay, persistent session tracking, profiling and log collection are not enabled. These monitoring integrations do not set cookies or write visitor identifiers to browser storage.

As with any network request, Sentry receives the connecting IP address to deliver the service. We have enabled Sentry’s setting to prevent IP addresses from being stored in error events, together with server-side data scrubbing and enhanced privacy controls. Our performance integration also instructs Sentry not to infer IP addresses or User-Agent information into performance records. Under our current account plan, error events are retained for 90 days and performance trace records for 30 days. Retention is determined by the plan active when data is received. Issue and release metadata can remain for ongoing fault management under the service’s retention rules.

The purpose is reliable, secure and efficient operation of our website, based on our legitimate interest under Article 6(1)(f) GDPR. Sentry processes data under its Data Processing Addendum. EU storage does not exclude access or processing outside the EU by Sentry and its subprocessors. Applicable transfer safeguards are described in the addendum, including the EU–US Data Privacy Framework where applicable and Standard Contractual Clauses. Further information: https://sentry.io/legal/dpa/ and https://sentry.io/privacy/. You may object to processing based on our legitimate interest by contacting us.

The recipients described above include Cloudflare, Sanity, Mux and Google Workspace, together with their infrastructure subprocessors. They may process data outside Germany or the European Economic Area, including in the United States. These services should not be understood as a promise of EU-only processing.

International transfers require an applicable safeguard under Chapter V GDPR. Depending on the recipient and service, this can be an adequacy decision under Article 45 or contractual safeguards such as the European Commission’s standard contractual clauses under Article 46. The applicable provider data-processing terms describe these mechanisms and subprocessors. Contact us for information about the safeguards relevant to your data and a copy where available.

Subject to the applicable legal conditions, you may request access, rectification, erasure, restriction of processing and data portability. If processing is based on consent, you may withdraw it at any time without affecting the lawfulness of earlier processing.

Where we rely on Article 6(1)(f) GDPR, you may object on grounds relating to your particular situation. If data is processed for direct marketing, you may object at any time without giving reasons. Send requests to contact@kaumstudios.com.

You may complain to a data-protection supervisory authority, particularly where you live or work or where an alleged infringement occurred. The Berlin authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin; mailbox@datenschutz-berlin.de.

We do not use your enquiry for automated decisions that produce legal or similarly significant effects under Article 22 GDPR.

Last updated: 24 October 2026.