Privacy policy

Who is responsible

Laytr is published by Waitery Inc, the data controller for the small amount of data described below. You can reach a human at support@laytr.app, normally answered within 3 business days.

What Laytr stores, and where

Everything you save — links, articles, videos, places, products, PDFs, images, screenshots, your notes, tags, cases, favourites, return times and search history — is stored in Laytr’s own storage on your device. If you leave iCloud backup or sync on, a copy is also kept in your own iCloud, which we cannot read. None of it is sent to us.

Text that Laytr reads out of your screenshots is produced on your device by Apple’s Vision framework. The images are not sent anywhere for processing, and neither is the text.

If you back up your iPhone to iCloud or a computer, your Laytr data is included in that backup, under Apple’s terms and your own settings. That backup is yours; we have no access to it.

Laytr’s own iCloud backup

Laytr also keeps a copy of your archive in your own iCloud, so your saves survive losing the app or the phone. It writes the same export ZIP you can produce yourself, into Laytr’s container in your iCloud account, and keeps the newest two copies.

It goes to your iCloud, not to us. There is no account of ours involved, no server of ours in the path, and nothing we could read: we have no more access to your iCloud than to your phone. Apple’s privacy terms govern what is stored there.

It is on by default and switched off in Settings → Storage. Turning it off stops further copies; copies already in your iCloud are yours to delete, from Laytr or from Apple’s own storage settings. Restoring from it is additive and never paywalled.

Network requests Laytr makes

Laytr contacts the internet in exactly four situations:

1. To fetch a page you saved. When you save a link, Laytr requests that page from its own website to get the title, a preview image, and — where the page allows it — the article text and pictures to store offline. That request goes to the site you saved, and nowhere else. Those sites see a request the same way any browser visit would, and their own privacy policies apply to it.
2. To keep your devices in step, through your own iCloud. On iPhone, iPad and Mac, Laytr syncs your saves between the devices signed in to your Apple Account through Apple’s iCloud, in your own private iCloud database, which we cannot read, and writes the backup described above to your own iCloud. Sync is on by default and switched off under Settings → Storage (on the Mac, Settings → Sync); both stop when iCloud is off for Laytr. Laytr for Android has no sync.
3. To complete a purchase. Purchases go through Apple’s App Store using StoreKit. Laytr never sees or handles your payment details, and there is no Laytr receipt-validation server. The purchase step is run on our behalf by RevenueCat, a purchases processor, which is described under Purchases below. It is not optional: it is the thing that performs the purchase, so it is used exactly when you buy something and never otherwise.
4. Diagnostics and campaign measurement, unless you switch them off. Described in the next section and under “Measuring our own campaigns”.

Laytr never contacts login-walled platforms at all, never downloads video from any platform, and never attempts to get past a paywall, a meter, or a consent gate.

Optional diagnostics

Laytr has two switches under Now → Settings → Privacy. Both are on by default, and you can turn either one off at any time. Off means dropped, not queued for later — and turning a switch back on never delivers anything that happened while it was off.

Turning off Share anonymous usage also deletes the random identifier it was using, so the link between what was sent before and anything sent later is broken rather than merely paused.

Share anonymous usage

Sends a fixed, published list of typed events — things like “an item was saved”, “a search returned results in the 1–10 band”, “the paywall was shown”. Values are categories and buckets, never precise counts and never text you typed. Processed by PostHog on our behalf, on their European Union servers.

Share crash reports

Sends the technical details of a crash or a freeze: the stack trace, the app version, the iOS version and the device family. Every report passes through a filter that removes URLs, file paths, filenames and e-mail addresses before it is sent. Processed by Sentry on our behalf, on their United States servers.

When usage sharing is on, a random identifier is created so two events can be recognised as coming from the same installation. It is generated from nothing — not your device, not your Apple Account, not an advertising identifier — and it is deleted the moment you switch the toggle off, so turning it back on starts a new, unlinked one. Reinstalling the app also produces a new one.

Also while usage sharing is on, once per installation, the app asks Apple whether one of our own App Store ads brought you here. It reads Apple’s AdServices attribution token and sends it to Apple, and Apple answers with the numbers of our campaign, ad group and keyword if an ad was involved — rows of our own advertising account, the same for everyone who arrived through that ad, and nothing about you. Whether an ad was involved, and from version 1.0.10 which of our campaigns, ad groups and keywords it was, is counted alongside the events above. This is not the advertising identifier (IDFA): Laytr never shows the App Tracking Transparency prompt, so iOS never gives that identifier to the app. With usage sharing off, the token is not read and nothing is sent.

