[go: up one dir, main page]

Privacy

Effective 20 November 2026. The revision history is at the end.

FactLot collects as little as it can. This notice covers factlot.com, the hosted API and MCP server at api.factlot.com, paid plans, and fact packages sent to another party through the Record. The open-source packages you run yourself send FactLot nothing, unless you call fact_package_send or fact_package_status (in releases after v0.5.0), which reach the Record as described below.

Who we are

factlot.com and api.factlot.com are run by Robert Stovall, a sole proprietor in Texas, USA, doing business as FactLot ("FactLot", "we"). FactLot decides how the information described here is used.

Email: contact@factlot.com
Postal address: PO Box 12488, San Antonio, TX 78212.

What we collect

The website

factlot.com sets no cookies and uses no advertising, tracking or third-party analytics. FactLot's own server counts page views in totals only: how many requests each group of pages (for example the pricing page, or all property pages together) received in a day, and an estimate of how many distinct visitors there were, made from a one-way hash of the IP address that changes every day. The counts hold no IP address, no page a particular visitor opened and nothing that identifies or follows a visitor, and are deleted after 40 days. Its only script, on the pricing and MCP server pages, asks the hosted API whether the free key (see below) is offered and shows a link to it if so; it sends nothing you typed and stores nothing in your browser. Cloudflare, which hosts it, processes your IP address, browser user agent and the page you ask for, to deliver the page and protect the site from abuse. Cloudflare may keep request logs under its own privacy policy; FactLot keeps no access log of its own. The site has no lookup form: an old link to /try/ or /lookup/ is sent to another page with whatever it carried in its address dropped, and nothing is looked up. When a request fails, FactLot's error logs record only the error's name; its page-view totals record only the group of pages; and Cloudflare's request logs may hold the page address.

