Privacy, in plain language

Amazigh History is published by Danny Rasul, who is responsible for the website’s own processing of personal information. Use the private contact form for privacy questions or requests. A public email address will only be added after its delivery has been confirmed.

Configuration described here: 5 October 2026. This notice describes the current website, not services we might add later.

Reading without an account

You do not need an account to read, use the atlas or practise writing. Requests reach our hosting provider, Hostinger. Delivering and securing the website can involve your IP address, requested URL, browser information and request time in server/security logs. We use hosting for the legitimate interests of operating and protecting the publication, not to build advertising profiles.

Hostinger processes data under its hosting terms and privacy information. Account-specific log retention and processing locations still require confirmation with the hosting account; we do not claim an unverified deletion period or that all processing stays in the UK. Ask through Contact for information about the actual account arrangements.

Advertising and optional measurement are paused

The Google AdSense script and the separately hosted portfolio analytics tracker are disabled on public pages during the configuration review. There are no advertising or analytics consent switches here that secretly enable them. A Google verification meta tag and ads.txt remain; these identify the publisher account and do not themselves request an ad or execute tracking code.

Earlier versions loaded AdSense and a tracker at ivory-chough-853879.hostingersite.com. Pausing them does not erase data already held by those services. The tracker’s controller, collection and retention are being reviewed before any reactivation. Advertising will require a suitable verified consent implementation and an updated notice. No visitor numbers or revenue are claimed here.

Saved names and reading progress

When you choose to save a name, article or reading progress, the website stores record IDs and preference state in this browser’s local storage. These features are requested by you; the publication does not upload your saved lists to an account. They remain until you clear them or your browser removes them. Blocking storage should leave the content readable, although saves may last only for the current page.

A shared shortlist puts selected record IDs in the link’s fragment. Anyone who has that link can see the selected names. Do not treat a shared link as secret. Importing it requires a choice; it does not automatically replace another list. Downloaded or printed copies are under your control.

The Tifinagh notebook keeps its text in the open page, not in our database or persistent browser storage. Copying text uses your device’s clipboard. Leaving or reloading the page can lose the notebook. Fonts are hosted with this site rather than requested from Google Fonts.

Manage this browser’s saved data

Corrections and other messages

The contact form stores your topic, page reference, message and optional reply email in a private queue on our hosting account. It does not publish your message or subscribe you to marketing. Please avoid sensitive personal information, children’s details and information about other people that is not needed to explain the issue.

We use the information to investigate and respond to enquiries and maintain accurate content, based on those legitimate interests. Only the publisher and authorised hosting maintainers should access the queue. An email is optional; without one we cannot send a personal reply. Submissions are not passed to an AI service automatically.

The application removes submissions older than 90 days when the enquiry queue is used. Hosting backups can retain earlier copies under the account’s backup policy. A correction’s non-personal factual substance and public correction note may remain with the article. Rate limiting uses a keyed hash of the requesting IP for a one-hour limit window. Expired rate-limit records are removed on a later successful submission; without another submission they can remain stored. The form’s own database does not store a raw IP. The hosting provider may separately log the request.

Essential security

The contact form uses a short-lived session cookie for anti-forgery protection. The private owner studio uses a separate secure session cookie, password hashing, access checks and rate limits. Public readers cannot create studio accounts. Editorial records and messages are stored outside the public web directory.

Your choices and rights

You can clear local saves, avoid submitting an email and ask about access, correction, deletion, restriction or objection concerning information held about you. Which rights apply depends on the circumstances; we may need enough information to locate a message or verify a request. Include your submission reference where available. You can raise a concern with the UK Information Commissioner or your relevant local authority.

External source links and recordings open services with their own policies. There are no children’s accounts, paid memberships or newsletter sign-ups on this site. Material changes to these arrangements will be reflected here before the new service is enabled.