Brooks Studio

Privacy Policy

(central for main website & all linked projects)


Controller (Art. 4 No. 7 GDPR)

Kirill Bobrov (also: “Kyle Brooks”)
Volksdorfer Grenzweg 139
22359 Hamburg, Germany
Email: official@kylebrooks.me


1) Scope

This privacy policy applies to my personal website as well as to all publicly accessible projects and demos linked from it (collectively referred to as “Services”), provided these projects reference this policy in their footer or description. If an individual project processes additional data (e.g. user accounts, analytics, payment systems), it will be specifically explained on that project’s page.


2) Types of Data Processed / Sources

- Usage and technical data: IP address, timestamp, requested resource/URL, referrer, browser, operating system (server logs).
- Communication data: contents of an email, sender address, metadata.
- Feedback data (only if a project provides a form): free text, optional name/email; transmitted to GitHub (issues).
- Content and embedding data (only for embedded content): when loading external content (e.g. YouTube), technically required data is transmitted to the respective provider.


3) Purposes and Legal Bases (Art. 6(1) GDPR)

- Operation, security, and error analysis of the services (server logs, cron jobs): legitimate interest (Art. 6(1)(f)).
- Communication / support by email or feedback: contract / initiation (Art. 6(1)(b)) and/or legitimate interest (Art. 6(1)(f)).
- Embeddings / convenience functions (e.g. videos): depending on configuration, legitimate interest (Art. 6(1)(f)) or consent (Art. 6(1)(a)).
- Cookies / tracking (if used in the future): consent (Art. 6(1)(a)); revocable at any time with effect for the future.


4) Hosting & Server Log Files (Vercel)

The services are hosted by Vercel Inc. When accessed, server log data is automatically processed (IP address, date/time, requested file/URL, referrer, browser/OS). Purpose: service delivery, stability, security, and prevention of misuse (Art. 6(1)(f) GDPR). Log data is generally stored only briefly and then deleted or anonymized. Vercel stores data in EU data centers and only transfers data to third countries when necessary.

Privacy policy: Vercel Privacy Policy


5) Scheduled Tasks (Vercel Cron Jobs)

For maintenance and automation, Vercel Cron Jobs call server-side endpoints at defined intervals. Technical log data such as IP, timestamp, and user-agent may be recorded; personal content is not processed. Legal basis: legitimate interest (Art. 6(1)(f) GDPR).


6) Contact by Email

When contacting me by email, the provided data (address, content, metadata) is processed to handle your inquiry (Art. 6(1)(b/f) GDPR). The data will be deleted after the communication is completed unless legal retention obligations require otherwise.


7) Feedback Forms → GitHub Issues (project-dependent)

If a project provides a feedback form, the entered data is transmitted server-side to GitHub to create an issue in the respective repository.

- Recipient / controller: GitHub, Inc. / GitHub B.V. (independent controller).
- Visibility: Issues in public repositories are visible worldwide – please do not include sensitive data.
- Legal basis: Art. 6(1)(b) (handling of request) and Art. 6(1)(f) (quality assurance, prevention of misuse).
- Deletion: Upon request, I delete or archive the issue; GitHub backups may persist independently.

Privacy policy: GitHub Privacy Statement


8) Cookies, Local Storage & Analytics

By default, the services do not use tracking cookies or any third-party tracking; fonts and scripts are served locally. If individual projects later use cookies or similar technologies (e.g. analytics), I will inform users in advance and obtain consent where required.


9) Embedded Content (e.g. YouTube) & External Links

Some pages may embed external content (e.g. videos). When loading such content, the provider receives usage data (e.g. IP, user agent). I strive to use privacy-friendly embedding methods (e.g. “Click to Load”). For external links, the respective site’s privacy policy applies; I have no influence over their content or data handling.


10) Recipients / Categories of Recipients

- Hosting / operations: Vercel (servers, logs, cron).
- Issue management (optional, project-dependent): GitHub (issues as feedback channel).
- Other recipients: only if explicitly named in a specific project.


11) Data Transfers to Third Countries

Vercel and GitHub are providers based in the USA. When data is processed or transferred to third countries, appropriate safeguards are used (e.g. EU–US Data Privacy Framework, Standard Contractual Clauses, or equivalent mechanisms). Details can be found in the providers’ privacy policies.


12) Storage Duration

Data is stored only as long as necessary for the respective purposes or as required by law. Afterwards, data is deleted or anonymized. Examples:
- Server logs: short-term, purpose-bound.
- Emails: until the request is resolved; subject to statutory retention periods.
- GitHub issues: until resolved or upon request; GitHub backups remain independent.


13) Obligation to Provide Data / Automated Decisions

There is no legal obligation to provide personal data unless necessary in a specific case (e.g. to respond). No automated decision-making including profiling takes place (Art. 22 GDPR).


14) Security

I implement technical and organizational measures (TOMs) to protect data from loss, misuse, and unauthorized access, including TLS encryption (HTTPS). However, absolute security cannot be guaranteed.


15) Data Subject Rights (Art. 15–21 GDPR)

You have, in particular, the following rights:
- Access, rectification, erasure, restriction, data portability, and objection to processing based on Art. 6(1)(f).
To exercise these rights, simply send an informal email to: official@kylebrooks.me

Right to lodge a complaint: You may contact a supervisory authority, for example, the Hamburg Commissioner for Data Protection and Freedom of Information (HmbBfDI).


16) Changes to this Privacy Policy

I update this policy when services, legal requirements, or providers change. The current version is always available here; in case of significant changes, I will provide additional notice.

Last updated: October 2025