Privacy Policy

What we collect when you use MaybeLater, what we do with it, who else handles it, and what you can do about it.

Last updated November 20, 2026

The short version

  • We collect what we need to save your articles and send them back to you: your email address, what you save, and how you use your library.
  • We don't sell your data, we don't show ads, and we don't use your data to train AI models.
  • With your permission, AI models write summaries, tags and a few other things for you. You can say no, or turn it off later, and MaybeLater still works.
  • You can export your library, turn off our emails, and delete your account yourself, at any time.

Who we are

MaybeLater is run by MaybeLater LLC, [Postal address to be added]. We are the controller of your personal data under the GDPR and UK GDPR, and the business responsible for it under US state privacy laws. For anything about your data, email support@maybelater.io.

Our representative in the European Union (GDPR Art. 27): [EU representative to be added, or removed if not required].
Our representative in the United Kingdom (UK GDPR Art. 27): [UK representative to be added, or removed if not required].
We haven't appointed a data protection officer; we aren't required to.

This policy covers the MaybeLater website (maybelater.io), the iOS app and its share extension, the browser extension, the emails we send, and the API and AI-assistant connection.

What we collect

Your account

  • Your email address, which is how you sign in (with a one-time code) and where we send your digest.
  • Your name, if you give it, or if Apple or Google share it when you sign in with them.
  • If you sign in with Apple or Google, an identifier from them that links that sign-in to your account, and (for Apple's private relay addresses) whether Apple still forwards email to you.
  • Your timezone, so the digest arrives on Sunday morning where you are, and your interests, if you pick any.
  • Your settings: email and notification choices, whether you've agreed to AI features, reading preferences.

What you save

  • The address (URL) of each page you save, and its title.
  • The page's text. Usually our servers fetch the page themselves. When you save from the browser extension or the iOS share sheet, your device can also send the text of the page as it appears to you, which is useful for pages our servers can't reach. That text can include anything on the page as you saw it, so think twice before saving pages that show private information.
  • What we derive from the page: the cleaned-up article, its reading time, and (with your permission) an AI summary and tags.
  • Your own tags, folders, hearts, archive and read state, and how far you've read.
  • Bookmarks you import from Pocket, Instapaper or a browser export.
  • Reports you send us about an article that didn't come through properly.

What we make for you

  • Your weekly digests, and the monthly Hindsight reports on Plus (your reading stats, a reading "archetype" and, with your permission, a short AI-written summary of your month).
  • Suggestions: articles picked for you from our own collection, based on what you save and hide.

Payments

If you buy Plus on the website, Stripe collects your card details directly; we never see or store your full card number. We receive your Stripe customer ID, your plan and its status, trial dates, the card type and its last four digits.

If you buy Plus in the iPhone app, Apple handles the payment and we see none of your payment details. Apple tells us about the subscription: its transaction IDs, the plan, the App Store environment, when it was bought and renews or ends, whether it's set to renew, any free trial or payment problem, and any refund. The app gives the purchase a random identifier of ours so Apple's notices reach the right account.

Devices and usage

  • Your IP address and browser or device type, which our servers see with every request. We use them to keep you signed in, to rate-limit and prevent abuse, and in server logs.
  • On iOS, a push notification token if you allow notifications.
  • Product analytics events: see Analytics.
  • Errors our servers log while handling your requests. If you've chosen to share analytics with app developers in iOS settings, Apple also sends us crash reports; we don't add a crash reporter of our own.

On your device

The iOS app keeps your sign-in token in the iOS Keychain (shared with its share extension so it can save for you), a queue of saves made while offline, a cache of your library and articles for offline reading, entries in the iOS Spotlight index so you can find saves from search, and settings and analytics events waiting to be sent. The browser extension keeps your sign-in token, a cache of your library and its settings in the browser's extension storage. Signing out clears your token.

How we use it, and our legal basis

Under the GDPR we need a legal basis for each use of your data. Here they are.

What we do Legal basis
Run your account, sign you in, save and sync your library, fetch and clean up articles, index them for search, build your digest and send itContract: it's the service you asked for (Art. 6(1)(b))
AI summaries and tags, the digest's subject line, search by meaning, and the Hindsight write-upYour consent (Art. 6(1)(a)), which you can withdraw in Settings at any time
Plus subscriptions, billing and tax recordsContract, and legal obligation for the records tax law requires us to keep (Art. 6(1)(c))
Suggestions and the Hindsight report's statsContract: they are features of the service
The short note about Plus in the digestLegitimate interests in telling you about our paid plan (Art. 6(1)(f)); you can unsubscribe from the digest email
Product analytics, error reports and debuggingLegitimate interests in understanding how MaybeLater is used and keeping it working; you can object
Security, rate limiting, fraud and abuse preventionLegitimate interests in keeping the service and its users safe
Emails about your account: sign-in codes, email-change confirmations, payment problems, and material changes to these policiesContract, and legal obligation where the law requires us to tell you
Complying with the law, and establishing or defending legal claimsLegal obligation, and legitimate interests

AI, and what it sees

We use a little bit of AI. Here is exactly where your data meets it. We don't train AI models, and nothing below is used to train one by us.

Only with your permission

Each app asks before any of this happens, and you can turn it off in Settings on the website, in the iOS app or in the extension. If you haven't agreed, none of it happens and your saves show no AI summaries.

  • Summaries and tags. We send an article's title, address and text to an AI model through OpenRouter, which returns a summary, tags and a category. Every save gets this.
  • Your digest's subject line. We send the titles of the week's saves to an AI model through OpenRouter.
  • Your Hindsight write-up (Plus). We send the month's reading stats (numbers, top sites and topics) to an AI model through OpenRouter.
  • Search by meaning. When you search your library, we send what you typed to OpenAI to turn it into a vector we can compare with your saves.

None of these requests includes your name, email address or account ID. A summary is written for the article, not for you: once made, it's shared with anyone else who saves the same page.

For every save

These run whether or not you've agreed to AI features, because saving an article depends on them. They work on the page, not on you: nothing about your account goes with it.

  • Fetching the page. We send the address you saved to Firecrawl, and if that fails to Jina AI's Reader, which fetch the page and return its text.
  • Cleaning it up. We send the page's text, title, author and date to an AI model through OpenRouter, which tells us which lines are menus, ads and other clutter so we can remove them.
  • Checking it's the whole article. We send the page's text to TypeSafe's Jev model, through OpenRouter, which tells us whether we got the full article or only a paywall teaser.
  • Indexing it. We send the article's title and summary (if it has one) to OpenAI to make the vector that powers search and suggestions.

OpenRouter passes each request to the company hosting the model, currently OpenAI, Microsoft Azure, Amazon Bedrock, Google and TypeSafe. We choose models from well-known providers and send them only what the task needs.

Who else handles your data

We don't sell your personal data, and we don't share it for advertising. These service providers process it for us, only to provide their service to us:

  • Laravel Cloud (and the cloud infrastructure it runs on): hosting, databases and backups.
  • Resend: sends sign-in codes, digests and other emails.
  • Stripe: payments for Plus. Stripe is also a controller of some payment data under its own privacy policy.
  • OpenRouter and the model hosts it routes to (OpenAI, Microsoft Azure, Amazon Bedrock, Google, TypeSafe): the AI tasks above.
  • OpenAI: search and suggestion vectors.
  • Firecrawl and Jina AI: fetching the pages you save.
  • PostHog: product analytics (see Analytics).
  • Apple: Sign in with Apple, push notifications, Plus bought in the iPhone app, and notices from Apple when you delete your Apple ID, stop sharing your email, or revoke Sign in with Apple, and about your App Store subscription.
  • Google: Sign in with Google, and the YouTube Data API, which we ask for details of videos you save.

Some services see your IP address because your browser or app loads something from them directly:

  • our website and emails load fonts from Google Fonts;
  • site icons next to your saves load from Google's favicon service, which also sees which site the icon is for;
  • article images, in the reader, the apps and our emails, load from the sites that published them.

We may also disclose data:

  • when you ask us to, for example by connecting an AI assistant to your library (Plus). That assistant then receives what it requests from your library, under its own terms, until you revoke its token on the Integrations page;
  • when you share a Hindsight report: anyone with its link can see that report, until you delete your account;
  • when the law requires it, or to protect the rights and safety of our users, the public or us;
  • to a buyer or successor if MaybeLater is sold or merged, who would be bound by this policy.

International transfers

We're based in the United States, and so are most of our providers, so your data is processed in the US. When we transfer personal data from the EU, the UK or Switzerland, we rely on the EU–US Data Privacy Framework (and its UK and Swiss extensions) where the recipient is certified, and otherwise on the European Commission's standard contractual clauses (with the UK addendum). You can ask us for a copy of the relevant safeguards.

How long we keep it

  • Your account, saves, tags, folders, digests and reports: for as long as you have an account. You can delete individual saves at any time.
  • When you delete your account: it's closed straight away, and we delete your account data within 30 days. See Deleting your account.
  • Articles: the shared copy of a page (its text, summary and tags) isn't tied to anyone and stays while anyone has it saved or it's among our suggestions.
  • Sign-in codes: expire after 15 minutes and are deleted within the hour after that.
  • Guest saves made in the browser extension without an account: 30 days, unless you create an account and they move into it.
  • App sign-in tokens: until you sign out, sign out everywhere, or they expire after a year.
  • Web sessions, which store your IP address and browser type: until you sign out or the session expires.
  • Push tokens: until Apple tells us they're invalid, or 30 days after your device last checked in.
  • Imported files: deleted within a few hours; the bookmarks become saves.
  • Analytics events: up to two years, and deleted with your account.
  • Server logs: a few weeks, for security and debugging.
  • Billing records: as long as tax and accounting law requires, typically seven years.
  • Backups: deleted data can remain in encrypted backups until they roll over.

Your rights

Depending on where you live, you have the right to:

  • access your personal data and get a copy of it;
  • correct it if it's wrong;
  • delete it;
  • restrict how we use it while a question about it is resolved;
  • object to our using it on the basis of legitimate interests, such as analytics, and to direct marketing at any time;
  • take it with you (portability) in a machine-readable format;
  • withdraw your consent to AI features at any time, without affecting what was done before;
  • complain to a data protection authority, in the EU the one where you live or work, in the UK the Information Commissioner's Office (ico.org.uk). We'd appreciate the chance to sort it out first.

Much of this you can do yourself:

  • export your library as CSV or JSON: Settings on the website, "Your data";
  • change your name and email: Settings;
  • turn AI features on or off: Settings on the website, in the iOS app or in the extension;
  • turn off the digest or Hindsight emails: the unsubscribe link in any of them, or Settings;
  • delete your account: Settings on the website or in the iOS app.

For anything else, email support@maybelater.io from your account's address. We reply within one month, and may need to confirm it's you first.

US residents (including California, Colorado, Connecticut, Virginia and other states with privacy laws) have the right to know what we collect, to access, correct and delete it, and to opt out of its sale, sharing for targeted advertising, and profiling. We don't sell personal information, share it for cross-context behavioural advertising, or profile you in ways that have legal or similarly significant effects, and we haven't in the last 12 months. You can use an authorised agent, appeal a decision we make about your request by replying to it, and we won't treat you differently for using any of these rights.

Deleting your account

You can delete your account yourself in Settings on the website or in the iOS app. It's closed immediately: you're signed out everywhere, a Plus subscription you bought on the website is cancelled, and your email address and Apple or Google sign-in are removed from it, and links you've shared to Hindsight reports stop working. We then delete your saves, reading history, preferences, digests and reports, and the analytics linked to your account, within 30 days, except billing records we must keep by law. Deletion can't be undone, so export your library first if you want to keep it.

Deleting your account doesn't cancel a Plus subscription you bought in the iPhone app, because Apple bills it: cancel it in your Apple Account first. Its record stays with your closed account until it's deleted with the rest.

If you signed in with Apple and later delete your Apple ID or stop using Sign in with Apple with MaybeLater, Apple tells us. If Apple was your only way to sign in, we delete your account; otherwise we remove the Apple sign-in and keep the rest.

What you have to give us

An email address is required to create an account, because it's how you sign in. Payment details are required to buy Plus. Everything else is optional: your name, your interests, AI features, notifications. Without an email address we can't provide an account; without the rest, MaybeLater still works.

Automated decisions

We don't make decisions about you based solely on automated processing that have legal or similarly significant effects. Suggestions, digest selection and Hindsight archetypes are automated, but they only decide what to show you.

Analytics

We use PostHog to understand how MaybeLater is used. The events are tied to your account ID, not your name or email, and describe what happened: signing in, saving an article, opening a digest, viewing the upgrade page. They include the app version, platform and device or browser type.

  • Website: PostHog's script runs without cookies or other storage on your device, and records page views. When you're signed in it links them to your account ID and plan. PostHog uses your IP address to estimate your approximate location.
  • iOS app: the app sends events to our servers, which pass them to PostHog. There's no PostHog SDK in the app.
  • Browser extension: the extension has no analytics code. Our servers record some events when the extension uses our API, such as signing in and saving.

Analytics traffic goes through our own address (folivore.maybelater.io) on its way to PostHog. To object to analytics, email us and we'll delete the analytics we hold about your account.

Cookies and similar technology

The website uses only the cookies it needs to work:

  • A session cookie that keeps you signed in and remembers your session;
  • A security cookie (XSRF-TOKEN) that protects forms against cross-site request forgery;
  • Short-lived sign-in cookies while you sign in with Apple or Google.

Some pages keep small preferences in your browser's local storage, such as having dismissed a notice. Our analytics sets no cookies. Stripe's checkout pages, on Stripe's own domain, use Stripe's cookies. We use no advertising cookies or trackers anywhere, including the apps.

Children

MaybeLater isn't meant for children under 13, or under the age of digital consent where you live. We don't knowingly collect their data, and if we learn we have, we delete it.

Security

Everything between your devices and our servers is encrypted in transit (HTTPS). Our database and backups are encrypted at rest by our hosting provider. On iOS your sign-in token lives in the Keychain. There are no passwords to leak: you sign in with one-time codes or Apple or Google. Access to user data is limited to what running MaybeLater requires. If a breach affects your data, we'll tell you and the authorities as the law requires.

Reporting a vulnerability

If you find a security problem in MaybeLater, please email support@maybelater.io with the details and how to reproduce it. Don't access or change other people's data, degrade the service, or share the problem before we've fixed it. Test only against your own account. We'll acknowledge your report, keep you updated, and won't pursue good-faith research that follows these rules. Our security.txt has the same details.

Changes to this policy

When we change this policy, we update the date at the top. If a change matters, for example a new use of your data or a new kind of provider, we'll tell you by email or in the app before it takes effect, and ask again for your consent where it's needed.

Contact

MaybeLater LLC, [Postal address to be added].
Email support@maybelater.io.