Privacy Policy

This Privacy Policy explains how Becoming collects, uses, stores, and shares information when you use our website, web app, browser extension, and related services.

It also covers the Becoming apps for iOS and Android and our MCP endpoints, and describes how we think about further surfaces such as public APIs and other integrations. As those products launch, we may add product-specific disclosures, but this policy is intended to be the core public baseline.

Account and profile information, such as your name, email address, sign-in method, language, timezone, and subscription tier or status.

Content you choose to bring into Becoming, including sources, highlights, notes, tags, review settings, Themes, Practices, and Weekly Check-In style reflections or review activity.

Import-related information from services and files you choose to use with Becoming, including Kindle, Apple Books, Kobo, Google Play Books, Goodreads, Readwise, your X (formerly Twitter) bookmarks and likes, posts you save from X, YouTube videos, web articles and links, PDF files, and emails you send or forward to your Becoming import address, along with metadata about those imports.

Photos or screenshots of book pages that you take with your camera or choose from your photo library, which we process to extract the text you want to import.

Searches you run in Becoming, such as searching your library or looking up a book, which we use to return results.

Authentication and security data, such as session identifiers, refresh-token records, device or browser information, user agent strings, sign-in history, IP-related sign-in metadata, and operational logs.

Billing and transaction-related information needed to manage plans and subscriptions. For web subscriptions, payment details are handled by Stripe. For subscriptions bought in the mobile apps, payment is handled by Apple or Google, and our subscription provider RevenueCat keeps track of your subscription status. Becoming does not store payment card details.

Crash reports, performance diagnostics, and product analytics events that record how Becoming is used, such as the screens you open and the actions you take, together with an account identifier and an identifier for your app installation or browser. Product analytics events do not include the text of your highlights, notes, or searches. Crash reports can include technical details of the request that failed, which may sometimes contain some of that text.

On the web app, recordings of some sessions that show how you move through pages. They are set up to hide the text of your library and the photos you import.

If you turn on notifications in a mobile app, a push notification token for your device.

Browser and device storage data, including essential cookies, browser storage, extension storage, and storage within the mobile apps, used to keep you signed in and make the product work correctly, and analytics cookies and storage that tell one visit or installation apart from another.

Directly from you when you create an account, update settings, subscribe, contact us, or add content.

From connected services or files you choose to use with Becoming, such as Kindle, Readwise, X, YouTube, uploaded clipping files and PDFs, emails sent to your import address, or saved web articles.

From your device, when you give a mobile app permission to use your camera or photo library to import pages, or to send you notifications.

Automatically from your use of the service, including product interactions, session activity, security logs, and technical diagnostics needed to operate the service.

From third-party sign-in and billing providers, including Google and Apple for sign-in, Stripe for web subscriptions, and Apple, Google Play, and RevenueCat for subscriptions bought in the mobile apps.

To create and manage your account, authenticate you, keep sessions active, and secure Becoming against abuse or unauthorized access.

To import, organize, deduplicate, and display your highlights, notes, sources, and related library data.

To deliver Becoming’s core experiences, including Daily Review, Themes, Practices, account settings, billing workflows, and support.

To send service messages such as account emails, billing notices, and product-related communications needed to operate your account.

To understand service reliability, debug issues, enforce limits, prevent fraud or misuse, and improve how Becoming works.

Becoming may use your imported highlights, notes, source context, and related activity to power AI-assisted features, including generating Themes, Practices, and similar experiences grounded in your own reading.

To provide these features, including reading the text on photographed pages and searching your library by meaning, we send the relevant content, such as highlights, search queries, text you write to generate Themes, emails you forward, and photos of pages you import, to AI service providers that process it on our behalf.

We may also use this information to improve AI-powered product features over time. We do not use your information for advertising or targeted ad profiling.

If you use the Becoming browser extension, the extension may read an authentication cookie set by Becoming so it can exchange that cookie for an access token and sync content to your account.

The extension may store an access token locally in extension storage so it can continue working without asking you to reauthenticate on every action.

