Privacy

Effective date: 7 November 2026.

This page covers the free questions and the reading at pathofliving.com: what reaches us when you use them, why, how long it stays, and what you can ask of us. You do not sign up, and we never ask for your name. You can leave your email if you want news from us or a reminder; “Your email, if you leave it” says what happens to it.

Who we are

Path of Living is run by Udefed, LLC, a limited liability company formed in Delaware, United States, Delaware file number 10762017, and run from Seoul, Korea. Our postal address is Udefed, LLC, c/o Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, USA. For anything on this page, write to support@udefed.com.

Korea's Personal Information Protection Act asks us to name who handles privacy questions and complaints. For Path of Living that is Privacy, Udefed, LLC, at support@udefed.com.

The short version

• The questions and your reading need no sign-up, and we never ask your name.
• If you want news from us or a reminder in a month, you can leave your email. It is kept apart from your answers and is not linked to your reading.
• When you finish, your browser sends your answers to our server twice: once to work out your reading, and once as a record we keep.
• The record includes the two lines you type about yourself, as you wrote them; the line at the end can be left empty.
• A comment on your reading is sent only if you write one.
• We, Udefed, LLC, keep the record with Cloudflare, which hosts the site for us.
• We keep the record for 365 days. Then we delete your reading, your comment and the two lines you typed, remove the ids that point to the record, and keep the answers.
• Until then, you can ask us to delete your record, if you send us your reading's address.
• We count visits to our pages, without cookies and without your answers.

What is not active yet

Some parts of Path of Living are built but switched off. None of them runs on the site today:

• Accounts and sign-in. There are none.
• Paid products. There are none, and nothing on this site is for sale.
• A picture to share. The share button shares a line of text and a link, as “The share button” below describes, and makes no picture.
• News emails. You can ask for news from us, and we keep your choice; we send no news yet.

Before any of these is switched on, this page will describe it and carry a new effective date.

What happens when you take the questions

Before the first question. The first screen says how the questions work, with links to this page and to the terms of use. Pressing Start accepts the terms. None of this run's answers is sent before you finish.

When you press Start or Continue, and again if that code runs out before your record is sent, your browser asks our server for a one-time code and sends it back with your record when you finish. The code holds nothing about you. It shows whether a record came back with a code our server gave out. A program can ask for a code too, so a code does not prove that a record came from this page. Our server does not keep the code; if your record cannot be sent, your browser keeps the code with it until it is sent.

While you answer. Your browser keeps your answers so far in that tab, so a reload does not lose them. They stay there until you close the tab or press Start over, after your reading appears too: a reload then shows Welcome back, and Continue asks our server for your reading again. If we change the questions in the meantime, a reload starts the run over.

When you finish. Your browser sends two things to our server.

The first is what your reading is worked out from: your answers to the questions that place you (39 of them, or 28 if you chose “Nothing right now”), whether you chose it, and the version of the questions. Our server works out your reading from them and sends the passage back; this request itself is not stored.

Apart from your network address and the browser details that every request carries, nothing else goes with this first request: not the two lines you type, not your answers to the two questions that are never used in your reading, not how long you took, and no cookie. If the reading does not come back, your browser tries up to twice more, and sends the same answers again when you press retry or when your device comes back online. It sends them again, too, each time you reload the page after finishing and press Continue, whether or not your reading had appeared.

The second is a record, which we keep. It holds:

• your answers to the questions you were shown, including two that are never used in your reading, if you answered them;
• whether you chose “Nothing right now”;
• the two lines you type, as you wrote them: the main thing you are doing, up to 60 characters, unless you chose “Nothing right now”, and the line at the end, up to 140 characters, if you wrote one;
• how long each answer took and when you first tapped it, where your browser could measure them;
• your result: the type, the state, the tone and the numbers behind them;
• a few numbers your browser works out about how you tapped: how many questions you answered, the longest run of identical answers, the longest run on one side, the share of answers on one side, your middle answer time, how many answers took under about a second, and whether those look unusual;
• three coarse facts about your browser: its language, whether it is a phone, a tablet or a computer, and which of three screen-size groups it falls in;
• a random id for this run, which your browser makes, and the version of the questions and of the record's layout.

