Privacy policy

Last updated: 2026-10-05

This page explains what personal data Martialis (martial.is) collects, why, and what rights you have over it. It covers two different things: the account-related parts of the site (sign-in, settings, the monthly updates newsletter), and the personal data of living people recorded in the public lineage database itself (names, dates, photographs, teacher/student relationships). These have different legal bases and are covered separately below.

Who is responsible for your data

Martialis is operated by Frederico Muñoz, Lisbon, Portugal, contactable at [email protected]. This is the “controller” for the purposes of data protection law.

Part 1: Account data

What we collect

We do not collect payment information, browsing history across other sites, or any special category of data (health, religion, etc.).

Cookies

Martialis uses a small number of cookies, all of them strictly necessary to make the site work:

Cookie Purpose Lifetime
martialis_session Keeps you signed in Tied to your session
martialis_pkce Secures the sign-in handshake 30 minutes
martialis_pending_consent Carries your newsletter choice through sign-in 30 minutes
lang Remembers your language choice 1 year
focus Remembers your default lineage focus person 1 year

None of these are used for advertising or cross-site tracking, so no cookie consent banner is shown: none is required for strictly necessary, functional cookies under EU law.

Why we process this data

We do not put account creation, sign-in, or suggestion handling under consent: those run on the contract and legitimate-interest bases above, so they do not stop working if you decline the newsletter.

Who else processes this data

We use a small number of external providers (“processors”) to run the site:

Processor Role
Supabase Authentication and account/database hosting. Sign-in emails (magic links) are delivered through Supabase's configured mail sending, currently Scaleway Transactional Email Manager.
Brevo Delivery of the monthly updates newsletter, if you opt in. Not used for sign-in emails.
Zoho Correction/suggestion and identity-claim requests are emailed to the maintainer's mailbox for review (see above): your display name always, and your email address only if you opted in – except for an identity claim, where the address is required so we can reply.
Cloudflare Access door to the website, sees connection metadata for every request.
Stripe Processes donations, if you choose to make one (see “Donations” below).

Data processing agreements are in place or being put in place with each of these; the underlying hosting infrastructure is not itself a data processor for personal data covered by this policy.

We do not sell your data, and we do not share it with anyone for their own marketing purposes.

Supabase, Brevo, and Hetzner resources are all in EU-located regions.

Donations

Support Martialis links to Stripe Payment Links, hosted entirely on Stripe's own pages. We never receive or store your card details. If you answer the optional question about being listed as a supporter, that answer (and the name you give, if any) is stored by Stripe, not by us; there is no supporter list today, but if one is added, only “yes” answers would be used. To withdraw that answer, or ask what was recorded, contact [email protected].

How long we keep your data

We keep your account data for as long as your account exists. If you delete your account (Settings > Delete my account), your account and its associated preferences are deleted immediately and permanently. Server request logs are kept only briefly (days, not months) and then rotated out. Submitted corrections are described above.

If you set a public handle (@handle), it can never be claimed by anyone else once it has been used – including by you again after deletion – because a handle sitting next to lineage claims could otherwise let someone impersonate a deleted account. To make that permanent restriction possible without keeping your handle or email on file, we keep only a one-way salted hash of the handle, indefinitely, plus a one-way salted hash of your email as the sole evidence for a manual, discretionary request to reclaim it later. Neither value is stored as plain text, and a copy of the hashes alone cannot be turned back into your handle or email; nothing reads the email hash automatically.

International transfers

Our processors may process data outside the EEA (for example, on sub-processors' infrastructure). Where that happens, it relies on that processor's own Standard Contractual Clauses or equivalent safeguard; we do not transfer your data to a third country ourselves, beyond what is involved in using these processors' services.

Part 2: Personal data in the database

The lineage database itself is about people, most of them historical, some living. For a living person recorded in the database – a name, dates, places, photographs, teacher/student relationships, ranks, and training venues – different rules apply than for site accounts, because this is third-party personal data collected from public and cited sources, not data the person gave us directly.

This is separate from, and in addition to, the copyright and database-rights notice covering the database as a body of work; see Licensing.

Your rights (account data)

You have the right to:

To exercise any of these rights beyond the self-service options above, contact us at [email protected].

Age

Registration requires you to be at least 13 years old (the age set for Portugal under Lei n.º 58/2019, transposing GDPR Art. 8, though since account creation here relies on contract rather than consent as its lawful basis, Art. 8 does not strictly apply). We do not knowingly collect account data from anyone younger.

Changes to this policy

We may update this policy as the site evolves. Material changes will be reflected here with an updated date, and, where they affect the newsletter, may prompt us to ask for your consent again. As of 2026-09-10: correction/suggestion submissions no longer go through GitHub – a git history can't be properly erased, which conflicted with your right to erasure. They are now emailed directly to the maintainer and are kept only until triaged, after which the email is deleted.

Contact

Questions about this policy or your data: [email protected].