Privacy Policy

The Creative Archive does not collect personal data as defined in GDPR's Article 4, except when you you explicitly choose to communicate it, in which case GDPR will be respected.

Moreover, the Creative Archive is designed to minimise privacy risks. Here's how!


The Creative Archive is open-source. Do look at the code and if you find any privacy breach or concern, let Pedro PSI know.


Here's the list of third parties the Creative Archive infrastructure relies on. Their respective privacy policies apply to the extent that they are relied on.

Github Pages (Microsoft)

This site is hosted on Github Pages, owned by Microsoft.


Some site features (form and feedback submission, analytics) are managed by the Creative Archive's associated Google account:

Private Communication

When you communicate with the Creative Archive, for instance by email or form submission, this communication is kept private. However, it flows through a Google mailbox and drive so it may stay there for archival purposes as long as Creative Archive runs.

Email subscriptions

The same provisions apply as for private communication. Plus, if you subscribe for Creative Archive emails, the use of your address or any other provided personal data will be restricted to that purpose. All such data is deletable by request, such as when you cancel a subscription.

Minimal analytics

The Creative Archive collects on each page load a minimal amount of non-personal visitor information (detailed below). This information is kept private in a Google account.

If you can suggest how to reach the same purposes while collecting less information, love to know!

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 the Creative Archive can be seen perfectly by all visitors. Do report any bug you find!
referrer url hashtag to compare the impact of different publicising efforts.
a randomly generated word to aggregate all data belonging the same visitor, across multiple pages.


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 see how many attempts per level are made and whether previously unknown solutions were found.
hints used (if available) to see whether and when players need help.
player feedback to improve the game.

Localsave cookies

Each game on the Creative Archive offers the Localsave option, which saves your progress across sessions using up to 3 cookies per game. Conveniently, Localsave is on by default (as stated in each game). However, those cookies can be deleted simply by deselecting the save icon (floppy disk).


Suggestions for improvement of the Creative Archive's Privacy are always welcome!