Our server adds three things: the time the record arrived, to the second; a random id for your reading; and its own check of the record, which says whether every answer is there, whether the answers came faster than reading allows, whether the times could be measured, whether your tap numbers look unusual, and one word for the whole record: clean, marked or unmeasured.

The check also says, in one word, what came back with the record: the unused code, no code, a code our server did not give or that ran out, or a code another record already used. The record is kept in every case.

The record has no field for a name, an email or a network address. It does hold the two lines you type, as you wrote them, so whatever you put in them is kept with it. This is separation, not anonymity: we do not claim that nobody could ever work out who you are.

If you reload the page after finishing and press Continue, your browser sends the record again under the same run id, and our server keeps it once. If you close the page before you finish, none of this run's answers is sent.

If the record does not get through. Your browser tries once more after a moment. If that fails too, it keeps the record on your device, the two lines you typed included, five at most, and sends it the next time you press Start, or when you reload the page on a run you started in that tab. It sends a record only within fourteen days of keeping it. A record it could not send can stay in your browser until you clear this site's data.

Your reading. Your reading appears on your screen when you finish. This browser keeps a list of the readings it has opened, sixty at most, so you can open one again; the All readings button at the end of your reading opens it. A reading opens from its address, a link that ends in # and 32 letters and digits, and our server shows it to whoever has that address. Anyone who uses this browser can see its list.

The two lines you type

The first line names the main thing you are doing, in up to 60 characters, and the questions after it ask about it by name; if you choose “Nothing right now”, there is no first line, and your state is then set by rule rather than read from your answers, as the method page explains. The second, at the end, is a line in your own words, up to 140 characters, and can be left empty. Both are shown back to you during your visit, neither is scored, and both are kept in your record as you wrote them.

We read them ourselves when we study the records. Nobody else reads them: they are never sent to Anthropic, never shown to another reader, published or quoted, and never appear in a reading's address.

The comment you can leave

While you read, you can tap any line that feels off or unnatural to you. At the end you can score the reading from 0 to 10 and, once you have chosen a score, write anything else that felt off, in up to 400 characters. If you choose a score, and our server has told your browser that your record arrived, your browser sends the score, the lines you tapped (twelve at most) and your comment, and they are stored with your record. They go when you press Send, and also when you page on past that screen or leave the page after choosing a score, so treat anything typed there as sent. If your browser has had no word that the record arrived, none of them is sent. The lines you tap are our sentences, not yours, but which ones you tapped can say something about you.

The comment and the two lines you type are the only things you write on this site that are sent to us, so they are where you could tell us who you are.

We read every comment ourselves, one at a time, with help from Claude, an AI tool made by Anthropic in the United States, which receives the text of your comment and nothing else. We turn off Anthropic's use of our chats for training before we read any comment. Anthropic may still use them, including for training, if its safety systems flag them or if we send it feedback on them; we do not send it feedback. Apart from that, nobody reads your comment but us, and it is never shown to another reader, published or quoted.

Your email, if you leave it

If you give us your email, we keep it only to send what you ticked: news and updates, a reminder in a month, or both. It is stored apart from your answers and is not linked to your reading. We do not sell it or share it for advertising. Every email has a way to leave, and we delete your address from our list when you do, or once the email confirming it has gone.

You can leave it at the end of a reading, on a reading you open again, and on the front page. Both boxes start unticked, and nothing is kept unless you tick at least one and press Keep me posted. Each box you tick is your consent to what it names, and that consent is our ground for keeping your address. With your address we keep which boxes you ticked and, for each box, the version of the words beside it when you first ticked it. We keep days, never times: the day you first left your address, the day you first ticked news (if you ticked news before we began keeping that day, the day you first left your address), and, for the reminder, the last day you ticked it, which its month counts from. We also keep a random key, made when you leave your address (or, for an address left before 7 November 2026, when we first email it), which is what makes the leave link in each email work; the day we last sent you the email confirming your sign-up; while an email to you is on its way, a mark with that day's date; if an email to you is refused as one mail systems will not take, a mark saying so, with that day's date, until you leave or ask us to delete your address; and the day you used your mail app's unsubscribe button, if you did. While a news email is going out, we keep which addresses it has reached, until it has reached everyone; then that list is deleted. We do not keep which page you left it on. Nothing from your reading goes with it: not its address, your answers or your result. Leaving your email is up to you; the questions and your reading work the same without it.