If you use Kindle import through the extension, the extension may access content you can see in your Kindle notebook, including book metadata, highlights, notes, and sync timestamps, and send that information to Becoming when you ask it to sync.

In the mobile apps, Kindle and X imports open that service's own sign-in page inside Becoming. You sign in directly with Amazon or X, and Becoming does not see your password. Once you are signed in, Becoming reads your Kindle highlights, notes, and book details, or your X bookmarks and likes, and sends them to your account when you ask it to sync.

If you use Readwise or other connected import methods, Becoming may store the credentials or tokens needed to complete the import and may store imported content and related metadata in your account.

Becoming uses essential cookies and similar storage to keep the service working. For example, we use authentication-related cookies for signed-in sessions and a simple language-preference cookie on the public site.

Our web and extension experiences may also use local or extension storage for operational needs, such as holding short-lived access tokens or temporary state needed to keep the product functional.

We also use analytics cookies and local storage on our website and web app to measure how Becoming is used.

We do not currently use advertising cookies, third-party ad networks, or cross-site behavioral advertising technology.

With service providers and infrastructure partners that help us run Becoming, such as hosting, email delivery, push notification delivery, subscription management, crash reporting, product analytics, and AI feature providers, which process information on our behalf. Payment, app store, and sign-in providers such as Stripe, Apple, and Google also handle the information they receive under their own terms and privacy policies.

With Google or Apple when you choose to sign in with them, with Stripe when you subscribe or manage billing on the web, and with Apple, Google Play, and RevenueCat when you subscribe in a mobile app.

With connected sources or integration providers only as needed to support the import or integration workflow you initiate, and with book catalog services, such as Google Books, when you look up a book.

If required by law, legal process, or to protect the rights, safety, security, or integrity of Becoming, our users, or others.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising.

We keep account data and user content for as long as your account remains active or as long as needed to provide the service you asked us to provide.

We may retain limited records for security, fraud prevention, legal compliance, billing, dispute resolution, or to enforce our agreements.

Imported content, settings, and AI-generated outputs may remain associated with your account until you remove them, close your account, or ask us to delete them, subject to legal or operational retention needs.

We delete photos of pages you import once they have been read, usually within two days. Pages waiting for AI credits are kept until they can be read or you delete your account, and photos you upload but never submit are deleted after about a week. The text we extract from your photos stays in your account.

You can update parts of your account information and settings from within Becoming.

If you want to access, correct, export, or delete your information, contact us at hello@usebecoming.com. We currently handle privacy requests manually.

You can also stop using a connected import source or browser extension at any time. You can manage billing or cancel a web subscription through the billing flows we provide, and a subscription bought in a mobile app from your Apple or Google account settings.

You can delete your Becoming account yourself. In the mobile app, open Settings, scroll to the bottom, and tap Delete account. In the web app at app.usebecoming.com, open Settings, go to the Account tab, and use Delete Account under Danger Zone.

If you no longer have the app or cannot sign in, write to hello@usebecoming.com from the email address on the account and we will delete it for you.

Deleting your account is permanent and cannot be undone. The help-center page linked below explains exactly what is removed, what we keep and why, and how long it takes.

How to delete your account

We use reasonable technical and organizational measures intended to protect your information. No system can be perfectly secure, and we cannot guarantee absolute security.

You are responsible for keeping your login credentials secure and for using trusted devices and browsers when accessing Becoming.

Becoming is not intended for children under 13, and we do not knowingly collect personal information from children under 13.

If you believe a child under 13 has provided personal information to Becoming, contact us at hello@usebecoming.com so we can review and address the issue.

The Becoming iOS and Android apps and our MCP endpoints — along with any public API or other integration we later offer — may collect or process account identifiers, authentication credentials or tokens, request metadata, logs, security telemetry, rate-limit information, and operational diagnostics needed to make those experiences work.

Some integrations may be used directly by end users through third-party tools, not only by software developers. We will add more specific disclosures as those products and access patterns become real.

We may update this Privacy Policy from time to time. If we make material changes, we may update the date on this page and provide additional notice where appropriate.

If you have questions about this Privacy Policy or want to make a privacy-related request, contact us at hello@usebecoming.com.