1. Kush përgjigjet për këto të dhëna
NASHI.ALB is a board of listings and a community for people living in Albania. This page explains which of your data we receive, what we do with it, and what you can do about that.
In law, whoever decides why and how data is processed is called the controller. The platform has not registered a legal entity yet, so the controller here is a person rather than a company:
- Name and legal form: Roman Litvin, a private individual.
- Registration number: none — no legal entity has been registered yet.
- Postal address: it will appear together with the registration of a legal entity. Until then letters about data go to the email address below, which is a working address and not a placeholder.
- Email for questions about data: privacy@nashialb.com
- Data protection officer: none appointed. The law requires one where data is processed on a large scale or people are systematically monitored; that is not us yet, and questions about data go to the address above.
- Server: rented from Hetzner Online GmbH (Germany) and standing in the Helsinki DC Park 1 datacentre — Helsinki, Finland, which is inside the European Union. The database and the uploaded files live on that same server: there is no separate database provider.
2. In short — the parts people least expect
- We do not know your password: the database holds only its cryptographic hash (Argon2id).
- A contact in a listing is not in the lists or on the cards. It is handed out by a separate request, and only to somebody signed in.
- We spoil the point on the map on purpose. The database holds six decimal places — ten centimetres; a public answer carries three — about a hundred metres — and the page draws a circle of 350 metres instead of a pin.
- We strip the EXIF out of every uploaded photograph, including the GPS tag a phone puts there. Instead we burn a translucent NASHI.ALB wordmark across the middle of it — in a corner it would survive exactly until somebody cropped it.
- All traffic to the site goes through Cloudflare, so Cloudflare sees the IP address, the page address and the headers of every request. The photographs live there too.
- The moment a map opens on a page, the browser pulls its tiles from openstreetmap.org — so OpenStreetMap sees your IP address as well.
- Every letter goes through Resend, so the recipient address and the whole text of the letter are visible there.
- There is no Google Analytics and no cookie banner on the site. No advertising trackers either: there is one advertising place on the home page, and we count it ourselves — numbers of impressions and clicks by day, handed to nobody.
- We send no SMS: phone confirmation is switched off.
- An account is deleted on request, and there are 14 days to change your mind.
3. Ligji mbi të cilin funksionon kjo
In Albania personal data is protected by Law No. 124/2024 "On personal data protection". It was approved on 19 December 2024, published in Official Gazette No. 9 of 17 January 2025, and came into force on 1 February 2025. It repealed the earlier Law No. 9887/2008 and is aligned with the EU General Data Protection Regulation (GDPR) and Directive (EU) 2016/680.
Some of its articles — on data protection impact assessments, prior consultation with the Commissioner, codes of conduct and telling people themselves about a data breach — start applying on 17 January 2027. The duty to notify the Commissioner of a breach within 72 hours applies already.
Below we refer to the articles of that law. If you are reading this from an EU country, you know the same rights by their GDPR names — they are the same rights.
4. What data we hold
What follows is everything about a person that lies in our database. The list is complete rather than indicative: it was gathered from the tables, not from memory.
4.1. The account
- An email address. Without it there is no account: it is how you sign in and how a confirmation code reaches you.
- A password hash — if you sign in with a password. The password itself is not in the database.
- A Google identifier — if you signed in through Google. We ask Google for three things: openid, the email address and the name. We store no Google tokens.
- A Telegram chat id — if you linked Telegram. The first name, last name, username and photograph Telegram sends with it are checked and then thrown away.
- A phone number and the date it was confirmed — if you gave one.
- The language to speak to you in.
- The state of the account, the dates the email and the phone were confirmed, the last sign-in, the number of sign-ins, the time of the last activity, where you came from (the registration form, Google, Telegram), your invitation code and the code of whoever invited you.
- If the account is restricted: the reason, who set it and when.
- Records of consent: which consent, which version of it, and when you gave it. We do not write the IP address down with it.
4.2. The profile
- The name you show, a few words about yourself, a date of birth, a photograph, the languages you speak.
- Settings: what to show in the profile and what to send notifications about.
- The green “at the site now” dot. The time of your last activity has always been kept (section 4.1); it is now turned into a single yes-or-no for other people — a dot beside your name on the seller card, on your profile and in messages. It goes out by itself 5 minutes after you leave. The time itself, when exactly you were last here, is shown to nobody anywhere: it is not in the site’s answers at all. The switch “Show that I am at the site” is in your account, under “Data and privacy”, and is on by default; switched off, there is no dot anywhere.
- Spare contacts — phone, Telegram, WhatsApp, Viber. They are not public: they are a way to recover access and to reach the administration. A contact in a listing is a separate field and a separate decision.
- A business number and what the register answered about it — see section 4.6.
- A profile photograph is cropped square, converted to webp and stripped of EXIF. We put no wordmark on it: on a person’s face it has no business being there.
4.3. Çfarë botoni vetë
Listings, reviews, community posts and events are text and photographs you send so that other people see them. Everything you write there is meant for a reader. So a home address, documents and financial details do not belong in it.
- A listing: title, description, city, district, category, price, attributes, language, photographs, the channel of contact and the contact itself.
- The contact in a listing does not enter the public lists or cards. A separate request hands it out, and only to somebody signed in. Every such opening is recorded: which listing, who opened it and when. We never show that list to the author: knowing exactly who looked at your number is of no use to anybody.
- The point on the map: six decimal places in the database, three in a public answer, and on the page a circle of 350 metres labelled "Approximate location". Only the author and a moderator see the six: one has to be able to drag the point back onto the right building, the other has to be able to see that the point is in the sea.
- Listing photographs: we convert them to webp, make two sizes, strip the EXIF and burn a translucent NASHI.ALB wordmark across the middle. The mark is in the pixels rather than in metadata precisely because metadata is gone after the first screenshot, and in the middle rather than in a corner because a corner is cropped away.
- Reviews: the rating, the text, the tags, who the review is about and who wrote it. One review from one author about one provider.
- Community posts: title, text, city, the date and the landmark of the meeting, the channel of contact. The contact, as in a listing, opens by a separate request. The landmark is a place in the city, not a home address.
- Events: if you suggest an event, the organiser, the contact and the address become part of the publication — public along with it. If you give an address, your browser asks nominatim.openstreetmap.org about it, and the point it finds is stored with the event so that its page can show a map.
- «I am going» on an event page: we store that your account said it was going to that event and when, and — if you answered «how many of you» — the size of your party. The organiser and other readers see only the numbers: how many said they were going and how many guests to expect, never who. The same button takes it back, and then the row is deleted at once. A day before the event we send a reminder to everybody who said they were going; the letters can be switched off in the cabinet, under the «community» topic.
- The blogger contest: the name shown and a link to a social profile. Somebody else may put a name forward — then we also keep who did. A winner’s name and link are copied into the table of winners, and there they stay.
- Saved searches: what you are looking for — category, city, price bounds, the words of the query — so that the digest you subscribed to can be sent.
- Favourites: which listings you set aside.
4.4. Requests, tickets, complaints
- A transfer: from, to, date, time, number of passengers, luggage, child seat, pet, comment, name and WhatsApp number, and the consent tick. No account is needed. The drivers in the pool do not see the contact: only the assigned driver receives it. The "my requests" page does not show the number either — not even to the owner of the account.
- A housing request: type of deal, type of property, city, district, budget, rooms, moving date, contact, and whatever you wrote in words. The whole request, contact included, goes by letter to the dispatcher — the person who will get in touch with you.
- A support ticket: subject, email address, text, the language of the page you wrote from, and the answer you were given. A ticket survives without an account — the address to reply to is inside the ticket itself.
- Photographs on a ticket: up to 5 of them, if you attached any. Photographs only, under the same rules as in a conversation: the EXIF is stripped, they have no public address, and they can be opened by support and by you in your cabinet. They live for 90 days and are then deleted automatically — the ticket itself and our answer stay.
- A complaint about a publication: the reason, the explanation, what the complaint is about and who made it. The author of the publication sees the moderator’s decision and its reason, but not who complained.
4.5. Technical records
- Sessions. Every sign-in writes a row: the hash of the refresh token, the browser (the User-Agent string, cut to 250 characters), the IP address, the time of the last activity and the expiry. It is there for one thing: so that you can see your own sessions in the cabinet and recognise one that is not yours. You can end any of them.
- The audit log. Administrative actions: who did what, to what, with which reason and how it ended. Request bodies never enter the log — they hold passwords and verification codes.
- Error records. The text of the error, the stack, the route, the service, how many times it happened. No request body, no cookie, no headers and no IP address are in there — deliberately.
- Rate-limit counters. So that one script cannot rake out the directory, we count requests. While you are not signed in, the counter is keyed to the IP address; it lives in Redis and goes away by itself when the window ends. Another such counter keeps one view of a listing from being counted twice — it holds an IP address for half an hour.
- A listing’s statistics are numbers, not a log of visitors: views, contact openings, saves.
- An advertising banner’s statistics are the same kind of numbers by day: impressions and clicks. So that one reader is not counted twice, a hash of the IP address, the tab’s mark and the date lies in Redis for a day — neither the address nor the mark can be read out of it, and neither is in the database. The daily numbers themselves are removed after 400 days.
- Searches that found nothing are kept without whoever asked: the query "lawyer for custody cases" together with a person’s identifier would say more about them than they meant to tell.
4.6. A business number, and papers sent to a moderator
We neither ask for nor accept identity documents: no passport, no ID, no residence permit. While there is no legal entity, there is nobody who can answer for such a copy — and the copy itself would confirm little beyond the fact that we are keeping it.
A business is checked by its Albanian tax number (NIPT) instead. The number is typed once, in the profile, and belongs to the account rather than to one listing. This is voluntary: without a number the listing is published just the same, only without the "Licence verified" mark.
- Beside the number we keep the state of its check, who made it and when, and, if it was refused, the reason — which the author reads in their profile.
- Once a quarter of an hour a background pass asks the open business register (format.qkb.gov.al) about a new number. One field goes there: the number itself. Not your name, not your email, not your account identifier.
- We keep the register’s answer as it is: number, name, trade name, legal form, state, date of registration, city, the activity it is registered for, and the list of administrators and partners. That is open register data; the administrators may be the names of real people.
- A person grants the mark, not a program. The register’s answer is what a moderator reads first, and no more than that: it can show a business exists, never that the number is yours.
- We do not show the number itself in the catalogue: a reader sees only the mark.
- Papers about a business or about the property — a licence, a permit, an ownership extract, the owner’s authority — may still be sent to a moderator, to receive the "Documents verified" mark.
- A sent file has no public address: it cannot be opened by a link, even by somebody who knows it. Only a moderator sees it, and every opening goes into the audit log together with who opened it.
- The file is kept for 30 days and then deleted automatically: first the file in storage, then the row about it. The mark stays, and so does the record in the log.
4.7. Messages between people
Conversations about a listing are new on the site, and they are the most sensitive thing we now keep: until now we held no text addressed to one named person at all. So here it is, separately and plainly.
- We store: the text of the message, who wrote it, to whom, about which listing, and when. The text sits in the database as it was typed, not encrypted — we do not say "nobody can read this", because that would be untrue.
- No contacts are passed inside a conversation: neither e-mail nor phone number — each side sees only the name from the profile.
- Photographs can be sent in a message — up to 5 of them in each. Photographs only: JPEG, PNG, WebP. No PDFs, no documents, no other files of any kind, and that is a decision rather than something unfinished.
- From every such photograph we strip the EXIF — together with the GPS tag the telephone writes into it — and re-encode the file as WebP. The address of the flat you are photographing does not travel to a stranger along with the picture. These photographs carry no NASHI.ALB lettering: that exists so a stolen listing photo keeps saying where it came from, and a picture of a broken boiler is not a shop window.
- These photographs have no public address at all: they are not on cdn.nashialb.com and there is no signed link to them. Only the API hands the file over — to a participant of the conversation, and to a moderator only in the same two cases as the text, with every such opening written into the journal as its own line: not "opened a conversation" but "opened this photograph".
- They live exactly as long as the conversation: 365 days from the last message, or 30 days after both sides have deleted it. The file is destroyed from storage together with the conversation rather than left behind in it.
- There is no screen anywhere on which a moderator could browse conversations: no list of threads, no search over message text, no "all conversations of this account".
- A moderator can read one conversation in two cases only: one of the two participants reported it, or a participant attached it to their own support ticket themselves. Then that one conversation opens — the same person’s other conversations do not.
- Every such opening is written into the audit journal: who, when, which conversation. The line is written even when the moderator changed nothing — that is precisely the case worth seeing.
- What a moderator may then do: hide one message, close the conversation to new messages, escalate it to moderation. A hidden message does not vanish — both participants see that it was there and that it was removed.
5. Pse i mbajmë këto, dhe mbi çfarë baze
The law asks us to name not only the purpose but the legal basis (Article 7). Here is everything we do, and the basis for each of them.
- So that you have an account and can publish — performance of our contract with you. You accept the rules while registering, and we keep which version of them it was.
- So that an email and a phone can be confirmed, sessions can be held and sign-in can be defended — performance of the contract, and our legitimate interest in a stranger not getting into your account.
- So that publications are moderated, complaints are examined and fraud is held back — our legitimate interest in the board being usable, and the interest of everybody who reads it.
- So that service letters and notices about your own publications can be sent — performance of the contract.
- So that a transfer request reaches a driver or a housing request reaches the dispatcher — your consent, which you give by a separate tick in the form.
- So that a business number can be checked in the open register — your consent: you type the number yourself, and without it nothing happens.
- So that a support ticket can be answered — performance of the contract, and for a guest without an account, our legitimate interest in answering somebody who wrote to us.
- So that a duty the law puts on us can be carried out — when such a duty really exists.
5.1. Letters
We run no advertising mailings. The letters that arrive are a sign-in code, a password reset link, a moderator’s decision with its reason, a warning that a listing is about to expire, an answer from support, or a digest for a search you subscribed to yourself.
What to disturb you with, and about what, can be set in the cabinet. A saved search can be deleted there too.
6. Çfarë ruhet në shfletuesin tuaj
There is no cookie banner on the site, and that is not an oversight: we have nothing to put in one. Everything that lies in the browser is there so that the site works, or so that you are not asked the same thing twice.
- Cookie nashi_city — the chosen city, for a year. Without it the server would not know which city’s catalogue to draw.
- Cookie nashi_locale — the chosen language, for a year. Without it a letter would arrive in the wrong language.
- In browser storage: nashi_tokens — what you are signed in with; nashi_locale and nashi_city — the same two choices; nashi_recent — up to twelve identifiers of listings you opened; nashi_transfers — up to ten numbers of your transfer requests with the route and the date.
- In the tab’s own storage: nashi_ad_reader — a random mark the page makes for itself, so that one showing of the advertising banner is not counted twice. It goes away with the tab, it is not a cookie, and it is sent to two addresses of ours and nowhere else — "the banner was seen" and "the banner was pressed".
- The list of what you viewed and the list of your requests are not sent to the server — they stay in your browser. They can be wiped by clearing the site’s data in your browser settings.
- If the Cloudflare Web Analytics counter is switched on — it is attached by a key at build time — the page sends Cloudflare an anonymous note that it was viewed. It sets no cookie and builds no profile.
- The fonts are ours. The site does not load Google Fonts, and the page cannot call an outside font service at all.
7. Who else sees this data
We do not sell data and we do not hand it to advertising networks. Outside the platform it is seen only by those without whom it does not work. Here is the whole list.
- Cloudflare (USA) — DNS, TLS and the defence of the site. Every request goes through it, so it sees the IP address, the page address and the headers. Its storage (R2) holds the photographs and the database backups, and the browser pulls every photograph straight from there. The view counter, when it is on, is Cloudflare too.
- Resend (USA) — sending letters. Every letter goes through it, so the recipient address, the subject and the whole text are visible there: a sign-in code, a password reset link, a moderator’s reason for refusing, an answer from support.
- Google (USA) — signing in with Google, if you use it. Google sees that you are signing in to our site. From Google we receive an identifier, the email address, whether it is confirmed, and the name.
- Telegram — signing in through Telegram and notifications through @nashialb_bot. The sign-in widget is loaded from telegram.org only when you have opened the sign-in window, not on every page. Notifications are sent to the bot by your chat id.
- OpenStreetMap Foundation (United Kingdom) — the map. The browser loads the map tiles from tile.openstreetmap.org, so OpenStreetMap sees your IP address the moment a map opens on a page. When you place a point or type an address in the publishing form, the browser asks nominatim.openstreetmap.org about it: the coordinates or the typed words and the language of the page go there — with no token and no cookie.
- The Albanian National Business Centre (QKB) — the open register. One field goes there: the number you typed.
- Hetzner Online GmbH (Germany) — the server everything runs on.
- Twilio (USA) — SMS. Switched off at the moment: phone confirmation does not work and we have never sent a single message. If we switch it on, this page will say so.
7.1. Çfarë nuk është në sit
There are no payment systems, no advertising networks, no Google Analytics, no Google Tag Manager, no Sentry, no PostHog and no captcha on the site. The page could not call any of those hosts even by mistake: the list of addresses it is allowed to reach is short and closed.
When you tap a contact in somebody else’s listing — Telegram, WhatsApp, Instagram, a phone number — the site warns you that you are leaving it. From there the rules of that service apply, not ours.
8. Where data goes outside Albania
The server is inside the European Union. But some of the companies named above are registered in the USA, and data travels to them.
Albanian law allows a transfer to a place where protection is recognised as adequate (Articles 39 to 41). The list of such countries is set by Commissioner Decision No. 01 of 30 April 2025: it holds every EU and EEA country, the United Kingdom, Switzerland — and the USA, but only for companies taking part in the EU-U.S. Data Privacy Framework.
Cloudflare, Google, Resend and Twilio state in their own public documents that they take part in that framework. We are relying on their own statement, not on a check of ours.
The storage of photographs and backups (Cloudflare R2) is not pinned to a region — so Cloudflare chooses the location itself, and it may be outside the European Union.
If you want to see what one of these transfers actually rests on, write to support and we will show you what we have.
9. How long we keep it
"As long as necessary" is not an answer. These are the real periods the site runs on today.
- A listing: it depends on what is in it. A service or a business page and housing are never taken off the board at all — we only ask you to confirm that it still holds, every 180 days for a service and every 60 for housing, and the card shows when that was last done. A thing for sale lives 45 days, a vacancy or a CV 30, a car or an event 60; a letter comes 5 days before the end, and after that the listing goes to the archive — out of the catalogue, but the row stays so that you can renew it.
- A community post: one day after the date of the meeting, then to the archive.
- A paper sent to a moderator: 30 days, then the file and the row about it are deleted.
- Single-use codes and links — the code from a letter, the code to a phone, a password reset link, a Telegram linking code: a week after they stopped working. They themselves last from ten minutes to a day, and the database holds a hash rather than the code.
- A notification in the bell: 90 days once read. An unread one stays: it is something that was said to you and you have not seen it yet. The exception is the kinds whose content spoils on its own — a digest for a saved search, the result of a contest, a warning about an expiry.
- The queue of letters to send: 30 days after the letter went out. What did not go stays — it is the only trace of a letter that never left.
- Error records: 30 days from the last occurrence.
- Conversations: 365 days from the last message in the thread — after that the conversation is deleted together with every message in it. The period runs from the last thing said rather than from the start: a conversation that is still going is not old. Two kinds stay longer: one with an open complaint about it, and one attached to a ticket we have not answered yet — deleting either would destroy the very thing the complaint is about.
- Photographs sent in a conversation: with the conversation itself and on the same clock — the files are destroyed from storage in the same pass that removes the thread. If both sides have deleted it, that is 30 days rather than 365.
- Photographs attached to a support ticket: 90 days from when they were sent. The file goes first, then the row about it; the ticket itself and our answer stay.
- «I am going» marks: 30 days after the event is over, then the row is deleted. Until then it belongs to whoever ran the event: «how many were interested» is asked the week after, not the year after.
- A request to delete an account: 14 days, during which it can be cancelled.
9.1. What has no period yet
Sessions together with the IP address and the browser string, the audit log, complaints, support tickets, consent records, transfer requests and housing requests are not yet swept by age.
For the audit log that is on purpose: it is the record of who decided what, and without it the decisions of moderation would be left with no reason behind them. For the rest it is not, and it is something we have to fix rather than something we chose. Your own sessions you can end yourself in the cabinet, any one of them or all.
10. Deleting an account
An account is deleted on request, from the cabinet. After that there are 14 days to change your mind: it is a defence both against an accidental tap and against somebody who got hold of a stranger’s access. A letter about the request arrives at once.
When the time has passed we do not wipe the row but make the account anonymous. Reviews, moderation decisions and the log stay: otherwise the reason for those decisions would be gone, and there would be nothing left to answer for them with.
- Gone: the password, the link to Google, the phone, Telegram, the spare contacts, the second-factor secret, the saved searches. The email address is replaced by a service string.
- The name and the description in the profile are wiped. Listings and community posts go to the archive — they disappear from the catalogue and the feed.
- Every session is ended.
- The profile photograph still stays in storage — that is an unfinished job, not a decision. It can be removed now, by you: there is a button in the cabinet for it.
- Staying: reviews without the author’s name, moderation decisions, the audit log, support tickets together with the address we answered to, and transfer requests with the name and number that were written in them.
- Letters already sent to a mailbox cannot be recalled by us.
11. Your rights
Articles 12 to 20 of Law No. 124/2024 give you the rights below. The names are official, so beside each one is what it means here.
- To learn what exactly we keep about you, and to get a copy (Art. 14).
- To correct what is wrong (Art. 15). Most fields you correct yourself in the cabinet, and that is the quickest way.
- To have it deleted (Arts. 15 and 16) — how that happens is in section 10.
- To restrict processing while we are settling a dispute (Art. 17).
- To receive your data in a form that can be moved elsewhere (Art. 18).
- To object to processing that rests on our legitimate interest (Art. 19).
- To withdraw consent as easily as you gave it (Art. 8). Withdrawing does not make what happened before it unlawful.
- Not to be subject to a decision taken by automatic means alone (Art. 20). We take no such decisions — see section 15.
- To complain to the Commissioner (Art. 86) and to go to court (Art. 87).
11.1. How to use them
Write through the support page. There is no "export my data" button on the site yet: we gather a copy by hand, on request.
The period for an answer in law is 30 days. If a request is complex, or there are many of them, the period can be extended to 60 days — and then we have to tell you so, with a reason, within the first 30 (Art. 12). An answer is free of charge.
To answer, we have to be sure that it is the owner of the account asking. So write from the cabinet, or from the address the account is registered to.
12. Complaining
If you think we are handling your data wrongly, tell us first — it is faster that way. But you are not obliged to: you may complain straight away.
The authority that examines this is the Commissioner for the Right to Information and Personal Data Protection (Komisioneri për të Drejtën e Informimit dhe Mbrojtjen e të Dhënave Personale), IDP for short.
- Address: Rr. "Abdi Toptani", Nd. 5, 1001 Tiranë, Albania
- Telephone: +355 42 23 7200; free line 08002050
- Email: info@idp.al
- Website: idp.al
12.1. Nëse ankesa nuk lëviz
A complaint to the Commissioner is free of charge (Art. 86). If the Commissioner has not examined it, or has not informed you, within 90 days, you may go to the administrative court (Art. 87). Damage — financial and non-financial — can be claimed for (Art. 88).
13. Security
- A password is only an Argon2id hash. Neither we nor an administrator knows it.
- Two-factor protection (TOTP) can be switched on in the cabinet. Recovery codes are shown once, and the database holds them as hashes.
- Refresh tokens in the database are hashes too, and they change at every renewal.
- Changing a password ends every session.
- Pages are served with a strict content security policy: an outside script will not run on the page, and the list of hosts the page may reach at all is closed.
- Papers sent to a moderator lie in closed storage with no public address.
- If we lose data in a way that threatens your rights, we have to notify the Commissioner within 72 hours (Art. 29).
- There is no absolute security — which is why the most valuable thing we do not ask for is the thing we do not keep: there are no copies of passports on this site.
14. Age
Albanian law lets a child under 16 give consent for an online service only through a parent or a guardian (Art. 8). So an account on NASHI.ALB is from 16 years old.
Romantic listings are for adults only; that is a separate rule, and a stricter one.
We ask for no documents and we do not check age. If you know an account belongs to a child under 16, write to us and we will take it down.
15. We take no decisions "by algorithm"
A decision about your publication is taken by a person. The number of complaints removes nothing by itself.
There is automation on the site, but it decides nothing about you: it looks for similar listings and shows a moderator a suspicion, it counts requests so that one script cannot rake out the directory, it sends letters when a period runs out. There is no profiling, no advertising targeting and no scoring of people on this site.
16. Changes to this page
When what we do with data changes, this page changes with it. The date of the update is at the top.
If a change matters — new data, a new recipient, a new basis — we will say so before it starts applying, not after.
17. How to reach us
About data, about a copy, about deletion and about anything written on this page, write through the support page. Every ticket is read by a person, and a ticket number comes back in reply.
By email as well: privacy@nashialb.com, which is the address given in section 1. The one difference is that a ticket from the cabinet tells us for certain who is asking, while a letter has to be matched against the address the account is registered to.
