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 describes how we think about future mobile apps, APIs, MCP endpoints, and integrations. When 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 you connect or use with Becoming, including Kindle imports, Readwise imports, web article saves, and metadata about those imports.

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. Payment card details are handled by Stripe, not stored directly by Becoming.

Browser and device storage data, including essential cookies, browser storage, and extension storage used to keep you signed in and make the product work correctly.

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, uploaded clipping files, or saved web articles.

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 for sign-in and Stripe for subscription and billing workflows.

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.

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.

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 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, payment processing, authentication, and AI feature providers.

With Google when you choose Google sign-in, and with Stripe when you subscribe or manage billing.

With connected sources or integration providers only as needed to support the import or integration workflow you initiate.

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.

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, and you can manage billing or cancel your subscription through the billing flows we provide.

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.

If Becoming later offers iOS or Android apps, public APIs, MCP endpoints, or other integrations, those products 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.