site.name does not collect //personal data// as defined in [Article 4|https://gdpr-info.eu/art-4-gdpr/], except when you **you explicitly choose** to communicate it, in which case [GDPR|https://gdpr-info.eu] will be **respected**.
Moreover, site.name is designed to minimise privacy risks. **Here's how**!

## Inspectable
All the code in site.name can be inspected, e.g. use [[Ctrl U]] to view the source or [[ctrl shift I]] to open the default inspector on most browsers. Do look at the code, and if you find any concern, @@@ please let site.author know @@@.

## Transparent
Here's the list of third parties site.name infrastructure relies on. Their respective privacy policies apply to the extent that they are relied on.

### Netlify
The site is served from //Netlify//.

### Microsoft Github
The site source is hosted on //Github//, owned by //Microsoft//.

### Google Apps Script
Some site features are managed by site.name's associated //Google// account:
- [hall of fame]
- [guestbook|contacts]
- feedback submission
- [#analytics]

## Email
If you choose to provide your email, it will be kept private and not used to spam you.
Plus, if you subscribe to any announcement or newsletter, you can [unsubscribe forever anytime|contacts] -- your data will be deleted.


## Analytics

Currently, analytics are ${Switchl("UrlAnalyticsed")}.

site.name collects on each page load a minimal amount of non-personal visitor information
If you can suggest ha way to reach the same purposes while collecting less information, site.author @@@ would love to know @@@!


### In-page

The following data is collected on page load:

DATA TYPE					PURPOSE
language + timezone			to estimate the geographic distribution of visits
date + time + timezone		to understand which times of the year, month, week and day are more popular. To see how new content is received by the public
screen size + user agent	to know whether site.name can be seen perfectly by all visitors. Do [report any bug|contacts.html] you find!
referrer					to compare the impact of different publicising efforts
a randomly generated word	to prevent double counting, across multiple pages

((Page analytics))

### In-game

[Puzzlescript games|puzzlescript/index.html] collect the following per-level data:

DATA TYPE					PURPOSE
level tried or beaten		to know how many players try vs beat the game and thus estimate difficulty
level timing				to understand which levels are harder to beat, and find gameplay bottlenecks
move sequence				to find unintended solutions and possibly some bottlenecks
hints used 					to see whether and when layers need help
player feedback				to improve the game
((Game analytics))

In addition, they offer the option to erase your progress (by default saved across sessions in the browser's local storage), by deselecting the localsave button ([[save]]).

## More...
Suggestions for improvement of site.name's Privacy are @@@ always welcome @@@!