Resend sends our emails for us (see “Who else handles it, and where it goes”). When you tick a box and press Keep me posted, we send you one email confirming what you asked for: the day you asked for news, and the day your reminder is due. We send it only when what you asked for has changed since the last one, at most once to an address in 24 hours, and not past our daily limit for these emails, so a sign-up on a very busy day may get none. It carries nothing from your reading and no advertising. A reminder is one email: it asks whether you want to see where you stand now, links to our front page, and carries nothing from your reading. If you ticked only the reminder, we delete your address from our list once it is sent. When more reminders fall due on one day than we send in a day, the rest go out on the following days, in the order they fell due. News emails are advertising and say so: each subject starts with “(광고)”, and each carries our name, email address, phone number and postal address. We send news only to an address whose box said the news is advertising. We send no news yet.

The confirmation, each reminder and each news email have a link to leave. Pressing the button on the page it opens deletes your address from our list at once and shows you that it is done. If you leave with your mail app's unsubscribe button instead, and you had ticked news, we take your address off the news and reminder lists at once, send one last plain email confirming that you left, normally the next day, and then delete it from our list. If you tick a box again before that email goes, it says so instead, and your new choice stands. If we cannot send it within 13 days, we delete your address anyway, unless you have ticked a box again since. If an email to you bounces for good (the address does not exist), or your mail provider reports it as spam, Resend does not send to that address again. We do not track whether you open an email or click its links. Until we have sent you an email, to have your address deleted, write to support@udefed.com from that address.

Why we collect each item

Each line below says what one item is for. The seven reasons behind them, and our legal grounds, follow in the next section.

• Your answers: to work out your reading, and to check whether each question measures what it claims to.
• The two answers not used in your reading: to compare two ways of asking about the same thing, before either counts toward anyone's reading.
• Whether you chose “Nothing right now”: the questions that follow depend on it, so the answers cannot be read correctly without it.
• The two lines you type: to see what the questions that name your main thing were answered about, and to compare what readers write about themselves with the readings they got, so the questions and the writing can be improved.
• Answer times and first taps: to see which questions are hard to read, and to find records answered faster than reading allows.
• Your result and the numbers behind it: to check that the same answers always give the same reading, and to see where the line between one type and the next should sit.
• The numbers about how you tapped: to find records filled in without reading, so they can be left out of the statistics.
• Browser language, device type and screen-size group: to check that the questions work the same on a phone as on a computer, and whether readers whose browser is set to another language answer them the same way.
• The random run id: so a record your browser sends twice is stored once, so you can ask us to delete it, and so a copy of a record you asked us to delete is not stored again.
• The random reading id: so your reading can be opened again, and so a deletion request can find your record.
• The question version and the record layout version: so your reading is worked out from the same questions you were shown, and answers given to different wordings are never mixed.
• The time the record arrived: to know when its 365 days are up, and to tell rounds of readers apart.
• Our server's check: to know which records to leave out of the statistics.
• Your score, the lines you tap and your comment: the score tells us whether a reading missed, the lines tell us which sentences felt off or unnatural, and the comment tells us why.
• Your network address: our server reads it as each request arrives and never keeps the address itself, so it is never written into a record. A scrambled form of it, made with a secret key, counts your requests for about an hour, so that no one address can flood the site. For the newer kind of address (IPv6), the counts are kept for the blocks of addresses yours belongs to, each scrambled the same way.
• What a page sends GoatCounter: to count how many people visit each page, where they came from, and how many start the questions and see a reading.
• An email you send us: to answer it.
• An email you leave for updates, with the boxes you tick, the days and the version of the words: the email and the boxes, to send what you ticked; the days, as the record of when you first said yes and to know when a month is up for the reminder; the version of the words beside each box, as the record of what you said yes to; the leave key, so that one click can take your address off the list.

