Privacy

DXNA (https://dxna.dev) lists what developers write on their own blogs. Akeem Philbert runs DXNA, personally. This page says what DXNA keeps about you, why, who else handles it, how long it is kept, and how to have it removed. Questions: hello@dxna.dev.

What DXNA keeps

When you sign in with GitHub, DXNA asks GitHub for read-only access to your email addresses and keeps one: the address GitHub marks as primary and verified. DXNA keeps no GitHub password or token. It reads your public repositories and stars to suggest stacks, and keeps the stacks it suggested and how many repositories led to each.

DXNA keeps what you have read, when you last looked, and the stacks you chose, so it can show you what is new.

If DXNA lists your blog, DXNA may send you one email inviting you to claim it. DXNA finds the address in your feed or on your site, and keeps it only after the email is sent. It also keeps a scrambled form of the address, so it never sends that address a second invitation. The invitation has a link to remove your blog from DXNA. If you claim a blog, DXNA reads its home page once, when you claim it, to find your badge there, and sends you no email about your claim.

If you delete your account on the Account page, DXNA erases your account, your reading and your stacks at once. Some things stay. If DXNA invited you to claim a blog, it keeps that address until the blog is removed from DXNA, and keeps the scrambled form after that, so you are not invited again. Log lines naming you stay until they age out (30 days by default), and database backups holding your record stay until they rotate (7 days by default).

DXNA shows no ads and uses no third-party tracking.

The rest, in detail

If you read DXNA without signing in

DXNA sets no cookie and keeps no record of what you read. Like any website, the servers DXNA runs on record each request (your IP address, your browser's name and the page you asked for) in logs. Those logs age out on Google Cloud's default, about 30 days.

If you sign in

Readers sign in with GitHub. DXNA also keeps:

DXNA keeps these until you delete your account.

DXNA uses your email address only to write to you about a blog you claim. The one exception: if a breach puts your data at risk, DXNA tells you at that address (see "Security"). DXNA sends no newsletter and no marketing email.

To suggest stacks, DXNA counts how many of your public repositories, the public repositories of your organizations and the repositories you starred name each stack. It keeps the counts, not the list of repositories. DXNA also reads the website on your GitHub profile, to offer you a blog of yours that it lists. It does not keep the website.

If your GitHub profile names a website, DXNA reads that address each time you sign in. If DXNA does not list that blog yet and the blog meets DXNA's rules, DXNA adds it to the directory and offers you a way to claim it. DXNA keeps which blog it offered you, not the address.

If you suggest a blog, DXNA keeps the address you suggested and which account suggested it until Akeem reviews it. After the review DXNA keeps the address and the decision, not who suggested it.

If you claim a blog

To check your claim, DXNA reads your site's home page when you claim it, and looks for your badge there. It does not look for the badge again. DXNA keeps a record of your claim: the blog, your GitHub username and account number, the way the claim was checked, and when.

When you open a claim page, DXNA makes a badge ID for your account. It is public: it appears in your badge's address. DXNA deletes it when you delete your account.

Once your claim is confirmed, your blog's page on DXNA shows your GitHub username, and DXNA shows the name you choose with your posts. Both are public. If you delete your account, DXNA releases your claim and stops showing them. Search engines can keep an old copy for days or weeks after that.

If DXNA lists your blog

DXNA reads your blog's public feed. For each post it shows the title, a short excerpt from your feed (the first sentence of the post's summary, or of the post, at most 280 characters), your name as your feed gives it, your domain and the date, with the link your feed gives for the post, which is usually your own site. It keeps no copy of the rest of the post. DXNA follows your site's robots.txt.

If your site says which country you are in — in a contact card at /.well-known/contact.vcf or in an h-card on your home page — or you choose one after claiming your blog, DXNA keeps that country and where it found it, and shows it in the Directory. It reads nothing else from the card and keeps nothing else. If you delete your account, DXNA forgets the country you chose.

The claim invitation is described above. Akeem sends it by hand, at most once to an address.

If you email DXNA

Mail you send to hello@dxna.dev, and DXNA's replies, are held in Gmail (Google). DXNA keeps them so it can answer you, until Akeem deletes them.

Why DXNA uses it

If you are in the European Union or the United Kingdom: your account is a contract with you (the first item), and the other items are DXNA's legitimate interests. You may object to any use based on a legitimate interest by writing to hello@dxna.dev.

DXNA sells no personal data.

Cookies and storage on your device

DXNA sets cookies only when you sign in. Each one is sent only over HTTPS, and scripts on the page cannot read it.

CookieWhat it doesHow long
Your sign-inKeeps you signed in24 hours
A short sign-in tokenProves your sign-in to DXNA15 minutes
The sign-in checkProtects the trip to GitHub and back10 minutes
The sign-in routeRemembers where your last sign-in started, so DXNA shows the right page if it fails24 hours

Signing out or deleting your account removes the first two.

DXNA's pages also install a small helper in your browser (a service worker). It keeps only DXNA's offline page and its stylesheet, scripts and icons, so DXNA can show you a page when you are offline. It never keeps a page you read or anything about you. You can remove it by clearing DXNA's site data in your browser.

Who else handles your data

DXNA shares your data with nobody else, unless the law requires it. If you live outside the United States, your data is handled in the United States.

How long DXNA keeps it

WhatHow long
Your account, reading, stacks, name, email address and sign-in recordsUntil you delete your account
Your claim recordsUntil you delete your account, or the blog is removed
A listed author's invitation addressUntil the blog is removed; the scrambled form after that
Posts DXNA listsWhile the blog is listed. After a removal, DXNA keeps the blog's and the feed's web addresses so that it does not list the blog again. DXNA's internal change history can still hold the titles and first lines of a removed blog's public posts.
Mail you send to hello@dxna.devUntil Akeem deletes it
LogsGoogle Cloud's default, about 30 days
Database backupsGoogle Cloud's default, about 7 days

Your choices and rights

If you are in the European Union or the United Kingdom, you can also ask DXNA to restrict how it uses your data, and you can complain to your data protection authority.

Children

You must be 16 or older to sign in to DXNA. If DXNA learns that a reader is under 16, Akeem deletes the account. To tell him, write to hello@dxna.dev.

Security

DXNA asks GitHub for read-only access and keeps no GitHub password or token. Sign-in cookies travel only over HTTPS and are hidden from scripts. Invitation addresses are matched through a keyed scramble, and removal links are stored only in scrambled form, though a link's address can appear in request logs for about 30 days. DXNA's data is held in Google Cloud. No service is perfectly secure.

If DXNA learns of a breach that puts your data at risk, it emails the affected readers at the address DXNA keeps for them and posts a notice on the site.

Changes to this page

When this page changes, DXNA publishes the new version here, with a dated "Last updated" line at the top. DXNA does not email you about changes.

Contact

Akeem Philbert runs DXNA. Write to hello@dxna.dev.