Privacy notice

Last updated: 11 October 2026

1. Controller and contact

The operator below is responsible for personal information they receive and decide how to use. GitHub also processes technical data for its own hosting and security purposes as described in its statement.

Legal name / business name

[aqui tu informacion personal]

Contact email

[aqui tu informacion personal]

Postal address for legal notices (including country)

[aqui tu informacion personal]

Tax identification number, where required

[aqui tu informacion personal]

Registration details, if applicable (otherwise state “Not applicable”)

[aqui tu informacion personal]

2. Data and purposes

The studio does not add visitor analytics, advertising pixels, fingerprinting, mailing-list software or profiling. It does not buy personal information or use download details for advertising. There is no automated decision-making with legal or similarly significant effects. Supplying an email is voluntary and is not required to download a drawing. Without contact information, an enquiry may not be answerable.

3. Legal bases

For correspondence handled by the operator, the basis under EU GDPR Article 6(1)(f), and UK GDPR where applicable, is the legitimate interest in answering requests, keeping the service secure and resolving issues, subject to the individual’s rights and reasonable expectations. Records necessary to meet a specific legal obligation rely on Article 6(1)(c). Handling legal claims may rely on legitimate interests and applicable legal requirements. Visiting a page is not consent to marketing. GitHub’s own legal bases for its processing are set out in its privacy statement.

4. Recipients and service providers

The public host is GitHub. If you email the operator, the operator’s email provider will process the message; authorised professional advisers or competent authorities may receive relevant information when necessary for a legal matter. The operator does not publish incoming messages or sell personal data. The email service provider and its privacy notice must be identified here:

[aqui tu informacion personal]

5. International processing

GitHub operates internationally and may process information outside the EEA or UK. Its statement explains the jurisdictions and transfer mechanisms it uses, including applicable adequacy frameworks and contractual safeguards. See GitHub’s privacy statement. The operator’s email provider, processing locations and applicable transfer safeguard, if any, must also be recorded here:

[aqui tu informacion personal]

You may contact the operator for further information and a copy of applicable safeguards, subject to lawful redaction. This notice does not claim that all data remains in Europe.

6. Retention

The operator keeps ordinary enquiries only for as long as needed to answer them and complete necessary follow-up, then deletes them or removes identifying details. Records connected with an unresolved dispute, rights request or legal obligation may be kept for the relevant statutory period or until the matter and any applicable claim period end. Provider-operated security logs and backups follow the provider’s own retention practices; the operator does not set or promise a retention period for GitHub’s logs.

7. Your rights

Where the relevant law applies, you may request access, correction, deletion or restriction, and data portability where its conditions are met. You may withdraw consent for any future consent-based processing without affecting prior lawful processing.

Right to object: You may object to processing based on legitimate interests for reasons relating to your situation. We must consider the objection under the applicable rules; some records may lawfully need to be retained.

Send requests to the operator’s contact email. Provide only the information reasonably needed to identify the records and verify the request. EU and UK GDPR requests are normally answered within one month; a lawful extension of up to two further months will be explained within the initial period. Requests are generally free, subject to applicable exceptions. For data controlled independently by GitHub, use its privacy contact channels.

You may complain to the Spanish Data Protection Agency (AEPD), another competent EEA supervisory authority, or the UK Information Commissioner’s Office where applicable, without first contacting us.

8. Children

The drawings are designed for children, while downloads and printing can be managed by parents and teachers. We do not ask children to register, submit artwork, send photos or provide personal information. Technical information needed to deliver and secure the site is still handled by the host. The operator does not use it to build children’s profiles or for behavioral advertising.

Do not send a child’s personal details, image, voice, location or school information by email. If the operator learns that unnecessary information about a child has been received, they will remove it, except where a specific legal obligation requires retention. Parents or guardians may contact the operator about information concerning their child.

No blanket age disclaimer replaces duties under US COPPA, EU/UK data protection or other applicable children’s privacy rules. Before introducing data collection, advertising, accounts, uploads or social features, the operator must assess age-related safeguards and any parental notice or verifiable consent requirements.

9. US and other visitors

The operator does not sell personal information or share it for cross-context behavioral advertising. State and national privacy rights apply where their legal scope and thresholds are met; this notice does not claim that the operator meets every US state-law threshold. You may contact the operator to request access, correction or deletion where available. Exercising a privacy right will not affect access to the free drawings.

10. Security and updates

HTTPS and the hosting platform’s security measures protect delivery. No website or email system can guarantee absolute security. Please avoid sending confidential or sensitive information. If data uses or providers change, the notice will be updated before the new processing begins, with additional notice or consent where required.