Last updated 24 September 2026
EPRIS Journal has no accounts, no advertising and no tracking profiles. This page explains, precisely, the small amount of data that does exist and why.
The app collects no personal data at all. There is no sign-in, no account, no advertising identifier, and no analytics, crash-reporting or tracking framework of any kind embedded in it. It does not track you across other companies’ apps or websites.
Everything the app remembers stays on your own device and is never transmitted to us:
You can clear the downloaded photographs and your reading progress at any time in the app’s Settings. Deleting the app removes all of it. Nothing is backed up to us, because we never receive it.
To show the journal, the app fetches its published content and photographs from the journal’s own servers, api.eprisjournal.com and eprisjournal.com. A few articles show photographs or video hosted where they were originally published – for example Wikimedia Commons or Unsplash – and those are requested from that host directly. Articles with a location show a map drawn by Apple Maps. Like any request on the internet, each of these carries your IP address, which the receiving server needs in order to reply; we do not use it to identify you, and the app sends nothing else about you with it.
The website counts page views so the editors know which pieces are being read. This counter is self-hosted – no Google Analytics, no third-party tracker, no advertising network, and no tracking cookies.
For each page view it records the time, the page address, the referring page, the page title, a coarse device category (phone, tablet or desktop), the browser language and screen width, and a salted, truncated cryptographic hash of the IP address. The IP address itself is never stored, and the hash exists only so repeat views within a period can be counted once rather than identifying anyone. It is not used to build a profile and is not shared.
The website loads its typefaces from Google Fonts, and some articles embed photographs, videos or maps from the services where they are published. Your browser contacts those services directly when the page loads. Video embeds do not load until you press play.
Like any web server, ours records requests for security and troubleshooting. These logs may include IP addresses and are retained only as long as they are operationally useful.
If you are invited to answer an interview questionnaire, we store what you actually submit – your written answers and any images you attach – so the editors can prepare the resulting article. Submitting is entirely voluntary, and the form asks for your consent before it is sent. Withdraw it at any time by writing to us and we will delete your submission.
If you choose to support the journal, payment is handled entirely by the provider you pick, such as PayPal or your bank. We never see or store your card details. Those providers apply their own privacy policies.
The journal is a general-audience publication about art, architecture and design. It is not directed at children, and we do not knowingly collect any data from them.
Wherever you live, you may ask what we hold about you, ask for a copy, have it corrected, or have it deleted; if you are in the European Union or the United Kingdom, the GDPR gives you these rights formally, along with the right to complain to your data-protection authority. Because we hold almost nothing, there is usually nothing to export or erase. Where we do hold something you gave us – a questionnaire submission, for example – we will act on your request within 30 days.
If this policy changes, the date at the top of this page changes with it. A change that affects the app will also be described in the app’s release notes.
Questions about privacy, or a request about your data: munister@outlook.com.