Privacy notice

What this site does not collect

• No public accounts, no registration and no visitor sign-in.
• No advertising, and no sale of any data.
• No third-party scripts on the pages of this site other than the analytics service described below.
• No form sends your data to any party outside this site. The search box sends what you type to this site’s own server, only so that it can answer.

Usage analytics

This site uses Google Analytics 4. The provider is Google. The purpose is to measure website usage in aggregate and to improve the service. Google receives the usage data that service measures.

The analytics service may use browser, device, network and usage information, according to Google’s operation of that service.

KSAFISH does not intentionally send private review data or personal information you enter as analytics event parameters. Specifically: the text you search for is not sent — only its length is.

This site does not yet have a cookie or consent manager, and this page is not offered as satisfying any legal obligation — it describes what the site does.

The two technical cookies

The site sets two technical first-party cookies. Neither is used to identify you or to follow you across sites:

• XSRF-TOKEN — a token that protects requests against cross-site request forgery.
• huwat-marine-encyclopedia-session — technical session continuity while you browse.

Both expire after 120 minutes, and both are scoped to this domain and are sent only over an encrypted connection.

These are the only cookies of this site itself. The analytics service may place cookies of its own in your browser, according to Google’s operation of it, and they are not these two.

Server logs

Like any web server, this one records incoming requests — the address requested, the time, and the IP address it came from — for operation and security. The encyclopedia application does not link these logs to any account and does not use them to build a profile of a visitor. How long they are kept is not stated on this page.

Contact

If you write to info@ksafish.com, you send us what you choose to send; this site does not collect your address by itself.

For what may be reused from the encyclopedia’s text, sources and images, see Content and image rights.

The observer account

Registration as an observer is not open in this version: no account is created and none of the following is collected. This describes what an observer account would collect if registration is opened.

• Your name, your email address and the username you choose.
• Your email address is where the verification code is sent, and it is how you sign in and recover your account. While a registration attempt is in progress the address and what you typed are kept in the attempt record encrypted, together with a keyed fingerprint from which the address cannot be read, used to find the attempt and to count attempts; both are wiped when the attempt ends. If a form is refused and you are sent back to it, the number and email you typed are kept in your session encrypted, not as typed.
• Your mobile number: it is stored encrypted on your profile, for contact only. It is not confirmed, nothing is sent to it for verification, and it is never used to sign in, to recover the account or to identify you; no keyed fingerprint is kept for it, so the same number can appear on more than one account.
• Your password: it is stored hashed and cannot be read.
• The type you declared about yourself (fisherman, outdoor enthusiast or hobbyist, interested, other); it grants no permission.
• When you accepted this notice and which version, and whether you agreed to notifications. The service sends no notification on the basis of that agreement today.
• What you put in your observations: the species you believe, the date, the sea or region, and your notes. The forms on these pages ask for no exact position and no coordinates. The programming interface behind the pages does, however, let a signed-in observer account attach photos and an exact position to an observation; the pages do not use it.
• Your session record: the server keeps your IP address and your browser identification (user agent) with your session, for as long as the session lasts, which is 120 minutes without activity, after which the record is removed by the routine cleanup of expired sessions.
• The message ledger: for each verification email that was sent, the sender’s name, its reference for the message, whether it accepted it, whether you typed the code it carried, and the time. Your email address and the text of the message are not in it, and email has no delivery report, so a server accepting a message is not counted as its arrival.

The purpose: to create your account and confirm your email, to let you recover access to it, and to tie your observations to you and have them reviewed.

What does not happen:

• Your name, mobile and email appear on no public page, and are neither sold nor given to any advertiser.
• The pages of your account, your observations and your registration are not measured by the analytics service described above.
• Confirming your email does not confirm your mobile, and your mobile is not treated as confirmed. For that reason the mobile is never used to sign in or to recover the account, and a password is recovered through the confirmed email alone, by sending a code to it.

No email sender is connected in this version, so no email is sent.

How long data is kept, as the service does it today:

• A verification code is valid for 10 minutes, and the whole attempt for 30 minutes. When an attempt ends the address (and the mobile number you typed with it) and the temporary details are wiped from its record, and the record itself is deleted after 24 hours. That happens at the next registration attempt, or when the operator runs the periodic sweep command; the server has no scheduler configured today, so an ended attempt can stay longer than that until one of the two happens.
• Message ledger rows are deleted after 400 days by the same command.
• Your account, its data and your observations are kept as long as your account exists; nothing deletes them automatically, and no final retention policy has been written yet.
• Account events (creation, sign-in, sign-out, email verification) are recorded in an audit log that cannot be edited and holds no password, no code, no email address and no phone number.

Deleting your account:

• There is no button to delete an account on these pages yet. To ask for it, write to us from the contact page page with your username. The operator then runs a command made for it.
• What the command does: it removes your mobile number from your profile and every verification attempt; it replaces your name, email, username and password with values that no longer point to you; it ends all your sessions, tokens and permissions; it wipes the name and details of your profile; and it withdraws all your observations from view.
• What it does not do: it does not delete the record of your observations, their history, their reviews or the audit records, because they are the record of what was looked at and the reviewers’ work, and audit records cannot be edited; after the deletion they point to nobody. On your request the free text of your observations (notes, place name) can be blanked as well.
• What it cannot reach: database backups taken before the deletion (the operator keeps them and does not rewrite them), the records the mail service and your own mail provider keep of the messages, and web-server logs.