Last updated: September 2026
Reading Akavish requires no account and no tracking. We do not sell or share your data for advertising, we do not build profiles of readers, and we do not use advertising cookies. If you create an account, we hold your email address so you can log back in — nothing more.
Akavish is published by Alexandre Sachs, who is the data controller for the purposes of the GDPR. Contact: privacy@akavish.gg. Publisher and hosting details are on the legal notice.
When you simply read the site. Our host records standard server logs, which include your IP address. We measure audience with Vercel Web Analytics, which is cookieless: it counts page views and approximate country without identifying you or following you across sites. If a page fails, an error report is sent to Sentry — configured to exclude your IP address, cookies, headers and any form content.
If you create an account. Sign-up and login are handled by Clerk. It holds your email address and whatever name or avatar you choose to provide. Reader accounts currently unlock nothing beyond being signed in.
If you email us. Messages sent to an @akavish.gg address are forwarded to a personal mailbox through Cloudflare Email Routing. We keep them for as long as needed to deal with your message.
We do not knowingly collect anything from children under 15, the age of digital consent in France.
Akavish sets only strictly necessary cookies, placed by Clerk to keep you signed in and to protect the login form. There are no advertising, profiling or audience-measurement cookies — which is why you are not greeted by a consent banner. You can block cookies in your browser; the site will still work, but you will not be able to log in.
We keep the list of third parties deliberately short. Each one acts on our instructions, for the purpose stated:
| Service | What it receives | Why | Location |
|---|---|---|---|
| Vercel | IP address and request metadata in server logs; aggregated, cookieless page-view counts. | Hosts and serves the website, and provides its audience statistics. | US |
| Clerk | Email address, and any name or avatar you provide. Only if you create an account. | Handles reader sign-up, sign-in and sessions. | US |
| Sentry | Error messages and stack traces, the URL path, browser and operating-system version. Configured to send no IP address, cookies, headers, request bodies or query parameters. | Tells us when a page breaks, so we can fix it. | US |
| Cloudflare | DNS queries for the domain; the content of any email you send to an @akavish.gg address; images served from storage. | Resolves the domain, forwards our email, and stores article images. | US |
| Neon | Article content and editor accounts. No reader data. | Hosts the database behind the site. | EU/US |
| Resend | Editor email addresses only — used for password resets on the admin panel. Readers are never emailed through it. | Sends transactional email for the editorial back-office. | US |
Several of these are based in the United States, so your data may be transferred outside the EEA. Those transfers rely on the European Commission’s Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework.
Serving the site and keeping it secure and working rests on our legitimate interest in running a functioning publication. Your account exists because you asked for it — that is performance of a contract. Where we ever rely on consent, we will ask for it plainly and you will be able to withdraw it.
Server logs and error reports are kept for a short operational period — Sentry retains events for 30 days on our plan. Account data lives for as long as your account does; delete it and it goes. Emails you send us are kept while the conversation is useful.
Under the GDPR you may request access to your data, correct it, delete it, restrict or object to its processing, and receive a portable copy. Write to privacy@akavish.gg and we will answer within one month.
If you are not satisfied with our answer, you may lodge a complaint with your national supervisory authority — in France, the CNIL.
We may revise this policy. The date at the top always reflects the current version, and significant changes will be noted on the site.