a going down; a descent, especially a journey down into the underworld and back out of it.
Origin: Greek κατάβασις, from κατά (down) and βαίνειν (to go).
Privacy Policy
In force from 8 August 2026.
1. Controller and scope
1.1. The controller of the personal data described in this Policy is the private individual who operates the Katabasis application at katabasis.quest (the "Operator"). The Operator may be contacted through the contact form published at katabasis.quest/contact, which requires no account, through the feedback function available on every page of the Service, or through the channel by which the invitation to the Service was received.
1.2. This Policy applies to personal data processed in the course of operating the Service. Processing is carried out in accordance with Brazilian Law No. 13.709/2018 (Lei Geral de Proteção de Dados). Where Regulation (EU) 2016/679 applies to a User, the rights set out in clause 9 are afforded on the same terms.
2. Data not collected
The Service does not collect an email address, a telephone number, a password, a postal address, a date of birth, payment details or contact lists. It contains no analytics, no advertising and no third-party tracking of any kind, and no personal data is disclosed for marketing purposes.
3. Categories of data processed
3.1. Account data: none beyond an internal identifier and the date the account was created. The Service holds no name, chosen or otherwise, for any User.
3.2. Authentication data: the public key and identifier of each passkey registered by the User, together with any label the User assigns to a device. The corresponding private key remains on the User's device and is not transmitted to the Service. Where the optional second factor is enabled, its shared secret is stored in encrypted form. The recovery code is stored only as a cryptographic hash.
3.3. Content: data submitted by the User in the course of using the Service, together with the User's preferences, and, where the User elects to provide it, approximate location coordinates and a label for that location.
3.3a. Where the User enables an optional feature that records a daily habit, the Service stores the quantity recorded and the date it relates to. Such records are self-reported measures of a routine and do not constitute data concerning health; they are not used to infer any health condition and are not disclosed to any recipient.
3.3b. Where the User records a place in a map, the Service stores the coordinates, the name and any details the User entered for it. These coordinates describe a place chosen by the User and are not transmitted to any third party.
3.4. Support data: the text of any feedback submitted, the page from which it was submitted, technical characteristics of the browser which do not identify the User individually (browser family, platform, interface language, approximate screen dimensions), and a rendered image of the page where, and only where, the User expressly requests that one be attached.
3.4a. Contact messages: where a person uses the contact form, the Service stores the email address, the subject and the message they provide, a telephone number if they choose to give one, the interface language of the page they wrote from, and the IP address the message was sent from. The address is used solely to reply and is not used for any other purpose; no message is sent automatically to it, and it is added to no list.
3.5. Authentication log: for each attempt to authenticate, the date and time, the outcome, the IP address from which the attempt originated and the user agent string transmitted by the browser.
3.6. Integrity records: a sealed record of changes to stored data, comprising the field affected, the area of the Service concerned and the time of the change. The content of the change is not recorded.
3.7. Biometric data: none. The Service performs no biometric identification of any kind, retains no facial image and stores no facial recognition data for any User, including the Operator. Where the interface offers to use a camera, the video is displayed in the User's own browser and no frame is transmitted to or stored by the Service.
4. Purposes and legal bases
4.1. Account, authentication and Content data are processed for the purpose of providing the Service to the User, on the basis of the User's request and consent (LGPD, art. 7, I and V).
4.2. The authentication log and the integrity records are processed for the purpose of detecting and investigating unauthorised access and unauthorised modification, on the basis of the legitimate interests of the Operator and of all Users in the security of the Service (LGPD, art. 7, IX; art. 46).
4.3. Support data is processed for the purpose of diagnosing and correcting defects, on the basis of the User's consent given at the time of submission.
4.4. Location coordinates are processed solely to obtain local weather, air quality and astronomical information for display to the User, on the basis of consent, which may be withdrawn at any time by removing the location in the settings.
4.5. Contact messages are processed for the sole purpose of receiving and answering the message, on the basis of the sender's consent, given by sending it (LGPD, art. 7, I; GDPR, art. 6(1)(a)). The IP address is processed on the basis of the legitimate interest of the Operator in preventing the abuse of a form open to the public (LGPD, art. 7, IX; GDPR, art. 6(1)(f)).
5. Cookies
The Service sets four cookies, all of them strictly necessary: a session cookie which maintains the authenticated session; a cookie used to prevent cross-site request forgery; a cookie which identifies a device the User has chosen to have remembered, so that the second authentication step is not repeated on it; and a cookie recording the interface language selected. No advertising or analytics cookie is set and no cookie is shared with any third party. No consent banner is presented, because none of these cookies requires consent.
6. Disclosure and transfers
6.1. Personal data is not sold, rented, licensed or disclosed to any third party for any commercial purpose. No processor acts on the Operator's behalf other than the hosting provider.
6.2. Certain information displayed by the Service is obtained from third-party sources. Except as stated in clause 6.3, these requests are made by the server and not by the User's browser. The sources are: Open-Meteo, to which approximate coordinates are transmitted in order to obtain weather and air quality data; Wikimedia, to which only a calendar date is transmitted; NASA, to which no data relating to the User is transmitted, the image being retrieved by the server and served from it; and, where the User pastes a shortened map link and asks the Service to resolve it, the operator of that shortening service, to which that link is transmitted in order to determine the location it refers to.
6.3. Where the User opens a dataset displayed as a map, the User's browser requests map imagery directly from OpenStreetMap. The operator of that service therefore receives the User's IP address and the area of the map being viewed. No account identifier, no name and no other content is transmitted with such a request, and no such request is made on any other page of the Service. This is the only circumstance in which the User's browser communicates with a party other than the Service, and the Operator may disable it, in which case places are drawn without map imagery.
6.4. The Service is hosted on infrastructure located in the United States of America. Personal data is therefore transferred outside Brazil and outside the European Economic Area. The transfer is necessary for the performance of the Service requested by the User (LGPD, art. 33, VIII).
6.5. Personal data may be disclosed where disclosure is required by a binding order of a competent authority. Where the Operator is lawfully permitted to do so, the User will be informed.
7. Access by the Operator
7.1. The Operator administers the server and holds the encryption keys, and is accordingly technically capable of reading stored Content. This is stated expressly so that no User is left with a contrary impression.
7.2. The integrity records described in clause 3.6 are designed to make modification of stored data detectable. They do not prevent access by the Operator and are not represented as doing so.
7.3. The Operator does not access Content other than where necessary to operate, maintain or repair the Service, or where required by law.
8. Retention and deletion
8.1. Personal data is retained for as long as the User's account exists, save as set out below. Images obtained from third-party sources for display are retained for fourteen days.
8.2. Entries in the authentication log described in clause 3.5 are deleted ninety days after they are recorded, whether or not the account they relate to still exists.
8.3. A backup copy of the database is taken before each update of the Service and is deleted thirty days after it is made. Data belonging to a deleted account may therefore remain in a backup copy for up to thirty days after deletion. Such copies are not reachable through the Service and are used only to restore it after a failure.
8.4. On deletion of an account, the following are erased: Content, preferences, authentication data, submitted feedback and attached images, and the integrity records relating to that account. Deletion is immediate and irreversible.
8.5. A single record is retained in the Operator's log of invitations, recording that a given invitation was used on a given date. The IP address and user agent associated with that record are erased.
8.6. A message sent through the contact form is deleted six months after it is received, or seven days after it is marked as unsolicited, whichever is sooner. The IP address recorded with it is erased thirty days after receipt, while the message itself remains. A sender may ask for their message to be deleted sooner by replying to the answer they receive.
9. Rights of the data subject
9.1. The User has the right to confirmation of processing, access, correction, anonymisation or deletion, portability, and information as to disclosure, together with the right to withdraw consent (LGPD, art. 18).
9.2. The rights of access, portability and deletion may be exercised directly and without request, by means of the export and deletion functions provided in the settings. Any other request may be addressed to the Operator by the means set out in clause 1.1 and will be answered without undue delay.
9.3. The User has the right to lodge a complaint with the Brazilian National Data Protection Authority (ANPD) or, where applicable, with the competent supervisory authority in the User's jurisdiction.
10. Security
10.1. Access to the Service requires public key authentication. Connections are encrypted in transit. The second factor secret is encrypted at rest, and recovery codes are stored only as hashes.
10.2. No system is immune from compromise. In the event of a security incident presenting a risk to Users, the Operator will notify affected Users and the competent authority as required by applicable law.
11. Amendments to this Policy
This Policy may be amended. The amended Policy takes effect on publication at this address and the date shown above is updated accordingly. No individual notice is given, as the Service holds no contact address for its Users.