Privacy Policy

Placeholder — review with a professional before publishing. Last updated: [date].

This policy explains how Srlaya Studio ("I", "me") handles personal data when you visit this website or get in touch. It is written to align with the EU General Data Protection Regulation (GDPR / AVG). Replace the bracketed sections with your own details.

1. Who is responsible

Srlaya Studio (Niko Ištuk) is the data controller, based in Eindhoven, the Netherlands. You can reach me at hello@srlaya.com. [Add registered business address, KvK number, and BTW/VAT number once available.]

2. What data I collect

Contact data you send me — name, email address, and the contents of your message — when you use the contact form or email me.
Technical data — basic server logs (IP address, browser type, pages visited) if the site is hosted with logging enabled. [Confirm what your host records.]

This site does not use tracking cookies or third-party analytics by default. [Update this section if you add analytics or embedded content.]

3. Why I use it and the legal basis

To respond to your inquiry and provide a quote or service — legal basis: steps taken at your request prior to a contract, and legitimate interest.
To keep the website secure and working — legal basis: legitimate interest.

4. How long I keep it

Inquiry correspondence is kept for as long as needed to follow up, and afterwards in line with applicable bookkeeping obligations. [State your retention period.]

5. Who I share it with

I do not sell personal data. Data may be processed by service providers I rely on, such as my email and hosting providers. [List processors once chosen.]

6. Your rights

Under the GDPR you can request access to, correction of, or deletion of your personal data, object to processing, and request data portability. To exercise any of these, email hello@srlaya.com. You may also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or the Croatian Personal Data Protection Agency (AZOP).

7. Changes

I may update this policy. The current version always appears on this page with its revision date.

← Back to home