What we use it for, and on what legal ground

We use what you send for seven reasons.

1. To give you your reading, and a way back to it. The answers sent for your reading, the record, and the reading's id.

2. To find out whether the reading lands, and to improve the questions and the writing. The record, the two lines you type and, if you give them, your score, the lines you tap and your comment. We publish statistics about how well the questions work, always for groups and never anyone's own answers.

3. To plan a possible paid version of this instrument. The same records, studied only as group statistics: we may build a paid version, and if we do, we want it built on what the free one taught us. Your own answers will never be used for a paid reading of you without a fresh, separate ask, and the paid service keeps its records in a separate database with no way to look yours up.

4. To keep the records honest. The run id and our server's check.

5. To keep the site up, and to know how many people visit it and finish it. The request counts made from your scrambled network address, and the visits and the two counted moments GoatCounter counts.

6. To answer you, if you write to us. Your email and what you wrote.

7. To send you what you ticked, if you leave your email. Your email, the boxes you ticked, the days, the version of the words and the leave key.

Pressing Start accepts the terms of use. That is not the ground we keep your answers on.

For the first six reasons our ground under European and UK privacy law is our legitimate interest, GDPR Article 6(1)(f): our interest in giving you the reading you asked for and a way back to it, in finding out whether it lands and improving the questions and the writing, in planning a possible paid version, in keeping the records honest and the site running and knowing how many people use it, and in answering the people who write to us. Because that ground is not consent, there is nothing to withdraw for those six; what you have instead is the right to object, set out below.

For the seventh, our ground is your consent, GDPR Article 6(1)(a). You give it by ticking a box and pressing Keep me posted, one box for each thing you want, and you can withdraw it at any time by leaving, as “Your email, if you leave it” says. Withdrawing does not undo what we did with it before.

Under Korea's Personal Information Protection Act we use all of this, apart from an email you leave for updates, without asking your consent, on these grounds. Your answers, whether you chose “Nothing right now”, the version of the questions, and an email you send us: because giving you the reading you ask for, and answering you when you write, needs them (Article 15(1)(4)). The record, the two lines you type and a comment, if you write one: our legitimate interest in finding out whether the reading lands, improving the questions and the writing, planning a possible paid version and keeping the records honest (Article 15(1)(6)). Your network address and what a page sends GoatCounter: our legitimate interest in keeping the site up and knowing how many people visit it and finish it (Article 15(1)(6)). Both uses under Article 15(1)(6) ask more of us: our interest has to clearly outweigh your rights, and the use has to stay closely tied to that interest.

An email you leave for updates, and what goes with it, we use only with your consent (Article 15(1)(1)), which you give by ticking a box; each box is a consent of its own. If you do not give it, nothing changes about the questions or your reading.

Your reading is worked out from your answers by a fixed formula, and nothing is decided about you with it.

No law and no contract requires you to answer. If you do not, there is no reading, and nothing else follows.

How long we keep it

