Last updated 31 August 2026

Privacy notice

Reading this site sends nothing to anybody else. If you write through the contact form, your name, your email address and your message are kept until I delete them by hand.

Who is responsible

Tomas, working as TXMSKA, in Argentina. For anything on this page, write to business@txmska.com.

What reading the site does

Nothing leaves this domain. Pages, images, video, fonts and scripts may be loaded from https://txmska.com and from nowhere else, and it is your browser that enforces that rule rather than my good intentions. There is no analytics, no advertising, no embedded video player, no social button, no chat widget and no consent platform. The two typefaces that are not the site's own are downloaded when it is built and served from this same domain, so opening a page does not tell Google, or anyone, that you were here.

The contact form

Sending the form files a ticket in a MySQL database at the same hosting provider that serves this site. The ticket holds the category you picked, your name, your email address, your message, the language you were reading in, the date it arrived, and the answer once there is one. Nothing else: the form has no file field, asks for nothing optional and stores no identifier of any kind.

It is kept so the message can be read and answered, and so the conversation can be found again if you write back about the same thing.

Two emails go out, and they are not the same kind of thing. One is a copy to me at support@txmska.com, and it carries everything you wrote. The other is a receipt to the address you typed, sent from the site's own noreply mailbox, and it repeats not one character of your message: it names the category you picked and a reference number, because it goes to an address a stranger could have supplied. One address gets at most one receipt a day.

The answer is written in the editor, saved on the ticket and sent to you from that same mailbox. If you reply to it, your reply goes to support@txmska.com.

The form also sends how long it was open and one field no person sees, both there to tell somebody writing from something filling forms in bulk. Neither is stored, and neither travels further than the check itself.

How long it is kept

Until I delete it. There is no retention period and nothing sweeps the table: no job runs at night, no ticket expires, no message is removed for being old. Answering marks a ticket answered and archiving takes it out of the inbox, but neither of those deletes anything. A ticket leaves the database when I delete it, and that is the only thing that removes it.

Who can see it

One person: me. The editor has one account, one password and no second user to add. Nothing is sold, rented, shared or handed to an advertiser, and no outside service ever sees a ticket: the form posts to this site and nowhere else, and the mail goes out over SMTP from a mailbox on this domain rather than through somebody else's mail service. The one company in the picture is the hosting provider, which runs the server, the database and that mailbox.

The sending limits

So the form cannot be turned into a way of mailing somebody who did not ask for it, the site counts recent sends. A count lives in the memory of the running process, never on disk and never in the database. It is your IP address, as the proxy in front of the site reports it, or your email address in lower case for the receipt count, together with a number and the time that count goes back to zero. Three sends an hour from one address, one receipt a day to one email address. Every count is forgotten when its window ends, and all of them are gone when the process restarts.

The rest of the database

Everything else in it is published content: the posts, the images inside them and the two cards on the links page, all of it written through the editor. Images are uploaded by me, never by a visitor. There is no record of who read what.

The server logs

The hosting provider keeps its own access logs, the ordinary kind: address, time, what was asked for and which browser asked. Those are the provider's, kept under their own policy. This site does not read them, does not combine them with anything and builds no profile out of them.

Cookies

The site can set two, and neither of them is about you: the language you chose and the sign-in session of the editor. Both are listed in full in the cookie notice.

Asking for a copy, or for it to go

Write to business@txmska.com from the address you used and tell me which of the two you want. A copy is what the ticket holds, read out of the same inbox I answer from. A deletion is that ticket removed from the database, which cannot be undone. Nothing else about you is held anywhere, so there is nothing else to ask for.

Changes

If this page changes, the date at the top changes with it. There is no mailing list to warn, because there is no mailing list.