What is never collected

None of the following is ever sent off your device by Laytr, on any setting:

• The addresses, titles or text of anything you saved
• Your notes, tags, collection names or favourites
• Article text, screenshots, images, PDFs, or text read out of them
• Anything you typed into search
• Reminder times or notification text
• Filenames, or anything you exported
• Your location, contacts, photos library, calendar, health or camera
• The advertising identifier (IDFA), or any identifier that other companies’ apps can read

This is enforced in Laytr’s own automated tests, which fail the build if a diagnostic event so much as carries a field that looks like user content — not by policy alone.

Advertising and tracking

We show no ads and we sell nothing to data brokers. Laytr never uses the advertising identifier (IDFA) and never presents the App Tracking Transparency prompt. We do measure which of our own links and campaigns bring people to Laytr; the next section says how.

Measuring our own campaigns

From version 1.0.15, Laytr for iPhone and iPad uses Singular (Singular Labs, Inc.), a measurement service, so we can see which of our own links and campaigns lead to an install or a purchase. It is a sales tool for us. It shows you nothing and changes nothing in the app.

While Share anonymous usage is on, Singular receives a device id Apple gives to our apps on your device (not the advertising id), your IP address, and basic device details such as the model and iOS version. If you tap one of our links, in a video description, an article or on our site, and later open Laytr, Singular uses the IP address and those device details to match the tap to the install. That is how we learn which link worked. It also reads the Apple ad token described under “Optional diagnostics”, so Apple can tell it which of our ads was involved. RevenueCat also tells Singular when a purchase happened, matched by an identifier Singular makes up for the installation. Singular gets no name, no e-mail, no account and nothing you saved.

Switch Share anonymous usage off and it stops. The app stops Singular and removes Singular’s identifier from RevenueCat, so purchases stop reaching it too. Laytr for Mac does not include it. Singular’s own policy is at singular.net/privacy-policy.

Permissions Laytr asks for

Notifications

On iPhone and iPad, asked for once and explained first: on the “Turn on reminders” step of the first-run tour, or, if you said not now there, the first time you give a save a return time. Laytr for Mac schedules no notifications and does not ask. Declining never breaks anything — the item still returns to the top of Now at the time you chose.

Photos and Files

Reached only through the system share sheet and document picker, one item at a time, when you choose to save something. Laytr never browses or indexes your photo library.

Laytr requests no location, contacts, camera, microphone or health access.

Purchases

Payment is handled entirely by Apple. Laytr receives from StoreKit only whether an active entitlement exists; it never receives your name, card, billing address or Apple Account. Refunds, renewals and cancellations are managed in your Apple Account settings, not by us.

The purchase step itself is run for us by RevenueCat (RevenueCat, Inc.), a purchases processor acting on our behalf. When you buy a plan, RevenueCat receives a random identifier its software makes up for your installation — not your name, not your Apple Account, not an advertising identifier — together with the purchase history attached to it: which plan, when, and whether a subscription is still active. Its software also sends the device id Apple gives to our apps with its requests. It never receives your name, card, billing address or Apple Account, and it never receives anything you saved. It does not use any of this for tracking or advertising, and it is not linked to you as a person. What the app unlocks is still decided by Apple’s own verified record on your device, not by RevenueCat.

There is no switch for this, and it would be misleading to offer one: RevenueCat is what performs the purchase, so it is involved exactly when you buy something and at no other time. Nothing is sent to it while you save, read, search or export.

This website

laytr.app sets no cookies, runs no analytics, loads no third-party fonts, scripts, embeds or trackers, and asks you for nothing. There is no contact form; the only way to write to us is the e-mail address above, from your own mail app.

The site is served by our hosting provider, which processes standard server request data (IP address, requested page, user agent, timestamp) to deliver pages and defend against abuse. We do not use that data to identify or profile visitors, and we do not combine it with anything else.

Retention

Your saved content is kept on your device until you delete it. Deleted items go to Recently Deleted and are recoverable for 30 days before being removed permanently. Deleting the Laytr app removes all of it from the device. Optional diagnostics data is retained by our processors for no longer than 12 months, and is deleted sooner on request. The purchase record RevenueCat holds for a random identifier is kept for as long as that purchase can still affect what the app unlocks, and is deleted on request; Apple’s own purchase record is Apple’s.

Your rights