• The request for your reading: not stored. The same answers are kept in your record, below, if it reaches us.
• The request counts made from your scrambled network address: each deletes itself about an hour after the first request it counted; if that deletion fails, it is tried again six times over about three and a half hours, then once a day. When an address goes over its limit, the Cloudflare location that refused it also keeps a marker under the same scrambled name until that hour is out.
• The note that a one-time code was used: which record used it, in scrambled form; it deletes itself about an hour after the code was given.
• The run id of a record you asked us to delete: kept on a list of deleted runs, the run id alone, so that a copy of the record still waiting in a browser is refused and not stored again. It points to no record in our database. We keep it with no end date.
• Your record and your reading: 365 days from the time the record arrived. Then a clean-up that runs every hour deletes your reading, so its address opens nothing, and removes the run id, the reading id, the two lines you typed and your comment from your record. The rest of the record, your score and the lines you tapped included, stays, without either id and with its arrival time cut to the day, and we keep it with no end date, for reasons 2 and 3.
• Copies held by our database host: a deleted record, an address taken off the email list, or a record the clean-up has changed, can still be restored from our database host's own history for up to 30 days, and then it is gone from there too.
• Working copies on our own computer: to study the records, to check a backup, or to repair the database after a fault, we sometimes copy records, or lists of their ids, to our own computer. Its disk is encrypted, and its backups leave these copies out. We delete a working copy when the work is done, and within 30 days at most, with any file or log from that work that holds a record or its ids. Until then, a record deleted from the database can still be in it.
• Notes our program writes: when something fails on our side, or an address goes over its limit, our program may write a one-line note, with no network address and no answers. It also writes a short line of counts each hour and each day, with no network address, no answers and nothing you typed. Cloudflare keeps these notes for us for 7 days at most.
• Cloudflare's own records of requests: Cloudflare also keeps its own records of the requests that reach its network, under its own privacy policy. How long is Cloudflare's to set, not ours.
• Resend's record of the emails we send: the address each email went to and the email itself, for up to 30 days after sending. An address that bounced for good, or that a mail provider reported as spam, stays on Resend's list of addresses it will not send to.
• What GoatCounter keeps: each page view is added to hourly and daily counts of which page was seen, the page you came from or the campaign named in the link you followed, your browser and system, your screen size and your rough location. The two counted moments are added to the same counts, each under its fixed name. GoatCounter stores no network address. To tell a first visit from a return, it holds your network address and browser details in memory only, for up to 8 hours, linked to a random id, and never writes them to its database. The counts stay in our GoatCounter account for as long as we run the site.
• What your browser holds: see “In your browser” below.
• An email you send us: until the matter it raises is closed. Then we delete it, and our reply with it.
• Which addresses a news email has reached: while it is going out, until it has reached everyone; then that list is deleted. This is kept for every address it reached, including an address that left with its mail app's unsubscribe button while that email was going out.
• An email you leave for updates, and what goes with it: on our list until you leave or ask us to delete it. If you ticked only the reminder, we delete it from our list once the reminder has been sent. If you leave with your mail app's unsubscribe button while you get news, we keep it until we have sent the one email confirming that you left, or for 13 days at most if that email cannot be sent, unless you have ticked a box again since.
• Your comment at Anthropic: we delete each chat in which we read comments within 7 days of the read. Anthropic then deletes it from its own systems within 30 days, though it may keep a chat its safety systems flagged for longer.

Deleting a record means removing its rows from the database. Apart from the copies named above, we keep no other copy of a record. Taking an address off the list means removing its row from the database. Deleting an email means removing it from the mailbox and then from the mailbox's bin. For up to 25 days after that, it can still be restored from our mail account's admin settings; after that it is gone.

Who else handles it, and where it goes

The services below handle what you send. Cloudflare, Google and Resend do so on our behalf, each only for the work named with it. Anthropic receives the text of a comment when we read comments with Claude, under its consumer terms and privacy policy, with no other agreement with us. GoatCounter counts our visits under its own terms and privacy policy, with no other agreement with us; its privacy policy says it shares what it receives with no third party.

• Cloudflare, Inc. (United States) hosts the site, runs the programs that work out your reading and receive your record, keeps the short-lived request counts, stores the records in two databases we created, which we asked it to keep in western Europe, and keeps the emails readers leave for updates in a third, apart from both. Every request passes through it, your network address among them. It works on our behalf under its data processing addendum.
• Anthropic, PBC (United States) receives the text of your comment when we read comments for reason 2, and nothing else: not your score, the lines you tap, the two lines you type, your answers, your result or any id.
• GoatCounter (run by Martin Tournoij in Ireland, with its data kept by Hetzner Online GmbH in Finland and Germany) counts visits to our pages. When a page loads, your browser fetches GoatCounter's script and then sends GoatCounter the page's address, anything after a ? in that address, the page's title, the address of the page you came from, your screen's size, and whether your browser looks automated, with the network address and browser details every request carries. On the page with the questions, your browser also tells GoatCounter when you press Start and when your reading appears, so we can count how many people start and how many finish: each time, a fixed name for that moment, your screen's size and whether your browser looks automated, with the network address and browser details every request carries. It receives none of your answers and nothing you type.
• Google LLC (United States) runs the mailbox at support@udefed.com. If you write to us, it holds your email address and what you wrote.
• Plus Five Five, Inc., which runs Resend (a United States company), sends the emails you ticked and the email confirming them, from Japan (Tokyo), the region of our account. When we email you, it receives your email address and the email's words, and nothing from your reading. It does this on our behalf under its data processing addendum, which comes with our account with it.

