Privacy

Capora is currently in beta. This notice describes that beta. It does not present Capora as a registered company, and it states no registration number, tax number, or registered address.

An account requires an email address and a password. Authentication is provided by Supabase. Capora's application database does not store the password in plaintext. Capora also stores whether the email address has been confirmed, and the session that keeps you signed in.

When you capture or type language, Capora stores the text you submit, any context sentence supplied with it, your language settings, and the learning card generated from that text. A capture from the browser extension can also include nearby page text, the page title, and the page URL. Recall stores ratings and when a saved item is shown again. Explain notes are shown in the browser session and are not stored as part of the card.

The current extensions are for Chrome and Firefox. Connecting an extension stores a sign-in token in the browser's extension storage and sends that token to Capora with requests for your account. When you choose Add to Capora, the extension reads that page and can send the selected text, nearby text, the page title, and that page's URL. It does not upload a browsing history, and installing it does not send Capora pages you do not capture. Safari and mobile extensions are not part of this beta.

Card and suggestion text is generated by sending the relevant language to OpenAI. Account and lexicon data are stored with Supabase. If you choose Unlock Pro, checkout is handled by Dodo Payments, which collects payment details on its own page. Capora then stores the subscription status it receives.

A lexicon item you delete is removed shortly afterwards. Explore suggestions expire after 14 days. The rest of the account and lexicon is kept while the account exists. Backup periods and payment-provider retention periods are not fixed in this notice. Deleting the account removes the Capora account and its lexicon. It does not, by itself, delete the payment provider's customer record.

Where privacy law gives you a right of access, correction, deletion, restriction, objection, portability, or complaint, this notice does not waive it. You can edit some card text, delete items, and delete the account in the product. There is no data-export tool. Privacy and legal requests for this beta can be sent to robert@capora.app.

When the website hits an unexpected error, Capora sends a diagnostic report to Sentry so the problem can be found and fixed. The report can include the error and stack trace, the Capora page involved, browser and device information, and the IP address of the connection that delivers the report. It is configured not to include passwords, authentication tokens, cookies, request bodies, capture text, or third-party page URLs. The browser extensions do not send these reports. This is error monitoring, not advertising or product analytics. How long Sentry keeps a report is not stated here.

Capora can measure site use with Google Analytics 4 and advertising with the Meta Pixel. A tool loads only if you allow that choice, the site is the production site at capora.app, and Capora has configured that tool. You can accept both, reject both, or set them separately. The choice is stored in this browser only. Cookie settings, in the page footer or on sign-in and onboarding, lets you change it. Rejecting a tool, or turning it off later, stops it. This choice does not include the error reports in this notice, and it does not turn those reports off.

When a tool is allowed to run, the request can include an online identifier set by that tool, the IP address used to deliver the request, the Capora page path, campaign parameters from the link you opened (utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, and fbclid), and the events Capora sends: a page view, signup, email verification, finished onboarding, an extension connection, a first capture, the Pro paywall, starting checkout, and a confirmed Pro subscription. An extension connection can include a coarse browser label: Chrome, Firefox, or other. A first capture can include whether it came from the website or the extension. Checkout and subscription events can include the public plan and the public price. Capora does not send your email address, password, user id, sign-in token, capture text, context, or the address of a page you captured. Other parameters in the page address are left out. Advertising measurement is not sent when the page address has any other parameter, or when the previous page is not a Capora page in that same form. The tag is set so Google signals and ad personalization signals are off. The website code does not set how long Google or Meta keep the data. The Chrome and Firefox extensions do not load these tools. An extension capture is counted only when a Capora page is open to receive it.