Your reading, and your privacy.

ReadGlade saves articles for later reading and lets you keep notes or ask AI about what you read. This notice describes the current preview.

Information we store

When you sign in with Google, we receive your Google account identifier, name, and verified email address. We use these to identify your library. We request basic sign-in information, not access to your Gmail, Drive, or other Google content.

Your saved article text, original URLs, titles, annotations, discussions, favorites, and reading progress are stored in Cloudflare D1 and a private Cloudflare R2 bucket. The service checks your account before returning library content.

Saving a link or sharing from iPhone

The iPhone shortcut sends the web link you select to the ReadGlade website. It does not contain an account credential or send your browser cookies. After you sign in and confirm saving, ReadGlade requests the public page from its publisher and extracts readable text. The publisher receives a request from our server. We do not send your Google sign-in details to the publisher. Pages that require a login or subscription may need you to paste the article text instead.

We keep a short-lived account-level import-attempt counter to limit repeated requests. It contains no article URL or content and is removed after a day of inactivity.

When you use AI

Saving or reading an article does not invoke an AI model. When you request AI help, we send the article text, selected passage, question, and relevant thought discussion to the configured AI provider. Define and Explain use OpenAI through OpenRouter. Summaries, questions, and thought discussions use Anthropic.

Those providers process the submitted content under their own service terms and privacy practices. Please consider what you include in a question or note before submitting it for AI help. ReadGlade stores AI usage counts, model names, token counts, timing, and request dates to enforce limits and manage costs. Completed answers you keep are part of your library.

While an answer is being prepared, we temporarily store the submitted reading context so the request can survive a lost connection. We remove that temporary copy when the request completes, fails, or expires. Deleting an article or annotation also removes its cached AI answers from our active database. Credit and usage records remain for accounting and to prevent duplicate charges.

Payments and service measurement

When purchases are available, Stripe hosts checkout and processes payment details. ReadGlade stores purchase identifiers, amounts, payment status, refunds, and credit transactions. Card details are entered on Stripe, not stored in ReadGlade.

We keep a daily account-level record of opening the library, reading an article, saving an article, viewing an answer balance, or viewing the purchase prompt. These records contain no article titles, URLs, questions, or reading content, and are retained for up to 400 days. We use them to understand whether the service is useful and to manage costs. They stay in our Cloudflare database; we do not send them to an advertising analytics service.

Cookies and external content

We use a session cookie for sign-in and a temporary cookie to complete Google authentication. The Chrome extension stores only its library URL, a save-only access credential, and its expiry in local extension storage. It does not receive or store your account name or email. When an older extension is updated and its background worker starts, it removes previously cached account details while retaining the connection credential. The ReadGlade website still receives and stores your Google account identifier, name, and verified email for sign-in and library ownership, and shows the account on its pairing confirmation page. You can disconnect that browser in the extension or revoke all extension access from your ReadGlade account. Article images may load from the original publisher or image host, which receives a normal image request from your browser.

Your controls

You can export your library from the app, delete articles and annotations, sign out, and revoke paired extension access. Deleted articles immediately disappear from your library; if storage is temporarily unavailable, removal of the stored article body is retried. Account deletion is currently handled by request rather than an in-app control. To request account and library deletion, or ask a privacy question, contact support@readglade.app. We may need to verify that you own the account before acting on a request.

Library content and account records are retained to provide the service until removed or your account deletion request is processed. Infrastructure backups and provider records may follow their own retention schedules. This preview does not include advertising or sell your reading library.