Cloudflare and Google each have parts of this work done by other companies, and publish who they are: Cloudflare at cloudflare.com/gdpr/subprocessors, Google at workspace.google.com/terms/subprocessors.html. GoatCounter's data is kept by Hetzner Online GmbH, as above.

Apart from GoatCounter, our pages load nothing from other sites: the fonts and everything else come from pathofliving.com.

Nobody else receives your answers, your record or your comment. We do not sell your data, there are no ads on this site, we do not follow you across other sites, and we do not join your answers to anything else.

Moving data out of Korea. We are run from Korea, and the services above are outside Korea, so in Korean law's terms what you send through this site is moved abroad. Korean law allows this on two grounds. To Cloudflare, Anthropic, Google and Resend, because the service you agreed to in the terms of use, from your reading and its record to the comments we read, and our answers when you write, needs their work, and the details below are published here (Article 28-8(1)(3)). The same ground covers an email you leave for updates, which goes to Cloudflare, and to Resend when we email you: you ask for the news or the reminder by ticking its box, and keeping your address and sending to it needs their work. To GoatCounter, because it keeps its data in the European Union, which Korea's Personal Information Protection Commission has recognised as protecting personal data at substantially the same level as Korean law (Article 28-8(1)(5)). These are the details Korean law asks us to publish:

• What goes: to Cloudflare, everything described under “When you finish”, “The comment you can leave” and “Your email, if you leave it”, and the network address and browser details every request carries; to GoatCounter, what a page sends when it loads, and the two counted moments (see above); to Anthropic, the text of your comment; to Google, an email you send us; to Resend, your email address and each email we send you.
• Where: Cloudflare, the United States as the company, western Europe for the stored records, where we asked it to keep them, and for each request whichever of its locations serves it, with each request count kept wherever Cloudflare places it (its locations are listed at cloudflare.com/network); GoatCounter, Ireland, with its data kept in Finland and Germany; Anthropic, the United States; Google, the United States and the other countries where it keeps mail; Resend, Japan (Tokyo), where it sends our emails from, and the United States as the company.
• When and how: as each request leaves your browser, over an encrypted connection; to Anthropic, when we read comments, over an encrypted connection; to Google, when you send us an email; to Resend, when we send you an email, over an encrypted connection.
• Who receives it, and how to reach them: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA; GoatCounter, run by Martin Tournoij, through the contact details at goatcounter.com; Anthropic, PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA; Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA; Plus Five Five, Inc. (Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA.
• What for, and for how long: the reasons and the periods above.
• How to refuse, and what refusing does: do not press Start, or close the page before the last question. Then none of this run's answers is sent and there is no reading, though your visit still passes through Cloudflare. Pressing Start also sends any record from an earlier run that your browser kept because it could not send it, and so does reloading the page partway through a run you started in that tab. Closing the page does not undo that. "If the record does not get through" says which records it sends. Not writing a comment keeps it from Anthropic and from us. Not leaving your email keeps it from Cloudflare, Resend and us: nothing is sent unless you tick a box and press Keep me posted, and the questions and your reading work the same without it. Your visit is still counted by GoatCounter; to keep your visits from GoatCounter, use the switch under “To object” below, or block its script in your browser or with a content blocker; the questions work the same without it.

For readers in the EU and the UK. Cloudflare, Anthropic and Google are in the United States, and so is the company that runs Resend, which sends our emails from Japan (Tokyo). Cloudflare is certified under the EU-U.S. Data Privacy Framework, which the European Commission's adequacy decision of 10 July 2023 covers, and under its UK Extension, which UK regulations of 2023 recognise in the same way. Its data processing addendum, part of our agreement with it, uses the EU standard contractual clauses, with the UK addendum for UK data, if that certification lapses. Google's data processing terms use the EU standard contractual clauses for such data, or another lawful transfer route Google has adopted. When Resend sends our emails, its data processing addendum, part of our agreement with it, uses the EU standard contractual clauses, and the UK's for UK data, and says that Resend complies with the EU-U.S. Data Privacy Framework. Anthropic receives the text of a comment under its consumer terms and privacy policy, and we have no data processing agreement or standard contractual clauses with it. GoatCounter keeps its data in the EU. You can read Cloudflare's addendum at cloudflare.com/cloudflare-customer-dpa, Google's terms at cloud.google.com/terms/data-processing-addendum and Anthropic's privacy policy at anthropic.com/legal/privacy, and we will send you a copy if you ask.

What you can ask of us

To delete your record. Write to support@udefed.com with your reading's address: the link that ends in # and 32 letters and digits, which you can find by opening the reading from this browser's list of readings. If your browser never got an address for a record, because it had no word that the record arrived, it keeps that record in this site's data, with the run id it made for it; that run id, sent with the record's full set of answers, works too. We delete the record, its comment and the reading by hand, within 10 days of your email, and tell you when it is done. When we delete a record, its run id goes on a list of deleted runs, so that a copy still waiting in your browser is refused and not stored again. A run id you send us with its answers goes on that list even when we hold no record under it yet. "How long we keep it" says how long the list keeps it. We do not ask who you are or why.

To object. You can object at any time to our keeping your answers, for any of the reasons above or all of them. Write to the same address with your reading's address. We do not weigh your objection against our reasons: we delete the record as above. To keep your visits out of GoatCounter's counts, open the method page this way once: GoatCounter's script then stops counting this browser, and opening it that way a second time starts it again. You can also block GoatCounter's script; the questions work the same without it. There is nothing in the request counts or in GoatCounter's counts that we could pick out as yours: the request counts are deleted about an hour after they start, and GoatCounter's counts hold no network address.

To take your email off the list. Use the leave link in any email from our list: pressing the button on the page it opens deletes your address from our list at once. Or write to support@udefed.com from that address; we delete it, and what goes with it, within 10 days of your email, and tell you when it is done.

What we do not offer. We do not send anyone a copy of a record, change one, or set one aside unused. Your record has no field for a name or a contact detail, and an email you leave for updates is not linked to it, so we could not tell whether the person asking is the person who answered: a deletion harms nobody, and a copy could. When you ask us to delete a record, we look for it only by its reading's address or its run id. After its 365 days a record holds neither, so from then on a request to delete it finds nothing.

About an email you send us. You can ask us for a copy of it, ask us to correct it, ask us to stop using it, or ask us to delete it before its matter is closed. Write to support@udefed.com. Someone you authorise in writing, or your legal guardian, can make any request on this page for you.

To complain. You can complain to us first, at the same address. You can also complain to your data protection authority: in the EU, the supervisory authority of your country; in the UK, the Information Commissioner's Office; in Korea, the Personal Information Protection Commission, whose report centre, run by KISA, takes complaints at privacy.kisa.or.kr or by phone on 118, and whose Personal Information Dispute Mediation Committee mediates at kopico.go.kr; elsewhere, your local equivalent.

In your browser

We set no cookies. We count visits to our pages with GoatCounter, without cookies. Nothing on our pages reads your browser's Do Not Track or Global Privacy Control setting, and nothing on them follows you across other sites.

Your browser holds five things for this site, all on your device:

• the run you are part way through or have just finished, the two lines you type included: until you close the tab or press Start over;
• a record that could not be sent, the two lines you typed included: as described above, five at most;
• the list of readings this browser has opened: sixty at most, until you clear this site's data;
• whether you paused the motion: until you press play again or clear this site's data;
• the theme you picked for the pages of the sixteen types, Auto, Light, Dark or Color: until you pick another or clear this site's data.

The run holds where you are, your answers so far, whether you chose “Nothing right now”, the two lines you type, how long each answer took and when you first tapped it, the version of the questions, a random id your browser makes for the run, and, once you finish, when you finished and whether your reading has appeared. From these, your browser sends us what “When you finish” describes, a record that could not be sent, as described above, and the address of a reading you open from the list. Whether you paused the motion and the theme you picked are never sent. In Auto, each type page follows your device's or browser's light or dark setting; your browser reads that setting on the page, and it is never sent. None of the five is a cookie. You can refuse them by blocking this site's data in your browser's settings: the questions still work, but a reload loses your progress, a record that fails to send is lost, the list of readings stays empty, and each type page opens light or dark, as your device or browser is set. Clearing this site's data removes all five. GoatCounter's script also looks in this site's storage for a setting that tells it not to count your browser. It writes that setting only when you open one of our pages with #toggle-goatcounter at the end of its address, and removes it when you do that again; clearing this site's data removes it too.

The share button

The share button uses your device's own share sheet, or copies to your clipboard, the line that names your result and a link to this site, never your reading's address. Where it goes is your choice, and nothing about it, including whether you shared at all, is sent to us.

How it is protected

• Our pages, and everything they send, travel over an encrypted connection. An address typed with http:// gets nothing back but a redirect to the encrypted site.
• Your record and your reading are kept in two separate databases. The record's database belongs to a separate program with no public address. The program that answers your browser can add records to it and find one by its ids, but none of its calls hands an answer back.
• Your network address is never written into a record, and the request counts are kept under a scrambled form of it.
• An email you leave for updates is kept in a third database, with no reading id, answer, result, page or time of day beside it, and nothing in the other two points to it.
• The reading our server sends back is marked so that no cache stores it. Reading pages are kept out of search engines and sent without a referrer, and each network address can make only so many requests an hour.
• We read the stored records through the one Cloudflare account that holds both databases and the email list, and Cloudflare, like any host, can reach what is stored on its machines. Anyone who broke into that account could reach both databases and the email list, and, once we send email, anyone who broke into our Resend account could read the emails it sent in the last 30 days, which is why the record has no field for a name, an email or a network address, and the list holds nothing from a reading. The exceptions are the two lines you type and a comment, which hold whatever their writer typed.

Under 16

This site is for people 16 and older. We do not ask your age, and we cannot check it.

The site is not meant for children, and we do not knowingly keep anything from anyone under 16. If you believe someone under 16 sent us a record, write to us with the reading's address and we will delete it. If a child writes to us, we delete the email once the matter is closed, as with anyone else.

If something goes wrong

If anything we hold is ever exposed, we cannot reach you directly unless you wrote to us or left your email for updates, because the record holds no contact detail. We would post a dated notice on our status page (pathofliving.com/status), on the front page, on this page and on the method page, saying what happened and when, which information it touched and what we did about it, and we would report it to the authorities the law names.

Changes to this page

If this page changes, the effective date at the top changes with it, and a short note here says what changed. If what we collect ever changes, we will say so here before it changes, not after.

29 October 2026. Saving is switched on. Your answers, the two lines you type and a comment, if you write one, are now kept, as this page describes. Until this date saving was switched off, and nothing you answered was kept. The line under Start now links this page and the terms, and pressing Start accepts the terms.

30 October 2026. A line you tap while you read now marks one that feels off or unnatural to you. Before this change it marked one that did not fit you. This page now says there are no ads on this site, where it said we run no advertising.

31 October 2026. The pages of the sixteen types now follow your device's or browser's light or dark setting, and let you pick their theme: Auto, Light, Dark or Color. Your browser remembers your pick. “In your browser” now names it as a fifth thing your browser holds; it stays on your device.

6 November 2026. You can now leave your email for news and updates from Udefed, a reminder in one month, or both, at the end of a reading, on a reading you open again and on the front page. A new section, “Your email, if you leave it”, says what is kept and why; it is the seventh reason we use what you send, and its ground is your consent. We send no email yet.

7 November 2026. Resend now sends our emails, and joins the services that handle what you send. When you leave your email, we send one email confirming what you asked for. “Your email, if you leave it” says what each email holds, how to leave, and what Resend keeps, and names what we now keep with an address: the day you first ticked news, the leave key, the day we last confirmed your sign-up, a mark while an email is on its way or set aside, the day you used your mail app's unsubscribe button, and, while a news email goes out, which addresses it has reached. Emails from us are no longer listed as not active; news emails still are, and we send no news yet.