Privacy notice

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 unless you allow it. Pages, images, video, fonts and scripts are loaded from https://txmska.com, and it is your browser that enforces that rule rather than my good intentions. The exceptions are YouTube videos in Learning classes and blog posts, under the same external-content choice. Neither is asked for at all until you allow it from the banner. The site keeps the first-party counts described below and uses no third-party analytics, advertising, embedded social widget, chat widget or consent platform. Every typeface, including the ones that are not the site's own, is served from this same domain, so opening a page does not tell Google, or anyone, that you were here, unless you allowed external content and opened a class or a post with a YouTube video.

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 about you: the form has no file field, asks for nothing optional and stores no visitor or device identifier.

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

The panel has separate staff accounts. Each one has its own username, password, role and permissions. Sign-in checks the password and a TOTP code from an authenticator app, or one unused backup code. A browser can be marked as trusted for thirty days, and then skips the code while that trust is valid. The database keeps each account's alias, email address, username, role, state, owner's note, creation time and second-factor setup time. Passwords and backup codes are stored as hashes, and TOTP secrets are encrypted. Account details and tickets are available inside the panel according to the account's role. 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.

Other data the site holds

The database also holds staff account records and the audit entries created by panel actions. Published content includes the posts, the images, video and audio inside them and the two cards on the links page, all of it written through the editor. Files are uploaded through the panel, never by a visitor. Reading contributes only to the first-party totals described below, without a history of pages linked to a person.

First-party counts

The site counts public page views, opened Learning classes and activations of channels and cards on the Links page in its own MySQL database. Aggregate totals cover the previous 730 days and are available only to the owner and operators. To estimate visits and daily visitors, the server temporarily converts the request's IP address into a keyed digest that changes each day; the raw address, browser details and a history of pages linked to that digest are not stored in the metrics tables. These temporary digests and event receipts expire after 48 hours and are removed by the next cleanup when a count is recorded; the key stays only in server memory. Shared addresses and server restarts can affect these estimates, and the visitor figure adds daily estimates rather than identifying distinct people across a longer period. The counts set no cookie or browser-storage entry and send no information to a third-party analytics service. A class view means that a class was opened; saved courses, watched-class markers and learning progress remain in the browser and are not sent to the counters.

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 a language preference cookie, the answer you gave the consent banner, and strictly necessary cookies for panel sign-in and account setup. Learning also keeps what you saved and what you marked as watched in your own browser, where it stays: it is never sent here, so it is not data this site holds. All of it is listed 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. The first-party counts described above are not tied to a name or an account, and they are not part of that ticket.

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.