Legal
Privacy
How AI Lately handles data about readers and about the people it covers, including data-subject requests.
Effective Oct. 15, 2026. This page explains what data AI Lately handles, why, and how you can exercise your rights. Two distinct groups appear here: readers of the site, and people covered by its journalism. Each group gets its own section, because the law treats them differently and so do we.
Readers
What the site collects by default. ailately.com is a static publication served through Vercel. Reading it requires zero accounts, and each page loads two measurement scripts, Vercel Web Analytics and Google Analytics, both described below. Vercel's infrastructure logs standard request data (IP address, user agent, requested URL, timestamp) for security and delivery, retains it for a short period under Vercel's own policy, and shares it with us only as aggregate traffic figures.
Analytics. Since Sept. 26, 2026, Vercel Web Analytics has measured page views and referrers on the site through a cookie-free method that hashes request data and discards it within a day. We see the results as aggregate figures in Vercel's dashboard.
Google Analytics 4 joined it on Oct. 14, 2026, measuring visits, page views, referrers, and broad device and location data. It also records three actions: a click on a button that leads toward the paid calendar, a newsletter sign-up, and a completed Pro purchase, which arrives with its amount, its currency, and Stripe's reference number for the sale. Email addresses, names, and card details stay out of everything Google receives. Outside the European Economic Area, the United Kingdom, and Switzerland, it sets two first-party cookies, _ga and _ga_1T77CJG85T, which tell a returning visitor from a new one and expire after two years at most. Inside those regions, Google's consent mode keeps analytics cookies switched off, so the page sends Google cookieless measurement signals only. Advertising features stay off everywhere: Google Signals, ad personalization, and advertising cookies are disabled for this site. We use the figures to learn which pieces readers find and how they arrive. Google processes the data under its own privacy policy. To opt out, use any standard tracker blocker or Google's opt-out browser add-on.
Photos and videos. Pictures inside a piece load from Wikimedia Commons and Pexels, which see your browser's request for the image the way any web server would. A YouTube video in a piece stays a still picture until you press play; only then does the player load, from YouTube's privacy-enhanced domain, youtube-nocookie.com, under Google's privacy policy.
Email sign-ups. An address you submit through a sign-up card is stored with what you asked for (the daily email, the articles, or both), the page you signed up from, the time, and the country your connection came from. It is kept in a private Vercel Blob store and copied to a private Google Sheet that only the editor can open, under Google's privacy policy. Both serve one purpose: sending you what you asked for. Write to editor@ailately.com and the address comes off both within two days.
Accounts. Since Oct. 20, 2026, you can open a free AI Lately account to save and like pieces and to follow people, companies and agents. Sign-in runs on Clerk, a service that holds your email address, your name if you give one, a password if you choose one, and the Google account link if you sign in that way, under Clerk's privacy policy. Clerk sets the cookies that keep you signed in; they serve no other purpose. AI Lately keeps what you do with the account in a private store: the pieces you saved and liked, who you follow, and when you last looked, keyed to an account id rather than your address. Each piece also keeps a count of likes made from a hashed form of that id, so the count on the page carries no one's identity. Whether your address is on the email list and whether you pay for Pro are copied onto your account so the account page can show them. Delete the account from Profile and security, or write to editor@ailately.com, and the record goes within two days.
Email. A newsletter, when it launches, will run on a dedicated sending subdomain through a platform that supports one-click unsubscribe under RFC 8058. Every address on the list will have opted in directly. Subscriber data lives in that platform, apart from the editorial research base, and is used only to deliver the issues you asked for and to keep the list healthy: addresses with zero engagement over ninety days get suppressed. You can unsubscribe with a single click in any issue, and the request takes effect within two days.
Payments. If paid tiers launch, payments will run through Stripe. Card data stays with Stripe, apart from our systems.
Your rights as a reader. Wherever you live, you can ask what we hold about you, request a copy, seek correction or deletion, and object to marketing. Residents of the EU, the UK, and California hold specific statutory rights, and we honor them in full. Write to editor@ailately.com; we answer within thirty days and confirm identity in proportion to the sensitivity of the request.
People covered by our journalism
What we publish. AI Lately reports on named people in their professional capacity: who joined which company, in which role, from where, and when. The allowlist is deliberately short: name, role, employer, public source, and date. Home addresses, personal contact details, ages, nationalities, health information, family details, and protected characteristics stay out of the record in every circumstance.
Where the information comes from. Company announcements, regulatory filings, government disclosure data, public job boards, academic preprints, the person's own public statements, and reporting from publications of record. Each piece cites its sources, and each Signal entry links to one.
Legal basis. Processing for journalistic purposes falls under the freedom-of-expression provisions of data-protection law, including Article 85 of the GDPR and the equivalent provisions of the UK Data Protection Act 2018. AI Lately operates as a journalistic enterprise with a masthead, published editorial standards, a corrections policy, and bylines, and that purpose is documented here in advance.
Your rights as a person we cover. You can ask what the editorial record holds about you and receive a copy. Pointing out an error prompts a check of the source and a prompt correction under the corrections policy. A request to add a response or an update gets published with the same prominence as the original claim. Requests for erasure of accurate, sourced, professional information get a considered reply; where the journalistic exemption applies, the record stays, and the reply explains why. Write to editor@ailately.com.
Source protection. Confidential sources stay out of the editorial research base entirely. Requests that would reveal a source receive the response that the publication protects its sources.
Data architecture
Editorial research data and any future subscriber data live in separate systems with separate access controls and separate retention rules. Research material is retained for as long as it serves the archive. Subscriber data is retained for as long as you remain subscribed, plus a short suppression record after you leave so we honor your unsubscribe permanently.
Security
Multi-factor authentication protects the registrar, hosting account, code repository, and any future email and payment platforms. Backups are encrypted. A breach involving subscriber data would trigger notification to affected people and, where required, to regulators within seventy-two hours.
Children
The Service is written for professionals and is directed at adults. We collect zero data from children knowingly, and we delete any such data on notice.
International transfers
AI Lately is operated from the United States. Readers and subjects elsewhere should expect their data to be processed in the United States under this policy and, where applicable, under standard contractual clauses maintained by our service providers.
Changes
Updates to this page appear at this address with a new effective date. Material changes get a note on the site.
Contact
Privacy requests: editor@ailately.com. Corrections: editor@ailately.com. Everything else: editor@ailately.com.