Privacy Policy

개인정보 처리방침

Effective 10 November 2026 · Version 2.6

HanSups ("we", "us") operates the website hansups.com, the email list you can join from it, and the HanSups app at app.hansups.com. This policy explains what personal data we collect, why we collect it, how long we keep it, and who processes it. It also explains the rights you have under the Republic of Korea's Personal Information Protection Act (PIPA), which is the law that governs us.

1. What we collect

  • Email list: the email address you submit, a coarse language preference (e.g. en, vi), which form you used, when you signed up, and when you confirmed by clicking the link we email you. We send advertising emails only to addresses that have confirmed. If you opt out, we also keep the date you did so, precisely so we do not send you advertising emails again. The box you tick says that you agree to receive advertising emails (광고성 정보 수신동의). We record which wording you agreed to and when.
  • The app (app.hansups.com): when you create an account we hold your email address and, if you sign in with Kakao, Google or Facebook, the name and email that provider returns. You can set a display name and a profile photo; if you do, we store them, and the photo is held in private storage that only you can read. As you study we record your diagnostic and mock-exam attempts and their answers, your review history and level estimate, your chosen study language, your visa goal, your exam date, and your usage of the AI tutor. If you enter the details of your exam sitting, we store the venue, room and address you enter. This is the study record the app needs to work. It is yours, and you can ask us to delete it. If you choose advertising emails in the app, we record your choice, its date and the version of the consent wording. It is the same choice as on the email list. If your account's email address is not confirmed yet, we put it on the email list instead and email you a confirmation link. Your agreement counts only once you click that link. We link the two by your email address, and your most recent choice counts. So unsubscribing in either place stops all our advertising emails. You can turn it off in Profile at any time.
  • Purchases: when you buy a plan in the app we record the order: the name you give for the receipt, your account's email address and identifier, what you bought, the price, how you paid (card, easy pay or bank transfer, but never the card or account number), when you paid, your access dates, that you confirmed you are 19 or over and accepted the terms, and any cancellation or refund. Your card number never reaches us: you enter it with our payment company. On a computer, you also type a phone number for the payment company. It goes only to PortOne and KG Inicis, and we do not keep it. If you ask for a bank-transfer refund, the bank account you name is passed to our payment company to make that refund and is not kept by us.
  • Free practice test: the test itself runs in your browser. When you ask to unlock your detailed review, your score summary (the paper's name, your score, your percentage and your estimated level) is sent to our server for one purpose: to put it in the email we send you. We do not store that summary. What we do store is your email address, your language, and the fact that the address was verified. The unlock arrives as a link, not a code. That link works for 24 hours, and anyone who has it can open your review, so treat it like a password.
  • Speaking practice, and your microphone: the 구술시험 (oral exam) rehearsal in the web app can record your spoken answer so you can play it back and hear yourself. Your browser asks your permission first, and you can refuse and still use the rehearsal. The recording stays in your browser's memory. It is never sent to us or to anyone else, it is never saved as a file or on your device, and it is discarded the moment you delete it, re-record, move on, or leave the page. We collect no voice data. Recording is offered on the web app only; the Android app does not record.
  • Answering by speaking (dictation): in the web app you can answer a speaking question by talking instead of typing, and your browser turns what you said into text. Dictation is offered only where your browser can recognise Korean entirely on your device, and we check before offering it. Your device does the recognising, and your voice is not sent to any speech service. Where your browser cannot do it on the device, dictation does not run rather than falling back to a server. The first time you use it, your browser downloads a Korean speech model from Google. That download reaches Google, so your IP address does too, exactly as loading the tour video does; no audio and nothing else about you goes with it. It is optional — decline it and you can still record yourself and play it back. What reaches us is the text, never the audio. When you read a passage aloud, even the text stays with you: it is shown back to you so you can see what you said, and nothing is sent. If you ask for a check on what you said, the text, never the audio, is sent for it, the same way a writing check is — see Google (Gemini) in section 3 for what that means. Dictation is offered on the web app only; the Android app does not have it.
  • Contact: if you email us, we receive whatever you include in that message.
  • Contact form: your email address, your message, the type of question, and your organisation's name and size if you add them.
  • On this website (hansups.com) we do not collect your name, payment data or precise location (purchases happen in the app, as described above), and we run no advertising trackers and no analytics script. If you vote on the public roadmap, we generate a random identifier for your browser so that your vote is counted once. It is a random value and it is not linked to your name. It is listed, with every other thing we store on your device, on the Cookies and Storage page.

2. Why we use it (purpose & legal basis)

If you agreed to advertising emails (광고성 정보 수신동의), we use your address to send you news about new features, practice papers and offers. If you asked us to tell you when paid plans open, we send you that one email. We also use the list to measure demand by region and language, and to run the practice-test email verification. Legal basis: your consent, given when you submit the form. For the email list it is complete only when you confirm by the link we email you. You may withdraw it at any time. We do not sell or rent your data and do not use it for automated decision-making.

Purchases. We use the order record to make the sale, open your access, send your receipt, handle cancellation and refunds, and keep the transaction records Korean e-commerce law requires. Legal basis: carrying out the contract you make with us (PIPA article 15(1)4), and complying with a legal obligation (article 15(1)2; the 전자상거래법, article 6).

The app. We use your account and study record to provide the service you signed up for. Section 1 lists what they hold, under "The app". Legal basis: carrying out the contract you make with us (PIPA article 15(1)4).

Keeping the service safe and working. We use a bot check, usage counters and crash reports (Sentry), as sections 3 to 5 describe. Legal basis: for account holders, carrying out the contract you make with us (PIPA article 15(1)4). For everyone, our legitimate interest in a safe and working service (PIPA article 15(1)6). It clearly outweighs your rights here, because the data is small and kept for a short time.

Sign-ups that are not finished. We keep an account whose sign-up is not finished for up to 30 days, so that you can finish it. Then we delete it, as section 5 says. Legal basis: steps you asked for while making a contract with us (PIPA article 15(1)4).

3. Processors we use

  • Supabase: our sign-in service, including sign-in with Kakao, Google or Facebook. Its database holds your account and study record, purchase records, the email list and the database counters. Its file storage holds profile photos. It also sends the email with your sign-up code, through Resend. The public site can neither read nor write the email list; new entries go through our own server.
  • Resend: sends our emails. Some are sign-in emails that Supabase hands over to it. These are your sign-up code, a sign-in link, a password reset, an email-change confirmation and a confirmation code. Others are our own account emails: a password-reset link, a note naming how your account signs in, and a welcome email. Resend also sends the email-list confirmation and its dated notices, and the practice-test unlock link. It also sends purchase receipts, refund emails, a notice when we refuse a paid bank transfer, and our advertising emails. Resend also carries messages from our site's contact form to our inbox, and the alerts our server sends us.
  • KG Inicis Co., Ltd. (주식회사 케이지이니시스): our payment company. It processes your payment and any refund, and you give your card or account details to it directly.
  • Korea PortOne Co., Ltd. (주식회사 코리아포트원): the PortOne payment service that connects our app to KG Inicis. It passes the order (its number, the amount and the name you give for the receipt) between us and KG Inicis, and the refund account if you name one. On a payment made on a computer, it also passes your account's email address and the phone number you type, which KG Inicis requires.
  • Cloudflare: hosting for the website and the app (Cloudflare Pages), and DNS. Its server functions (Cloudflare Pages Functions) sign the practice-test unlock link and handle unsubscribe and account-deletion requests. They also run the AI explanations and checks, send the contact form, and take and check payments. Its short-term storage (Workers KV) holds the cached AI replies and the usage counters described in section 5. Its bot check (Turnstile) protects email sign-up, log-in and password-reset requests in the web app. A scheduled job (Cloudflare Workers) rechecks open payments every 15 minutes; it handles counts and times, not your details.
  • Google Workspace: our email. If you write to an @hansups.com address, such as hello@ or support@, your message and your email address are kept in our Google Workspace mailbox. This includes a refund request and anything you write in it, and the payment alerts our server sends us.
  • Sentry: crash reporting for the app. When something breaks we receive the error and where in the code it happened. We have turned OFF the setting that would attach your identity, so it does not receive your name or email, but like any service you connect to it does see the IP address the report came from.
  • Google (Gemini): the AI tutor. When you ask why an answer was wrong, or ask for a writing or speaking check, the question and what you wrote, or the text your device made from your speech, are sent to Google's Gemini service, which writes the reply in the language you chose. We do not send your name or your email with it. The app asks you before the first time this happens, and the reply can be wrong, so treat it as study help rather than as an authority.
  • YouTube (Google): the app tour video on the home page and on /watch. We use the youtube-nocookie.com player (Google's "privacy-enhanced mode"). Google says a view in this mode is not used to personalize YouTube or the advertising you see elsewhere. The player loads only when you press play, such as "Play the Tour" on the home page. Loading it sends your IP address and browser details to Google. Until you press play, the page sends nothing to Google.

These providers process data on our behalf under their own security and data-processing terms.

4. Sending data outside Korea

Korean law (the Personal Information Protection Act, Article 28-8) requires every transfer of personal data abroad to be published item by item: who receives it and how to contact them, where it goes, what goes, when and how it is sent, why, and for how long. Here it is in full. We make these transfers because they are needed to make and carry out our contract with you. That is why we publish the details here (PIPA article 28-8(1)3). These transfers travel over encrypted (HTTPS) connections, and a plain request to our site is redirected to an encrypted one straight away.

Who receives it, and their contactWhereWhat they get, and whenWhy, and for how long
Supabase Pte. Ltd.
privacy@supabase.com		SingaporeYour sign-in details and sign-up code, your account, profile, photo and study record, your purchase records, and your email-list entry. The database counters, which hold an account id, an order number, or a code made from an email or IP address with our secret key. Sent when you sign up or sign in, each time you study, when you buy, and when you join the email list.To run sign-in and to store it. Kept as section 5 says: the account while it exists, purchase records 5 years, database counters at most 2 days after last use.
Cloudflare, Inc.
dpo@cloudflare.com		Global edge networkRequests to our site and app, sent each time you use them. Also the cached replies in section 5: a writing or speaking check reply (7 days) and a wrong-answer explanation (30 days). Usage counters that hold an account id, or a code made from an email or IP address (up to 25 hours). For the bot check in the web app: your IP address, browser details and a fingerprint of your secure connection.To serve the site, run our server functions and stop bots. Request logs are short-lived; the cached replies and counters last as section 5 says. Cloudflare's bot-check privacy terms give no fixed period for that data.
Plus Five Five, Inc. (Resend)
privacy@resend.com		United StatesYour email address and each email we send you. Examples are a sign-up code, a sign-in or password-reset link and a welcome email. Others are an email-list confirmation or notice, a practice-test link, a receipt, a refund email or an advertising email. From the contact form: your email address, your message and any organisation details you add, on their way to our inbox. Alerts to us: a payment alert names an order number, and an alert about an unfinished account deletion names the account id. Sent each time we email you, or you use the form. Our emails used to record when they were opened and which links were clicked. We turned this off on 9 November 2026. Clicks on links in emails sent before then are recorded until 17 November 2026, when we remove the web address used for tracking. Each record holds the time, the IP address and the mail program or browser. Resend keeps these records for 30 days, so the last ones are deleted by 17 December 2026. After 17 November 2026 we record nothing of this kind.To deliver that email. Resend keeps it for 30 days, then deletes it.
Functional Software, Inc. (Sentry)
compliance@sentry.io		United StatesCrash reports, timings from a 10% sample of app activity, and the IP they came from. Sent when the app hits an error, and for the sampled activity.To find and fix bugs. Sentry deletes it within 90 days, and from its backups within a further 90 days.
Google LLC (Gemini)
support.google.com/cloud/contact/dpo		Any Google Cloud location worldwide. The service we use does not fix one.Your question, and what you wrote or the text your device made from your speech. Never the audio. Sent each time you ask for an explanation or a check.To generate the tutor's reply and the writing and speaking checks. These run on our own Google Cloud project. Not used to identify you. Google does not use it to train its models. We have switched Google's response caching off, so Google keeps nothing once it has answered. One exception: a request flagged by Google's automatic safety checks may be kept up to 90 days. Authorized Google staff may read it to check for abuse.
Google LLC (Google Workspace)
support.google.com/a/contact/googlecloud_dpr		Google's data centres worldwideYour email address and your message, including a refund request, and the payment alerts our server sends us. Sent when you email an @hansups.com address, and with each alert.To receive and answer your email. We keep it until your question is settled. An email about a purchase or refund is kept 5 years, a complaint about a purchase 3 years.
Google LLC (speech model)
googlekrsupport@google.com		Google's data centres worldwideYour IP address, sent when the model downloads. No audio.So dictation runs on your device. Google keeps the download log as its privacy policy says; it publishes no fixed period for it.
Google LLC (YouTube)
googlekrsupport@google.com		Google's data centres worldwideYour IP and browser, sent when the video player loads. It loads only when you press play.To play the video. Google keeps the player's logs as its privacy policy says; it publishes no fixed period for them.

Google's representative in Korea, for every Google service above, is Google Korea LLC: data-access-requests@google.com.

How to refuse. You can use HanSups without the AI tutor: simply do not open it, and nothing is sent to Google. You can also use the speaking rehearsal without dictation: record yourself and play it back instead, and no speech model is downloaded and no text is produced. If your browser offers the model download, declining it leaves the rest of the rehearsal working. Our videos on the home page and on /watch load from YouTube only when you press play. The web app runs a bot check (Cloudflare Turnstile) when you sign up or log in with email, or ask to reset your password. To avoid it, sign in with Kakao, Google or Facebook instead. To stop the rest, delete your account, which removes the data we hold. Refusing means we cannot run the service for you, because storing your study record is the service. We will not treat you differently for asking.

5. Retention

Email list. If you agreed to our advertising emails, your agreement ends one day before two years have passed since you last agreed. On the email list we then delete your address. In the app we stop treating you as agreed. Some addresses joined the list through a sign-up form under our earlier wording. We delete those 30 days after our email announcing that our paid plans are open. If you agree again under the new wording before then, we keep yours. If we also hold your address for the practice test, we delete only the earlier agreement, and the address stays under that rule. If you sign up but do not confirm by the link we email you, we delete your address 30 days later. If we already hold it for the practice test, it stays under that rule instead. Any other address on the list is kept for 24 months, counted from your most recent of: joining, giving consent, or opting out. We delete it at the end of that period. You can also ask us to delete it sooner, and we will.

Opting out. Every advertising email has a one-click unsubscribe link that works immediately. You can also write to hello@hansups.com. When you opt out we keep your address, marked as opted out, for the rest of that 24 months and no longer. That is not us holding on to you: it is the only way to be sure you are not added again by accident. We use it for nothing else, except to tell you once on what date your unsubscribe took effect.

Your account and study data. Kept while your account exists, and deleted with it. Some things outlast the account for a set time. Purchase records stay 5 years, as below. A writing or speaking check reply stays up to 7 days in Cloudflare's cache. A wrong-answer explanation stays up to 30 days, but it is not filed under you. Usage counters end as described below. Backups work as section 6 says, and section 4 says how long our providers keep what they receive. To delete your account, open Profile and choose Delete Account, or email hello@hansups.com from the address you signed up with. See how account deletion works for what is removed and how long it takes.

Sign-ups that are not finished. You may sign in with Kakao, Google or Facebook but not finish signing up. We then delete that account and everything in it 30 days after you signed in. Finishing means confirming your age and agreeing to the Terms of Use. The sign-up screen tells you this. This applies to accounts created on or after 12 November 2026. Legal basis: steps you asked for while making a contract with us (PIPA article 15(1)4).

Purchase records. Kept for 5 years, counted from the last of: the purchase, any refund, and the end of the access it gave. Korean e-commerce law requires records of contracts, withdrawals, payments and supply to be kept that long (전자상거래법 시행령, the Enforcement Decree, article 6(1)2 and 3). They are kept even if you delete your account, but the link to the account is removed. What stays is the order number, what you bought, the amount, how you paid and the dates. It also keeps the name you gave for the receipt and your account's email address. It keeps when you confirmed you are 19 or over, and which terms version you accepted. It notes whether the payment was real or a test, and any refund with its amount, date and reason. They are deleted at the end of the 5 years.

Emails to us. Kept until your question is settled, then deleted. An email about a purchase or refund is kept 5 years, with the purchase records above. A complaint about a purchase is kept 3 years, as the same Enforcement Decree requires for records of complaints and disputes (article 6).

AI tutor usage records. Each time the tutor explains a wrong answer, or checks your writing or speaking, we keep a record. It holds the question number, the model used and what it cost us. For an explanation, the record also notes which answer was chosen and the language of the explanation. It also holds a yes or no mark of whether the explanation seemed to promise an exam result. That mark helps us check the tutor's quality. We also keep technical details, such as how long it took. The records are linked to your account only by a scrambled code, so they are deleted when you delete your account. They contain no name, no email address and nothing you wrote or said. We keep them for 24 months.

The reply to a writing or speaking check. We keep it for 7 days, so that re-opening the same check costs you nothing. It is held in Cloudflare's network cache, filed under a one-way fingerprint made from your account, the question and your own text; that fingerprint cannot be turned back into any of them. The reply can repeat parts of what you wrote or said, so those 7 days are the life of that text too. After 7 days it is gone, and asking again generates a fresh one.

The tutor's explanation of a wrong answer. We keep this one for 30 days, also in Cloudflare's network cache. It is filed under the question, the answer that was wrong and the language — not under you — so the same explanation is reused for anyone who missed that question the same way. It contains nothing you wrote or said: it explains the question, not your answer.

The practice-test unlock link. It expires 24 hours after we send it, and we keep no copy: it is signed rather than stored, so it stops working on its own.

Usage counters. To stop overuse, we count some requests for a short time. The counters for the AI features and our emails are kept in Cloudflare's network. They hold your account id, or a code made from your email or IP address, and expire within 25 hours. The counters kept in our database are for payments and for password-reset requests. They hold your account id, an order number, or a code made from your email or IP address. That code uses our secret key and never contains the address itself. One of them guards the check when you return from the payment window. Each is deleted at most 2 days after its last use. Notes that we sent an alert or a one-time email are kept up to 400 days. They hold an order number or an account id, the kind of note and when it was sent, and nothing else about you. A note with an account id is deleted with the account.

6. How we destroy data

When a retention period ends, or when you ask us to delete something, it is deleted, not hidden. We do not keep a copy marked "deleted". Records are removed from our database, and files such as a profile photo are removed from storage at the same time. On the plan we use, our database provider keeps no backups that we can restore. Deleted data is never restored to the live service.

7. Security safeguards

Korean law requires us to keep your personal data safe (PIPA article 29) and to describe how in this policy (PIPA Enforcement Decree article 31(1)3). These are the measures we take today.

  • Encrypted connections. Our website and app use only encrypted (HTTPS) connections. A plain request is redirected to an encrypted one. A browser that has visited refuses a plain connection for a year after its last visit. Our database provider also encrypts every connection to it.
  • Encrypted storage. Our database provider encrypts all the data it stores (AES-256).
  • Access rules in the database. Every table that holds your data has rules that decide, row by row, who may read or change it. Your account can read only its own records, such as your study record and your purchases. The email list and the database counters are closed to the app and the website. Only our server can reach them.
  • The service key stays on our side. The service key, which can pass those rules, is never in the app or the website. Only our server functions and the operator's own tools use it.
  • Passwords. If you sign up with email, your password goes from the app straight to our sign-in provider, Supabase. It never passes through our own server. Supabase stores only a one-way hash of it (bcrypt with a random salt), not the password itself.
  • A bot check. In the web app (app.hansups.com), email sign-up, log-in, resending a code and resetting a password first pass a bot check (Cloudflare Turnstile). Supabase refuses these requests without a valid check.
  • Rate limits. We limit how often one account, email address, order or network address can use our emails, the AI features and the payment steps. Section 5 says what these counters hold.
  • Access limited to the operator. Only one person can sign in to the provider accounts that run HanSups and hold your data. That person is the operator named under "Who is responsible for your data". These are our database, hosting, email, payment, code and error-report services. No one else has those sign-in details.

8. Cookies & local storage

No cookies at all, on any page. What we do use is storage on your own device: small notes your browser or phone keeps for us, such as which language you chose or that you have unlocked your review. They stay on your device and no third party reads them.

Every single one is listed, with what it is for and how to remove it, on the Cookies and Storage page. There are more than thirty, so naming a handful here and calling it complete would be worse than sending you to the full list.

9. Your rights

Under PIPA you may request access to, correction of, or deletion of your personal data, ask us to stop processing it, and withdraw a consent you gave. To exercise any right, email hello@hansups.com. We answer within 10 days, which is the period PIPA allows, and we tell you the outcome either way. You may also complain to the Korea Personal Information Protection Commission (PIPC).

10. Children

The site is not directed to children under 14. We do not knowingly collect their data. Contact us if you believe we have.

11. Who is responsible for your data

Korean law requires us to name a person, not just an inbox.

  • 개인정보 보호책임자 (Personal Information Protection Officer): SAJID ALI
  • Email: hello@hansups.com
  • Phone: 010-9830-9201

HanSups is operated by one person, so that person is the officer. If that ever changes, this section changes with it.

12. If you think we have got this wrong

Write to us first, because it is usually faster. If that does not resolve it, these are Korean bodies that exist for exactly this, and you do not need a lawyer to contact them:

  • 개인정보분쟁조정위원회 (Personal Information Dispute Mediation Committee): 1833-6972, kopico.go.kr
  • 개인정보침해 신고센터 (Privacy Infringement Report Centre), run by KISA: 118, privacy.kisa.or.kr
  • 개인정보보호위원회 (PIPC): pipc.go.kr

13. Changes to this policy

Privacy contact: hello@hansups.com. We will update this page as the product develops. The version number and effective date at the top of this page change whenever it does.

What changed in version 2.6. This version takes effect on 10 November 2026. The previous version, 2.5, is kept at /legal/privacy-2.5/ so you can compare them. The changes are:

  1. Advertising emails. Before: "We send updates only to addresses that have confirmed." Now: we send advertising emails only to addresses that have confirmed. The sign-up box now asks you to agree to advertising emails (광고성 정보 수신동의), and we record which wording you agreed to. We also send one email to people who asked to be told when paid plans open.
  2. Advertising emails in the app. Before: not offered. Now: you can agree to advertising emails in the app. It is the same choice as on the email list, and you can turn it off in Profile. If your account's email address is not confirmed yet, we put it on the email list instead and email you a confirmation link. Your agreement counts only once you click that link.
  3. How long we keep the email list. Before: 24 months from when you last joined, agreed or opted out. Now: your agreement ends one day before two years have passed since you last agreed, and then we delete your address. An address that is never confirmed is deleted after 30 days. Addresses that joined under our earlier wording are deleted 30 days after our email announcing our paid plans. Other addresses, such as an opt-out record, are still kept for 24 months.
  4. The opt-out record. Before: it is never used to send you anything. Now: we use it only to tell you once on what date your unsubscribe took effect.
  5. The contact form. Before: not listed. Now: section 1 lists what the contact form collects.
  6. Why we use your data. Before: section 2 named the legal basis for the email list and for purchases. Now: it also names the basis for the app, which is carrying out our contract with you. It also names the basis for keeping the service safe with the bot check, usage counters and crash reports.
  7. Our service providers. Before: Supabase stored the email list, and Resend sent the practice-test email and receipts. Now: section 3 lists everything each provider does. For example, Supabase also runs sign-in and holds your account, and Resend sends all our emails, including sign-up codes, password resets and account emails.
  8. Transfers abroad. Before: listed without the reason. Now: section 4 says they are needed to make and carry out our contract with you.
  9. Videos. Before: the home-page video started by itself, so every visit sent your IP address to Google. Now: the video player loads only when you press play.
  10. The bot check. Before: section 4 did not say when it runs. Now: it says when the bot check runs and how to avoid it.
  11. What stays after you delete your account. Before: section 5 said that purchase records stay after deletion, and you closed your account by email. Now: it also lists the other things that stay for a set time, and what a purchase record keeps. You can also delete your account in the app, under Profile.
  12. Usage counters and alert notes. Before: not described. Now: section 5 says what they hold and when they are deleted.
  13. Backups. Before: deleted data could stay for a short time in routine encrypted backups. Now: on the plan we use, our database provider keeps no backups that we can restore.
  14. A new section on security safeguards. Before: none. Now: section 7 lists how we protect your data. The sections after it moved down by one number.
  15. A legal reference. The purchase-records sentence now names the exact clauses of the law it relies on.
  16. Sign-ups that are not finished. Before: not described. Now: you may sign in with Kakao, Google or Facebook on or after 12 November 2026 and not finish signing up. We then delete the account 30 days later. Section 2 gives the legal basis, and section 5 says what finishing means.
  17. Email tracking. Before: not mentioned. Now: the Resend row says what our emails recorded about opens and link clicks, until when, and when those records are deleted. After 17 November 2026 we record nothing of this kind.

Questions about this document: hello@hansups.com. This is the operator's own statement of practice, written in good faith. It is not legal advice.