Depending on where you live — including under the UK and EU GDPR and the California Consumer Privacy Act — you have rights to access, correct, delete, and port your personal data, and to object to or restrict its processing. Laytr is an unusual case for a good reason:

• Access and portability are built in. Your entire archive exports from the app as one ZIP of readable Markdown, HTML and your original files, free, at any time, on any plan or none. We could not provide it to you because we never had it.
• Deletion is in your hands. Delete an item, or delete the app, and it is gone. There is no copy with us to request the deletion of.
• For diagnostics data, switching the toggle off deletes the random identifier immediately and severs the link between past and future events. To have already-received diagnostics deleted, write to support@laytr.app.
• For the purchase record held by RevenueCat, write to support@laytr.app and we will have it deleted. Because the identifier is random, tell us roughly when you bought and on which plan so it can be found.

We do not sell or share personal information as those terms are defined under U.S. state privacy laws, and we have no “Do Not Sell” obligation to honour because there is no sale to opt out of. You also have the right to complain to your local data protection authority.

Children

Laytr is not directed at children and collects nothing that would identify anyone, of any age. It has no accounts, no social features, no messaging, and no user-generated content from anyone but you.

International transfers

Your saved content does not travel, because it does not leave your device. Optional diagnostics, if you enable them, are processed by our providers on infrastructure that may be outside your country, under the transfer safeguards in their own agreements with us. The purchase record described under Purchases is processed by RevenueCat on infrastructure in the United States, under the transfer safeguards in its agreement with us. This website is served from a global content network, so the page you are reading may have been delivered from a server near you.

Laytr for Android

In effect 14 October 2026 ·Laytr for Android, version 1.0.15

This section describes Laytr for Android and stands on its own. Where the rest of this page describes other devices, it does not apply to the Android app. Who is responsible, how to reach us, and what this website does are the same as above.

What Laytr stores on Android, and where

Everything you save — links, articles, files, images, screenshots, your notes, tags, cases, return times and search history — is stored in Laytr’s own storage on your phone. None of it is sent to us. Android’s own backup and device-transfer features are switched off for Laytr, so Android does not copy it to a cloud either. To move your library to another phone, export it from Laytr as a ZIP and import it there.

Text that Laytr reads out of your screenshots is produced on your phone, by text-recognition models that are bundled inside the app. The images are not sent anywhere for processing, and neither is the text. Google's text-recognition library inside Laytr does not send usage reports; we removed that. It does tell Google Play services on your phone that a recognition ran and how long it took, without your text, your picture or any Laytr id, and Google Play services handles that under Google's terms.

Network requests Laytr makes on Android

1. To fetch a page you saved. When you save a link, Laytr requests that page from its own website to get the title, a preview image and, where the page allows it, the article text and pictures to store on your phone. For links to YouTube and Vimeo it also asks that service for the video’s title and picture. The request goes to the site you saved and nowhere else. It carries no cookies and no account: only a fixed name for the app. Those sites see a request the same way any browser visit would, and their own privacy policies apply to it.
2. To complete a purchase. Purchases go through Google Play. Laytr never sees or handles your payment details. See Purchases, below.
3. Diagnostics and install source, unless you switch them off. Described next.

Optional diagnostics, on Android

Laytr has two switches under Settings → Privacy. Both are on by default, they work independently, and you can turn either one off at any time. Off means stopped at once and anything waiting to be sent is thrown away — and turning a switch back on never delivers anything that happened while it was off.

A version of Laytr sends these reports only if it was built connected to the two services named below. The first build released to testers on Google Play (version 1.0.15, build 1001501) is connected to neither, so it sends them nothing, whichever way the switches are set. What follows describes what a connected version sends.

Share anonymous usage

Sends a fixed list of typed events — things like “a save was added”, “a search returned results in the 1–10 band”, “the paywall was shown”. Values are categories and buckets, never text you typed. Each event goes with the app version, the Android version, your phone’s maker and model, your language, and the random identifier described below. Processed by PostHog on our behalf.

Share crash reports

Sends the technical details of a crash or a freeze: the stack trace, the type of error, the app version and a few technical labels. The error's own message is never sent. Every report passes through a filter that removes links, host names, file paths, e-mail addresses and long codes before it is sent. It never includes a screenshot or what was on screen, and not the phone model. Processed by Sentry on our behalf.

