Privacy Policy
Last updated: November 18, 2026 · version b72a97e8
The short version
We designed Let's Live There so that we know as little about you as possible. Here is what that means in practice:
- There are no accounts. Your survey answers, saved places and kinds of place live in your browser. Clear your browser's site data for letslivethere.com, or press "Reset" in the footer, and they are gone.
- When you run results, your weights and filters are sent to our server to be scored and are not kept. When you ask for an AI summary or type a custom criterion, those go to the AI model we use (Anthropic) under our account. Don't type personal information into a custom criterion. We keep a monthly count of how often each custom criterion is asked for, with nothing that says who asked.
- We measure how the site is used with our own first-party system: a random visitor id cookie that lasts 13 months, a session id, and a log of page views and product events (a survey start, a results view, a saved place, a share) with the referrer or campaign that brought you here. It records what a browser did, never who you are: no IP address, no answers, no typed text, no email. We also use Plausible, a cookieless service, for top-line traffic counts.
- If you buy the pass, we keep your email address and the pass record. If you join a plan, we keep the plan's code, the label you chose and your priorities for as long as the plan is in use.
- We do not sell your personal information, and we do not share it for advertising. Ads are chosen by the place on your screen and by your own stated priorities, inside our own system, without tracking you across sites.
- If you ask us to, we'll introduce you to places on your shortlist: we send you one email on a community's behalf, and the community learns who you are only if you reply. Everything else we may add later (a newsletter, third-party ad networks as fill) will be opt-in, explained before you choose, and easy to undo.
- When you finish the survey, your answers are added to nationwide counters that carry no visitor id and cannot be traced back to you. We use them for an annual public report on what people want in a place.
- Questions or requests: [email protected]. The full policy below is the version that counts.
1. Who we are and what this policy covers
1.1. This policy describes how Watkyn Corporation, a Delaware corporation ("we," "us," "our"), handles information in connection with letslivethere.com, including the survey, results, place pages, the Journal at letslivethere.com/journal, the pass and related features (the "Service"). Our mailing address is 5830 East 2nd Street, PMB 99469, Casper, WY 82609, United States.
1.2. It covers visitors and pass holders. Advertisers who use our advertiser portal are covered briefly in section 8 and fully in the advertiser terms.
1.3. The Service is intended for residents of the United States. It may be used by people aged 13 and over; buying the pass, asking a community to contact you and subscribing to email require that you be at least 18. The Service is not directed at children under 13 (section 13).
2. How the Service is designed
2.1. There are no user accounts. You do not sign up, log in or give us a name to use the free Service.
2.2. The Service keeps your work in your own browser (section 3) and sends information to our servers to do something you asked for (score your answers, write an AI summary, rate a custom criterion, create or open a share code or a plan, buy or restore a pass, send us a message) and to measure how the Service is used (section 5.4). Section 5 lists exactly what reaches us and what we keep.
2.3. We do not use Google Analytics or any third-party tracking script. Our measurement is first-party: our own event log (section 5.4) and Plausible Analytics, a cookieless service whose script we serve from our own domain and which reports only aggregate page views, referrers and a handful of goals (such as a survey start or a pass purchase). Plausible sets no cookie and does not identify or track individual visitors. We also read Google Search Console, which tells us which searches on Google led people to the Service in aggregate; it contains nothing about you individually.
3. What stays in your browser
3.1. The following is stored in your browser's local storage for letslivethere.com and is not sent to us except as described in section 5: your survey answers and filters, intake progress, your kinds of place (saved preference sets), your saved places and shortlist, pinned comparisons, your "group near-identical neighbors" preference, dismissed notices and dismissed ads, a short trail of recently viewed places, and, in session storage for the current tab, which Journal article you arrived from (for 24 hours) and a tab-scoped note of the place page you came from.
3.2. You control this data. Clearing site data for letslivethere.com in your browser, or using "Reset" in the site footer, removes it, along with the visitor id cookie. Because it is in your browser, it does not follow you to another device unless you use a share link or restore a pass.
4. Cookies
4.1. We set only first-party cookies, and only these:
| Cookie | What it does | How long |
|---|---|---|
llt_vid | A random visitor id with nothing else in it. It keys our event log (section 5.4) so that we can count visitors, sessions and return visits, and it keys the daily limits on free AI features so that they apply per browser rather than per network address. It is not linked to a name, email or pass. | 13 months, renewed on each visit |
llt_sid | A random session id, so that one visit's page views and events can be counted together. A session ends after 30 minutes without activity, or when you arrive again from a new source. | 30 minutes of inactivity |
llt_pass | Identifies a pass you bought or restored in this browser. It is signed by us and names the pass record; it holds no personal information. | Until the pass expires |
llt_article | The identifier of the Journal article that brought you to the Service, so that our logs can credit the article for a later survey start. Article id only. | 24 hours |
fys_gate | During a private test period only: a signed token showing that this browser entered the tester passcode. Removed when the Service opens to the public. | 30 days |
fys_admin | A signed token set only for our own administrators when they sign in to the administration pages. Visitors never receive it. | 12 hours |
llt_preview | Set only when you open an advertiser preview link we sent you: a signed token naming that preview, so that the preview banner and its sample ad are shown as you move around the site. It identifies the preview, not you, and is never set for ordinary visitors. Clearing cookies removes it. | 45 days |
4.2. These cookies are set by us and read only by us. There are no third-party cookies, no advertising cookies and no cookies from any analytics vendor. The visitor and session ids exist to count usage and enforce limits; they are not used to build a profile of you, to target advertising, or to follow you to other sites.
4.3. You can block or delete cookies in your browser, or press "Reset" in the footer. Deleting llt_vid gives you a fresh visitor id (and a fresh daily count). Deleting llt_pass removes the pass from that browser until you restore it (section 5.7).
4.4. Global Privacy Control. If your browser sends the Global Privacy Control signal, we treat it as a request to opt out of any sale or sharing of your personal information under the state laws that recognize the signal (section 10.3). Because we have no accounts, the signal can only apply to the browser that sends it.
5. What reaches our servers, and what we keep
5.1. Scoring requests. When you view results, your weights and filters are sent to our server, scored against the dataset, and returned. They are not stored. Our event log records that a results run happened and how many rows it produced (section 5.4), not what your weights were.
5.2. AI requests. When you press the button for an AI summary of a place, or when a custom criterion you typed needs to be rated, our server sends the relevant data to Anthropic's API under our account: your weights, the place's figures, and, for a custom criterion, the text you typed. Section 6 explains how that text is handled, including the monthly count of how often each criterion is asked for (section 6.5), and what Anthropic does with it. The reply is cached by us so that the same request need not be paid for twice; the cache holds the generated text and the inputs that produced it, not any identifier for you.
5.3. Page views. Opening a place page, a Journal article or any other page is an ordinary web request. Our hosting provider and our content-delivery network receive the request, including your IP address and your browser's standard headers, as every web host does; see section 5.11.
5.4. Our event log. The Service records page views and product events in its own log so that we can understand how it is used and report honestly on it. Each record carries: a timestamp; the visitor id and session id from the cookies in section 4; the page path and type; whether the screen is phone- or desktop-sized; the release and dataset version; and, on the first record of a session, the referring site, any campaign parameters in the link you followed (UTM source, medium, campaign and content), the landing page and a classification of the source (search engine, AI assistant, social network, email, referral, the Journal, or direct). The events are things like a page view, a survey opened, a first answer, a survey completed (with the number of answers and filters), results viewed, a place viewed and where you came to it from, a place saved or unsaved, a comparison opened, a search used, a share link or card created or opened, a plan created, joined or viewed, an AI summary requested, a custom criterion added, an ad shown, viewable, clicked or dismissed, a pass gate encountered, a pass bought, restored or refunded, and a client error code. We also keep one first-touch record per visitor, keyed by a hash of the visitor id, holding the source and landing page of that visitor's first session, so that later visits can be attributed to what first brought them. The log never contains your IP address, your answers or weights, the text of a custom criterion, an email address, a name, or a plan label. Whether the browser holds an active pass may be recorded as a yes or no; which pass it is, and the email behind it, are never written to the log.
5.5. The AI spend log and the traffic log. Separately, for each AI call we log the model, the token counts, the cost, a per-request id and a keyed hash of the visitor id; and we log each results run, survey start and place-page view with the same keyed hash, the number of grouped result rows, and the Journal article id when the visit was attributed by the llt_article cookie. No IP address, no prompt text, no criterion text, no answers. The hash is computed with a secret key and cannot be reversed.
5.6. Rate limiting. To stop abuse, our server keeps short-lived counters in memory: per visitor id and per network address for AI requests, and per network address for passcode attempts, share-code creation, pass checkout and pass restore requests. These counters hold salted hashes, reset within 24 hours, and are never written to disk. This is the only use the Service itself makes of your IP address.
5.7. The pass. If you buy the pass, we keep: the email address you give at checkout; the pass record (dates, price, status, how it was issued); hashed single-use restore tokens; the transaction reference our payment processor assigns; and, in our revenue ledger, the amount and date of the payment and of any refund with a short hash of that reference, never your email. Your card details go to the payment processor and never touch our servers. We use the email address to send your receipt and restore links. The pass record is kept apart from our logs: we never write a pass id or a pass holder's email alongside the visitor id, and we do not use the pass to look up what a browser did.
5.8. Plan together. A plan is stored on our server under its code and holds each member's chosen label, each member's priorities (weights), the shortlist, reactions, suggested places and a "visit first" choice. No email addresses or other contact details are collected. A plan's priorities include whatever its members chose to rate, which may include preferences about a community's religious life, political lean, age profile, diversity or the LGBTQ+ filter; those are stored only because the plan needs them to merge priorities, are visible only to people who hold the code, and are never used for advertising or for anything else. The number of members a plan can hold is the limit shown in the product. A plan that no one opens for 12 months is deleted. The person who created it can delete it sooner.
5.9. Share codes. A results share link can be shortened to an eight-character code. The code stores the same answers and place ids the long link carries, and nothing about you. Share codes are deleted 12 months after they were last opened.
5.10. Journal events. When you come to the survey from a Journal article, your browser tells the Journal's service that a survey started, that a first answer was given, and that the survey was completed, each with the article id only. The receiving service adds a timestamp. No visitor identifier, no answers, no IP address.
5.11. Hosting and delivery. The Service runs on Fly.io in the United States, behind Cloudflare, which provides our domain name service and passes every request through its network. Like any web host and network, Fly.io and Cloudflare receive each request and keep their own transient infrastructure logs, which can include IP addresses, under their own retention policies. We read Cloudflare's aggregate request counts to check our own figures against an independent source; we do not read individual request records from either provider.
5.12. Images from other sites. Place pages show photographs hosted by Wikimedia Commons, loaded directly by your browser from that site. Wikimedia receives the standard request information (such as your IP address) that any site you load an image from receives, and nothing about your answers. Terrain imagery on place pages comes from the U.S. Geological Survey, but our server fetches it and passes it to your browser; your browser does not contact the USGS.
5.13. Messages you send us. If you email us, we keep the message and our reply for as long as we need to handle it and for our records, up to three years.
If you use the "Send a correction or comment" form on a Journal article, your message (its type, your text and, if you give one, an email address for a reply) goes to our editorial desk and is held there privately; the Service itself stores nothing from the form. We never publish the message and never use it for advertising, analytics or AI prompts. A correction becomes an editorial work item, and any reply is an email written by a person. We erase the text and any email address 90 days after the item is closed, keep a record of the outcome that does not identify you for one year, and erase messages identified as spam after 30 days.
5.14. What we do not collect. We do not collect your name (unless you email us, buy the pass or ask us to reserve an advertising placement, and then only what you give), your postal address, your phone number, your precise location, your contacts, or anything from your other accounts or devices. We do not fingerprint browsers and we do not track you across other websites.
5.15. Aggregate survey statistics. When you finish the survey, the Service adds to a set of counters: how many finishers gave each priority each weight; for each place in a finisher's top ten, which priorities carried which weight; which filters were used; and the finisher's state, taken from a coarse region label our network provider attaches to the request, never from the IP address itself, counted against the places in their top ten. These are counts only. No visitor id, session id or other key is written with them, so they cannot be traced to a browser or a person, and the event log in section 5.4 still never contains your answers or weights. Preferences about political lean, religious community, the LGBTQ+ filter, diversity and the age of a community are counted on their own and never against places. Any figure we publish or share from these counters is suppressed where fewer than 20 finishers are behind it. We use them for an annual public report on what people across the country say they want in a place and for aggregate insight we provide to economic-development partners, under the commitments in section 9.5.
6. AI processing
6.1. We use Anthropic's Claude models through Anthropic's API, under our commercial account, to write place summaries and explanations and to rate custom criteria. Each request contains your weights, the figures we hold for the places involved, and, for a custom criterion, the text you typed. Requests do not contain your IP address, the visitor id, your email or any other identifier.
6.2. Anthropic processes these requests as our service provider under its commercial API terms, which do not permit it to use our inputs or outputs to train its models. Anthropic may retain API data for a limited period for abuse detection under those terms.
6.3. A custom criterion is text you wrote. We may send it to the model, may use it to run a small number of web searches to rate places against it, and keep the resulting ratings, indexed by the criterion text, so that another visitor who types the same thing gets the same answer without a new paid request. That stored rating has no link to you. Do not include personal information in a criterion.
6.4. AI-written text is labeled where it appears and can be wrong. It is not used to make any decision about you.
6.5. Counting custom criteria. We also count how often each custom criterion is asked for, month by month, so that we can rate the common ones in advance for everyone. The count holds the text of the criterion and a number for the month. It holds no visitor id, session id, network address or time of day; it is kept apart from the logs in sections 5.4 and 5.5, which still never contain the text of a criterion; and nothing in it links a criterion to you. Our staff can see a criterion in the count only once it has been asked for at least five times, and a person reads a criterion before we add it to the ones we rate in advance. We keep each month's count for 24 months. If you typed something you would like removed, email [email protected] with the text and we will delete it from the count and from the stored ratings on the live Service. Deletion cannot reach backup copies already made: they are encrypted, are not read in ordinary operation, and expire on the schedule in section 12 (nightly backups after 35 days, server snapshots after 60 days, monthly backups after 400 days). If we ever restore from a backup, we delete it again. The count itself records only the month. Because backups are made every night, comparing one night's backup with the next could show the day a criterion first appeared; only an administrator holding the backup key could do that, and we do not do it.
7. Advertising
7.1. Ads on the Service are chosen by our own system from advertisers who have bought placements with us. The choice is made by the place on your screen and, for some placements, by overlap between the ad's declared subjects and the priorities you have stated; your priorities are sent to the ad route for that purpose and are not stored by it. Cards in the row of featured places on the home page are shown to every visitor alike, in rotation, and nothing about you is used to choose them. Every ad carries a "Why this ad?" explanation that states the actual reason it was chosen.
7.2. Advertising never affects scores, rankings or search. There are no ads in the survey, the comparison view or the map.
7.3. Housing advertisers (agents, builders, communities and the like) are shown by the place on the page, or to every visitor alike, and never by anything you told us about yourself. We never select them using, and "Why this ad?" never cites, your preferences about schools or childcare, religious community, the LGBTQ+ filter, the age of a community, diversity or political lean.
7.4. We record ad impressions, viewability, clicks and dismissals in our event log (section 5.4) and report aggregate counts to advertisers. Advertisers never receive anything that identifies you.
7.5. Today there are no third-party ad networks and no third-party advertising scripts on the Service. If we add a network to fill unsold slots (section 9.4), its code will load only inside a labeled ad slot, after the page content, never in the survey, the comparison view or the map; where the law requires it we will ask for your consent through a consent manager first, and you will be able to opt out as described in section 10.
8. Advertisers and prospective advertisers
If you use our advertiser portal, we collect your business contact name, email address, company, the creative and copy you upload, and billing information handled by our payment processor. We use it to review, publish and bill your campaign and to report its performance to you. Payments and refunds are recorded in an append-only revenue ledger holding the amount, the date, an invoice number or a short hash of the payment processor's reference, and the advertiser's business name; it never holds card data or a buyer's email address. If you ask us to reserve a placement from an advertiser preview page, we collect your name, your work email address and any message you include, and we use them to respond to you and to follow up about advertising with us. These are business records. Portal records are kept for the life of the relationship and as long afterward as tax and accounting rules require; reservation requests are kept for 24 months, and the copy emailed to our advertising mailbox for up to three years. The advertiser terms describe this in full.
9. Things we plan to offer, and how we will handle them
The Service will grow. This section describes features we intend to add, and two that launched with these rules already in place (sections 9.2 and 9.5), so that you know now what to expect. Each is optional where it involves you, and none of the others is live as of the "Last updated" date.
9.1. Real payments. Payments for the pass and for advertising will be processed by Stripe. Stripe receives your card details and billing information directly and handles them under its own privacy policy; we receive a transaction reference, the last four digits of the card and the email you gave.
9.2. Introductions to places on your shortlist. After results, you may ask us to introduce you to places you shortlisted. If you do, we ask for your email address and confirm it by sending you a link; we keep nothing beyond the address until you click it, and an unconfirmed request is deleted after seven days. Once confirmed, we keep: your email address, the places you chose, your top-weighted priorities with every preference about schools or childcare, religious community, the LGBTQ+ filter, the age of a community, diversity or political lean removed, and the version and time of the consent you gave. We never hand this record to anyone. When a community you chose has an agreement with us, we send you one email on its behalf, from us, with the community's reply address; the community learns who you are only if you reply, and what you say to it is between you and the community. Communities that sell or rent housing (agents, builders, developments and the like) are not eligible, and the Service refuses them in code. Introductions can be sent for six months after you opt in; at six months we send one closing note if none of your places joined; and we delete the record 12 months after you opted in, or sooner if you ask. Every email we send under this feature carries a one-click link that stops further introductions, and you can also write to [email protected]. Because your details are never disclosed to a community unless you choose to reply, this is not a sale or sharing of personal information under the state laws that use those terms; a reply is a disclosure you direct. You must be 18 or older to opt in.
9.3. Newsletter. An email newsletter you can subscribe to with your email address. Every message will carry an unsubscribe link and our mailing address. We will not add pass holders or advertisers to it without their asking.
9.4. Third-party ad networks. We may use an advertising network to fill ad slots that no direct advertiser has bought. Networks use their own cookies or identifiers and may use information about your visit for their own purposes, which some state laws treat as "sharing" for cross-context behavioral advertising. Before any network code runs, we will update this policy, provide a consent manager where the law requires one, honor the Global Privacy Control signal and the opt-out in section 10.3, and keep network code out of the survey, the comparison view and the map.
9.5. Aggregate research. We analyze survey answers only in the aggregate form described in section 5.15 and may publish or license those aggregates (for example, how often people across the country rate a priority as essential, or which priorities people who match a region most often hold). Aggregates are built so that they cannot reasonably be linked to any person, and we commit to maintain and use them only in that form, not to attempt to re-identify anyone, and to require the same of anyone we license them to. We will never publish or license personal information.
9.6. Affiliate links. Journal articles and place pages may include links to movers, insurers, utilities, licensed real-estate referral networks and similar services, through which we earn a commission. Clicking such a link takes you to the partner's site, which collects information under its own policy; we receive only aggregate referral and commission reports, not your identity, unless you provide it to the partner and the partner reports it back for commission purposes.
10. Your choices and your rights
10.1. In your browser. You can clear everything the Service stores in your browser at any time, including the visitor id, with "Reset" in the footer or your browser's controls (section 3.2). You can delete or block cookies (section 4.3). You can use the Service without ever giving us an email address.
10.2. Requests to us. You may ask us to tell you what personal information we hold about you, to correct it, to delete it, to give you a copy in a portable form, or to limit how we use it. Email [email protected]. We will confirm receipt within ten business days and respond within 45 days, extending once by 45 days if we need to and telling you why. You may use an authorized agent; we will ask for proof of authorization. If we refuse a request, we will say why and you may appeal by replying to our decision; we will answer the appeal within 45 days. We will not discriminate against you for exercising a right.
10.3. Opt out of sale or sharing. We do not sell personal information, and we do not share it for cross-context behavioral advertising. Introductions (section 9.2) disclose your details to no one; you stop them with the link in any introduction email or by emailing [email protected]. If and when a third-party ad network is live (section 9.4), you may opt out of its sharing at letslivethere.com/privacy/choices, by sending the Global Privacy Control signal from your browser, or by emailing [email protected]. An opt-out made from a browser applies to that browser; an opt-out by email applies to the email address you name. We do not use or disclose sensitive personal information to infer characteristics about you, and the only sensitive preferences we hold on our servers (section 5.8) are used solely to run the plan you joined.
10.4. What we can and cannot identify. Most of what the Service handles is anonymous by design. We cannot connect a visitor id or a hashed token in our logs to a person, so a request about "my log entries" cannot be fulfilled beyond telling you that; you can, however, end the trail yourself by pressing "Reset," which discards the visitor id. We can act on: a pass record, if you give us the email used at purchase; an introduction record, if you write from the email you confirmed; a plan, if you give us its code and tell us which member label is yours; a share code, if you give us the code; a custom criterion, if you give us its exact text (section 6.5); messages you sent us; and advertiser records. To verify a request we will ask you to write from the email address on the record or to supply the code.
10.5. Residents of California and other states with consumer privacy laws (including Colorado, Connecticut, Delaware, Oregon, Texas, Utah and Virginia) have the rights in sections 10.2 and 10.3 under those laws, and this policy serves as the notice those laws require. In the 12 months before the "Last updated" date we collected these categories of personal information: identifiers (a random visitor id and session id for every visitor; an email address from pass holders, advertisers, prospective advertisers and people who opted in to introductions only); commercial information (pass purchases and advertiser orders); internet activity (the event log, spend log and traffic log in sections 5.4 and 5.5, held only against the visitor id or a hashed token); and user content (plan labels and priorities, custom criteria, and the places and priorities kept for an introduction). We collected them from you directly and from your browser's requests. We used them for the purposes in sections 5 through 8. We disclosed them only to the service providers in section 11.2. We did not sell or share personal information. We retain them for the periods in section 12. We do not collect precise geolocation, biometric, health, financial-account or government-identifier information.
10.6. Nevada residents. We do not sell covered information as defined in Nevada law. You may email [email protected] to record a request that we not sell it in the future.
11. How we share information
11.1. We do not sell personal information. We share it only as follows.
11.2. Service providers that process information on our behalf and under our instructions:
| Provider | What it does | Location |
|---|---|---|
| Fly.io | Hosts the Service and its data | United States |
| Cloudflare, Inc. | Domain name service, content delivery and request routing; and R2 object storage, where we keep write-once archives of our event log and of monthly summary tables (section 12) | United States |
| Anthropic, PBC | AI model processing (section 6) | United States |
| Plausible Insights OÜ | Cookieless aggregate web analytics (section 2.3) | European Union |
| Stripe, Inc. | Payment processing (planned; section 9.1) | United States |
| A transactional email service (Resend or similar) | Sending receipts, restore links and, later, newsletters (planned) | United States |
| Watkyn LLC (an affiliate under common ownership, acting as our service provider) | Operates the host that runs our editorial desk, where Journal correction and comment messages are held | United States |
We will keep this table current as providers change.
11.3. At your direction. With the people who hold a plan code or a share link you distribute; with a community you reply to after an introduction (section 9.2), which then receives whatever you write to it; with affiliate partners you click through to (section 9.6).
11.4. Legal and safety. When we believe in good faith that disclosure is required by law, subpoena or court order, or is necessary to protect the rights, property or safety of the Service, our visitors or the public, or to enforce our Terms.
11.5. Business transfers. If we sell, merge or transfer the Service or its assets, information we hold may transfer with it, subject to this policy, and we will post notice.
11.6. Aggregates. De-identified aggregate data as described in section 9.5, and the aggregate usage figures we derive from our event log, which contain no personal information.
12. How long we keep information
| What | How long |
|---|---|
| Data in your browser | Until you clear it |
llt_vid | 13 months, renewed on each visit; llt_sid 30 minutes of inactivity; llt_article 24 hours; llt_pass until the pass expires; fys_gate 30 days during a private test period; fys_admin 12 hours, administrators only; llt_preview 45 days, preview links only |
| Event log (raw records, section 5.4) | 13 months on our servers. Each day's records are also copied to a write-once archive, normally within a few days; an archive copy cannot be changed or deleted for 400 days after it is made and is deleted when that lock ends, so it lasts a few days longer than 13 months |
| Visitor first-touch records (first source and landing page, per visitor hash) | 13 months |
| Daily aggregates derived from the event log | Kept indefinitely; they contain no personal information |
| AI spend log and traffic log | 90 days |
| Rate-limit counters | In memory only; reset within 24 hours |
| AI response cache | Kept to avoid repeat requests; contains no identifier |
| Stored ratings of custom criteria, with the text of each criterion as it was typed (section 6.3), including the criteria we rate in advance | Kept indefinitely, so that the same criterion is not rated twice, until we delete a criterion on request (section 6.5); contain no identifier |
| Monthly count of custom criteria (section 6.5) | 24 months after the month counted; contains no identifier |
| Ad events | Two years; contain no personal information |
| Journal events | Aggregate counters, kept; contain no personal information |
| Plan together | Deleted 12 months after the plan was last opened, or sooner by its creator |
| Share codes | Deleted 12 months after last opened |
| Pass records and email | For the life of the pass and three years afterward; restore tokens expire after 30 minutes and are stored only as hashes |
| Revenue ledger (payment and refund amounts and dates, invoice numbers or a short hash of the payment processor's reference, advertisers' business names; never card data or a buyer's email) | At least seven years, for tax and accounting; we set no end date. Monthly tables drawn from the ledger are also kept in a write-once archive |
| Advertiser records | Life of the relationship plus the period tax and accounting rules require |
| Advertiser reservation requests (preview page form) | 24 months; the copy of each request that is emailed to our advertising mailbox is kept as a message you sent us, up to three years |
| Introduction records (confirmed email, chosen places, non-protected priorities, consent version and time) | 12 months from opt-in, or sooner on request; introductions sent only in the first six months; an unconfirmed request deleted after seven days |
| Aggregate survey counters (section 5.15) | Kept indefinitely; they contain no personal information |
| List of our own staff browsers (hashes of their visitor ids, marked so that our own visits are left out of our counts) | Kept indefinitely; our own browsers only, never a visitor's |
| Messages you send us | Up to three years |
| Journal correction and comment messages (text and any reply address) | Erased 90 days after the item is closed; spam erased after 30 days; a non-identifying outcome record kept one year |
| Hosting and delivery providers' infrastructure logs | Under Fly.io's and Cloudflare's own retention |
| Encrypted backups of our data, which can hold a copy of anything above that is kept on our servers | Nightly backups 35 days; server snapshots 60 days; monthly backups 400 days. Something deleted from the live Service, by the periods above or at your request, leaves the backups on that schedule. Backups are not read in ordinary operation, and after a restore we delete again whatever had been deleted |
13. Children
The Service is not directed at children under 13, and we do not knowingly collect personal information from them. There are no accounts, so a child cannot register. If you believe a child under 13 has given us personal information (for example, in a plan label or at pass checkout), email [email protected] and we will delete it.
14. Security
We protect information with measures appropriate to how little we hold: encrypted connections (HTTPS) everywhere, signed cookies that cannot be forged, hashed tokens in logs, no card data on our systems, restricted administrative access, nightly backups and write-once archives. No method of transmission or storage is perfectly secure, and we cannot promise absolute security. If a breach affects your personal information we will notify you as the law requires.
15. Visitors outside the United States
The Service is built for people choosing a place to live in the United States, and its data is processed and stored in the United States. If you use it from elsewhere, you do so on that basis and your information will be transferred to and processed in the United States, where privacy laws may differ from those where you live.
If you are in the European Economic Area, the United Kingdom or Switzerland: our legal bases for processing are performance of the service you asked for (scoring, AI requests, plans, share codes, the pass), our legitimate interests in operating, securing, measuring and improving the Service (the event log, rate limiting, ad events), and your consent (the introductions opt-in, and any future newsletter or network advertising). You have the rights of access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent at any time; exercise them at [email protected]. You may also complain to your local data-protection authority.
16. Changes to this policy
We will post any change here and update the "Last updated" date. If a change materially reduces your rights or expands what we collect or share, we will post a notice on the Service for at least 30 days before it takes effect and, for pass holders, email the address on file. Earlier versions are available on request.
17. Contact
Privacy requests and questions: [email protected]
General questions and corrections: [email protected]
Legal notices: [email protected]
Mail: Watkyn Corporation, 5830 East 2nd Street, PMB 99469, Casper, WY 82609, United States
Version b72a97e8 is the pinned digest prefix of the approved text of this page.