The hosted API

  • Usage records. For each request we record the time, the API key ID (the first 16 characters of a SHA-256 hash of the key, never the key itself, "free-key" for a free key, or "anonymous" when there is no key), the plan tier, the path, the HTTP method and the response status code. No IP address is recorded. These records are kept in a Cloudflare Workers Analytics Engine dataset.
  • Daily usage totals. We count requests and events in totals for each day: requests by page or route group, registry lookups by tool and by state prefix, registry answers that found nothing by tool and outcome, refusals for a used-up quota or a plan limit, free answers that left earlier values out, checkouts started and completed, reports and model calls, each by kind of caller (no key, free connection, free key, Pro, Team). We also keep an estimate of how many distinct callers of each kind there were, as a fixed-size sketch built from values that are already hashes (the daily-changing hash of the IP address, a connection's ID, or the key ID); a sketch cannot be turned back into a list of callers. The totals hold no IP address, address searched, parcel, key or email, and are kept in Cloudflare Workers KV and, for events, in the Analytics Engine dataset.
  • Rate-limit counters. To enforce the per-minute limit, requests are counted per IP address on the Free plan and per key on paid plans, for the current one-minute window only.
  • Lookup quota counters. To enforce registry lookup quotas, lookups are counted for the current day on the Free plan, keyed by a hash of the IP address (for IPv6, of its /64 prefix), never the address itself, and per subscription for the current month on paid plans. Days and months are UTC. A counter is deleted when its window ends. Registry answers that found nothing and were not counted as lookups are tallied for the current hour under the same key, as a number only (no search text), and that tally is deleted when the hour ends.
  • Report counters. To enforce the monthly report allowance, reports are counted for the current month, keyed by a hash of the IP address (for IPv6, of its /64 prefix), never the address itself, on the Free plan and per subscription on paid plans. Months are UTC. A counter is deleted when its month ends.
  • Report files. When you build a report with report_create, we store the generated file (an XLSX workbook, PDF or ICS calendar) for 24 hours so you can download it, then delete it. The file contains the figures and any text you passed (a title, citations, adjustment reasons). It is stored under a hash of the download link's random token, and nothing else about the request is stored. Anyone who has the link can download the file until it is deleted.
  • Error logs. When a request fails, the Worker logs only the error's name (for example TypeError), never its message or any request content.
  • Key records. For each paid key we store a SHA-256 hash of the key, the plan, the key's status, the Stripe customer and subscription IDs, the subscription status, the date the key was created, the time of the last subscription check, the time the key was revoked (revoked_at), whether a refund or payment dispute has put the key on hold, and the time a payment last failed (payment_failed_at).
  • Free key by email (optional). The Free plan works without a key. If you ask for a free key, at factlot.com/account or with POST /v1/keys/free, you give your email address and confirm that you accept the terms and this notice. We send one email to that address: a link that works once and expires after 30 minutes. It is a transactional message sent through Cloudflare Email Sending, and it contains the link and no key. We send no marketing email unless you tick the separate box for optional emails described below, and nothing else to that address because of this request except the deletion email described below if you ask for it. The address is used in memory to send the email and to make a hash of it; it is not written to storage, usage records or logs, except as described for the optional emails below if you tick that box. What we store instead is a hash of the address: SHA-256 of the lower-case address together with a secret that only FactLot holds. We treat that hash as personal information, because it is the same every time the same address is used. Opening the link only shows a button; pressing it creates the key, which is shown once. We then store a record of the key (a SHA-256 hash of the key, the address hash, the date it was created and, once the key is replaced, the time it was revoked) and, for each address hash, which key is its current one. One address has one active free key: a new key replaces the earlier one, which stops working. A link that is never used creates nothing and expires. Between asking and opening the link we keep a record of the link (a hash of its random ID, the address hash and its expiry) for 30 minutes, and a marker of the address hash for 5 minutes, so that one address gets at most one link email every 5 minutes. A marker that a link was used, held under a hash of its random ID and not linked to the address, is kept for 13 months so that the link cannot be used twice. The link is a web address that you open, so Cloudflare's request logs may hold it; it cannot be used a second time or after it expires.
  • Free key counters. A free key's requests are counted per minute and its registry lookups per UTC day under the key's ID. The free keys used from one IP address also count together toward a shared minute limit and a shared daily lookup cap, and the keys made from one IP address are counted per day (at most 3), all keyed by a hash of the IP address as described for lookup quota counters, never the address itself. Reports are counted for the current UTC month under part of the address hash, so that replacing a key does not restart the count, and also under the hash of the IP address, the same monthly count that reports made without a key use, so that several free keys used from one IP address share it. A counter is deleted when its window ends, or when the free key is deleted (see below), except the counters keyed by an IP address.
  • Deleting a free key. You can delete a free key yourself in two ways. At factlot.com/account, or with POST /v1/keys/free/delete, you give the address and we send one transactional email through Cloudflare Email Sending: a link that works once and expires after 30 minutes, with no key in it. We send it only if that address has a free key, and the answer is the same for every address, so nobody learns from it whether an address has a key and nothing is sent to an address that never asked for one. Opening the link only shows a button; pressing it deletes. Or, with the key itself, send DELETE /v1/keys/free with the key as the bearer token: no email is sent. Either way we delete the key, every key it replaced, the record of the address hash, the report counter kept under the address hash and each key's counters. The deletion email uses the same kind of records as the link email: a link record for 30 minutes, a marker of the address hash for 5 minutes (at most one deletion email every 5 minutes), and a marker that the link was used, held under a hash of its random ID and not linked to the address, for 13 months. These are not deleted by deleting the key, and neither are: a link email you already received, which stays valid until it expires; counters keyed by an IP address; usage records, which hold "free-key" and no key ID or address; report files, which are not linked to the address and are deleted after 24 hours; and Cloudflare's own request logs. If you cannot use either way, email contact@factlot.com from the address the key was issued to and we do it for you.
  • Other transactional email. Paid plans send up to three kinds of message through Cloudflare Email Sending, each only because of something you did and none carrying an API key, besides the watch-list emails described under "Watch lists" below. A welcome email, once, to the address you gave Stripe when a checkout completes: it names the plan and price, says how the subscription renews (monthly, or yearly on Pro yearly) until cancelled, and gives setup steps and links to the account page and the API. We do not store that address unless you tick the box for optional emails described below. A sign-in link, when you enter an address under "Lost your key?" at factlot.com/account and Stripe has a customer with that address who has a FactLot subscription: it names each plan and has a link per subscription that works once, expires after 15 minutes and lets you issue a new key. A connect link, when an app connecting to the hosted MCP server asks for one for an address with a subscription: it names the app and has a link per plan that works once and expires after 10 minutes. Nothing is sent when no subscription matches, and the page answers the same either way. We look the address up in Stripe in memory, and keep a marker of a SHA-256 hash of the lower-case address (no secret added) for 5 minutes for the sign-in link and 2 minutes for the connect link, so that one address gets at most one such email in that time. We send no marketing email except the optional emails described next, and only if you ticked the box for them.
  • Optional emails (only if you tick the box). When FactLot offers optional emails, the free key form and the page you see after checkout each have a separate box, unticked, that says what is sent (if you see no such box, they are not on offer and none are sent): up to 4 optional notes about a free key (one when a lookup leaves out earlier roll years or some of an owner's parcels, one if the key has not been used after 2 days, one when the daily limit is reached, and a summary after 7 days), or up to 2 about a plan (one if the key has not been used 1 day after you buy, and one after 7 days). Each note is sent at most once, never more than one a day, and carries our postal address and a link that stops all of them with one click, without signing in. While they are on offer you can also stop them by entering your address at factlot.com/account/stop (that page exists only then; for an address that gets no optional notes it records a stop only if the address has a free key), and you can always stop them by emailing contact@factlot.com. If you tick the box we record it only when you press the button on the page that the link in the free key email opens (so nobody can sign up another person's address), or, for a plan, when you save your choice on the page after checkout, using the address you gave Stripe. We then store, with your key or subscription, your email address (we cannot send without it), the time you ticked the box, a reference to your key's usage tally or your subscription, and the time each note was sent. That record, and the address in it, is deleted when you stop the notes, when you delete your free key (whether or not optional emails are still offered), and when your plan is cancelled. To send the notes that depend on time we also keep, for each such note, an entry holding the hash of your address and the hour it falls due; it is deleted once handled, and in any case 32 days after it falls due. For a plan we keep a pointer from the subscription to that hash, deleted with the record. When you stop, we keep one marker: the hash of your address described above and the time you stopped, and nothing else, so that you are never sent an optional note again, even if you later ask for a new key or tick the box again. Deleting a key does not delete that marker. The stop link holds the same hash of your address, signed so it cannot be forged, and does not expire; Cloudflare's request logs may hold it. While optional emails are on, a free key's registry lookups are also tallied by day, by tool and by state prefix under the key's ID, never the parcel or address searched, so that the summary can state them; the tally is deleted with the key and otherwise after 90 days. Between ticking the box on the free key form and pressing that button, your address is held in the 30-minute link record. To enforce "at most once" and "at most one a day" we keep two markers in a Durable Object, each named by a one-way hash of your address hash with the message or the day; they hold nothing else, are kept for 395 days, and are not deleted when you stop or delete your key. Optional notes go through Cloudflare Email Sending. Their legal basis is your consent, which you can withdraw at any time as described; withdrawing does not affect notes already sent.
  • Checkout return link. When you start checkout from a property page, the parcel's ID can travel in the checkout's return web address, so that the page after payment, and the welcome email, link back to it. A checkout link that carries an address searched (at most 120 characters of letters, digits and simple punctuation) keeps it there too, though no page of the site makes one any more. It holds no email address, key or name; Stripe's and Cloudflare's logs may hold it.

Watch lists

If a Pro or Team subscription uses watch lists, we store its lists, the registry identifiers on them and, for each record, a summary of its registry data used to detect changes (values, owner of record, the dates and amounts of recorded documents, and hashes; no party names from recorded documents). If you turn on alert emails, we store the address you give for them, send it one confirmation email, and once it is confirmed use it only to send those alerts: one transactional email through Cloudflare Email Sending after each registry update that changed something you watch, each with a link that stops them with one click. Stopping the alerts deletes the address, removing a record or a list deletes its data, and cancelling the subscription deletes all of it.

Connecting an app

When an app such as Claude connects to the hosted MCP server through api.factlot.com/mcp/signin, it opens a FactLot sign-in page at api.factlot.com. If you paste a key there, the key travels in the body of the form, is checked once and is not stored by the page; the connection is tied to the subscription the key belongs to, or for a guest key to that key's ID. If you continue on the free tier, the connection is tied to a salted hash of your IP address range, never the address itself, so that free connections from one address share one daily allowance. For each connection we store the app's name and client ID, the web address it returns to, when the connection was made, when it expires and when it was last used; its access and refresh tokens are stored only as hashes. A connection ends 30 days after the app last refreshed it, or when you disconnect it at factlot.com/account, or when the subscription ends. An app that registers itself is recorded by its name and return addresses for 90 days.

The sign-in page sets two cookies on api.factlot.com. Both hold a random value that scripts cannot read. One ties the sign-in to the browser that opened the page and lasts 1 hour; the other lets a page left open finish in the same browser and lasts 24 hours. Neither identifies you, follows you to another page or is used for anything else. A record of the page (the app's name, where it returns, and hashes of the request and of the second cookie) is kept for 24 hours.

Fact packages sent to another party

fact_package_send is the one tool that passes what you give it to someone else. It runs only when you call it with the name of the person who approved sending. FactLot's API passes the package on and keeps no copy; it goes to the Record (cre-record.vercel.app), a separate service run by the same operator as FactLot, which keeps it so that the other party can answer. The Record stores:

  • the package: its title and subject label; the name of each organisation and of the person given for each; the email addresses given for the sender and the other party, which are kept with the package and shown on no page; each fact with its quote, its page and the SHA-256 fingerprint of the document it cites; the calculation and each item with both figures; the approver's name and the time; and whether the package was a test;
  • hashes of the two links it returns (the other party's link and the sender's private status link), not the links themselves;
  • for a package sent for real, an ID of the FactLot account that sent it (a hash, never the key);
  • the other party's answers: agree or dispute for each item, any reason they write, the name and organisation they give, and the time;
  • a history of what happened to the package and, for a package sent for real, a reliance record for each item accepted or agreed: the two organisations' names, the subject, the package's digest, the decision and the date.

The Record never receives the documents themselves. Anyone who holds the other party's link can read the package and answer it, and anyone who holds the status link can read the answers, so treat both links as you would the package. For a tenant estoppel, the sender can also name a lender or buyer as a relying party: the Record stores that firm's name and role and a hash of its own view link, and anyone who holds that link can read the statements, the tenant's answers and the document fingerprints, and record that the firm relies on a confirmed statement (kept as a reliance record, with the name the firm gives). fact_package_status reads a package with its status link. The Record's database holds no IP address; the request logs of Supabase and Vercel, which host it, may hold one under their own policies. If you are the other party and received a link, this notice covers what you enter on that page too.

Packages are not deleted automatically. To have one deleted, email contact@factlot.com with its link or ID, as the sender or as the other party: we delete the package with its answers and history, and void any reliance records made from it.

Billing

Stripe runs checkout and billing and collects what it needs to take payment: your email address, name, card or bank details, billing address, and a tax ID if checkout asks for one. Stripe handles these under its own privacy policy. In Stripe, FactLot can see your email, name and billing address as you entered them, your subscription status, your invoices, and your card's brand and last four digits. FactLot never sees or stores your full card number.

Email

If you write to contact@factlot.com, we receive your email address, your message and anything you attach. Cloudflare Email Routing forwards it to the operator's mailbox. If you reply to the free key email, your reply comes to the same mailbox and is handled the same way. Please do not send confidential leases or personal data by email.

GitHub

Issues and Discussions on GitHub are public and covered by GitHub's privacy statement. Anything you post there can be read by anyone.

What we do not collect

  • Request bodies, tool inputs and outputs, and documents. Document text is processed in memory to answer the request and is not stored or logged. There are two exceptions. A report you build with report_create: the generated file is kept for 24 hours (see "The hosted API" above). And a fact package you send with fact_package_send: the Record keeps it (see "Fact packages sent to another party" above).
  • Request headers, other than reading the key to authorise the request.
  • IP addresses in usage records.
  • Cookies, tracking pixels or advertising identifiers, other than the two sign-in cookies described under "Connecting an app".
  • Natural-person names in the registry. The registry holds commercial property and the organisations that own it. It is built to keep owners that are organisations and to exclude natural persons' names, and owner records a source withheld are never recovered or inferred. If a record names you as a person, or is wrong, email contact@factlot.com and we will remove or correct it.

We do not use your requests or documents to train models, and we do not build profiles of you.

Why we use it

  • To provide the service you asked for: answering requests, checking keys, applying your plan. This is needed to perform our agreement with you.
  • To send you the free key you asked for: the one link email described above. This is needed to perform our agreement with you. We do not use the address for anything else.
  • To keep the service working and fair: rate limits, quotas, abuse prevention and fixing errors. This is our legitimate interest in running a reliable service.
  • To bill you and keep tax records: needed to perform our agreement and required by law.
  • To answer you when you write to us, and to send notices about your plan, these terms or a security problem.
  • To send the optional emails you ticked the box for: your consent.
  • To send watch-list alerts you turned on, and the one email that confirms the address: needed to perform our agreement with you.
  • To connect an app and to send a fact package when you ask for either: needed to perform our agreement with you. What the other party enters on the Record's page is kept to give the sender the answer they asked for: our legitimate interest and the sender's.
  • To plan capacity: counting requests by tool path, plan and status, with no IP address.

We do not sell personal information, do not use it for advertising, and make no automated decisions about you with legal or similar effects.

How long we keep it

What Kept for
Usage records 90 days
Daily usage totals 40 days (90 days for event totals in Analytics Engine)
Rate-limit counters The current one-minute window
Lookup quota counters Until the day (Free) or month (paid) resets; the hourly tally of answers that found nothing, until the hour ends
Report counters Until the month resets
Report files 24 hours, then deleted
Error logs As long as Cloudflare keeps Worker logs, at most 30 days
Free key records and address hashes Until you delete them yourself or ask us to. After a key is replaced, its record is kept for 12 months and then deleted
Free key link records 30 minutes, then deleted. The marker that a link was used is kept 13 months
Free key counters Until the minute, day or month they count (UTC) ends, or until the free key is deleted
Optional-email consent records Until you stop the emails, delete your free key or cancel your plan (deleted at once); the entry for each note that depends on time until it is handled, at most 32 days after it falls due
Which optional emails were sent As long as the consent record, and at most 395 days
Optional-email stop markers Kept until you ask us to remove them, so that you are not mailed again; they hold the address hash and the time
Optional-email once-only and daily markers 395 days; not deleted by a stop or a key deletion
Free key lookup tally (optional emails on) Up to 90 days, or until the free key is deleted, whichever is first
Watch-list stop-link records The subscription ID under a random ID, no address; deleted when the alerts stop or the subscription is cancelled
Watch lists and alert address Until you remove them, stop the alerts or the subscription is cancelled; an address waiting for confirmation 24 hours; detected changes at most 400 days
App connections Until 30 days after the app last refreshed the connection, or until you disconnect it or the subscription ends; an app's own registration 90 days
Sign-in page cookies and record The cookies 1 hour and 24 hours; the record of the page 24 hours
Fact packages in the Record Until the sender or the other party asks us to delete them
Key records While the subscription is active, then up to 12 months to answer billing questions
Billing records As long as tax and accounting law requires, generally 7 years; Stripe keeps its own records under its terms
Email As long as needed to answer it, at most 24 months
Cloudflare request logs Under Cloudflare's own policy
Supabase and Vercel request logs (the Record) Under their own policies

Sharing and subprocessors

These companies process information for FactLot to run the service:

Company What for Where
Cloudflare Hosting factlot.com and api.factlot.com (Workers, KV, Durable Objects, Analytics Engine), email routing for contact@factlot.com, and Email Sending for transactional email such as the free key link, its deletion link, the welcome email and sign-in links United States; requests are served from its global network
Stripe Checkout, subscriptions, invoices and payments United States
GitHub Source code, releases, issues and discussions United States
Anthropic PBC Model inference, only for doc_extract_lease and report_narrative when you call them United States
Supabase The Record's database and functions, only for fact packages you send with fact_package_send and the answers to them United States
Vercel The Record's web page, where the other party reads and answers a package United States; requests are served from its global network

Two hosted tools use a model, and only when you call them: doc_extract_lease sends the text of the document you submit, and report_narrative sends the tool result you submit, to Anthropic's API for model inference. Every request asks Anthropic to run the inference in the United States. Anthropic does not train models on API inputs. Under its published API retention policy it deletes API inputs and outputs within 30 days of receipt or generation, unless it must keep them longer by law or to enforce its Usage Policy (inputs and outputs that its safety systems flag may be kept for up to 2 years). FactLot stores neither the document, the result nor the model's answer, and logs none of them. Every other FactLot tool runs without any model.

We share personal information otherwise only when the law requires it, to protect the service or people's safety, or with a successor if the FactLot business is transferred, in which case we tell you first. We do not sell or share personal information, in the meaning of California law or any other law.

Your rights

Anyone can ask us to:

  • tell you what personal information we hold about you and give you a copy (access);
  • correct it (correction);
  • delete it (deletion);
  • give it to you in a portable, machine-readable form (portability); and
  • stop using it for a purpose you object to.

We give everyone the rights above. Where the California Consumer Privacy Act or the Texas Data Privacy and Security Act applies, they include the rights that law sets out.

California Consumer Privacy Act (as amended by the California Privacy Rights Act): the rights to know what personal information we collect, use and disclose; to delete it; to correct it; to opt out of its sale or sharing; and to limit the use of sensitive personal information. We do not sell or share personal information and do not use sensitive personal information, so there is nothing to opt out of or limit.

Texas Data Privacy and Security Act: the rights to confirm whether we process your personal data and to access it; to correct it; to delete it; to get a portable copy; and to opt out of targeted advertising, sale, and profiling that has legal or similarly significant effects. We do none of those three. If we decline your request, you may appeal by replying to our answer with the word "Appeal"; we answer an appeal within 60 days. If you are not satisfied with that answer, you can contact the Texas Attorney General.

We will not treat you differently, charge you more or give you a worse service for using any of these rights.

How to use your rights

Email contact@factlot.com from the address on your account, or include your API key ID from a response or your Stripe receipt. Never send us the key itself. A free key you can delete yourself, without writing to us: at factlot.com/account (we email a link to the address) or with DELETE /v1/keys/free and the key. If you cannot, write from the address you asked for it with and say so: we find its records by the hash of that address and delete them. We confirm who you are by replying to that address, answer within 45 days (once extendable by another 45 days if we tell you why), and charge nothing. An authorised agent may ask for you with your written permission.

Security

  • API keys are random, shown once, and stored only as a SHA-256 hash.
  • Every connection to factlot.com and api.factlot.com is encrypted with TLS.
  • We keep as little as possible: no request content, no documents, no IP addresses in usage records, and no card numbers.
  • Stripe handles all card data.

No system is perfectly secure. If a breach affects your personal information, we will tell you as the law requires. To report a vulnerability, see SECURITY.md.

Children

FactLot is a business service for people aged 18 or older. It is not directed to children, and we do not knowingly collect information from anyone under 18. If you believe a child has sent us personal information, email us and we will delete it.

International use

FactLot is run from the United States. Cloudflare serves requests from the data centre nearest you on its global network, and Cloudflare, Stripe and GitHub are United States companies. If you use FactLot from outside the United States, your information is processed in the United States.

Changes to this notice

We post changes here with a new effective date. For a material change we email paid subscribers at least 30 days before it takes effect.

Revision history

  • 20 November 2026: described two things the hosted server now does when you ask for them, with no change to how anything else is handled: connecting an app through the sign-in page (what a connection stores, and the page's two cookies), and fact packages sent to another party with fact_package_send (what the Record keeps, who can read it, and how to have it deleted); added Supabase and Vercel, which host the Record, to the subprocessors.
  • 14 November 2026 (second update): the site's lookup by address (/try/ and /lookup/) was withdrawn; removed its description and that of the script that ran it, and said what happens to an old link.
  • 14 November 2026: described the lookup pages, which carry the address searched or the parcel ID in the page address, and what FactLot's logs, its page-view totals and Cloudflare's request logs keep of it.
  • 13 November 2026: described the hourly tally of registry answers that found nothing and were not counted as lookups, and the daily totals of such answers by tool and outcome; stated that the daily totals keep a state prefix only; stated that the welcome email says how the subscription renews, monthly or yearly.
  • 12 November 2026 (fourth update): gave the operator's postal address (a PO box) in the section on who we are.
  • 12 November 2026 (third update): described the optional emails you can ask for with a separate, unticked box (what is sent and how often, what is stored for your consent and for stopping them, and how to stop them), and the checkout return link; and watch lists for Pro and Team (what is stored to detect changes, the alert address and its confirmation email, and when each is deleted).
  • 12 November 2026 (second update): described the daily totals of page views and API calls by page group, tool and kind of caller, and the estimate of distinct callers, in place of the statement that the website had no analytics of any kind.
  • 12 November 2026 (update): added self-service deletion of a free key (by email link or with the key), what it removes and what it does not; described the welcome, sign-in and connect emails.
  • 12 November 2026: described the optional free API key by email: the one link email, the address hash, the key and link records, the free key counters, how long each is kept, and how to have a free key deleted.
  • 7 November 2026 (update): added report files, kept 24 hours so you can download them, and the monthly report counters, for the hosted reports that opened that day.
  • 7 November 2026: named the operator; listed every record the hosted API keeps, with a retention period for each; added lookup quota counters, billing detail, subprocessors, purposes, and California and Texas privacy rights with how to use them. Replaces the notice of 3 November 2026.