While usage sharing is on, a random identifier is created so two events can be recognised as coming from the same installation. It is generated from nothing — not your phone’s Android ID, not an advertising identifier, not an account — and it is deleted the moment you switch the toggle off, so turning it back on starts a new, unlinked one. Reinstalling the app also produces a new one. As with any request to any server, the services that receive these reports can see the IP address they came from.

Also while usage sharing is on, once per installation, Laytr asks Google Play which link or campaign brought you to Laytr. Play records this when you install from a link. Laytr keeps three short fields from it — source, medium and campaign name — and drops everything else, including any click identifier. They are counted alongside the events above. This is not the advertising identifier: Laytr for Android neither requests nor reads it. With usage sharing off, Play is not asked, and anything kept from it is deleted.

Laytr also asks once, during the first-run tour, where you heard about it. You can pick an answer from a fixed list or skip. An answer is counted only while usage sharing is on, and it is never typed text.

What is never collected, on Android

None of the following is ever sent off your phone by Laytr, on any setting:

• The addresses, titles or text of anything you saved
• Your notes, tags, case names or favourites
• Article text, screenshots, images, files, or text read out of them
• Anything you typed into search
• Reminder times or notification text
• File names, or anything you exported
• Your location, contacts, photos, calendar, health data, camera or microphone
• Your Android ID, the advertising identifier, or any device fingerprint

Advertising and tracking, on Android

There is none. Laytr for Android contains no advertising code, sells nothing to data brokers, does not track you across apps or websites, and does not use the Android advertising identifier or ask for the permission to read it.

Permissions Laytr asks for on Android

Notifications

Asked for once, and explained first — on the reminders step of the first-run tour, or the first time you give a save a return time if you skipped the tour. Declining never breaks anything: the save still returns to the top of Now at the time you chose.

Alarms and reminders

Android lets you allow exact reminder times in its own settings. If you do, a reminder arrives at the minute you chose. If you do not, it arrives within about ten minutes after that minute.

Running when the phone starts

Only to put your reminders back after a restart, an update, or a change of clock or time zone.

An ongoing notification while exporting or importing

Laytr shows one for as long as the work lasts, so that Android keeps it going if you leave the app. It goes away when the file is done.

Files and photos

Reached only through Android’s share sheet and file picker, when you choose to save something. Laytr never browses your photos or your files.

Internet

For the requests listed above, and to wait for a connection before making them.

Laytr for Android requests no location, contacts, camera, microphone, phone, SMS or health access.

Purchases, on Android

Payment is handled entirely by Google Play. Laytr asks Google Play which purchases you have, checks Google’s signature on that answer on your phone, and keeps what is unlocked on your phone. It never receives your name, card, billing address or Google account. There is no Laytr server and no other purchase service in the path. Refunds, renewals and cancellations are managed in Google Play, under Payments & subscriptions, not by us. While usage sharing is on, Laytr counts which plan card you chose (monthly, annual or lifetime) and whether the purchase completed, was cancelled or failed — never a price, an order number or a payment detail.

Laytr may ask Google Play to show its own rating sheet. Google decides whether to show it, and Laytr is never told what you answered.

Retention and your rights, on Android

Your saved content is kept on your phone until you delete it. Deleted saves go to Recently Deleted and are recoverable for 30 days before being removed permanently, files included. Uninstalling Laytr removes all of it. Optional diagnostics data is retained by our processors for no longer than 12 months, and is deleted sooner on request.

• Access and portability are built in. Settings → Export writes your whole library as one ZIP of readable Markdown, HTML and your original files, free, at any time, on any plan or none.
• Deletion is in your hands. Delete a save, or delete the app, and it is gone. There is no copy with us to ask us to delete.
• For diagnostics data, switching “Share anonymous usage” off deletes the random identifier immediately and severs the link between past and future events. To ask us to delete diagnostics we have already received, write to support@laytr.app. Because the identifier is random and Laytr does not show it, we may not be able to find yours, and we will tell you so if that is the case.

Children, on Android

Laytr for Android is for people aged 13 and over. It is not directed at children, and it has no accounts, no social features, no messaging, and no user-generated content from anyone but you.

If this section changes

If this section changes in a way that affects what leaves your phone, the change ships with an app release, and the Data safety section of Laytr’s Google Play listing is updated at the same time. The date at the top of this section always reflects the current version.

Changes to this policy

If this policy changes in a way that affects what leaves your device, the change ships with an app release and the App Store privacy label is updated at the same time. The effective date at the top of this page always reflects the current version.

Contact

support@laytr.app
Waitery Inc